search for: powersummaryid

...device Device matches HID descriptor retrieved (Reportlen = 1535) Report descriptor retrieved (Reportlen = 1535) Found HID device Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) Report Descriptor size = 1535 Detected a UPS: unknown/unknown Using subdriver: MGE HID 0.8 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, Value: 1.000000 Path: UPS.PowerSummary.FlowID, Type: Feature, Value: 4.000000 Can't retrieve Report 52 (-5/5): Input/output error Path: UPS.PowerSummary.RemainingCapacityLimitSetting, Type: Feature Path: UPS.PowerSummary.Rechargeable, Type: Feature, Value: 1.000000 Path: UPS.Pow...

...uot;, HU_FLAG_STATIC, NULL }, { "battery.voltage.nominal", 0, 0, "UPS.PowerSummary.ConfigVoltage", NULL, "%s", HU_FLAG_STATIC, mge_battery_voltage_nominal }, Here are some of the UPS.PowerSummary lines from running with "-DD": Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x26, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PowerSummary.FlowID, Type: Feature, ReportID: 0x26, Offset: 8, Size: 8, Value: 4.000000 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x27, Offset: 0, Size: 16, Value: 120.000000 Path: UPS.PowerSummary.Vo...

...uct: OPEN-UPS 0.319560 - Serial Number: PBSO4-LiFePO 0.319567 - Bus: 008 0.319574 Trying to match device 0.319622 Device matches 0.321508 HID descriptor length 519 0.325501 Report Descriptor size = 519 0.325668 Using subdriver: EXPLORE HID 0.1 0.326510 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1 0.327502 refresh_report_buffer: expected 4 bytes, but got 2 instead 0.327516 Path: UPS.PowerSummary.iName, Type: Feature, ReportID: 0x10, Offset: 0, Size: 8, Value: 1 0.328503 refresh_report_buffer: expected 4 bytes, but got 2 in...

On Apr 5, 2014, at 7:18 AM, Mick wrote: > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > Username (suzy): admin > Password: > OK This command is sending the value to the UPS (via the usbhid-ups driver). > $ upsc iDowell at localhost ups.delay.shutdown > 30 And this command ends up reading the value back from the UPS. > However, following

...0x12, Offset: 0, Size: 8, Value: 230 0.982822 Path: UPS.Flow.[4].ConfigFrequency, Type: Feature, ReportID: 0x0d, Offset: 0, Size: 8, Value: 50 0.982845 Path: UPS.Flow.[4].ConfigApparentPower, Type: Feature, ReportID: 0x0d, Offset: 8, Size: 16, Value: 257 0.982861 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 24, Size: 8, Value: 0 0.982876 Path: UPS.PowerSummary.FlowID, Type: Feature, ReportID: 0x0b, Offset: 32, Size: 8, Value: 0 0.986836 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 8, Value: 2 0.986861 Path: UPS...

Hi All, I'm using an iDowell UPS with the usbhid-ups driver: $ upsc iDowell at localhost battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 battery.type: Pb acc device.mfr: iDowell device.model: iBox device.serial: 00000001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto

Hi everybody, If we let the feature running, it appears that the driver gets unbound after a while ( variable from quarter of hour to 6 hours ) and cannot reconnect. This behavior appear with both MGE Ellipse ASR and non-ASR models with connection to an UHCI and OHCI controllers. The USB core is from 2.4.28 kernel. We use nut-2.0.3. Start, powerfail and recovery detections, UPS shutdown work

...D: 0x10, Offset: 56, Size: 8, Value: 4 9.957969 Path: UPS.PowerSummary.ffff00f1, Type: Feature, ReportID: 0x10, Offset: 64, Size: 8, Value: 6 9.985299 Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 0 9.985535 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 32, Size: 8, Value: 1 10.017719 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1 10.017958 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 8,...

...ure, ReportID: 0x10, Offset: 32, Size: 8, Value: 4 4.940728 Path: UPS.PowerSummary.iVersion, Type: Feature, ReportID: 0x10, Offset: 40, Size: 8, Value: 6 4.985946 Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 0 4.986141 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 88, Size: 8, Value: 1 5.035951 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 1, Value: 1 5.036159 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 1, Value: 1...

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

...ure, ReportID: 0x10, Offset: 32, Size: 8, Value: 4 5.680027 Path: UPS.PowerSummary.iVersion, Type: Feature, ReportID: 0x10, Offset: 40, Size: 8, Value: 6 5.727946 Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 0 5.727964 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 104, Size: 8, Value: 1 5.777970 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 1, Value: 1 5.777987 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 1, Value:...

...ize: 8, Value: 12 7.330739 Report[get]: (6 bytes) => 07 09 b8 0b 31 03 7.331204 Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 9 7.331332 Report[buf]: (6 bytes) => 0b 01 04 00 04 01 7.331733 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 32, Size: 8, Value: 1 7.430670 Report[get]: (2 bytes) => e1 03 7.430941 Path: UPS.PowerSummary.ffff0094, Type: Feature, ReportID: 0xe1, Offset: 0, Size: 8, Value: 3 7.530374 Report[get]: (6 bytes) => 01 01 00 01 00 01 7.530...

...ering libusb_get_report 9.980264 Report[get]: (4 bytes) => 07 00 1b 00 9.980291 Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 0 9.980327 Report[buf]: (6 bytes) => 0b 01 04 03 04 01 9.980363 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 32, Size: 8, Value: 1 9.980393 Entering libusb_get_report 10.012262 Report[get]: (6 bytes) => 01 01 00 01 00 00 10.012292 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1...

...re, ReportID: 0x10, Offset: 40, Size: 8, Value: 3 7.737010 Path: UPS.PowerSummary.iVersion, Type: Feature, ReportID: 0x10, Offset: 48, Size: 8, Value: 5 7.768583 Path: UPS.PowerSummary.PercentLoad, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 30 7.768606 Path: UPS.PowerSummary.PowerSummaryID, Type: Feature, ReportID: 0x0b, Offset: 32, Size: 8, Value: 1 7.806602 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1 7.806618 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 8, Value: 1...

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT