Quads 4 motors continuously beeping

Im running Pixhawk FC, and Tekko32 F4 4in1 50A ESC on Qgroundcontrol - Ardupilot.

My 4 motors are beeping and can not find which parameters to change in order to get them to stop. I was previously running px4 on qgroundcontrol and the motors worked fine.

parameters.params.zip (6.7 KB)

What Pixhawk and what firmware on the ESC?

Pixhawk 6c mini and the ESC should have AM32 firmware on it.

Either move the motors to the Aux outputs (best option) or enable BRD_IO_DSHOT so they will work on the main outputs you have them configured on now. Use Dshot300 for the Main outputs or Dshot600 for the Aux outputs. Configure the SERVO_BLH_MASK if using the Aux outputs. Set SERVO_DSHOT_RATE to triple loop if they are AM32. Set SERVO_DSHOT_ESC,1 for now until you get it working, then try 3 for EDT.

I updated the parameters and it didnt work. I am getting the fail messages:
[18:28:49.183 ] Critical: PreArm: Battery 1 unhealthy
[18:28:49.177 ] Critical: PreArm: RC not found

qgroundcontrol also says my battery voltage is at 1.3. I dont know why the battery level would be reading that low with a fully charged battery.

do you think it could be the battery settings that is causing the motors to beep consistently?

No. It’s most likely still a configuration problem.

im having trouble configuring my ESC as well. I dont know if that is linked to the same problem.

Parameters.params.zip (6.8 KB)

Heres the updated parameters. I think I have everything in place but the motors are still beeping. I updated the battery settings to reflect the type of battery i am using.

It seems like the ESC wants to start but doesnt finish.

The battery is now reading 24V on qgroundcontrol but it still says it’s critical.

You don’t.
You didn’t move to to the AUX outputs and if you did wire them that way you didn’t set the Servo outputs to use them.
Dshot600 will not work on the Main Outputs as I said.
The SERVO_BLH_MASK value of 16384 makes no sense. That’s one output (15)
This should be at default: SERVO_BLH_OTYPE
You didn’t set the SERVO_DSHOT_RATE.
You didn’t change SERVO_DSHOT_ESC back to one.

Looks like you ignored most of what I suggested.

Ditch QGroundControl for now and use Mission Planner for setup. configuration and tuning. You can go back to QGC as a Ground Control Station when this thing is flying.

parameters.param (17.9 KB)

I switched over to mission planner.

SERVO_BLH_OTYPE is at DShot600 - this is correct for using AUX outputs?
SERVO_DSHOT_RATE is set to 3 for tripple loop
SERVO_DSHOT_ESC is set to 1.

Motors are still beeping.

So you have connected to the AUX outputs but are still configured on the main outputs. You need to assign the SERVOx_FUNCTION parameters for outputs 9-12 for the 4 motors and delete them from the Main outputs.
And set SERVO_BLH_OTYPE,0 as I said.
And, since you are on the AUX outputs set this back to default BRD_IO_DSHOT,0

I updated the parameters.

These are the messages im getting:

