@mawriyo Here3 GPS support is now available in voxl-px4 1.4.27 available here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.4.27-202209272330_arm64.deb. This needs to be used with the Here3 in "i2c mode" which means opening up the unit, placing the switch in the "i2c" position, and creating a custom wiring harness to route UART and i2c lines over to VOXL 2 J19. Launch voxl-px4 with the new -h flag to enable this new support. The Here3 unit has an ak09916 magnetometer and TCA62724FMG LED controller.

Hi, Is there any news about ros2 ? Best, Aya

TX Overflow happens because you are trying to connect to QGC with the serial connection being leveraged by gazebo for HITL. So what you need to do is open QGC after gazebo is running and connected to the VOXL2. Once this is done, you can only connect to QGC via the UDP connectoin. This can be done by enabling voxl-vision-px4 and voxl-mavlink-server services. So you connect to the gazebo via the serial, and QGC via the UDP connection.

Hi, When running lsmod I would expect to see a list of different kernel modules including the 88XXau kernel module which is the driver for that wifi dongle. Luckily we've also included the kernel module in the Voxl2 file system under the path: /lib/modules/4.19.125/kernel/drivers/net/wireless/88XXau.ko I would suggest first trying to load this kernel module using the insert module command: insmod /lib/modules/4.19.125/kernel/drivers/net/wireless/88XXau.ko You should then run ifconfig and see if the wlan0 interface appears, if it does then the module has been successfully loaded and you should now be able to use your wifi dongle. However, I do recommend upgrading your system image by installing our newest 1.3.1-0.8 platform release. This will upgrade your system image to 1.3.1 and install the 0.8 SDK. This can be found on our downloads page. I recommend doing this because for some reason all your kernel modules are missing. I'm not sure what might've caused this, but it might lead to other issues.

@Eric-Katzfey 232. I'm not terribly worried about it. I've worked with their VN-100 series before, which we might go with. A logic shifter should work fine. So maybe we open another UART? Our custom daughter board connects to J3 and J5 so we can get more than 1 UART even though we're currently only using UART7? from the J3.

Hi @ComputerDev , The Microhard Modem Carrier Addon (M0048-1 internally) has a USB hub in it already (USB2514Bi), so I'm wondering if we have something funky going on with chaining... Does this only show up with the second hub attached? Good that you are independently powering as that was my next line of though.

Thanks for your reply! I got it working. Thank you!

It is normal for the CPU to throttle. It cannot run full speed indefinitely without turning down. It is by design and not necessarily a problem unless you need to do more. Any airflow will help though reduce thermal load so you can get more performance out of the system

@Vinny It's all good. They work fine with soldering. It's more of a pain getting the headers off than anything else. We do stuff like that all the time. I've done 6 or 7 of them already.

@Chad-Sweet Hi, I was able to specify front stereo camera using the below command, 'voxl-calibrate-camera stereo_front -s 7x9 -l 0.02' Thank you!

@Mia-Thomas said in VOXL2 Flir Boson Image Type: YUV422 The first width x height bytes of NV21 and NV12 are the 8-bit luminance values (mono). So, you should be able to publish MONO8 pretty easily with a little extra code.

@Chad-Sweet I am also looking for a Voxl2 IO. My project has come to a halt without it.

We resolved offline, but ended up have Zach use an STLink. How to build FW is here: https://docs.modalai.com/voxl2-io-firmware/ And here's an example using STLink (download from ST's site...) BL_FW_FILE="modalai_voxl2_io_bl.bin" BL_FLASH_START_ADDR="0x8000000" APP_FW_FILE="modalai_voxl2io-v2.bin" APP_FLASH_START_ADDR="0x08001000" if ! [ -f "${BL_FW_FILE}" ]; then exit 10 fi if ! [ -f "${APP_FW_FILE}" ]; then exit 11 fi echo "erasing..." sleep 1 STM32_Programmer_CLI -c port=SWD -e all echo "programming bootloader..." sleep 1 STM32_Programmer_CLI -c port=SWD -w "${BL_FW_FILE}" "${BL_FLASH_START_ADDR}" -v echo "programming application..." sleep 1 STM32_Programmer_CLI -c port=SWD -w "${APP_FW_FILE}" "${APP_FLASH_START_ADDR}" -v echo "resetting..." sleep 1 STM32_Programmer_CLI -c port=SWD -hardRst

@tom thanks

@I_Dwyer Great! Sounds like that VOXL had been run through the voxl-modem-configure setup and the others had not. One other thing I would check is see if the voxl-modem service is enabled with systemctl status voxl-modem, if it's enabled on that one and disabled on the others you may want to disable it with systemctl disable voxl-modem as you may see some network inconsistencies between VOXLs otherwise.

This page may be useful as well https://docs.modalai.com/voxl2-rc-configs/

If it's one of our 4G modems, then it will be off J3 (you were close !) https://docs.modalai.com/voxl2-connectors/#j3---legacy-board-to-board-connector-b2b For example, here's an image: https://docs.modalai.com/voxl2-hardware-setup/#4g-cellular-connectivity