The issue of being unable to connect after changing the device IP.

[Lafatalite]

Currently, I have encountered two issues during development. The first issue is that after changing the IPv4 address of the device that deploys pyri, some default devices fail to connect because the system reads a database file at startup. Is there an effective way to update the device addresses?

The second issue involves a custom device. After restarting the custom device, pyri cannot connect to it—even though the device status shows as "ready"—and it fails to execute its functions. The console log indicates that the device object cannot be found, which suggests that the device management within pyri has not updated the device connection promptly. After waiting for a while or restarting pyri, the device works normally. Is there a better method to reconnect to the device faster after a custom device restart?

[johnwason]

Currently, I have encountered two issues during development. The first issue is that after changing the IPv4 address of the device that deploys pyri, some default devices fail to connect because the system reads a database file at startup. Is there an effective way to update the device addresses?

I have been working on a better strategy for managing device connections in the Robot Raconteur packages but it has not been ported to PyRI yet.

The second issue involves a custom device. After restarting the custom device, pyri cannot connect to it—even though the device status shows as "ready"—and it fails to execute its functions. The console log indicates that the device object cannot be found, which suggests that the device management within pyri has not updated the device connection promptly. After waiting for a while or restarting pyri, the device works normally. Is there a better method to reconnect to the device faster after a custom device restart?

By default for most device manager clients, not all devices are connected at startup. You may need to call the device_manager.connect_device() function. Here is an example: https://github.com/pyri-project/pyri-robotics-browser/blob/549fecff9b8b291be2a2f499a9f22eecf5fdc069/src/pyri/robotics_browser/components/jog_component.py#L555

I am planning to spend some time working on PyRI to fix the issues you have found and improve the database structure, but I have other higher priority tasks at the moment. I will probably work on it starting in Q2.

[johnwason]

I will be presenting about the Tesseract motion planner and PyRI during the ROS-I Tesseract meeting April 10 at 10:30 am EDT. Sign up here if you want to join: https://rosindustrial.org/events/2025/1/9/tesseract-monthly-check-in-f6ayn-92mpa-dpjz7