@Alex-Kushleyev Thanks again!

For the diagram I was referring to the FCv2 side. I attached a screenshot with what I think are the discrepancies highlighted. pin6 is ground and the table shows that, but the diagram shows pin 5 as ground. Apologies if I'm misunderstanding!

M.

@Alex-Kushleyev ,

Thank you! We'll test this out and let you know if there are any issues.

Just as a FYI, I found two issues with the documentation (I'm happy to send/post these elsewhere too).

1. "Configure the Bitrate if needed (#3). For VOXL2, the default is 2000000, for FCv1/v2, use 250000." -> The motors would not spin at all UNLESS I had the bitrate set to 2000000 with my FCv2->VOXL-ESC-Mini. I spent a good couple hours trying to figure out why the motors would not spin with the actuator sliders and decided to try the higher bitrate at a whim and it worked.

2. On this page, I think the diagram is wrong , it shows ground going to the second to last pin (pin 5) on the FCv2 and it should be the last pin (pin 6).

Thanks again!

Martin.

@Alex-Kushleyev ,

Thanks for the response!

We are looking to have always 5.0V as soon as it boots up -- so a permanent setting that is remembered between power cycles/boots. I think the first option, having a ESC config param, works for us.

Thanks!

Martin.

Hello!

I have a FCv2 running px4 1.14 and 2.0.109. The VOXL ESC 4-in-1 mini is connected via J5 on the FCv2.

The FCv2 is powered by a separate step down to 5V from the battery (not the modal power harness). I can power the ESC and the FCv2 separately.

I'm able to control the motors with my RC so I know everything is working. I'm also able to test the motors through the actuators message in QGroundControl.

The problem I have is that when I arm, the motors immediately start spinning.

I think this means I need to do PWM ESC Calibration through QGroundControl, correct? With individual ESC, I think this is the equivalent step where you power them on with the throttle all the way up, they beep, and then you slide the throttle down.

So my question is, what is the proper procedure to do this PWM ESC Calibration (no props) with QGroundControl with the FCv2 and ESC Mini?

I get two error messages from QGC.

The first error: 'calibration failed: battery unavailable'. This happens when:

• The FCv2 powered only via USB and there is no power to the ESC

The second error: 'battery must be disconnected. disconnect the battery and try again'. This happens when:

• if I have power to the FC2 from the battery, USB connected to the FCv2, and NO POWER to the ESC.

I've tried various combinations of powering the FCv2 separate from the ESC - e.g. with the modal power harness (so it is reporting battery voltage) and with my own harness that is providing just 5v (since the ESC is providing the power data to the FCv2).

I've tried various combinations of all this and I get one of the two messages above.

Is there some other way to perform the ESC calibraiton or adjust parameters so I the motors don't spin when I arm?

Thank you!

@Vinny Thank you!

I'm having trouble figuring out the command based off the informatino.

I tried the command with --id 14 --val 1 ... and also --val 0, but neither make the output 5V.

I'm connecting directly to the ESC via a USB to Serial adapter and the command finds the board and is able to send the command.

The board-detect script outputs:

INFO: Scanning for ESC firmware: /dev/ttyUSB0, baud: 2000000
INFO: ESC(s) detected on port: /dev/ttyUSB0, baud rate: 2000000
INFO: Detected protocol: firmware
INFO: Additional Information:
INFO: ---------------------
ESC detected: ModalAi 4-in-1 ESC (M0129-6)
ESC detected: ModalAi 4-in-1 ESC (M0129-6)
ESC detected: ModalAi 4-in-1 ESC (M0129-6)
ESC detected: ModalAi 4-in-1 ESC (M0129-6)

Thanks again!

M.

Hello! The datasheet says the Aux power output: "3.3V or 5.0V @ 500mA (default 3.3V, SW-controlled)"

I'd like to change it from 3.3V to 5.0V. I checked the m0129 params here, but I didn't see a setting for it. Does it require a different firmware? How can I change it?

Appologies if I missed something in the documents on how to change it.

Thank you!

Martin.

When you all are testing, can you also confirm that the two USB wires are not swapped. Thanks!

I just tested my cable and it is the same issue that caused mine to melt. I sent my board for RMA so I'll respond to that email thread.

FYI it is possible to pull the pins out and swap them, but it weakens the little plastic retaining piece so it is not as solid anymore ... and it makes it confusing since the red is now ground.

I've had almost the exact same thing happen but I think ours got hot enough to desolder a part (see pictures). Feels like a manufacturing issue. Is there a way to send it in for an RMA/replacement/etc?

Here is more info:

We have a FC2.

The FC2 is brand new (purchased within the last couple months).

We did the following:

• connected the USB cable '10' to J3.
• connect a known working micro-usb cable to my laptop running QGC.
• didn't here the usual windows 'new usb device sound'

This was the first time we connected this board. We didn't see any LED's turn on within a second or two so we picked it up by the corners and noticed it was VERY hot.

We quickly disconnected everything.

We inspected the board and found a component on the bottom looks like it shifted off it's solder pads. See attached picture. We didn't inspect the board before hadn

What could have caused this? Especially given a few others have had this.

Thanks!