I've built an Emonglcd, (running the SolarPV sketch) which is working fine EXCEPT I keep getting "x min basefail" messages displayed. The "x" is usually no more than 5. The Emonglcd unit is in the same room as the Raspberry Pi, so I don't think range is the problem. The time *is* being updated on the Emonglcd, as I can see the backlight come on when it first comes through after a restart (always within 5 mins).
Should the Emonbase be sending messages to the Emonglcd more frequently than the time update every 300 seconds? (That seems to be the only thing resetting the "basefail" timer, which starts whinging after 2 minutes).
If I reduce the "interval" to 100 seconds, the basefail messages disappear, but there must be something wrong with my setup otherwise everyone else would be seeing the same error messages??
It probably isn't related, but I keep getting these messages every 5 minutes (exactly) on the Pi.
2015-01-19 21:36:31,814 DEBUG 10776 NEW FRAME : 1421703391.81 > 0s
2015-01-19 21:36:31,817 WARNING 10776 Discard RX frame 'information' : ['>', '0s']
2015-01-19 21:36:32,023 DEBUG 10777 NEW FRAME : 1421703392.02 -> 4 b
2015-01-19 21:36:32,027 WARNING 10777 Discard RX frame 'information' : ['->', '4', 'b']
System is shop-supplied build (Oct 2014) running as local build on Raspberry Pi, two EmonTX, one EmonTH (all of which are working fine AFAIK, thanks to assistance previously provided!).
Re: Emonglcd keeps saying basefail
The 'original' NanodeRF sketches request the time from the server every 60 s, therefore the GLCD is expecting a time update that often. If your Pi is set to send it only every 300 s, then obviously you will need to adjust the timeout. It's around line 66 in display.ino Both emonTx and emonBase transmission rates are tied together, so that piece of code looks as if it needs a rethink.
Re: Emonglcd keeps saying basefail
Thanks Robert, I'll tweak the "interval" setting in /boot/emonhub.conf down to 100, that should fix it. I presume that is equally valid to modifying the SolarPV sketch to wait for ~360 seconds before declaring basefail?
I'm a bit surprised I seem to be the first to have asked the question though!
PS The instructions to set the interval to 300 came from
http://openenergymonitor.org/emon/emonglcd
Realtime Clock: A Raspberry Pi-based emonhub can be configured to send the current time information to an emonGLCD.
On the Pi, edit the emonhub.conf (usually /boot/emonhub.conf) using a text editor. Find the section labelled [[RFM2Pi]] [[[runtimesettings]]], add the following line, and save. (No need to restart)
interval = 300
This will send the current time using its RFM12b, every 5 minutes (5 x 60 secs)
Re: Emonglcd keeps saying basefail
I guess Glyn/Trystan thought every minute was a good number, and Paul thought every 5 minutes was a good number. Remember this is "Open-source"!
Your approaches are equally valid, but of course not the same. Personally, I'd have thought both intervals were overkill, but then I haven't studied the timekeeping accuracy of the GLCD.
In the circumstances, I'd change the GLCD so as to have less load on the Pi - not that it'll make a lot of difference.
Re: Emonglcd keeps saying basefail
I can't say where the "intervals" came from originally, but the 300 seconds in emonHub was carried over from OEM gateway, And Glyn has asked for that "standard" value to be included in the emonhub.conf.
I haven't previously encountered any other value for updating glcd time and that quote from the wiki was actually copied over from a forum post and appears correct.
I'm inclined to agree with Robert, that it may be from an earlier "NanodeRF" implementation and that even 300 is possibly too frequent, but I don't think a short transmission every 5 mins will add to the RF congestion or power consumption etc You should be ok with a more frequent update but if you find packets are being lost extending this interval might be the answer.
Paul