Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-26 Thread Nicolas Will 



On Fri, 22 Jun 2007 20:00:15 +0100, Nicolas Will <[EMAIL PROTECTED]> wrote:
> So, what brand/model is known to work without fuss for DVB-T, and is
> widely available in the UK (Aberdeen, Scotland in particular?

I bought a Freecom stick from the local PCWorld, and it worked immediately 
without fuss with the recent HG code installed on my machine.

Great! Thanks to the developpers! A beer is on me to any who passes by Aberdeen.

The offer to make the ADSTech stick available still stands.

Nico


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-22 Thread Nicolas Will 
On Mon, 2007-06-11 at 09:39 +0100, Michel Ludwig wrote:
> What I can tell you from personal experience is that the short stick
> antenna 
> is *not* sufficient to receive DVB-T correctly in my place
> (uk-WinterHill). 
> You could try to connect a roof antenna to your stick and then see
> whether 
> you can get a correct reception in Windows. And after that is working
> you 
> could try it out in Kaffeine. 


OK, I have tried the tuner at my new house.

There is a roof antenna that was connected to a DVB-T box tuner for a
regular TV. I do not have a TV to test it, but I can assume that it was
working.

I plugged the dvb-t usb stick, launched Kaffeine, did a full AUTO scan,
and got nothing again.

I have attached a sample of the outputs.

I can help debug the thing, and when the container arrives with the rest
of my computer stuff, and when I have Internet, I can even give some
account and remote access.

But in the mean time, I might as well buy something that works right out
of the box. The current tuner I have was a gift, a new one is not that
expensive. 

So, what brand/model is known to work without fuss for DVB-T, and is
widely available in the UK (Aberdeen, Scotland in particular?

Thanks for any help,

Nico
Kaffeine output sample
==


Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 82600 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 54/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 83400 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 55/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 84200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 56/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 85000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 57/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 85800 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 58/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 86600 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 59/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 87400 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 60/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 88200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 61/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 89000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 62/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 89800 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 63/63

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Transponders: 63
dvbsi: The end :)
Channels found: 0





Kernel output sample




Jun 22 19:24:47 youkaida kernel: [ 1059.424000] tm6000: got start feed request 
tm6000_start_feed
Jun 22 19:24:47 youkaida kernel: [ 1059.424000] tm6000: got start stream 
request tm6000_start_stream
Jun 22 19:24:47 youkaida kernel: [ 1059.44] tm6000: pipe resetted
Jun 22 19:24:48 youkaida kernel: [ 1059.784000] 10
Jun 22 19:24:49 youkaida kernel: [ 1060.784000] 10
Jun 22 19:24:50 youkaida kernel: [ 1061.784000] 10
Jun 22 19:24:51 youkaida kernel: [ 1062.784000] 10
Jun 22 19:24:52 youkaida kernel: [ 1063.784000] 10
Jun 22 19:24:53 youkaida kernel: [ 1064.728000] tm6000: got stop feed request 
tm6000_stop_feed
Jun 22 19:24:53 youkaida kernel: [ 1064.744000] tm6000: status != 0
Jun 22 19:24:53 youkaida kernel: [ 1064.848000] should set frequency 85800
Jun 22 19:24:53 youkaida kernel: [ 1064.848000] and bandwith 0
Jun 22 19:24:54 youkaida kernel: [ 1066.368000] setting frequency d5e0
Jun 22 19:24:54 youkaida kernel: [ 1066.368000] setting frequency d5 e0
Jun 22 19:24:54 youkaida kernel: [ 1066.416000] demodulator status: 
FE_HAS_CARRIER 2 
Jun

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-11 Thread Nicolas Will 
On Mon, 2007-06-11 at 09:39 +0100, Michel Ludwig wrote:

> 
> What I can tell you from personal experience is that the short stick antenna 
> is *not* sufficient to receive DVB-T correctly in my place (uk-WinterHill). 
> You could try to connect a roof antenna to your stick

That I will do. I just hope that my temporary apartment has a roof
antenna, it come with satellite for TV.


>  and then see whether 
> you can get a correct reception in Windows. And after that is working you 
> could try it out in Kaffeine.

For this, I would need a Windows machine, which I do not possess...

Nico


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-11 Thread Michel Ludwig 
On Monday 11 June 2007 09:20:37 Nicolas Will wrote:
> Well, I have not met the expected success.
>
> So, here is what I have done, once I have connected the antenna that
> came with the tuner (short stick, nothing like a roof antenna, which may
> be a reason for the current failure):
>
>  1. Open Kaffeine
>  2. go to the DVB menu
>  3. search on is set to "AUTO", offset is 0
>  4. start scan
>  5. -> get no channel
>  6. Change the search to uk-Durris, which is supposed to be by
> emitter for Aberdeen, Scotland
>  7. Scan again
>  8. -> get no channel
>  9. redo both scans on AUTO and uk-Durris with all offsets set (0,
> +167, -167)
> 10. -> get no channel
>
> Most of the time the "Lock" indicator is green, rarely off.

That's because the lock signal is currently faked, i.e. it will always 
indicate a correct "lock".

> I have some messages from syslog and kaffeine that I will paste at the
> end of the message.
>
> I'll test anything and can provide any additional information asked.

What I can tell you from personal experience is that the short stick antenna 
is *not* sufficient to receive DVB-T correctly in my place (uk-WinterHill). 
You could try to connect a roof antenna to your stick and then see whether 
you can get a correct reception in Windows. And after that is working you 
could try it out in Kaffeine.


Thanks,

Michel

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-11 Thread Nicolas Will 
On Fri, 2007-06-08 at 14:42 +0100, Michel Ludwig wrote:
> 
> It looks good so far, but you definitely need an antenna! :-)

