vehicle did not respond to command: MAV_CMD_DO_MOTOR_TEST

[suvasis]

I connected the qgroundcontrol. I see the parameters set correctly. However, when doing motor testing I see the message pops up:

vehicle did not respond to command: MAV_CMD_DO_MOTOR_TEST

How do I resolve this?

Thanks.
suvasis

[Eric Katzfey]

@suvasis Can you explain a little bit about the products you are using? Is this on Flight Core or on VOXL2?

[suvasis]

I bought calibrated voxl2 and 4-in-1 esc separately and attached to my own holybro drone. I wired up the esc and voxl2.

1. All the motor testing works fine as the result shows below:

2. after the test,
   #when done, restore original libpx4.so
   cd /usr/lib/rfsa/adsp
   rm libpx4.so
   cp libpx4.so.bak libpx4.so
   systemctl enable voxl-px4
   reboot

I started the QGC, i see the sensor details etc. Here i click on the motors on the left side of QGC, then I start motors one by one. after a min or so i see "vehicle did not respond to command: MAV_CMD_DO_MOTOR_TEST" this message and motor never works this way.

Is there more settings required here as per, modalai documentation doesn't point to this though https://docs.qgroundcontrol.com/master/en/SettingsView/General.html?

Or there any missing information? The modalai documentation is not clear at this stage, https://docs.modalai.com/voxl2-px4-quickstart/.

motor testing Test results:

Installation Instructions for VOXL2

#stop and disable PX4 while using voxl-esc tools
systemctl stop voxl-px4 && systemctl disable voxl-px4

#temporarily move libpx4.so and create symlink for slpi bridge to libpx4.so
#this is required because currently the slpi application loader looks for libpx4.so (hardcoded)
cd /usr/lib/rfsa/adsp
mv libpx4.so libpx4.so.bak
ln -s ./libslpi_uart_bridge_slpi.so ./libpx4.so

#reboot VOXL2
reboot

Looks now it works after I re-did the steps:

result:

voxl2:~$
voxl2:~$ cd /usr/lib/rfsa/adsp
voxl2:/usr/lib/rfsa/adsp$ ls -l libpx4.so
lrwxrwxrwx 1 root root 29 Mar 16 17:41 libpx4.so -> ./libslpi_uart_bridge_slpi.so
voxl2:/usr/lib/rfsa/adsp$ cd
voxl2:~$ pwd
/home/root
voxl2:~$ cd voxl-esc/tools/
voxl2:~/voxl-esc/tools(dev-python3)$ ./voxl-esc-scan.py
Detected Python version : 3.6.9 (default, Jun 29 2022, 11:45:57)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.1
VOXL Platform: M0054
Detected VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 250000
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 250000
INFO: Detected protocol: firmware
INFO: Additional Information:
INFO: ---------------------
ID : 0
Board : version 34: ModalAi 4-in-1 ESC V2 RevC (M0117)
UID : 0x203034305743570C00360052
Firmware : version 36, hash f75f1fdb
Bootloader : version 183, hash 25317f42

ID : 1
Board : version 34: ModalAi 4-in-1 ESC V2 RevC (M0117)
UID : 0x203034305743570C0036004C
Firmware : version 36, hash f75f1fdb
Bootloader : version 183, hash 25317f42

ID : 2
Board : version 34: ModalAi 4-in-1 ESC V2 RevC (M0117)
UID : 0x203034305743570C0036004B
Firmware : version 36, hash f75f1fdb
Bootloader : version 183, hash 25317f42

ID : 3
Board : version 34: ModalAi 4-in-1 ESC V2 RevC (M0117)
UID : 0x203034305743570C0042001C
Firmware : version 36, hash f75f1fdb
Bootloader : version 183, hash 25317f42

[suvasis]

hi Eric,

Is there any update on the issue?
Thanks.
suvasis

[Eric Katzfey]

@suvasis Unfortunately, motor testing using the QGC motors tab is not supported on VOXL2.