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

lost contact

Talk about anything that doesn't fit elsewhere - PLEASE don't put Cumulus queries in here!
Post Reply
zecrich
Posts: 37
Joined: Tue 16 Aug 2011 9:42 am
Weather Station: WH1081
Operating System: Windows 7
Location: Southchurch, Essex

lost contact

Post by zecrich »

My WH1081 is in constant connection with the display but I'm always getting error messages on Cumulus.
I have a small notebook connected to the station and I have turned off the power saving on USB, the notebook doesn't sleep its always on.

What else could it be?
If it hurts, you're still alive!
water01
Posts: 3670
Joined: Sat 13 Aug 2011 9:33 am
Weather Station: Ecowitt HP2551
Operating System: Windows 10/11 64bit Synology NAS
Location: Burnham-on-Sea
Contact:

Re: lost contact

Post by water01 »

Have you tried ticking Configuration / Station / Settings / Synchronise Fine Offset reads, this sometimes helps depending on your model of WH1081 (usually solves the problem on newer models).
David
Image
AllyCat
Posts: 1132
Joined: Sat 26 Feb 2011 1:58 pm
Weather Station: Fine Offset 1080/1 & 3080
Operating System: Windows XP SP3
Location: SE London

Re: lost contact

Post by AllyCat »

Hi,
zecrich wrote: I'm always getting error messages on Cumulus.
What do the error messages actually say? The "Lost Contact" message (in your title) normally indicates that there is a problem with the radio communications between the transmitter and Console. It occurs after about 6 minutes of "missing" data (which Cumulus then repeats each minute until corrected) and corresponds with "--" fields on the Console LCD.

There are numerous possibles causes, such as local radio interference, excessive expectations of the achieveable range (the ~"100m" specification is only for "open field" or "line of sight" conditions), or a "faulty" transmitter or Console, etc. Take a look at this recent thread for example.

Cheers, Alan.
Post Reply