Michel, and all other dvb hackers,

Well, I have not met the expected success.

So, here is what I have done, once I have connected the antenna that
came with the tuner (short stick, nothing like a roof antenna, which may
be a reason for the current failure):

 1. Open Kaffeine
 2. go to the DVB menu
 3. search on is set to "AUTO", offset is 0
 4. start scan
 5. -> get no channel
 6. Change the search to uk-Durris, which is supposed to be by
emitter for Aberdeen, Scotland
 7. Scan again
 8. -> get no channel
 9. redo both scans on AUTO and uk-Durris with all offsets set (0,
+167, -167)
10. -> get no channel

Most of the time the "Lock" indicator is green, rarely off.

I have some messages from syslog and kaffeine that I will paste at the
end of the message.

I'll test anything and can provide any additional information asked.

Thanks,

Nico


[EMAIL PROTECTED]:~$ kaffeine 
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
0
/dev/dvb/adapter0/frontend0 : opened ( Zarlink ZL10353 DVB-T )
/dev/dvb/adapter0/frontend1 : : No such file or directory
/dev/dvb/adapter1/frontend0 : : No such file or directory
QLayout "unnamed" added to QWidget "unnamed", which already has a layout
[EMAIL PROTECTED]:~$ DvbCam::probe(): /dev/dvb/adapter0/ca0: : No such file
or directory
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 401833000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 1/189

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 40200 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 2/189

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 402167000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 3/189

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 409833000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 4/189

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 41000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 5/189

Invalid section length or timeout: pid=17


Invalid section length or timeout: pid=0

Frontend closed
Using DVB device 0:0 "Zarlink ZL10353 DVB-T"
tuning DVB-T to 410167000 Hz
inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
. LOCKED.
Transponders: 6/189

Invalid section length or timeout: pid=17

Frontend closed




Jun  9 17:36:49 youkaida kernel: [ 1706.792000] 10
Jun  9 17:36:50 youkaida kernel: [ 1707.792000] 10
Jun  9 17:36:51 youkaida kernel: [ 1708.792000] 10
Jun  9 17:36:52 youkaida kernel: [ 1709.456000] tm6000: got stop feed
request tm6000_stop_feed
Jun  9 17:36:52 youkaida kernel: [ 1709.472000] tm6000: status != 0
Jun  9 17:36:52 youkaida kernel: [ 1709.576000] should set frequency
65800
Jun  9 17:36:52 youkaida kernel: [ 1709.576000] and bandwith 0
Jun  9 17:36:53 youkaida kernel: [ 1711.096000] setting frequency a3e0
Jun  9 17:36:53 youkaida kernel: [ 1711.096000] setting frequency a3 e0
Jun  9 17:36:53 youkaida kernel: [ 1711.144000] demodulator status:
FE_HAS_CARRIER 2 
Jun  9 17:36:53 youkaida kernel: [ 1711.144000] demodulator status:
FE_HAS_VITERBI 4 
Jun  9 17:36:53 youkaida kernel: [ 1711.144000] demodulator status:
FE_HAS_LOCK 16 
Jun  9 17:36:53 youkaida kernel: [ 1711.144000] demodulator status:
FE_HAS_SYNC 8 
Jun  9 17:36:53 youkaida kernel: [ 1711.144000] demodulator status:
FE_HAS_SIGNAL 1 
Jun  9 17:36:53 youkaida kernel: [ 1711.144000] tm6000: got start feed
request tm6000_start_feed
Jun  9 17:36:53 youkaida kernel: [ 1711.144000] tm6000: got start stream
request tm6000_start_stream
Jun  9 17:36:53 youkaida kernel: [ 1711.148000] 10
Jun  9 17:36:53 youkaida kernel: [ 1711.16] tm6000: pipe resetted
Jun  9 17:36:53 youkaida kernel: [ 1711.20] 10
Jun  9 17:36:54 youkaida kernel: [ 1711.792000] 10
Jun  9 17:36:55 youkaida kernel: [ 1712.792000] 10
Jun  9 17:36:56 youkaida kernel: [ 1713.792000] 10
Jun  9 17:36:57 youkaida kernel: [ 1714.792000] 10
Jun  9 17:36:58 youkaida kernel: [ 1715.792000] 10
Jun  9 17:36:59 youkaida kernel: [ 1716.448000] tm6000: got stop feed
request tm6000_stop_feed
Jun  9 17:36:59 youkaida kernel: [ 1716.464000] tm6000: status !=

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-08 Thread Michel Ludwig 
On Friday 08 June 2007 14:37:12 Nicolas Will wrote:
> On Fri, 2007-06-08 at 14:13 +0100, Nicolas Will wrote:
> > On Fri, 2007-06-08 at 14:01 +0100, Michel Ludwig wrote:
> > > This device should be another candidate for the TM6000 driver. The only
> > > problem is that I don't have much time at the moment to work on it. But
> > > I can try to add your device to the driver as it is now, and it could
> > > be the case that you could use the DVB-T of your device already now.
> >
> > Compiling now... But it will probably fail due to the wrong USB Id I
> > guess.
>
> It did not work.

Yes, that's ok.

> But I wnt into the source, changed the USB Ids, recompiled, installed,
> got the formware files in the right place, plugged the stick and, after
> a lot of firmware loading output:
>
> Jun  8 14:32:53 youkaida kernel: [16414.036000] tm6000:
> firmware2 transmitted
> Jun  8 14:32:53 youkaida kernel: [16414.964000] 7f
> Jun  8 14:32:53 youkaida kernel: [16414.98] DVB: registering
> new adapter (Trident TVMaster 6000 DVB-T)
> Jun  8 14:32:53 youkaida kernel: [16414.98] DVB: registering
> frontend 0 (Zarlink ZL10353 DVB-T)...
> Jun  8 14:32:53 youkaida kernel: [16414.98] usbcore:
> registered new interface driver tm6000
>

Alright, that's what I intended to do as well.

> Kaffeine sees the thing.
>
> I hate myself for not having an antenna right here and now.
>
> I will report of total success or last minute failure tomorrow.

It looks good so far, but you definitely need an antenna! :-)


Michel

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-08 Thread Nicolas Will 
On Fri, 2007-06-08 at 14:13 +0100, Nicolas Will wrote:
> On Fri, 2007-06-08 at 14:01 +0100, Michel Ludwig wrote:
> 
> > 
> > This device should be another candidate for the TM6000 driver. The only 
> > problem is that I don't have much time at the moment to work on it. But I 
> > can 
> > try to add your device to the driver as it is now, and it could be the case 
> > that you could use the DVB-T of your device already now.
> 
> Compiling now... But it will probably fail due to the wrong USB Id I
> guess.


It did not work.

But I wnt into the source, changed the USB Ids, recompiled, installed,
got the formware files in the right place, plugged the stick and, after
a lot of firmware loading output:

Jun  8 14:32:53 youkaida kernel: [16414.036000] tm6000:
firmware2 transmitted
Jun  8 14:32:53 youkaida kernel: [16414.964000] 7f
Jun  8 14:32:53 youkaida kernel: [16414.98] DVB: registering
new adapter (Trident TVMaster 6000 DVB-T)
Jun  8 14:32:53 youkaida kernel: [16414.98] DVB: registering
frontend 0 (Zarlink ZL10353 DVB-T)...
Jun  8 14:32:53 youkaida kernel: [16414.98] usbcore:
registered new interface driver tm6000


