that was simple enough, just had to enable the website.
Here is the URL with the gauges showing, but no updates. At least progress.
the customclientraw.txt file is returning with a “403 - Forbidden” error.
Does that web host allow the use of .txt files as a MIME type?
Try naming it something else like .js - both the actual filename and the filename in gauges.js
I have no problem seeing one here File not found - DriveHQ Web and File Hosting Service
if you note, that customclientraw.txt is from 9:45pm last night. Not sure why no updates since. So should I make the changes that Mark suggested or is the .txt file okay as is?
The updating is a separate issue so I would put that on one side until you have data, stale or not, on the gauges. I don’t think there is anything wrong with the customclientraw.txt but certainly try what Mark suggests, he is the author…
I am nervous that this doesn’t appear to be a regular web hosting account and that may be impacting your results.
on a lark, I decided to restore the file name in gauges.js back to just ‘customclientraw.txt’ and now the gauge show the date from 9:45pm last night! MORE PROGRESS!!! Now to sort out the updating issue
That’s good 
re the updating issue
that is done via a cron program
(cronftpreal for the mac version, in the Resouces folder, in the application folder…if you run that in a terminal window, what shows there?)
FTP real vers 4.1
location of ini files via location.txt /Users/Melissa/Documents/wdisplay/
customclientraw flag
client raw location from ini file /Users/Melissa/Documents/wdisplay/webfiles
client raw location from ini file /Users/Melissa/Documents/wdisplay/webfiles
clientraw name =clientraw
Not Using file rename
Port to use 21
Passive mode on
FTP Host to use:
1 3
2 3
3 3
4 3
logging on to
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.
Deleting expired sessions…7 completed.
[Process completed]
I checked and the customclientraw.txt file located in /Users/Melissa/Documents/wdisplay/webpages appears to be updating every minute based on date modified, but the data inside is stale and NOT being updated. Still this file IS not being FTP’ed properly for some reason
it looks like it has lost the FTP settings
try restarting WD
also are you using the latest version?
…or the settings were edited out for security.
A few observations this morning.
Using Cyberduck to FTP a freshened copy of customclientraw.txt into the proper folder on my FTP site DOES result in it being refreshed to the displayed webpage on the next 15 second cycle. This proves that IF we solve the FTP problem & the fact that WD does NOT seem to be updating the c
WD on an initial startup DOES refresh customclientraw.txt on the local machine in the web files directory with the latest data from the weather station display including the initial time stamp and the timeUTC data.
WD after initial startup is updating weather data of the station data once every 60 seconds in customclientraw.txt
WD after initial startup is NOT updating the time stamp information in customclientraw.txt. This following string remains constant < {“date”:“08:02 AM”,“dateFormat”:“m/d/y”. As I stated, if I exit WD and restart then the time stamp does update. Also further down in the file ,“timeUTC”:“2018,04,26,13,02,00”, appears and like the earlier timestamp this one is not updating after the initial startup of WD.
FTP in WD is simply NOT working for whatever reason. I have NO issues using Cyberduck with the same credentials, so it is NOT a hosting site issue.
So, it would seem that we have 2 issues. I would think we need to resolve the customclientraw.txt updating issues before we tackle the FTP problem.
I am running version 10.37MAC Build 299 and NO I did not edit out the FTP data. I noticed that there was nothing showing when I sent you that info. I have restarted WD multiple times including this morning, but FTP is not working
Despite having rebooted several times, I had never simply cycled “Main Internet” in the WD FTP connections page. That fixed the FTP issue, so now to resolve the time stamp issue in customclientraw.txt
Any thoughts on the time stamp issue? The weather station data IS updating properly, but the time stamp info is NOT reflecting the time of the update but rather the time when WD was launched!
attached is a copy of the customclientraw.txt file that is being created in the webfiles directory and successfully FTP’ed to the hosting site. While you can’t tell from the attachment, the file was created at 9:38am yet the timestamp info shows 9:28am. This gap grows every minute as the weather station data updates but NOT the timestamp info.
customclientraw.txt (1.61 KB)
This is SO close to working as expected and yet this latest issue is perplexing. Got the FTP working to my web server and got the webpage posting properly. The data IS updating every 15 seconds as I have set. The problem is that WHEREVER the steel gauges pulls the time for the latest upload of data is NOT getting updated. This can’t be all the difficult to resolve but I don’t have a clue as to where to begin.
Please, anyone that might have an idea, chime in and lets resolve this.
My guess - your ftp is not putting the file in the location the gauges are looking for it, they are picking up the file you manually transferred.
I can see the file being updated by the FPT and the weather station data IS being updated and reflected to the webpage. What is happening is after several minutes of the webpage showing that everything is fine (green LED, status bar indicating current trends) the LCD status bar displays a message that the station is offline and it gives how long since the last update…but the updates ARE still occurring AND the gauges are changing as the station outputs change.