Posts made by JP Drone

I would like to request a feature that allows taking photos and videos using an RC switch on VOXL 2 Mini.

We’ve investigated how to trigger photo/video capture by sending MAV_CMD_IMAGE_START_CAPTURE (or MAV_CMD_VIDEO_START_CAPTURE) from PX4-firmware when an RC switch is toggled. However, it seems that mavlink-camera-manager (voxl-mavcam-manager) currently only processes commands coming from GCS, and does not handle commands that originate from the PX4 autopilot.

Environment:
VOXL 2 Mini (SDK 1.3.5)
px4-firmware side with #define ATL_MANTIS_RC_INPUT_HACKS enabled to use photo_switch and video_switch.
Confirmed that MAV_CMD_IMAGE_START_CAPTURE is indeed being sent by PX4 upon toggling the RC switch.
From our investigation, mavlink-camera-manager/src/qgc.c only handles messages from FROM_GCS_PIPE_NAME ("mavlink_from_gcs"). As a result, any capture commands (MAV_CMD_*_CAPTURE) sent by the PX4 autopilot via an RC switch are not recognized, so photos or videos are never saved.

Having the ability to start/stop captures via a user’s RC switch instead of exclusively through a GCS would be extremely helpful. We would greatly appreciate it if mavlink-camera-manager could also accept and handle MAV_CMD_*_CAPTURE commands from PX4 (or if there is an alternative way to accomplish this, we’d be interested in hearing about it).

Thank you for your time and consideration. We look forward to any updates or guidance you can provide on this topic.

I am trying to access VOXL Portal from my smartphone(iPhone) to display the camera feed.
However, even when I select an individual camera from the menu, it does not display.
Additionally, the snapshot capture feature is not functioning, which is also an issue.

When I select Multi-View, the camera display does work, but since I cannot take snapshots, it does not meet my intended use case.

Could this issue be due to a bug?

One more question: Is there any plan to implement a video recording feature in Portal in the future?

@Eric-Katzfey
Thank you for your quick update.
I was able to confirm that it is functioning properly.
Really appreciate your support. Wishing you a wonderful New Year!

@Eric-Katzfey
I think the messages of OSD_STATUS_ROW appear on both, OSD_STATUS and OSD_FM.
Problem seems the message is appear to OSD_FM_ROW when OSD_STATUS_ROW is enabled.

@Eric-Katzfey

Here is the OSD params

1	1	OSD_BAND	5	6
1	1	OSD_BATT_COL	44	6
1	1	OSD_BATT_ROW	17	6
1	1	OSD_CBATT_COL	44	6
1	1	OSD_CBATT_ROW	16	6
1	1	OSD_CHANNEL	1	6
1	1	OSD_CH_COL	-1	6
1	1	OSD_CH_HEIGHT	0	6
1	1	OSD_CH_ROW	-1	6
1	1	OSD_CURR_COL	-1	6
1	1	OSD_CURR_ROW	-1	6
1	1	OSD_DIS_COL	1	6
1	1	OSD_DIS_ROW	11	6
1	1	OSD_DWELL_TIME	500	6
1	1	OSD_FM_COL	1	6
1	1	OSD_FM_ROW	9	6
1	1	OSD_HDG_COL	21	6
1	1	OSD_HDG_ROW	0	6
1	1	OSD_HOME_COL	-1	6
1	1	OSD_HOME_ROW	-1	6
1	1	OSD_LAT_COL	-1	6
1	1	OSD_LAT_ROW	-1	6
1	1	OSD_LOG_LEVEL	3	6
1	1	OSD_LONG_COL	-1	6
1	1	OSD_LONG_ROW	-1	6
1	1	OSD_REMOTE	0	6
1	1	OSD_RSSI_COL	-1	6
1	1	OSD_RSSI_ROW	-1	6
1	1	OSD_SCROLL_RATE	125	6
1	1	OSD_STATUS_COL	1	6
1	1	OSD_STATUS_ROW	17	6
1	1	OSD_SYMBOLS	16383	6
1	1	OSD_VIO_COL	38	6
1	1	OSD_VIO_ROW	0	6

