EM06-A : Need Help, modem isn't working after a power outage

[hw1353]

I had a power outage this weekend, when the power came back, my EM06-a would not connect to verizon.

I found another thread with someone seeing the same error as I am in the Debug logs:
http://wirelessjoint.com/viewtopic.php?f=15&t=1061&start=10

I've reset the APN, and the configuration on the router, reflashed the router. I've also tried a different router altogether, same result. WE826 and WE1326v5

I've read the thread above and have tried to reset the EM06-a to default settings using the information I found in the AT-Commands manual from the Quectel website.

AT&F0

I get OK, wait a few then reboot the router, but nothing actually resets to default. All of the settings I had previously(LTE only, no roaming, etc) are still there when I look them up in the AT-Command window after the reset and reboot.

I'm not sure why a power outage would have caused this issue, I've lost power several times before and everything typically comes right back up. I've since ordered a UPS off amazon to run my networking equipment on to prevent this in the future.

Here is some output from the Debug window:

Code: Select all

  
Tue May 26 19:12:27 2020 : /dev/ttyUSB2 AT+QINDCFG="all",0
OK
  
Tue May 26 19:12:29 2020 : /dev/ttyUSB2 AT+QINDCFG="smsincoming",0
OK
  
Tue May 26 19:12:30 2020 : /dev/ttyUSB2 AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",3
OK
  
Tue May 26 19:12:32 2020 : /dev/ttyUSB2 AT+CFUN=1
OK
ATI
Quectel
EM06
Revision: EM06ALAR03A05M4G
OK
AT+CNUM
+CNUM: "Line 1","+19xxxxxxx",145
OK
AT+CPBR=?
+CME ERROR: 100
  
Tue May 26 19:12:33 2020 : /dev/ttyUSB2 AT+CGMI
Quectel
OK
  
Tue May 26 19:12:34 2020 : /dev/ttyUSB2 AT+CGMM
EM06
OK
  
Tue May 26 19:12:35 2020 : /dev/ttyUSB2 AT+CGSN
861364040xxxxxx
OK
  
Tue May 26 19:12:37 2020 : /dev/ttyUSB2 AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",3
OK
  
Tue May 26 19:12:38 2020 : /dev/ttyUSB2 AT+CIMI
311480556xxxxxx
OK
  
Tue May 26 19:12:40 2020 : /dev/ttyUSB2 AT+CRSM=176,12258,0,0,10
+CRSM: 144,0,"98410800007541963322"
OK
  
  
Tue May 26 19:12:42 2020 : /dev/ttyUSB2 AT+COPS=0,,,7
OK
  
Tue May 26 19:12:43 2020 : /dev/ttyUSB2 AT+CGDCONT=?
+CGDCONT: (1-24),"IP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"PPP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV6",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV4V6",,,(0-3),(0-4),(0-1),(0-1)
OK
  
Tue May 26 19:12:44 2020 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","VZWINTERNET","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
+CFUN: 1
OK
  
Tue May 26 19:12:49 2020 : /dev/ttyUSB2 AT+CMGS=?;+CMGL=?;+CMGR=?
+CMGL: ("REC UNREAD","REC READ","STO UNSENT","STO SENT","ALL")
OK
  
Tue May 26 19:12:50 2020 : /dev/ttyUSB2 AT+CMGF=0
OK
  
Tue May 26 19:12:53 2020 : /dev/ttyUSB2 AT+CPMS="SM","SM","SM"
+CPMS: 0,0,0,0,0,0
OK
  
Tue May 26 19:12:55 2020 : /dev/ttyUSB2 AT+CPMS="ME"
+CPMS: 0,99,0,0,0,0
OK
  
Tue May 26 19:12:57 2020 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0
OK
  
Tue May 26 19:13:24 2020 : /dev/ttyUSB2 AT+CMGL=4
+CMS ERROR: 303

TIMEOUT ERROR
  
Tue May 26 19:13:30 2020 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0
OK

Also some output from ServingCell, shows LIMSRV:

Code: Select all

AT+QENG="servingcell"
+QENG: "servingcell","LIMSRV","LTE","FDD",311,480,1DA9C0C,105,2125,4,4,4,792E,-106,-8,-78,18,15

OK

Any thoughts on what :

Code: Select all

+CMS ERROR: 303

TIMEOUT ERROR

Could be? Same error as the other user saw in the thread I posted earlier. None of the fixes there seem to help. Open to suggestion. Is there a different reset command I could try? Or is this modem done?

[Didneywhorl]

I had a power outage this weekend, when the power came back, my EM06-a would not connect to verizon.
......

Any thoughts on what :

Code: Select all

+CMS ERROR: 303

TIMEOUT ERROR

Could be? Same error as the other user saw in the thread I posted earlier. None of the fixes there seem to help. Open to suggestion. Is there a different reset command I could try? Or is this modem done?

Its relating to the command on the line just before it

AT+CMGL=4

CMS is an error message. 303 says this command isn't supported or allowed. AT+CMGL is one of the text (SMS) message commands. Ignore.

To be honest, your modem looks fine. Have you tried putting the SIM card into a phone and checking if the data works on it?

I'll bet Verizon has your data suspended. I could be wrong, but check.

[BillA]

I had a power outage this weekend, when the power came back, my EM06-a would not connect to verizon.

A power outage may have corrupted the modem's NVM (Non-Volatile-Memory).
I would reset it and try both QMI and MBIM modes.

QMI mode
Copy and paste each command one at a time, and make sure you get an "OK" response after each command:

Code: Select all

AT+QPRTPARA=3

Wait a minute, restart the router, then copy and paste these commands:

Code: Select all

AT+QCFG="usbnet",0

Restart the router, and see if you can connect.


MBIM mode
Copy and paste each command one at a time, and make sure you get an "OK" response after each command:

