Voxl2 ESC Error

AP123

Hello,

I have a Voxl 2 with SDK 1.0.0. I'm using a ModalAI 4-in-1 ESC (M0134) which i have connected with a MCBL-00029 to the Voxl. When i CD to /usr/share/modalai/voxl-esc-tools and send command voxl-esc and choose option 2 detect i get this:

enabling bridge
detected voxl-px4 is enabled
Removed /etc/systemd/system/multi-user.target.wants/voxl-px4.service.
detected voxl-px4 is running, stopping it now
bridge enabled
Received standard error event 2
\e[91m[ERROR] No ESCs detected\e[0m
disabling bridge
re-enabling voxl-px4
Created symlink /etc/systemd/system/multi-user.target.wants/voxl-px4.service → /etc/systemd/system/voxl-px4.service.
restarting voxl-px4
bridge disabled
EXITING VOXL-ESC WITH ERROR

What am i missing? Is the M0134 compatible or do i have to use M0049 or M0117 only?
I just got the unit brand new last week, do i need to install any drivers?

All help would be much appreciated.

Thank You So Much!

Eric Katzfey

@AP123 What happens when you use ./voxl-esc-scan.py?

AP123

Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.2
VOXL Platform: M0054
Detected VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 250000
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 921600
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 230400
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 57600
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 115200
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 38400
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
Sending library name request: libslpi_uart_bridge_slpi.so
Received standard error event 2
Sending initialization request
Received standard error event 2
Couldn't configure flight_controller sensor
Error calling voxl_uart_init
Updated baud rate to 38400
Segmentation fault

The M0134 lights do not turn on nor do i hear any beeps, is it defective or is this normal?

Eric Katzfey

@AP123 I'm guessing that voxl-px4 is running and the voxl-esc commands are not able to stop it. You can try to do this manually. Run systemctl disable voxl-px4 and then reboot. You should then be able to use the voxl-esc tools. After you are done use systemctl enable voxl-px4 to get voxl-px4 on auto start again.