I’ve updated my old nanodeRF to an emonBasePi but the emonGLCD is not updating the time (the LCD shows ‘emonBase fail’). The commented out section in ‘void power_calculations()’ is to stop the resetting of wh_gen & wh_consuming to zero during the day (not at 00:00). Is the RTC code in the nanodeRF…

You did delete the hash ‘#’ at the beginning of that line, didn’t you? # interval = 0 # Interval to transmit time to emonGLCD (seconds) so that it reads interval = 60 # Interval to transmit time to emonGLCD (seconds)

That’s really of no interest - it’s saying that you have 671 W on CT1 of your emonTx. (You step through the message, byte by byte, with the up & down buttons. The RH side tells you where you are in the string.) So the emonBase is not transmitting - you should be seeing something from Node 5 - but …

[image] Robert.Wall: (You step through the message, byte by byte, with the up & down buttons. The RH side tells you where you are in the string.) The 3 buttons on the RH side of my emonGLCD do nothing! Thanks Robert (I’m out of my depth here)

They should do - I’ve absolutely no idea why they don’t. A quick recap - is this correct? You swapped your NanodeRF for an emonBase (= Raspberry Pi + RFM69Pi) You’re running the “shop” SD emonCMS on it. You’re seeing the data from your emonTx both in emonCMS and on the GLCD. You’re not getting …

Correct. I sent the output of your sketch emonGLCD_debug to the serial port & there is no data from node 5 (emonBasePi), only node 10 (emonTx)

We need someone who knows how to make the emonBase transmit. There have been recent changes - someone pushed through a change that transmitted the emonPi’s data, I don’t know whether it’s been incorporated in the standard software, or whether that has broken the time transmissions from the emonBase,…

Thanks Robert. Hopefully someone out there knows where to go from here

Bingo! that sorted it. :slight_smile: Now if it had been // instead of # I might have spotted it (told you I wasn’t a coder) Thanks for all your help Robert

What beats my logic is why that line needed to be commented, when AFAIK, ‘0’ means don’t do it anyway. :roll_eyes: Different programs use different characters to denote a comment. The safe way is to look for an obvious comment and see what’s being used. e.g. Bloody Awful Set of Interpreted Command…

[image] Robert.Wall: interval = 0 # Interval to transmit time to emonGLCD (seconds) Since interval = 60 (seconds) could interval = 0 means the time is transmitted continously (every 0 seconds) Just a thought. I’ve only come across REM & // for commenting out lines

So why isn’t a sensible default set - 30, 60, 300 - in the value instead of zero? I don’t know. If I’d written it, I’d have used 0 as a special value meaning ‘No transmit’.

Community

OpenEnergyMonitor

Home
Docs
Community
Shop
Search

OpenEnergyMonitor Community

emonGLCD time not updating

Emoncms

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled