My serially connected emonTX seems to have given up reading energy on CT1
The PiZ had stopped for some reason (no web or SSH access), though it looks like the data was still flowing, so I pulled the DC plug on the TX (as the Pi is powered via the TX UART).
On reboot no power readings from the emonTX. Tried to reboot a second time this time removing the AC as well and still no readings - I do get messages though.
pi@emon-serial:~ $ miniterm --rtscts /dev/ttyAMA0 115200
--- Miniterm on /dev/ttyAMA0 115200,8,N,1 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
emonTx V3.4 EmonLibCM Continuous Monitoring V1.70
OpenEnergyMonitor.org
Loaded EEPROM config
Settings:
Group 210, Node 15, Band 433 MHz
Calibration:
vCal = 268.97
i1Cal = 90.90
i1Lead = 4.20
i2Cal = 90.90
i2Lead = 4.20
i3Cal = 90.90
i3Lead = 4.20
i4Cal = 16.67
i4Lead = 6.00
datalog = 10.01
pulses = 1
pulse period = 100
temp_enable = 1
Temperature Sensors found = 0 of 1
Temperature measurement is NOT enabled.
RF off
POST.....wait 10s
'+++' then [Enter] for config mode
CT1 detected, i1Cal:90.90
AC present
MSG:1,Vrms:247.33,P1:0,E1:0,pulse:1
MSG:2,Vrms:247.25,P1:0,E1:0,pulse:1
MSG:3,Vrms:247.19,P1:0,E1:0,pulse:1
MSG:4,Vrms:247.27,P1:0,E1:0,pulse:1
MSG:5,Vrms:247.30,P1:0,E1:0,pulse:1
--- exit ---
I then wondered if the CT channel had given up so powered down and switched to CT2.
pi@emon-serial:~ $ miniterm --rtscts /dev/ttyAMA0 115200
--- Miniterm on /dev/ttyAMA0 115200,8,N,1 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
emonTx V3.4 EmonLibCM Continuous Monitoring V1.70
OpenEnergyMonitor.org
Loaded EEPROM config
Settings:
Group 210, Node 15, Band 433 MHz
Calibration:
vCal = 268.97
i1Cal = 90.90
i1Lead = 4.20
i2Cal = 90.90
i2Lead = 4.20
i3Cal = 90.90
i3Lead = 4.20
i4Cal = 16.67
i4Lead = 6.00
datalog = 10.01
pulses = 1
pulse period = 100
temp_enable = 1
Temperature Sensors found = 0 of 1
Temperature measurement is NOT enabled.
RF off
POST.....wait 10s
'+++' then [Enter] for config mode
CT2 detected, i2Cal:90.90
AC present
MSG:1,Vrms:247.25,P2:417,E2:1,pulse:1
MSG:2,Vrms:247.29,P2:416,E2:2,pulse:1
and there we have it - data again.
I then though ‘I wonder if CT1 will now work’ - go back to CT1 and I have data again on that channel. Weird.
Any suggestions @Robert.Wall @TrystanLea as to why? Nothing in the logs. Could the hard power down cause the Channel to do this?
Why would unplugging the CT and plugging it back in make it work?