Made some small changes… Better results (I think)
Request International Mobile Equipment Identity, Check Network Registration and Signal Quality Report are showing okay!
My NEW /etc/config/network
config interface ‘3G’
option proto ‘3g’
option service ‘umts’
option apn ‘basic.internet.spmb.data’
option delegate ‘0’
option peerdns ‘0’
option dns ‘8.8.8.8’
option auto ‘0’
option device ‘/dev/ttyUSB2’
option username ‘’
option password ‘’
1: Request International Mobile Equipment Identity
root@domino:/etc/config# echo -e “AT+GSN \r\n” > /dev/ttyUSB2
root@domino:/etc/config# cat /dev/ttyUSB2
AT+GSN
861075021949474
OK
AT+GSN
861075021949474
OK
When you Request SIM’S ICCID,you get +CMD ERROR:3,from Quectel_UC20_AT_Commands_Manual_V1.5.pdf,the error 3 is Operation not allowed,I don’t this is why.If you can make sure you iuput command is right,I think the SIM-crad is not connect to MiFi,this is only suspect.From you next command result,I can confirm something.
When you Check Network Registration,you get +CREG:0,2,the number 2 is not we want,we want number is 1,from Quectel_UC20_AT_
Commands_Manual_V1.5.pdf,the number 2 mean Not registered, but ME is currently searching a new operator to register to.
So I think your SIM-card have problem connect to MiFi.
Thank you for taking the time to help us.
I will try to clean the SIM slot with some alcohol, and re-run the tests later.
If still no success I will order a new MiFi, (without the UC20) and test again.
Will report back later. Need to go to a party 1st
PS: As seen in my previous posts I did already correct the commands.
I think that the forum software in converting the "
This is looking better I think!
I did the test on USB3 and USB2
Still not able to make a working connection over 3g/umts!
Part of the logread at the end of this post.
/etc/config/network
config interface '3g'option proto '3g'option service 'umts'option apn 'basic.internet.spmb.data'option device '/dev/ttyUSB3'
1: Request International Mobile Equipment Identity
@guest, I think it is like this: you have to choose ttyUSB2 to send AT commands and use ttyUSB3 for data. Or you can do it reversely, i.e. use ttyUSB3 to send command and use ttyUSB2 for data. But don’t combine it. In your code, you are using both ttyUSB2 and ttyUSB3 to send AT command.
Sorry for the silence. I’m a bit busy at the moment and have no time to research this. Will pick it up later.
We have multiple issues going on here it seems.
First off your your QCCID command gives an error but in my case it reports success. I will post my output later when I have a chance to look at it.
Once you get beyond that stage you will run into PPP issues like I have. Upon studying the Quectel Linux USB Driver Guide in the downloads section a bit further it would see Quectel says it has specific dial scripts and PPP negotiation scripts like “quectel-chat-connect” and more that I cannot find anywhere on the internet nor in the downloads. This is from the manual:
Three scripts named as "quectel-ppp", "quectel-chat-connect" and "quectel-chat-disconnect". They are provided by Quectel in directory "linux-ppp-scripts". Depending on your product, you may need to make some changes. More information please refer to "linux-ppp-scripts\readme". You should copy "quectel-ppp", "quectel-chat-connect" and "quectel-chat-disconnect" to the directory "/etc/ppp/peers". Then you can start to set up PPP call by below command: pppd call quectel-ppp The process of dialing is shown as below (example of UC20): root@joe-OptiPlex-790:~# pppd call quectel-ppp pppd options in effect: debug # (from /etc/ppp/peers/quectel-ppp) …… user test # (from /etc/ppp/peers/quectel-ppp) password ?????? # (from /etc/ppp/peers/quectel-ppp) remotename 3gppp # (from /etc/ppp/peers/quectel-ppp) /dev/ttyUSB3 # (from /etc/ppp/peers/quectel-ppp) 115200 # (from /etc/ppp/peers/quectel-ppp) lock # (from /etc/ppp/peers/quectel-ppp) connect /usr/sbin/chat -s -v -f /etc/ppp/peers/quectel-chat-connect # (from /etc/ppp/peers/quectel-ppp) disconnect /usr/sbin/chat -s -v -f /etc/ppp/peers/quectel-chat-disconnect # (from Quectel Confidenti
3) This whole PPP route seems much too cumbersome for me and I have had much more success in the past using a manufacturer's higher level driver and connection manager (NCM for Huawei) and in this case QMI for Qualcomm.
As soon as I have time I am going to dive into this. It is explained in “5.4. Test GobiNet or QMI WWAN With Connect Manager” section of the same manual.
I am finishing the Start Guide and testing the driver/firmware now. I hope to send it to you once I finish it. Hopefully in one or two weeks because of the Chinese New Year delay.
@Guest, I just tested mine SIM card today. I have the same problem: every settings are correct but cannot connect. By unplug the power and power it again, it works.
I updated as there was an update available, and rebooted. When done it could not find the modem, so I rebooted again!
Now I have 2 green light (power and ??) and 1 red light! (see attached image).
I also see no WiFi signal from the MiFi, and when using a network cable I get no IP.
When setting IP manually (192.168.1.10) I’m also not able to access the MiFi on 192.168.1.1
Is there a way to reset the MiFi? (I’ve tried the reset button with no luck)
this is based on Domino so it finds the domino firmware for update. So all drivers are gone. We will send you a firmware so that you can re flash it back.
