Dear Expert,
There are 4 MoMo connected to the integrated SINAMICS of SIMOTION D445.

The following errors have been observed sometimes inthe drive and it cannot be acknowledged. We have to switch off the power supply for one MoMo and the controller.

1. Vector A1315: Drive object not ready for operation.
2. Vector A1481 Topology: Comparision power unit missing in actual topology.
3. Vector F30885: CU Drive - Cliq- Cyclic data transfer.

Observation: One of the 4 MoMo goes into not ready state(inferred by the red led indication in MoMo) while the other 3 are healthy.
The Drive CliQ cables are routed through a conduit and the connection of CliQ cable is tight.
So what may be the reason for this error and the preventive action?

Attached: the screenshot of thetopolgy window of drive

Regards
Bist

 check drive-cliq cable contact tight,;

  check motor encoder drive-cliq  insert ok,

  replace  power module to test;

Wi21

Greetings estimated support service I write because I had a recurring fault in a sinamic s120 the same is intermittent the equipment can run for hours and also several days however when the fault occurs the motor is left uncontrolled which damages the process The fault is F31885 N, A) Encoder 1 DRIVE-CLiQ (CU): Cyclic data transfer disturbed xx = 21 hex = 33 dec: The cyclic telegram has not yet arrived. I hope they help solve this problem .

 Hello, did you solve your problem??? if answer is yes then how did you solve?

thanks in advanced

Eduardo, maybe it's your same fault but the circumstances aren't the same.

Unfortunately the thread started never explained how he solved the problem (this is not a great attitude for this forum) so you need to search again the reasons.

A DQ error like that should never appear. If it happens after few minutes (hours?) AND if the envirinmental conditions are ok (mainly temperature) AND if the cable/connectors integrity is fine AND if the component with that error is always the same ( nevertheless the others S120) then one can consider changing the S120 with a new one...

Just my 2 cents

We had similar problems (random faults 30860 31860 30885 31885).

So, we suspected that the encoder on the servomotor failed.

The solution was to replace the servo with a new one . . .