rosserial vs custom serial protocol #127
Replies: 2 comments 3 replies
-
@niwhsa9 actually already brought this to our attention less than a month ago (mentioned in #esw-23) Here's what I had to say: " Here are some links for future reference. |
Beta Was this translation helpful? Give feedback.
-
Ok sounds good, altho I now have a different possible solution. I found this ROS package specifically for this IMU that seems to have a pretty well made python API for it and they suggest using UART mode and just connecting it straight to the computer over USB instead of having an arduino. Assuming this package actually works, is there any reason on the hardware side that we couldn't do this? |
Beta Was this translation helpful? Give feedback.
-
For our hardware drivers that use serial to communicate from an external processor to our main computer, I found the rosserial package which seems to be the recommended solution. Basically it will make your external processor a ROS node and have it publish/subscribe to data encoded over serial, and then you have a translator node on the main computer which interfaces with that serial connection and translates it into the main ROS network.
Is this something we want to do? Our previous solution as I understand (at least for the IMU) is to implement our own very simple custom serial protocol for sending data, then decode that on a driver node running on the main computer, which would then publish that data to the main network. I worry the rosserial solution could be less reliable, but I don't actually know enough about the characteristics of serial communication to know if that worry is founded. @tabiosg @sashreek1 what do you think?
Beta Was this translation helpful? Give feedback.
All reactions