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
The NMT state of the driver, as observed via candump, transitioning to Operational
The registered NMT state callback being called and printing out "NMT CB, state: 5"
The following being logged: "Slave 0x3: Switched NMT state to START"
An /nmt_state topic is published indicating a new NMT state of "START"
This is all as expected.
However, when I later run:
proxy_driver->reset_node_nmt_command();
The NMT state of the driver, as observed via 'candump', transitions to Initializing, then to Pre-Operational, as expected
The registered NMT state callback being called and printing out "NMT CB, state: 5"
The following being logged: "Slave 0x3: Switched NMT state to START"
An /nmt_state topic is published indicating a new NMT state of "START"
The same behavior is seen when triggering NMT commands via the /nmt_start_node and /nmt_reset_node ROS services.
Expected behavior
Calling reset_node_nmt_command() resets the drive to pre-operational mode, as expected. However, the feedback that is given through the NMT callback, the logs, and the ROS topic all indicate that the NMT state is switched to "START" (or Operational) rather than Pre-Operational.
Logs
[ros2_control_node-1] Reset NMT
[ros2_control_node-1] NMT CB, State: 5
[ros2_control_node-1] [INFO] [1738690767.237019553] [transport_base]: Slave 0x3: Switched NMT state to START
[ros2_control_node-1] Start NMT
[ros2_control_node-1] NMT CB, State: 5
[ros2_control_node-1] [INFO] [1738690772.048130197] [transport_base]: Slave 0x3: Switched NMT state to START
[ros2_control_node-1] Reset NMT
[ros2_control_node-1] NMT CB, State: 5
[ros2_control_node-1] [INFO] [1738690775.697599678] [transport_base]: Slave 0x3: Switched NMT state to START
[ros2_control_node-1] Start NMT
[ros2_control_node-1] NMT CB, State: 5
[ros2_control_node-1] [INFO] [1738690780.508815138] [transport_base]: Slave 0x3: Switched NMT state to START
[ros2_control_node-1] Reset NMT
[ros2_control_node-1] NMT CB, State: 5
[ros2_control_node-1] [INFO] [1738690784.157194190] [transport_base]: Slave 0x3: Switched NMT state to START
Describe the bug
The reported NMT state is incorrect, at least from what I have observed while using the Proxy Driver
To Reproduce
Setup:
I later start one of the drivers as follows:
This results in:
candump
, transitioning to Operational/nmt_state
topic is published indicating a new NMT state of "START"This is all as expected.
However, when I later run:
/nmt_state
topic is published indicating a new NMT state of "START"The same behavior is seen when triggering NMT commands via the
/nmt_start_node
and/nmt_reset_node
ROS services.Expected behavior
Calling
reset_node_nmt_command()
resets the drive to pre-operational mode, as expected. However, the feedback that is given through the NMT callback, the logs, and the ROS topic all indicate that the NMT state is switched to "START" (or Operational) rather than Pre-Operational.Logs
From candump:
From ROS2 CLI:
Setup:
The text was updated successfully, but these errors were encountered: