Page 2 of 2
Re: Min temp always 0
Posted: Thu 08 Dec 2011 7:14 pm
by Swede
Great Joy. Cumulus shows a minimum temp AND pressue this afternoon. Dunno if it's a result of me playing with the time setting on the WMR200 or it just happens to be afternoon (clock off 12 hours).
In any case Joy to the World.
===========================================
"Suspicion always haunts the guilty mind;
The thief doth fear each bush an officer."
Shakespeare (Henry VI)
===========================================
Re: Min temp always 0
Posted: Sat 10 Dec 2011 2:29 am
by Swede
Just ran into another problem. I leave C running all day (sometines all night too). Anyway I came up this evening (9 pm) and C was froze up. No readings since 4.30 pm. The WMR200 is still working though.
Couldn't shut C down normally (File/Exit) or by Red X. Had to use File Mgr (Alt-Ctl-Del) to shut it down. Am now using Win 7 Pro (have to update my profile, I see).
As you can see by the readings displayed after I restarted, C was down during some VERY severe weather (high winds and HEAVY rain) occurred while I had my afternoon nap. Just my luck to miss all the fun. {grin}
Here's the Diags zip:
http://swedesdock.com/weather/Diags.zip
===========================
He of whom many are afraid
ought to fear many.
Sir Francis Bacon
===========================
Re: Min temp always 0
Posted: Sat 10 Dec 2011 3:22 am
by Swede
I shut C down, edited a couple files (DayFile.txt?) and deleted bum data, renamed most of the .ini files (Old_alltimelog.txt, Old_month.ini, Old_today.ini, Old_year.ini, Old_yesterday.ini) so new iones get built, restored the a couple files from their .bak's.
Restarted C. Be still my heart, all seems well. {fingers crossed}. Just lost yesterday's totals for today (I think). Will know better tomorriw. {sigh}.
============================
"Dancing is silent poetry."
Simonides (556-468bc)
============================
Re: Min temp always 0
Posted: Sat 10 Dec 2011 10:22 am
by steve
It looks like your station had some kind of problem just after 1627. When you started Cumulus up again, the station started sending it the missing history data, and got as far as 1627:
12/9/2011 20:51:12.251 : Packet:D2 31 1B 10 09 0C 0B 00 00 00 00 00 00 CC 01 00 0C 01 01 07 00 04 19 20 02 00 20 FF FE 13 FE 33 01 00 D1 00 36 70 00 00 91 64 00 47 34 00 00 B8 08
12/9/2011 20:51:12.251 : History data for: 2011-12-09 16:27
After this, the date in the timestamps in the archive data starts going strange:
12/9/2011 20:51:12.470 : History data for: 2011-04-09 16:28
12/9/2011 20:51:12.626 : History data for: 2003-04-09 16:29
12/9/2011 20:51:12.797 : History data for: 2011-12-09 16:30
12/9/2011 20:51:13.000 : History data for: 2003-04-01 16:23
12/9/2011 20:51:13.172 : History data for: 2003-12-09 16:32
12/9/2011 20:51:13.328 : History data for: 2011-04-09 16:33
12/9/2011 20:51:13.499 : History data for: 2011-12-09 16:34
12/9/2011 20:51:13.702 : History data for: 2003-12-09 16:35
12/9/2011 20:51:13.858 : History data for: 2011-12-09 16:36
12/9/2011 20:51:14.076 : History data for: 2003-04-09 16:37
12/9/2011 20:51:14.248 : History data for: 2003-04-01 16:38
12/9/2011 20:51:14.404 : History data for: 2011-04-09 16:39
later, it starts sending garbage:
12/9/2011 20:51:19.380 : Packet:D2 23 02 11 01 04 FF FF FF 00 00 00 00 44 FF FF FF 00 FF 06 FF 04 FF 40 00 00 00 57 56 12 FF 12 FF 61 0D
12/9/2011 20:51:19.380 : History data for: 2255-04-01 17:02
12/9/2011 20:51:19.755 : History packet too short. Sensor count = 255
12/9/2011 20:51:31.954 : Packet:D2 2A 02 12 01 FF FF 00 FF FF FD FF FF 44 FF FF FF FF FF FF FF FF FF 7F F7 7F FF FD FF 12 FF FF 00 FF FF FF 7F FF FF FF BC 1E
12/9/2011 20:51:31.954 : History data for: 2255-255-01 18:02
12/9/2011 20:51:31.954 : Invalid date, ignoring
The time part of the timestamp seems to stay correct throughout, though, except towards the end:
12/9/2011 20:52:21.110 : Packet:D2 A3 FF 14 FF FF FF FF FF FF FF FF FF 40 FF FF FF FF FF FE FF 7F FF FF FF FF FF FF FF 12 FF FF 7F FF FD FF 7F FF FF FF 97 1A 00 FF FF 00 00 35 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 78 37 19 00 46 37 19 00 E0 26 2B 0C 0A A0 00 00 20 01 00 CB 00 3B 78 2D 2B
12/9/2011 20:52:21.110 : History data for: 2255-255-255 20:255
12/9/2011 20:52:21.110 : Invalid date, ignoring
12/9/2011 20:52:21.250 : Packet:D2 23 FF FF FF FF FF FF FF FF FF FF FF FF FD FF FF FF FF FF FF 7F FF 7F FF FD FF 7F FF FF FF FF FF 52 1E
12/9/2011 20:52:21.250 : History data for: 2255-255-255 255:255
12/9/2011 20:52:21.250 : Invalid date, ignoring
I don't know enough about diagnosing this kind of problem to be of much help, I'm afraid - a faulty memory chip, perhaps?