Thank you for the advice.
Both messages are disappeared when I set OSD_STATUS_ROW to -1

Also it was working as expected when I try it from the J10 port

@Eric-Katzfey Thank you for your support and the updated package.

I have successfully verified that the OSD works using J19 pins for UART communication. The msp_dp_osd program is displaying the OSD as expected.

However, I noticed an issue where a STATUS message or similar text is displayed in two locations. One appears correctly in the lower-left corner, as configured, but another is also visible near the center-left of the screen (please see the attached image).

Could you confirm if this behavior is expected?

Current configurations:
OSD_DIS_COL 1
OSD_DIS_ROW 11
OSD_STATUS_COL 1
OSD_STATUS_ROW 17

I would also be happy to handle long error messages.

@Eric-Katzfey Thank you for providing the updated package.
I will test it within the next three days.
I’ll get back to you with the results shortly.

@Eric-Katzfey Thank you for your response.

Yes, that's correct. I don't use GPS for indoor flight, so it's fine to use that UART port on J19 for OSD.

I appreciate your support and look forward to the update.

I am currently working on configuring the OSD program (msp_dp_osd) on VOXL 2 Mini. I have successfully confirmed that the OSD works using Pins 4/5 on J10 (/dev/ttyHS0).

However, Pins 4/5 on J10 (/dev/ttyHS0) are required for other critical purposes, and as a result, I would like to utilize J19 Pins 2/3 (SSC_QUP6) for OSD UART communication.

As these pins are connected to the DSP (SLPI processor), the current OSD implementation cannot access SSC_QUP6 directly because it requires QURT compatibility.

I kindly request that the OSD program be extended for QURT compatibility so it can function over SSC_QUP6 (J19 Pins 2/3). This modification would free up /dev/ttyHS0 for other critical tasks and allow more efficient use of the VOXL 2 Mini's available UART resources.

Thank you for considering this request. I look forward to your response and any guidance on potential workarounds or a timeline for implementing QURT compatibility for the OSD program.

@Alex-Kushleyev
I try reducing the pulse next.

We use ArduPilot with an external flight controller.
It would be nice to use the ESC UART protocol directly from the FC.
Having ArduPilot work on the VOXL 2 mini would be even better.

We are planning to fly only in PWM.
Can PWM based control always be enabled as we want to avoid crashing due to the PWM to be disabled in flight?

if there is any valid packets received by the ESC via UART, the pwm input interface is disabled until the ESC is rebooted. This should not happen unless you are actually communicating with the ESC via UART. This is done to avoid any possible interference between UART-based control and PWM-based control while in flight. UART protocol is still fully functional.

Also, the flight is PWM based control, but I would like to get the ESC telemetry (RPM, voltage and current) via UART.
Could you make it possible?

@Alex-Kushleyev Thank you very much.
I was able to set the parameter for ID 3 from the information you provided.

And, I also confirmed that the motor spins via PWM by motor tests.
However, after the motor test was completed, some motors continued to spin even after the FC set the PWM to 1000.
Some motors will stop rotating once the motor test is complete.
I don't know if this is a parameter issue or an ESC firmware issue.
I modified min_rpm and min_pwm, but did not solve the problem.

<EscParameters>

  <IdParams>
    <param name="id"              value="127"/>  <!-- 0-7 .. 127 means use hardware ID pins to read ID-->
    <param name="dir"             value="2"/>    <!-- 0=fwd, 1=rev, 2=fwd id-based, 3=rev id-based -->
  </IdParams>

  <UartParams>
    <param name="protocol_version" value="2"/>          <!-- reserved for future use -->
    <param name="input_mode"       value="0"/>          <!-- reserved for future use -->
    <param name="baud_rate"        value="2000000"/>     <!-- communication bit rate -->
    <param name="char_timeout_ns"  value="0"/>          <!-- not used -->
    <param name="cmd_timeout_ns"   value="100000000"/>  <!-- timeout for incoming commands before ESC will stop the motor -->
  </UartParams>

  <TuneParams>
    <param name="pwm_frequency"       value="48000"/>  <!-- switching freqency of PWM signal going to motors. 24Khz and 48Khz are only options for now -->
    <param name="vbat_nominal_mv"     value="14800"/>  <!-- used for sanity checking and limiting of voltage-dependent funcions -->
    <param name="num_cycles_per_rev"  value="7"/>      <!-- number of pole pairs in the motor. used for converting electrical frequency to mechanical rpm -->
    <param name="min_rpm"             value="500"/>   <!-- minimum RPM that will be attempted, otherwise capped -->
    <param name="max_rpm"             value="29344"/>  <!-- maximum RPM that will be attempted, otherwise capped -->
    <param name="min_pwm"             value="30"/>     <!-- cap for minimum power to be ever applied. max is 999 -->
    <param name="max_pwm"             value="999"/>    <!-- cap for maximum power to be ever applied. max is 999 -->
    <param name="pwm_vs_rpm_curve_a0" value="0"/>  <!-- this is actually motor_voltage vs rpm curve.. using legacy naming -->
    <param name="pwm_vs_rpm_curve_a1" value="0"/> <!-- Emax RS1306 3300KV with tri-blade 3x3x3 -->
    <param name="pwm_vs_rpm_curve_a2" value="0"/>
    <param name="kp"                  value="250"/>    <!-- RPM controller proportional gain -->
    <param name="ki"                  value="30"/>     <!-- RPM controller proportional gain -->
    <param name="max_kpe"             value="300"/>    <!-- maximum proportional erorr term (max is 999) -->
    <param name="max_kie"             value="100"/>    <!-- maximum integral error term (max is 999) -->
    <param name="max_rpm_delta"       value="0"/>    <!-- cap for maximum rpm error used in RPM controller -->
    
    <param name="spinup_type"         value="1"/>      <!-- 0: traditional, 1: sinusoidal -->
    <param name="spinup_power"        value="70"/>     <!-- power used to during spin-up procedure -->
    <param name="latch_power"         value="70"/>     <!-- power used during latching stage of spin-up (out of 999)-->
    <param name="spinup_power_ramp"   value="8"/>      <!-- it will take ( 4096 / (spinup_power_ramp*10000) ) seconds to ramp sinusoidal start-up power from 0 to spinup_power -->
    <param name="spinup_rpm_target"   value="1000"/>   <!-- Desired RPM at the end of the sinusoidal spin-up procedure -->
    <param name="spinup_time_ms"      value="1000"/>   <!-- Duration of the sinusoidal spin-up procedure -->
    <param name="spinup_bemf_comp"    value="1"/>      <!-- 0: disable, 1:enable back-emf compensation in sinusoidal spin-up procedure -->
    <param name="motor_kv"            value="2850 "/>    <!-- kV value of the motor. used in back-emf compensation during spin-up -->

    <param name="min_num_cross_for_closed_loop" value="50"/>  <!-- exit latching mode of fixed power after this number of zero crossings -->
    <param name="protection_stall_check_rpm" value="1000"/> <!-- if motor spins below this RPM, stall check will trigger and stop / restart the motor -->

    <param name="brake_to_stop"       value="0"/>             <!-- apply brake when stopping motor (or not) -->
    <param name="stall_timeout_ns"    value="20000000"/>      <!-- after spin-up, if no zero crossing is not detected for this amount of time, motor is considered stalled -->
    <param name="require_reset_if_stalled"      value="0"/>   <!-- require sending an array of zero commands to reset before next spin-up, if motor stalled -->

    <param name="tone_freqs"          value="[200, 215, 225, 250, 0,0,0,0, 0,0,0,0]"/> <!-- 200 is 2000Hz, max 255 -->
    <param name="tone_durations"      value="[10,  10,  10,  10,  0,0,0,0, 0,0,0,0]"/> <!-- duration of each tone in units of 10 milli-seconds. Poor naming!!! -->
    <param name="tone_powers"         value="[60,  60,  60,  60,  0,0,0,0, 0,0,0,0]"/> <!-- max is 255 -->

    <param name="dt_threshold_ns"       value="150000"/>      <!-- during start up, ignore inter-commutation times less than this val, probably noise -->
    <param name="max_dt_ns"             value="2500000"/>     <!-- min and max values for time between two commutations. these are used as caps -->
    <param name="min_dt_ns"             value="10000"/>
    <param name="dt_bootstrap_ns"       value="2000000"/>     <!-- filter bootstrap value for commutation dt during start up -->

    <param name="spinup_stall_dt_ns"    value="6000000"/>     <!-- during spin-up, if no zero crossing is not detected for this amount of time, motor is considered stalled -->
    <param name="spinup_stall_check_ns" value="30000000"/>    <!-- time after beginning of spinup to start checking for spinup stall -->

    <param name="alignment_time_ns"     value="0"/>           <!-- alignment time before spin-up -->
    <param name="timing_advance"        value="0"/>
    <param name="sense_advance"         value="0"/>

    <param name="demag_timing"          value="0"/>    <!-- unused -->

  </TuneParams>
