Re: Confirm E3131 modeswitch to CDC mode?
Posted: 10 Feb 2013, 14:35
In to other word, I can not even switch to initial mode using usb_modeswitch?
Ok, I will try to reset using AT commands
Ok, I will try to reset using AT commands
Everything Linux and Modeswitching USB Devices
http://www.draisberghof.de/usb_modeswitch/bb/
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=1295
usb_modeswitch is made for switching from default mode (install mode) to target mode and not the other way around.ursus wrote:In to other word, I can not even switch to initial mode using usb_modeswitch?
Ok, I will try to reset using AT commands
I think you need to realize that the vendor never intended you to play with these commands at all. The only supported mode switching is the one done by the Windows software installed when the device is first plugged into a Windows machine. That is the only mode which is safe to use.Guest wrote:ursus, I tried the same command it works with me also and I have now Product ID 1c05.
Now the conclusion is that I have tree different ways to switch the usb modem to serial port each one has different target Product ID
12d1:1001 (using MessageContent 55534243123456780000000000000011060000000000000000000000000000)
12d1:1442 (Using http://192.168.1.1/html/switchProjectMode.html)
12d1:1c05 (Using At Cmd AT^U2DIAG=0)
If as LOM said 1442 serial port interfaces are for maintenance and and diagnostics purpose.
Why their exist both 1001 and 1c05 ?
Why the modem didn't convert from cdc ethernet (12d1:1f01) to target (12d1:14db) when using MessageContent 55534243123456780000000000000011060000000000000000000000000000, as LOM said, but instead (12d1:1001) ?
What if switchProjectMode is not exists and I can't use command like AT^U2DIAG=0, how can I know that a specific MessageContent can be used to convert the modem to serial ports (if no way is known to let the windows driver to convert it manually to serial port mode), I mean is it just tring different MessageContent and see the result ?
Code: Select all
Taking all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.5 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x1f01
TargetVendor= 0x12d1
TargetProduct= 0x1442
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011060000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice enabled (default)
Success check disabled
System integration mode disabled
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_devices: Found 008 on 001
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
Looking for target devices ...
searching devices, found USB ID 12d1:1f01
found matching vendor ID
searching devices, found USB ID 7392:7811
searching devices, found USB ID 05e3:0608
searching devices, found USB ID 0424:ec00
searching devices, found USB ID 0424:9512
searching devices, found USB ID 1d6b:0002
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 12d1:1f01
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 7392:7811
searching devices, found USB ID 05e3:0608
searching devices, found USB ID 0424:ec00
searching devices, found USB ID 0424:9512
searching devices, found USB ID 1d6b:0002
Found device in default mode, class or configuration (1)
Accessing device 008 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
No driver found. Either detached before or never attached
SCSI inquiry data (for identification)
-------------------------
Vendor String: HUAWEI
Model String: Mass Storage
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI HiLink
Serial No.: not provided
-------------------------
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
-> Run lsusb to note any changes. Bye.
Code: Select all
usb_modeswitch -W -I -v 12d1 -p 1f01 -V 12d1 -P 1001 -M "55534243123456780000000000000011060000000000000000000000000000"
Code: Select all
Bus 001 Device 008: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Code: Select all
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Modem Type = Analog Modem
Baud = 460800
New PPPD = yes
Modem = /dev/ttyUSB0
ISDN = 0
[Dialer umts]
Dial Command = ATD
Carrier Check = no
Phone = *99#
Username = internet
Password = t-d1
Stupid Mode = 1
Init4 = AT+CGDCONT=1,"IP","internet.t-d1.de"
Dial Attempts = 3
Code: Select all
wvdial --config=/etc/wvdial.conf umts