Because multiple robots will usually be present on the same IP network, their respective graphs must be distinguished from each other. The ROS2 environment variable ROS_DOMAIN_ID is provided to accomplish this. This change retrieves the Raspberry Pi's serial number and then does some simple modulo arithmetic on it to get a usually unique integer between 1 and 101, inclusive.
Tested by updating updater.py manually on my dev robot and rebooting the Raspberry Pi. Waited for the RoboQuest application to start and then attempted ros2 topic list and ros2 node list from my desktop. Both commands didn't list anything
Set the desktop ROS_DOMAIN_ID the same as the Raspberry Pi containers and repeated the commands. Now both show the graph from the Raspberry Pi.
Because multiple robots will usually be present on the same IP network, their respective graphs must be distinguished from each other. The ROS2 environment variable ROS_DOMAIN_ID is provided to accomplish this. This change retrieves the Raspberry Pi's serial number and then does some simple modulo arithmetic on it to get a usually unique integer between 1 and 101, inclusive.
Tested by updating updater.py manually on my dev robot and rebooting the Raspberry Pi. Waited for the RoboQuest application to start and then attempted ros2 topic list and ros2 node list from my desktop. Both commands didn't list anything Set the desktop ROS_DOMAIN_ID the same as the Raspberry Pi containers and repeated the commands. Now both show the graph from the Raspberry Pi.
https://github.com/billmania/roboquest_core/issues/41