Download data missing with WS3085

[davepaterson]

Large chunks or data is lost if MX b3117 is off for several hours. This has been happening since I got the WS3085, I used my old WS1093 as a backup to collect the lost data. I got a replacement WS3085 console and reinstalled Cumulus1 and used it when I lost data.I had gone through all possible causes from console location, USB, Cable, and swapping consoles including going back to b3101.
On the 3rd I setup Easyweather +, Cumulus1 and MX at 15:30 then switched off the LapTop. At 21:44 I loaded up all the versions(one at a time). Easyweather + loaded every min., Cumulus1 only lost 2 which was during the download time, however CumulusMX had no data between 17:32 and 19:59. and 1 min at download time. Have attached Diag files from 1 and MX

[ConligWX]

perhaps the logfiles from CumulsMX might help. the zip fle contains logs from cumulus only.

Diags1

Code: Select all

03/03/2021 08:14:37.676 : Cumulus 1.9.4 Build 1099 startup
03/03/2021 08:14:37.676 : "C:\Cumulus\cumulus.exe"
03/03/2021 08:14:37.676 : Appdir = C:\Cumulus\
03/03/2021 08:14:37.676 : Working directory = C:\Cumulus

DiagsMX

Code: Select all

03/03/2021 08:24:52.485 : Cumulus 1.9.4 Build 1099 startup
03/03/2021 08:24:52.485 : "C:\Cumulus\cumulus.exe" 
03/03/2021 08:24:52.485 : Appdir = C:\Cumulus\
03/03/2021 08:24:52.485 : Working directory = C:\Cumulus

try zipping up and posting the MXDIAGS folder from CumulusMX directory, not cumulus.

[davepaterson]

OOPPSS
MX attached.

[ConligWX]

OOPPSS
MX attached.

there is no log entries from the time frame you have given. so cumulusMX was not running.

logfile:20210303-154213.txt and ends:

Code: Select all

Exiting system due to external: Close Main Window
2021-03-03 15:53:11.643 Cumulus closing
2021-03-03 15:53:11.643 Stopping timers
2021-03-03 15:53:11.643 Stopping station...
2021-03-03 15:53:11.643 Stopping data read timer
2021-03-03 15:53:11.643 Stopping minute timer
2021-03-03 15:53:11.643 Nulling hidDevice
2021-03-03 15:53:11.643 Exit FOStation.Stop()
2021-03-03 15:53:11.643 Station stopped
2021-03-03 15:53:11.643 Writing today.ini file
2021-03-03 15:53:11.643 Completed writing today.ini file
2021-03-03 15:53:11.643 Stopping extra sensors...
2021-03-03 15:53:11.643 Extra sensors stopped
2021-03-03 15:53:11.643 Station shutdown complete
Cumulus has shutdown

next logfile is: 20210303-213239.txt starts@

Code: Select all

2021-03-03 21:32:39.716  ========================== Cumulus MX starting ==========================
2021-03-03 21:32:39.729 Command line: "C:\CumulusMX\CumulusMX.exe"  
2021-03-03 21:32:39.729 Cumulus MX v.3.10.2 build 3117

If you care to look at the file you will see this last file reads the data from logger then processes it.

I did notice this in the logfile however:

2021-03-03 21:33:19.177 Processing data for 03/03/2021 19:59:47
2021-03-03 21:33:19.177 Ignoring bad data: inhum = 128
2021-03-03 21:33:19.178 Ignoring bad data: pressure = 6580.9
2021-03-03 21:33:19.178 offset = 27.4
2021-03-03 21:33:19.178 Sensor contact lost; ignoring outdoor data

not sure if that means anything.

Code: Select all

2021-03-03 21:33:19.175 Latest reading: 
2021-03-03 21:33:19.177 Processing data for 03/03/2021 19:59:47
2021-03-03 21:33:19.177 Ignoring bad data: inhum = 128
2021-03-03 21:33:19.178 Ignoring bad data: pressure = 6580.9
2021-03-03 21:33:19.178                    offset = 27.4
2021-03-03 21:33:19.178 Sensor contact lost; ignoring outdoor data
2021-03-03 21:33:19.178 Windrun: 0mph for 1 minutes = 0.0miles
2021-03-03 21:33:19.178 DoLogFile: Writing log entry for 03/03/2021 19:59:47
2021-03-03 21:33:19.178 DoLogFile: Written log entry for 03/03/2021 19:59:47
2021-03-03 21:33:19.178 Writing today.ini, LastUpdateTime = 03/03/2021 19:59:47 raindaystart = 1.64173228179 rain counter = 1.64173228179
2021-03-03 21:33:19.178 Latest reading: 
2021-03-03 21:33:19.178 Processing data for 03/03/2021 20:00:47

perhaps Mark could advise.

[davepaterson]

