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
When publishing messages that consist of an (unspecified length) array, that array is not filled and always received empty.
I'm busy making a ROS2 (Foxy) driver for an old Neato vacuum robot using https://github.com/LoyVanBeek/neato_rust. I just started learning Rust and wanted to do more ROS2, so why not cause myself a lot of trouble learning 2 things at the same time?
The Rust interface with the robot over serial works fine, next step is to wrap that driver in a ros2-rust Node. I can perfectly fine publish a message, but when I publish a sensor_msgs/LaserScan and echo the topic, the ranges field is just empty. Same for intensities.
From what I gather, the generated code concerning a LaserScan message is this, but AFAICT, there is no code generated to handle the ranges/intensities:
When publishing messages that consist of an (unspecified length) array, that array is not filled and always received empty.
I'm busy making a ROS2 (Foxy) driver for an old Neato vacuum robot using https://github.com/LoyVanBeek/neato_rust. I just started learning Rust and wanted to do more ROS2, so why not cause myself a lot of trouble learning 2 things at the same time?
The Rust interface with the robot over serial works fine, next step is to wrap that driver in a ros2-rust Node. I can perfectly fine publish a message, but when I publish a
sensor_msgs/LaserScan
and echo the topic, theranges
field is just empty. Same forintensities
.From what I gather, the generated code concerning a
LaserScan
message is this, but AFAICT, there is no code generated to handle the ranges/intensities:Same issue holds for eg. an Int8MultiArray (which I thought was the simplest message having an array)
I'd love to help out, but this is currently beyond my Rust chops.
The text was updated successfully, but these errors were encountered: