Great to hear! Feel free to create a pull request if you would like to get the feature into the mainline so you don't need to maintain a fork.

ADB was not connected. After connecting the fastboot board, it turned out to turn on the device in fastboot mode. After connecting in the fastboot mode manually, using the fastboot command, the disk partitions were flashed, as is done in the install.sh script. Problem solved

Here is our rma page to follow: https://www.modalai.com/pages/rma?_pos=2&_sid=4b1e0e876&_ss=r

@modaltb Interesting, that's good to know they should be identical (what I assumed), that's why I was puzzled when it didn't seem to work. On VOXL Flight we're using port J13 and it's always worked perfectly without issue the first time we're wired up a new unit. I have not tried starting via the command line, but that's a good idea to try. My best guess is a loose connection in the wiring somewhere or a pin not making good contact on the board. If it should be working the most obviously problem is user error on our part or something not making contact properly. We ended up sending them one of our VOXL Flight units where we knew it worked perfectly each time instead of using the Flight Core because they were in a rush to get things working. Thanks for the suggestions!

Those are the specs from the vendor, we don't have any more information, sorry. The intensity image is published in MPA so you could perform a calibration on it to find out more details.

Glad to hear it was a QGC issue - interesting to see that. For the flight core portion of VOXL-Flight: Re-flashing the firmware will bring you back to factory (https://docs.modalai.com/flight-core-firmware/#px4-v111) and after that load parameters from our repo (https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/). That should do it

Thanks @modaltb! I just searched for "voxl-logger" and nothing came up because it's not the name of a project. I will spend some time exploring the repos.

Thanks, Chad!

@Chad-Sweet how many ekf_imu instances would you suggest running on a VOXL-FLIGHT in general, considering a decent workload already on the VOXL -part? cheers

Sorry for the late reply, were you able to fix this? Based on more recent posts maybe reloading the Flight Core Firmware fixed the issue?

Hey, I played around with them today a bit and found yes, your values did reduce the frequency with which the failure occurred so I'll continue tweaking there, thanks a lot. Actually your link was double-helpful since I was looking for those specific parameters that regard the takeoff for quite some time now as well (without success...) ;D I understand this is actually more closely related to PX4 but I very much appreciate the help anyway. I sincerely don't even remember anymore why yesterday I thought this must somehow boil down to the fact that it's running on the VOXL-Flight hehe.

We got it to work by just navigating to the launch file and invoking the roslaunch command from there (and excluding the package name): roslaunch voxl_mpa_to_ros.launch. Thanks, @Alex-Gardner!

We test all of our PCBs thoroughly before they are shipped. We do ship the PCBs bare though, which means they are susceptible to ESD and other damage. We really can't warranty against how different people may handle the PCBs. We publish handling instructions that are also shipped with the PCBs, found here An issue many run into with Flight Core is that they plug USB into the Spektrum port and fry the board. The RMA diagnostic process is for ModalAI technicians to spend time looking into the root cause of the failure, and then provide analysis on what to do next.

Hi Parisa, A number of the gnu standard tools are defined explicitly to our architecture on voxl: arm-oemllib32-linux-gnueabi. If you tab out that (or just tab out "arm") you'll see a number of the standard tools like gcc, gdb, ld, objdump, etc. To run gdb on voxl would thus be arm-oemllib32-linux-gnueabi-gdb

Thank your for your reply. The command is pip3 install opencv-contrib-python-headless (=title of the question). Ubuntu docker is a good but not enough . I need this (opencv python package) on the target board, again like supported by modalai's python numpy package. Please help me to create/ download/install this python package on a voxl board. I need it for later using as ROS node (written in python)

Your video points to a bad camera configuration. The tracking camera cannot produce the resolution that VLC is receiving.

If there are not a lot of file operations, it is pretty rare. It can happen during development as folks are making changes on the board and then pulling power. Linux has a setting for how often the flash is committed to reduce the risk, but of course there could be different side effects. You can see a writeup on the topic here, as it is common in all of this type of single board computers Your smartphone fixes this by making you press the poweroff button before shutting off power.

The Qualcomm Flight RB5 5G is our flagship 5G product at the moment. We do expect VOXL to support 5G directly by the end of CY '21 with a new add-on.

@Adarsh96 Hey there, reading your issue reminded me of something I once experienced. EKF not initializing position is a separate issue but I can tell you if you're able to arm the quad amd have the motors spinning, it should be good. What flightmode did you arm it in? Because with some you need to raise throttle above 60% to takeoff. Just a thought but you might have just been in the wrong mode bc quad arming means you're basically ready to fly.

Yes, I realized I forgot to load the correct .params file before starting calibration. After selecting the one that disables gps and mag I had success. Thank you