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:
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.