@zachary-lowell-0 That worked perfectly, thanks!
D
DavidTorres
@DavidTorres
Posts
-
VOXL 2 SDK 1.8.0 ROS2 missing -
VOXL 2 SDK 1.8.0 ROS2 missingAfter upgrading a VOXL 2 (M0054) from SDK 1.6 to 1.8.0,
apt-get install voxl-ros2-foxyreturns "Unable to locate package" and/opt/ros/foxyis gone. My sources point atdists/qrb5165/sdk-1.8/binary-arm64/, which updated today.apt-cache search ros2only returnsvoxl-microdds-agent, andvoxl-mpa-to-ros2is also missing from the repo and from/data/voxl-suite-offline-packages.Questions:
- Was
voxl-ros2-foxyremoved from 1.8, or is it renamed or delayed? - Is there a release date for a 1.8-compatible Foxy package that includes
voxl-mpa-to-ros2? - Until then, what's the supported way to run Foxy on 1.8 with MPA-to-ROS2, microDDS to PX4 1.18, and no Docker?
Thanks,
- Was
-
Bots Unlimited Wifi CrashHi, I'm running a Bots Unlimited Sparrow (M0213 VOXL 2 Wi-Fi add-on) on a VOXL 2 M0054.
Setup:
- System image: 1.8.09-M0054-14.1a-perf-20261009 (
/etc/version) - voxl-suite 1.8.0
- Kernel:
4.19.125 - Packages: botsu-sparrow 1.0.8-r0, botsu-sparrow-utils 1.0.14, voxl2-wlan 1.0-r0
- Firmware/driver: USB8997---16.197.121.p2-MX5X16505.p7.2-(FP197)
- Station mode, 5 GHz, 80 MHz. Country set manually with
iw reg set(does not persist across reboot) - Mitigation installed with the sparrow-ba bundle, power-cycled.
verifyreports ADDBA timeout 0, mitigation ACTIVE, one BA stream.
Crash (during an iperf3 UDP test at -b 800M; iperf3 reported about 142 Mb/s delivered):
Timeout cmd id (...) RSSI_INFO [0xa4]tx_pending = 415,wmm_tx_pending[0] = 366fw_dump_timer fired,Start to process hanging, then repeatedBlock woal_cfg80211_scan in abnormal driver statedmesg | grep "Timeout cmd id = 0xd0"returns nothing, so this doesn't appear to be the DELBA path the workaround covers.- No
/data/dump_*directory was created.
Questions:
- Is the RSSI_INFO timeout under TX load a known issue? Is there a fix or firmware update?
- Is there a recommended maximum offered load to avoid transmit queue buildup?
- Is botsu-sparrow 1.0.8-r0 the intended driver for this image, alongside botsu-sparrow-utils 1.0.14?
- How do we persist the regulatory domain on this image?
See the dmesg tail https://drive.google.com/file/d/1hVnhbvKdmFDvvVXIw6YxXD4b4HGkP1hO/view?usp=sharing
- System image: 1.8.09-M0054-14.1a-perf-20261009 (