</EscParameters>

@Alex-Kushleyev
I updated to the new firmware.
However, ESC ID 3 doesn't work now.

ESC ID 3 is set as the fallback from this message.

WARNING: 57600 baud rate is the fallback baud rate if ESC params are not valid

I then attempted to rewrite the parameter using this command, but it failed.

./voxl-esc-upload-params.py --params-file ../voxl-esc-params/boards/esc_params_generic_m0129_pwm.xml --device /dev/slpi-uart-2 --baud-rate 57600

In light of this situation, could you advise if it's possible to fix the configuration issue with ESC ID 3 for proper functionality?

Logs:

Here is the log of the firmware update, and it's successful.

voxl2-mini:~/voxl-esc/voxl-esc-tools(enable-pwm-input-in-firmware)$ ./voxl-esc-scan.py
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000, protocol: firmware


INFO: ESC Information:
INFO: ---------------------
        ID         : 0
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0036
        Firmware   : version   37, hash a0ca0a86
        Bootloader : version  184, hash 10bf24c8

        ID         : 1
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0032
        Firmware   : version   37, hash a0ca0a86
        Bootloader : version  184, hash 10bf24c8

        ID         : 2
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0034
        Firmware   : version   37, hash a0ca0a86
        Bootloader : version  184, hash 10bf24c8

        ID         : 3
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0038
        Firmware   : version   37, hash a0ca0a86
        Bootloader : version  184, hash 10bf24c8

---------------------




voxl2-mini:~/voxl-esc/voxl-esc-tools(enable-pwm-input-in-firmware)$ ./voxl-esc-upload-firmware-all.sh
Usage:
- Autodetect board and upload latest firmware to all ESCs:
    ./voxl-esc-upload-firmware-all.sh
- Autodetect board and upload latest firmware to a single ESC ID <esc_id>:
    ./voxl-esc-upload-firmware-all.sh <esc_id>

Detecting ESCs...
Received standard error event 2
[INFO] M0129-3 detected
ESC Firmware:  modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
Flashing all ESCs
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6

INFO: Firmware file name : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
INFO: Firmware file size : 23024 bytes


VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000
INFO: ESC(s) detected: [0, 1, 2, 3]
INFO: Sending reset command to ESC ID 0
Updated baud rate to 230400
INFO: Installing firmware to ESC ID 0 : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
        Progress: 100% [##################################################]

INFO: Firmware successfully updated for ESC id 0
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6

INFO: Firmware file name : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
INFO: Firmware file size : 23024 bytes


VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000
INFO: ESC(s) detected: [1, 2, 3]
INFO: Sending reset command to ESC ID 1
Updated baud rate to 230400
INFO: Installing firmware to ESC ID 1 : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
        Progress: 100% [##################################################]

INFO: Firmware successfully updated for ESC id 1
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6

INFO: Firmware file name : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
INFO: Firmware file size : 23024 bytes


VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000
INFO: ESC(s) detected: [2, 3]
INFO: Sending reset command to ESC ID 2
Updated baud rate to 230400
INFO: Installing firmware to ESC ID 2 : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
        Progress: 100% [##################################################]

INFO: Firmware successfully updated for ESC id 2
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6

INFO: Firmware file name : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
INFO: Firmware file size : 23024 bytes


VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000
INFO: ESC(s) detected: [3]
INFO: Sending reset command to ESC ID 3
Updated baud rate to 230400
INFO: Installing firmware to ESC ID 3 : /home/root/voxl-esc/voxl-esc-tools/firmware/modalai_esc_firmware_m0129_3_v0_39_RC13_eef79926.bin
        Progress: 100% [##################################################]

INFO: Firmware successfully updated for ESC id 3

And then I uploaded the parameters. It seems to write IDs 0, 1, and 2, but it fails for ID 3.

voxl2-mini:~/voxl-esc/voxl-esc-tools(enable-pwm-input-in-firmware)$ ./voxl-esc-upload-params.py --params-file ../voxl-esc-params/boards/esc_params_generic_m0129_pwm.xml
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6

INFO: Params file name : ../voxl-esc-params/boards/esc_params_generic_m0129_pwm.xml
INFO: Params file size : 7419 bytes


VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000
INFO: ESCs detected:
INFO: ---------------------
ID: 1, SW: 39, HW: 40: ModalAi 4-in-1 ESC (M0129-3)
ID: 2, SW: 39, HW: 40: ModalAi 4-in-1 ESC (M0129-3)
---------------------
INFO: Loading XML config file...
INFO: Uploading params for ESC ID 255...
-- board config
-- id config
-- uart config
-- tune config
    DONE
INFO: Resetting ESCs...
    DONE
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 250000
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
ERROR: No ESC(s) detected
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 921600
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
ERROR: No ESC(s) detected
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 230400
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
ERROR: No ESC(s) detected
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 57600
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 57600
INFO: ESCs detected:
INFO: ---------------------
ID: 0, SW: 39, HW: 40: ModalAi 4-in-1 ESC (M0129-3)
---------------------
INFO: Loading XML config file...
INFO: Uploading params for ESC ID 255...
-- board config
-- id config
-- uart config
-- tune config
    DONE
INFO: Resetting ESCs...
    DONE
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 115200
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
ERROR:   voxl_uart_read_bytes: Bus '12' is not initialized
Updated baud rate to 230400
ERROR: No ESC(s) detected

Scan command says ID 3 is fallback mode.

voxl2-mini:/$ voxl-esc
Starting Wizard

What do you want to do?
1) scan              3) spin              5) upload_params
2) detect            4) upgrade_firmware
#? 1
enabling bridge
bridge enabled
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000, protocol: firmware


INFO: ESC Information:
INFO: ---------------------
        ID         : 0
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0036
        Firmware   : version   39, hash eef79926
        Bootloader : version  184, hash 10bf24c8

        ID         : 1
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0032
        Firmware   : version   39, hash eef79926
        Bootloader : version  184, hash 10bf24c8

        ID         : 2
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0034
        Firmware   : version   39, hash eef79926
        Bootloader : version  184, hash 10bf24c8

---------------------
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 250000
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 921600
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
ERROR:   voxl_uart_read_bytes: Bus '12' is not initialized
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 57600
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 57600, protocol: firmware


INFO: ESC Information:
INFO: ---------------------
        ID         : 3
        Board      : version 40: ModalAi 4-in-1 ESC (M0129-3)
        UID        : 0x2039333557555304003D0038
        Firmware   : version   39, hash eef79926
        Bootloader : version  184, hash 10bf24c8

---------------------

WARNING: 57600 baud rate is the fallback baud rate if ESC params are not valid
WARNING: Please verify params using voxl-esc-verify-params.py
WARNING: Motors will not spin unless valid params are present
---------------------

Found ESCs:
id: 0, port: /dev/slpi-uart-2, baud rate: 2000000
id: 1, port: /dev/slpi-uart-2, baud rate: 2000000
id: 2, port: /dev/slpi-uart-2, baud rate: 2000000
id: 3, port: /dev/slpi-uart-2, baud rate: 57600
successfully pinged ESCs
disabling bridge
bridge disabled
DONE

./voxl-esc-upload-params.py --params-file ../voxl-esc-params/boards/esc_params_generic_m0129_pwm.xml --device /dev/slpi-uart-2 --baud-rate 57600

esc_params_generic_m0129_pwm.xml

<EscParameters>

  <IdParams>
    <param name="id"              value="127"/>  <!-- 0-7 .. 127 means use hardware ID pins to read ID-->
    <param name="dir"             value="2"/>    <!-- 0=fwd, 1=rev, 2=fwd id-based, 3=rev id-based -->
  </IdParams>

  <UartParams>
    <param name="protocol_version" value="2"/>          <!-- reserved for future use -->
    <param name="input_mode"       value="0"/>          <!-- reserved for future use -->
    <param name="baud_rate"        value="2000000"/>     <!-- communication bit rate -->
    <param name="char_timeout_ns"  value="0"/>          <!-- not used -->
    <param name="cmd_timeout_ns"   value="100000000"/>  <!-- timeout for incoming commands before ESC will stop the motor -->
  </UartParams>

  <TuneParams>
    <param name="pwm_frequency"       value="48000"/>  <!-- switching freqency of PWM signal going to motors. 24Khz and 48Khz are only options for now -->
    <param name="vbat_nominal_mv"     value="14800"/>  <!-- used for sanity checking and limiting of voltage-dependent funcions -->
    <param name="num_cycles_per_rev"  value="7"/>      <!-- number of pole pairs in the motor. used for converting electrical frequency to mechanical rpm -->
    <param name="min_rpm"             value="4000"/>   <!-- minimum RPM that will be attempted, otherwise capped -->
    <param name="max_rpm"             value="29344"/>  <!-- maximum RPM that will be attempted, otherwise capped -->
    <param name="min_pwm"             value="70"/>     <!-- cap for minimum power to be ever applied. max is 999 -->
    <param name="max_pwm"             value="999"/>    <!-- cap for maximum power to be ever applied. max is 999 -->
    <param name="pwm_vs_rpm_curve_a0" value="0"/>  <!-- this is actually motor_voltage vs rpm curve.. using legacy naming -->
    <param name="pwm_vs_rpm_curve_a1" value="0"/> <!-- Emax RS1306 3300KV with tri-blade 3x3x3 -->
    <param name="pwm_vs_rpm_curve_a2" value="0"/>
    <param name="kp"                  value="0"/>    <!-- RPM controller proportional gain -->
    <param name="ki"                  value="0"/>     <!-- RPM controller proportional gain -->
    <param name="max_kpe"             value="0"/>    <!-- maximum proportional erorr term (max is 999) -->
    <param name="max_kie"             value="0"/>    <!-- maximum integral error term (max is 999) -->
    <param name="max_rpm_delta"       value="0"/>    <!-- cap for maximum rpm error used in RPM controller -->
    
    <param name="spinup_type"         value="0"/>      <!-- 0: traditional, 1: sinusoidal -->
    <param name="spinup_power"        value="70"/>     <!-- power used to during spin-up procedure -->
    <param name="latch_power"         value="80"/>     <!-- power used during latching stage of spin-up (out of 999)-->
    <param name="spinup_power_ramp"   value="8"/>      <!-- it will take ( 4096 / (spinup_power_ramp*10000) ) seconds to ramp sinusoidal start-up power from 0 to spinup_power -->
    <param name="spinup_rpm_target"   value="1000"/>   <!-- Desired RPM at the end of the sinusoidal spin-up procedure -->
    <param name="spinup_time_ms"      value="1000"/>   <!-- Duration of the sinusoidal spin-up procedure -->
    <param name="spinup_bemf_comp"    value="0"/>      <!-- 0: disable, 1:enable back-emf compensation in sinusoidal spin-up procedure -->
    <param name="motor_kv"            value="2850 "/>    <!-- kV value of the motor. used in back-emf compensation during spin-up -->

    <param name="min_num_cross_for_closed_loop" value="100"/>  <!-- exit latching mode of fixed power after this number of zero crossings -->
    <param name="protection_stall_check_rpm" value="1000"/> <!-- if motor spins below this RPM, stall check will trigger and stop / restart the motor -->

    <param name="brake_to_stop"       value="0"/>             <!-- apply brake when stopping motor (or not) -->
    <param name="stall_timeout_ns"    value="20000000"/>      <!-- after spin-up, if no zero crossing is not detected for this amount of time, motor is considered stalled -->
    <param name="require_reset_if_stalled"      value="0"/>   <!-- require sending an array of zero commands to reset before next spin-up, if motor stalled -->

    <param name="tone_freqs"          value="[200, 215, 225, 250, 0,0,0,0, 0,0,0,0]"/> <!-- 200 is 2000Hz, max 255 -->
    <param name="tone_durations"      value="[10,  10,  10,  10,  0,0,0,0, 0,0,0,0]"/> <!-- duration of each tone in units of 10 milli-seconds. Poor naming!!! -->
    <param name="tone_powers"         value="[60,  60,  60,  60,  0,0,0,0, 0,0,0,0]"/> <!-- max is 255 -->

    <param name="dt_threshold_ns"       value="150000"/>      <!-- during start up, ignore inter-commutation times less than this val, probably noise -->
    <param name="max_dt_ns"             value="2500000"/>     <!-- min and max values for time between two commutations. these are used as caps -->
    <param name="min_dt_ns"             value="10000"/>
    <param name="dt_bootstrap_ns"       value="2000000"/>     <!-- filter bootstrap value for commutation dt during start up -->

    <param name="spinup_stall_dt_ns"    value="6000000"/>     <!-- during spin-up, if no zero crossing is not detected for this amount of time, motor is considered stalled -->
    <param name="spinup_stall_check_ns" value="30000000"/>    <!-- time after beginning of spinup to start checking for spinup stall -->

    <param name="alignment_time_ns"     value="0"/>           <!-- alignment time before spin-up -->
    <param name="timing_advance"        value="0"/>
    <param name="sense_advance"         value="0"/>

    <param name="demag_timing"          value="0"/>    <!-- unused -->

  </TuneParams>
