Christo Simeonoff
2017-Apr-17 09:54 UTC
[Nut-upsdev] New UPS information - Liebert GXT4 via US
Hi UPS List members, I have purchased a number of Emerson Power / Liebert GXT4 UPS units. I have these working correctly under nut, but limited detsils are being reported. I am happy to supply information on the USB communications to improve the reported details I can use WireShark to capture the comms between the supplied Windows GUI tool and the UPS Please advise the best way I can help. In the meantime, The output of: /sbin/usbhid-ups -DD -a liebert -i 120 | tee /tmp/liebert-GXT4.txt is attached STDOUT: Network UPS Tools - Generic HID driver 0.37 (2.6.5) USB communication driver 0.31 STDERR Attached: /tmp/liebert-GXT4.txt -- Regards, Christo Simeonoff, Technical Director, Integrity Net P/L Ph: (02) 8012 5115 M: (04) 19 992 965 F: (02) 99070990 E: integritynet at iinet.net.au -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20170417/4317086b/attachment.html> -------------- next part -------------- 0.000000 debug level is '2' 0.000558 upsdrv_initups... 0.003256 Checking device (10AF/0000) (001/004) 0.004504 - VendorID: 10af 0.004536 - ProductID: 0000 0.004555 - Manufacturer: Emerson Network Power 0.004574 - Product: Liebert GXT4 0.004597 - Serial Number: ZZZZZZZZZZZZZZZ 0.004613 - Bus: 001 0.004630 Trying to match device 0.004678 Device matches 0.004705 failed to claim USB device: could not claim interface 0: Device or resource busy 0.004740 detached kernel driver from USB device... 0.005265 HID descriptor length 505 0.007255 Report Descriptor size = 505 0.007544 Using subdriver: Belkin HID 0.15 0.007767 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 0.008018 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 4, Value: 3 0.008049 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x02, Offset: 4, Size: 4, Value: 1 0.008078 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID: 0x02, Offset: 8, Size: 4, Value: 1 0.008109 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x02, Offset: 12, Size: 4, Value: 6 0.008146 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x02, Offset: 16, Size: 8, Value: 100 0.008390 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x03, Offset: 0, Size: 24, Value: 250 0.008419 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x03, Offset: 24, Size: 2, Value: 2 0.008448 Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: 0x03, Offset: 26, Size: 1, Value: 1 0.008480 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x03, Offset: 27, Size: 5, Value: 1 0.008638 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 20 0.008892 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 100 0.008921 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x06, Offset: 0, Size: 8, Value: 100 0.009139 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 1, Value: 1 0.009168 Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID: 0x0c, Offset: 1, Size: 1, Value: 0 0.009195 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x0c, Offset: 2, Size: 1, Value: 1 0.009226 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x0c, Offset: 3, Size: 1, Value: 0 0.009250 Path: UPS.PowerSummary.BatteryPresent, Type: Feature, ReportID: 0x0c, Offset: 4, Size: 1, Value: 1 0.009274 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x0c, Offset: 5, Size: 3, Value: 0 0.009298 Path: UPS.PowerSummary.Charging, Type: Input, ReportID: 0x0c, Offset: 0, Size: 1, Value: 1 0.009334 Path: UPS.PowerSummary.Discharging, Type: Input, ReportID: 0x0c, Offset: 1, Size: 1, Value: 0 0.009358 Path: UPS.PowerSummary.ACPresent, Type: Input, ReportID: 0x0c, Offset: 2, Size: 1, Value: 1 0.009382 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0c, Offset: 3, Size: 1, Value: 0 0.009411 Path: UPS.PowerSummary.BatteryPresent, Type: Input, ReportID: 0x0c, Offset: 4, Size: 1, Value: 1 0.009442 Path: UPS.PowerSummary.Undefined, Type: Input, ReportID: 0x0c, Offset: 5, Size: 3, Value: 0 0.009642 Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x04, Offset: 0, Size: 8, Value: 0 0.009673 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, ReportID: 0x04, Offset: 8, Size: 8, Value: 0 0.009702 Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, ReportID: 0x04, Offset: 16, Size: 8, Value: 1 0.009731 Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, ReportID: 0x04, Offset: 24, Size: 8, Value: 1 0.010016 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 0 0.010047 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 0.010260 Path: UPS.PowerSummary.Test, Type: Feature, ReportID: 0x08, Offset: 0, Size: 8, Value: 0 0.010511 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 0 0.010760 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x32, Offset: 0, Size: 8, Value: 1 0.011002 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.011031 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x33, Offset: 0, Size: 8, Value: 1 0.011264 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 0 0.011512 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x3c, Offset: 0, Size: 8, Value: 0 0.011761 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x3d, Offset: 0, Size: 8, Value: 0 0.012015 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x3e, Offset: 0, Size: 8, Value: 1 0.012263 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x3f, Offset: 0, Size: 8, Value: 0 0.012512 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x40, Offset: 0, Size: 8, Value: 0 0.012762 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x41, Offset: 0, Size: 8, Value: 0 0.013012 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x42, Offset: 0, Size: 8, Value: 1 0.013264 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x43, Offset: 0, Size: 8, Value: 1 0.013512 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x44, Offset: 0, Size: 8, Value: 1 0.013762 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x50, Offset: 0, Size: 8, Value: 0 0.014014 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x51, Offset: 0, Size: 8, Value: 0 0.014261 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x52, Offset: 0, Size: 8, Value: 0 0.014510 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x53, Offset: 0, Size: 8, Value: 0 0.014760 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x54, Offset: 0, Size: 8, Value: 0 0.015011 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x55, Offset: 0, Size: 8, Value: 0 0.015264 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x56, Offset: 0, Size: 8, Value: 1 0.015513 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x57, Offset: 0, Size: 8, Value: 0 0.015762 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x58, Offset: 0, Size: 8, Value: 1 0.016014 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x59, Offset: 0, Size: 8, Value: 0 0.016263 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x5a, Offset: 0, Size: 8, Value: 1 0.016512 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x5b, Offset: 0, Size: 8, Value: 1 0.016762 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x5c, Offset: 0, Size: 8, Value: 0 0.017014 Path: UPS.PowerSummary.Undefined, Type: Feature, ReportID: 0x5d, Offset: 0, Size: 8, Value: 0 0.017054 Report descriptor retrieved (Reportlen = 505) 0.017073 Found HID device 0.017098 Detected a UPS: Emerson Network Power/Liebert GXT4 0.017148 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 20 0.017184 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, ReportID: 0x04, Offset: 8, Size: 8, Value: 0 0.017225 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x02, Offset: 12, Size: 4, Value: 6 0.017676 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 100 0.017725 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 0 0.017746 Input/OutputVoltage = 0 -> assuming correction factor = 1e+07 0.017779 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 0.017799 ConfigVoltage = 0 -> assuming correction factor = 1e+08 0.017837 Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID: 0x0c, Offset: 1, Size: 1, Value: 0 0.017873 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 1, Value: 1 0.017910 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x0c, Offset: 2, Size: 1, Value: 1 0.018090 find_nut_info: unknown info type: load.off.delay 0.018112 find_nut_info: unknown info type: load.on.delay 0.018133 find_nut_info: unknown info type: load.off.delay 0.018159 upsdrv_initinfo... 0.018189 upsdrv_updateinfo... 0.079719 Got 6 HID objects... 0.079755 Path: UPS.PowerSummary.Charging, Type: Input, ReportID: 0x0c, Offset: 0, Size: 1, Value: 1 0.079786 Path: UPS.PowerSummary.Discharging, Type: Input, ReportID: 0x0c, Offset: 1, Size: 1, Value: 0 0.079816 Path: UPS.PowerSummary.ACPresent, Type: Input, ReportID: 0x0c, Offset: 2, Size: 1, Value: 1 0.079842 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0c, Offset: 3, Size: 1, Value: 0 0.079875 Path: UPS.PowerSummary.BatteryPresent, Type: Input, ReportID: 0x0c, Offset: 4, Size: 1, Value: 1 0.079901 Path: UPS.PowerSummary.Undefined, Type: Input, ReportID: 0x0c, Offset: 5, Size: 3, Value: 0 0.079920 Quick update... 0.079944 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 100 0.079968 Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID: 0x0c, Offset: 1, Size: 1, Value: 0 0.079990 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 1, Value: 1 0.080012 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x0c, Offset: 2, Size: 1, Value: 1 0.080132 dstate_init: sock /var/run/nut/usbhid-ups-liebertA open on fd 5 0.080163 upsdrv_updateinfo... 0.112015 Got 1 HID objects... 0.112051 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x06, Offset: 0, Size: 8, Value: 100 0.112075 Quick update... 0.112106 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 100 0.112130 Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID: 0x0c, Offset: 1, Size: 1, Value: 0 0.112152 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 1, Value: 1 0.112173 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x0c, Offset: 2, Size: 1, Value: 1
Charles Lepple
2017-Apr-17 13:08 UTC
[Nut-upsdev] New UPS information - Liebert GXT4 via US
On Apr 17, 2017, at 5:54 AM, Christo Simeonoff <integritynet at iinet.net.au> wrote:> > Hi UPS List members, > > I have purchased a number of Emerson Power / Liebert GXT4 UPS units. > I have these working correctly under nut, but limited detsils are being reported.What is reported (upsc output), and what other details are you looking for? For comparison, this is all that we have working for the GXT3: http://networkupstools.org/ddl/Liebert/GXT3.html (note that one is for the serial driver, which is quite different from usbhid-ups.) While there have not been many differences to the Belkin/Liebert HID mappings since NUT 2.6.5, there have been numerous changes in the surrounding code. One of these changes is to print numbers as floating point, so that values that have been mistakenly divided will show up as decimals rather than zero. Also, any fixes to this driver will require source code changes. You might want to set up a development environment to rebuild NUT for your particular distribution.> I am happy to supply information on the USB communications to improve the reported details > > I can use WireShark to capture the comms between the supplied Windows GUI tool and the UPSOrdinarily, a debug level of 3 can be overwhelming, but this vendor has some issues with scaling. Can you please re-run the driver with "-DDD" and let it go for about a minute? The list has a limit of ~ 40KB for attachments and body, so please compress the log with gzip. Also, depending on what is missing, it is helpful to have a list of real-world events to go along with the Wireshark USB log. That is, if you cut the mains power, mention the time as seen by the system running Wireshark, and any other indications (front-panel display on the UPS, GUI response, etc.)