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 have encountered some odd behavior. At some point, a subscriber topic decrease throughput, when the publishing topic does not decrease the throughput.
I have a cpp node publishing a string representing a base64 image at 10Hz, which its rate does not decrease over time. Checked via ros2 topic hz /b64_image.
Rosbridge_server is launched too, via ros2 launch rosbridge_server rosbridge_websocket_launch.xml.
A webpage is receiving /b64_image with roslibjs, and the image is rendered into a canvas. Eventually, the frame rate (fps) of message received decrease almost to 0 fps (image attached). If, I refresh manually, the webpage returns to 10fps but return to 0 fps a few seconds later.
Roslibjs topic is configured like this:
var listener = new ROSLIB.Topic({
ros : ros,
name : '/b64_image',
messageType : 'std_msgs/String',
queue_size: 1,
throttle_rate: 10
})
Library Version: 1.3.2-1jammy.20240517.175148
ROS Version: ROS2 Humble
Platform / OS: Ubuntu 22.04
Expected Behavior
I expect to get an almost constant frame rate at 10 fps at the webpage, let's say forever.
Actual Behavior
Webpage has 10 fps during only a few seconds/minuts.
Thanks
The text was updated successfully, but these errors were encountered:
We use our robots in environments where the network conditions are sometimes quite bad and I have seen the exact same issue which seems to be exacerbated by the network dropping in and out. I was able to fix it by removing the timeout at
Hi,
I have encountered some odd behavior. At some point, a subscriber topic decrease throughput, when the publishing topic does not decrease the throughput.
Roslibjs topic is configured like this:
Expected Behavior
I expect to get an almost constant frame rate at 10 fps at the webpage, let's say forever.
Actual Behavior
Webpage has 10 fps during only a few seconds/minuts.
Thanks
The text was updated successfully, but these errors were encountered: