search for: refresh_report_buffer

...47 c4 ff 1d 0.307038 00 66 01 10 b1 a2 85 16 09 56 b1 a2 85 17 09 6e 75 01 15 00 25 01 35 00 45 0.307048 00 65 00 b1 a2 09 65 b1 a2 75 06 b1 01 85 18 75 10 09 44 26 c2 01 66 21 d1 0.307056 55 07 b1 a2 c0 c0 0.307133 Using subdriver: CyberPower HID 0.3 0.310846 refresh_report_buffer: expected 2 bytes, but got 8 instead 0.310858 Report[err]: (8 bytes) => 01 01 98 0d 2c 01 64 00 0.310870 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1.000000 0.314846 refresh_report_buffer: expected 2 bytes, but got 8 instead...

...74 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 instead 0.328518 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x11, Offset: 0, Si...

...Byte" > And old specs for BNT protocol: > "16 8456 DelayBeforeStartup *** R/W 2 Byte" > So, the length for DelayBeforeStartup report changed from 2 to 5 bytes. From the 2012 thread, it looks like the DelayBeforeStartup report might be encoded as hexadecimal: 0.440981 refresh_report_buffer: expected 3 bytes, but got 2 instead 0.441006 Report[err]: (2 bytes) => 0f 00 0.441024 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 0 0.445020 Report[get]: (5 bytes) => 10 30 30 30 30 0.445051 Path: UPS.PowerSummary.DelayB...

...r pattern of > "libusb_get_interrupt: Connection timed out" messages. UPS was powered. Actually, inverter of this particular UPS is broken (but undetected by it's logic), so I was unable to test it fully. I need UPS free of so called power race condition, however, 10.507657 refresh_report_buffer: expected 3 bytes, but got 2 instead and ups.timer.start: 740160 looks suspicious. As you suggest to test it on batt, I'm unsure what to do now - get it replaced or exchange to IMPERIAL series. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.a...

...portID: 0x0d, Offset: 0, Size: 16, Value: 17455 0.125933 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x37, Offset: 0, Size: 16, Value: 800 0.125942 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x37, Offset: 0, Size: 16, Value: 800 0.126551 refresh_report_buffer: expected 3 bytes, but got 2 instead 0.126560 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 0 0.127183 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x10, Offset: 0, Size: 32, Value: 12336 0.127930...

...ch device 0.062330 Device matches 0.062354 failed to claim USB device: could not claim interface 0: Device or resource busy 0.062375 detached kernel driver from USB device... 0.071243 HID descriptor length 653 0.098232 Report Descriptor size = 653 0.098450 Using subdriver: Belkin HID 0.12 0.101243 refresh_report_buffer: expected 2 bytes, but got 8 instead 0.101289 Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 230 0.104233 refresh_report_buffer: expected 2 bytes, but got 8 instead 0.104268 Path: UPS.BELKINConfig.BELKINConfigFrequency, Type: Feature, Repor...

...t_interrupt: Connection timed out" messages. > Every 2 sec driver outputs the following: > 10.254942 upsdrv_updateinfo... > 10.507035 libusb_get_interrupt: Connection timed out > 10.507054 Got 0 HID objects... > 10.507060 Quick update... > 10.507657 refresh_report_buffer: expected 3 bytes, but got 2 instead > 10.507671 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, > ReportID: 0x0f, Offset: 0, Size: 16, Value: 0 --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.Fahn...

On Sep 8, 2016, at 8:14 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > Hi again, > > Thanks for the prompt reply. > > Just for the record i am running debian unstable/sid with nut 2.7.4-3 > Thanks, that is useful. > 0.447725 refresh_report_buffer: expected 13 bytes, but got 8 instead This is the first sign of trouble. > 0.447736 Report[err]: (8 bytes) => 08 03 4d 00 45 00 43 00 Note that for the first HID query, it returned a USB string descriptor for "MEC" (08 bytes, 03 == string, rest is 16-bit Unicode). > 0.447...

...20150109 150451 100 250.0 66.0 [OL] NA NA 20150109 150951 100 250.0 72.0 [OL] NA NA 20150109 151451 100 250.0 66.0 [OL] NA NA 20150109 151951 100 250.0 73.0 [OL] NA NA output of /usr/local/libexec/nut/usbhid-ups -a maxell -DD at a time when low battery is reported: 161.408239 refresh_report_buffer: expected 5 bytes, but got 3 instead 161.408313 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, Offset: 0, Size: 32, Value: 250 161.419115 Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x46, Offset: 0, Size: 8, Value: 230 161.428351 Path: UPS...

...ature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1 0.073997 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8208 0.074644 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.075266 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.075310 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.075908 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.075952 Path: UPS.ffff0015.[1].ffff00d3, Type: Feature, ReportID: 0xb5, Offset:...

Hi Charles, Thanks for your response. > For the 1000, do the values match this page? > > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/Smart-UPS_1000.html > > Yes it does (except that mine is a 120 V model, so input/output voltage is about 125) It doesn't look like we have an entry for a C1500 yet. Would you care to > submit the output of

...05 10 95 01 66 01 f0 55 05 27 fe ff 00 00 81 02 09 35 75 10 95 01 15 00 26 ff 0.443017 00 81 02 09 02 a1 02 09 65 09 6e 09 6f 75 01 95 03 15 00 25 01 65 00 81 02 0.443024 75 05 95 01 81 03 c0 c0 c0 c0 0.443079 Using subdriver: EXPLORE HID 0.1 0.443087 36 HID objects found 0.447725 refresh_report_buffer: expected 13 bytes, but got 8 instead 0.447736 Report[err]: (8 bytes) => 08 03 4d 00 45 00 43 00 0.447745 Path: 00860004.Flow.FlowID, Type: Feature, ReportID: 0x01, Offset: 0, Size: 4, Value: 3 0.447755 Report[buf]: (13 bytes) => 08 03 4d 00 45 00 43 00 00 00 00 00 00 0.447767 Pat...

...ype: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8210 0.188432 Path: UPS.TLCustom.[1].ffff00df, Type: Feature, ReportID: 0x9f, Offset: 0, Size: 32, Value: 3 0.190439 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.192393 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.192571 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.194518 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.194696 Path: UPS.ffff0015.[1].ffff00d3, Type: Feature, ReportID: 0...

...ature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1 0.070327 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8208 0.070953 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.071418 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.071462 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.072034 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.072077 Path: UPS.ffff0015.[1].ffff00d3, Type: Feature, ReportID: 0xb5, Offset:...

...t;(75): Value too large for defined data type" may > > indicate that the UPS is unhappy with the size of the buffer provided > > by NUT (apparently 13). You can play with this by hacking a larger > > buffer size. It should be easy to do this in the function > > libhid.c:refresh_report_buffer(), by setting len to something bigger > > (or smaller). > >Sorry if that advice was drowned in a sea of other comments. This is >what you should do. I don't know if it will work, since I don't have >an Ablerex device to play with. > >-- Peter > >P.S. I am movin...

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.

On Jan 8, 2015, at 11:43 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: > Hello Nutters, > > I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason

...nt, Type: Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 1 771.884656 Path: UPS.Input.APCLineFailCause, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, Value: 0 771.884737 Path: UPS.Input.APCLineFailCause, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, Value: 0 771.893677 refresh_report_buffer: expected 5 bytes, but got 3 instead 771.893774 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, Offset: 0, Size: 32, Value: 248 771.904649 Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x46, Offset: 0, Size: 8, Value: 230 771.913733 Path: UPS.Output.Voltage, Type: F...