hello,
since i nstalled 10.18t the programm ends up every 2 or 3 minutes. i’m starting it again, always the same. nothing changed in windows or anywhere else. programm error log shows the baro (1015.5 hpa) as a number. nothing else.
HELP PLEASE! whats that???
Think there is something definitely wrong with the ‘t’ version. I loaded it up and after watching my CPU usage running at 65-70% consitently I dropped back to my previous version and its acting normally…
what weather station tye graphix?
Per his website he has a WS2000.
so then it must have a problem with it getting data from the ws2010-23 data logger at start up…i,.e when its extracting the data
i will do some tests here with my one
losmon, no other reports at this stage like yours…
(but there was few revisions to 10.18t) (and now 10.8u is out).
Ok, will try the ‘U’ version. FYI, I didn’t have NexStorm connected either when this was occurring.
Brian,
Version 10.18U (cut from program error log:
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0000FFFF. Read of address 0000FFFF at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 00000000. Read of address 00000000 at time/date 1:47:18 AM 10/31/04
ERROR: Access violation at address 0041ACC2 in module ‘WeatherD.exe’. Read of address FFFFFFFF at time/date 1:47:32 AM
I’ve dropped back to “J” version which is running fine.
10.18u seems to work without crashes for the moment. running since about 1 hour now. great!
but there is another problem again now: %maxgstdirectionletter% shows “—”. but thats the smaller problem. thx brian for the fix …
one thing more: the com port release times dont work again. in 10.18t it worked good, but then came the problem with the crashes. title says “comm port free” but it isn’t. something even a given time for release is completely ignored by wd.
i’m afraid i’m getting grey hair …
“comm port free”
when does it say that?
when you first start up wd?
or when it goes to release the comport?
that max gust direction i am not sure why its not working just at the moment,…investigating…
it says “comm port free” when it goes to release the comport. but even if it says that my other software wswin can’t find the comport. when i close wd, the comport ist free and wswin can find it. so i guess, the comport release of wd doesnt work as it should.
max gust direction letter is a funny thing now. in 1018t it show a number and in u it only shows —. but thats not the big problem … take time to investigate … 
i have fixed the max gust letter bug in 10.18z
for the com port, i have changed nothing…and so no reports of it not working for other weather station types, like a davis
the problem is your weather station type…a ws2010-13 data logger…
that the problem
as every 3 minutes wd opens the com port…thats the problem.,…other weather station types the com port is never re openeded…with the ws2010-13 data logger, the com port is openeded then closed every 3 minutes (thats the way it has to work with that station), so its just that it not going to work with your weather station type
but i can fix that
10.18z? i guess you mean x? can’t find 10.18z in the downloads. 
i’m using the datalogger ws 2500-pc (so called in germany) from ELV. i don’t know if its the same as ws2010-13. but i would be satisfied if wd would release the comport at the times set in commport setup. for me that would be every hour for 5 minutes. that should be the solution. my datalogger collects data every 5 minutes too. i tried around a couple of weeks now. sometimes it works, sometimes not. don’t know what else to do …
hi
yes, its becuase of the fasct that wd is re opening the com port to get the data from that station type
I will upload a new 10.18x now that should fix this
(i.e the problem you describe only happens with the weather station type you have)