Alarm question

[Puttputt maru]

With the Jeti we have two ways to set alarms. For example if I want a capacity alarm with my Mezon I can program it in the Mezon itself but I could just do it in the DC/DS-16 directly.

My question is if I do it directly what value would I put in the mezon or anything else for that matter?
If I was to leave both active what happens then?
(Ok so two questions)

[Kiba]

If you disable the morse alarms in the TX then the morse alarms generated by different telemetry sensors will not be displayed or reported on the TX. If the alarms in the device itself are still enabled the device will still send out the "legacy" morse code alarm but the TX will ignore it.

The morse alarms are more for pre-EX hardware and the Profibox and other legacy Jeti hardware than they are for the DC/DS16 where you can set the alarm parameters right on the TX.

[Puttputt maru]

So basically most of the Mezon setup was useless I could have left all the alarm setting at any numbers it would mot have mattered?
What I am concern about is the cutoff type setting you can't deactivate it ? How is it going to work ?

[Kiba]

If you're using a DS/DC16 then setting the alarm parameters in the Mezon or another Jeti telemetry module isn't needed unless you want to use the "legacy" morse alarms controlled by settings in the individual devices/modules which are less flexible and more time consuming to set than the alarms right in the TX. It's far faster and more flexible to disable the Morse alarm support in the TX, ignore those settings in the devices (via Jetibox), and set all the alarm parameters right on the TX alarms menu.

However, the LVC and capacity cutoff settings in the Mezon aren't alarms-- they are hard limits and those must be set through the Jetibox. When the voltage or capacity (mah) cutoff threshold is reached the Mezon will either do a hard cut or soft (gradual slowdown) of the throttle depending on your setting.

The capacity based throttle cut/slow down in the Mezon resets at every power up. If you don't want the Mezon to have a capacity-based throttle cut then set it to a value well above your pack capacity so it will never be reached.

With my Mezon on 12S 5000 packs I have the Mezon LVC set to 37.2V (cell count autodetect off so it won't detect an incorrect number of cells if I accidentally plug in an already-flown pack) and the capacity cut is set to 4500mah. Cut type is "slow down." In the TX I have the capacity alarm set to 3200mah (by the time I come in and land it's usually between 3350-3500mah consumed) and the voltage alarm set to 38.4V.

[Puttputt maru]

Thank you that was exactly what I wanted to know, much appreciate it.

[Jotto]

There is one advantage with the morse alarm though: the morse code alarm triggers a voice alarm every tenth second or so. The tx-defined alarm is repeated every second. The latter will drive you mad.


Sent from my cellphone

[BustedRaptor77]

Originally Posted by Jotto

There is one advantage with the morse alarm though: the morse code alarm triggers a voice alarm every tenth second or so. The tx-defined alarm is repeated every second. The latter will drive you mad.


Sent from my cellphone

I put the "Repeat" to an x on the ones I didn't want to repeat.

[BustedRaptor77]

On Mah I ended up setting it up to read the value in 1000 mah increments and not repeat. The final one is the actual Warning that repeats. Worked on the bench and why the value shows 10 for testing the theory out.

[Kiba]

Originally Posted by Jotto

There is one advantage with the morse alarm though: the morse code alarm triggers a voice alarm every tenth second or so. The tx-defined alarm is repeated every second. The latter will drive you mad.


Sent from my cellphone

True. If Jeti would add a "repeat delay" it would be appreciated.

On the "fuel level low" voice alert on my turbine I added 5 seconds of silence in the .wav file so there is a 5 second pause between alerts rather than incessant back to back nagging.

On my Goblin the capacity alarm constantly nags me until I flip the switch to turn the alarms off. Maybe I'll record a 5 second blank .wav file and assign that to the alert, that way there will be 5 seconds of silence in between the TX alarm calling out the actual battery mah used.

[BustedRaptor77]

Originally Posted by Kiba

True. If Jeti would add a "repeat delay" it would be appreciated.

On the "fuel level low" voice alert on my turbine I added 5 seconds of silence in the .wav file so there is a 5 second pause between alerts rather than incessant back to back nagging.

On my Goblin the capacity alarm constantly nags me until I flip the switch to turn the alarms off. Maybe I'll record a 5 second blank .wav file and assign that to the alert, that way there will be 5 seconds of silence in between the TX alarm calling out the actual battery mah used.

You don't have to do any of this just set more than one alarm and turn the repeat off.

[Puttputt maru]

An alarm usually means time to land. So you don't need to hear it again. My original solution still stand

https://www.helifreak.com/showthread.php?t=529241

Put the volume control on a knob and just turn it off. Till Jeti gives us an other option

Repeat off is good too. Turning it off gives you the option to hear it again if you have bad memory or bad hearing .

[BustedRaptor77]

Mine reads off every 1000 mah and then the warning goes off at 3500 mah signaling it's time to land by doing this. No repeating. The one I have repeat is the voltage limit as that is what will really mess up your packs. Landing at 19% vs 20% ain't going to ruin the packs.

[Kiba]

I like having the really important alarms on repeat... there has been more than one instance where I've missed the initial alert because of background noise or someone talking to me and distracting me. Thus I have the important alarms on repeat activated by a switch I can easily turn off once I hear them or I can turn the volume down with the LH slider.

One time alerts are good for "progress" reports but for the critical alerts like fuel level, time to land pack capacity, etc I like to have them on repeat. Having an adjustable "repeat" delay would be appreciated to avoid the non-stop nagging as it's currently implemented. As mentioned you could set up multiple alarms with just enough difference between the alarm settings that it would essentially be a "delayed repeat" without being a constantly repeating alarm.

[Puttputt maru]

Originally Posted by BustedRaptor77

Mine reads off every 1000 mah and then the warning goes off at 3500 mah signaling it's time to land by doing this. No repeating.

I like that.
I wonder if we might run out of alarms for some more involved setup. I did not see a limit on the number of alarm possible in the manual.

[BustedRaptor77]

I think the best solution is if the alarms could be global and separate like everything else. Then you could just have an on ground flight mode switch.

[Puttputt maru]

In the end the ideal would be a repeat that you can turn off with a switch or even better momentarily delay

Jeti are you listening

[BustedRaptor77]

Originally Posted by Puttputt maru

I like that.
I wonder if we might run out of alarms for some more involved setup. I did not see a limit on the number of alarm possible in the manual.

Easy to test. I have a whole slew of them and haven't run out. I have 12 alarms and seems fine.

[BustedRaptor77]

Originally Posted by Puttputt maru

In the end the ideal would be a repeat that you can turn off with a switch or even better momentarily delay

Jeti are you listening

Should of said something earlier I saw them today at Joe Nall LOL.

[Kiba]

Originally Posted by BustedRaptor77

I think the best solution is if the alarms could be global and separate like everything else. Then you could just have an on ground flight mode switch.

You can already do this with logical switches; make a logical switch that's only active in certain flight modes and use that logical switch to enable the alarms. Assign the "nagging" alarms to be active only while flying and as soon as you land and switch throttle hold on the alarm shuts off.

I'd still like to see Jeti implement an adjustable "repeat delay" parameter for the alarms.

[BustedRaptor77]

Originally Posted by Kiba

You can already do this with logical switches; make a logical switch that's only active in certain flight modes and use that logical switch to enable the alarms. Assign the "nagging" alarms to be active only while flying and as soon as you land and switch throttle hold on the alarm shuts off.

I'd still like to see Jeti implement an adjustable "repeat delay" parameter for the alarms.

Cool thanks I'll play with that tonight.