search for: lowvoltagetransfer

...136.0 139.0 > 121.7 122.1 121 136.0 120.0 This is starting to come back to me - I think we saw this with several other CPS devices. Here's an excerpt from 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,...

...In case, we should signal that in 'device.type'. 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....

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: > >

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

...t; > > > 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.WarningCapa...

...IC HID 0.1 Network UPS Tools: 0.28 USB communication driver 0.28 - core 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 Pa...

...: 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 > > Path: UPS.Output.APCDelayBeforeStartup, Type: Input, Value: 0.000000 > > Path: UPS.Output.APCDelayBeforeStartup, Type: Feature, Value: > > 0.000000 >...

...s., Type: Feature Path: UPS.PowerSummary.AudibleAlarmControl, Type: 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.Dela...

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

...ature, ReportID: 0x0d, Offset: 0, Size: 8, Value: 3 0.263390 Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x0e, Offset: 0, Size: 8, Value: 120 0.263488 Path: UPS.Input.Voltage, Type: Feature, ReportID: 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...

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

Hello Charles, Thank you for your reply. For the discrete value thing, this morning I did try to run sudo upsrw -s input.transfer.low=x -u * -p * ups I changed "x" value from 60 to 96 then checked upsc result. All the script return OK but only 84 and 96 got picked up and working. Out model is Eaton 3S 500. And in windows it has a Eaton Personal Solution Pac. In Battery transfer

On Jun 5, 2014, at 10:53 PM, Charles Lepple wrote: > As you have seen, the "default.*" and "overwrite.*" names are not actual variables: they are configuration options to change what is returned from upsc. That is why you get VAR-NOT-SUPPORTED. typo; should have been "override.*" -- Charles Lepple clepple at gmail

...s., Type: Feature Path: UPS.PowerSummary.AudibleAlarmControl, Type: 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.Delay...

...ature, ReportID: 0x0d, Offset: 0, Size: 8, Value: 3 0.133070 Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x0e, Offset: 0, Size: 8, Value: 120 0.133141 Path: UPS.Input.Voltage, Type: Feature, ReportID: 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...

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) => 28 06 96 0C 8C == ?? UPS.APC860018.Input (2 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.APC8...

...urer, Type: Feature, ReportID: 0x0d, Offset: 0, Size: 8, Value: 3 0.033910 Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x0e, Offset: 0, Size: 8, Value: 120 0.034656 Path: UPS.Input.Voltage, Type: Feature, 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...

...x28, Offset: 0, Size: 32, Value: -1.34135e+09 > 0.072280 Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 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 >...

...et: 0, Size: 32, Value: -1.34135e+09 >> 0.072280 Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 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 &g...