You might have both qvio and openvins running? That could lead to issues. Only one should be running at a time
have you looked through the troubleshooting guide? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio
Usually looking at the ovins-overlay in voxl-portal offers good insight
The common issues are vibration is too high, the extrinsics are incorrect or there are not enough features to track in the environment
@QSL here is our app note on thermal https://docs.modalai.com/voxl2-thermal-performance/#thermal-performance
@cmall the VOXL 2 IO connects via UART. You could use any breakout board, like an Arduino, to generate PWM
@VictorG have you looked at the instructions here? https://docs.modalai.com/flight-core-v2-usb-to-qgc/
@Daniel-Rincon have you looked through the troubleshooting guide? https://docs.modalai.com/flying-with-vio/#troubleshooting-vio
Usually looking at the ovins-overlay in voxl-portal offers good insight
The common issues are vibration is too high, the extrinsics are incorrect or there are not enough features to track in the environment
The easiest way to connect an IMX412, AR0144 and TOF would be to follow the Starling 2 architecture found here: https://docs.modalai.com/voxl2-d0014/
To just connect the TOF directly to VOXL 2, the M0172 is likely what you are looking for: https://www.modalai.com/products/mdk-m0172-1-00
We need to connect the following: Forward Facing MSU-M0149-1, MSU-M0107, and VOXL 2 Time of Flight (TOF) Depth Sensor
Sensor with Adapter PCB and M0177 Starling Flex (Molex 40-pin) and a second TOF Depth Sensor in the Rear of our platform as well facing downward. We seem to not be able to figure out which connector works from the TOF we have (MSU-M0178-1-01) with any of the connectors or adapter we have purchased. Do we need to instead be using the (MSU-M0169-1-01) TOF sensor and PCB? Or is there a way to buy the connector and PCB separately to use with the ones we have?
I’m setting up a delta-wing platform with the VOXL2 and using the VOXL2 IO board (M0065). I followed the instructions provided here to update the firmware.
However, I couldn’t locate the m0065_firmware.bin file mentioned in the instructions on the public downloads site. Instead, I used the voxl2_io_firmware_m0065_v1_35_58c82813.bin file. I later realized that this firmware is only compatible with VOXL2 SDK v1.1.1, while I’m currently using SDK v1.4.1. I don't see any other firmware file for the m0065.
Could you please advise how I should proceed to reflash the IO board with the correct firmware version compatible with SDK v1.4.1?
I appreciate any guidance you can provide.
@kerct the higher number cores are larger and more powerful, and they generate more heat. So, the kernel is intelligently biased towards keeping the chip from overheating
@cegeyer that does seem suspicious
Here's the code for cpu-monitor https://gitlab.com/voxl-public/voxl-sdk/services/voxl-cpu-monitor/-/blob/master/server/voxl-cpu-monitor.c?ref_type=heads
@Moderator We will ask about QGC configuration of the ESCs.
@will-huang-oksi you should connect to QGC with a WiFi connection. The "U" USB-C port is for ADB, and not QGC
https://docs.modalai.com/qgc-wifi/
ETA: It looks like you're connected to QGC via the network already, so you can ignore the above. That message likely means that you can only perform the calibration via command line. Here are the calibration instructions
There is some risk in extending sensors, see this doc
This is the extension flex for the Panasonic connectors: https://docs.modalai.com/M0036/
This should extend the TOF connection: https://docs.modalai.com/M0178/
the micro-coax sensors (M0161 and M0166) are going to be much easier to mount up front. TOF has no micro-coax implementation though
@george-kollamkulam Here's voxl-logger https://docs.modalai.com/voxl-logger/ which you can use to record data. if you need to access the data real-time, that's a good source code starting point for how to capture the data into your application
@sssagara IBSS is not something we have any experience with. As you see, it is an open source driver. You can also use different wifi adapters
Hadron 640R support is in beta. You can request a custom invoice for the adapter at https://modalai.com/contact
We have no experience with Herelink. The modems we have support for MVX, Doodle Labs, Cellular and Wifi
You cannot use HD Zero to send video from VOXL 2
The software is all open, so if you need to send custom gimbal commands you may need to update the software
VIO cameras need to be fixed mounted with the VOXL 2 and cannot be on a gimbal
@chenzhe that is a Sentinel, you can find the 3D models here: https://docs.modalai.com/sentinel-functional-description/#sentinel-3d-step
@wolde-cosgrove there is a lot of documentation on this topic here: https://docs.modalai.com/voxl-px4/
We plan to make a version available with a thermal camera in the summer of 2025. It may be subject to export controls
Which Microhard units do you recommend for reliable integration with the VOXL m500 (both for the air unit and the ground unit)?
Could you provide a complete wiring map or diagram showing how to physically connect the Microhard modem to the VOXL board, including power supply details and which ports to use?
Do you provide flash files or firmware for the Microhard air and ground units that are configured to work with the m500 out of the box?
Do you provide documentation that explains how to access and configure the Microhard units via their IP interfaces?
Specifically, we’re looking for a step-by-step guide (PDF or otherwise) that shows how to: