<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[ROS2 StarlingV2 image streaming]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I am trying to stream images from the hires camera over ros using the starlingV2 drone for a robotics application. I am facing a lot of issues due to network bandwidth.</p>
<p dir="auto">I would like to know what the best approach to stream images from the hires_small_color camera stream to a host computer at a modest rate of 5hz. I have tried the following approaches</p>
<p dir="auto">Simply streaming the raw images over a ros topic at a rate higher than 1 hz seems to lead to significant latency and lag which at worst case has crashed my qvio and caused the drone to crash. Running iperf seems to suggest a bandwidth of about 200Mbits between my host computer and the drone, so I imagine the issue here is in the serialization of the images.</p>
<p dir="auto">Using a RTSP server seems to stream the images quickly, but for my use case I require accurate and aligned timestamps with QVIO.</p>
<p dir="auto">I have tried to subscribe to the /hires_small_encoded topic, but the entire mpa_to_ros2 program crashes with this error.</p>
<pre><code>Interface hires_small_encoded now publishing
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
</code></pre>
<p dir="auto">I recently reflashed a recalibrated my starling2 drone. The following are the outputs of voxl-version</p>
<pre><code>--------------------------------------------------------------------------------
system-image: 1.7.8-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Sat May 18 00:10:25 UTC 2024 4.19.125
--------------------------------------------------------------------------------
hw platform:  M0054
mach.var:     1.0.1
--------------------------------------------------------------------------------
voxl-suite:   1.3.3
--------------------------------------------------------------------------------
</code></pre>
<p dir="auto">I am looking for any advice as to how to stream the hires_small images from the drone to a host computer at around 5hz.</p>
]]></description><link>https://forum.modalai.com/topic/3744/ros2-starlingv2-image-streaming</link><generator>RSS for Node</generator><lastBuildDate>Sat, 14 Mar 2026 20:08:34 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/topic/3744.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 27 Aug 2024 18:42:04 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to ROS2 StarlingV2 image streaming on Wed, 04 Sep 2024 04:15:57 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.modalai.com/uid/2555">@gitcoder</a> You really shouldn't use ROS for this, especially when network bandwidth is limited. ROS and ROS 2 add significant network bandwidth both local to the device and over the network.</p>
<p dir="auto">If you really need it over ROS 2, you should use a compressimage sensor message. Here's some code we found through a search <a href="https://answers.ros.org/question/385599/how-to-publish-a-compressedimage-in-ros2-foxy/" rel="nofollow ugc">https://answers.ros.org/question/385599/how-to-publish-a-compressedimage-in-ros2-foxy/</a></p>
]]></description><link>https://forum.modalai.com/post/18882</link><guid isPermaLink="true">https://forum.modalai.com/post/18882</guid><dc:creator><![CDATA[Moderator]]></dc:creator><pubDate>Wed, 04 Sep 2024 04:15:57 GMT</pubDate></item><item><title><![CDATA[Reply to ROS2 StarlingV2 image streaming on Tue, 03 Sep 2024 21:56:18 GMT]]></title><description><![CDATA[<p dir="auto">Wow, I had this same exact problem! Hopefully we get some feedback from the Devs soon.</p>
]]></description><link>https://forum.modalai.com/post/18880</link><guid isPermaLink="true">https://forum.modalai.com/post/18880</guid><dc:creator><![CDATA[gitcoder]]></dc:creator><pubDate>Tue, 03 Sep 2024 21:56:18 GMT</pubDate></item></channel></rss>