| Author | Message | ||
|---|---|---|---|
< Device Information ~ Franklin u210 |
|||
|
|||
| Posts: 3Joined: Fri Apr 02, 2010 1:33 am |
I have a Franklin u210 in my hands, and as usual it needs to be modeswitched to run on our beloved Linux.
Here's the config: Code: ########################################################
# Franklin Wireless U210 DefaultVendor= 0x1fac DefaultProduct= 0x0130 TargetVendor= 0x1fac TargetProduct= 0x0131 CheckSuccess=20 MessageContent="55534243b82e238c24000000800108df200000000000000000000000000000" Tested on Ubuntu 9.10 and OpenWrt trunk. Enjoy! -Adam J. Porter |
||
| Top |
 
|
||
|
|||
| Site AdminPosts: 6289Joined: Sat Nov 03, 2007 12:30 am |
Great, thanks a lot!
Will be in the next release (soon). Is that a serial device or does it do CDC/ACM after switching ? |
||
| Top |
|
||
|
|||
| Posts: 3Joined: Fri Apr 02, 2010 1:33 am |
It's a serial device, worked with option driver but not with usbserial-generic.
Active port is +1, eg /dev/ttyUSB1 |
||
| Top |
|
||
|
|||
| Posts: 15Joined: Fri Apr 09, 2010 10:46 pm |
I should know .. but .. can someone guide me on how one identifies active port?
|
||
| Top |
|
||
|
|||
| Site AdminPosts: 6289Joined: Sat Nov 03, 2007 12:30 am |
pdc_2 wrote: .. can someone guide me on how one identifies active port? If a device provides several ttyUSB ports the "active" port (used for the actual ppp connection) has interrupt transfer type contrary to bulk transfer type.
You simply do a "lsusb -v -d <vendid>:<prodid>" and look for the interface with the right transfer type. The interface number does not necessarily correspond with the ttyUSB number; therefore you have to climb into the usbfs under /sys/bus/usb/devices. There are folders for every interface number, and a ttyUSBx subfolder inside (if the "option" module was bound correctly). |
||
| Top |
|
||
|
|||
| Posts: 15Joined: Fri Apr 09, 2010 10:46 pm |
many thanks; I will investigate this with a couple of my modems; I greatly appreciate this
so with a 3565-Z that has been flipped I get (lsusb) 19d2:0063 ONDA Communication s.p.A. I type lsusb -v -d <19d2>:<0063> and I get: bash: syntax error near unexpected token '63' and for lsusb -v -d <0x19d2>:<0x0063> bash: syntax error near unexpected token 'new line' grateful for pointers |
||
| Top |
|
||
|
|||
| Site AdminPosts: 6289Joined: Sat Nov 03, 2007 12:30 am |
The "<" and ">" chars denote a placeholder. Just leave them out:
lsusb -v -d 19d2:0063 The "0x" hexadecimal indicator is optional for lsusb parameters. |
||
| Top |
|
||
|
|||
| Posts: 15Joined: Fri Apr 09, 2010 10:46 pm |
thanks;
worked well; and did echo $TEXT > lsusb.txt to copy to file to read later in gedit; I get this Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 so will research further; if you can make any comments on this, happy to hear them my longterm thought was to gain some grasp of why particular ttyUSB ports are selected |
||
| Top |
|
||
|
|||
| Site AdminPosts: 6289Joined: Sat Nov 03, 2007 12:30 am |
You should get a lot more output from lsusb. The more direct way to save it in a text file is:
lsusb -v -d 19d2:0063 > lsusb.txt There should be at least two or three interfaces listed. |
||
| Top |
|
||
|
|||
| Posts: 15Joined: Fri Apr 09, 2010 10:46 pm |
lsusb.txt gives
Code: Bus 001 Device 004: ID 19d2:0063 ONDA Communication S.p.A.
Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x19d2 ONDA Communication S.p.A. idProduct 0x0063 bcdDevice 0.00 iManufacturer 2 iProduct 1 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 161 bNumInterfaces 6 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 3 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 4 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x87 EP 7 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 5 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x06 EP 6 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x88 EP 8 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 |
||
| Top |
|
||
|
|||
| Site AdminPosts: 6289Joined: Sat Nov 03, 2007 12:30 am |
There you have it:
Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 4 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 3 Transfer Type Interrupt So it's interface 4 out of 5. Now find the corresponding folder in /sys/bus/usb/devices. |
||
| Top |
|
||
|
|||
| Posts: 15Joined: Fri Apr 09, 2010 10:46 pm |
how can I attach 2 screenshots please to show you the results:
|
||
| Top |
|
||
|
|||
| Site AdminPosts: 6289Joined: Sat Nov 03, 2007 12:30 am |
No local attachments possible, sorry. But you can include external pics via the [img] BBCode.
|
||
| Top |
|
||
|
|||
| Posts: 7Joined: Wed Jan 19, 2011 3:15 am |
aport wrote: I have a Franklin u210 in my hands, and as usual it needs to be modeswitched to run on our beloved Linux.
Here's the config: Code: ######################################################## # Franklin Wireless U210 DefaultVendor= 0x1fac DefaultProduct= 0x0130 TargetVendor= 0x1fac TargetProduct= 0x0131 CheckSuccess=20 MessageContent="55534243b82e238c24000000800108df200000000000000000000000000000" Tested on Ubuntu 9.10 and OpenWrt trunk. Enjoy! -Adam J. Porter I am trying to install the same device on my Ubuntu 10.10 64bit and it does not create a modem device (no /dev/ttyUSB? no ttyACM). I have usb-modeswitch 1.1.4-1 installed that has support for device 1fac:0130 however when I use lsusb I find it under 1fac:0032 Is there a quick hack for the config file? can I just copy the /etc/usb_modeswitch.d/1fac:0130 to /etc/usb_modeswitch.d/1fac:0032 and change some numbers? What do I deed to do to get this Franklin U210 working? Thanks! |
||
| Top |
|
||
|
|||
| Site AdminPosts: 6289Joined: Sat Nov 03, 2007 12:30 am |
Yes, you can try to just copy the existing file as you proposed. You need to change the value for "DefaultProduct" to "0x0032". Then try the new file manually (as root or with sudo):
Code: # usb_modeswitch -I -c /etc/usb_modeswitch.d/1fac:0032 It will likely work, but there is no guarantee the switching procedure is identical to the other model.
If you are successful you can make the switching automatic by adding a rule line to "/lib/udev/rules.d/40-usb_modeswitch.rules". It's pretty straightforward if you look into it. |
||
| Top |
|
||
All times are UTC + 1 hour [ DST ]
Users browsing this forum: No registered users and 0 guests
| You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum |