Moving existing installation to new native RFM69 format?

Ok so I have a EmonPi running successfully since 2015, with EmonTX3 sending data as well.

I have read the posts from Robert on the new format, and it seems that it will allow the EmonPi to do CM like the EmonTX3?

Is it as simple as flashing the EmonPi and the EmonTX over to the new RFM69 format so they can all talk to each other - is this now the default going forward?

I am adding an EmonTX4 this morning, but its USB connected to the Pi and I ordered with the legacy FW anyway on it - so does not really affect the main topic of the EmonPi and EmonTX3 moving to new radio format.

Stability is more important to me than the EmonPi doing CM, so if its more robust to leave it alone I will just retain the old format radio. If there are advantages to making the change I can switch over while I am doing changes.

Thanks for any pointers/tips from those that have made the change.

As the release post says, if you don’t want CM on your emonPi, there’s no need to change. If you do, then you must use the native message format because this allows almost all of the radio reception processing to be done inside the RFM69CW. Running emonLibCM on an emonPi with JeelIb ‘Classic’ resulted in about 15 - 20% (from memory) success rate for data from a single emonTx.

Do you really think I’d have released the software if it didn’t work???

Hi Robert, not questioning in anyway if it works or the quality of the implementation!

I read some posts that say after reboot the FW is reset to the old version etc - but of course I am trying to absorb a few years of changes and things change over time - I guess phrased better if I write the new library format to the EmonPi and change my EmonTX’s over is this bleeding edge or now “standard”?

CM on the EmonPi would be favourable, as it has the house CU and the solar on it at present.

Hello Paul, just a note to say that there are 3 formats, in order of date of firmware release:

  1. JeeLib Classic (shipped as standard on all our units up to November this year)
  2. JeeLib Native (thanks to Robert Wall, developed to enable continuous monitoring on the emonPi)
  3. LowPowerLabs (latest available with the emonTx4, adopted to make use of acknowledgment and retry mechanism).

Robert posted a useful comparison of these here: Emon Tx V4 and 433MHz Radio Formats
and there’s more on them in the docs too: Technical Guide — OpenEnergyMonitor 0.0.1 documentation

JeeLib Native and LowPowerLabs are very similar in that they use the RFM69 native functionality - but they are not compatible due to different settings. I will be releasing emonPi and emonTx3 firmware that works with the LowPowerLabs format soon, so I might advise waiting for that.

Ok thanks, that helps!

So I have classic on my vintage emonpi, Robert’s CM firmware is with Jeelib native? And the Lowpowerlabs is just for emontx4 at present and new hw, I would not want to run that yet as there is no emontx3 fw for that radio format, I think I got it now.

I will leave my EmonPi alone, I ordered my EmonTx4 from the shop with the legacy fw so it’s reporting OK to the emonpi over radio (although I will direct usb it to power the emontx4).

1 Like