New quad, motor test worked initially but now nothing

I just assembled a Holybro X500 V2. I installed a Pixhawk 6c. As part of the set up I did a motor test. It worked just fine. At some point of the build the motors stopped responding to either Arming or motor test commands. I don’t get any error messages. I’ve tried all the DShot protocols. I even tried calibrating the ESCs but that didn’t do anything. I’ve tried the all at once calibration but again, nothing happens. When I plug in the battery I can hear the ESCs make an initial sound but they simply won’t spin. In the motor test I’ve tried increasing the output from 5% to 10% and even higher but still nothing. The very first time I did the motor test it worked with the default settings and everything was great. I’m pulling my hair out trying to figure out what changed as I didn’t change any parameters. I’ve tried searching through previous threads and tried a few things but they don’t seem to apply to my build. It’s weird that it worked at first and not now.

Post the parameter file. Are the ESC’s the standard BLHeli_S units supplied with the kit?

Oooh boy, I’ll see how to post the parameters file. I’m not very computer savvy. Yup, they’re the standard ESCs that came in the ARF kit.

Connect to Mission Planner, go to Full Parameter List and Save File. Attached the file in a post.

I hope I did this right.

MP param.param (17.9 KB)

Dshot won’t work on the main outputs as you have it configured. So try this:
BRD_IO_DSHOT,1
MOT_PWM_TYPE,5
SERVO_DSHOT_ESC,2

and then reboot the Flight Controller. You don’t calibrate ESC’s running a Dshot protocol.

THANK YOU! That worked. I don’t understand those settings but now I have some stuff to read up on. I still don’t know why it would have worked initially and then not as I don’t ever remember changing those parameters but alas I’m a happy camper. Thanks again!

Its worked until you change mot_type to dshot. Normal pwm was what you see in first place.

Can I ask another question about ESCs and ArduPilot?

I recently tried some AM32 ESCs made by Sequre. I couldn’t get them to spin the motors. I’m now wondering if I had the wrong parameters for them as well. What settings should I be using for that type of ESC?

BRD_IO_DSHOT,1
MOT_PWM_TYPE,5
SERVO_DSHOT_ESC,1

1 Like

If you use AM32 you will need the very latest ESC firmware

Can I flash the latest FW to the ESCs via the Pixhawk? Admittedly I’m naive when it comes to updating ESC firmware.

Go here and use the configurator to flash the latest version.
AM32
FC should pass thru.

I used a cheap Sequre single AM32 ESC for a thrust test stand project (ongoing), and I couldn’t update it. It works fine, and I think it’s even sending BDSHOT telemetry (have to confirm that, as serial telemetry is also enabled). But the configurator refuses to flash it.

Will be curious as to the experience here with a different model from that manufacturer.

I tried to flash them using the Pixhawk and the AM32 configurator. I wasn’t able to get it to work. The configurator never gave me a green connect button. All the buttons were in red. I might take an old FC and flash Betaflight on it and then connect the ESCs to it and see if I can use it as an interface.

Passthrough may not work on IOMCU.

This pass through is only available on NON IOMCU outputs. Use this features on “AUX” or “FMU” outputs with DShot capability.

It did mention.

1 Like