Posts made by TPSetati

We'll have to take a look on our side then. Could we receive the schematics of the board and perhaps the source code for the qualcomm so we can test?

We flew the drone and had a semi-hard landing (I say semi-hard because we've had harder landings but the drone got back to flying easily). When we went in to check the drone, nothing was physically damaged. We just noticed that the WiFi was off.

We thought cycling the power would work, as it usually did, but this was not the case now. When trying to connect via ADB and noticed it didn't work, that's when we knew something was wrong.

We tried fastbooting the board, and that also was not working. So we realized that this problem is deeper than just a bricked board.

The add-on board we have connected is the WiFi board with its Fastboot button. The only SW2 I have spotted is the one depicted on https://docs.modalai.com/voxl2-qdl/.

Before the system image got corrupted, everything worked fine and no buttons or switches were engaged. I am finding it weird that it seems that the board went into EDL mode upon corruption with no changes made to the hardware.

Our setup is similar to that on https://docs.modalai.com/voxl2-d0006/. All of this is on a Sentinel drone.

@TPSetati I am just realizing that the VOXL2 board was already in QDL mode before I switched SW2 to the ON position. Even if I switch it back to off, it remains in QDL mode. Is there another switch that could be causing this?

I ran thesudo apt remove --purge modemmanager command to uninstall it, but there was nothing to uninstall according to the output

When the board is disconnected, the qdl command can detect that nothing is connected

Good day

Thank you for your response and for showing me another solution to try. I am trying the QDL route, but have hit a speed bump.

SW2 has been switched to on and the host PC recognizes that the VOXL2 is in QDL mode

I downloaded the system image on the QDL page and unzipped it. When running the sudo qdl command, nothing happens.

What could the issue be here?

Apologies, I realized the error on my part. Here is the correct output

Re: VOXL2 bricked

Good day

I am facing the bricked VOXL2 issue and forcing fastboot is not working.
After following the instruction to force a fastboot, I connect the USB cable to the host PC. Running dmesg -wH shows:

lsusb also confirms the Qualcomm device is connected

Unfortunately fastboot devices still gives no output

It seems that the variable "external_fc" in voxl-mavlink-server.conf kept resetting to true, when it should remain false.

I'll try them out. Thank you.

No, I have not. How do I reach out?

Good day

I am currently having a problem receiving messages from px4 via MAVLINK on my VOXL2 board. I think this started after we tried flying autonomously and there was an FCU: Vision Failure error after takeoff. From there we could not connect to QGC regardless of how many times we ran and restarted the MAVLINK server and voxl-vision-px4.

Running voxl-vision-px4 --debug_udp_recv gives:

I mean the RAM on the host PC running QGC. I can't have QGC open for more than 5 minutes without the machine freezing up.

I am using the drone in softAP mode and connecting to its WiFi.

I have a 3 cell battery. I just looked at the vehicle settings in QGC and I see that the battery settings were set to the 4 cells. I changed it accordingly and the battery percentage now reads an acceptible 94%.

Thank you.

I thought this screenshot would give a better indication of the communication issue between the drone and QGC

I have just charged my battery and this is the info from the MAVLINK Inspector Tool

Good day

Does anyone have any idea what the issue here could be? Because the battery % will not show, QGC won't give us any information about the current battery level.

Not long ago, I was running some offboard mode test code to autonomously "fly" the drone with the propellers off. While the code was running, everything just stopped without warning, but the onboard PC and GPS module were still on. Unplugging the replugging the battery revealed that the battery is probably low. If we were flying-flying, this could have been an incident.

Any assistance as to why the drone won't read the battery state and send it to QGC will be appreciated.

voxl-inspect-battery gives