emonPi Problem after emonPi_CM/LPL firmware upgrade

[rupert]

An update …

My emonPi stopped logging data from my emonTx4 (node 14) again on July 9. However it continued logging emonPi data (node 5) from the emonPi Shield, so communication between the Shield and the Pi over ttyAMA0 was still working.

Looking at the emonHub log, there was nothing there from the emonTx4 (node 14), but there were entries from the emonPi (node 5).

After noticing in a helpful post from @Robert.Wall in the topic:

EmonTX 3 update to continuous Monitoring

This is very likely the case. Node 15 is the new default. This is one way to do it. I strongly suggest you stay with the Arduino IDE and not attempt to use platformio. The ‘obvious’ way would be to download the sketch into your laptop with the Arduino IDE on it, edit the default Node ID in the sketch and then compile and upload the changed sketch. You’ll also need to download and install some libraries in order to be able to compile the sketch. All the instructions are in ‘Docs’ here: Using t…

that there was a serial monitor in the EmonCMS Admin page, I stopped emonhub and had a look at what was appearing on ttyAMA0, at 115200 bps. This was while the emonTx4 data was not apparently being logged. The result was:

service-runner trigger sent for '/var/www/emoncms/scripts/serialmonitor/start.sh 115200 /dev/ttyAMA0'
|emonPiCM V1.1.4
|OpenEnergyMonitor.org
|Radio format: LowPowerLabs
LCD found i2c 0x27
OK 5 1 0 0 0 0 0 0 0 0 0 189 99 214 8 48 117 48 117 48 117 48 117 48 117 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
OK 14 126 53 8 0 132 97 80 1 1 0 1 0 0 0 0 0 1 0 23 48 0 0 229 2 0 0 205 4 0 0 242 2 0 0 144 22 12 0 12 147 19 0 114 8 177 8 114 8 152 194 3 0 (-68)
OK 5 2 0 0 0 0 0 0 0 0 0 200 99 214 8 48 117 48 117 48 117 48 117 48 117 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
OK 14 127 53 8 0 130 97 80 1 1 0 1 0 0 0 0 0 2 0 24 48 0 0 229 2 0 0 205 4 0 0 242 2 0 0 144 22 12 0 12 147 19 0 114 8 177 8 114 8 153 194 3 0 (-78)
OK 5 3 0 0 0 0 0 0 0 0 0 160 99 214 8 48 117 48 117 48 117 48 117 48 117 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
OK 14 128 53 8 0 110 97 80 1 1 0 1 0 0 0 0 0 2 0 25 48 0 0 229 2 0 0 205 4 0 0 242 2 0 0 144 22 12 0 12 147 19 0 102 8 177 8 114 8 154 194 3 0 (-67) 

So the data was present from node 5 (the emonPi Shield) as expected, but also from node 14, my emonTx4 - but was not being logged.

And when I restarted emonHub, the data from the emonTx4 was now being logged again …

The graph below shows the two feeds for Vrms from the emonPi and emonTx4. Note at the extreme right that the emonTx4 feed starts working again after emonHub has been restarted

Are there any clues here as to what’s going on?

Is the emonPi Shield correctly receiving the emonTx4 data all the time, and transferring it to the Pi over ttyAMA0, where it is being lost?