Extensive Problems with RB5 Drones

[alfa budiman]

M2100000CTT
powers on
detected by usb
connects to wifi and Q Ground Control
Cannot Arm - "system power unavailable"

M2100000CU7
powers on
not detected by usb*

M2100000CTU
powers on
not detected by usb*

M2100000CTV
does not power on anymore**

**Drone M2100000CTV used to work it stopped working after testing what would happen if connectivity were to shut off.
To test this, I had the drone (with propellers off) powered by an external power supply with it and a computer connected on the
same wifi network. I armed the drone from QGround control and used virtual joystick to throttle it. It responded as expected. With the throttle up, I turned off the wifi. The motors stopped spinning, I disconnected hte drone from the pwoer supply and re-connected it to the power. At this moment the drone doesn't power up anymore.

*Between CU7 and CTU, one of them was working fine, I was able to connect it to the computer and it was detected. I was able to setup wifi connectivity and even arm it through Q Ground Control. However, it stopped connecting to wifi and stopped being detected by usb (but still powers on). The other one was never detected by usb. I forget which one does which

[Chad Sweet]

I am sorry to hear you're having issues.

An external power supply should definitely not be used to test the vehicle with motors. An external power supply can only be used for booting the computing portion for software development.

It is designed to only power the motors with a battery. It is very difficult to know what could have happened. We do have an RMA process where we could diagnose any damage. It seems likely at least of of the drones has a power system failure.

Hopefully the sudden power offs just "bricked" the computing device? You can try the fastboot recovery found here: https://docs.modalai.com/Qualcomm-Flight-RB5-system-image/

[alfa budiman]

Thanks.

CTV, CTU and CTT*:
detected by usb, connects to wifi / Q Ground control and can be armed / throttled. For some reason these just worked after I pushed the button and powered them on, didn't have to go through the full-flash process.
*For CTT it was a Q Ground Control related issue. I saved the parameter file from CTV and loaded it onto CTT.

CU7:
non-responsive to flash-full process:

[INFO] version: 0.0
[INFO] adb installed
[INFO] fastboot installed
[INFO] qti-ubuntu-robotics-image-qrb5165-rb5-boot.img present
[INFO] abl.elf present
[INFO] qti-ubuntu-robotics-image-qrb5165-rb5-sysfs.ext4 present
[ERROR] Device in fastboot mode.  Unable to backup camera files.
[INFO] Please bring device out of fastboot mode by first running:
          fastboot reboot

I then enter fastboot reboot and try sudo ./flash-full.sh again. It gets stuck at

[INFO] version: 0.0
[INFO] adb installed
[INFO] fastboot installed
[INFO] qti-ubuntu-robotics-image-qrb5165-rb5-boot.img present
[INFO] abl.elf present
[INFO] qti-ubuntu-robotics-image-qrb5165-rb5-sysfs.ext4 present
[INFO] Saving camera calibration files

and is no longer detected by usb. However, when I push the button again, it does appear on lsub and fastboot devices.

c9ce2d0d	fastboot