Apologies for a possibly premature question ahead of proper issue investigation & calibration on my part. I've pondered over this for a few days, but I haven't wanted to break a system that's starting to work, and I can't see this particular issue has been raised elsewhere in the forums.
I have successfully made an initial basic EmonTx setup posting to emoncms.org but the mains voltage feed shows c328VAC, value = 3283 in Inputs.
Switching off the supply to the AC adapter (as I've just done) doesn't remove the feed so I'm obviously not actually seeing the mains voltage?
Before I properly start to investigate this issue and calibrate does anyone have any suggestion as to what I am seeing in my Inputs / Feeds / Dashboard?
Looking at my inverter upload to pvoutput.org that my actual mains voltage varied today in the range 243 - 250VAC.
Thank you,
Steve
Setup
UK domestic installation
EmonTx v2.2 standard build, RFM12B / Pi, Raspberry Pi
emonTx_CT123_Voltage sketch from cJuly / Aug '13. No calibration or other changes to sketch have been attempted yet
1 CT plugged into CT1 port
CT ports 2 & 3 turned on in sketch but no CTs and not yet in use.
AC/AC adaptor (not from shop) providing c11.2VAC on mains of c247VAC measured last week
Re: RRSOLVED EmonTx CT123 Voltage - Fixed, high voltage shown even when ac/ac adapter is off
Hi Steve, well done for getting system up and running.
Have you got a multimeter to hand which can measure ac voltage? If so could you measure the output of the ac adapter. This should be around 11v ac unloaded at 230v on the input
Re: RRSOLVED EmonTx CT123 Voltage - Fixed, high voltage shown even when ac/ac adapter is off
AC/AC adaptor (not from shop) providing c11.2VAC on mains of c247VAC measured last week
Hi Glyn,
Even with the adapter powered off I see a value of 3283 in my inputs.
Regards,
Steve
Re: RRSOLVED EmonTx CT123 Voltage - Fixed, high voltage shown even when ac/ac adapter is off
Reloading or loading the emontx_ct123_voltage sketch with the latest libraries and turning off the CTs 2 & 3 has resolved my issue. I suspect though that somewhere along the way I caused this issue as it was back in the summer when I first tested the board then put it away until recently when I had more time. I'll get on to calibration now.
Thank you,
Steve