Posted: Mon Jun 04, 2012 19:05 Post subject: Problem with Cmotech CNU680 CDMA modem+wr1043
Spend a lot of time trying to use CNU 680 as wan connection. At lost i made it, but there is another problem. WAN bandwith is limited at 62 Kbyte/sec (stable line), I don't understand why. Trying another modem AnyData 520+DD-WRT - everything ok - up to 200 Kbyte. Trying OpenWRT+CNU680 - also no bandwith limit, but not stable connection.
In windows modems work good.
What I do:
Flash r18777,
usb_modeswitch -v 0x16d8 -p 0x6803 -m 0x07 -M 5553424308e0408524000000800008ff524445564348470000000000000000
and set in GUI protocol 3g dial #777 login, password. It's all, modem make a connection and all good except Internet speed.
How to view log of pppd, or what to do?
P.S sory for my english
There is probably a combination of reasons for the low speed, one is that the modem is not supported by the option driver which normally improves the performance compared to only using usb-serial.
Your modeswitch message doesn't look right either, give me the output from "cat /proc/bus/usb/devices", first without running the modeswitch command and then once again after the modeswitch command.
Where did you get that modeswitch message?
Your AnyData modem is supported in the option driver so no surprise that it is faster. _________________ Kernel panic: Aiee, killing interrupt handler!
I don't remember where i get this string.
There is another one wich also work, and the speed is also low, the modem is attached as ttyACM0, and i should start pppd manual
I wonder what driver OpenWRT are using since you are getting much higher speed there, you can do the same cat cmd or lsusb to see which driver is attached to the stick in OpenWRT.
The modem can, as you have noticed, be switched into presenting itself as a cdc device by using a different modeswitch message.
You should remove the endpoint specification (-m 0x07) from your message, that switch is only for testing and should never be needed for normal use since the usb_modeswitch routine will automatically detect that the stick has switch to modem mode without the need for an endpoint to be specified.
Here is a link to a thread in the usb_modeswitch forum for this stick, you could try the messages listed there to see if they make any difference. I guess the message with the extra "31" inside will set it to cdc mode.
The CMOTECH series of modems will soon be supported in dd-wrt and I intend to add support for them in the option driver unless they work better in cdc mode.
In such case they will get modeswitch messages for cdc mode instead of option serial mode.
It would be good if you can show me an interface list for each of the other 3 messages (yours cdc + the 2 messages from the usb_modeswitch forum.
There is not much info on the net about these modems so any input is appreciated. _________________ Kernel panic: Aiee, killing interrupt handler!
Thank you for you help. I don't undarstand what happens, but everything is working now. I use my second command to switch modem in ttyACM0 and start connection manual, and everything work, speed is about 2mbit/s. Here is working command
usb_modeswitch -v 0x16d8 -p 0x6803 -M 555342435c00000009000000000
00aff524445564348473100000000000000
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 003 on bus 001 ...
Using endpoints 0x07 (out) and 0x86 (in)
Using endpoints 0x07 (out) and 0x86 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached
SCSI inquiry data (for identification)
-------------------------
Vendor String: CMOTECH
Model String: Mass Storage
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: CMOTECH CO., LTD.
Product: USB Mass Storage
Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x07 for message sending ...
Trying to send message 1 to endpoint 0x07 ...
Sending the message returned error -4. Trying to continue
Resetting response endpoint 0x86
Error resetting endpoint: -4
Resetting message endpoint 0x07
Error resetting endpoint: -4
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.
next
root@DD-WRT:~# usb_modeswitch -v 0x16d8 -p 0x6803 -M 555342431234567824000000800
008ff524445564348473100000000000000
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 005 on bus 001 ...
Using endpoints 0x07 (out) and 0x86 (in)
Using endpoints 0x07 (out) and 0x86 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached
SCSI inquiry data (for identification)
-------------------------
Vendor String: CMOTECH
Model String: Mass Storage
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: CMOTECH CO., LTD.
Product: USB Mass Storage
Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x07 for message sending ...
Trying to send message 1 to endpoint 0x07 ...
Sending the message returned error -4. Trying to continue
Resetting response endpoint 0x86
Error resetting endpoint: -4
Resetting message endpoint 0x07
Error resetting endpoint: -4
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.
last
root@DD-WRT:~# usb_modeswitch -v 0x16d8 -p 0x6803 -M 555342431234567824000000800008ff524445564348470000000000000000
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 007 on bus 001 ...
Using endpoints 0x07 (out) and 0x86 (in)
Using endpoints 0x07 (out) and 0x86 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached
SCSI inquiry data (for identification)
-------------------------
Vendor String: CMOTECH
Model String: Mass Storage
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: CMOTECH CO., LTD.
Product: USB Mass Storage
Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x07 for message sending ...
Trying to send message 1 to endpoint 0x07 ...
Sending the message returned error -4. Trying to continue
Resetting response endpoint 0x86
Error resetting endpoint: -4
Resetting message endpoint 0x07
Error resetting endpoint: -4
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.
Modeswitch in 1st and 2nd time is work normal, there some errors, but modem switched and work. I don't know why it was not worked before.
May be you can help me one more time? There is a lot of errors in ppp:
ppp0 Link encap:Point-to-Point Protocol
, what to do with it, where to see it, or may be it's normal?
And how to make connection and modeswitch automatically. Ican not to edit nvram parameter (nvram set 3gdata="/dev/ttyACM0"), it in a few second become 3gdata=/dev/usb/tts/0.
And after rebooting modem i need to write a file ppp.conf to tmp dir. I can't make jffs, there is no free space.
P.S. thanks for you help one more time
Ok, so it works well with the cdc-acm driver, I will then add support for it as a cdc device.
The number of receive errors you have is nothing to worry about, 5000 error packets out of 12 millions is less than 0.05%..
The reason why your 3gdata variable gets changed is due to the connection watchdog in combination with the modem not being supported yet in dd-wrt and you can probably fix this by killing the connection watchdog.
do a ps cmd and find the pid for the process, looks like this:
995 root 1256 S /tmp/ppp/redial 30
and then kill -9 995
in ps you will also see:
19639 root 1436 S pppd file /tmp/ppp/options.pppoe
which you also can kill, edit the options.pppoe file and then restart pppd.
This file is for pppoe WAN connecion type but I think the same file is also used for 3G. _________________ Kernel panic: Aiee, killing interrupt handler!
