CoE drive does not switch power on

[joelfernandez]

Hello @CodeShepherd,

I tried the same configure than Eric, but I have news errors. These errors are not the same but I can't to solve. Errors are:

Any ideas?

[CodeShepherd]

Moved to own topic from "Cannot switch to "Running" configuring a ctrlX Drive in CoE with FSoE".

Please tell us the used ctrlX OS app versions or add a system report of your system (How to generate a system report and switch on additional traces).

[joelfernandez]

Hello @CodeShepherd,

I attach the system report of the ctrlX.

Thanks.

[CodeShepherd]

From control side we could see a problem in the first place, you could add the diagnostic message of the drive to the cyclic data and the axisprofile to get all drive error messages into the controls diagnostic logbook.

Did you check if DC bus is loaded at the drive? Is the drive in a non safety state? Could you add a parameter save of all drive parameters after trying to switch power on?

[joelfernandez]

Hello @CodeShepherd,

I put the diagnostic message but it doesn't change when the error appears. It's strange because when the error appears, the drive is in Ab and ready for operation. The diagnostic message that I have is: 16#C00A0012

The drive have DC and it doesn't have a safety state because is in Ab. I attach the backup of the drive (because I only work with 1 ctrlX Drive).

Thanks.

[Michael_A]

Good morning, i guess it is the missing mapping of Mode of Operation (0x6060) and Mode of Operation Dispaly (0x6061) in the axisprofile. Add this two parameters to the cyclic data of your io-project for the CoE drive and than map it to the axisprofile.

[joelfernandez]

Hello @Michael_A,

I tried to mapping the Mode of Operation and Mode of Operation Display and I can't work with them, because when I add these parameters in the IO, the safex doesn't have connection with the drive (safex with yellow LED) and it's not working. If I don't add these two parameters the safex works and communicates with drive and ctrlX (safex with green LED).

Also, I tried the same configuration with Ethercat SoE instead of Ethercat CoE and I can’t move the drive with motion. I can activate the drive, but I got an error, the same error had Eric in his drive.

The problem is when I got this error I can’t reset, I switch off the system (Safex, Drive and ctrlX) and I switch on the system but I can’t activate the drive again. The drive is in StandStill_Pending when I activate the power in the drive (also I activate the Quick Stop option because @ericvergara  told me this is the bit that can power the axis). 

[Michael_A]

Hello, can you try to disable the safety on the drive and enable the drive without safety. In the parameterfile there are FSoE connection errors.
Let's try first without safety to switch to running and power. 

[joelfernandez]

Hello @Michael_A,

If I try to move with safety, the drive is enable and the motor can move. The problem is when the safety is enable and active. Any ideas?

[Michael_A]

May be we should do a teams meeting so that i can have a look on your system.

[joelfernandez]

Hello Michael,

I sent you my mail to do a meeting.

Thanks.

[Michael_A · Accepted solution]

@CodeShepherd ,
the problem is solved. It was caused by mapped but not used (allways updated) MDT variables (DL realtime) in the PLC.