</EscParameters>

@Alex-Kushleyev Thank you! I will check it works.

@Alex-Kushleyev
Thank you for your response. I understand your availability and appreciate your willingness to assist. I'll await your firmware update next Wednesday.

I attempted to upgrade the ESC firmware before, but encountered an error:
ERROR: Bus 12 is already initialized. To reinitialize, please close it first.

Besides enabling bridge (disabling voxl-px4), are there any other services I should stop or additional steps I should take to free up the serial bus before attempting the ESC firmware upgrade?

$ voxl-esc
Starting Wizard

What do you want to do?
1) scan              3) spin              5) upload_params
2) detect            4) upgrade_firmware
#? 4
enabling bridge
bridge enabled
[INFO] Setting CPU to performance mode
[INFO] Scanning for ESC...
Received standard error event 2
[INFO] M0129-3 detected
[INFO] has for most recent firmware: eb6fb500
[INFO] Expected ESC firmware info:
        Firmware: modalai_esc_firmware_m0129_3_v0_39_RC10_eb6fb500.bin
        Firmware hash: eb6fb500

[INFO] Number of ESCs with correct FW: 0

[INFO] 0 of the ESCs do not have the current firmware
[INFO] Uploading current ESC firmware...
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.6

INFO: Firmware file name : firmware/modalai_esc_firmware_m0129_3_v0_39_RC10_eb6fb500.bin
INFO: Firmware file size : 22672 bytes


VOXL Platform: M0104
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Received standard error event 2
Sending initialization request
INFO: ESC(s) detected on port: /dev/slpi-uart-2, baud rate: 2000000
WARNING: Unable to detect ESCs in order to reset them..:
'NoneType' object has no attribute 'get_detected'
WARGING: Attempting to continue
ERROR:   Bus 12 is already initialized. To reinitialize, please close it first.
Updated baud rate to 230400
INFO: Installing firmware to ESC ID 0 : firmware/modalai_esc_firmware_m0129_3_v0_39_RC10_eb6fb500.bin

ERROR: An error occured during the write process.
[ERROR] failed to upload firmware to ESC0
disabling bridge
bridge disabled
EXITING VOXL-ESC WITH ERROR

@Alex-Kushleyev
Thank you for reply.
We understood the circumstances in which RPM control is recommended.
However, I would like to continue testing PWM control as well.

Yes, we are connecting the PWM input to A0 - A3 and try to using with 1-2ms pulse.
Please let me know when it's enabled.

