FrSky Alarms no longer working in newer versions

derFrickler · Post by **derFrickler** » Mon Feb 06, 2012 6:42 pm

Hi there, i have a problem that the Voltage Alarms in the FrSky module are no longer set correctly in the latest versions of the er9x-frsky.
After some research i found out that whatever i set in the alarm settings, the "Alarm Level" bit in the Frame that is sent to the frsky module is never set.

for example this frame is sent if i try to set the alarm level for Analog 1 Alarm 1

7e fc 61 01 00 00 00 00 00 00 7e

the 5th bit of the frame is zero even if i choose alarm level orange, yellow or red, that is why i do not get any acoustic notifications any more....

Is this a bug in the firmware or a setting that i did wrong?

Thanks for your help

Johannes

Post by **cre8tiveleo** » Mon Feb 06, 2012 6:44 pm

What version? There is a warning from Mike that 701 is broken.

---
I am here: http://maps.google.com/maps?ll=44.003067,-79.457256

Post by **MikeB** » Mon Feb 06, 2012 6:52 pm

Erazz has done a quick build of the fix, r703 should sort the problem.

Mike.

derFrickler · Post by **derFrickler** » Mon Feb 06, 2012 7:07 pm

thanks for the fast response, unfortunately it is still not working in the r703 from here:

http://code.google.com/p/er9x/source/br ... -frsky.hex

still get only zeros at the 5th byte.
7e fc 55 00 00 00 00 00 00 00 7e

Just checked, with the r656 it works fine.

7e fc 55 00 02 00 00 00 00 00 7e

derFrickler · Post by **derFrickler** » Mon Feb 06, 2012 7:34 pm

it seems that this is due to the frskyinternalalarm setting, if it is false, a zero for no alarm is transmitted to the frsky module.

menus.cpp: g_eeGeneral.frskyinternalalarm = onoffMenuItem( b, y, PSTR("Int. Frsky alarm"), sub==subN, event ) ;

But where do i set this setting?

Post by **Rob Thomson** » Mon Feb 06, 2012 8:43 pm

On the main system menu.. you should be able to set the sound to alert mappings?

derFrickler · Post by **derFrickler** » Mon Feb 06, 2012 9:03 pm

can't find it...is this only in the speaker version?

Post by **Rob Thomson** » Mon Feb 06, 2012 9:14 pm

Yes. You need the speaker mod for it to work..

However.. if the speaker mod is not on.. it should still use the regular on module sound?

Rob

derFrickler · Post by **derFrickler** » Mon Feb 06, 2012 9:19 pm

i think this is the problem, if speaker mode is disabled i am not able to enable the frsky alarm and the default seems to be that it is disabled instead of enabled....

YES, if i switch to speaker mode i can disable the internal alarm which enables the module internal alarm, back to beeper mode the alarm in the frsky module is working again.

So i think internal alarm should be disabled by default if beeper-mode is selected.

uint8_t frskyinternalalarm:1; should be changed to 0 in myeeprom.h: typedef struct t_EEGeneral

Post by **Rob Thomson** » Mon Feb 06, 2012 9:30 pm

Strange..

Can you try enable it...

turn radio off and on...

then

disable it...

turn radio off and on..

Sounds like it has somehow gotten into the wrong mode!

I saw this happen once on my tx when we where developing the sound mod.. but thought the issue had been resolved. At the time Mike added some code to resolve this.

investigation needed

derFrickler · Post by **derFrickler** » Tue Feb 07, 2012 7:09 am

Unfortunately i will not have time to check this this week, going for skiing tomorrow morning.

But a said before, the default value of frskyinternalalarm is 1, meaning the FrSky Module Alarm is disabled by default.
The default mode of the er9x sound-system is beeper, which requires the FrSky Module to do the alarm by itself.
This does not fit together well, one option would be to set the default value of frskyinternalalarm to 0 to enable the module alarm or even to enable the module-alarm whenever beeper-mode is selected in the er9x.

Thanks a lot for your help and this great firmware!

Johannes

openrcforums