OK, so I worked thru the the process of elimination as supplied by Ricky. So far the WS has been running and sending data to the PC since 1030pm Tuesday night… all the Current data is in sync with the staton console…BUT… the graphs are NOT updating they are just flatlines, showing zero recordings… any clues lads? For a minute I thought it may be fixed…alas…perhaps not quite yet!!!
hi
any errors under view, program error log?
also, what is the barometer reading on the console?
strange you are getting flat lines…
are you getting actual up to date data on the WD main screen, and is the data received light flashing, etc?
LOL I just tried a reboot of the PC…and you guessed it now I cannot reestablish a comms link between the PC and the console :twisted:
Anyway, to anwser your question, all the data in the current weather window appeared the same as on the console screen including the barometer pressure, data quality light was green and the data recieved light green and flashing (7000 plus recieved)…graphs all flatlines…
yes, good progress
1 step at a time
try:
delete all the files in the datafiles folder, before restarting wd
also, when it starts up, is the data received light flashing?
sometimes it might mis fire with establishing a link and waking up the console, so try restarting wd again
Had to use the good weather to get some chores on the farm today, so now experimentation with the WS was possible!!!
Anyway, am back into it now…
There has been some definite progress, altho the comms link is still quite unreliable between PC and Console…
However here is todays results!
I restrated the WS after no communications between console and PC over night this morning. Console took 2 hours to start sending data to PC, but then graphs ran and recorded correctly till 6pm when comms was lost. (this is the best performance so far…)
I noticed the time was not synchronised with the console so sync’s time via the WD interface. Comms restarted but the graphs were not updated. Real time data was correct at both console and PC.
I have taken your advice and deleted all datafiles… graphing has resumed… will advise on outcome and how long it lasts!
I am running the console on batteries only. This :appears" to have IMPROVED but not CURED the intermittent comms issues. It is now easier to get the console talking to the PC, but it still will fail at times without reason.
Current status - 710pm data is being recieved, green light quality, graphs are running. Console is running with the sensors wired to it, not wireless.
So there it is lads… I’d love any thoughts or opinions…could the culprit be the Plugpack delivering 6VDC 500Ma (is the 500Ma insufficient to drive the WS???) Graphing is still irregualr and stops occasionaly, altho data continues to be recieved ok from the console!!!
:?: I m confused about that!! :?:
Cheers all,
Andrew
hi
i havent sent off my console yet, in case you get it all sorted
re graphing, when it stops, check under view, program error log, for any errors
but,the graphing should not be stopping like that.,…
weird…
yeah fair enough mate…hold off and I will se how long the staion remains “up”!!!
so far so good, graphs ahve been recording since 7pm and still all data is working ok. I am not even touching the console or PC as I do not want to alter any configuration!!!
Re the error log, before I deleted the data files, there was errors in the log regarding time faults…looks like WD was sending time requests to the console and not getting a response…anyway, now its all been delted, it seems to be ok…
Another non related question, do I need to enter a barometer offset in WD for NZ conditions? Or just run with the readings coming from the station? If I do need to enter a offset, what do i set it to? Presently, my barometer reads 1017.9MB and rising at 0.3MB per hour…does that sound about right?
hi
you should be a little bit higher than that
i have 1019 hpa here…so set a 2 hpa offset for starters
but its pretty close
(i.e you need to compare to your nearest official reading , at the same time, and take into account any differences in the pressure gradient (isobars)
This whole hobby is all new to me, but I find it absolutely fascinating! What is the nearest “official” live weather site for us here in Auckland? I guess as the crow flys, you are probably 50 - 60kms from my place. Would you expect a large difference in local baro pressure over that distance?
since its a southerly airflow,and a light one at that, we are nearly on the same isobar line, so you can set to me
i am now 1019.2
metar:
there is the auckalnd aiport
NZAA.TXT
so you can enter that as a metar to download (i.e say hourly), and then set to use that to update local sky conditions/ icon
note, click on show metar download times to set those…
and then in the summary image and icon setup, you can tick to set the icon to the metar…
but maybe let wd run overnight as it is…and look at this tomorrow
I have set the offset at +2.0MB, My reading now is 1019.8MB, is that close enough or should I adjust it further in your opinion?
Good call, I’ll leave any other settings till tommorow!! just getting quite excited as it it starts to work properly!! The bizarre thing is, I actually don’t know whats different EXCEPT for:
the WS is now operating on battery supply only.
I deleted all the datafiles as directed by you.
Now when I restart WD, comms comes up quickly and the graphs are running correctly… be interested to see if it continues till morning…
Just catching up with the latest developments here…
all very strange, but good that things are working better now,
sounds like the serial connection has been right on the edge of operating properly, for whatever reason… oh well see how it all goes I guess for a while then try plugging the adapter back in! do you have the dick smith part number?
You mentioned error messages about reading console time…? Brian, thats not an option that would be valid/useful here is it perhaps? did you have an option in WD somewhere for PC sync? that should probably be turned off?
my fingers are crossed for you! all very technical lol
Comms was lost (according to the graphs) at around 2am (after recording a external temp low of -1.2 deg C - mean frost here this morning) and the graphs flatlined thru till 7am (console data was different to PC data being displayed in current weather - altho data was still being recieved with green lights showing and packet count moving) when I checked the PC and restarted WD…so far , I have not been able to reestablish the comms link betwen the two, but found that yesterday if I just left the console and PC connected, after around 2 hours, they would start to talk to each other!! Have left it like that for now!
Ricky, there is an option to sync the PC time with the console, and my WD is set to do this every 6 hours (I thought the 2 devices had to be in sync?)…which coincidentally is about the time the graphs flatline…you could be on to something there!!! Altho, that does’nt explain why it takes so long for comms to establish betweent he PC and Console at startup!! Still this could be another way forward…
hi
been at a school “olympics” all day …
yes, definatly try untikcing to sync the pc time to the console
that must be one of the problems by the look
instead, maybe, use the internet time sync, in the barometer/rainfall and offsets setup…(but you need to have the internet setup in the connections in the ftp/internet setup)
hi
ok, i have reviewed the code for the time sync of the pc time to the console time every 6 hours, and i can see that is the problem all along…
i.,e sometimes it is failing…
and so now i am putting in a fail safe 1 minute later…
so it looks to be my fault!
uploading a fix now as a new 10.16d
Gidday Brian, good news, hopefully this will fix my fault?? Do i just download the WD10.16d exe file and install it to the WD folder and it will all be taken care of?