Posts made by Moderator

Yes, when MISP is enabled, voxl-camera-server will output a pipe with the suffix _bayer

For IMX412, there should be a pipe named "hires_bayer". That pipe is outputying raw bayer data directly from the sensor

For color measurement and validation on the IMX412 module we require either:

1. Direct RAW image output, or

2. An ISP fixed configuration (with all automatic/adaptive functions disabled).

Could you please confirm whether RAW output is available?

VOXL 2 is a Linux computer, so if you want to write software to coordinate multiple UAS you have open access to do so

For Flir support, you can start here: https://docs.modalai.com/M0153/

For flight I/O, you can refer here: https://docs.modalai.com/voxl2-connectors/

For software support, you can refer here: https://docs.modalai.com/voxl-sdk/

Good morning, I have three Starling 2 Max's with your VOXL Cellular LTE and USB hub add-on. I am struggling to find a sim card / data provider that is reliable. While I could connect with a sim card from Hologram, their network prioritization was not ideal and dropped too often for reliable MAVLINK based control. I have sense tried Mint, and AT&T data cards which never would connect. I am hoping to skip the guess work and inquire to if you have a list of known good sim card providers and plans.

For Mint Mobile, I have tried "wholesale" and a few others for the APN. Can you pass what configuration you used?

Sorry you are running into issues

Can you help with some more information?

• What motor are you using with the M0129 ESC?
• What battery cell count are you using?
• Have you performed the ESC calibration?
• Can you share the ESC params you are using?
• Can you share a video of the issue?

@Idan-Fiksel Is the calibration card mounted to a hard backing piece so there are no warps or wrinkles in the checkerboard?

Did you print with a PDF so that the checkerboard measurements are accurate?

@Breanne-Crockett yes, the depth sensor is pointed straight forward

We do not have support for Realsense

@lohithvamsi it is probably easiest to return

Please reach out at https://modalai.com/contact and reference this post.

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.