EmonPI periodically stops working. Alays managed to get back on track with hard reset... 'till now

[rupert]

@CrisPastore
I don’t think I can help with the emonPi (presumably V.1) stopping working, but seeing

@CrisPastore

I dunno if helps but the built in display shows _ _ _on both Power 1 and Power 2, which makes me thinking of a faulty EmonPI board (probaly the UART sending data to the Raspberry PI)
BTW did you noticed the /dev/ttyAMA0 communication error? Doesn’t this sounds as an HW error to you? BTW I tried to dial down the communication speed to 9600 bps, gettin the same error.

reminded me that you might want to look at the topic

Should I update Emon Pi firmware to CM, and how?

I have just an emonpi, no other kit, so I don’t use radio to transfer info. I regularly update the software on the pi via the admin page on its website. I do a “full update”. I recently noticed that this doesn’t update the firmware, so after a bit of reading, I decided to update to the Continuous monitoring version, chosing port ttyAMA0, hardware emonpi, radio format RFM69 Low power labs, Firmware …continuous monitoring… V1.1.4. The update process shows on screen, then it appears to load an…

When the CM (continuous measurement) method was introduced instead of the previous DS (discrete sampling) method some time ago, the format for the radio transmissions was changed from the Jeelib format to the LPL (Low Power Labs) format. This required new firmware in the emonPi board for the CM and LPL updates.

When this happened there were problems with incorrect results showing oh the emonPi LCD display, so there may not be a hardware problem with your emonPi board.

From memory, the other things that changed in the CM/LPL update were

1. the /dev/ttyAMA0 baud rate increased from 38400 to 115200
2. the emonHub config for the emonPi changed as the CM/LPL format included a message number at the beginning of the data and extra pulse2count,E1,E2 measurements
3. the CM node name for the emonPi in emonHub was originally suggested as emonpiCM. As the original DS node name was emonpi, this meant that the CM data did not appear in the original inputs, unless the CM node name was changed back to emonpi.

So you might want to check what updates you’ve done.

Don’t know if this helps! Apologies in advance for any mistakes!