2014-11-08 20:46 GMT-03:00 Charles Lepple <clep...@gmail.com>: > On Nov 7, 2014, at 7:30 AM, Marcelo Fernandez > <marcelo.fidel.fernan...@gmail.com> wrote: > >> 2014-11-07 0:16 GMT-03:00 Charles Lepple <clep...@gmail.com>: >>> On Nov 6, 2014, at 5:56 PM, Marcelo Fernandez >>> <marcelo.fidel.fernan...@gmail.com> wrote: >>> >>>> battery.voltage: 10000000. >>>> battery.voltage.nominal: 0.0 >>> >>> Well, these are certainly interesting values ;-) >>> >>> I suspect the correction for earlier units has failed. Can you please start >>> the driver with "-DDD", let it run for a minute, then gzip and attach the >>> resulting log? >> >> Yes, sure. Here it is. >> >> Let me know if it's enough to diagnose that weird value. > > Here is the problem: > > Starting at 0.062904 (reformatted): > > Report[buf]: (5 bytes) => 05 51 00 48 00 > Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, > Size: 16, Value: 1 > > Report[buf]: (5 bytes) => 05 51 00 48 00 > Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: > 16, Size: 16, Value: 0 > > ConfigVoltage = 0 -> assuming correction factor = 1e+08 > > The Voltage of 0x51 (81 V) and ConfigVoltage of 0x48 (72 V) seem reasonable, > but somewhere else in the HID Report Descriptor, the voltages are getting > scaled to a "Logical" range of 0-1. > > Can you temporarily comment out line 383 in drivers/libhid.c and rebuild? It > currently looks like this: > > *Value = logical_to_physical(hiddata, hValue); > > If that works, we can add a flag to ignore logical-to-physical mappings. >
Hello Charles, Now it seems I'm getting the same values but formatted differently in the output: root@nut:/usr/local/ups/bin# ./upsc liebert battery.charge: 100 battery.charge.low: 20 battery.charge.warning: 0 battery.type: PbAc battery.voltage: 1.0 battery.voltage.nominal: 0.0 device.mfr: Emerson Network Power device.model: Liebert GXT3 device.serial: 1226603098AF453 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.2.5 driver.version.data: Belkin/Liebert HID 0.17 driver.version.internal: 0.38 ups.mfr: Emerson Network Power ups.model: Liebert GXT3 ups.productid: 0008 ups.serial: 1226603098AF453 ups.status: OL CHRG ups.vendorid: 10af I'm attaching a new debug log with this modification, just in case, but I'm still seeing the lines you've pointed at: 0.062308 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x05, Offset: 0, Size: 16, Value: 1 0.062336 Report[buf]: (5 bytes) => 05 51 00 48 00 0.062352 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 0.062379 ConfigVoltage = 0 -> assuming correction factor = 1e+08 Thank you -- Marcelo F. Fernández Buenos Aires, Argentina Lic. en Sistemas de Información E-Mail: marcelo.fidel.fernan...@gmail.com Blog: http://blog.marcelofernandez.info Twitter: http://twitter.com/fidelfernandez
liebert-2.log.gz
Description: GNU Zip compressed data
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
