-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EcCiA402Drive] Fault with status word: 4744 directly after Operation Enabled, but not every time #151
Comments
Hello @bryangd34, To help us to debug your problem, could you share your config file?
And the error does not seem resettable, as you are probably in automatic reset mode the ethercat ros driver tries indefinitely to reset it.
replace the Could you also share the ethercat kernel logs?
delete the kernel messages :
then launch the ros node and stop it after a few seconds (the time for an error reset cycle) and finally retrieve the kernel messages: Ideally, you should follow this procedure for a functional case and a non-functional case |
Thanks @pzanne for all your suggestions.
FYI, the drive seems to be in error most times at start up, even when successfully entering operation enabled and remaining there: |
I am working with a ZeroErr drive unit and am using the generic plugin EcCiA402Drive.
I would say approximately 90% of the time, when I try launch and bring up the drive, I get the following:
...
[ros2_control_node-1] Slave: State 0x01.
[ros2_control_node-1] Slave: State 0x02.
[ros2_control_node-1] Domain: WC 3.
[ros2_control_node-1] Domain: State 2.
[ros2_control_node-1] STATE: Fault with status word :648
[ros2_control_node-1] Slave: State 0x04.
[ros2_control_node-1] Master AL states: 0x0A.
[ros2_control_node-1] Slave: State 0x08.
[ros2_control_node-1] Slave: operational.
[ros2_control_node-1] STATE: Switch on Disabled with status word :4816
[ros2_control_node-1] STATE: Ready to Switch On with status word :4785
[ros2_control_node-1] STATE: Switch On with status word :4787
[ros2_control_node-1] STATE: Operation Enabled with status word :4791
[ros2_control_node-1] STATE: Fault with status word :4744
[ros2_control_node-1] STATE: Switch on Disabled with status word :4816
[ros2_control_node-1] STATE: Ready to Switch On with status word :4785
[ros2_control_node-1] STATE: Switch On with status word :4787
[ros2_control_node-1] STATE: Operation Enabled with status word :4791
[ros2_control_node-1] STATE: Fault with status word :4744
...
and then about 10% of the time, the drive is successfully brought up:
[ros2_control_node-1] Slave: State 0x01.
[ros2_control_node-1] Slave: State 0x02.
[ros2_control_node-1] Domain: WC 3.
[ros2_control_node-1] Domain: State 2.
[ros2_control_node-1] Slave: State 0x04.
[ros2_control_node-1] STATE: Ready to Switch On with status word :689
[ros2_control_node-1] STATE: Switch on Disabled with status word :4816
[ros2_control_node-1] Slave: State 0x08.
[ros2_control_node-1] Slave: operational.
[ros2_control_node-1] STATE: Ready to Switch On with status word :4785
[ros2_control_node-1] STATE: Switch On with status word :4787
[ros2_control_node-1] STATE: Operation Enabled with status word :4791
From here, I can control the drive successfully.
Does anyone know how I may get the drive to consistently start successfully?
See also this issue
The text was updated successfully, but these errors were encountered: