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?
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
ISS contact lost
-
steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: ISS contact lost
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.mcrossley wrote:They only way I can think of is to compare the <#DavisTotalPacketsReceived> and <#DavisTotalPacketsMissed> over a period of time?
Steve
-
prodata
- Posts: 317
- Joined: Sat 05 Feb 2011 7:13 pm
- Weather Station: VP2
- Operating System: Windows - all flavours
- Location: Littleport, East Cambs, UK
Re: ISS contact lost
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.
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.