Since 10.20t ftp was upgraded from FTP3.3 => FTP 3.4 (what are the extra fearures?)
but more important: why is the second ftp server version 3.2 (this was also the case in lower versions)
this means that it is impossible (unless one uploads the local raw client daily & extra file seperately)
I think not many people use this redundancy & therefore was not seen yet (I hope)
hi
you mean the clientrawrealtimeftp.exe?
i added in hourly uploads of the nexstorm hour data for the nexstorm lightning, if enabled…
I did not add that routine to the 2nd clientrawrealtimeftp2.exe, as not many people would be using that feature, but I can add that easy enough
the next version of WDL will have a drop down to select which hour or nexstorm based lightning data to view
thx, that would be nice
furthermore it’s not only the client raw, (version 3.2 used as second FTP) but from off FTP 3.3 & higher
also the clientextra and client daily are uploaded …
I guess useing latest FTP all the way could ease also your programming (since you can use same sequence …)
cheers,
J
hi
not quite sure what you are meaning
could you please exlain more OK
FTP 1 (most peopple use as standard real time) = version 3.4 (no problem with that, works fine (= FT3.3+nextstorm)
FTP2 is FTP version 3.2 (doesn not upload the clientextra.txt an clientdaily.txt, since you must specify the clientraw.txt as
sinle uploadable file to a second ftp site) I work around by using the seperate ftp uploader of WD to upload the clientrawextra.txt
and clientrawdaily.txt.
I hereby suggested that If FTP1 = FTP2 = … = FTPn are all of version 3.4
confusions are avoided since FTP2 works exaclty like FTP1
oh, it should be uploading those files…
I will check
uploading a new 10.20u now, will be ready in an hour or less to download
with a updated clientrawrealtimeftp2.exe
(which is a now a clone of the clientrawrealtime.exe (I have tested and its OK)
I also fixed a bug with the clienreadaily.txt repeadetly uploading for the whole minute, each 10 minutes
wow, thx 4 the splendid support!!!