Hi folks,
I have just installed my brand new emonTx4 setup and I have one persistent data anomaly that I’m not sure what (if anything) to do with.
First, here’s the setup:
- emonTx4 + emonVs + emonBase bundle (order #29921)
- emonTx4 firmware updated to v1.5.4, though if you can tell me where to look to double-check that, I can’t see it listed anywhere in the emonCMS UI
- UK plug plus an adaptor for an Australian socket - I understand AU and UK power are very similar
- Single phase
- CT1 50A (total home), CT2 50A (oven), CT3-CT6 20A (other individual circuits)
- Input configuration using the emonTx4 device template
When I first installed it, I accidentally had the oven sensor (CT2) around the wrong way, so had negative power readings from it. I have since reversed the direction of the sensor and trimmed all feeds’ data up to a point after the orientation was fixed. All of the P* and E* numbers now look plausible, except E2.
E2 is reading -65.43kWh. The EmonHub log is also giving the value as -65430, so I guess this means it’s the hardware that’s reporting the large negative number? (Also, I notice that value is not far off 2^16, though it’s not very close either…)
2023-01-09 08:55:48,560 INFO SPI Packet received 52 bytes
2023-01-09 08:55:48,560 DEBUG SPI 271 NEW FRAME :
2023-01-09 08:55:48,562 DEBUG SPI 271 Timestamp : 1673254548.560673
2023-01-09 08:55:48,562 DEBUG SPI 271 From Node : 17
2023-01-09 08:55:48,563 DEBUG SPI 271 Values : [275, 234.06, 825, 0, 563, 141, 2, 110, 7517, -65430, 2208, 3263, 126, 1692, 0, 0, 0, 4294967295, 0, 0.0]
2023-01-09 08:55:48,563 DEBUG SPI 271 RSSI : -27
My best guess is that initially collecting some negative power data on CT2 has caused this, but I can’t work out how to reset it and start again.
Is my best bet to just include a “+65430” processing step on the input, throw away any older E2 data, and be done with it? Do you have any other recommendations?
Thanks,
Suzy