Reading from. dat file

…i really suspect its the delay during the minute change…
I dont know whats causing it, i shut down internet as a test, but that didnt help either.
I really dont know why Loggernet isnt having this issue, maybe because its writing the data at a faster rate probably…
Ive openend the Loggernet logtool and saw it updating data twice a second.
It depends on the amount of rain a day, but on average its recording approximately 0.15mm short every 1.5mm.

it could be that WD is not reading in all the decimal places with the rain data
if you could .zip and email me your settings files and the data file used as the data source, and any other associated files, and detail how it should be setup

Hi Brian,

Ive send you the settings files and the datafile by mail.
Loggernet is running and updating the .dat file and cronpakbusnew is running because that way WD updates faster in the minutechange…
Below are some settings currently set in WD.
In the last post in this topic on page 2 theres a detailed list of rain data recorded by WD.
The csv files in the last picture below doesnt contain data, that probably because cronpakbusnew isnt getting data, but cronpakbusnew is running because that way WD updates faster during the minutechange…

With kind regards.


to stop the cronpakbus starting up
see the screen shots attached

to have the data received light flash,
use this version:
http://www.weather-display.com/downloadfiles/weatherdisplaytest.zip

for me, using your settings,WD completes the minute change over with the seconds being at 2

if your pc is a bit slow and WD is taking too long, then it might be missing some rain tips


Hi Brian,

Thanks for your effort.
The data received box is flashing ok know, great.
The datalogger type setup doesnt hold its setting, when i choose the file input option, its always set to cr200 when i re-open the setting. Ive mentioned this earlier. See picture below.
WD is still updating much slower when not running cronpakbusnew along with WD.
Without running cronpakbusnew it takes around 6 seconds, when running cronpakbusnew its about 2.
Really dont know why.
The 60 excel files to check for missing windgusts during the minutechange in the WD folder arent present when not running cronpakbusnew. You have set that some time ago.
Could this be implemented again when cronpakbusnew isnt running? Maybe to check for missing rain too?
I am wondering if its technically possible to bypass the delay during the minutechange?
Maybe by setting it to update 2 or 3 times a second during the minutechange?
Or writing the mainscreen graphs and data to internet (WU and WOW for example) faster.
If so, i really like to help/test for you. :smiley:

With kindest regards. :smiley:


The datalogger type setup doesnt hold its setting, when i choose the file input option, its always set to cr200 when i re-open the setting. Ive mentioned this earlier. See picture below.
that does not matter the main thing is now the cronbackbus program does not start up

I am not seeing the slow minute change here with your settings and input file

Ive watched the source data (the .dat file i send you) and thats updating flawless every second, no delay in the minutechange. Also the minute data file im running in Loggernet is updating every minute fine without delay.
Do the Davis station users have the same delay during the minutechange?
Even if i stop the source from updating, WD is showing the delay.

Regarding the 60 csv files produced every minute to check for missing data when cronpakbusnew was running, isnt produced now cronpakbusnew isnt running.
Is it possible these can be produced again to check for missing data during the minutechange when cronpakbusnew isnt running now?

With kindest regards.

I just noticed when having the source data (.dat file) screen running next to the WD mainscreen that the live time shown on WD mainscreen sometimes makes a 2 second step instead of 1, and that the data shown in WD is one second behind the source data.
Could this be the delay issue?

Hi Brian, good morning,

I was wondering if its technically possible to resolve the minutechange delay?
That would solve this issue fine :smiley:
It isnt related to pc, its a i5 processor with 8gb memory. Only running WD and Loggernet.
Not better when i switch off internet, no (animated) images running on the mainscreen…
The datasource hasnt got delays and is running smoothly.
You mentioned in a previously post “if WD is taking too long”, whats the cause of that?

With the kindest regards. :smiley:

If the delay cant be fixed technically, (which i think can be done by increasing the update rate during the minutechange and solve this finally), a solution could be the check every minutechange, which was present when cronpakbusnew was running (now isnt) , was running to check for missing windgusts and other weather data during the annoying delay (60 excel files every minute overwritten in the WD folder…)

With the kindest regards. :smiley:

Hi Brian,

WD is running flawless with my hardware, except the issue mentioned above.
Is it technically possible to resolve it?

With kind regards. :smiley:

Hi Brian,

I assume this isnt something thats possible to get solved no?

With the kindest regards. :smiley:

No, ok. I will correct the raintotals every end of the day by using data from Loggernet, which hasnt got the delay in the minute change so it doesnt miss raintips (and maybe more weatherdata…) on the minute change…

With the kindest regards.

…as seen in this custom 1 second log, its missing data…
Unfortunately no seconds are shown, so you have to count the amount of data in a minute…
In the 22:47 its missing 5 seconds of data.
https://youtu.be/ljmdikk7_pI
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:46 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:47 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:48 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:49 0.000 0 0.170
13/1/2019 22:50 0.000 0 0.170
13/1/2019 22:50 0.000 0 0.170

There is a seconds tag if that’s what you want to log:

%time-second%…Current second
%time-minute%…Current minute
%time-hour%…Current hour

…but I’m pretty sure wxsim doesn’t care about data by the second.

Thanks alot Niko for your help, i now can see the seconds in the custom logfile. :smiley:

Ive bought myself an SSD harddisk, maybe this will speed things up hopefully #-o
I dont give up that easily…
Ill try everything to get WD to work properly
I hope i get it up and running today or tomorrow :smiley:

With kind regards.

Have you mapped your schedule of events to see what you have asked WD to do every second and every minute? Cron entries, custom log file, db read/writes, all need cpu/bus cycles access to complete. The fact that WD is able to do all asked of it in 2 or 3 seconds is amazing.

No doubt there are other processes on your computer also competing for cpu/bus cycles. The fact you are able to collect and log data every second is astounding even if you miss a second or two here and there. If you had a Davis station I would say just have WD query the console at the end of the day for the rain total and be done with it. :wink:

Hi,
Thanks for your reply :smiley:
No i havent set WD to do loads of stuff, it made no difference in load even when i stopped to have the source updating…
Ive made the custom log to update every second for some time, that seemed to speed up things a bit.
Having said that, i think its a writing of data kind of delay…
Loggernet im using has 8 pages of weatherdata, animated gifs and graphics, doesnt miss a second…

But im busy installing a SSD harddisk, see if that is going to help.

With kind regards.

WD running now on new SSD harddisk.
So far its running a bit faster, ill see.

With kind regards.

Ive WD running now for some time and it seems to work faster, now and then its “thinking” a bit longer, dont know why.
So im happy with the investment regarding the HD. :smiley:

Hi,

I assume the lack of/or no response on my suggestions/questions here and my other topic, means a no, no further action?
Just let me know.

Ok Thanks.

With kindest regards.