search for: highvoltagetransf

...om the CP1500AVRLCDa HID descriptor: Collection(Physical) Report ID(16) Usage(LowVoltageTransfer) Logical Minimum(97) Logical Maximum(103) Feature(Data,Variable,Absolute) Usage(LowVoltageTransfer) Input(Constant,Variable,Absolute) Usage(HighVoltageTransfer) Logical Minimum(136) Logical Maximum(142) Feature(Data,Variable,Absolute) Usage(HighVoltageTransfer) Input(Constant,Variable,Absolute) Report ID(18) Usage(Voltage) Feature(Constant,Variable,Absolute) Report Size(8) Lo...

On 5/30/2017 10:47 PM, Charles Lepple wrote: > On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote: >> >> On 5/21/2017 10:39 AM, Charles Lepple wrote: [snip] > Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: > >

On 1/27/19 9:49 PM, Charles Lepple wrote: > You might be lucky with this particular model, but definitely beware of the USB issues I mentioned in another thread: > > https://github.com/networkupstools/nut/issues?q=is%3Aissue+is%3Aopen+label%3A%22CyberPower+%28CPS%29%22 > > The output of upsc is sorted alphabetically by key, so it isn't immediately obvious which values come

...Now, just a few questions on the mapping: 1. Are the following items read-only? And do they change from time to time and need to be polled, or once retrieved they remain the same (i.e. they are static)? - input.transfer.low / UPS.Input.LowVoltageTransfer - input.transfer.high / UPS.Input.HighVoltageTransfer - input.transfer.low / UPS.PowerConverter.Output.LowVoltageTransfer - input.transfer.high / UPS.PowerConverter.Output.HighVoltageTransfer - battery.charge.warning / UPS.PowerSummary.WarningCapacityLimit - battery.charge.low / UPS.PowerSummary.RemainingCapacityLimit 2. Do the following...

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

...gt; 1. Are the following items read-only? > > And do they change from time to time and need to be polled, or once > > retrieved they remain the same (i.e. they are static)? > > - input.transfer.low / UPS.Input.LowVoltageTransfer > > - input.transfer.high / UPS.Input.HighVoltageTransfer > > - input.transfer.low / UPS.PowerConverter.Output.LowVoltageTransfer > > - input.transfer.high / UPS.PowerConverter.Output.HighVoltageTransfer > > - battery.charge.warning / UPS.PowerSummary.WarningCapacityLimit > > - battery.charge.low / UPS.PowerSummary.Re...

...0.30 (2.1.0) Path: 00860004.Flow.FlowID, Type: Feature, Value: 0.000000 Path: 00860004.Flow.ConfigVoltage, Type: Feature, Value: 0.000000 Path: 00860004.Flow.ConfigFrequency, Type: Feature, Value: 0.000000 Path: 00860004.Flow.LowVoltageTransfer, Type: Feature, Value: 0.000000 Path: 00860004.Flow.HighVoltageTransfer, Type: Feature, Value: 0.000000 Path: 00860004.Flow.iManufacturer, Type: Feature, Value: 0.000000 Path: 00860004.Flow.iProduct, Type: Feature, Value: 0.000000 Path: 00860004.Flow.iSerialNumber, Type: Feature, Value: 0.000000 Path: 00860004.Flow.FlowID, Type: Feature, Value: 0.000000 Path: 0086000...

...: UPS.Output.Frequency, Type: Feature, Value: 50.000004 > > Path: UPS.Output.Voltage, Type: Feature, Value: 231.800003 > > Path: UPS.Output.ConfigVoltage, Type: Input, Value: 230.000000 > > Path: UPS.Output.ConfigVoltage, Type: Feature, Value: 230.000000 > > Path: UPS.Output.HighVoltageTransfer, Type: Input, Value: 253.000000 > > Path: UPS.Output.HighVoltageTransfer, Type: Feature, Value: > > 253.000000 > > Path: UPS.Output.LowVoltageTransfer, Type: Input, Value: 208.000000 > > Path: UPS.Output.LowVoltageTransfer, Type: Feature, Value: > > 208.000000 >...

...Feature, Value: 2.000000 Path: UPS.PowerSummary.iManufacturer, Type: Feature, Value: 3.000000 Path: UPS.Input.ConfigVoltage, Type: Feature, Value: 120.000000 Path: UPS.Input.Voltage, Type: Feature, Value: 120.000000 Path: UPS.Input.LowVoltageTransfer, Type: Feature, Value: 90.000000 Path: UPS.Input.HighVoltageTransfer, Type: Feature, Value: 140.000000 Path: UPS.Output.Voltage, Type: Feature, Value: 120.000000 Path: UPS.Output.PercentLoad, Type: Feature, Value: 92.000000 Path: UPS.Output.Test, Type: Feature, Value: 1.000000 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, Value: -1.000000 Path: UPS.Output.D...

Dear Daniele, nice to meet you, I'm a collegue of Gabriele. The problem with "blazer_usb" driver ("blazer_ser" works correctly) is related to the following commands: - "F" and "I": when the KRAULER subdriver check these UPS answers it uses wrong constants to check the lenght of the received packets, so these commands are considered as "not

...tracking what you mean by 'scaled to the > transfer voltage range' though. Could you clarify? > The "output.voltage" column in the quoted portion at the link is clipped/scaled to the range 136.0 to 142.0, which happens to be the range of possible settings for the USB HID HighVoltageTransfer voltage (NUT variable: input.transfer.high): https://alioth-lists.debian.net/pipermail/nut-upsuser/2017-June/010685.html

...0x0f, Offset: 0, Size: 16, Value: 119 0.263575 Path: UPS.Input.LowVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 0, Size: 16, Value: 88 0.263585 Path: UPS.Input.LowVoltageTransfer, Type: Input, ReportID: 0x10, Offset: 0, Size: 16, Value: 88 0.263593 Path: UPS.Input.HighVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 16, Size: 16, Value: 139 0.263601 Path: UPS.Input.HighVoltageTransfer, Type: Input, ReportID: 0x10, Offset: 16, Size: 16, Value: 139 0.263718 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: 136 0.2638...

Gentlemen, I have now had a chance to run some initial tests of my changes to apc-hid.c of the current development tree. Running newhipups and inspecting the -DDDD output seems to indicate that with the fix below everything seems to work as expected. However, I have not yet shut my system in order to take the UPS out of action so that I can do my various tests with a lightbulb load. I still hope

...Feature, Value: 2.000000 Path: UPS.PowerSummary.iManufacturer, Type: Feature, Value: 3.000000 Path: UPS.Input.ConfigVoltage, Type: Feature, Value: 120.000000 Path: UPS.Input.Voltage, Type: Feature, Value: 123.000000 Path: UPS.Input.LowVoltageTransfer, Type: Feature, Value: 90.000000 Path: UPS.Input.HighVoltageTransfer, Type: Feature, Value: 140.000000 Path: UPS.Output.Voltage, Type: Feature, Value: 123.000000 Path: UPS.Output.PercentLoad, Type: Feature, Value: 0.000000 Path: UPS.Output.Test, Type: Feature, Value: 1.000000 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, Value: -60.000000 Path: UPS.Output.D...

...0x0f, Offset: 0, Size: 16, Value: 129 0.133228 Path: UPS.Input.LowVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 0, Size: 16, Value: 88 0.133233 Path: UPS.Input.LowVoltageTransfer, Type: Input, ReportID: 0x10, Offset: 0, Size: 16, Value: 88 0.133238 Path: UPS.Input.HighVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 16, Size: 16, Value: 139 0.133242 Path: UPS.Input.HighVoltageTransfer, Type: Input, ReportID: 0x10, Offset: 16, Size: 16, Value: 139 0.133339 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: 137 0.133...

Hello Charles! As promised, I just checked out the CVS and recompiled everything. In the attached .txt is what is coming out from my UPS. I am wondering about all those zeroes. Also, this morning I plan to connect the UPS to a Win box running the monitoring program supplied with the UPS (UPSilon2000) and a USB sniffer program. If you have any suggestions on what to look for in the data,

...bytes) => 30 78 == 120 UPS.APC860018.ConfigVoltage (2 bytes) => 31 74 == 116 UPS.APC860018.Voltage (2 bytes) => 32 58 == 88 UPS.APC860018.LowVoltageTransfer (2 bytes) => 33 8B == 139 UPS.APC860018.HighVoltageTransfer (2 bytes) => 34 B1 == 177 UPS.APC860018.APC860024 (2 bytes) => 35 02 == 2 UPS.APC860018.APC860061 (2 bytes) => 36 00 == 0 UPS.APC860052.APCGeneralCollection (2 bytes) => 40 00 == 0 UPS.APC86...

...ReportID: 0x0f, Offset: 0, Size: 16, Value: 120 0.035409 Path: UPS.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 0, Size: 16, Value: 100 0.035450 Path: UPS.Output.LowVoltageTransfer, Type: Input, ReportID: 0x10, Offset: 0, Size: 16, Value: 100 0.035487 Path: UPS.Output.HighVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 16, Size: 16, Value: 139 0.035523 Path: UPS.Output.HighVoltageTransfer, Type: Input, ReportID: 0x10, Offset: 16, Size: 16, Value: 139 0.036156 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: 136 0.036904 Path: U...

...D: 0x30, Offset: 0, Size: 8, Value: 230 > 0.072912 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 235 > 0.073536 Path: UPS.Input.LowVoltageTransfer, Type: Feature, ReportID: 0x32, Offset: 0, Size: 16, Value: 176 > 0.074160 Path: UPS.Input.HighVoltageTransfer, Type: Feature, ReportID: 0x33, Offset: 0, Size: 16, Value: 282 > 0.074783 Path: UPS.Input.ff860024, Type: Feature, ReportID: 0x34, Offset: 0, Size: 16, Value: 128 > 0.075399 Path: UPS.Input.APCSensitivity, Type: Feature, ReportID: 0x35, Offset: 0, Size: 8, Value: 1 > 0.0760...

...Offset: 0, Size: 8, Value: 230 >> 0.072912 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x31, Offset: 0, Size: 16, Value: 235 >> 0.073536 Path: UPS.Input.LowVoltageTransfer, Type: Feature, ReportID: 0x32, Offset: 0, Size: 16, Value: 176 >> 0.074160 Path: UPS.Input.HighVoltageTransfer, Type: Feature, ReportID: 0x33, Offset: 0, Size: 16, Value: 282 >> 0.074783 Path: UPS.Input.ff860024, Type: Feature, ReportID: 0x34, Offset: 0, Size: 16, Value: 128 >> 0.075399 Path: UPS.Input.APCSensitivity, Type: Feature, ReportID: 0x35, Offset: 0, Size: 8, Value: 1 >>...