Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
(Note that 4.1.0 (build 4024) - 05 June 2024 remains available, but usage of this version is not recommended - particularly for Davis stations - and the included utility in this distribution for migrating to v4 is known to contain errors affecting conversion of dayfile.txt)
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
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
(Note that 4.1.0 (build 4024) - 05 June 2024 remains available, but usage of this version is not recommended - particularly for Davis stations - and the included utility in this distribution for migrating to v4 is known to contain errors affecting conversion of dayfile.txt)
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
Sensor contact lost
- nking
- Posts: 808
- Joined: Thu 17 Dec 2009 2:03 pm
- Weather Station: W-8681
- Operating System: Windows 10
- Location: Hurstpierpoint, West Sussex, UK
- Contact:
Sensor contact lost
I get this error "Lost Sensor Contact!!!"about once a day and wonder what the Cumulus logic is for deciding that there is an error (I've done a quick search without success). I think I read at sometime that the error warning can be turned off but I may have imagined this. However, depending on the logic - what would be a nice solution would be to have a user variable to state how long/number of "No Contacts" before reporting it as an error. I would add that this would be a nice to have feature if it doesn't involve much effort.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Sensor contact lost
It's part of the data; the console sets a flag.nking wrote:I get this error "Lost Sensor Contact!!!"about once a day and wonder what the Cumulus logic is for deciding that there is an error
I think you imagined itI think I read at sometime that the error warning can be turned off but I may have imagined this.
That would be fairly easy to do; the "number" version, that is. You would have to take into account the fact that Cumulus reads the data every 10 seconds but the data is only updated every 48 seconds. How many consecutive error messages do you typically get (in the diags file) currently?what would be a nice solution would be to have a user variable to state how long/number of "No Contacts" before reporting it as an error. I would add that this would be a nice to have feature if it doesn't involve much effort.
Steve
-
- Posts: 1127
- Joined: Sat 26 Feb 2011 1:58 pm
- Weather Station: Fine Offset 1080/1 & 3080
- Operating System: Windows XP SP3
- Location: SE London
Re: Sensor contact lost
Hi Neil,
I believe that Cumulus simply repeats the "error" message from the station. However, AFAIK, the station only reports this after 6 - 8 transmission messages are "lost", so it should only occur if the system is really "struggling".
Therefore, an extra delay in Cumulus may not help (much); the proper solution is to try to improve the wireless connection (maybe easier said than done).
Cheers, Alan.
I believe that Cumulus simply repeats the "error" message from the station. However, AFAIK, the station only reports this after 6 - 8 transmission messages are "lost", so it should only occur if the system is really "struggling".
Therefore, an extra delay in Cumulus may not help (much); the proper solution is to try to improve the wireless connection (maybe easier said than done).
Cheers, Alan.
-
- Posts: 363
- Joined: Thu 04 Feb 2010 12:22 pm
- Weather Station: 1wire-Cumulus & Fine Offset
- Operating System: Windows 7
- Location: Whitehorse, Yukon Territory, Canada
Re: Sensor contact lost
If it's a recent phenomenon, the solution is most likely to put in new batteries.AllyCat wrote: the proper solution is to try to improve the wireless connection (maybe easier said than done).
Do NOT use rechargable ni-cad or ni-mh.
If it's been going on almost since the first installation, then you are at the hairy edge of range and need to address that as Alan suggests. A search of the forum will bring up lots of advice.
Changing the number of times you get the message before reporting it is treating symptoms not the disease. If the station is set up properly you should never see this message until several years after the first install.
- nking
- Posts: 808
- Joined: Thu 17 Dec 2009 2:03 pm
- Weather Station: W-8681
- Operating System: Windows 10
- Location: Hurstpierpoint, West Sussex, UK
- Contact:
Re: Sensor contact lost
Thanks for the replies.
Steve - here is a filtered list of the lost contacts
Line 3081: 25/08/2012 03:29:37.280 : Lost sensor contact!!!
Line 3082: 25/08/2012 03:29:47.288 : Lost sensor contact!!!
Line 3083: 25/08/2012 03:29:57.296 : Lost sensor contact!!!
Line 3567: 26/08/2012 18:24:16.782 : Lost sensor contact!!!
Line 3950: 27/08/2012 21:39:23.874 : Lost sensor contact!!!
Line 4363: 29/08/2012 05:00:42.087 : Lost sensor contact!!!
Line 4809: 30/08/2012 16:06:43.050 : Lost sensor contact!!!
Line 4873: 30/08/2012 21:20:17.750 : Lost sensor contact!!!
Line 6204: 02/09/2012 11:16:54.767 : Lost sensor contact!!!
Line 6497: 03/09/2012 08:35:14.940 : Lost sensor contact!!!
Line 6539: 03/09/2012 12:03:14.702 : Lost sensor contact!!!
Line 6908: 04/09/2012 17:03:57.538 : Lost sensor contact!!!
Line 7460: 05/09/2012 04:57:49.764 : Lost sensor contact!!!
Line 7545: 05/09/2012 06:55:25.428 : Lost sensor contact!!!
It's not quite daily! If I am interpreting the data correctly it seems that the error light comes on as soon as one lost contact is registered.
Alan/Charlie
The site has not changed and the batteries are new. It is happening more since using the newer kit but as you will note it really is a minor issue. It's just another FO's anomaly and just like the "spike removal" Steve has built, I wondered if a similar approach could be employed for lost sensor contacts. Steve is very good at "making a silk purse out of a sows ear"
Steve - here is a filtered list of the lost contacts
Line 3081: 25/08/2012 03:29:37.280 : Lost sensor contact!!!
Line 3082: 25/08/2012 03:29:47.288 : Lost sensor contact!!!
Line 3083: 25/08/2012 03:29:57.296 : Lost sensor contact!!!
Line 3567: 26/08/2012 18:24:16.782 : Lost sensor contact!!!
Line 3950: 27/08/2012 21:39:23.874 : Lost sensor contact!!!
Line 4363: 29/08/2012 05:00:42.087 : Lost sensor contact!!!
Line 4809: 30/08/2012 16:06:43.050 : Lost sensor contact!!!
Line 4873: 30/08/2012 21:20:17.750 : Lost sensor contact!!!
Line 6204: 02/09/2012 11:16:54.767 : Lost sensor contact!!!
Line 6497: 03/09/2012 08:35:14.940 : Lost sensor contact!!!
Line 6539: 03/09/2012 12:03:14.702 : Lost sensor contact!!!
Line 6908: 04/09/2012 17:03:57.538 : Lost sensor contact!!!
Line 7460: 05/09/2012 04:57:49.764 : Lost sensor contact!!!
Line 7545: 05/09/2012 06:55:25.428 : Lost sensor contact!!!
It's not quite daily! If I am interpreting the data correctly it seems that the error light comes on as soon as one lost contact is registered.
Alan/Charlie
The site has not changed and the batteries are new. It is happening more since using the newer kit but as you will note it really is a minor issue. It's just another FO's anomaly and just like the "spike removal" Steve has built, I wondered if a similar approach could be employed for lost sensor contacts. Steve is very good at "making a silk purse out of a sows ear"
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Sensor contact lost
It's interesting that, with the exception of the 25th, it's only reported once. You would imagine that the console would only set/unset the flag at 48-second intervals, so you would expect Cumulus to report it four or five times at least, for each occurrence. So perhaps these are actually spurious - some kind of data corruption?
Steve
- nking
- Posts: 808
- Joined: Thu 17 Dec 2009 2:03 pm
- Weather Station: W-8681
- Operating System: Windows 10
- Location: Hurstpierpoint, West Sussex, UK
- Contact:
Re: Sensor contact lost
Hi Steve,
Do you need any other data from me to assist or is this one of those things to just live with. I think you may have missed the duplicates for 30/8, 3 and 5/9, not that this is a significant number. I will try another combination of console and transmitter to see if I still get the Lost Sensors, this will probably have to wait a few days.
Do you need any other data from me to assist or is this one of those things to just live with. I think you may have missed the duplicates for 30/8, 3 and 5/9, not that this is a significant number. I will try another combination of console and transmitter to see if I still get the Lost Sensors, this will probably have to wait a few days.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Sensor contact lost
Those were separate occurrences. My point is that as Cumulus reads the data every 10 seconds, and the console updates it every 48 seconds, then every time the console signals 'contact lost', you would expect to see at least 4 notifications in Cumulus, 10 seconds apart.nking wrote:I think you may have missed the duplicates for 30/8, 3 and 5/9, not that this is a significant number.
Steve
- nking
- Posts: 808
- Joined: Thu 17 Dec 2009 2:03 pm
- Weather Station: W-8681
- Operating System: Windows 10
- Location: Hurstpierpoint, West Sussex, UK
- Contact:
Re: Sensor contact lost
I see what you mean - yes it's odd. Would this also imply that Cumulus takes it as a lost sensor after only one occurrence?steve wrote:Those were separate occurrences. My point is that as Cumulus reads the data every 10 seconds, and the console updates it every 48 seconds, then every time the console signals 'contact lost', you would expect to see at least 4 notifications in Cumulus, 10 seconds apart.nking wrote:I think you may have missed the duplicates for 30/8, 3 and 5/9, not that this is a significant number.
Probably not relevant but the new FO's seem to have different communication protocol to the old FO's as I have mention on the forum https://cumulus.hosiene.co.uk/viewtopic.php?f=13&t=7741 , I wonder if there is any connection? (no pun intended) .
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Sensor contact lost
It's probably worth you turning on the debug log (delete any existing file) until you next get a lost contact error, then we can look at the raw data and see what it looks like. Might be informative.
Steve