Cumulus Support

I can not understand why I am getting this values.
Min temp 0° C Min pressure 0 hPa.
Win 7 64 bit

Possibly because Cumulus had problems reading the data from the console. Is your console connected to a real serial port, or via a USB adapter? What version and build of Cumulus are you using? If you zip up the diags folder and attach it, I'll see if I can see any problems in Cumulus.

God evening.
I am using a real serial port.
Cumulus version 1.9.3 build 1059
I am sorry for my bad english, hope you understand.

You can see my problem in this picture.

You have your console set to an archive interval of 274 minutes:

2013-10-22 18:14:33.835 : Archive info from station:
2013-10-22 18:14:33.835 : interval=274 countdown=91 numrecords=175

When you started Cumulus up at 05:30 this morning, there were no archive entries available to catch up from 21:20 the day before. So it had to do the rollover for yesterday immediately with no data, so those zero values got marked as the minimum values for today. As it says in the readme.txt: "If you close Cumulus down each night, you should avoid closing it down just before midnight (if you use a midnight end of day), i.e. when the station will not make any more logger entries before midnight. This is likely to cause problems when Cumulus starts up again in the morning, as it will have no 'new' data to read before it has to do the rollover."

To correct those figures for today, stop Cumulus and edit today.ini. But you will either need to adjust your logging interval, or not close Cumulus down overnight, or you will hit the same problem again at some point.

Thanks Steve for great support.
I installed Heavy Weather and saw that archive interval was set to over 4 hours. This morning, when I started Cumulus, everything looked good.
/Fredde

I have a La Crosse W2357, and have had what I think are data transmission problems since installation in My 2013. Yesterday I discarded the USB/Serial adapter, established a proper serial port on my PC, and connected the station directly via serial port. I also upgraded Cumulus to 1.9.4.

This morning I noted the Cumulus home screen reporting '0' for both min temp and min pressure. The diags files show that from 02h00 this morning, on every hour to 05h00, Cumulus has reset itself. My PC is set not to hibernate or sleep, and my archive interval is 5 minutes, as I remember.

Hope some light can be shed on this problem.

Please zip up the diags folder and attach it.

Hi Steve,

I attach my zipped diags folder, as well as a screenshot of the main Cumulus screen. Please note the 'recent extremes' box, especially the times.

There's something strange going on with the date settings on your system. Cumulus is getting confusing information from Windows about whether today is the 12th November or the 11th December. What do the first few lines in your today.ini file look like - the lines with the dates and times? You could try resetting your system date settings; change them to some other setting and then back to the ones you want. Don't have Cumulus running when you do this.

You seem to have 'restart if data stops' set, so Cumulus is constantly restarting, and because of the date confusion, it keeps resetting today's highs and lows. As it says in the help, it is not a good idea to use this setting with La Crosse stations, because it is quite common for it to take over a minute to actually read any data from them.

Thanks for the speedy reply.

From the time I installed my La Crosse and Cumulus I have had date format confusion, and have not been able to sort it out. I have now unchecked 'restart if data stopped', changed system time in windows to a random date and back again the the correct time and date.

Below is my today.ini file:

[General]
Date=12/11/2013
Timestamp=12/11/2013 12:38:00 PM
CurrentYear=2013
CurrentMonth=11
CurrentDay=12
[Wind]
Speed=11.4157829284668
SpTime=12:32
Gust=14.039999961853
Time=12:22
Bearing=67
Direction=ENE
Windrun=7.10687494277954
DominantWindBearing=347
DominantWindBearingMinutes=56
DominantWindBearingX=-41.3455390930176
DominantWindBearingY=185.117752075195
[Temp]
Low=0
LTime=11:42
High=24.8999996185303
HTime=11:42
Total=1382.30004882813
Samples=57
ChillHours=0.0333333350718021
HeatingDegreeDays=0
CoolingDegreeDays=0.248263940215111
[Pressure]
Low=0
LTime=11:42
High=1009.09997558594
HTime=11:42
[Rain]
High=0
HTime=11:42
HourlyHigh=0
HHourlyTime=11:42
Start=0
Yesterday=0
LastTip=2013-11-12 11:42
ConsecutiveRainDays=0
ConsecutiveDryDays=11
RG11Today=0
[ET]
Annual=0
Startofday=0
[Humidity]
Low=0
High=66
LTime=11:42
HTime=12:31
[Solar]
SunshineHours=0
SunshineHoursToMidnight=0
HighSolarRad=0
HighSolarRadTime=11:42
HighUV=0
HighUVTime=11:42
SunStart=0
[HeatIndex]
High=24.8999996185303
HTime=11:42
[AppTemp]
Low=0
LTime=11:42
High=26.1967372894287
HTime=12:09
[WindChill]
Low=0
LTime=11:42
[Dewpoint]
Low=0
LTime=11:42
High=18.014591217041
HTime=12:35
[NOAA]
LatestMonthlyReport=
LatestYearlyReport=
[FineOffset]
FOSensorClockTime=0
FOStationClockTime=0

AntSeiderer wrote:changed system time in windows to a random date and back again the the correct time and date.

That won't help - sorry, I wasn't clear. It's the format you need to change. In the 'locale' settings in the Windows control panel. Change the 'short date format' to something else, save it, and then change it back again. This is apparently a known issue with XP SP3; there was (or still is?) a similar problem with Windows 7.

Changed short and long date format to US style and 'applied', then back to dmy format and 'applied' again.

Is there any way I can check whether this has solved the problem, or do I have to wait and see whether date formats get confused again? Do you think that once the date format issue is resolved, the other issues will disappear?

Thanks again for your help.

AntSeiderer wrote:Is there any way I can check whether this has solved the problem, or do I have to wait and see whether date formats get confused again?

Restart Cumulus and see whether today's extremes get reset.

Do you think that once the date format issue is resolved, the other issues will disappear?

What are the other issues? The only issue you've reported is that today's extremes keep getting reset. The cause of that is the date format confusion.

Restarted Cumulus and sadly the extremes have not been reset. Have a look at my monthy highs and lows for November, which demonstrates the problem well.