How to monitor OP mode in Panasonic A6B Ethercat

Dear all,

Is there any method to monitor OP state of driver?? Many times some drives not coming in OP mode and also many times not coming Servo Lock. And still Linuxcnc goes into homing and working mode. How to stop this?? Any solution? 

Thanks in Advance 

try running this in terminal:

however drives not getting to OP mode must have a reason. What hardware are you on? I have similar issue with RPI5 and generic driver. I tried faster servo threads, but developers told me, that generic driver is only good for 1 000 000 ns servo thread.

it is strange that LCNC doesn't throw an error in this case. For my EtherCAT drivers if any of those not in OP mode or not ready and i try to move or do something with it, it power machine off and throw an error.

As an addition i also check for OP of driver with `slave-oper` pin, each lcec device should have it as well as other states
slave-state-init
slave-state-op
slave-state-preop
slave-state-safeop

also you can designate your own pins from driver state from int -> bit

<pdoEntry idx="6041" subIdx="00" bitLen="16" halType="complex">
<complexEntry bitLen="1" halPin="status.ready-to-switch-on" halType="bit"/>
<complexEntry bitLen="1" halPin="status.switch-on" halType="bit"/>
<complexEntry bitLen="1" halPin="status.operation-enabled" halType="bit"/>
<complexEntry bitLen="1" halPin="status.fault" halType="bit"/>
<complexEntry bitLen="1" halPin="status.voltage-enabled" halType="bit"/>
<complexEntry bitLen="1" halPin="status.quick-stop" halType="bit"/>
<complexEntry bitLen="1" halPin="status.switch-on-disabled" halType="bit"/>
<complexEntry bitLen="1" halPin="status.warning" halType="bit"/>
<complexEntry bitLen="1"/>
<complexEntry bitLen="1" halPin="status.remote" halType="bit"/>
<complexEntry bitLen="1" halPin="status.target-reached" halType="bit"/>
<complexEntry bitLen="1" halPin="status.internal-limit-active" halType="bit"/>
<complexEntry bitLen="1" halPin="status.op-limit-active" halType="bit"/>
<complexEntry bitLen="1" halPin="status.op-limit-active1" halType="bit"/>
<complexEntry bitLen="1"/>
<complexEntry bitLen="1" halPin="status.home-find" halType="bit"/>
</pdoEntry>

Thanks for response ... Yes, I'm giving try to this.

I am using i3 gigabyte motherboard. No ethercat Switch. Using parallel port for I/O

Many times drives getting into OP Mode without trouble. and If i restart system or forgot to power on drive before computer then it is volatile. any random drive out of 5 is not getting into OP mode. Strange is  from all 5 = X Y1 Y2 Z A .. .sometimes it is Y2 Z sometimes X Y1 or any random and last drive A is coming in OP mode and Servo-ON normally


 

it is strange that LCNC doesn't throw an error in this case. For my EtherCAT drivers if any of those not in OP mode or not ready and i try to move or do something with it, it power machine off and throw an error.

 Yes power cycle reset error often. But not sure....

As an addition i also check for OP of driver with `slave-oper` pin, each lcec device should have it as well as other statesslave-state-initslave-state-opslave-state-preopslave-state-safeop 

Ok I'm checking this.

also you can designate your own pins from driver state from int -> bit<pdoEntry idx="6041" subIdx="00" bitLen="16" halType="complex"><complexEntry bitLen="1" halPin="status.ready-to-switch-on" halType="bit"/><complexEntry bitLen="1" halPin="status.switch-on" halType="bit"/><complexEntry bitLen="1" halPin="status.operation-enabled" halType="bit"/><complexEntry bitLen="1" halPin="status.fault" halType="bit"/><complexEntry bitLen="1" halPin="status.voltage-enabled" halType="bit"/><complexEntry bitLen="1" halPin="status.quick-stop" halType="bit"/><complexEntry bitLen="1" halPin="status.switch-on-disabled" halType="bit"/><complexEntry bitLen="1" halPin="status.warning" halType="bit"/><complexEntry bitLen="1"/><complexEntry bitLen="1" halPin="status.remote" halType="bit"/><complexEntry bitLen="1" halPin="status.target-reached" halType="bit"/><complexEntry bitLen="1" halPin="status.internal-limit-active" halType="bit"/><complexEntry bitLen="1" halPin="status.op-limit-active" halType="bit"/><complexEntry bitLen="1" halPin="status.op-limit-active1" halType="bit"/><complexEntry bitLen="1"/><complexEntry bitLen="1" halPin="status.home-find" halType="bit"/></pdoEntry> 

This is bit difficult for me to understand can you simplify please. I'm attaching my XML file. I don't know how to grab drive parameters for XML file.  

 

It doesn't help today, but there's an open bug for similar issues.  We also fail to notice, for example, if you oversubscribe the power on a row of Beckhoff EL* modules.  The modules themselves know and stop working, but that's utterly invisible in LinuxCNC.

We need to do a better job of monitoring diagnostics, and then expose them in the UI one way or another.