Code: Select all

AT+QPRTPARA=3

Wait a minute, restart the router, then copy and paste these commands:

Code: Select all

AT+QCFG="usbnet",2

Restart the router, and see if you can connect.

[hw1353]

A power outage may have corrupted the modem's NVM (Non-Volatile-Memory).
I would reset it and try both QMI and MBIM modes.

QMI mode
Copyy and paste each command one at a time, and make sure you get an "OK" response after each command:

Code: Select all

AT+QPRTPARA=3

Wait a minute, restart the router, then copy and paste these commands:

Code: Select all

AT+QCFG="usbnet",0

Restart the router, and see if you can connect.


MBIM mode
Copyy and paste each command one at a time, and make sure you get an "OK" response after each command:

Code: Select all

AT+QPRTPARA=3

Wait a minute, restart the router, then copy and paste these commands:

Code: Select all

AT+QCFG="usbnet",2

Restart the router, and see if you can connect.


p.s. This is really weird, when I write "copy and paste" at the beginning of a line (only at the beginning) and try to post it, I get a "Page_not_found" error and my IP get's blacklisted, so I had to misspell "copy" as "copyy" Uhhhh!
I had to get a new IP in order to get back into the forum. Talk about weird....

Bill,

Thanks for these commands!

I saw these on the other thread, but saw "Use at your own risk" and the fact that it was for a slightly different modem had me thinking it wasn't the right command, which caused me to try and find the correct one in the AT manual.

"AT+QPRTPARA=3" is not in the AT-Manual I downloaded from quectel. However, I've added these to my notes.

I sent the "AT+QPRTPARA=3" command, and got an "OK" which then changed to "error" about 3 seconds later. I waited about 30s and rebooted the router.

Modem booted up and connected to LTE like I would have expected it to! Thanks! Solved the issue.

[hw1353]

Of course, I've added my other settings back as well. All seems to be working fine.

[BillA]

Bill,

Thanks for these commands!

I saw these on the other thread, but saw "Use at your own risk" and the fact that it was for a slightly different modem had me thinking it wasn't the right command, which caused me to try and find the correct one in the AT manual.

"AT+QPRTPARA=3" is not in the AT-Manual I downloaded from quectel. However, I've added these to my notes.

I sent the "AT+QPRTPARA=3" command, and got an "OK" which then changed to "error" about 3 seconds later. I waited about 30s and rebooted the router.

Modem booted up and connected to LTE like I would have expected it to! Thanks! Solved the issue.

It's an undocumented command, and not unusual for manufactures to omit certain ones, even if it's "dangerous" there are ways to fix it. If you would like to make sure that the modem only connects to an LTE signal and never roams accidentally on anther carrier due to low signal (they can suspend your account for roaming too much), you can fix it via the commands below. It will simply ensure that you're always connected to an non-roaming LTE signal.
.Copy and paste each command one at a time, and make sure you get an "OK" response after each command:

Code: Select all

AT+QCFG="nwscanmode",3,1
AT+QCFG="roamservice",1,1

Restart the router, and make sure you can browse the web.

[hw1353]

It's an undocumented command, and not unusual for manufactures to omit certain ones, even if it's "dangerous" there are ways to fix it. If you would like to make sure that the modem only connects to an LTE signal and never roams accidentally on anther carrier due to low signal (they can suspend your account for roaming too much), you can fix it via the commands below. It will simply ensure that you're always connected to an non-roaming LTE signal.
.Copy and paste each command one at a time, and make sure you get an "OK" response after each command:

Code: Select all

AT+QCFG="nwscanmode",3,1
AT+QCFG="roamservice",1,1

Restart the router, and make sure you can browse the web.

Well, I had a false sense of hope, the modem works...somewhat.

So when I issue the factory reset command, and then reboot the router, the modem initially boots up in MBIM mode. Connects to verizon fine, good results with speed test and downloads. Higher latency.

When I reboot the router a second time after the factory reset, it switches to QMI mode without me setting anything previously. The modem will not connect, same as the original issue, "LIMSRV", just stays at "Connecting"

It was late last night, I didn't even snap to the fact that it was booting up in MBIM after the factory reset. It really through me for a loop today, as I factory reset it again, got it working fine inside, took it outside, booted it up and would not connect. Did that twice before I realized the pattern.

So the modem does work, just only in MBIM mode, for whatever reason.

I don't have a USB adapter but can order one. Does this in both my WE826 and the WE1326, I reflashed both just to be sure it wasn't an OS issue. I guess I could reflash to some older versions I have, but just doesn't really make sense in the longrun I guess.

EDIT!:

So I tried factory reset, rebooting the router, then manually setting the modem to MBIM, doing the second reboot...the modem still doesn't connect. So it only works after the initial factory reset, after the next power cycle, it doesn't connect.

I'd say it was the router, but I have 2 routers and they both do it. Both work fine with the exact same sim cards(I have a rental/third party verizon plan I'm trying to get rid of because its expensive, and a second pre-paid verizon sim) with a MC7455...I'm letting my brother test my ATT sim at his place nearby to see if it will work for him.

I may try my t-mobile sim card, I think it has service for 1-2 more days.

I've ordered a USB adapter, going to look into re-flashing the firmware.

Know of any guides for quectel firmware flashing?

[BillA]

Just email Quectel for the latest firmware update package for the EM06.
Send and email to both of these addresses:
Info@Quectel.com
Support@Quectel.com


For those who have the EP06-A model, here's the latest firmware package including the flashing app for those who need it. It's easy to use, just unzip all three packages and run the QFlash_V4.16.exe app in the Quectel_QFlash_v4.16 folder.

Quectel_EP06-A_Firmware_EP06ALAR02A07M4G.ZIP
https://androidfilehost.com/?fid=4349826312261739964

[hw1353]

