I will be releasing LowPowerLabs firmware for the emonTx3 and emonPi soon, so I would advise waiting for that. The advantage being that you can then make use of the acknowledgment and retry mechanism available in the LowPowerLabs implementation.
If I’m involved - whatever update is needed for the ‘old’ emonPi, it won’t happen for a while. I’m far too busy with the emonTx V4 and it’s likely to remain like that for the foreseeable future. You can always use the emonPiCM set of software, which is available for the entire “emon” range (emonTx V2, V3.2, V3.4 but excluding the emonTx V4 and the long-obsolete emonGLCD and NanodeRF), and uses the rfm69nTxLib for transmitting and the (patched) RF69 library in the emonPi for receiving.
Yes it’s my intention to use adapt Roberts emonPiCM firmware to use the LowPowerLabs format. The changes are relatively small and for now @Robert.Wall I don’t plan to add anything relating to this to your work load
I’m a bit delayed on this work though @rupert as I’m trying a finish a couple of emonTx4 documentation related updates, I might have been optimistic on timelines…
Thanks @Robert.Wall, @TrystanLea for the updates. I can understand that you’re both very busy at the moment and don’t have time to work on the ‘old’ emonPi. I’m very grateful for all the current work that you’re both doing. I was just interested in what the plan for the future was.
For information, I have tried, to the best of my knowledge, to put together a table of device vs radio format which may be of interest. My apologies in advance for any errors! The table is a snapshot in time, as things will probably change in the future.
I have included the Mk2 PV Router by @calypso_rae as it is a very popular device.
Having looked, I wouldn’t call it “simultaneous”. There are two parallel receivers, not one receiver switching between formats or receiving either format and correctly recognising and decoding it. I know it’s moot, but it could be misleading without a careful explanation.