Hi all,
I updated my emonPi2 earlier this week - full update and firmware (DB, single phase, 6 CTs).
I have since come to realise that it’s recording approximately twice the kW that is actually being consumed; and more than is being recorded separately as being imported! So clearly it’s the emonPi2 that is incorrect.
I’ve tried another full update and the CM firmware but no change.
The unit was left in place during the updates - nothing unplugged and put back incorrectly etc.
Any ideas?
Have you checked that the original C.T. calibrations have been retained? Each channel should start at the nominal rating of the c.t. connected to it, i.e. “50” for a 50 A c.t. If it is 100 for a 50 A c.t, there’s your answer. It’s quite legal to adjust the value by a small amount (only a few percent maximum) to cater for individual components being not quite the nominal value. It certainly should not be out by a factor of two for any other reason.
Setup →Admin → Serial Config is where you need to be.
That was it - thanks!
The real question is, why was your old configuration (emonhub.conf) not retained? Did you “update” it or start again from scratch? If you had changed anything from the original defaults (which I think you must have done), then I think the settings should have saved for you automatically (but I might be wrong), and that change should not have been overwritten when you updated. If you started from scratch, you get the factory default settings.
I don’t have an emonPi2 so I can’t test all the possible permutations to try to discover a bug.
I just ran the updates from the admin pages.
Mine is no. 11 of a batch of specially configured early emonPi2s for a heat pump trial with Nesta.
When I received it I just plugged it in and it beamed its data to a preconfigured emonCMS.org account.
I hardly touched it (except for adding some DS18B20s and interfacing the data to my own internal emonCMS).
The trial has been over for a couple of years now so I thought I’d make it my main device although I think it won’t be able to see 2 of my older emonTH’s but I can live without them!
The key question is the radio module. If the two older ones have RFM12Bs, then you can’t use them, not without a separate emonBase or something like @borpin came up with a while ago to handle them - I can’t remember now exactly what he suggested or what it involved.
It would be easy enough to make the RFM12B transmit a message that is part-compatible with LPL and would be received by it, but as far as I know there’s not the processing power/memory remaining in the emonTH to do the encryption part. That could be overcome by turning off encryption on your emonBase and everything else.
They’re already talking to an old emonBase so I think I will just keep that and interface the data to the emonPi2.