@garret I use the Sparkfun CAB-12977 and CAB-17240 for HITL and it works really well.

@Hector-Gutierrez Point a small fan at the VOXL 2 while you have it on your desktop. You need to have air flow. When it is on a drone and flying you get a lot of airflow from the propellers but on the desktop you should have a small fan.

@Jetson-Nano VOXL 2 does not have PWM out. You would need our IO expander board M0065 to bridge between UART and PWM. https://www.modalai.com/products/voxl2-io?variant=40610514206771

Hi @AidanGallagher
That USB2 port Port, J12, on M0062 is not much different than many other expansion board USB ports. It goes through a HUB, and as Tom pointed out, if you use M0130, your setup will simplify.
M00130 is the only USB2 product we have that can power the Doodle directly: https://docs.modalai.com/expansion-design-guide/#usb-expansion-over-j3--j5

I'm not entirely sure either why your M0062 will not work, but I'm thinking it may be something with the grounding and VBUS connection due to the external board you use for power, and it not sharing a ground with the M0062 where the USB comes from. For example, our MCBL-00085-1 handles all that: https://docs.modalai.com/cable-datasheets/#mcbl-00085
Our USB3 debug board does not have a current limiting IC like M0062 has, and will not impact USB operations. However, with M0062, since it goes through the hub, and it has power control, if anything goes wrong with power or ground, the port may be disabled.
I would first try to see if your J12 port works normally, with a thumb drive for example (or I think you did that with a WiFi and were good). Then, if you want to try to share some more ground connections between your M0062 and the external power supply, that could be a good test.

But, we do suggest you change to an M0130 as you will have a much nicer setup long term.
Hope that helps.

@cguzikowski Yes, we have tested Ardupilot with GPS and have customers using Ardupilot with GPS. However, I don't know that anyone has ever tried with an M9N unit so perhaps there is some issue with that. Can you try with one of these: https://store.3dr.com/mini-gps-ublox-max-m10s/?

@Hector-Gutierrez What branch are you trying to build? If you install dependencies from the dev repo then you should also be building the dev branch of voxl-vision-hub

@Avishkar-Seth It's kind of scattered around in the docs. But here is the high level architecture: https://docs.modalai.com/how-to-connect-voxl-to-flight-core/

PX4 cannot run on VOXL, only on VOXL 2. On an m500 it will be running on the separate flight core board.

@berayksl Hi there,

In the VOXL2 file /etc/modalai/vio_cams.conf all the cameras should be listed as a JSON record. the top-level disable attribute of each record can be edited to turn cameras on and off (make front true and the others false for just the front camera).

On calibration, instructions can be found here.

If the camera's physical positions changed from delivered, then you'll need to update the extrinsics.

@berayksl
Hi there,

1. Since you were able to run a limited bench test, having it fly away after a couple movements indicates 3 possibilities:

• extrinsics are incorrect -- either bad imu_apps to cam# values or camera outputs are flipped.
• intrinsics are incorrect (bad camera calibrations)

2. yes you can run without mag enabled. Should work normally if (of course) VIO is running normally.

3. As for PX4 parameters, VIO enabling can be setup applying this param file.

My thinking is the camera extrinsics maybe off or mismatched to the camera ID. If you can only enabling one camera at a time and run the bench/hand test as if like a single camera vio setup, hopefully it will reveal the misconfigured camera (if all then we have an imu issue).