We are currently in the process of updating the panther_ros image version (in compose.yaml in the RPi). We have encountered some issues when upgrading from 2.0.4 to 2.1.1 (husarion/panther:humble-2.1.1-20240828).
When trying this version, I added /dev/spiled-channel1 and /dev/spiled-channel2 under “devices” as per this example. This throws the following error when running docker compose :
Error response from daemon: error gathering device information while adding custom device "/dev/spiled-channel1": no such file or directory
I tracked down the change from spidev0.0 and spidev0.1 to spiledfront and spiledrear (then other terms until the current version : spiled-channel1 and 2) to your issue 347 but I don’t see any guidance on how to establish the symlink correctly. I guess that’s done within the RPi’s OS and not in the docker container ? Can you provide the steps to fix this issue (preferably steps to reproduce manually and not just an OS reinstall, which would mean some work on our end to redeploy our codebase and would deprive us from a learning opportunity )
I forgot to ask : was this information (about the new rules file) published somewhere and I missed it ? Or is it expected from users of the Panther to flash the newest OS image to the RPi for each panther_ros upgrade ?
Information about symlinks is probably not provided anywhere, so thank you for asking on the forum. Thanks to this, some customers with the same problem will be able to find a solution. We try to maintain API consistency, but the ROS 2 driver is quite new, and some issues may require reinstallation of the operating system.