Closed GoogleCodeExporter closed 9 years ago
Addendum: The above was with the board being powered from the MCU programmer,
display at 4.8V. Oddly, when we connected the main batteries, the alarm started
working. Hmmm.
Original comment by gru...@gmail.com
on 16 Mar 2012 at 4:24
Have a look around gruvin9x.cpp:1696
Original comment by bson...@gmail.com
on 2 Apr 2012 at 8:13
... && g_vbat100mV>49
WTF? That's being removed right now. Must be some hangover from the days before
bandgap checking, which is another thing I must get on to for the stock board.
Ironically however, there was another cause for this specific fault. The
transmitter was being powered by the gProg programmer at the time, which meant
that the separate 5V regulator for the stock piezo beeper had no power. Hence,
no sound. but this is good spotting anyhow.
Original comment by gru...@gmail.com
on 3 Apr 2012 at 4:20
No -- I was wrong about the stock beeper not getting power when the switch is
off. It still worked when I tested it.
Investigations in the frsky branch revealed that the intention of the >49 code
was to silence the alarm when being powered off a Flash programmer. The
inactivity alarm is likewise silenced. I can't recall, but this was probably
some of my not-so-brilliant coding.
A better approach would be to also check for !SLAVE_MODE, as well as the 4.9V
lower threshold. In this way the "badness" of this code for genuine flying
conditions will be minimised to occasions when a trainer is available to take
back control of the model.
I'm effecting this in code now. I'll test it in both frsky and trunk and if my
theory works out correctly, I'll generate a maintenance release -- also
including the BG averaging I've been meaning to do for a long time.
Original comment by gru...@gmail.com
on 3 Apr 2012 at 4:44
Original comment by gru...@gmail.com
on 3 Apr 2012 at 4:53
Fixed in trunk and also committed as new frsky maintenance release. I won't
bother announcing it, as it's not really a big deal.
I also added a simple low-pass filter to remove bandgap jitter on the stock
board as well as improving the efficiency (in terms of CPU clock load/spread)
for the v4 board bandgap stuff.
Original comment by gru...@gmail.com
on 3 Apr 2012 at 6:46
Original issue reported on code.google.com by
gru...@gmail.com
on 16 Mar 2012 at 2:17