Incorrect reporting in native interface

Ask questions about the GEM here.
Post Reply
VanMak
Posts: 9
Joined: Sun Dec 05, 2021 10:55 pm

Incorrect reporting in native interface

Post by VanMak » Tue Feb 15, 2022 11:33 am

I've had my GEM installed with most channels receiving data for a few months now though I haven't been doing anything with that data as I wait for the HomeAssistant integration to come inline with the new Energy dashboard. I have however been looking at the native interface from time to time, the one hosted on the GEM itself, listening on port 8000 which is rudimentary at best. My question is around the "Live Data" piece. On one specific circuit, a 40A GFCI that feeds my hot tub, I've got a CT on either leg of the split phase feeding the tub. One CT is facing inwards while the other is facing outwards, both are donut-style and both black leads go to pin 2 and both white leads go to pin 3. The circuit is not listed as 240V as I am using two CTs, per the instructions:
Chan_CT.png
Chan_CT.png (127.49 KiB) Viewed 840 times
When I pull up the live data stream however, the two values presented are only accurate if the voltage was 120V, here are three readings with various states of power consumption:
Screen Shot 2022-02-15 at 8.29.58 AM.png
Screen Shot 2022-02-15 at 8.29.58 AM.png (65.16 KiB) Viewed 840 times
Should I have the 240V variable set to 1, contrary to the instructions? Do I have the CTs wired correctly or should one of them be flipped?

Thanks in advance.
ben
Site Admin
Posts: 4262
Joined: Fri Jun 04, 2010 9:39 am

Re: Incorrect reporting in native interface

Post by ben » Tue Feb 15, 2022 11:55 am

I'll see if we can change the label for future units. If you're monitoring both legs you don't need the X2 setting enabled.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
VanMak
Posts: 9
Joined: Sun Dec 05, 2021 10:55 pm

Re: Incorrect reporting in native interface

Post by VanMak » Tue Feb 15, 2022 1:52 pm

ben wrote:
Tue Feb 15, 2022 11:55 am
I'll see if we can change the label for future units. If you're monitoring both legs you don't need the X2 setting enabled.
Hi Ben,

Thanks for the response. Are you saying that my setup sounds correct then? The live data is still wrong however:

W/V=A, 8131/120=67.8A (ignoring PF, the value of 72.16A is close enough.)

This is a 240V circuit so it should be showing 33.9A but the GEM has no way of knowing it's 240V. If I change 240V to "1", contrary to the instructions does that only affect the math that produces the data presented? If so, it seems as though I should indicate that CT is 240.
ben
Site Admin
Posts: 4262
Joined: Fri Jun 04, 2010 9:39 am

Re: Incorrect reporting in native interface

Post by ben » Tue Feb 15, 2022 2:33 pm

VanMak wrote:
Tue Feb 15, 2022 1:52 pm
ben wrote:
Tue Feb 15, 2022 11:55 am
I'll see if we can change the label for future units. If you're monitoring both legs you don't need the X2 setting enabled.
Hi Ben,

Thanks for the response. Are you saying that my setup sounds correct then? The live data is still wrong however:

W/V=A, 8131/120=67.8A (ignoring PF, the value of 72.16A is close enough.)

This is a 240V circuit so it should be showing 33.9A but the GEM has no way of knowing it's 240V. If I change 240V to "1", contrary to the instructions does that only affect the math that produces the data presented? If so, it seems as though I should indicate that CT is 240.
Yeah, we're monitoring at 120V so the amperage from both sides is summed.

If you increase the CT Range by 1 and enable the X2 setting the amperage should show half after. CT Range halves the scaling.
Ben
Brultech Research Inc.
E: ben(at)brultech.com
Post Reply