Can you please confirm whether it’s a ‘date’ or ‘data’ format error? nowcast.txt doesn’t have a date in it so I’m not sure how it could have a ‘date’ format error, e.g. my latest file (with test data) is…
1 strokes per minute 4 strokes in past 5 mins. (avg. 0.8 /min) 13 strokes in past 10 mins. (avg. 1.3 /min) 29 strokes in past 20 mins. (avg. 1.4 /min) 40 strokes in past 30 mins. (avg. 1.3 /min) 90 strokes in past 60 mins. (avg. 1.5 /min)
That’s correct. The file is created on the fly…so my proposed solution of Samba/NFS or SFTP wouldn’t work. Sorry for the confusion.
this was the full error before i turned it off
‘2021/14/01 20:51:00’ is not a valid date and time
Above error or program log occured at :23 29 16 15/01/2021
i may have been still running 120 build at the time
have turned it back on for now using build 125 and will see if i get the same error
If it happens again can you please grab a copy of the current nowcast.txt file to check the contents. I’m wondering if an error was being generated by the CGI script. I’m not sure the errors have dates in but it would mess up the output format. The error date appears to be over 24 hours before the WD error which is also puzzling. If expect the date/time of an error to be within a few seconds if real time for a script that generates output on demand.
Having said that WD seems to have been looking for a date/time which it shouldn’t have been doing from Nowcast.txt.
well i reenabled the lightning using use 2000 nowcast.txt and checked the file location then enabled the http download from the raspberry last night every 5 min
when i checked the nowcast.txt about 20:30 this evening it was showing false strikes but wd has not picked that up which i expected it to have done so not sure what happening
Hmmm, that’s odd. I’m sure other people have reported picking up data from the web nowcast before so it seems to be possible. I’m not currently running the Windows WD so I can’t easily test it. As an experiment try copying the contents of the web nowcast.txt file into a local file and then point WD at the local file to see if it picks the info up then.
well i enabled the simulated lighting and restarted the service eventually wd logged something i have attached some files plus part of the programerrorlog
‘2021/01/04 15:06:00’ is not a valid date and time
Above error or program log occured at :15 06 16 01/04/2021
‘2021/01/04 15:06:00’ is not a valid date and time
Above error or program log occured at :15 07 17 01/04/2021
‘2021/01/04 15:06:00’ is not a valid date and time
Above error or program log occured at :15 08 16 01/04/2021
‘2021/01/04 15:06:00’ is not a valid date and time
Above error or program log occured at :15 09 16 01/04/2021
‘2021/01/04 15:06:00’ is not a valid date and time
Above error or program log occured at :15 10 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 11 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 12 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 13 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 14 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 15 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 16 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 17 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 18 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 19 16 01/04/2021
‘2021/01/04 15:11:00’ is not a valid date and time
Above error or program log occured at :15 20 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 21 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 22 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 23 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 24 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 25 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 26 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 27 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 28 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 29 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 30 16 01/04/2021
‘2021/01/04 15:21:00’ is not a valid date and time
Above error or program log occured at :15 31 16 01/04/2021
and this is continuing to be added too every minute
looking at all the info it is something to do with the lightning that is causing the error but as to whether its the nowcast file or WD i do not know
nowcast - Copy1.txt (258 Bytes)
nowcast.txt (253 Bytes)
lightninglog.txt (69 Bytes)
I think this must be something inside WD. The error doesn’t actually make sense, ‘2021/01/04 15:06:00’ is a valid date and time whether you’re using yyyy/mm/dd (4th Jan) or yyyy/dd/mm (1st April). However, nowcast.txt doesn’t contain any dates/times, as expected and as shown in your attachments of the file, so the date/time can’t be coming from that file. It must be something in the processing of the file, but I haven’t changed the file format and it’s been working for others so I don’t understand why it doesn’t work now.
I can’t remember when the new compiler version of WD came into use, but I wonder if it’s something that’s happened as part of that change?
Hi
its to do with the last strike time shown on the lightning page of WD if i reset all, the error stops till the next strike this was doing it in build 120 pre new compiler
thanks for your input Chris will post as a bug
re the other thread
the problem is the date format
for meteotemplate data
2021/01/04
WD is expecting
01/04/2021
I am not sure where or how or why your lightning time strike is the wrong format
how do you have your windows date format set?
i see now…that other thread did not mention you are using the lightning 2000 nowcast.txt method to get lightning counts into WD
that has the date format as above
but that is not how meteotemplate is expecting it
so that is the problem
I will fix that and let you know
a new .zip update is WD is ready
After building and installing my lightning detector in a waterproof case a few months back, I’ve been waiting for some thunderstorms.
We had a number of them through last night with a few overhead. Plenty of thunder and lightning.
My lightning detector showed nothing, Just the regular ‘noise detected’.
Pretty bummed.
Grrrrr…first thunderstorm in months and my Pi with the AS3935 in it also has the BME680 in it…which means it had the SD card for testing running in it…and that doesn’t have the AS3935 code installed on it. By the time I switched back to the card with AS3935 on the storm had gone. So I’ve no evidence of whether it worked or now. I think the storm was probably about 20-30km south of me so perhaps too far to detect given my noisy local electrical environment, but at least it would have been a test.
I think I need to find something to simulate lightning electrically rather than in software!
I’m not sure if mine is working anymore even after rebooting it. It says the service is running but here’s what is on the http page. I do get values shown on the ‘Useful Links’:
it must of been very close to you and now some sad news on BBC web
It does appear to have been much closer than I thought. The news that Harold is referring to is that a 9 year old boy was killed by lightning whilst playing football in a field about 3 miles away from me.
had some lightning in my area last week but the pi failed to see it just disturbers and noise yet i looked while it was happening
i get sporadic false strikes the attached taken a short time ago shows false strikes but not seen and lightning or heard any thunder
I have the same issue. Did you find out how to fix?
I’ve not been back to visit this recently. Not because I don’t want to fix it. It’s just that there have been so few thunderstorms to allow me to do any real testing. I only remember 2 here in the last 12 months!
