Anyway of looking at or implementing something to stop WDconsole from loosing connection or automatically do something to regain connection.
Ever since roughly version 9.9/10.0, i have issues with wdpi loosing connection with the weather station (i have tried moving away from weatherlinkIP back to serial, but some problem occured). Output below is when the connection drops, the program carries on.
Luckily, wunderground email me when no communication has been had to 2 hours
651 records writen in database
login OK to 192.168.1.141
changing to /Qweb/weather
upload clientraw.txt to 192.168.1.141 OK
upload testtags.php to 192.168.1.141 OK
upload WeatherViewTags.xml to 192.168.1.141 OK
3128 records writen in database
652 records writen in database
login OK to 192.168.1.141
changing to /Qweb/weather
upload clientraw.txt to 192.168.1.141 OK
upload customclientraw.txt to 192.168.1.141 OK
upload clientrawextra.txt to 192.168.1.141 OK
upload clientrawhour.txt to 192.168.1.141 OK
upload testtags.php to 192.168.1.141 OK
upload WeatherViewTags.xml to 192.168.1.141 OK
3129 records writen in database
653 records writen in database
login OK to 192.168.1.141
changing to /Qweb/weather
upload clientraw.txt to 192.168.1.141 OK
upload testtags.php to 192.168.1.141 OK
upload WeatherViewTags.xml to 192.168.1.141 OK
Never used to have this issue earlier on its the software’s life, in fact, i had wdconsole going for about 40 days without any issue at some point, early october i think that was.
This usually happens at randoms time lengths from starting wdconsole, from a few minutes to a day or 2.
I find that it is a power issue with the PI, I have a HDMI to analog converter connected to my PI and find this uses to much power and the link to the weather station is lost, I unplug the converter when not viewing the screen, and it works fine.
Hmm, this night at 02:10 i got a msg from WU about my station not uploading for 2 hours… Is there a specific logfile where I can see what is causing this?
Both occasions WD console stopped at midnight 00:01. Is that coincedence?
I haven’t experienced sudden deaths in previous releases so I’m craving for a downgrade for now. Can anyone tell me if previous releases are still available for download? And if that’s the case, where to find them.
No, there wasn’t any error in the console window while using Putty. Or shouldn’t it be there? Is there a specific logfile where I can look? Do CWOP was set to no. I can’t find any other NOAA setting in config file.
actually this may be a new problem, same error keeps coming up now. Even after a pi reboot, running in root etc…
consolewd runs for a few seconds, collects 2 or 3 samples of data then comes up with that error.
Seems that started at 21:00 going by the wunderground email.
Current data : Temperature= 9.2 Windspeed =0.6 Gustspeed =12.0 Direction =201 Humidity=96 Barometer=996.1 Daily Rain=10.0
An unhandled exception occurred at $000E48CC :
EInvalidOp : Invalid floating point operation
$000E48CC
$00089948
$000D54E0
OK, fresh installations yesterday of both raspberry and 10.4 wdconsole.
Got email from wunderground this morning at 8am saying no response from station for 2 hours.
So consolewd stopped working at 6am.
Just tried to start it running again and now getting this error after 3 seconds of collections
urrent data : Temperature= 10.1 Windspeed =0.6 Gustspeed =8.0 Direction =163 Humidity=93 Barometer=1003.6 Daily Rain=0.6
An unhandled exception occurred at $000E4C9C :
EInvalidOp : Invalid floating point operation
$000E4C9C
$00089CD0
$000D5868
Now all consolewd does is print this once a minute
602 records writen in database
login OK to 192.168.1.141
changing to /Qweb/weather
upload clientraw.txt to 192.168.1.141 OK
upload testtags.php to 192.168.1.141 OK
upload WeatherViewTags.xml to 192.168.1.141 OK
I have the same problem: http://discourse.weather-watch.com/p/463139
In my case consolewd can run for several days, perhaps a week, before it suddenly stops with the invalid floating point operation message. Two hours later Wunderground tells me my station has stopped. When I then try to start consolewd again, sometimes it starts right away. Other times the floating point message comes after just a few downloads and I have to “sudo ./consolewd” a lot of times before it starts running again. I think this has been with version 10.2, 10.3 and 10.4.
Brian has maybe just found something and has advised me to try version 10.5 b. I have just switched to that version.