After an SD issue I’ve reloaded my Pi with the current emonPi image & all is generally well, apart from my emonGLCD will no longer report time from the Pi (it’s transmitting temperature information happily enough from what I can tell - certainly reported in emonCMS).
I’ve configured the interval setting in EmonHub & can see the following entries in the log:
Which suggest the Pi is at least sending time information, baseid is set to 20 as is the nodeId on the GLCD (re-flashed with the current SolarPV sketch). Any ideas where to look next?
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). Find the section labeled [[RFM2Pi]] [[[runtimesettings]]], add the following line. Save the file. No need to restart.
interval = 300
This will send the current time using its RFM12b, every 5 minutes (5 x 60 secs)
group = 210
frequency = 433
baseid = 20 # emonPi / emonBase nodeID
quiet = true # Report incomplete RF packets (no implemented on emonPi)
calibration = 230V # (UK/EU: 230V, US: 110V)
interval = 5 # Interval to transmit time to emonGLCD (seconds)
& the sketch:
#define MYNODE 20 // Should be unique on network, node ID 30 reserved for base station
#define RF_freq RF12_433MHZ // frequency - match to same frequency as RFM12B module (change to 868Mhz or 915Mhz if appropriate)
#define group 210 // network group, must be same as emonTx and emonBase
You’re tangled up there.
The base node is usually 5, “#define MYNODE 20” is defining the GLCD as Node 20.
So you have two Node 20s on the system, which is not allowed.
Change the base node back to 5 with
baseid = 5
and tell the GLCD to receive from node 5 with
“const int emonBase_nodeID = 5;”
Then make sure the base can receive from node 20 (the GLCD) with a section that starts
Indeed, 5 seconds is silly. The GLCD keeps time itself and it’s only necessary to correct it occasionally. The only thing that a fast update does is limit the number of values sent starting with the default power-up time (I can’t remember what that is) until it receives an update.
Hi chaps - thanks for that, the 5 secs update was just in there to help speed things up while I was banging my head against the wall with it
const int emonBase_nodeID doesn’t exist in the sketch file (or any of them that I can find on github), the config seems to assume a base nodeid of 15 however:
Success - I dont think the last edit took in the web interface, clicked elsewhere & was prompted to login again, did so & the old baseID was in there still, changed & re-saved & it sprang into life.