<html><head></head><body><div dir="auto">Sounds pretty normal from what I see. It appears that this is *NOT* a true 240v UPS, but rather one that provides two legs of 120v output from two legs of 120 input, and what is seen as "L2" is actually neutral, and the line names are reporting incorrectly. With that in mind, each leg in should be 120v, as well as the outputs, which is exactly what you are seeing.(The fact tht L1 to L3 is 240v really isn't relevant).<br><br>- Tim</div><br><br><div class="gmail_quote"><div dir="auto">On November 11, 2024 6:56:51 PM EST, Greg Troxel via Nut-upsuser <nut-upsuser@alioth-lists.debian.net> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">John Ackermann N8UR via Nut-upsuser<br><nut-upsuser@alioth-lists.debian.net> writes:<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">I am monitoring via the SNMP driver an APC SmartUPS that has split<br>phase (2L + neutral) 240V input and 120/120 volt outputs. The data<br>for the voltages is not what I'm expecting, and I am wondering how I<br>should interpret it.<br></div></blockquote><div dir="auto"><br>Wow, that sounds kind of industrial. Model?<br><br>Is the input an L14-20P? Or equivalent non-twistlock?<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto"> Here is an example from upsc:<br><br> input.L1-L2.voltage: 121<br> input.L2-L3.voltage: 120<br> input.voltage: 121.20<br> output.current: 5.90<br> output.L1-L2.voltage: 119<br> output.L1.current: 5.90<br> output.L2-L3.voltage: 119<br> output.L2.current: 1<br><br> The "input.voltage" value doesn't reflect the 240 volts that is<br> actually being applied. To get that, would I combine the L1-L2 and<br> L2-L3 voltages?<br></div></blockquote><div dir="auto"><br>I would address figuring this out as two steps. One is to see what the<br>device actually sends and what makes sense there. And then to see if<br>NUT is mapping or making synthetic.<br><br>I find it odd for the neutral to be labeled L2, as it seems to be. I<br>would think there would be L1 and L2, both reported as phase-to-neutral.<br>You might see if there is confusion.<br><br>odd for output.L2.current, vs L3, given that voltage seems to be L1/L3<br>vs L2.<br><br>Probably the first voltage is mapped to just 'voltage' and probably it<br>would be better to use the L1/L3 voltage. Similar for output.voltage.<br><br>output.current should probably be average if output.voltage is 240ish.<br>Or better yet <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">Note that the "output.current" value matches the L1 output current,<br>ignoring the L2 current. Perhaps that is a clue that the overall<br>"input" and "output" values are not meaningful in this case?<br></div></blockquote><div dir="auto"><br>yes, and they are perhaps mapped from something else?<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">How should I interpret these values to know the actual input and<br>output voltages and currents?<br></div></blockquote><div dir="auto"><br>You're going to need to put a meter on it and compare to the reports, I<br>suspect.<br><br>First, see if you can get specs, and look at the snmp mib directly and<br>see what you can figure out. Turn up debugging/verbose in nut.<hr>Nut-upsuser mailing list<br>Nut-upsuser@alioth-lists.debian.net<br><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br></div></pre></blockquote></div><div dir="auto"><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>