You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a Copley NES drive and trying to operate it in CSP mode. When I try to use the .nan default value however it always sends 0 as the position command. I've confirmed this by querying the 0x607a object with an SDO upload. The drive always rejects this change because it's too large of a step from its real position and it triggers a following error.
If I set a value close to the real current position value in the default then the drive will properly control to that position on startup. Querying the 0x607a object here will give the value that I set in the default. So the drive is properly configured, going to the correct operation state, and the driver is sending the value that I've commanded. The failure seems to be in the .nan feedback interface. A potentially related issue is that I'm also not able to send a command to the position command interface with a ROS2 Control ForwardCommandController, again it's always 0.
I'm successfully using the .nan position feedback with other devices, but there seems to be something in particular wrong with this specific drive combination. I think it may be related to the drive using a TPDO/RPDO in a non standard address range (0x1700 for RPDO and 0x1B00 for TPDO), but that's an unconfirmed suspicion.
I've spent a few days debugging this so any help would be greatly appreciated.
Hello, I encountered a similar issue. In my case, the root cause was the joint_trajectory_controller.
The problem was that the controller was being spawned too early, causing the position command to default to zero. I resolved this by introducing a delay before spawning the controller, making sure that the system had enough time to initialize properly.
Thanks for the response @filippo-bosi , but in my case it looks like it was a similar issue to this other issue #125 . I didn't have object 0x6061 mode of operation display mapped and that apparently prevents all commands to the target position object. This seems like a pretty important dependency that should be mentioned in the documentation
I'm using a Copley NES drive and trying to operate it in CSP mode. When I try to use the .nan default value however it always sends 0 as the position command. I've confirmed this by querying the 0x607a object with an SDO upload. The drive always rejects this change because it's too large of a step from its real position and it triggers a following error.
If I set a value close to the real current position value in the default then the drive will properly control to that position on startup. Querying the 0x607a object here will give the value that I set in the default. So the drive is properly configured, going to the correct operation state, and the driver is sending the value that I've commanded. The failure seems to be in the .nan feedback interface. A potentially related issue is that I'm also not able to send a command to the position command interface with a ROS2 Control ForwardCommandController, again it's always 0.
I'm successfully using the .nan position feedback with other devices, but there seems to be something in particular wrong with this specific drive combination. I think it may be related to the drive using a TPDO/RPDO in a non standard address range (0x1700 for RPDO and 0x1B00 for TPDO), but that's an unconfirmed suspicion.
I've spent a few days debugging this so any help would be greatly appreciated.
YAML config:
The text was updated successfully, but these errors were encountered: