Lacrosse WS 2355 Heavy Weather Review Programme

[John G]

I recently purchased a Lacrosse  Professional Remote Weather Station  WS 2355.  The accompanying soft ware--Heavy Weather downloads the data  from the Station console to the computer satisfactorily. But  when I use that data in "Heavy Weather Review" program  the  charting  data is imported as being 9 hours behind Australian Time.  No matter what time  zone I set, the data  interpreted by "Review"  is always 9 hours behind.
I bought and installed equipment in Australia- where I live.
What's the solution please?

[Weather Display]

is the time correct on the station?
is your windows time zone correctly?

[John G]

Yes,  The time on the  console is correct; as is the date:   And if I  change the  zone  back to zero  it  correctly returns the time to Greenwich  Time.   And  the Heavy Weather  History file shows the correct  time and Date

Yes  my computer clock is  running correctly--icon  on bottom task bar shows correct time and date for Australia.

Problem seems to be in Heavy Weather Review software,  using the Data in Heavy Weather's History File.
Thanks for your response!

[Weather Display]

you could look into using different software that works with your station

[John G]

I shouldn't need to!  The software sold with the  equipment should work correctly, otherwise its  mis representation  and false advertising. 

Any suggestions as to which software I should try.
Thanks again

[ALITTLEweird1]

hmmmm...  http://www.weather-display.com/index.php ???

Ive had my la crosse for over 2 years now, and never did once install the software it came with. Found WD, and been using it ever since.

[John G]

Thanks;  Hopefully somebody may have a solution using provided software:

I doesn't look promising though:

Just noted James F. Moore  posted  a similar request "WC 2310  time stamp problems"    on  Jan 29, 2006   and  no body got back to him.

Looks like Heavy Weather Software need a  rocket!!
They should have a patch downloadable by now!

[niko]

I also suggest you try Weather Display software which has many more possibilities than HW, but I have moved this thread out of the Weather Display software support forum since that's not a good place to be posting complaints about Heavy Weather.

[John G]

Its  not  a complaint---its  a plea for a  fix to a problem  that  Heavy Weather may not addressed!

[Weather Display]

but this is not a support forum for that software, and the author of the software is not going to know of the problem
I would suggest emailing La Crosse about the issue

[John G]

Understand    Thank you:

I  was just hoping somebody out there  knew a solution to the problem.

[Mark-C]

Same thing I wrote in another post:

I have the same station and the same problem. After some experimention, I think I have the exact nature of the problem (but don't yet have a solution). (This on Windows NT, I haven't tested on XP yet to see if it is better.)

- The base unit reads the data (up to 175 points) and stores them with the time (I don't know if the base unit DST offset is used or not for the recorded points.
- Heavy Weather is used to download the data.
- Heavy Weather reads the data and converts the date to GMT/UT and stores the data in history.dat in UT form.
- Problem 1: HW does not count for daylight saving, it only uses the raw timezone offset.  So in my case (NZ) it subtracts 12 hours from the datetimes and stores them.
- When Heavy Weather displays or Saves the data, it re-adds the timezone offset, again ignoring any DST.
- Heavy Weather Review loads history.dat and graphs the data.
- Problem 2: HWR does not add any timezone offset at all, it just displays the UT datetimes.
- Problem 3: HWR adds 1 hour if the Windows timezone has daylight saving adjustment selected, but it adds 1 hour all year round, not just when DST is active in the summer.  It just looks at the Windows timezone "Automatically adjust clock for daylight saving changes" checkbox, but does no test to check if DST is actually active.

@John G: Is that the same you are getting?

Given the previous 4 year old mentions of the same problem, I think I am about to try and patch HWR and HW to remove all of the crap DST handling code...