Hi @Arrowtec ,

I've seen this myself before. In my case the device would then show up after running sudo fastboot devices and I could proceed after trying again.

If it's not showing up with either sudo fastboot devices or adb devices it would likely need the Debug board which allows you to force it to boot into fastboot....

The Flight Deck has the two main components (VOXL and FlightCore). They share a 5VDC rail that is fed by the Power Module on the M500.

The FlightCore portion of the board is a little STM32 microprocessor running PX4. PX4 reads that 5VDC from an ADC.

Depending on your toolset, it could be easy to probe that voltage: https://docs.modalai.com/voxl-flight-datasheet-connectors/#j1013---5v-dc-power-input-i2c3-to-power-cable-apm

When you did the manual flight you had no issues?

@James-Strawson got it.

My test s/w version is volx-vision-px4 0.3.4 and has a same problem, am I right?

Okay, I’ll proceed test VOA using 0.2.0 version before releasing new version s/w.

Can I know release date for new version?

Thanks,

@MattO The instructions should be more clear now: https://gitlab.com/voxl-public/other/voxl-python-3.6.9#installing-the-ipk

I assume you are using the master version of voxl-vision-px4.

Since the is_cam_master is false, is voxl-vision-px4 still running? vvpx4 would be the camera master in that case

Can you check what TRACKING_CAM_ID is?

'echo $TRACKING_CAM_ID'

If you have high-res, stereo and tracking plugged in TRACKING_CAM_ID should be 1 which matches what you have in the launch file

@gauravshukla914 ,

I for the first time got the "avionics power low" message! I turned off the ADCs on FlightCore for a test and got this error.

PX4 monitors the 5VDC rail (and 3.3VDC), and this makes sense now, as the output of that power module was lower than expected.

Anyhow, I remembered this post so figured I'd put some details here while I saw it 😉

@FourPointTwoMm I've done this a bunch myself!!

Thanks for the feedback! The documentation has been updated.

@Eric-Katzfey Thank you so much for your answer!

I'm having same issue. Might want to update the documentation.

Hi @abdullah ,

Was the PX4 FW version changed at any point? We have seen some performance issues with PX4 1.11 and the position controller. I see in your logs you have v1.11.2 going.

Is there anyway to load the ModalAI 1.10 FW as a data point and see if the flight performance changes?

https://docs.modalai.com/flight-core-firmware/#px4-v110

Thanks!

gstreamer in a Docker also works

Thanks for this detailed response! This would be good information to put in the technical documentation when searching in google for "modalai flight core connections for magnetometer" there wasn't much information on how to setup a magnetometer with the flight core.

I was able to setup the the RM3100 by using J13.[1,2] for 3.3 VCC and GND and the J10.[4,5] for the I2C protocol. This allowed me to set

in PX4 and successfully calibrate the compass

Hi @modaltb ,

Thank you for your message. Yes, it was the case and I am doing a benchtop development. After changing to 0, they don't beep anymore. So, I can work in peace. :))

@kiprock do you mind if I use your images in our docs?

Hi @James-Strawson,

Thanks for the tip I will try it out!

Good news. We will get that updated to be a little more clear.

thank you !!