Gentlemen,
I have a new HID USB device, that seems to be quite similar to the
currently supported APC HID UPS. I append the dump-tree output, and would
much appreciate advice on how to proceed.
Certain entries for the current device are not available, but maybe there
are some replacements that could be used. This may of course require a new
table in apc-hid.h, and I would prefer not to do this without some guidance.
Also, it looks to me like the driver did actually start its standard loop,
but I thought it best to first sort out the appropriate tables.
Thanks, AG
P.S. for Arnaud, I had the option to use a different device, and so I did!
I will therefore unfortunately not be able to provide you with the
TrippLite information that you requested. I suspect we didn't loose
much!
--------------------------------------------------------------------------------
debug level is '2'
Opening new device (0000/0000)
Opening new device (0000/0000)
Opening new device (0000/0000)
Opening new device (0000/0000)
Opening new device (051D/0002)
Found 0x51d
- Manufacturer : APC
- Product : Back-UPS ES 650 FW:818.w1.D USB FW:w1
- Serial Number: QB0518132135
HID descriptor retrieved (Reportlen = 872)
Report descriptor retrieved (Reportlen = 872)
found 1 (872)
Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2)
Report Descriptor size = 872
Detected an UPS: APC/Back-UPS ES 650 FW:818.w1.D USB FW:w1
Path: UPS.PowerSummary.iSerialNumber
Path: UPS.PowerSummary.iDeviceChemistry
Path: UPS.PowerSummary.iOEMInformation
Path: UPS.PowerSummary.Rechargeable
Path: UPS.PowerSummary.APCStatusFlag
Path: UPS.PowerSummary.APCStatusFlag
Path: UPS.PowerSummary.ManufacturerDate
Path: UPS.PowerSummary.ConfigVoltage
Path: UPS.PowerSummary.Voltage
Path: UPS.PowerSummary.iManufacturer
Path: UPS.PowerSummary.CapacityMode
Path: UPS.PowerSummary.RemainingCapacity
Path: UPS.PowerSummary.RemainingCapacity
Path: UPS.PowerSummary.RunTimeToEmpty
Path: UPS.PowerSummary.RunTimeToEmpty
Path: UPS.PowerSummary.DesignCapacity
Path: UPS.PowerSummary.FullChargeCapacity
Path: UPS.PowerSummary.WarningCapacityLimit
Path: UPS.PowerSummary.CapacityGranularity2
Path: UPS.PowerSummary.RemainingCapacityLimit
Path: UPS.PowerSummary.CapacityGranularity1
Path: UPS.PowerSummary.PresentStatus.Charging
Path: UPS.PowerSummary.PresentStatus.Charging
Path: UPS.PowerSummary.PresentStatus.Discharging
Path: UPS.PowerSummary.PresentStatus.Discharging
Path: UPS.PowerSummary.PresentStatus.ACPresent
Path: UPS.PowerSummary.PresentStatus.ACPresent
Path: UPS.PowerSummary.PresentStatus.BatteryPresent
Path: UPS.PowerSummary.PresentStatus.BatteryPresent
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
Path: UPS.PowerSummary.PresentStatus.ShutdownImminent
Path: UPS.PowerSummary.PresentStatus.ShutdownImminent
Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired
Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired
Path: UPS.PowerSummary.PresentStatus.NeedReplacement
Path: UPS.PowerSummary.PresentStatus.NeedReplacement
Path: UPS.PowerSummary.PresentStatus.OverLoad
Path: UPS.PowerSummary.PresentStatus.OverLoad
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.PresentStatus.00000000
....................... a total of 46 PresentStatus.00000000 lines
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.RemainingTimeLimit
Path: UPS.PowerSummary.AudibleAlarmControl
Path: UPS.Battery.APCBattReplaceDate
Path: UPS.Battery.ManufacturerDate
Path: UPS.Battery.RemainingCapacity
Path: UPS.Battery.RunTimeToEmpty
Path: UPS.Battery.RunTimeToEmpty
Path: UPS.Battery.RemainingTimeLimit
Path: UPS.Battery.ConfigVoltage
Path: UPS.Battery.Voltage
Path: UPS.Battery.ff860024
Path: UPS.ff860018.Input
Path: UPS.ff860018.ConfigVoltage
Path: UPS.ff860018.Voltage
Path: UPS.ff860018.LowVoltageTransfer
Path: UPS.ff860018.HighVoltageTransfer
Path: UPS.ff860018.ff860024
Path: UPS.ff860018.ff860061
Path: UPS.APC860052.APCGeneralCollection
Path: UPS.APC860052.APCForceShutdown
Path: UPS.APCDelayBeforeShutdown.PowerConverter
Path: UPS.APCDelayBeforeShutdown.PercentLoad
Path: UPS.ff860024.ff860001
Path: UPS.ff860024.ff860023
Path: UPS.ff860024.ff860026
Path: UPS.ff860025
Path: UPS.iProduct
Path: UPS.APC_UPS_FirmwareRevision
Path: UPS.iSerialNumber
Path: UPS.iManufacturer
Path: UPS.ManufacturerDate.PresentStatus
Path: UPS.ManufacturerDate.Charging
Path: UPS.ManufacturerDate.Discharging
Path: UPS.ManufacturerDate.ACPresent
Path: UPS.ManufacturerDate.BatteryPresent
Path: UPS.ManufacturerDate.BelowRemainingCapacityLimit
PPath: UPS.ManufacturerDate.ShutdownImminent
Path: UPS.ManufacturerDate.RemainingTimeLimitExpired
Path: UPS.ManufacturerDate.NeedReplacement
Path: UPS.ManufacturerDate.OverLoad
Path: UPS.ManufacturerDate.00000000
Path: UPS.ManufacturerDate.00000000
........................... a total of 22 ManufacturerDate.00000000 lines
Path: UPS.ManufacturerDate.00000000
Path: UPS.ManufacturerDate.00000000
Path: UPS.APCPanelTest
Path: UPS.AudibleAlarmControl
Path: UPS.ff860029
Path: UPS.ff86002a
entering identify_ups(0x051d, 0x0001)
Can't find object UPS.Battery.Temperature
Can't find object UPS.Output.PercentLoad
Can't find object UPS.PowerSummary.DelayBeforeShutdown
Can't find object UPS.Battery.Test
Can't find object UPS.Battery.Temperature
process_status_info: OL
Can't find object UPS.Input.Voltage
Can't find object UPS.Output.Voltage
Can't find object UPS.Output.ConfigVoltage
Can't find object UPS.BatterySystem.Battery.Test
Can't find object UPS.BatterySystem.Battery.Test
Can't find object UPS.BatterySystem.Battery.Test
Can't find object UPS.PowerSummary.DelayBeforeShutdown
Can't find object UPS.PowerSummary.DelayBeforeStartup
upsdrv_updateinfo...
process_status_info: OL
dstate_init: sock /var/lib/ups/newhidups-start open on fd 5
upsdrv_updateinfo...
Waiting for notifications...
ok
upsdrv_updateinfo...
Waiting for notifications...
ok
=>Got 2 HID Objects...
battery.runtime = 2265
battery.charge = 100
upsdrv_updateinfo...
Waiting for notifications...
ok
=>Got 9 HID Objects...
find_hid_info: unknown variable:
UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired
find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.BatteryPresent
ups.status = OL
process_status_info: OL
upsdrv_updateinfo...
Waiting for notifications...
ok
upsdrv_updateinfo...
Waiting for notifications...
ok
=>Got 2 HID Objects...
battery.runtime = 2265
battery.charge = 100
upsdrv_updateinfo...
Waiting for notifications...
ok
.................................
--------------------------------------------------------------------------------
--
----------------------------------------------------------------------
Alfred Ganz alfred-ganz@agci.com
AG Consulting, Inc. (203) 624-9667
440 Prospect Street # 11
New Haven, CT 06511
----------------------------------------------------------------------
> I have a new HID USB device, that seems to be quite similar to the > currently supported APC HID UPS. I append the dump-tree output, and would > much appreciate advice on how to proceed. > > Certain entries for the current device are not available, but maybe there > are some replacements that could be used. This may of course require a new > table in apc-hid.h, and I would prefer not to do this without some guidance.FYI: - apc-hid.h still need to be completed. John Stamp (cc'ed) has began to work on this. Mostly, the shutdown procedure, which varies between APC models, has to be completed... Check with John for more info... - this table lists all available data for all the devices of a manufacturer, - At launch time, newhidups check the data available from the current device. If there are data redundancies (ie multiple definition for a same nut variable), then the first available is used. I put the better first (ie if there is one RW var for high end UPS, and another RO for low end, put the RW first, as for "battery.charge.low" in mge-hid.h) - look at mge-hid.h for more examples and ask questions as I've not yet made the document to extend newhidups...> Also, it looks to me like the driver did actually start its standard loop, > but I thought it best to first sort out the appropriate tables.sure. what upsc gives you for the moment?> P.S. for Arnaud, I had the option to use a different device, and so I did!> I will therefore unfortunately not be able to provide you with the > TrippLite information that you requested. I suspect we didn't loose > much! no problem for me at all. although I'm the NUT project leader, I'm paid and employed by MGE for that task, not APC nor Tripplite... But you should have prefered an MGE to support NUT ;-)> ...the task is: - to check is the below path are already in apc-hid.h - to add it otherwise (check mge-hid for example) and link it to the right nut var. - the 000000 suffixed path are due to the use of the MGE HID Parser. These are ignored, except for the dump (I'll modify it not to pollute...) Once more, coordinate with John to get information and complete all that... Arnaud Quette --- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt OpenSource Developer - http://arnaud.quette.free.fr/ Debian Developer - http://people.debian.org/~aquette/ ... and much more ...