search for: 84001e

Displaying 4 results from an estimated 4 matches for "84001e".

2007 Jan 31
3
Re: [Nut-upsuser] Ablerex 625L USB version
...memcpy(raw_buf, p_raw_buf_test, ReportSize); return rc; } else return 0; } From this I now get Detected a UPS: UIS Ablerex/Ablerex USB Interface 049e Using subdriver: EXPLORE HID 0.1 parsing 00860004 parsing Flow hid_lookup_usage: found 84001e parsing FlowID hid_lookup_usage: found 84001f Path depth = 3, Path: 00860004.Flow.FlowID, Node1/2/3:, 860004, 84001e, 84001f 0: Usage(00860004) 1: Usage(0084001e) 2: Usage(0084001f) Buffer is stale. refreshing Noting in the buffer for rbuf->data[0] Noting in the buffer for rbuf->data[1] Notin...
2007 Jan 26
4
Ablerex 625L USB version
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.
2007 Jan 26
4
Ablerex 625L USB version
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.
2007 Jan 28
0
Fwd: Re: [Nut-upsuser] Ablerex 625L USB version
...get invalid responses. I notice in > the latest output that the length of the data and the length being > requested seem different (I put a couple of extra debugging statements in). > > Using subdriver: EXPLORE HID 0.1 > parsing 00860004 > parsing Flow > hid_lookup_usage: found 84001e > parsing FlowID > hid_lookup_usage: found 84001f > Path depth = 3 > 0: Usage(00860004) > 1: Usage(0084001e) > 2: Usage(0084001f) > Entering libusb_get_report. ReportSize: 13 > typesafe_control_msg: size: 13 > Can't retrieve Report 1 (75): Value too large for defined...