I have been struggling with getting meaningful warnings about low battery. Thus, I have installed a small panel with 3 LEDs; one for arming connected to pin A7, one for GPS connected to A6 and the third for low battery connected to A5 (I wanted to use a LED instead of a beeper).

In MP, I set the LED_MODE to 11 and turned on the Battery failsafe with action to land. (see pictures).

When testing this a few days back, I kept the hex at a low altitude (to avoid fatal crashes). I have also installed a FrSky battery monitor so I can see the voltage on the radio.

When I was getting close to the low voltage alarm I had set on the FrSky, I suddenly saw the arm led on the hex blinking. Probably because I had reached the low voltage set in MP. After a split second, the hex leaned over about 45 degrees and crashed into some chairs. Fortunately only some propellers and the GPS pole was damaged.

If someone could provide some help on the 2 issues below, I would be very grateful.

  1. I have tried to analyse the log, but I have to little knowledge about it. I can see in line 2908 that I get ERR 6 and that MODE is set to Land in line 2907 (the line before ??).
    But why does the hex lean over and crash?
    I have attached the log below. Any help on looking at it would be very much appreciated.
  2. Regarding the low voltage alarm, I would just want to get an alarm at a specified voltage so I can land manually. And why does not the LED connected to A5 light up when I reach the limit? 

Views: 2239

Attachments:

Reply to This

Replies to This Discussion

good guess,  right before it rolls over, it hits a record-low of 3.59v/cell (most likely a 6s setup),  it's too high for a cutoff, but might be a very high soft-cutoff ?

I am sure that is not cause. Neither props or any other mechanical failure in my case. All my props tightened and ESC cut off is set to 2.8. My log attached.

Attachments:

I'm sure I had no loose props as they are fixed with a 3 hole mount.

Embarassed to say that I have not checked the Low Voltage Cutoff on my ESC. However, I'm using the HobbyWing Platinum Pro 30A ESCs. The factory default for these are "Middle" and I have not changed it.

I'm waiting for new propellers before I can do any more testing.

I recently had a sudden lean over, flip and crash on my Y6B running 3.2 on Pixhawk.  I was in a low hover, testing the new firmware, in PosHold and it just flipped over.  No Failsafe but a similar crash.  This might not be related to you issue but it seems very similar to me.

After looking at the log it appears that the front left motors suddenly dropped so I suspect an ECS or sync issue.

My concern is that there is a few people mentioning sudden rolls so I wonder I there is a more in depth problem.  My first inclination is to say that it is not a firmware issue but a hardware one.  However, if a Fe people are seeing uncommanded rolls and flips then maybe there is a problem.

I am running 3DR ESC's with SimonK firmware.  Could there be an issue with sync in the latest release?  Not a code problem but a hardware combination?  Do we need to have a specific version of the ESC firmware to avoid this?

I will test some more when I get new props.

Reply to Discussion

RSS

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service