I have been working the past weeks converting software for one of our standard OEM machines (Running on an Omron system (PLC/HMI/DRIVES/I/O) ) to the ctrlX core platform.
My initial agenda was to hijack the Ethercat network with the ctrlX core. There is some rack I/Os attached to the OMRON PLC, but I access these through Ethernet/IP to the Omron PLC (NJ501-1300).
But when I try to start everything up I get problems with the Omron servo drives (1s). The Omron servo drives are running EtherCat (CoE) as a base for communications.
I have tried the two different options for the Axis Profile
But I keep getting an error message when I try to start the axis profile (Please see attached picture). The Diagnostic logbook doesn’t give any future messages.
I understand the support for third-party drives such as Omron's servo drives might not yet be in place. But for us, this would be very interesting since our testing is now halted until we can get this solved.
Solved! Go to Solution.
Just to get the infos right, please confirm:
- RM2207 / Apps 1.16 in operation.
- IO Signals provided by Omron-PLC with a TCP/IPSocketcom. The nonRT behaviour is accepted.
- Drives connected directly to ECAT-Master of the ctrlX.
*ctrlXIO Engineering used to add the Omron drives in the ECAT config.
What about the COE adjustments which needs to be checked and setup - unfortuanlty the axisprofile setup is not yet supported editing the attributes via a dialog-screen. That needs to be done by adjusting the axisprofile attributes directly in the Datalayer.
Please have a look inhere: