CPS wrong output voltage

[pedro042]

I recently bought OR1500ERM1U and I"m very happy it's supported by Nut. Thanks a lot!

I see a minor issue in upsc:
input.voltage: 232.0
input.voltage.nominal: 230
output.voltage: 253.0

The value 253 in output.voltage is actually high transfer value. Probably easy to fix.

Version 2.7.4-5004-g1f143e5e (recemt/current git branch master)

[jimklimov]

Nice to hear it (mostly) works for you :)

As for the issue at hand, can you please share a bit more about the configuration (which driver, some debug logs per troubleshooting hints in the documentation)?

So far I'd have two guesses: we are either mapping a wrong value indeed (whether our community's mistake, or firmware differences over time so "they" report a data point at a different node than the one which worked before), or in case of USB connections it may be or not be an issue with LogMin/LogMax processing per #1040 and related trail.

[pedro042]

Of course, here is log, ups.conf and udev rules
ups.zip
You're right, it's maybe firmware issue.

I'm not alone - for example #1191 - nominal voltage 120, output voltage 265 or #520 - 4 years old comment:

input.transfer.high: 139
input.transfer.low: 88
input.voltage: 116.0
input.voltage.nominal: 120
output.voltage: 140.0

But it differs - transfer high is 139 and output 140

[1ockwood]

FWIW, I'm seeing this as well on a CP1500PFCLCD. The reported output voltage fluctuates around 136v. The display on the UPS itself, however, reports the expected output voltage ~120v. Let me know if there's any other info I can provide that may be helpful.

device.mfr: CPS
device.model: CP1500PFCLCDa
device.type: ups
driver.name: usbhid-ups
driver.version: 2.7.4
driver.version.data: CyberPower HID 0.4
driver.version.internal: 0.41
input.voltage: 120.0
input.voltage.nominal: 120
output.voltage: 136.0
ups.mfr: CPS
ups.model: CP1500PFCLCDa
ups.productid: 0601
ups.vendorid: 0764

[pedro042]

Hi,

I' think your reported output voltage doesn't fluctuate. It's (reported) constantly 136V or, sometimes, zero. It's probably some issue in your monitoring software, IMO.

Your UPS display is right. Your input voltage is 120, your output voltage is 120V too. If this type of UPS ("line interactive") is not running on battery, the current simply pass thru; output is the same as input. The UPS start acting when input voltage is bellow low transfer setting or above high transfer setting or if there is an power outage (zero input power is, of course, bellow low transfer setting).
Output voltage can differ from input voltage only if line interactive UPS is running on battery.
Here is important part of my debug log:

0.009244     [D1] Path: UPS.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 0, Size: 16, Value: 207
0.009253     [D1] Path: UPS.Output.LowVoltageTransfer, Type: Input, ReportID: 0x10, Offset: 0, Size: 16, Value: 207
0.009258     [D1] Path: UPS.Output.HighVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 16, Size: 16, Value: 253
0.009261     [D1] Path: UPS.**Output.HighVoltageTransfer**, Type: Input, **ReportID: 0x10, Offset: 16**, Size: 16, Value: **253**
0.009452     [D1] Path: UPS.**Output.Voltage**, Type: Feature, **ReportID: 0x12, Offset: 0**, Size: 16, Value: **253**

On line 4, there is ReportID 0x10 offset 16 - HighVoltageTransfer 253
On line 5, ReportID 12, offset 0, Output Voltage 253
Based on the debug - I'm not sure what ReportID exactly is, does NUT really read diferrent data and UPS reports the same value 253 or NUT actually reads the same data? Or ReportID 0x10 offset 16 is the same part of data as ReportID 12 offset 0 ?

Someone tried PowerPanel? What reports PowerPanel?

[jes1417]

I see this is as well and have seen it since the UPS was put in over a year ago.