Just email Quectel for the latest firmware update package for the EM06.
Send and email to both of these addresses:
Info@Quectel.com
Support@Quectel.com


For those who have the EP06-A model, here's the latest firmware package including the flashing app for those who need it. It's easy to use, just unzip all three packages and run the QFlash_V4.16.exe app in the Quectel_QFlash_v4.16 folder.

Quectel_EP06-A_Firmware_EP06ALAR02A07M4G.ZIP
https://androidfilehost.com/?fid=4349826312261739964

I sent them an email. I also put in a support request a few days ago a to their website and never heard back. Hopefully I'll get a response soon.

I've noticed the pattern as to what happens during a good boot, then connection with the modem(right after a factory reset) and what the debug log looks like when it fails to boot.

GOOD

Code: Select all

  
Wed May 27 15:33:40 2020 : /dev/ttyUSB2 AT
OK
  
Wed May 27 15:33:41 2020 : /dev/ttyUSB2 AT+CNMI?
+CNMI: 1,1,0,2,0
OK
  
Wed May 27 15:33:42 2020 : /dev/ttyUSB2 AT+QINDCFG="smsincoming"
+QINDCFG: "smsincoming",1
OK
  
Wed May 27 15:33:45 2020 : /dev/ttyUSB2 AT+QINDCFG="smsincoming",0,1
OK
  
Wed May 27 15:33:46 2020 : /dev/ttyUSB2 AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",0
OK
  
Wed May 27 15:33:48 2020 : /dev/ttyUSB2 AT+CFUN=1
OK
ATI
Quectel
EM06
Revision: EM06ALAR03A05M4G
OK
AT+CNUM
+CNUM: "Line 1","+193xxxxxxxx",145
OK
AT+CPBR=?
+CME ERROR: 100
  
Wed May 27 15:33:49 2020 : /dev/ttyUSB2 AT+CGMI
Quectel
OK
  
Wed May 27 15:33:50 2020 : /dev/ttyUSB2 AT+CGMM
EM06
OK
  
Wed May 27 15:33:51 2020 : /dev/ttyUSB2 AT+CGSN
861364040034322
OK

  
Wed May 27 15:33:53 2020 : /dev/ttyUSB2 AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",0
OK
  
Wed May 27 15:33:54 2020 : /dev/ttyUSB2 AT+CIMI
3114805564xxxxx
OK
  
Wed May 27 15:33:56 2020 : /dev/ttyUSB2 AT+CRSM=176,12258,0,0,10
+CRSM: 144,0,"984108000075419xxxxx"
OK
  
Wed May 27 15:34:01 2020 : /dev/ttyUSB2 AT+CMGS=?;+CMGL=?;+CMGR=?
+CMGL: ("REC UNREAD","REC READ","STO UNSENT","STO SENT","ALL")
OK
  
Wed May 27 15:34:02 2020 : /dev/ttyUSB2 AT+COPS=0
OK
  
Wed May 27 15:34:03 2020 : /dev/ttyUSB2 AT+CGDCONT=?
+CGDCONT: (1-24),"IP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"PPP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV6",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV4V6",,,(0-3),(0-4),(0-1),(0-1)
OK
  
Wed May 27 15:34:05 2020 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
+CFUN: 1
OK
  
Wed May 27 15:34:14 2020 : /dev/ttyUSB2 AT+CGDCONT=1,"IPV4V6","vzwinternet";+CFUN=0;+CFUN=1
OK
  
Wed May 27 15:34:15 2020 : /dev/ttyUSB2 AT+CMGF=0
OK
  
Wed May 27 15:34:18 2020 : /dev/ttyUSB2 AT+CPMS="SM","SM","SM"
+CPMS: 0,0,0,0,0,0
OK


  
Wed May 27 15:34:18 2020 : /dev/ttyUSB2 AT+CPMS="SM","SM","SM"
+CPMS: 0,0,0,0,0,0
OK
  
Wed May 27 15:34:20 2020 : /dev/ttyUSB2 AT+CPMS="ME"
+CPMS: 0,99,0,0,0,0
OK
  
Wed May 27 15:34:22 2020 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0
OK
  
Wed May 27 15:34:50 2020 : /dev/ttyUSB2 AT+CMGL=4
+CMS ERROR: 303

TIMEOUT ERROR
  
Wed May 27 15:34:54 2020 : /dev/ttyUSB2 AT+CMGS=?;+CMGL=?;+CMGR=?
+CMGL: ("REC UNREAD","REC READ","STO UNSENT","STO SENT","ALL")
OK
  
Thu May 28 10:28:17 2020 : /dev/ttyUSB2 AT+COPS=3,0;+COPS?
+COPS: 0,0,"Verizon ",7
OK
AT+COPS=3,2;+COPS?
+COPS: 0,2,"311480",7
OK
ATI
Quectel
EM06
Revision: EM06ALAR03A05M4G
OK
AT+CGEQNEG=1
ERROR
AT+CNUM
+CNUM: "Line 1","+193xxxxxxx",145
OK
  
Thu May 28 10:28:20 2020 : /dev/ttyUSB2 AT+CREG=2;+CREG?;+CREG=0
+CREG: 2,3
OK
AT+CEREG=2;+CEREG?;+CEREG=0
+CEREG: 2,1,"792E","1DA9C01",7
OK
AT+C5GREG=2;+C5GREG?;+C5GREG=0
ERROR
  
Thu May 28 10:28:22 2020 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0
OK

Thu May 28 10:28:25 2020 : /dev/ttyUSB2 AT+CREG=2;+CREG?;+CREG=0
+CREG: 2,3
OK
AT+CEREG=2;+CEREG?;+CEREG=0
+CEREG: 2,1,"792E","1DA9C01",7
OK
AT+C5GREG=2;+C5GREG?;+C5GREG=0
ERROR
  