Kaffeine sees the thing.

I hate myself for not having an antenna right here and now.

I will report of total success or last minute failure tomorrow.

Thanks again.

Nico



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-08 Thread Nicolas Will 
On Fri, 2007-06-08 at 14:01 +0100, Michel Ludwig wrote:

> 
> This device should be another candidate for the TM6000 driver. The only 
> problem is that I don't have much time at the moment to work on it. But I can 
> try to add your device to the driver as it is now, and it could be the case 
> that you could use the DVB-T of your device already now.

Compiling now... But it will probably fail due to the wrong USB Id I
guess.

DVB-T is most of what I want. Analog is just bonus if it ever comes.

Thanks for the answer!

Nico


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-08 Thread Michel Ludwig 
On Friday 08 June 2007 12:30:21 Nicolas Will wrote:
> I've used Google, the wiki, the mailing list archives and failed to find
> my answer.
>
> I have one ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick.
>
> After a bit of plastic surgery, I found the following inside:
>   * Philips TDA9830T - TV sound AM-demodulator and audio source
> switch
>   * Trident TVMaster TM6000 - Audio codec, Video decode, USB 2.0
> Bridge
>   * XCEIVE XC3028 analog and digital TV Tuner
>   * Zarlink (now Intel) ZL10353 DVB-T demodulator
>   * 24LC641SN
>   * LBNJ N208 601
>
> I have posted pictures here:
> http://www.youplala.net/v/nicolas/computer/htpc/adstechminidualtv/
>
> On the picture page, you can find links to the product pages, and evena
> datasheet for the Philips component.
>
> My lsusb info will be at the end of the post.
>
> I have today's v4l-dvb-experimental compiled in.
>
> Do I have any hope of using this device on Linux?
>
> If not yet, what can I provide to help, outside of code?

This device should be another candidate for the TM6000 driver. The only 
problem is that I don't have much time at the moment to work on it. But I can 
try to add your device to the driver as it is now, and it could be the case 
that you could use the DVB-T of your device already now.

http://linuxtv.org/v4lwiki/index.php/TM6000


Michel

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick

2007-06-08 Thread Nicolas Will 
Hi,

I've used Google, the wiki, the mailing list archives and failed to find
my answer.

I have one ADSTech Mini DualTV Hybrid Analog-DVB-T USB stick.

After a bit of plastic surgery, I found the following inside:
  * Philips TDA9830T - TV sound AM-demodulator and audio source
switch
  * Trident TVMaster TM6000 - Audio codec, Video decode, USB 2.0
Bridge
  * XCEIVE XC3028 analog and digital TV Tuner
  * Zarlink (now Intel) ZL10353 DVB-T demodulator
  * 24LC641SN 
  * LBNJ N208 601

I have posted pictures here:
http://www.youplala.net/v/nicolas/computer/htpc/adstechminidualtv/

On the picture page, you can find links to the product pages, and evena
datasheet for the Philips component.

My lsusb info will be at the end of the post.

I have today's v4l-dvb-experimental compiled in.

Do I have any hope of using this device on Linux?

If not yet, what can I provide to help, outside of code?

Thanks for any help.

Nico




~$ lsusb
Bus 005 Device 001: ID :  
Bus 002 Device 001: ID :  
Bus 004 Device 001: ID :  
Bus 003 Device 003: ID 0b97:7762 O2 Micro, Inc. Oz776 SmartCard Reader
Bus 003 Device 002: ID 0b97:7761 O2 Micro, Inc. 
Bus 003 Device 001: ID :  
Bus 001 Device 006: ID 06e1:b339 ADS Technologies, Inc. 
Bus 001 Device 002: ID 413c:a005 Dell Computer Corp. 
Bus 001 Device 001: ID :  






Bus 001 Device 006: ID 06e1:b339 ADS Technologies, Inc. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x06e1 ADS Technologies, Inc.
  idProduct  0xb339 
  bcdDevice0.01
  iManufacturer  16 ADS
  iProduct   32 Mini DualTV USB
  iSerial64 2.0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   78
bNumInterfaces  1
bConfigurationValue 1
iConfiguration 48 2004090820040908
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0 
  bInterfaceProtocol255 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x  1x 0 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   1
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0 
  bInterfaceProtocol255 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x1400  3x 0 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   2
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  0 
  bInterfaceProtocol255 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous