ctrlX DRIVE w/ PROFINET stuck in status = prepare (FWA AXS0308.03)

[lg-lima]

Hi colleagues,

There is an issue with the profinet protocol which reports status prepare for no apparent reason, consequently all communication seems to be stopped with the control. I had this problem earlier (3-4 months ago), and solved it by upgrading from firmware 0308.02 to 0308.03, initially seemed to had solved it but it just came back from the dead.

I know there is an recent firmware version 0308.04, didn't tested it though.

Any thoughts on this?

PS: Had to zip the .par file because the extension is not supported on community.

[lg-lima]

@Drives_Uwe , can you evaluate or forward to someone please? We have little time with the costumer.

[Drives_Uwe]

It looks like the initialization was stuck with an encoder access problem, see diagnostics trace:

If this problem was present at the time you report the error this is clear.

Of course it could be helpfull to update to the ltest firmware version. I attached it in here.

[lg-lima]

@Drives_Uwe 

Oh, I see. What could be the reason behind this encoder communication errors? Any hints on what we should check?

This error is not persistent, it only occured twice this week. The error is reset with a drive reboot.

Additionally, we're using MSK motor with ctrlx drive multiencoder interface.

[Drives_Uwe]

Check for shielding and grounding of the motor power and encoder cables.

[lg-lima]

We have much more information now, and things look quite different than initially reported at creation of this thread.

This issue happens every time the user turns the machine on. The sequence below describes what we diagnosed:

- Drive boot to PM

- Master PLC boot and switch profinet to Operating

- Drive switch to Ab

- Drive Profinet Producer reports status running

- Drive Profinet Consumer reports status prepare (screenshot attached in first post)

This means that we can see position feedback values being refreshed over time, but we can't switch to AH through control word because producer seems to not be running.

Those encoder errors in diagnostic trace doesn't seem to affect the initialization of the drive. So problems with grounding are discarded for now.

Any experience with this behavior?

[lg-lima]

Not sure, but for me seems to be something related with the parameters configured in Consumer.

[Drives_Uwe]

Did you already test with new firmware? Please resend the parameter file (format: all parameters) when you have the problem.