Thats what I figured. Cronftp also stopped working after testing 220…even when I went back to build 24 so it must be something outside of WD
Last login: Tue Jun 16 18:05:12 on ttys000
pauls-computer:~ ploiacono$ /Applications/WeatherD.app/Contents/Resources/cronftpreal ; exit;
program execute location /Applications/WeatherD.app/Contents/Resources/
location of ini files via location.txt /Users/ploiacono/Documents/wdisplay/
Client raw FTP Upload 18:09:04 16-6-15
FTP real vers 3.8
location of ini files via location.txt /Users/ploiacono/Documents/wdisplay/
custom flag
client raw location from ini file /Users/ploiacono/Documents/wdisplay/webfiles/
clientraw name =clientraw
Not Using file rename
Port to use 21
Passive mode on
1 5
2 5
3 5
4 5
5 5
6 5
logging on to
Log in failed
Result
uploaded /Users/ploiacono/Documents/wdisplay/webfiles//clientraw.txt failed
Result
uploaded /Users/ploiacono/Documents/wdisplay/webfiles//clientrawextra.txt failed
uploaded /Users/ploiacono/Documents/wdisplay/webfiles//clientrawdaily.txt failed
Hi Brian, I have checked my ISP and my web host and everything is working fine. I uploaded the clientraw file using Filezilla and had no issue doing so. It seems to be tied with my testing of build 220, strange that it would affect all previous builds I have on my pc. Any suggestions?
I could not find a difference between the wdisplayftp.ini dated June 14 created under build 24 and the one created today after starting build 222. I emailed you the two files in case you wanted to take a look. Right now I am using the one from June 14 and using build 24 for the night. Tomorrow I will try build 222 again and be sure to use the wdisplayftp file from the 14th.
Hi Brian B233 history data extraction working. (see Screen Shoots) and much faster. First screen shoot logfile while waiting for WD to download. 2 screen shoot data logger extraction. 3 logfile after startup
WD downloaded the data from the VP data logger then immediately crashed.
Started WD again. It downloaded the data that it had previously downloaded and saved. I know it has saved the data because I can see it on the graphs. It then immediately crashed.
Also, when a program crashes in OS X usually you get a message saying crash information will be sent to Apple. No such message appeared with these crashes. I don’t know why this is the case.
Build 223, no change as far as data transfer from Weatherbridge is concerned. Data is apparently being sent to Weatherdisplay as indicated by the Meteohub missed data extraction window, but nothing appears in the main window, including the graphs. Previously the graphs were flatlining, then they appeared to be displaying data for a very brief time, then those stopped and no line is being generated at all now.
@Hugh Whalen
if you could .zip and email me your settings files
next update , out soon,will fix where alot of settings are not sticking
(is due to a difference in the way the compiler handles tick boxes (I had the same problem I remember now with the original version…need to use onchange instead of onclick event)
Tried build 223 for about 4 hrs tonight. Works real well except it randomly closes at times. WD shutdown 3 times over the 4 hr period I was testing, did not see a definite cause for it.
I see build 224 is out now, I’ll try that tomorrow.