Folks, I've asked this question on the FreeNAS forum but there are no ideas there as it looks like it's a NUT issue. Original question: https://forums.freenas.org/index.php?threads/apc-ups-reporting-wrong-input-voltage.60888/ the nut driver is reporting the wrong input voltage. I am in the UK, 230V but it's reporting circa 108. If I connect it to the laptop and run powerchute it reports the correct voltage. AFAIK, the driver is the correct one. Anything I can try to get this corrected? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20180303/94d985e2/attachment.html>
[please use reply-all to CC the list, thanks!] On Mar 3, 2018, at 11:42 AM, Crispin Proctor wrote:> > Folks, > > I've asked this question on the FreeNAS forum but there are no ideas there as it looks like it's a NUT issue. > > Original question: https://forums.freenas.org/index.php?threads/apc-ups-reporting-wrong-input-voltage.60888/ > > the nut driver is reporting the wrong input voltage. I am in the UK, 230V but it's reporting circa 108. > > If I connect it to the laptop and run powerchute it reports the correct voltage. > > AFAIK, the driver is the correct one.The short version is that you shouldn't have to worry about the reported voltages affecting shutdowns, but I would still test it anyway (using a power strip or other switch to keep the UPS grounded while cutting the mains). There is a single bit coming back from the UPS for each of the OL/OB and LB states, and the UPS makes the decision as to when it considers its battery to be low. device.mfr: American Power Conversion device.model: Back-UPS XS 1400U device.serial: 3B1519X22971 ... driver.version: 2.7.4 driver.version.data: APC HID 0.96 driver.version.internal: 0.41 ... input.voltage: 108.0 input.voltage.nominal: 102 ^^^ Note that the nominal voltage is also off. This means it is most likely a scaling issue in the NUT code, but it derives those numbers from data provided by the UPS (which is frequently formatted incorrectly). If you stop the UPS service on the NAS, and run the following as root, what do you get in the log file? (You can press Ctrl-C to kill it after 30-60 seconds - it will loop.) /usr/local/libexec/nut -a ups -DDD 2>&1 | tee /tmp/APC-230V-log.txt (^C) gzip /tmp/APC-230V-log.txt
On Mar 5, 2018, at 4:41 PM, Crispin Proctor <crispin.proctor at gmail.com> wrote:> > The UPS functions as it should - it works when there is no power but cannot test brownout or anything else.Okay.> > I ran the command you put but it fails to log anything to file. Not sure why.I'm assuming a Bourne-compatible shell like bash or zsh - can't remember what it should be for csh/tcsh. Be sure there aren't spaces between "2>&1".> > Here is the output though - hope there is enough here. > 4.344452 Report[get]: (2 bytes) => 13 01 > 4.344475 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 1 > 4.348575 Report[get]: (3 bytes) => 14 00 00 > 4.348596 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 0 > 4.348611 Report[buf]: (4 bytes) => 06 00 00 08 > 4.348622 Path: UPS.PowerSummary.APCStatusFlag, Type: Feature, ReportID: 0x06, Offset: 16, Size: 8, Value: 8 > 6.329754 upsdrv_updateinfo... >It's missing the report descriptor dump (part of the first few seconds) and the lines corresponding to voltages.