[Nut-upsdev] Re: PowerCom USB units...
Peter Selinger
selinger at mathstat.dal.ca
Mon Feb 5 22:41:43 CET 2007
Yes, the iCute is 0d9f/0002, but the other two devices I mentioned are
0d9f/0001. They look very similar to yours.
* the thread on nut-upsuser with subject "Newpoint 200897 UPS"
(December 2006).
* the thread on nut-upsuser with subject "Gentoo Ultra USB UPS" in
July/August 2006 [possibly the same as your device?]
We never got them to work yet.
Jon got the most interesting output from descriptor 0, which is the
one you did not test. For descriptor 0, the index actually
matters. Here's what he got:
index response meaning (what happens)
0 ?
1 UIS Ablerex Manufacturers name
2 Ablerex USB Interface 049e Product
3 (246.5 140.0 246.5 024 50.0 27.0 25.0
00001000. Volt_in ?? Vol_out %cap Hz ?? ?? ??
4 USB No Ack Test for 10 secs
5 USB No Ack Test
disconnect from mains
6 USB No Ack Disconnect mains
7 USB No Ack Toggle beep on/off ?
8 USB No Ack Toggle beep on ?
9 USB No Ack Toggle beep on ?
10 USB No Ack ?
11 USB No Ack Reconnect mains
12 JP 01053T ?
13 #240.0 0.0 024.0 50.0. Volt_in
14 breaks the pipe
Could you check descriptor 0? -- Peter
Eric Ashley wrote:
>
> Thanks for the tips. Unlike the PowerCom iCute mentioned last month,
> my units (1000VA and 1025VA-LCD) identify themselves with vendor 0x0d9f
> and productid 0x0001.
>
> I ran get_descriptor for descriptors 1 through 128 inclusive, indexing
> 0 through 8 incl. These units, except for descriptor 3, will always
> return the same value regardless of index so I'm guessing that the
> descriptor index is ignored for the most part. However, for descriptor
> 3, index 0 returns data; indices 1 through 3 produce a "Connection
> timed out" error, and any other indices produce "Broken pipe", which is
> also the error returned by non-supported descriptors.
>
> The real data seems to be in descriptor 0x22 (see below). Does this
> data look similar enough to an existing unit that's supported for me to
> try an existing driver? If not, how do I go about trying to decode the
> data?
>
> Thanks,
> Eric
>
> --------------- get_descritor output ---------------
>
> Bus 002 device 008 configuration 1 interface 0 altsetting 0 endpoint
> 128 descriptor 0x01 index 0:
>
> 12 01 00 01 00 00 00 08 9f 0d 01 00 00 01 01 02 03 01
>
> ..................
> Bus 002 device 008 configuration 1 interface 0 altsetting 0 endpoint
> 128 descriptor 0x02 index 0:
>
> 09 02 22 00 01 01 00 40 00 09 04 00 00 01 03 00 00 00 09 21 00 01 00
> 01
> 22 af 00 07 05 81 03 08 00 fa
>
> ..".... at ...........!....".........
> Bus 002 device 008 configuration 1 interface 0 altsetting 0 endpoint
> 128 descriptor 0x03 index 0:
>
> 04 03 09 00
>
> ....
> Can't get endpoint 128 descriptor 0x03 index 1: error sending control
> message: Connection timed out
> Can't get endpoint 128 descriptor 0x03 index 2: error sending control
> message: Connection timed out
> Can't get endpoint 128 descriptor 0x03 index 3: error sending control
> message: Connection timed out
> Can't get endpoint 128 descriptor 0x03 index 4: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x03 index 5: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x03 index 6: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x03 index 7: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x03 index 8: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x04 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x05 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x06 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x07 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x08 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x09 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x0a index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x0b index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x0c index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x0d index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x0e index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x0f index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x10 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x11 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x12 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x13 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x14 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x15 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x16 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x17 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x18 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x19 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x1a index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x1b index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x1c index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x1d index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x1e index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x1f index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x20 index 0: error sending control
> message: Broken pipe
> Bus 002 device 008 configuration 1 interface 0 altsetting 0 endpoint
> 128 descriptor 0x21 index 0:
>
> 09 21 00 01 00 01 22 af 00
>
> .!...."..
> Bus 002 device 008 configuration 1 interface 0 altsetting 0 endpoint
> 128 descriptor 0x22 index 0:
>
> 05 02 09 04 a1 01 05 02 85 07 95 01 75 08 15 00 26 ff 00 09 86 b1 02
> 85
> 08 09 87 b1 02 85 01 95 02 09 83 09 85 81 02 09 10 a1 00 85 01 09 36
> 09
> 30 15 00 26 ff 00 95 02 75 08 81 02 95 01 75 18 27 ff ff ff 00 09 84
> 81
> 02 c0 05 02 09 16 a1 00 09 1a a1 00 26 ff 00 85 03 75 08 95 02 09 32
> 09
> 30 81 02 c0 09 1c a1 00 75 08 95 05 09 30 09 35 09 81 09 82 09 32 81
> 02
> c0 85 05 25 06 15 00 75 08 95 01 09 58 b1 02 85 02 25 02 15 01 09 68
> b1
> 02 85 04 26 ff 00 15 00 09 57 b1 02 85 06 95 01 75 18 27 ff ff 0f 00
> 15
> 00 09 56 b1 02 c0 c0
>
> ............u...&.............................6.0..&....u.....u.'.......
> ............&....u....2.0.......u....0.5.....2.....%...u....X....%....h.
> ...&.....W......u.'.......V....
> Can't get endpoint 128 descriptor 0x23 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x24 index 0: error sending control
> message: Broken pipe
> Can't get endpoint 128 descriptor 0x25 index 0: error sending control
> message: Broken pipe
>
>
>
> ____________________________________________________________________________________
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail beta.
> http://new.mail.yahoo.com
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
>
More information about the Nut-upsdev
mailing list