No inputs after emonpi new SD card and CM firmware update

Hardware emonPi
42

That’s true - but why I don’t know. Trystan never seemed keen to adopt it despite asking me to get the emonPi to do CM - and with JeelibClassic, about 40% of the radio data from ONE remote emonTx got through.
I think all the instructions you need for the ‘Native’ format all round are in the link @rupert gave you above, you need a programmer and a computer, or I believe you could even load all the sources into the emonPi, compile and upload using that - but you’d be doing it essentially by remote control, and I can’t tell you how because I’ve only done it to get the ‘Native’ software into the RFM12Pi and the CM sketch into the emonPi front end, never to go to an emonTx/TH plugged into the Pi. I think you’d either have to drive the Arduino IDE using the command line (even if that’s possible) or use platfromio which I refuse to touch, so I still can’t tell you how.

Nobody’s mentioned that there’s no technical reason why your emonTxs and emonTHs can’t use LPL - though it stands to hammer the battery life in the THs.

What are you using ordinarily to replace the iMac?

43

If you want to stick with Jeelib Native firmware on your emonTx3s and emonTHs I don’t think you have to do anything to them as you say it’s on them already. - ‘just’ put the emonPi back to emonPi CM Jeelib Native firmware.

44

I think that if you can log in to the emonPi using SSH, transfer the compiled CM Jeelib Native firmware hex file onto the emonPi using scp (Linux), you can then use avrdude to program the atmega328 via ttyAMA0. This is a bit like how Setup/Admin/Firmware does it. I don’t know if there are instructions how to do this in the Docs somewhere?

Note that you need a OEM version of avrdude as you need to use GPIO Pin 4 (BCM) as the DTR reset pin. This might be installed already to do the firmware upgrades from the admin page?

Anyone?

45

I just fired it up, but sadly not, nor the Arduino IDE I used to update the emontx3’s. I must have wiped/reinstalled it. It was, after all, a 2007 iMac.

The battery consumption is enough to deter me, thanks.

Not sure I understand the Q, but it is 2 iMacs and a MacBook Pro ago…And I just can’t bear to chuck it out :wink:

Exactly.

I very much appreciate the lead @rupert

Firmware — OpenEnergyMonitor 0.0.1 documentation says

How to compile and upload firmware

It is also possible to compile and upload the emonPi firmware (Instructions need to be added here on how to compile and upload directly on an emonPi).

Although as Rupert points out, the emontx’s and emonth’s should be ok already, it’s just the pi that needs the old library back.

One question I’m still struggling with: I’m 99% certain I never updated the emonpi firmware to anything other than a standard release. So how did I get this Jeelib Native firmware there in the first place?

46

I don’t know either!
If your emonTxs and emonTHs are really using Robert’s CM firmware using Jeelib Native RF format, then you would need the corresponding firmware on the emonPi to receive it.

Just to be sure, have you checked the serial output of an emonTx3 or emonTH to see if it says what the firmware is?

47

That’s a great shout. But how do I do that?

48

From before (topic is getting long!):

49

You will need to make sure that the serial connections and supply voltage on the serial to USB adapter match those of the emonTx3 otherwise ‘sparks may fly and the magic smoke may escape’ …

I am assuming that you know what to do as you say that you’ve done it before …

I don’t want you to damage anything, including your self!

50

Thanks! I did it before via the Arduino IDE, I need to set up the environment again, and my old iMacs aren’t supported any more. Found the cable though :slight_smile:

51

OK, emontx serial output:

emonTx V3.4 EmonLibCM Continuous Monitoring V0.10
OpenEnergyMonitor.org
Loaded EEPROM config
Settings:
Group 210, Node 16, Band 433 MHz
Calibration:
vCal = 262.60
i1Cal = 9090
i1Lead = 4.20
i2Cal = 91.60
i2Lead = 4.20
i3Cal = 91.80
i3Lead = 4.20
i4Cal = 16.80
i4Lead = 5.00
datalog = 9.95
pulses = 1
pulse period = 100
temp_enable = 1
Temperature Sensors found = 0 of 1
Temperature measurement is NOT enabled.
RF whitened
RFM69CW only Node: 16 Freq: 433MHz Group: 210

@Robert.Wall does this identify what library it is using?

52

emonth2 serial output

OpenEnergyMonitor.org
emonTH FW: V324
No EEPROM config
Int RFM...
RFM Started
Node: 24 Freq: 433Mhz Network: 210
Int SI7021..
SI7021 Started, ID: 21
SI7021 t: 21.00
SI7021 h: 60.44
No DS18B20

I’m not sure what V324 means (perhaps 3.2.4?), the current options in Admin/Update/Firmware for emonth2 are both 4.1.5, but only for LPL or JeeLib Classic, not JeeLib Native.

Interestingly, I found this in the documentation:

Available Firmware

emonTh2:

New: Support for three different radio formats is available: JeeLib Classic, JeeLib Native and LowPowerLabs.

So what’s the deal with JeeLib Native? It was clearly offered as a choice at one time, but it seems to have been withdrawn.

I am trawling through GitHub trying to find old versions, but without much success so far.

53

Just to clarify things here and avoid confusion :blush:

emonLibCM release ~Aug 20
Robert’s continuous measurement Arduino Library for the emonTX3.4

emonPiCM release ~Jul 21
Robert’s work on emonPiCM and JeeLib Native RF format is at

emonPi_CM release ~Feb 23
This is the updated emonPi CM measurement firmware using LPL format

54

@PeteF
For the Jeelib Native details, see:

55

But I’d linked to all that way back up the thread!

emonTx V3.4 EmonLibCM Continuous Monitoring V0.10 signifies that it was indeed a development version, I’m reasonably sure that it’s release successor will be this:
EmonTxV34CM_rfm69n.zip (71.4 KB)

emonTH V3.2.4 was a prior version of this:
EmonTH_V2_rfm69n.zip (54.8 KB)
(It is listed in the “Changes”)

I think I tried to explain this above too. Does nobody read what I’m writing?

56

Looking at the emonTx3.4 code for JeeLib Native from Robert, the setup greeting is:
from
emonTx V3.4 single phase: EmonTxV34CM_rfm69n.ino

t#ifdef DEBUG
    Serial.print(F("emonTx V3CM Continuous Monitoring V")); Serial.write(firmware_version);
    Serial.println(F("OpenEnergyMonitor.org"));
  #else
    Serial.println(F("describe:EmonTX3CM"));
  #endif

where firmware_version = 1.0.0 where this is the first release
.
.
.
Looking at the emonTx3.4 code for JeeLib Classic and discrete sampling, the setup greeting is:
from

Serial.begin(115200);
  Serial.print("emonTx V3.4 Discrete Sampling V"); Serial.println(version*0.1);
  Serial.println("OpenEnergyMonitor.org");
  Serial.println(" ");

where the current version is 3.4, although there were previous versions starting at 1.1
.
.
.
Looking at the emonTx3.4 code for continuous monitoring and a choice of JeeLib Classic, JeeLib Native or LPL (by a #define statement) the setup greeting is:
from

 #ifdef DEBUG
    Serial.print(F("emonTx V3.4 Continuous Monitoring V")); Serial.write(firmware_version);
    Serial.println(F("OpenEnergyMonitor.org"));
  #else
    Serial.println(F("describe:EmonTX3CM"));
  #endif

where the current version is 2.4.0, although there were previous versions stating at 1.0.0

Hope I have this correct as it’s a bit mind boggling!

57

@PeteF
For your emonTx3 greeting you have:

which doesn’t exactly match any of the above, especially the V0.10
So I don’t know if we’re any further forward!

58

@Robert.Wall
Sorry for that, I was just trying to get it clear in my mind …

59

Edited: No inputs after emonpi new SD card and CM firmware update - #55 by Robert.Wall

60

@PeteF
Thanks Robert, for confirming that PeteF’s emonTx3 and emonTh are running Jeelib Native firmware.

61

Sorry @Robert.Wall, I did read it and understood that no further development would be done on JeeLib native, which is entirely acceptable. What I find less so is that my (I think) ‘responsibly’ doing updates to emonSD and emonsms leads one (me) into a non-working system and an apparent cul-de-sac .

The emontx3CM V0.10 would indeed have been a development version, which I willingly tested for you. It worked perfectly, without any significant dropouts for - well - ever. I can’t remember the last time I had to reboot a tx3. I am certain that the data format didn’t change for the production version, so I saw no need to update it. It just worked.

But surely it’s not the emontx3 or emonth that’s the problem? The ONLY thing I have essentially changed to a system that has been happily and reliably working for several years is the emonpi firmware. All I would like to do is have the opportunity to get it back.