and from the server

Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 525
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 13.6
battery.voltage.nominal: 12
device.mfr: CPS
device.model: OR500LCDRM1Ua
device.serial: GA4JW2000855
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 15
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: CyberPower HID 0.4
driver.version.internal: 0.41
input.voltage: 118.0
input.voltage.nominal: 120
output.voltage: 135.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 63
ups.mfr: CPS
ups.model: OR500LCDRM1Ua
ups.productid: 0601
ups.realpower.nominal: 300
ups.serial: GA4JW2000855
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: -60
ups.vendorid: 0764

[jimklimov]

Just in case, would you have a chance to build a recent NUT source from github and check in-situ if the current drivers also mis-report that? (and what is the expected value range for you - circa 220-240V or 110-127V?) Thanks.

…

and from the server Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 525 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.6 battery.voltage.nominal: 12 device.mfr: CPS device.model: OR500LCDRM1Ua device.serial: GA4JW2000855 device.type: upsdriver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 15 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.41 input.voltage: 118.0 input.voltage.nominal: 120 output.voltage: 135.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 63 ups.mfr: CPS ups.model: OR500LCDRM1Ua ups.productid: 0601 ups.realpower.nominal: 300 ups.serial: GA4JW2000855 ups.status: OL ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 — Reply to this email directly, view it on GitHub <#1338 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMPTFBSXA5JCBI6TQPS5G3VE4YQTANCNFSM5RQM5VUA> . You are receiving this because you commented.Message ID: ***@***.***>

[pedro042]

Hi,
thank you, just rebuilt, nothing changed from my point of view. Output voltage still reported 253 V
commit bce1d52
Merge: 573a03a 22a32f1
Author: Jim Klimov jimklimov@gmail.com
Date: Tue Apr 19 19:39:24 2022 +0200

battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 9425
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 27.4
battery.voltage.nominal: 24
device.mfr: CPS
device.model: OR1500ERM1U
device.serial: GBULX2000140
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 60
driver.parameter.ondelay: 300
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.version: 2.8.0-rc2-109-gbce1d5201
driver.version.data: CyberPower HID 0.6
driver.version.internal: 0.47
driver.version.usb: libusb-1.0.24 (API: 0x1000108)
input.voltage: 230.0
input.voltage.nominal: 230
output.voltage: 253.0
ups.beeper.status: disabled
ups.delay.shutdown: 60
ups.delay.start: 300
ups.load: 8
ups.mfr: CPS
ups.model: OR1500ERM1U
ups.productid: 0601
ups.realpower.nominal: 900
ups.serial: GBULX2000140
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: -60
ups.vendorid: 0764

[45413]

As a fellow owner of a CP1500PFCLCDa (US Model - ProductID: 0601), I believe this issue is related to issue #439 and fix #1245. This addresses an issue with CPS firmware returning and invalid LogMin/Max value but the fix is only applied for product ID 0x0501:

nut/drivers/cps-hid.c

Line 285 in 587af14

if (vendorID != CPS_VENDORID || productID != 0x0501) {

.

@flashydave posted in #439 2 days ago saying it should be an easy fix and would raise a PR, my guess just adding in the additional ProductID 0x0601 in the if statement so it runs cps_fix_report_desc and doesn't just return.

[flashydave]

Exacrly right! I am away from my PC so if you want to do the change then im happy for you to proceed. Dave

…

On 12:07, Tue 12 Jul 22, Austin Sabel wrote: As a fellow owner of a CP1500PFCLCDa (US Model - ProductID: 0601), I believe this issue is related to issue #439 and fix #1245. This addresses an issue with CPS firmware returning and invalid LogMin/Max value but the fix is only applied for product ID 0x0501: https://github.com/networkupstools/nut/blob/587af14347cb1a85a093eca603c2c3c29cab9c89/drivers/cps-hid.c#L285. @flashydave posted in #439 2 days ago saying it should be an easy fix and would raise a PR, my guess just adding in the additional ProductID `0x0601` in the if statement so it runs `cps_fix_report_desc` and doesn't just return. -- Reply to this email directly or view it on GitHub: #1338 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>