This diag file 20210303-213239 shows the lost data times
Attached

[ConligWX]

so did your other two programs import the erroneous data?

Code: Select all

2021-03-03 21:33:19.177 Ignoring bad data: inhum = 128
2021-03-03 21:33:19.178 Ignoring bad data: pressure = 6580.9
2021-03-03 21:33:19.178 offset = 27.4

[davepaterson]

From 15:30 to 21:45 cumulus and the laptop were off. The lost data and some large spikes are sometimes entered (like over 600 ins. of rain this year) and is only seen after a restart

[davepaterson]

As I use the saved data folder the .ini files go with it although the errors in the log files are removed.

[ConligWX]

From 15:30 to 21:45 cumulus and the laptop were off. The lost data and some large spikes are sometimes entered (like over 600 ins. of rain this year) and is only seen after a restart

the logfile says different.

CumulusMX was started at 21:32, no not sure how if your laptop was off. confused.....

Code: Select all

2021-03-03 21:32:39.716  ========================== Cumulus MX starting ==========================
2021-03-03 21:32:39.729 Command line: "C:\CumulusMX\CumulusMX.exe"  
2021-03-03 21:32:39.729 Cumulus MX v.3.10.2 build 3117

your logfile report a pressure of:

Code: Select all

Ignoring bad data: pressure = 6580.9

6580.9

thats not normal. and possibly CumulsMX has dumped whatever was collected. Maybe someone could advise.

@mcrossley

[davepaterson]

After starting MX the log files from 15:30 to startup are saved.

these are the log file entries that show the lost time

03/03/21,17:30,2.8,85,0.5,0,7,308,0.00,0.00,1037.2,1.64,19.0,56,0,2.8,2.8,0.0,0,0.000,0.000,0.9,0,5.0,22,0.00,0.00,2.8,2.8
03/03/21,17:31,2.7,85,0.4,0,7,319,0.00,0.00,1037.3,1.64,18.9,57,2,2.7,2.7,0.0,0,0.000,0.000,0.8,0,5.0,90,0.00,0.00,2.7,2.7
03/03/21,17:32,2.7,85,0.4,0,7,322,0.00,0.00,1037.3,1.64,18.9,57,4,2.7,2.7,0.0,0,0.000,0.000,0.8,0,5.0,270,0.00,0.00,2.7,2.7
03/03/21,19:59,2.7,85,0.4,0,7,322,0.00,0.00,1037.3,1.64,18.9,57,4,2.7,2.7,0.0,0,0.000,0.000,0.8,0,5.0,270,0.00,0.00,2.7,2.7
03/03/21,20:00,2.7,85,0.4,1,2,247,0.00,0.00,1037.2,1.64,18.9,56,2,2.7,2.7,0.0,0,0.000,0.000,0.6,0,5.0,247,0.00,0.00,2.7,2.7

[mcrossley]

You can see that MX is downloading the logger, and the memory locations skip time...

Code: Select all

2021-03-03 21:33:02.471 Read logger entry for 03/03/2021 20:00:47 address 6D70
2021-03-03 21:33:02.622 Read logger entry for 03/03/2021 19:59:47 address 6D5C
2021-03-03 21:33:02.777 Read logger entry for 03/03/2021 17:32:47 address 6D48
2021-03-03 21:33:02.928 Read logger entry for 03/03/2021 17:31:47 address 6D34

But in Cumulus they do not...

Code: Select all

03/03/2021 21:50:35.841 : Request EW data block, addr = 006D70 
03/03/2021 21:50:35.856 : EWUSB: EW startup data line 13  01 38 BD 00 55 1B 00 72 
03/03/2021 21:50:35.864 : EWUSB: EW startup data line 14  27 03 0A 00 0B 8B 00 00 
03/03/2021 21:50:35.864 : EWUSB: Data: 01 38 BD 00 55 1B 00 72 27 03 0A 00 0B 8B 00 00 
03/03/2021 21:50:35.872 : EWUSB: EW startup data line 15  00 00 00 00 01 38 BD 00 
03/03/2021 21:50:35.872 : Solar Data: 00 00 00 00 
03/03/2021 21:50:35.880 : EWUSB: EW startup data line 16  55 1B 00 72 27 00 07 00 
03/03/2021 21:50:35.880 : EWUSB: interval = 1
03/03/2021 21:50:35.880 : EWUSB: timestamp = 03/03/2021 20:00:30
03/03/2021 21:50:35.880 : EWUSB: Lastupdatetime = 03/03/2021 15:35:00
03/03/2021 21:50:35.884 : Request EW data block, addr = 006D5C 
03/03/2021 21:50:35.904 : EWUSB: EW startup data line 13  01 38 BD 00 55 1B 00 72 
03/03/2021 21:50:35.912 : EWUSB: EW startup data line 14  27 07 1F 00 07 8B 00 00 
03/03/2021 21:50:35.912 : EWUSB: Data: 01 38 BD 00 55 1B 00 72 27 07 1F 00 07 8B 00 00 
03/03/2021 21:50:35.920 : EWUSB: EW startup data line 15  00 00 00 00 01 38 BD 00 
03/03/2021 21:50:35.920 : Solar Data: 00 00 00 00 
03/03/2021 21:50:35.928 : EWUSB: EW startup data line 16  55 1B 00 72 27 03 0A 00 
03/03/2021 21:50:35.928 : EWUSB: interval = 1
03/03/2021 21:50:35.928 : EWUSB: timestamp = 03/03/2021 19:59:30
03/03/2021 21:50:35.928 : EWUSB: Lastupdatetime = 03/03/2021 15:35:00
03/03/2021 21:50:35.933 : Request EW data block, addr = 006D48 
03/03/2021 21:50:35.952 : EWUSB: EW startup data line 13  01 39 BD 00 55 1B 00 73 
03/03/2021 21:50:35.960 : EWUSB: EW startup data line 14  27 00 11 00 0C 8B 00 00 
03/03/2021 21:50:35.960 : EWUSB: Data: 01 39 BD 00 55 1B 00 73 27 00 11 00 0C 8B 00 00 
03/03/2021 21:50:35.968 : EWUSB: EW startup data line 15  00 00 00 00 01 38 BD 00 
03/03/2021 21:50:35.968 : Solar Data: 00 00 00 00 
03/03/2021 21:50:35.976 : EWUSB: EW startup data line 16  55 1B 00 72 27 07 1F 00 
03/03/2021 21:50:35.977 : EWUSB: interval = 1
03/03/2021 21:50:35.977 : EWUSB: timestamp = 03/03/2021 19:58:30
03/03/2021 21:50:35.977 : EWUSB: Lastupdatetime = 03/03/2021 15:35:00
03/03/2021 21:50:35.981 : Request EW data block, addr = 006D34 
03/03/2021 21:50:35.999 : EWUSB: EW startup data line 13  01 39 BD 00 55 1B 00 73 
03/03/2021 21:50:36.008 : EWUSB: EW startup data line 14  27 00 07 00 04 8B 00 00 
03/03/2021 21:50:36.008 : EWUSB: Data: 01 39 BD 00 55 1B 00 73 27 00 07 00 04 8B 00 00 
03/03/2021 21:50:36.015 : EWUSB: EW startup data line 15  00 00 00 00 01 39 BD 00 
03/03/2021 21:50:36.015 : Solar Data: 00 00 00 00 
03/03/2021 21:50:36.024 : EWUSB: EW startup data line 16  55 1B 00 73 27 00 11 00 
03/03/2021 21:50:36.024 : EWUSB: interval = 1
03/03/2021 21:50:36.024 : EWUSB: timestamp = 03/03/2021 19:57:30

At block address 6D48 MX skips the time ahead 27 minutes.

I do not know how Cumulus 1 did it, but the MX code uses the value of first byte of each data block to determine the number of minutes to skip forward to timestamp the next logger record.

MX then decodes all the history records from 15:53 until it gets to that jump - that is when the data it decodes is bad.
After that it is OK again. But you have a 27 minute gap in your data.

As C1 read it OK, it looks like there may be some glitch on USB when MX download the data that caused a bad block.

[davepaterson]

To cut out any USB difference the MX,C1 and EW+ ran one after another without moving the laptop, station or cable. It is only since getting the WS3085 that massive time loss has happened but never using C1. MX was tried today at 13:32 with only then mins. lost during download time. C1 rain shows over 600 ins. for this year, which file hold that record?
Will continue to use C1 and update in a few days.

[davepaterson]

C1 takes a long time to download so kept b3117 going, with b3101 as a backup on the other station. So far the station (on b3117) locked up once and had to be reset. The main change between what I use MX for is and others on this form is I do not have a web site and don't need to run non stop but have done so over the last few days. I update b3101 3 time a day and have noticed that during the time taken, when b3117 is restated the logfile has no entry in the logfile during that time period plus the next expected entry.
The wind entry with b3117 is now an integer

[mcrossley]

The wind entry with b3117 is now an integer

You can adjust the decimals under Station Settings > General Settings > Units > Advanced Options

[davepaterson]

Thanks Mark. But as I entered the last post the station using b3101 started missing data 2.5 hours worth over a 5 hour period. As I keep a copy of the morning data file a fresh start C1 downloaded correct including the lost time. I left C1 running overnight until Windows did an update. Restarted C1 and download was OK. but station using b3117 jumped from 1 min. times to default 30 min. although other setting were OK.
MX is out with C1 being used until there are more missed data and then the WS3085 will also be OUT.
C1 show 600+ inch (from a previous problem) of rain for this year where can I edit this field?