How to monitor OP mode in Panasonic A6B Ethercat

scottlaird wrote:

For what it's worth, "parallel port" means something very different in this context. It's the 25-pin connector used to talk to pre-USB printers. 

Pre-USB???? Surely Pre-ethernet is a better benchmark. Never buy a USB printer.. Insist on an ethernet port.
I'll take my old digital document production hat off now!
 

I have had similar issues when trying EtherCAT on new Raspberry Pi 5 running faster servo threads.
You can try pcie ethernet card with intel chip and then change master device 0  MAC address and generic driver for igb/igc/e1000e or similar in ethercat.conf - depending on you ethernet controller driver. It might be an issue with onboard ethernet controller.
On my dell optiplexes onboard ethernet results in pings 0.300ms and pcie ethernet around 0.080ms, which makes a difference.

Hello Everyone,

I was trying different suggestions as per post replies but not getting foolproof system. However I was monitoring Hal configuration. I found one pin "lcec.0.0.drivestatus-0" which is representing drive OP state. This pin goes high when drive is healthy and is in OP state.
I have already configured Axis Fault alarm to "lcec.0.0.drivestatus.3" because it is going low when drive is healthy and there is no alarm.

Now, do I need to invert "lcec.0.0.drivestatus-0" ? How it can be done? And if there is other option to link this pin with Emergency or even axis limit(ghetto idea) or anything which prevents EMC power-on(Servo-On)

Or may be more reliable setup
Check drive status
If ok then only power On, or else alarm
Check Servo On
If ok then only power on or else alarm


Thanks in Advance.     

Anyone?

Now, do I need to invert "lcec.0.0.drivestatus-0" ? How it can be done?

Maybe try the 'NOT' component:
linuxcnc.org/docs/devel/html/man/man9/not.9.html

It is recommended to solve the problem from the root. One of the three servo drives I had before, the z-axis, also randomly failed to operate. Later, I found that the xml version in this drive was different from the other two. It was higher than the xml version in the other two drives, and it would automatically create a network interface. Later, I copied the sii data in the x-axis servo drive and wrote it to the z-axis servo drive that randomly failed to operate.