Nut upsdev - Feb 2007 - PowerCom USB units...

Greetings all,

Anyone done any work on these products?  I have several (a couple of
different models) that are rebranded Ultra in the US.  Using explore
with usbhid returns some significant quantities of data and I've done
some captures with usbsnoop.  I've also asked Ultra to get me the HID
definition that was used for them, in the hopes I don't have to
usbsniff all the setting variable mapping and control ops.

Best regards,
Eric


 
____________________________________________________________________________________
Finding fabulous fares is fun.  
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel
bargains.
http://farechase.yahoo.com/promo-generic-14795097

Hi Eric,
l?r 2007-02-03 klockan 06:29 -0800 skrev Eric Ashley:
> Greetings all,
> 
> Anyone done any work on these products?  I have several (a couple of
> different models) that are rebranded Ultra in the US.  Using explore
> with usbhid returns some significant quantities of data and I've done
> some captures with usbsnoop.  I've also asked Ultra to get me the HID
> definition that was used for them, in the hopes I don't have to
> usbsniff all the setting variable mapping and control ops.
Yes there is one project going on in the svn that may be of interest.

svn://svn.debian.org/svn/nut/branches/megatec-usb

Read the thread on upsuser Ablerex 625L USB verison.

Regards
Kjell

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

 .."....@...........!....".........
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