Thu May 28 10:28:31 2020 : /dev/ttyUSB2 AT+CSQ
+CSQ: 31,99
OK
AT+QENG="servingcell"
+QENG: "servingcell","NOCONN","LTE","FDD",311,480,1DA9C01,105,5230,13,3,3,792E,-70,-11,-43,12,-
OK
AT+QNWINFO
+QNWINFO: "FDD LTE","311480","LTE BAND 13",5230
OK
AT+QCAINFO
+QCAINFO: "pcc",5230,50,"LTE BAND 13",1,105,-70,-10,-42,12
+QCAINFO: "scc",2125,75,"LTE BAND 4",1,105,-94,-10,-76,11
OK
AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",0
OK
AT+QTEMP
+QTEMP: 31,30,30
OK
  
Thu May 28 10:28:38 2020 : /dev/ttyUSB2 AT+CSQ
+CSQ: 31,99
OK
AT+QENG="servingcell"
+QENG: "servingcell","NOCONN","LTE","FDD",311,480,1DA9C01,105,5230,13,3,3,792E,-70,-11,-42,12,-
OK
AT+QNWINFO
+QNWINFO: "FDD LTE","311480","LTE BAND 13",5230
OK
AT+QCAINFO
OK
AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",0
OK
AT+QTEMP
+QTEMP: 32,30,30
OK
  
Thu May 28 10:28:42 2020 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0
OK

BAD:

Code: Select all

  
Thu May 28 10:52:47 2020 : /dev/ttyUSB2 AT
OK
  
Thu May 28 10:52:48 2020 : /dev/ttyUSB2 AT+CNMI?
+CNMI: 1,1,0,2,0
OK
  
Thu May 28 10:52:50 2020 : /dev/ttyUSB2 AT+QINDCFG="smsincoming"
+QINDCFG: "smsincoming",0
OK
  
Thu May 28 10:52:51 2020 : /dev/ttyUSB2 AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",0
OK
  
Thu May 28 10:52:53 2020 : /dev/ttyUSB2 AT+CFUN=1
OK
ATI
Quectel
EM06
Revision: EM06ALAR03A05M4G
OK
AT+CNUM
+CNUM: "Line 1","+193xxxxxx",145
OK
AT+CPBR=?
+CME ERROR: 100
  
Thu May 28 10:52:54 2020 : /dev/ttyUSB2 AT+CGMI
Quectel
OK
  
Thu May 28 10:52:55 2020 : /dev/ttyUSB2 AT+CGMM
EM06
OK
  
Thu May 28 10:52:56 2020 : /dev/ttyUSB2 AT+CGSN
8613640400xxxxx
OK
  
Thu May 28 10:52:58 2020 : /dev/ttyUSB2 AT+QCFG="nwscanmode"
+QCFG: "nwscanmode",0
OK
  
Thu May 28 10:52:59 2020 : /dev/ttyUSB2 AT+CIMI
3114805564xxxxx
OK

  
Thu May 28 10:53:01 2020 : /dev/ttyUSB2 AT+CRSM=176,12258,0,0,10
+CRSM: 144,0,"984108000075xxxxxxx"
OK
  

  
Thu May 28 10:53:02 2020 : /dev/ttyUSB2 AT+COPS=0
OK
  
Thu May 28 10:53:04 2020 : /dev/ttyUSB2 AT+CGDCONT=?
+CGDCONT: (1-24),"IP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"PPP",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV6",,,(0-3),(0-4),(0-1),(0-1)
+CGDCONT: (1-24),"IPV4V6",,,(0-3),(0-4),(0-1),(0-1)
OK
  
Thu May 28 10:53:05 2020 : /dev/ttyUSB2 AT+CGDCONT?;+CFUN?
+CGDCONT: 1,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
+CFUN: 1
OK
  
Thu May 28 10:53:10 2020 : /dev/ttyUSB2 AT+CMGS=?;+CMGL=?;+CMGR=?
+CMGL: ("REC UNREAD","REC READ","STO UNSENT","STO SENT","ALL")
OK
  
Thu May 28 10:53:11 2020 : /dev/ttyUSB2 AT+CMGF=0
OK
  
Thu May 28 10:53:14 2020 : /dev/ttyUSB2 AT+CPMS="SM","SM","SM"
+CPMS: 0,0,0,0,0,0
OK
  
Thu May 28 10:53:16 2020 : /dev/ttyUSB2 AT+CPMS="ME"
+CPMS: 0,99,0,0,0,0
OK
  
Thu May 28 10:53:18 2020 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0
OK
  
Thu May 28 10:53:45 2020 : /dev/ttyUSB2 AT+CMGL=4
+CMS ERROR: 303

TIMEOUT ERROR
  
Thu May 28 10:53:51 2020 : /dev/ttyUSB2 AT+CPMS="SM"
+CPMS: 0,0,0,0,0,0
OK

Looks like when it doesn't connect(2nd reboot after factory reset), it never passes the APN to the modem.

Also during the "bad" startup, the output of "AT+CGDCONT?;+CFUN?" changes to:

Code: Select all

+CGDCONT: 1,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
+CFUN: 1
OK

Whereas on a "good" startup(first boot after factory reset) it returns:

Code: Select all

+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
+CFUN: 1
OK

Seeing as how this is a quectel modem, and programming CGDCONT doesn't seem to persist, I'm not sure what else I can do other than re-flash the firmware.

I firmware recovery flashed my W1326 to GoldenOrb 3-31-20, tried, got the same results, and then flashed to the latest WiFiX version, got the same results.

Any other thoughts while I wait on quectel?

EDIT:

Just for fun I tried manually passing the APN to the modem, no luck.

I have my ATT and T-mobile sims back, so I'll test and see if anything different happens.

EDIT 2:

I am not able to recreate the issue with my t-mobile or ATT sims. Any verizon-based sim(pageplus,prepaid vz, rental vz hotspot account) it fails to connect properly.

[hw1353]

This probably should have been in the questions and support section.

[BillA]

This probably should have been in the questions and support section.

I've read in another forum that QMI mode works better with CDMA/LTE carriers such as Verizon/Sprint, while both QMI and MBIM mode works with ATT and Tmobile, but needs to be tested.
Have you tried manually switching the modem into QMI mode as I have posted earlier?
After a good bootup regardless of the mode, you might be able to save the NV items via this command:

Code: Select all

AT&W
AT+CFUN=1,1

Reboot, and see if the settings have persisted.

You can also try a NV factory reset via:

Code: Select all

AT&F
AT&F1
AT&W
AT+CFUN=1,1

Reboot, and see if it works.

[hw1353]

I've been trying so many different things, where to begin.

First off, 2 of these EM06 modems I have no longer work. The most recent one was after I did a hard reboot. No power failure/brown out associated with it. So this is now 2 EM06 Quectel modems that are not working. Same firmware, same issue across both modems.

So I got some USB adapters and finally got the firmware from quectel. I've reflashed both modems, they experience the exact same issue.

I was really scratching my head. I came across a MC7354(pretty sure its out of a cradlelink LPE400), I went ahead and installed the MC7354 in my WE826, router boots up, detects the modem just fine...but exhibits the exact same problem the quectel modems do.

I've tried the generic / verizon firmwares. Both have the same effect. Placing the modem in MBIM or QMI doesn't seem to have an effect either.

I guess I'm entertaining its an issue with the SIM card. I've just rule that out, as it works in an unlocked cell phone just fine, and works with a MC7455 just fine...still a possibility. It also still seems to happen with ATT/T-mobile, although there have been these twilight zone moments where it looks like its connecting over ATT, but nothing ever happens.

I'm also seriously considering the 05/5/20 version of wifix/go to be the culprit. As I have 2 identical EM06 modems that are just extremely problematic. I wish there was an archive of previous OS's to download from, seems that they only publish the latest version on thewirelesshaven.com

I'm in the process of downgrading my WE826 to rooter/GO 3-20 to see if there's any change.

[BillA]

I've been trying so many different things, where to begin.

First off, 2 of these EM06 modems I have no longer work. The most recent one was after I did a hard reboot. No power failure/brown out associated with it. So this is now 2 EM06 Quectel modems that are not working. Same firmware, same issue across both modems.

So I got some USB adapters and finally got the firmware from quectel. I've reflashed both modems, they experience the exact same issue.

I was really scratching my head. I came across a MC7354(pretty sure its out of a cradlelink LPE400), I went ahead and installed the MC7354 in my WE826, router boots up, detects the modem just fine...but exhibits the exact same problem the quectel modems do.

I've tried the generic / verizon firmwares. Both have the same effect. Placing the modem in MBIM or QMI doesn't seem to have an effect either.

I guess I'm entertaining its an issue with the SIM card. I've just rule that out, as it works in an unlocked cell phone just fine, and works with a MC7455 just fine...still a possibility. It also still seems to happen with ATT/T-mobile, although there have been these twilight zone moments where it looks like its connecting over ATT, but nothing ever happens.

I'm also seriously considering the 05/5/20 version of wifix/go to be the culprit. As I have 2 identical EM06 modems that are just extremely problematic. I wish there was an archive of previous OS's to download from, seems that they only publish the latest version on thewirelesshaven.com

I'm in the process of downgrading my WE826 to rooter/GO 3-20 to see if there's any change.

You've mentioned that you have service in a test phone, just wondering if your signal might be too low for the router to pick up (unlikely but possible). You may want to take the router over to someone's home and try it there too.
Keep up updated with your modem saga.

[hw1353]

The only real service around is Verizon service. Closest ATT tower is 7 miles away.

I have a 5 band cell booster inside my house I test these devices with before I try them outside. All of my other verizon hotspots work over the booster and connect fine. Theres 2-3 bars of verizon service outside my house. My MC7455 is doing almost 100mbps down with my verizon plan, has been since my quectel started giving me fits.

Where I'm at:

The MC7354 I have only seem to work with a cradlepoint(I have a CBA750b) inside of their cradlepoint usb enclosures. I cannot make them work with a WE826 connected directly to PCIE. I tried all the firmwares.

[hw1353]

Connect it(MC7354) to the CBA750B with the correct firmware programmed, either ATT SIM or Verizon SIM works great. So I'm sure CP has these modems locked to their hardware.

I've flashed the EM06 modems. I've even tried flashing it back-to-back, I don't think quectel has a firmware management feature, but I wanted to make sure I flashed it twice to make sure it persists. Probably doesn't do anything.

The EM06's will work with verizon after the first boot up after reflashing or after a OEMREST, boots up connects to verizon LTE perfectly, I see the speeds I would expect.

Reboot the modem 1 time after re-flash or oem restore, and it will not connect. Never finishes connecting. It will keep settings through a reboot now. Just will not re-connect.

However, after double re-flashing, the EM06s will work with ATT, and will continue working after several reboots. So that issue seems to be resolved.

So it seems my real issue is with the EM06s is with CDMA SIM cards, GSM sim cards seem to work fine so far after the reflash.

Changing routers or router firmwares had no effect.

This isn't really signal issue, I've literally driven to the tower, about 100yds from the road, and tried. Will not connect after a reboot.

[hw1353]

Idk, I'm to the point I'm going to throw them on eBay for a cheap price and let them go. Neither modem lasted a month.

I purchased 2 of these, one for myself and one for a LTE rig I setup for a family member.

Given one may have been my fault, I wasn't using a UPS and a brown-out likely caused the fit. However, the other EM06 I purchased was used at my brother's residence, who lives about a mile away. He has a battery backup for his computer and had a spot for the modem, and was spared from the brown out. However, a few days later, clear sunny day, it just stopped reconnecting to verizon, after a hard reboot, just like mine.

I'm wondering if the brown-out(maybe it was just a flicker) didn't really even cause my issue. Seems that the issue can simply come from pulling the power cord from the router, waiting 5 seconds, then plugging it back in. Sucks for me, I'm out about 200$ worth of modems. Will not be buying quectel in the future.

All of my modems/routers use 2amp adapters or use the 3amp POE splitters/injectors from The Wireless Haven.

[JimHelms]

Looks like when it doesn't connect(2nd reboot after factory reset), it never passes the APN to the modem.

On the initial startup (which you define as a good start up) we see the default APN of "ims" set in profile slot 1.

Code: Select all

+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

Then, GoldenOrb sends the APN from the Modem Profile to profile slot 1 and updates "ism" to "vzwinternet", and the modem is accepting it:

Code: Select all

+CGDCONT: 1,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

So, it does appear to be functioning properly even though it is not connecting thereafter.

Makes one wonder what function, if any, the APN "ims" plays.

Notice the admin APN in profile 2:

Code: Select all

+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

I see this APN show up in Cradlepoint routers in profile 1 which seems to make some sort of hand shake with the network (i.e, possibly for OTA functions) shortly before using and connecting with the vzwinternet APN which is usually in profile 3.

What I have noticed is that when the admin APN is available in one of the modem profile slots, the connection is short lived unless the plan and SIM card is provisioned to the modem's IMEI.

It is possible to remove/overwrite the admin APN in whatever profile slot its residing in (i.e., 3 in the above example) and maintain a connection.

Code: Select all

AT+CGDCONT=3,"IPV4V6","vzwinternet"

Also, you might try setting the modem to LTE only. This was discussed prior to resetting the modem. LTE mode It is the only way I have been able to establish a connection with the EM06 (and a few other Quectel modems) on the Sprint network:

Code: Select all

AT+QCFG="nwscanmode",3,1

Lastly, are you using a different SIM Card adapter for the Verizon SIM card that the other SIMs?

I have seen a lot of strange connection issues related to SIM cards and adapters. The SIM Card must fit into the adapter snug--not too tight and not loose. The tits/tabs must be sanded/removed from all sides of a SIM Card where it lays flat in the adapter without having to force it.

I then use a piece of thick piece of scotch tape over the back side of the SIM card adapter to hold the SIM Card in place (and to be able to see what SIM card is in that adapter). This will also make the SIM card and adapter fit a little tighter into the router where its contact with the pins are not so effected by heat as the router warms up.

[BillA]

What I have noticed is that when the admin APN is available in one of the modem profile slots, the connection is short lived unless the plan and SIM card is provisioned to the modem's IMEI.

It is possible to remove/overwrite the admin APN in whatever profile slot its residing in (i.e., 3 in the above example) and maintain a connection.

Interesting observation, "vzwadmin" is a provisioning/OTA APN... who would have thought that could interfere.... nice catch.

[hw1353]

On the initial startup (which you define as a good start up) we see the default APN of "ims" set in profile slot 1.

Code: Select all

+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

Then, GoldenOrb sends the APN from the Modem Profile to profile slot 1 and updates "ism" to "vzwinternet", and the modem is accepting it:

Code: Select all

+CGDCONT: 1,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

So, it does appear to be functioning properly even though it is not connecting thereafter.

Makes one wonder what function, if any, the APN "ims" plays.

I'm following you here, the output of CGDCONT doesn't really matter at that point, as its passed the correct apn from the Modem Profile/GO?

Notice the admin APN in profile 2:

Code: Select all

+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

I see this APN show up in Cradlepoint routers in profile 1 which seems to make some sort of hand shake with the network (i.e, possibly for OTA functions) shortly before using and connecting with the vzwinternet APN which is usually in profile 3.

What I have noticed is that when the admin APN is available in one of the modem profile slots, the connection is short lived unless the plan and SIM card is provisioned to the modem's IMEI.

It is possible to remove/overwrite the admin APN in whatever profile slot its residing in (i.e., 3 in the above example) and maintain a connection.

Code: Select all

AT+CGDCONT=3,"IPV4V6","vzwinternet"

I will try this and see what happens. I'm not sure I 100% follow you.

Also, you might try setting the modem to LTE only. This was discussed prior to resetting the modem. LTE mode It is the only way I have been able to establish a connection with the EM06 (and a few other Quectel modems) on the Sprint network:

Ah, yes. I guess I did not do that before I grabbed these logs. I had done that in the past, but must have forgot after the latest OEM reset. I'll change that.

Lastly, are you using a different SIM Card adapter for the Verizon SIM card that the other SIMs?

I have seen a lot of strange connection issues related to SIM cards and adapters. The SIM Card must fit into the adapter snug--not too tight and not loose. The tits/tabs must be sanded/removed from all sides of a SIM Card where it lays flat in the adapter without having to force it.

I then use a piece of thick piece of scotch tape over the back side of the SIM card adapter to hold the SIM Card in place (and to be able to see what SIM card is in that adapter). This will also make the SIM card and adapter fit a little tighter into the router where its contact with the pins are not so effected by heat as the router warms up.

I've tried 2 different SIMs, one is a Noosy adapter, sim is clean cut and smooth, fits fine. Works with any other modem. I have a full size SIM with different plan, same behavior with both, same behavior with EM06 in a different router, and also with a usb adapter.

I'll try the steps you mention and post back.

[hw1353]

Still unable to get the EM06-a to work in a WE826 or a WE1326.

If I factory reset, put the EM06 in a usb enclosure, connect to windows, set QMI mode, set it up via Huwaei terminal, the modem connects no problem on verizon. I can disconnect and reconnect the USB at will, still reconnects.

I'm literally using the connection as I type this. So the modem does work with vzw. This is an issue with Goldenorb. Right? If I can remove the modem as configured from the router, and install into a USB enclosure and it connects with windows 10, that would tell me its most likely an issue with the router.

I've tried 2 different WE826 and a WE1326. Out of ideas.

Edit - after trying a few things...

I know we're saying the order/enumeration/existance of values of CGDCONT(other than 1) do not matter, but:

What I'm thinking is happening, is that the quectel modem, once defaulted, has the values in CGDCONT:

Code: Select all

Recieve: AT+CGDCONT?
Recieve: +CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
Recieve: +CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
Recieve: +CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
Recieve: +CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
Recieve: +CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
Recieve: +CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1
Recieve: OK

As long as I use it with my windows 10 machine, these values do not change.

However, once they are installed in a GO router, they are modified, as it overwrites CGDCONT=1 to :

Code: Select all

IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

Seems that after that happens, the modem will not connect via windows or Goldenorb. Until I factory reset it and try again.

Once the 1 spot for the APN has been overwritten, the modem will not connect in windows. It shows "Not Connected" with 0 bars.

I connect to the modem with Huwaei terminal(Usb enclosure on a windows 10 machine), and issue the following commands:

Code: Select all

AT+CFUN=0
AT+CGDCONT=1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
AT+CFUN=1

The modem will connect, with 4-5 bars of service showing. And I see the speeds I would expect.

---------------

At this point, I can plug this enclosure into the WE826, and power it up.

The first bootup, it will connect fine.

However, after a power cycle, it will not. Shows "Connecting" I've let it sit overnight before. Nothing happens. No WAN connection whatsoever.

The only difference I'm seeing here is the value of the CGDCONT=1 variable.

Edit 2:

Last thing I wanted to add, both of my EM06-a's exhibit this exact same behavior.

[hw1353]

I guess my next thought is modifying the connect script to modify the CGDCONT=3 value instead of 1?

-------------------

When I'm seeing the issue of not connecting on the WE826,

issuing a :

Code: Select all

AT+CGDCONT=1,"IPV4V6","ims";+CFUN=0;+CFUN=1

Via the AT-Terminal in WiFiX will cause the modem to connect, and I'll have a WAN connection on the router.

I'm not technical enough with this stuff yet to know exactly why thats working/happening, but if I had to take a guess, perhaps its the latest rev of the EM06-a firmware causing it? Isn't there an issue with a EM20 model on latest firmware?

[Didneywhorl]

I might have something for you.

But just to concentrate on one thing. Please give a clear explanation of exactly what happens when you boot up after a fresh flash AND what is it that makes it stop working?

Im collecting that it seems to NOT be saving your parameter changes after a reboot.

[hw1353]

I might have something for you.

But just to concentrate on one thing. Please give a clear explanation of exactly what happens when you boot up after a fresh flash AND what is it that makes it stop working?

Im collecting that it seems to NOT be saving your parameter changes after a reboot.

Sorry, I know I've jumped around a bunch in this thread, I tend to ramble. I toyed with making a new thread to avoid the confusion, but I'm going to try and step through whatI'm seeing:

When I factory reset or reflash the firmware on the EM06, and then insert a vzw sim card, the output of AT+CGDCONT? (In the Huwaei Terminal )is:

Code: Select all

+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1

With the modem in QMI mode, this modem will connect with a windows 10 machine. Works well actually.

However, when I put this in a WE826/WE1326(first boot inside a router):

Watching the Debug window, I see the console output AT+CGDCONT?:

Code: Select all

+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1

Then shortly after that this command is passed:

Code: Select all

AT+CGDCONT=1,"IPV4V6","vzwinternet";+CFUN=0;+CFUN=1

Which overwrites the value for AT+CGDCONT=1.

Now...this is where it gets weird, and my theories come in, because the modem was initially booted with the "factory"( the default settings after a factory reset and inserting a verizon SIM card) settings for vzw, it completes the connection and works. However, when I reboot(power cycle) the router, this is what I see in the debug window for AT+CGDCONT?:

Code: Select all

+CGDCONT: 1,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","vzwinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzw800","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1

(The reason I think this could be happening, is because setting the AT+CGDCONT values for "IP" instead of "IPv4v6" are ignored, and it must be set in the create_connect.sh, or the modem connects with dual stack...So when the router reboots, the modem originally is initialized with the incorrect AT+CGDCONT=1 value, because WiFiX/GO overwrote it on the previous startup.)

So on this second boot, the modem does not complete the connection. It will sit for hours. If I power cycle it again, it has the same affect. Never connects.

"SEARCH" is the only results from "servingcell" during these times.

----------------------
Workaround
----------------------

However, I've found that if I issue the command via AT-Terminal in WiFiX after its already tried to pass the APN and connect:

Code: Select all

AT+CGDCONT=1,"IPV4V6","ims";+CFUN=0;+CFUN=1

Which effectively changes the value of AT+CGDCONT=1 to our "factory" values we saw earlier, and then flips the modem on/off.

I can wait about 10-15 seconds, and the WAN interface comes up, and I'm connected over LTE. However, when the modem reboots (power cycles) again, the value of AT+CGDCONT=1 gets set back to "vzwinternet" and the process repeats itself.

The biggest part that has me scratching my head, is that none of the other modems I've used (MC7455) require the "IMS" value. I'm not sure it's actually needed, but for some reason, in my case it is?

Hope that clears it up.

[Didneywhorl]

When you've done a fresh factory reset on it, what AT commands do you send to it for setting it up the way you like? Any?

Do this one thing for me. Get it connected to the LTE the way you want. Before you reboot it to see if it did its silliness, send the following AT Command:

Code: Select all

AT+QPRTPARA=1

Do this absolutely LAST right before you reboot, and making sure you are setup exactly as you like it, connected to the internet and all.

This command will backup all of your settings to memory IF the memory sector isn't corrupted. It is how you save all the stuff you setup on your modem to backup. If the backup location is blank, like after an AT+QPTRPARA=3, and possibly an AT&F, it has nothing to load from after a reboot. This is my deduction of the commands usefulness, and what it does big picture.

[Didneywhorl]

Did I kill it? Any follow up?

[hw1353]

Did I kill it? Any follow up?

Sorry for late reply.

Life gets in the way sometimes you forget.

I still had issues with both of these modems even after trying your command. Kinda shevled the quectel modem projects and replaced them with Sierra cards. As one was my main connection at home where I work remotely, and couldn't deal with the quirkiness.

However the last few days, I decided to play with the quectel modems a bit again.

Whats worked lately with visible(verizon) and ATT is:
-Program the correct APN into the connection profile manager
-Remove all of the AT+CGDCONT entries, including AT+CGDCONT=1, via AT-Terminal window.
-Power cycle the router

Router will come up, program the correct APN and eventually connect, and has been persisting through multiple reboots.

Seems that when I change SIMS, the default values of AT+CGDCONT? change, I assume due to the type of sim card. My testing so far shows that if there is any other entry than the APN we're trying to connect to in AT+CGDCONT causes some kind of issue.

Still somewhat of a mystery, but they modem has worked for two days and through several reboots. I'm still not sure I trust them though lol.

[Yipzy]

Whats worked lately with visible(verizon) and ATT is:
-Program the correct APN into the connection profile manager
-Remove all of the AT+CGDCONT entries, including AT+CGDCONT=1, via AT-Terminal window.
-Power cycle the router

Router will come up, program the correct APN and eventually connect, and has been persisting through multiple reboots.

Seems that when I change SIMS, the default values of AT+CGDCONT? change, I assume due to the type of sim card. My testing so far shows that if there is any other entry than the APN we're trying to connect to in AT+CGDCONT causes some kind of issue.

Still somewhat of a mystery, but they modem has worked for two days and through several reboots. I'm still not sure I trust them though lol.

You are correct when you switch SIM or when Quectel modem detects a different sim that it recognizes. It will switch to that carrier's MBN file (in this case it's Verizon) which gives you all the APNs that you see when doing AT+CGDCONT? When it doesn't recognize the SIM, it will switch to the default generic MBN file which is why it works on carrier like T-Mobile/SimpleMobile without encountering the connection problems.

What you want to do is issue the following commands:

Code: Select all

AT+QMBNCFG="AutoSel",0                                (stop Autoselect config on sim detection)
AT+QMBNCFG="Deactivate"                               (disable MBN config)
AT+CFUN=1,1                                           (reboot the modem)

That should let you use the APN you set in your router.

If you have problem connecting without using the MBN config, select the generic config by typing:

Code: Select all

AT+QMBNCFG="List"
AT+QMBNCFG="Select","The_Generic_Config_Listed"
AT+CFUN=1,1

Also, if your modem doesn't use band 66 for CA for some reason. Force it by disabling band 4. For me,

Code: Select all

AT+QCFG="band" yields AT+QCFG="band",0,2000001003300185a,1

change to

Code: Select all

AT+QCFG="band",0,20000010033001852,1
AT+CFUN=1,1 (reboot only if change does not take effect after a few seconds in your debug window with band 66)

[BillA]

You are correct when you switch SIM or when Quectel modem detects a different sim that it recognizes. It will switch to that carrier's MBN file (in this case it's Verizon) which gives you all the APNs that you see when doing AT+CGDCONT? When it doesn't recognize the SIM, it will switch to the default generic MBN file which is why it works on carrier like T-Mobile/SimpleMobile without encountering the connection problems.

Great info, it will definitely help many folks.
In case anyone needs to clear all APN slots (1-5) at once, simply copy and paste the long command line below into the AT-Command Terminal. After rebooting the router, the APN contained in Connection Profile > APN will overwrite APN slot#1.

Code: Select all

AT+CGDCONT=1;+CGDCONT=2;+CGDCONT=3;+CGDCONT=4;+CGDCONT=5;+CFUN=0;+CFUN=1

[Yipzy]

Good catch, it will definitely help many folks.
In case anyone needs to clear all APN slots (1-10) at once, simply copy and paste the long command line below into the AT-Command Terminal. After rebooting the router, the APN contained in Connection Profile > APN will overwrite APN slot#1.

Code: Select all

AT+CGDCONT=1;+CGDCONT=2;+CGDCONT=3;+CGDCONT=4;+CGDCONT=5;+CGDCONT=6;+CGDCONT=7;+CGDCONT=8;+CGDCONT=9;+CGDCONT=10;+CFUN=0;+CFUN=1

It should automatically clear the APNs when you deactivate the MBN file.

[BillA]

It should automatically clear the APNs when you deactivate the MBN file.

Well, I meant for those who don't want/need to deactivate the MBN, nonetheless it doesn't diminish your work.

[mezmerizz0454]

Great info guys this is Gold level information

[freep]

This thread has been incredibly helpful. Thanks to everyone who worked on this issue.

[Time-Pilot]

Thanks, this thread helped me get VIsible running on a GL-X750 with an EP06-A i just swapped in. There was whiskey involved, so I will need to break it again and re do it so I can take note of the steps I used. I think my Visible nano sim isn't working great with an adapter because some times the modem would just disappear from the GL Control Panel.

Visible just seemed to work when I had the EC25AF modem in there (using/dev/ttyUSB3, LTE & VSBLINTERNET in manual setup )

But it is working now and I have been using it all day. Don't know if it will persist a reboot/power cycle.