Motor/ESC keeps beeping

Hardware Pixhawk family
1

Hello,
I have a Pixhawk (don’t know if it is 2.4.8 or anything else) It’s a clone one.
Everything was ready for testing, but due to some reason, I was not able to test the drone for the last couple of months.

Today, I resumed working on it. And thought to upgrade the firmware. I did the same. And then I was facing a Throttle Failsafe issue. Which I think, I have resolved. However, along with the throttle issue, another issue I kept on facing is, beeping of ESC/Motor continuously.
The error on the mission planner/QGC is “Prearm: Hardware Safety Switch” with Yellow flashing on Pixhawk.
The moment I armed it, it started beeping faster.

For details on Firmware and one more error, check image.

Can anyone please help me with the issue resolution?

Additionally, just curious to know a couple of things
a. Is MANUAL Flight Mode removed from the list? (My Flight Mode list is not showing that)
b. I want to BYPASS the SAFETY SWITCH and assign a Channel 5 for ARM/DISARM. How to do that? (I have done it in the past, however, now I am not able to do that)

Thanks and waiting for the insights.

Px3
Px31284×680 70.2 KB

2

There is no Flight Mode called “Manual”. Stabilize is likely what you are referring to or possibly Acro.
Flight Modes
BRD_SAFETYENABLE set to 0 disables the switch. You can assign any channel for switch arming/disarming with an RCx_OPTION set to 41. This can be risky if you inadvertently hit the switch while flying.

1 Like
3

Hi Dave,
Thanks for your input on flight modes and arming disarming enabling with switch.

I am still looking for motor continuosly beeping issue to resolve asap.

Thanks again.

4

Post the Parameter file.

1 Like
5

Param list.param (15.5 KB)

6

Try to change MOT_SAFE_DISARM and see if the behaviour changes.

7

Thanks, David for your input. But nothing resolved that.
Motor Safe Disarm was 0, initially.
I changed it to 1.
Issue not resolved
Changed it back to 0.

Another issue I faced today was when I turned the craft ON.
The safety switch armed automatically. The flashing red light turned solid after a minute of power ON.
The switch on the remote control side was already disarmed. No one touched the hardware safety switch to arm it.

8

Well if you have BRD_SAFETYENABLE set to 0, than the safety switch is not used.

1 Like
9

I agree that once it is disabled, safety switch doesn’t make sense.
A Remote Control switch is already assigned for that purpose.

10

Sorry, I have no more ideas. If you have BRD_SAFETYENABLE set to 0 and everything else default, the pixhawk should output MOT_PWM_MIN to the ESCs. If you connect the UAV to your PC you can check what PWM value is output to the ESCs in MissionPlanner under the Status tab. Search for ch1out, ch2out, etc.

grafik
grafik733×831 236 KB

11

Here is the image for your reference

px42
px42638×693 96.3 KB

12

Also, find the error sound here in the attachment.

The attachment is in PPT format. Just click on the speaker in the slideshow. I had no choice other than this, as this forum does not allow us to send any sound format.

Pixhawk.pptx (36.2 KB)

13

I suspect, that 982 might be too low for the ESCs to initialize and thats why they are beeping continously. Try to set MOT_PWM_MAX to 2000 and MOT_PWM_MIN to 1000 and do an ESC calibration.

The PPT did not work. The picture only links to a file Pixhawk error.m4a on your computer in the downloads folder. You can send a .zip file :wink:

1 Like
14

Yes. Thanks for the idea of the ZIP File.

Also, check this image. Isn’t it weird that both the Mot max and min PWM were 0, so far?

PX5
PX5940×464 39.8 KB

Pixhawk error.zip (496.8 KB)

15

No, that´s the default behaviour. If you have them set to 0, than the ch3 values form the radio transmitter calibration are used.

1 Like
16

Hi David,

I found that after calibration and changing those settings of motor min and max., the issue is resolved.
Now there is total silence. No beeps :grinning:

Thank you so much for your time and help.
I will go on a test flight tomorrow. Hope it will have a good flight.

17

I went for the testing and found a couple of issues still stopping me from having a smooth flying.

  1. Slow response towards controlling the craft with my FRSKY 2.4 GHZ Tx-Rx pair
  2. CG is balanced, yet finding that Craft is tilting towards left before taking off
  3. Even in stabilize mode, the craft is not remaining in position and moves towards a direction.
  4. Also, I feel, the motor takes more power before take-off.

Is there any solution in the mission planner for faster response time?

Any solution to these issues is welcome. And that’s a request to guide. Thanks

18

Post a link to .bin flight log. Did you follow the Initial Parameter Setup in Mission Planner’s Setup>Mandatory Hardware screen before 1st flight?

Stabilize mode does not hold position only attitude. Read the Wiki about Flight Modes:
Flight Modes

19

Hi Dave,

Please find the .bin files here - December Test .bin files - Google Drive

Yes. I have followed and done all the Mandatory flight settings before going to the field.
Basically, I tried to fly it in stabilize mode and in planes, it keeps the craft stable, so thought that would be the same here too. Also, I wasn’t able to take off in Loiter mode.

Also, refer to the image attached to this thread post. It is of QGC screen which describes that it has some missing parameters.

Thanks for sharing the flight mode link. That was useful.

2021-12-04 14-47-57.bin (549.5 KB)

20

I see no evidence that you have set the Initial Tuning Parameters as I suggested.

Read about it here:
Tuning Process Instructions
And found here in Mission Planner:

Initial tune
Initial tune1150×866 108 KB

If you don’t see this screen update Mission Planner to latest Beta from the Help screen.