-
-
Notifications
You must be signed in to change notification settings - Fork 427
CyberPower CP900EPFCLCD showing incorrect output voltage #581
Copy link
Copy link
Closed
Labels
CyberPower (CPS)Incorrect or missing readingsOn some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)USBUSB-HID encoding/LogMin/LogMaxIssues and solutions (PRs) specifically about incorrect values in bitstreamIssues and solutions (PRs) specifically about incorrect values in bitstream
Milestone
Metadata
Metadata
Assignees
Labels
CyberPower (CPS)Incorrect or missing readingsOn some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)USBUSB-HID encoding/LogMin/LogMaxIssues and solutions (PRs) specifically about incorrect values in bitstreamIssues and solutions (PRs) specifically about incorrect values in bitstream
Using the usbhid-ups driver my CP900EPFCLCD reports the output voltage as being between 260 and 270 - though it sits at 260 most of the time. The input voltage averages around 240 as would be expected.
Running the driver directly (/usr/local/libexec/nut/usbhid-ups -DDD -a ups) results in the following voltage information:
0.010678 Report[get]: (3 bytes) => 0f ef 00
0.010687 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 239
...
0.011178 Report[get]: (3 bytes) => 12 ef 00
0.011188 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: 260
I'm not entirely sure what to make of this, though it would appear that ef (239) is somehow being interpreted as 260?
Extra note: Configured through FreeNAS's UI and set to CP1000PFCLCD as it's the closest option - not sure if this makes any difference.