@Alex-Kushleyev

• I updated the correct kV and uploaded the params to the ESC.
• I increased the spin-up time from 0.5s to 1s; and spin-up power from 90 to 110 and then to 120. There was a bit of improvement but still the motor spins very intermittently. Previously, it would just barely move and stop.
• I swapped motors on ESC channel 1 (good channel) and ESC channel 2 (bad channel). So the motor working nicely on channel 1 stopped working when moved to channel 2. And the motor that was not working on channel 2, worked fine when moved to channel 1. So it is definitely not the motor (or short in winding).
• We have made sure the ESC is free of any debris and not touching anything.

Is there a good way to share video? I can share a folder with you if you give me an email pls.

Thanks.
Regards.

@Alex-Kushleyev

I tried spinning the motor (ESC ch. 2) with a fresh battery at 10% power. Now it shows 16V but still the same behavior.

I tried recalibrating, but it doesn't spin properly during calibration. Also, the end parameters are way off than the original ones (which are the same on the other 3 motors).

@Alex-Kushleyev the tests were done all in succession with the same 4S (16V) battery. We are using Xing2 2205 2300kv motors with 5 inch props.

I followed the ESC calibration guide: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md

I started with this parameter file: lumenier_2305_2400kv_GF_D90_4S.xml and modified it as follows:
param name="vbat_nominal_mv" value="15200"
param name="num_cycles_per_rev" value="7"
param name="min_rpm" value="3200"
param name="max_rpm" value="25000"

Then I uploaded these, and did the calibration. I got good results initially, and all motors were spinning up fine.
param name="pwm_vs_rpm_curve_a0" value="29.00369359"
param name="pwm_vs_rpm_curve_a1" value="0.414700099"
param name="pwm_vs_rpm_curve_a2" value="3.58E-06"

Nothing else was changed in the parameter file, and it was uploaded to the ESC.

But while the drone was on bench, after 2 or 3 times of running, the motor on ESC channel 2 stopped spinning. I tried re-calibrating but now even during the calibration that ESC channel does not spin up the motor.

Hi,

I have the VOXL FPV ESC and I cannot spin/ calibrate one of the motors. 3 motors spin calibrate fine but one motor spins very intermittently. I tried replacing that motor but same behavior.

Screenshot of the ESC detection:

Good motor spin:

Bad motor spin:

I think it is a bad ESC, but need your guidance if this can be fixed. The output when running this motor is different: it shows extra BOARD_VOLTAGE, and BOARD_CURRENT fields when spinning. Also it knows the RPM keeps going to zero.

Hi,

I am attaching a VOXL io expander board to the stinger drone instead of the ELRS, and started the px4 voxl-io driver using

qshell voxl2_io start -p 7 #(use QUP7)

I can use the actuator tab in QGC to control the PWM outputs, but there are limited options for the PWM channel "function" assignment. This limits my ability to control that channel with mavlink commands.

I am thinking of using the voxl-io-server to control pwm outputs using mavlink commands. But I am not sure how the voxl-io-server works? Can you share some insight into how voxl-io-server runs with voxl-px4 and the voxl-io driver inside?

Thanks.

@Eric-Katzfey thank you for pointing me to that. It is really helpful!

Two more questions:
1- is there a way to know the git commit for the voxl-px4 on the drone at the moment?
2- how lights are operated on the stinger? is there a direct passthrough from RC to the outputs (P0,P1,P2,P3) on the ELRS receiver? If not, where in the voxl-px4 code does the Lights pwm get assigned pls?

Thanks for your support!

@Eric-Katzfey I tried that parameter, but I did was not able to get the motors to spin in turtle mode.
I tried searching the voxl-px4 repo and could not find how that parameter is used. Do you mind sharing some insight on how the joystick button will trigger turtle mode?
Just to highlight that I am not using a VTX but doodlelabs radio to connect to a handheld gcs/joystick.

Hi.

We have the stinger drone and would like to fly it using the UXV SRoC controller (joystick). We have done the following modifications:

• removed the VTX and plugged in a doodlelabs radio in its place.
• removed the ELRS receiver and plugged in the VOXL IO expander board (to get PWM for the IR/visual lights).
• Connected the Lights signal wire to the IO expander.
• In software, we:
  a. stopped the vtx service, and configured the doodlelabs radio
  b. configured the voxl-streamer to stream the fpv camera
  b. in px4 config file, set RC = EXTERNAL (to support joystick)
  c. in px4 start, set "qshell voxl2_io start -p 7 #(use QUP7)" to start voxl io on that port
• We get telemetry and video on QGC. In the "Actuators" tab, we are able to control the motors and the lights.
• We get mode switch and arming to work by mapping actions to buttons for joystick.

Where we got stuck is using joystick to control the Lights, turtle mode, and camera switching. Can you pls suggest how we can control these functionality with joystick? I see that the voxl-px4 service is using an older px4 firmware that publishes a basic manual_control_setpoint message when "manual_control" messages are received from the gcs.

Hello.

We at Qubotics are building a live video streamer product for robotic applications, and would like to use the following in our product:

Modal AI Voxl 2 as the main processing unit,
IMX412 camera,
optionally Flir hadron camera boards,
optionally voxl 2 cellular LTE, and,
voxl latest suite of software.
We will be incorporating some of our own hardware in the product and software built on top of voxl's. I just wanted to understand what steps need to be taken in order to make this product. We really like the VOXL2 since it is the lightest QRB5165 based computer, and would love to use it in our products.

Thank you for your support and guidance.

Hello.

We at Qubotics are building a live video streamer product for robotic applications, and would like to use the following in our product:

• Modal AI Voxl 2 as the main processing unit,
• IMX412 camera,
• optionally Flir hadron camera boards,
• optionally voxl 2 cellular LTE, and,
• voxl latest suite of software.

We will be incorporating some of our own hardware in the product and software built on top of voxl's. I just wanted to understand what steps need to be taken in order to make this product. We really like the VOXL2 since it is the lightest QRB5165 based computer, and would love to use it in our products.

Thank you for your support and guidance.