Bug? Still sending velocity commands when /driver/halt is called
bxc237 opened this issue · 6 comments
Hello, I map velocity commands 60ff to PDO. When I call /driver/halt, candump still showing those PDOs. Is this a bug?
I am mapping 60ff to 1602sub1 and controlling two motos with ID 1 and 2 so that the PDO are 401 and 402 here.
Hello, I map velocity commands 60ff to PDO. When I call /driver/halt, candump still showing those PDOs. Is this a bug?
No, this is expected, because the input does not change and you seem to use synchronous PDOs.
Please note that the Halt bit will be set as well, so the motor must not move.
The controller (ros_control) might reset the command during the recover service.
Please note that the Halt bit will be set as well, so the motor must not move.
Thank you for your reply, then the problem is that motors are still moving after I call halt service if these PDOs are still there and those values are not zero...very strange...It seems like the Halt bit does not work.
Another question is I map 6079 (for the motor driver I am using, is the input voltage) to PDO and when I publish 6079 and monitor the value by subscribing it, the value does not match the value I use candump. The candump value is correct but topic value is wrong. These are my eds and canopen_config.yaml files. Thank you again.
Hello, I map velocity commands 60ff to PDO. When I call /driver/halt, candump still showing those PDOs. Is this a bug?
No, this is expected, because the input does not change and you seem to use synchronous PDOs.
Please note that the Halt bit will be set as well, so the motor must not move.The controller (ros_control) might reset the command during the
recoverservice.
One more question, how to monitor if the Halt bit was set or not?
One more question, how to monitor if the Halt bit was set or not?
It is the ninth bit of the control word.
One more question, how to monitor if the Halt bit was set or not?
It is the ninth bit of the control word.
It seems that the driver is not strictly following the DS301 standard. Close issue!
It seems that the driver is not strictly following the DS301 standard. Close issue!
Could you explain this a little bit more, please?