Cumulus Support

How would you determine that ISS contact has been lost?

<#DataStopped> tells you if communication with the logger has been lost I think. But there is no equivalent of <#SensorContactLost> that the FO generates.

They only way I can think of is to compare the <#DavisTotalPacketsReceived> and <#DavisTotalPacketsMissed> over a period of time?

Anyone know what happens to <#txbattery> if no signal is received for some time?

mcrossley wrote:They only way I can think of is to compare the <#DavisTotalPacketsReceived> and <#DavisTotalPacketsMissed> over a period of time?

That's probably the most reliable way. Cumulus probably has an inkling that contact has been lost, because the outside temperature reading will presumably start giving the 'bad data' value (probably at the same time that the console starts showing dashes). But the 'bad data' value could also be returned for other reasons.

Wind speed is the best parameter to monitor in principle - console temperature readings can persist for some time after ISS contact has been lost. (Talking about LCD display readings here - I presume the same will be reflected in the LOOP packets, but never specifically checked.)

The only caveat with this approach is when an anemometer transmitter is in use. For system configurations with multiple transmitters then you need to consider which transmitter outage you're most concerned about.