ZTE 8710 with IPCOP 1.9.15 (2.0)

richtech · Post by **richtech** » 07 Sep 2010, 14:28

The version of usb_modeswitch is 1.1.3 but the 3g Modem ZTE 8710 is not listed. am having problem getting the modem to switch.
the hw ID is 19d2:FFFF.
even after the switch in winxp with SniffUSB 2.0 the hw address is still the same with a sub address of 0000 for the modem.
But i have the log from SniffUSb if it will help.

Post by **Josh** » 07 Sep 2010, 18:09

The ZTE AC8710 should be supported, but there are several variants.

Are you sure it is not switched already? 19d2:ffff is known to be the target ID after switching.

To be sure, I would like to see the output of "lsusb -v -d 19d2:ffff". You can post it here in full, I can edit it afterwards to remove non-relevant parts.

richtech · Post by **richtech** » 08 Sep 2010, 08:40

Bus 003 Device 004: ID 19d2:ffff ONDA Communication S.p.A.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x19d2 ONDA Communication S.p.A.
idProduct 0xffff
bcdDevice 0.00
iManufacturer 1 ZTE, Incorporated
iProduct 2 USB Storage
iSerial 3 000000000002
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

Post by **Josh** » 08 Sep 2010, 10:45

O.K., thanks. We seem to have a new device variant here.

I recommend you install version 1.1.4, with data package 20100826. Contrary to version 1.1.3 it is "boot-proof".

Copy the file "/etc/usb_modeswitch.d/19d2:fff6" to
"/etc/usb_modeswitch.d/19d2:ffff".

Open it in an editor. Leave the "MessageContent" line (and below) as it is. Change the other stuff so that it looks like this:

Code: Select all

########################################################
# ZTE "fff" devices 3

DefaultVendor= 0x19d2
DefaultProduct=0xffff

TargetClass=0xff

MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"

CheckSuccess=20

Then, add these lines to /lib/udev/rules.d/40-usb_modeswitch.rules, preferably close to the other similar lines:

Code: Select all

# ZTE "fff" devices 3
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="ffff", RUN+="usb_modeswitch '%b/%k'"

These changes should get your device going.

If things don't work as expected, switch on logging as indicated on the usb_modeswitch doc page, paragraph "Troubleshooting".

richtech · Post by **richtech** » 08 Sep 2010, 13:02

Gee, thanks its working now. Then with modprobe usbserial, I got ttyUSB0 to 3.

That is perfect.

Post by **Josh** » 08 Sep 2010, 22:23

Your IPCOP version has a modern kernel so you should not need to load "usbserial". The better choice is the "option" driver which is optimized for high-speed wireless modems.

If usb_modeswitch was successful with switching, it will try to load the "option" module and even add a convenience link to the right port for connection.

If you see a symbolic link file "gsmmodem" in the /dev folder, this procedure has worked well.
If not, check if you have the module ("modprobe -v option").

richtech · Post by **richtech** » 10 Sep 2010, 10:28

Actually am trying to us IPcop 1.4.21 which is the current stable version as against 2.0. also I NEED to use UpdateAccelerator

very important for my 3g broadband (or its my money the ISP will use for beer monthly

So question is there a binary ready for ipcop 2.4 kernel? the version I got is 0.9

Post by **Josh** » 10 Sep 2010, 11:35

It was and is my intention to keep the binary switching tool separated from the rest of the "framework", with very few assumptions about the system version. So it does work with embedded and pretty dated systems as well. You can use the latest version with no problem.

Things are different with the udev rules and the dispatcher. They assume that a certain minimum udev version is installed and are using the /sys tree quite a bit which is a 2.6 addition if I'm not mistaken.

You might have to set up your own udev rule calling the usb_modeswitch binary directly, which can use the matching config file from the data package.