About telem alarm

The current telem alarm logic is not good. Once a telem voltage is lower than setting target, alarm is triggered and never stop unless the voltage goes back up +0.5v above the setting target.

My minicp's voltage drops from 4.1v to about 3.5v when flying. I set the alarm value to 3.4v, if the alam is triggered, I don't see the heli's battery can recover back to 3.9v even it stops flying, so the TX keeps beeping.

I think we should check if the monitorer value is lower/higher than a target for a certain duration, e.g. 2seconds, instead of using hysteresis.

Also, the current codes try to play 6 set of music to identify different telem configs.Think about that if more than 1 condition are met, could the TX play different tones at the same time?

vlad_vy wrote: I think 2 seconds is very long time. I don't know how frequently updated telemetry data, but if it is 50Hz, will be better to get 5 consecutive reading comply with the condition to trigger alarm, then reset counter. If one of that reading do not comply with the condition, reset counter.

the codes scan telem update for every 100ms , so 5 consecutive reading is only 500ms.

PB, I have checked in modified codes for Telemetry_update(), it check if the monitorer value is lower/higher than a target for a duration of 500ms. And the music is played for every 2 seconds.
Please check it out

vlad_vy wrote: It's more then enough, 0,5 sec delay (valid condition) before trigger alarm. I think 3-5 consecutive reading will be OK.

Vlad_vy, please try attached dfu in your devo8. The telemetry alarm should work as what we discussed here.

vlad_vy wrote: "Telemetry is turned off" - Nice warning, but without reading the user manual (new???) it will be difficult to find where it can be enabled.

Maybe better will be:
"Telemetry is turned off. See protocol options."

In previous version, the telem option is easily to find, but PB asked me to put it inside the Devo button. Frankly speaking, I don't like the idea of letting textsel widgets have a button option, it is an example of good for coders but bad for users.

But inside the protocol options seems to be semantically correct. Users need to read the manual, at least once.

Hi, how does it work in V4.0.1 and Nightly-Build V4.0.1-92e1705?


Once a DSM telemetry alarm is fired (e.g fades=80, frameloss >40, hold >0, voltage) the Devo beeps and vibrates.

I seem not to be able to stop the alarm using a button like it is possible with the CLEAR button on the Spektrum DX8??
It makes sense to stop the alarm with a button and only re-alarm once the threshold is quickly reached again.

In (DX8) practice: You reset flightlog data with the Clear/Stop button.
For voltage you set alarming only to vibrate so it will continue (<=3,5V/cell steadily) or stop if voltage goes back to >3.5V (if you take down full throttle).

The manual tells nothing about stopping telemetry alarms once fired as it seems.
Have I overread or overlooked something?

Can you give me a tip?

Regards

Thomas