8/15/2025 3:37:47 PM : EKF3 IMU0 is using GPS
8/15/2025 3:37:40 PM : PreArm: Check mag field (xy diff:175>100)
8/15/2025 3:37:18 PM : EKF3 IMU0 origin set
8/15/2025 3:37:18 PM : Field Elevation Set: 249m
8/15/2025 3:37:18 PM : EKF3 IMU1 origin set
8/15/2025 3:37:12 PM : u-blox 1 HW: 000A0000 SW: ROM SPG 5.10 (7b202e)
8/15/2025 3:37:09 PM : PreArm: Check mag field (xy diff:184>100)
8/15/2025 3:37:08 PM : GPS 1: detected u-blox
8/15/2025 3:37:08 PM : GPS 1: probing for u-blox at 230400 baud
8/15/2025 3:37:04 PM : EKF3 IMU1 MAG0 initial yaw alignment complete
8/15/2025 3:37:04 PM : EKF3 IMU0 MAG0 initial yaw alignment complete
8/15/2025 3:37:04 PM : EKF3 IMU1 tilt alignment complete
8/15/2025 3:37:04 PM : EKF3 IMU0 tilt alignment complete
8/15/2025 3:37:02 PM : AHRS: EKF3 active
8/15/2025 3:37:02 PM : EKF3 IMU1 initialised
8/15/2025 3:37:02 PM : EKF3 IMU0 initialised
8/15/2025 3:37:01 PM : Wait or reboot
8/15/2025 3:37:01 PM : PreArm: AHRS: EKF3 Roll/Pitch inconsistent 13 deg.
8/15/2025 3:37:00 PM : RCOut: PWM:1-16
8/15/2025 3:37:00 PM : AHRS: DCM active
8/15/2025 3:37:00 PM : ArduPilot Ready
8/15/2025 3:37:00 PM : Initialising ArduPilot
8/15/2025 3:36:55 PM : Initialising ArduPilot
8/15/2025 3:36:50 PM : Initialising ArduPilot
8/15/2025 3:36:46 PM : Frame: QUAD/X
8/15/2025 3:36:46 PM : IMU0: fast sampling 2.0kHz/2.0kHz
8/15/2025 3:36:46 PM : RCOut: Initialising
8/15/2025 3:36:46 PM : IOMCU: 410 2003 411FC231
8/15/2025 3:36:46 PM : Pixhawk6C 0030001F 32335117 36343938
8/15/2025 3:36:46 PM : ChibiOS: 88b84600
8/15/2025 3:36:46 PM : ArduCopter V4.6.2 (1ebd4d99)
8/15/2025 3:36:45 PM : Frame: QUAD/X
8/15/2025 3:36:45 PM : IMU0: fast sampling 2.0kHz/2.0kHz
8/15/2025 3:36:45 PM : RCOut: Initialising
8/15/2025 3:36:45 PM : IOMCU: 410 2003 411FC231
8/15/2025 3:36:45 PM : Pixhawk6C 0030001F 32335117 36343938
8/15/2025 3:36:45 PM : ChibiOS: 88b84600
8/15/2025 3:36:45 PM : ArduCopter V4.6.2 (1ebd4d99)
8/15/2025 3:36:45 PM : Frame: QUAD/X
8/15/2025 3:36:45 PM : IMU0: fast sampling 2.0kHz/2.0kHz
8/15/2025 3:36:45 PM : RCOut: Initialising
8/15/2025 3:36:45 PM : IOMCU: 410 2003 411FC231
8/15/2025 3:36:45 PM : Pixhawk6C 0030001F 32335117 36343938
8/15/2025 3:36:45 PM : ChibiOS: 88b84600
8/15/2025 3:36:45 PM : ArduCopter V4.6.2 (1ebd4d99)
8/15/2025 3:36:45 PM : Initialising ArduPilot
8/15/2025 3:36:45 PM : Frame: QUAD/X
8/15/2025 3:36:45 PM : IMU0: fast sampling 2.0kHz/2.0kHz
8/15/2025 3:36:45 PM : RCOut: Initialising
8/15/2025 3:36:45 PM : IOMCU: 410 2003 411FC231
8/15/2025 3:36:45 PM : Pixhawk6C 0030001F 32335117 36343938
8/15/2025 3:36:45 PM : ChibiOS: 88b84600
8/15/2025 3:36:45 PM : ArduCopter V4.6.2 (1ebd4d99)

I got the motors to spin however they all spin the same direction. I try to change them in the setup bit it doesnt work.

Well, you probably still have a configuration problem because of this. So of course you can’t reverse the motors in software because it’s not configured for Dshot.

I was able to change the direction of the motors and test a flight that was unsuccessful. However now Mission Planner says ready to arm whenever I have the drone plugged in but whenever I unplug the drone it will not let me arm. I’m assuming this is a failsafe setting that is preventing the drone from being armed?

Ive worked on recalibrating everything and changing some parameters but nothing solves the issue.