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 would like to make a raspberry pi device communicate to a ROS pc without installing ROS on the rpi itself.
I know that ROS2 supports rpi OS but I'm sticking to ROS1 and I don't want to compile ROS1 from scratch on the rpi just to publish one single ROS message. I also don't want to install something like LCM and translate from LCM to ROS.
If I understand correctly, the cros library can scan a custom message definition (i.e. a *.msg file) and act as a publisher or subcriber for this message type.
My question is: does the library support nested message definitions, i.e. a custom message that refers inside itself to another custom message?
Thanks.
The text was updated successfully, but these errors were encountered:
Hi all,
thanks for making this project.
I would like to make a raspberry pi device communicate to a ROS pc without installing ROS on the rpi itself.
I know that ROS2 supports rpi OS but I'm sticking to ROS1 and I don't want to compile ROS1 from scratch on the rpi just to publish one single ROS message. I also don't want to install something like LCM and translate from LCM to ROS.
If I understand correctly, the
cros
library can scan a custom message definition (i.e. a*.msg
file) and act as a publisher or subcriber for this message type.My question is: does the library support nested message definitions, i.e. a custom message that refers inside itself to another custom message?
Thanks.
The text was updated successfully, but these errors were encountered: