Little more detail, we've validated with FrSky X8R reciever and Taranis X7 transmitter with the following setup:

3c237719-e867-4ed7-908c-cb2db6cef7d1-image.png

We have a new cable about to come out to assist with this wiring as well:
https://docs.modalai.com/cable-datasheets/#mcbl-00018

That aligns with what we have posted on the datasheet here

@Chad-Sweet hi. i am reading mavros document now. Thank for your guide.

@Vũ-Văn-Long wow amazing goodjob

@Chad-Sweet oh my godness. My mistaken, i didn't realise that before that i had configured UAV off board mode. when I check the /etc/modalai/voxl-vision-px4.conf the offboard_mode ="figure_eight" => so that's why it's cause the problem here. anyway, it's work again, thank you so much for the effective support

Hi @Kaiba-Kun ,

Hmm, we normally use voxl-configure-vision-px4 when setting up the vehicle.

For the m500, we have a -f option which will set it to factory state with respect to voxl-vision-px4, so voxl-configure-vision-px4 -f

The camera configs in the ENV variables should be fine after this.

I'd try that option above, if you've configured your GCS IP address in the config file needs to be updated, eg.

vi /etc/modalai/voxl-vision-px4.conf and setup your GCS IP after running with the -f flag.

After that, I'd then reboot the system, and then do a 'hand flight' validation, where you can pick the vehicle up and move around, validating local position NED in QGC.

Here's a video where I do this: https://youtu.be/gTuSaHLCz8w?t=571

voxl-i2c should be pretty straightforward. Just send the i2c commands and get the data. The VOXL platform has a large amount of flexibility and expandability, you should be able to do what you need with a few i2c commands.

Edit: reverting to original driver returns the functionality to default (upside down feed)

Yes, after adding some foam, The UAV now are stable than a bit. Do you think the battery should be problem? Our 3S battery are quite old.

Hi @vmassague ,

We currently can add the R-XSR or X8R, if you purchase just let us know (you can even post here) what flavor you would want installed.

Our Shopify page needs some work to allow product customization... until then we might need to have some back and forth to get the customizations you want.

Thanks!
Travis

If you're interested in Python and MAV SDK, you should start here: http://docs.modalai.com/mavsdk

I reran the calibration outdoors with gps signal and far from any metal. I also raised the drone to be ~3-4' from the metal turntable below it. This improved the calibration quite a bit and the drone is not drifting as much as before. However, there still seems to be more drift in the VIO than there was when I first received the drone. I still don't have the PWM_MIN parameter that the docs say I should check for the assure the PX4 parameters loaded properly. I see that this parameter is in the custom2.params file, but the note in the document says it turns off the gps.

Can you please explain the steps you go through during your calibration process? Should I also be loading this custom2.params file? If so, does that mean that gps is not used when in VIO (no sensor fusion etc)?

Got the problem sorted out.

%YAML:1.0 M: !!opencv-matrix rows: 3 cols: 3 dt: d data: [ 2.7874039916528164e+02, 0., 3.3988271378331154e+02, 0., 2.7880227185614154e+02, 2.5258101356853410e+02, 0., 0., 1. ] D: !!opencv-matrix rows: 4 cols: 1 dt: d data: [ -1.4185703635329491e-02, 2.1172901376532889e-02, -1.4431453715214168e-02, 3.4931558175981398e-03 ] width: 640. height: 480. distortion_model: fisheye

Cheers

Hi Prasanth, you should be able to find how to connect to ESCs, GPS, and other peripherals here: https://docs.modalai.com/flight-core-connections/

That page is relevant for both Flight Core independently and integrated with VOXL on VOXL Flight

SDIO Card Specification version 3.0, 4-bit, up to 2TB 🙂

You can see an example of how to write telemetry on top of a video frame here
https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-qvio-server/-/blob/master/server/main.cpp#L715

In the parameters list, check for "dshot_config". Our most recent M500's use dshot 600.

Thanks Matt, that did the trick 👌