WS-2080 Ambient Weather Station will stop downloading data after a couple of days. I returned the first station thinking it was the hardware, and the second one does the same thing. The console continues to display proper readings. Removing a battery and restarting Cumulus will cause it to work again for a couple of days, but eventually it quits downloading data. I tried adding a line to ini file suggested elsewhere ( EWdisablecheckinit=1), but that didn't help. PC is a Windows 7, SP1 32bit. I'm using release v1.9.2 build 1029. diags zip file attached. Appreciate any help.
Looks like a problem with the station. It stopped sending data just before 1600 on the 4th Feb:
2/4/2012 15:54:00.194 : *** Data input appears to have stopped
You had previously been getting a lot of 'lost sensor contact' reported - for several hours at a time.
When you restarted Cumulus, the first 8 bytes of the station's memory had been corrupted (presumably a symptom of the problem that caused it to stop sending data):
2/5/2012 09:04:45.695 : Request EW data block, addr = 000000
2/5/2012 09:04:45.715 : EWUSB: EW startup data line 01 09 7F 00 2B 00 49 50 04
2/5/2012 09:04:45.725 : EWUSB: EW startup data line 02 60 E1 0A FB 9F 1E F5 FF
2/5/2012 09:04:45.735 : EWUSB: EW startup data line 03 1E 47 08 2D 09 00 00 00
2/5/2012 09:04:45.745 : EWUSB: EW startup data line 04 85 00 00 E0 00 00 F0 0E
2/5/2012 09:04:45.745 : EWUSB: Bad startup block 0, discarding. Byte 0 = 09 Byte 1 = 7F
It looks like you then reset the station, as its memory then contained sensible values:
2/5/2012 09:06:44.070 : Request EW data block, addr = 000000
2/5/2012 09:06:44.090 : EWUSB: EW startup data line 01 55 AA 80 10 20 E6 40 04
2/5/2012 09:06:44.090 : EWUSB: EW startup data line 02 60 E1 0A FB 9F 1E F5 FF
2/5/2012 09:06:44.100 : EWUSB: EW startup data line 03 1E 47 08 2C 09 00 00 00
2/5/2012 09:06:44.110 : EWUSB: EW startup data line 04 85 7F 00 01 00 00 00 01
You continue to get a lot of 'lost sensor contact' reported:
2/5/2012 09:07:04.324 : Lost sensor contact!!!
2/5/2012 09:07:14.326 : Lost sensor contact!!!
2/5/2012 09:08:03.912 : Lost sensor contact!!!
2/5/2012 09:08:13.913 : Lost sensor contact!!!
2/5/2012 09:08:23.924 : Lost sensor contact!!!
2/5/2012 11:25:30.833 : Lost sensor contact!!!
2/5/2012 11:25:40.834 : Lost sensor contact!!!
2/5/2012 11:25:50.835 : Lost sensor contact!!!
2/5/2012 11:26:00.846 : Lost sensor contact!!!
2/5/2012 11:26:10.846 : Lost sensor contact!!!
2/5/2012 11:26:20.868 : Lost sensor contact!!!
2/5/2012 11:26:30.868 : Lost sensor contact!!!
2/5/2012 11:26:40.889 : Lost sensor contact!!!
2/5/2012 11:26:50.890 : Lost sensor contact!!!
2/5/2012 11:27:00.891 : Lost sensor contact!!!
2/5/2012 11:27:10.922 : Lost sensor contact!!!
2/5/2012 11:27:20.922 : Lost sensor contact!!!
2/5/2012 11:27:30.925 : Lost sensor contact!!!
2/5/2012 11:27:40.927 : Lost sensor contact!!!
2/5/2012 11:27:50.947 : Lost sensor contact!!!
2/5/2012 11:28:00.958 : Lost sensor contact!!!
2/5/2012 11:28:10.962 : Lost sensor contact!!!
2/5/2012 11:28:20.973 : Lost sensor contact!!!
2/5/2012 11:28:30.974 : Lost sensor contact!!!
2/5/2012 11:28:40.994 : Lost sensor contact!!!
2/5/2012 11:28:50.995 : Lost sensor contact!!!
2/5/2012 11:29:00.996 : Lost sensor contact!!!
2/5/2012 11:29:10.997 : Lost sensor contact!!!
... and so on. It's not clear whether the 'lost sensor contact' problem is related to the problem of the station stopping sending data.