I am in the process of assembling a drone using the VOXL 2 Mini in conjunction with the VOXL Mini 4-in-1 ESC and an external FC. I selected the VOXL Mini 4-in-1 ESC due to its features of PWM control and power output capabilities.

Through the voxl-esc utility, I have successfully executed scan and spin commands, confirming that the motors are operational. However, when attempting to test the motors via PWM signals from the external FC, there is no response.

Could you please guide me on whether there is any additional setup required to enable motor movement via PWM through the VOXL Mini 4-in-1 ESC? Are there specific parameters or configurations that need to be adjusted on the ESC to facilitate this?
I would like to mention that I have not yet performed the ESC calibration. Could the lack of calibration be a factor in the motors not responding to PWM inputs from the external FC?

I'm looking forward to your suggestions and advice to resolve this issue.

@tom I appreciate your attempt to assist.
I have the following devices, and I've confirmed that SDK 1.1.2 works with all except for the VOXL Flight:

• VOXL
• VOXL Flight
• VOXL Flight Deck
• VOXL 2
• VOXL 2 Mini
• VOXL 2 Flight Deck

Could you please advise on an alternative solution or provide any specific steps I should follow for the VOXL Flight to address the issue with the camera server crashing? I'm eager to resolve this problem and would greatly appreciate any further guidance or recommendations you might have.

Thank you once again for your support.

@tom Thank you for your response.
There is no option for 21.
I tried it with v1.8.9 (SDK 1.1.2) and the dev version (74ad3a65) of the voxl-camera-server.

# voxl-configure-cameras 21
Camera Configuration: 21
invalid option
Please provide a camera configuration-id

available camera configurations are as follows:
0  None
1  Tracking + Stereo(OV7251)
2  Tracking Only
3  Hires + Stereo(OV7251) + Tracking
4  Hires + Tracking
5  TOF + Tracking
6  Hires + TOF + Tracking
7  TOF + Stereo(OV7251) + Tracking
8  Hires Only
9  TOF Only
10 Stereo(OV7251) only
11 Tracking + Hires + Dual Stereo(OV7251) Pairs
12 Stereo(OV9782) only
13 Hires + Stereo(OV7251)
14 Stereo(OV9782) + TOF + Tracking

Hello,

I'm currently facing an issue with my VOXL Flight (HiRes+Tracking+ToF) after attempting to upgrade from SDK version 0.9.4 to 1.1.2. After installing SDK 1.1.2 and running voxl-configure-cameras 6 for setup, the voxl-camera-server crashes after running for a few seconds.

Issue Description:

A few seconds after the voxl-camera-server starts, one of the CPU cores maxes out at 100% utilization.
Subsequently, the voxl-camera-server crashes.
After the crash, the CPU utilization drops back from 100%.

Error Messages:

Jan 01 00:00:01 apq8096 voxl-camera-server[2325]: ERROR:   Received Fatal error
of 16 still in use
Jan 01 00:00:05 apq8096 voxl-camera-server[2325]: WARNING: OMX_ErrorPortUnpopul
ated
Jan 01 00:00:06 apq8096 voxl-camera-server[2325]: ------ voxl-camera-server: Ca
mera server exited gracefully

Symptoms:

The voxl-camera-server crashes right after starting.
One CPU core is maxed out at 100% utilization.
Rolling back to SDK version 0.9.4 resolves the issue, indicating that it's unlikely to be a hardware or cable issue.

Troubleshooting Steps:

The setup works fine with Flight Deck (HiRes+Tracking+Stereo) and VOXL (HiRes+Tracking+ToF); the issue only presents with VOXL Flight.
I've tried setups with and without an extension cable, but the problem persists.
Testing with three different VOXL Flight units resulted in the same issue, suggesting it's not a hardware variance.
This issue seems specific to VOXL Flight devices, as it doesn't occur with other configurations. It's unlikely to be a cable issue, so I suspect it might be related to SDK version compatibility or a specific setting required for VOXL Flight with the new SDK.

Has anyone encountered this issue or have any suggestions for a solution? Any information on resolving or circumventing this problem would be greatly appreciated.

Thank you in advance for your assistance.