Nut upsuser - Dec 2016 - Incorrect scale on values for TRIPPLITE UPS

I?m setting up a new system and installed a new UPS with nut.
System Specifics:

OS: Debian 3.16.36
Nut version: 2.7.2
Install method: apt-get
Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver

Problem:
The output from upsc has a few incorrect values.  They appear to be a matter of
scale.

root at server:/etc/nut# upsc tripplite at localhost
Init SSL without certificate database
battery.charge: 97
battery.charge.low: 10
battery.charge.warning: 30
battery.runtime: 7354
battery.type: PbAC
battery.voltage: 0.0  ? Wrong
battery.voltage.nominal: 24.0
device.mfr: Tripp Lite
device.model: TRIPP LITE UPS
device.serial: 2630DVLSM872100097
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.7.2
driver.version.data: TrippLite HID 0.81
driver.version.internal: 0.38
input.frequency: 6020.0   ? Wrong
input.transfer.high: 150.0
input.transfer.low: 92.0
input.voltage: 0.0  ? Wrong
input.voltage.nominal: 120
output.current: 60.00
output.frequency: 6020.0  ? Wrong
output.frequency.nominal: 60
output.voltage: 0.0  ? Wrong
output.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 9
ups.mfr: Tripp Lite
ups.model: TRIPP LITE UPS
ups.power: 64.0
ups.power.nominal: 1300
ups.productid: 3016
ups.serial: 2630DVLSM872100097
ups.status: OL CHRG
ups.timer.reboot: 65535
ups.timer.shutdown: 65535
ups.timer.start: 65535
ups.vendorid: 09ae
ups.watchdog.status: 0

The debug output of the driver is quite long, so here are the relevant lines.
Note how the frequency values have a value of 6020 which should probably be
60.20 and the voltages are, for example .001214 which should be 121.4

   0.406677     Checking device (09AE/3016) (001/002)
   0.487716     - VendorID: 09ae
   0.487738     - ProductID: 3016
   0.487755     - Manufacturer: Tripp Lite
   0.487770     - Product: TRIPP LITE UPS
   0.487786     - Serial Number: 2630DVLSM872100097
   0.487801     - Bus: 001
   0.487816     Trying to match device
   0.487835     Device matches
   0.495723     HID descriptor length 878
   0.700727     Report Descriptor size = 878
   0.701027     Using subdriver: TrippLite HID 0.81
   0.755724     Path: UPS.PowerSummary.Input.ConfigVoltage, Type: Feature,
ReportID: 0x30, Offset: 0, Size: 8, Value: 120
   0.759722     Path: UPS.PowerSummary.Input.Voltage, Type: Feature, ReportID:
0x31, Offset: 0, Size: 16, Value: 0.001214
   0.856189     Path: UPS.Flow.ConfigVoltage, Type: Feature, ReportID: 0x01,
Offset: 0, Size: 8, Value: 120
   0.869186     Path: UPS.Flow.ConfigFrequency, Type: Feature, ReportID: 0x02,
Offset: 0, Size: 8, Value: 60
   0.878190     Path: UPS.Flow.ConfigApparentPower, Type: Feature, ReportID:
0x03, Offset: 0, Size: 16, Value: 1300
   0.882185     Path: UPS.PowerConverter.Input.Voltage, Type: Feature, ReportID:
0x18, Offset: 0, Size: 16, Value: 0.001214
   0.886188     Path: UPS.PowerConverter.Input.Frequency, Type: Feature,
ReportID: 0x19, Offset: 0, Size: 16, Value: 6020
   0.890185     Path: UPS.PowerConverter.Output.Voltage, Type: Feature,
ReportID: 0x1b, Offset: 0, Size: 16, Value: 0.00122
   0.894188     Path: UPS.PowerConverter.Output.Frequency, Type: Feature,
ReportID: 0x1c, Offset: 0, Size: 16, Value: 6020
   0.898189     Path: UPS.PowerConverter.Output.Current, Type: Feature,
ReportID: 0x46, Offset: 0, Size: 16, Value: 60
   0.902185     Path: UPS.PowerConverter.Output.ActivePower, Type: Feature,
ReportID: 0x47, Offset: 0, Size: 16, Value: 64
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161207/b61ec404/attachment.html>

On Dec 7, 2016, at 1:19 AM, <dwilliss at inebraska.com>
wrote:
> 
> OS: Debian 3.16.36
> Nut version: 2.7.2
> Install method: apt-get
> Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver
>  
> Problem:
> The output from upsc has a few incorrect values.  They appear to be a
matter of scale.
> 
Thanks for the detailed report.

Based on the version number above, it looks like you are using the Debian
"jessie" release. In "stretch" (the next release) is NUT
2.7.4, which includes the following commit:

  
https://github.com/networkupstools/nut/commit/ee25d33f19b9eb74bdbf94590975b3f954afe4b3

Although your unit is a SMART1300LCDT rather than SMART1500LCDT, it has the same
USB product ID (3016), so the scaling code added by that patch should work on
your system.

There are several ways to get the new version of NUT, but the answer provided
here seems to work in a quick test on a local Debian jessie container:

   http://unix.stackexchange.com/a/253866

Since NUT is in the main part of the package pool, you can follow that
suggestion to the letter. Currently, it says to add this to
/etc/apt/sources.list (although you could also create a new *.list file in
/etc/apt/sources.list.d):

   deb http://ftp.debian.org/debian stretch main

And create /etc/apt/apt.conf.d/default-release with the following contents:

   APT::Default-Release "jessie";

Then, run "apt-get update". Running "apt-cache policy
nut-server" should show something like this:

# apt-cache policy nut-server
nut-server:
  Installed: 2.7.2-4
  Candidate: 2.7.2-4
  Version table:
     2.7.4-4 0
        500 http://ftp.debian.org/debian/ stretch/main amd64 Packages
     2.7.2-4 0
        990 http://ftp.debian.org/debian/ jessie/main amd64 Packages

Since the "jessie" version has a higher priority (990), the
"stretch" packages would not be installed by default, but you can pass
a flag to apt-get to override that:

   apt-get -t stretch install nut-client nut-server

Make a note to remove the default-release file when you upgrade that system to
"stretch".

Reliability of the USB connection has been an issue for the SMART1500LCDT series
(the UPS provides power and updates the LCD status, but frequently disappears
from the USB bus) on newer motherboards (typically those capable of USB 3.0).
The investigation is ongoing, but we may be closer to figuring out why:

   https://github.com/networkupstools/nut/issues/300#issuecomment-265324133

At the moment, we do not have a .deb-based solution (other than for Ubuntu), but
it is possible to recompile NUT, and we do plan to roll the fix into a future
version of NUT.

Let us know how it goes.