its likely to be a ratio
but normally that is OK when you have the clientraw upload set to say every 5 seconds…so that then the customclientraw would be every 15 seconds in that case, sort of thing
(instead of every 3 minutes)
Uhmm, clientraw is set to one minute, so the ratio in this case is 1/5 since the customclientraw is updated every 5 minutes. 60 second is the shortest update interval for clientraw, so I cannot lower it.
The result is that with weather display live the newdata is refreshed every 1 minute and with steel gauges it’s refreshed every 5 minute. that’s the point, i would like to have the same uopdate rate also in steel gauges.
Brian, on the raspberry I tried several times and even setting the clientraw update interval to values lower than 60 seconds it remains 60 seconds. Not sure why, but I’m not able to set intervals less than one minute. Can you double check this issue? Is it a problem on my installation or there is a bug on that?
I looked at the wdconsole.ini and the value is set to 5:
[customclientraw]
updaterate=5
But, I’m quite confused… can I edit the consolewd.ini? I tought it was automatically generated with the data from config.txt? Isn’t it? Also it has some historical data (records, etc…) in it.
yes and no…
with that setting set at 5 seconds, then it should be updating at 5x slower than the clientraw.txt file update rate
i.e if the clientraw.txt file is set for 1 second, then it should update every 5 seconds
sort of thing
More info… definitely seems there is a problem here. This is the config.txt setting:
Do custom clientraw=Y //For updating customclientraw for steel gauges (set to Y for yes, N for no) (every 5 minutes)
Customclientraw update rate=60 //seconds
If I put 60 (it says it’s in seconds) the setting in wdconsole.ini is 60, but the file is not uploaded every minute… f I specify 1 in the config.txt the wdconsole.ini is written with the value of 5 and the customclientraw is uploaded every 5 minutes. So… something is wrong here, maybe some confusion between minute and seconds in the settings.
Finally, any settings I insert in config.txt the customclientraw is updated every 5 minutes… no more, no less.
The settings in config.txt says it’s the interval in seconds, not a multiplier to slow down the customclientraw, so this is quite confusing :?.
If I put that setting to 1 it should be uploaded by ftp at the same interval than clientraw, but this is not happening.
Also, clientraw.txt upload interval, minimum is 1 minute defined by FTP time interval=60, any value less than 60 it’s always uploaded every one minute and this can be ok.
I use PI 2 and 3 in two different locations. Same result with both versions. I use the same wd version, I’ve not tried yet the 64bit version for the PI 3.
Ok, with the updated version the customclientraw.txt file is created more often and this is great, but… it is transferred over FTP only every 5 minutes. Clientraw.txt is transferred over FTP every minute. So, you just need to FTP both files at the same time, every minute in my case and this will solve the issue
the upload rate by the cronftpreal
is determined by the setting
[customclientraw]
updaterate=
in the wdconsol.ini settings file (restart cronftpreal after making any changes)
e.g set that setting to 1
Brian, ok, editing the wdconsole.ini and restarting cronftpreal works and this is good, but each time I restart with GoWdconsole.sh, wdconsole.ini is rewritten with settings from cronfig.txt and the default value of updaterate=5 is used, no matter what I insert in config.txt… this is the problem. There is no correspondence between what i set in config.txt and what is written to wdconsole.ini, so finally when the system starts the ftp upload rate for customclientraw is always 5 minutes :roll:
Also, cronftpreal is started automatically by consolewd and runs in background I don’t start it separately.