[Nut-upsdev] Re: CyberPower 685AVR and newhidups

Sun Oct 23 05:54:53 UTC 2005

Dear Scott,

fantastic! Thanks for that data. Indeed, the CyberPower usage tree
looks extremely similar to that of APC. I have added support for your
CyberPower device to the Development branch on CVS.

Please test this. Run the driver as:

drivers/newhidups -DD -u root -x vendorid=0764 auto

(without the -x generic option from last time, as your model is now
supported).

I am particularly interested in the following variables:

* ups.power.nominal
  (this should report ca. 550VA. The device reports this as 390W, but
  NUT requires power to be reported in VA (not Watts), so I have
  converted the value. Arnaud: is this the correct thing to do?)

* ups.delay.shutdown  
  (this should report -1. This variables is writable to initiate a
  timed shutdown. It would be great if you could test this. Be careful
  to disconnect any equipment before testing.)

* ups.test.result
  (this should report "passed" or similar. The main interest of this
  variable is what happens when writing to it. Writing "1", "2", or
  "3", respectively, should initiate up to three different types of
  tests. Writing "0" should abort a test in progress. It would be
  great if you could report back what kind of test these actions
  perform.)

Please also check the values of the remaining variables to see that
they make sense. It would be great if you could post the output of
"upsc upsname at localhost" back to the list. 

Please also test the following instant commands (again, disconnect
your equipment from the UPS before testing):

load.off
load.on
shutdown.return
shutdown.stop
beeper.on
beeper.off

(the latter two will only work properly during a "beeper" event, i.e.,
when there is a power failure).

Finally, it would be great if you could test the -k flag, to see if it
shuts down the power. 

drivers/newhidups -DD -u root -x vendorid=0764 auto -k

Thanks, -- Peter

Scott Alfter wrote:
> 
> Peter Selinger wrote:
> 
> > Please get the newest Development version of NUT from CVS, and re-run
> > newhidups with the following command line:
> > 
> > drivers/newhidups -DD -u root -x generic -x vendorid=0764 auto
> > 
> > This will output a bunch of useful information, including many lines
> > starting with the word "Path:". (You can then use CTRL-C to kill the
> > driver). Please post this information back to the list. 
> 
> It's building right now...well, it was.  Looks like it just finished. :-)
> Here's what diagnostic info came out of it:
> 
> Network UPS Tools: New USB/HID UPS driver 0.28 (2.1.0)
> 
> debug level is '2'
> Checking device (0000/0000) (002/001)
> - - VendorID: 0000
> - - ProductID: 0000
> - - Manufacturer: Linux 2.6.9 uhci_hcd
> - - Product: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
> - - Serial Number: 0000:00:07.3
> - - Bus: 002
> Trying to match device
> Device does not match - skipping
> Checking device (0764/0501) (001/002)
> - - VendorID: 0764
> - - ProductID: 0501
> - - Manufacturer: CPS
> - - Product: UPS BF700
> - - Serial Number: unknown
> - - Bus: 001
> Trying to match device
> Device matches
> failed to claim USB device, trying 2 more time(s)...
> detaching kernel driver from USB device...
> trying again to claim USB device...
> HID descriptor retrieved (Reportlen = 374)
> Report descriptor retrieved (Reportlen = 374)
> Found HID device
> Report Descriptor size = 374
> Detected a UPS: CPS/UPS BF700
> Using subdriver: GENERIC HID 0.1
> Path: UPS.PowerSummary.iProduct, Type: Feature, Value: 1.000000
> Path: UPS.PowerSummary.iSerialNumber, Type: Feature, Value: 2.000000
> Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, Value: 4.000000
> Path: UPS.PowerSummary.iOEMInformation, Type: Feature, Value: 3.000000
> Path: UPS.PowerSummary.Rechargeable, Type: Feature, Value: 1.000000
> Path: UPS.PowerSummary.CapacityMode, Type: Feature, Value: 2.000000
> Path: UPS.PowerSummary.DesignCapacity, Type: Feature, Value: 100.000000
> Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, Value: 5.000000
> Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, Value: 10.000000
> Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, Value: 20.000000
> Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, Value: 10.000000
> Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, Value: 100.000000
> Path: UPS.PowerSummary.RemainingCapacity, Type: Input, Value: 120.000000
> Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, Value: 120.000000
> Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, Value: 930.000000
> Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, Value: 930.000000
> Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, Value: 300.000000
> Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, Value: 300.000000
> Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.000000
> Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 21.000000
> Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value: 1.000000
> Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input,
> Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, Value: 1.000000
> Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input,
> Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, Value: 1.000000
> Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type:
> Feature, Value: 0.000000
> Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Feature, Value: 1.000000
> Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature,
> Value: 0.000000
> 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: 124.000000
> Path: UPS.Output.PercentLoad, Type: Feature, Value: 38.000000
> Path: UPS.Output.Test, Type: Feature, Value: 1.000000
> Path: UPS.Output.DelayBeforeShutdown, Type: Feature, Value: -1.000000
> Path: UPS.Output.DelayBeforeStartup, Type: Feature, Value: 0.000000
> Path: UPS.Output.Boost, Type: Feature, Value: 0.000000
> Path: UPS.Output.OverLoad, Type: Feature, Value: 0.000000
> Path: UPS.Output.00840044, Type: Feature, Value: 390.000000
> entering identify_ups(0x0764, 0x0501)
> 
> upsdrv_updateinfo...
> dstate_init: sock /var/lib/nut/newhidups-auto open on fd 5
> upsdrv_updateinfo...
> Waiting for notifications...
> 
> =>Got 3 HID Objects...
> find_hid_info: unknown variable: UPS.PowerSummary.RemainingTimeLimit
> 
> find_hid_info: unknown variable: UPS.PowerSummary.RunTimeToEmpty
> 
> find_hid_info: unknown variable: UPS.PowerSummary.RemainingCapacity
> 
> upsdrv_updateinfo...
> Waiting for notifications...
> 
> =>Got 6 HID Objects...
> find_hid_info: unknown variable:
> UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired
> 
> find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.FullyCharged
> 
> find_hid_info: unknown variable:
> UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
> 
> find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.Discharging
> 
> find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.Charging
> 
> find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.ACPresent
> 
> Signal 2: exiting
> Closing device
> 
> Scott Alfter
> scott at alfter.us