Feature #416

Hold on to last valid value from sensors

Added by Hans Cappelle over 6 years ago. Updated over 6 years ago.

Status:NewStart date:04/27/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:FrSky HubSpent time:-
Target version:3.0 FrSky hub and sensors

Description

In case a zero value is received it might be better to hold on to the last valid value received for that sensor.

History

#1 Updated by Espen Solbu over 6 years ago

I don't agree. Unless we know that 0 is a invalid value for absolutely all states for the channel, only then can we ignore values. This should rather be part of the "valid range" option for source channels you mentioned before.

A rephrase of the Issue is probably good enough :)

#2 Updated by Hans Cappelle over 6 years ago

I ment if nothing is received than keep the last received value. The zero is irrelevant indeed.

Espen Solbu wrote:

I don't agree. Unless we know that 0 is a invalid value for absolutely all states for the channel, only then can we ignore values. This should rather be part of the "valid range" option for source channels you mentioned before.

A rephrase of the Issue is probably good enough :)

#3 Updated by Espen Solbu over 6 years ago

ah. then i understand.

It should not be a neccessary change as long as we are using the broadcasts (event based) updates. a channel should not update itself or its listeners unless it actually get a value.

This would be a neccessary option for each channel if we change to a cyclic architecture though.
(for our drilling instrumentation, some channels will go to 0 if no values for a certain time, some stay at previous value and go to "bad quality" (-999.25)
This also will depend some on how we want to implement alarms.. we porbably need to add a "stale" flag to channels, meaning that it has not updated for a long duration

Also available in: Atom PDF