Looking for testers for the new Mac version :)

I checked the 62015lg.txt file. You are correct, it did download all the data not just the data every 5 minutes. So, it was just the display during the download which led me to believe there was a problem. So, I guess that was a false alarm. Thanks for pointing me to the place where I could see this.

I opened the ftplogfullreal.txt file. Part of the file listing shows:

uploaded /Users/MacMini/Documents/wdisplay/webfiles//clientraw.txt OK
uploaded /Users/MacMini/Documents/wdisplay/webfiles//clientrawextra.txt OK
1 3
2 3
3 3
4 3
uploaded /Users/MacMini/Documents/wdisplay/webfiles//clientraw.txt OK
1 3
2 3
3 3
4 3
uploaded /Users/MacMini/Documents/wdisplay/webfiles//clientraw.txt OK
1 3
2 3
3 3
4 3

I do not know how to interpret the 1 3, 2 3, 3 3, 4 3 but the rest looks OK.

I have started WD Mac again. It appears to be changing the clientraw.txt file correctly every 2.5 seconds. It appears to be uploading correctly every 10 seconds. All the data on the webpage appears to be updating every 10 seconds except the section just below the radar which says at this time:

Updated: 16-Jun-2015 @ 3:59:46 pm (30 sec ago)

Strange, but of very minor importance.

I just checked the 62015lg.txt file again. This time WD did not download the logged data. Here is the relevant portion of the file:

16 6 2015 8 29 56.6 94 54.9 29.988 6.9 10.3 225 0.000 0.016 0.016 0.016 56.6
16 6 2015 8 30 56.6 94 54.9 29.987 6.9 10.3 217 0.000 0.016 0.016 0.016 56.6
16 6 2015 8 31 56.6 94 54.9 29.987 6.9 10.3 225 0.000 0.016 0.016 0.016 56.6
16 6 2015 8 32 56.6 94 54.9 29.986 6.9 10.3 218 0.000 0.016 0.016 0.016 56.6
16 6 2015 8 33 56.6 94 54.9 29.986 6.9 10.3 185 0.000 0.016 0.016 0.016 56.6
16 6 2015 15 55 56.6 94 54.9 29.985 6.9 10.3 186 0.000 0.016 0.016 0.016 56.6
16 6 2015 15 56 56.9 94 55.2 29.977 6.9 10.3 208 0.000 0.016 0.016 0.016 56.9
16 6 2015 15 57 61.0 92 58.7 29.856 8.1 10.3 211 0.000 0.016 0.016 0.016 61.0
16 6 2015 15 58 61.0 92 58.7 29.856 5.8 6.9 213 0.000 0.016 0.016 0.016 61.0
16 6 2015 15 59 61.0 92 58.7 29.857 5.8 8.1 202 0.000 0.016 0.016 0.016 61.0
16 6 2015 16 0 61.1 92 58.7 29.857 3.5 8.1 213 0.000 0.016 0.016 0.016 61.1
16 6 2015 16 1 61.1 92 58.8 29.857 4.6 9.2 227 0.000 0.016 0.016 0.016 61.1

As you can see the data stopped at 8:33 this morning when I stopped WD.
I restarted it at 15:55. The data starts at 15:55 but did not download the data from the logger for the period 8:34 to 15:54 inclusive.

Whoa, I was examining the Control Panel > Debug info when WD crashed. Restarted WD. Did not appear to download archived data but that is not surprising since it was only a minute or so since it was last opened. Opened Debug and it crashed again. Started WD again. Opened Control Panel > Debug Info and managed to copy this info … it has not crashed yet …

Loaded all time records
Loaded units
Comport open OK
connected OK to com port /dev/cu.SLAB_USBtoUART
restarting timer
*sending DMPAFT
Asking for archived data download
data length 5
re starting download, timer
restarting timer
*sending DMPAFT
Asking for archived data download
data length 3
re starting download, timer
restarting timer
*sending DMPAFT
Asking for archived data download
data length 3
re starting download, timer
restarting timer
*sending DMPAFT
Asking for archived data download
data length 3
re starting download, timer
restarting timer
*sending DMPAFT
Asking for archived data download
data length 3
re starting download, timer
restarting timer
*time out with requesting DMPAFT
Aborted
Asking for archived data download
All data downloaded or did not sync correct!
formating the VP data
vp data read in 1
Comport open OK
connected OK to com port /dev/cu.SLAB_USBtoUART
Weather station type number 31
/Users/MacMini/Documents/wdisplay/webfiles/
**** running cronftpreal
/Users/MacMini/Documents/wdisplay/webfiles/
/Users/MacMini/Documents/wdisplay/webfiles/
/Users/MacMini/Documents/wdisplay/webfiles/

Hope this helps.

Hugh

PS many thanks for looking at this.

*time out with requesting DMPAFT Aborted

for some reason it did not sync up with getting the history data

All the data on the webpage appears to be updating every 10 seconds except the section just below the radar which says at this time:

Updated: 16-Jun-2015 @ 3:59:46 pm (30 sec ago)


so maybe a problem with the script on the web page in how its picking up the time stamp in the clientraw.txt file or similar?

Thanks Brian, the data extraction panel now opens ok.

I have been trying out build 220 and unfortunately I cannot get the cronftpreal to work - login fails each time I try.

On the upside the WU rapid fire is now working with this release, thanks again.

it is the same cronftpreal version that was with the older WD mac verison

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

Quote
*time out with requesting DMPAFT
Aborted

for some reason it did not sync up with getting the history data

End Quote

That looks like it. Why would it do it some times and not others?

I just started it again and this time it picked up the logger data. Oops. It picked up the data from the logger then crashed…

Started it again and it looks fine … It’s connected to the console and is uploading data without a problem.

Random errors are the hardest to deal with. Sigh.

Hugh

doing some more testing with the Davis VP data extraction

if you run WD from a terminal window it should some info about the crash

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?

Thanks

logging on to

this is no server shown
check that the ftp server settings are still set correct for the real time ftp

re the davis VP history data: will get a fix up soon

I did just discover that the wdisplayftp.ini file is corrupted, I need to fix that. Using a previous wdisplayftp.ini file worked ok.

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.

new version up re the Davis VP data logger :slight_smile:

and another new update…removes some debug code from the Davis data logger update…
which makes that much faster now

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

Thanks again
BTrip


Screen Shot 62015lg shut down 2015-06-16 at 7.38.55 PM.png

Screen Shot WD Data Logger 2015-06-16 at 8.21.53 PM.png

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.

Hugh

Hi Brian,

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.

Aloha,

Mark

@Hugh Whalen
it must be a problem in your settings
as that is not happening here
and others are not reporting that

try running it from a terminal window (see my post above)

@mswatanabe
I really need to test by being able to access a meteohub, e.g via port forwarding (yours or someone elses)

@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)

build 224 is up :slight_smile:

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.