EM7565 Verizon LTE connection not stable at hight

Hi There !

I have an embedded system with two EM7565 modems talking with Verizon. I’m using RMNet plus the latest GobiSerial / GobiNet drivers. With light traffic such as ping, both modems run for days w/o problems, however when I run speed tests it seems to upset things as I lose connectivity. Then I keep trying to enable the data connection with at!scact=1,3 and eventually it comes back to life. This seems like a carrier thing, but I’m not sure how to troubleshoot it.

So what happens is that I send out the at!scact=1,3 which returns OK, and at!scact? shows it as enabled. But then about 5 seconds later it goes back to showing it as disabled.

at!scact=1,3
OK
at!scact?
!SCACT: 1,0
!SCACT: 2,0
!SCACT: 3,1
!SCACT: 4,0
!SCACT: 5,0
!SCACT: 6,0

OK
at!scact?
!SCACT: 1,0
!SCACT: 2,0
!SCACT: 3,1
!SCACT: 4,0
!SCACT: 5,0
!SCACT: 6,0

[5 sec wait]

OK
at!scact?
!SCACT: 1,0
!SCACT: 2,0
!SCACT: 3,0
!SCACT: 4,0
!SCACT: 5,0
!SCACT: 6,0

OK

I tried enabling these notifications, but did not see anything in the terminal

at+creg=1
at+cgreg=1
at+cereg=1

Is there any other way to enable more logging ? I did enable the Gobi Driver debugging, see below

May 28 04:30:02 avoca-cb user.info kernel: [ 2293.649288] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.649296] GobiNet::ReadCallback(5825) Read 35 bytes
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.649321] GobiNet::PrintHex(5825) : 01 22 00 80 01 12 04 EF 00 22 00 16 00 01 02 00 02 00 12 01 00 04 13 02 00 80 88 14 01 00 06 15 01 00 00
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.649344] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.649359] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.701281] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.701320] GobiNet::ReadCallback(5825) Read 35 bytes
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.701345] GobiNet::PrintHex(5825) : 01 22 00 80 01 12 04 F0 00 22 00 16 00 01 02 00 02 00 12 01 00 06 13 02 00 80 88 14 01 00 06 15 01 00 00
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.701380] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.701390] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.824770] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.824786] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:02 avoca-cb user.info kernel: [ 2293.824835] GobiNet::PrintHex(4261) : 45 00 00 54 32 30 40 00 40 01 DC DC 64 4C BB 44 08 08 04 04 08 00 90 55 10 A5 06 88 88 06 00 00 2A E5 AF 60 E1 30 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.109225] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.109232] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.109275] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F1 00 01 00 40 00 10 04 00 01 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 54 00 00
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.109295] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.109301] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.825806] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.825859] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:03 avoca-cb user.info kernel: [ 2294.825860] GobiNet::PrintHex(4261) : 45 00 00 54 32 31 40 00 40 01 DC DB 64 4C BB 44 08 08 04 04 08 00 6A 50 10 A5 06 89 89 06 00 00 2B E5 AF 60 05 35 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.109101] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.109108] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.109151] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F2 00 01 00 40 00 10 04 00 02 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 A8 00 00
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.109173] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.109179] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.827037] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.827054] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:04 avoca-cb user.info kernel: [ 2295.827104] GobiNet::PrintHex(4261) : 45 00 00 54 32 32 40 00 40 01 DC DA 64 4C BB 44 08 08 04 04 08 00 B0 4A 10 A5 06 8A 8A 06 00 00 2C E5 AF 60 BD 39 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.109104] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.109111] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.109154] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F3 00 01 00 40 00 10 04 00 03 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 FC 00 00
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.109174] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.109179] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.828272] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.828325] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:05 avoca-cb user.info kernel: [ 2296.828326] GobiNet::PrintHex(4261) : 45 00 00 54 32 33 40 00 40 01 DC D9 64 4C BB 44 08 08 04 04 08 00 BF 44 10 A5 06 8B 8B 06 00 00 2D E5 AF 60 AC 3E 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.109117] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.109126] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.109169] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F4 00 01 00 40 00 10 04 00 04 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 50 01 00
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.109189] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.109195] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.829498] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.829515] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:06 avoca-cb user.info kernel: [ 2297.829565] GobiNet::PrintHex(4261) : 45 00 00 54 32 34 40 00 40 01 DC D8 64 4C BB 44 08 08 04 04 08 00 0E 3F 10 A5 06 8C 8C 06 00 00 2E E5 AF 60 5B 43 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.109107] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.109114] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.109157] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F5 00 01 00 40 00 10 04 00 05 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 A4 01 00
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.109177] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.109182] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.830753] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.830806] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:07 avoca-cb user.info kernel: [ 2298.830807] GobiNet::PrintHex(4261) : 45 00 00 54 32 35 40 00 40 01 DC D7 64 4C BB 44 08 08 04 04 08 00 16 39 10 A5 06 8D 8D 06 00 00 2F E5 AF 60 51 48 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.109140] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.109148] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.109202] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F6 00 01 00 40 00 10 04 00 06 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 F8 01 00
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.109224] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.109230] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.831015] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.831037] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:08 avoca-cb user.info kernel: [ 2299.831089] GobiNet::PrintHex(4261) : 45 00 00 54 32 36 40 00 40 01 DC D6 64 4C BB 44 08 08 04 04 08 00 21 37 10 A5 06 8E 8E 06 00 00 30 E5 AF 60 44 49 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.109223] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.109230] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.109273] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F7 00 01 00 40 00 10 04 00 07 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 4C 02 00
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.109294] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.109299] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.832144] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.832196] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:09 avoca-cb user.info kernel: [ 2300.832197] GobiNet::PrintHex(4261) : 45 00 00 54 32 37 40 00 40 01 DC D5 64 4C BB 44 08 08 04 04 08 00 9C 31 10 A5 06 8F 8F 06 00 00 31 E5 AF 60 C7 4D 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.109445] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.109453] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.109497] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F8 00 01 00 40 00 10 04 00 08 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 A0 02 00
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.109524] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.109530] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.833411] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.833432] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:10 avoca-cb user.info kernel: [ 2301.833486] GobiNet::PrintHex(4261) : 45 00 00 54 32 38 40 00 40 01 DC D4 64 4C BB 44 08 08 04 04 08 00 DC 2B 10 A5 06 90 90 06 00 00 32 E5 AF 60 85 52 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.109223] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.109230] GobiNet::ReadCallback(5825) Read 77 bytes
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.109273] GobiNet::PrintHex(5825) : 01 4C 00 80 01 12 04 F9 00 01 00 40 00 10 04 00 09 00 00 00 11 04 00 00 00 00 00 12 04 00 FF FF FF FF 13 04 00 FF FF FF FF 14 04 00 FF FF FF FF 15 04 00 FF FF FF FF 19 08 00 F4 02 00
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.109294] GobiNet::QMIWDSCallback(5825) Net device link is connected
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.109299] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.834698] GobiNet::GobiNetDriverTxFixup(4261)
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.834751] GobiNet::GobiNetDriverTxFixup(4261) For sending to device modified:
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.834752] GobiNet::PrintHex(4261) : 45 00 00 54 32 39 40 00 40 01 DC D3 64 4C BB 44 08 08 04 04 08 00 A6 25 10 A5 06 91 91 06 00 00 33 E5 AF 60 B9 57 0D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.945162] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.945198] GobiNet::ReadCallback(5825) Read 34 bytes
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.945228] GobiNet::PrintHex(5825) : 01 21 00 80 01 12 04 FA 00 22 00 15 00 01 02 00 01 00 10 02 00 F0 03 11 04 00 06 00 24 00 12 01 00 06
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.945266] GobiNet::QMIWDSCallback(5825) Net device link is disconnected
May 28 04:30:11 avoca-cb user.info kernel: [ 2302.945280] GobiNet::QMIWDSCallback(5825) clientID :0x1201
May 28 04:30:12 avoca-cb user.info kernel: [ 2302.957092] GobiNet::ProcessReadWorkFunction(5825) ResubmitIntURB
May 28 04:30:12 avoca-cb user.info kernel: [ 2302.957098] GobiNet::ReadCallback(5825) Read 34 bytes
May 28 04:30:12 avoca-cb user.info kernel: [ 2302.957120] GobiNet::PrintHex(5825) : 01 21 00 80 01 12 04 FB 00 22 00 15 00 01 02 00 01 00 10 02 00 F0 03 11 04 00 06 00 24 00 12 01 00 04
May 28 04:30:12 avoca-cb user.info kernel: [ 2302.957135] GobiNet::QMIWDSCallback(5825) Net device link is disconnected
May 28 04:30:12 avoca-cb user.info kernel: [ 2302.957139] GobiNet::QMIWDSCallback(5825) clientID :0x1201

Also, here are the standard troubleshooting command responses

ATI
Manufacturer: Sierra Wireless, Incorporated
Model: EM7565
Revision: SWI9X50C_01.14.02.00 2e210b jenkins 2020/08/19 14:18:39
IMEI: 353533100240350
IMEI SV: 12
FSN: UF923587400315
+GCAP: +CGSM

OK
ATI8
Manufacturer: Sierra Wireless, Incorporated
Model: EM7565
Revision: SWI9X50C_01.14.02.00 2e210b jenkins 2020/08/19 14:18:39
IMEI: 353533100240350
IMEI SV: 12
FSN: UF923587400315
+GCAP: +CGSM

OK
AT!BAND?
Index, Name
00, All bands

OK
AT!SELRAT?
!SELRAT: 00, Automatic

OK
AT!SELCIOT?
ERROR
AT+CGDCONT?
+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”,“vzwclass6”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0

OK
AT+COPS=?
+COPS: (2,“Verizon Wireless”,“VZW”,“311480”,7),(1,“T-Mobile”,“T-Mobile”,“310260”,7),(1,“311 490”,“311 490”,“311490”,7),(1,“T-Mobile”,“T-Mobile”,“310260”,2),(1,“AT&T”,“AT&T”,“310410”,2),(0,1,2,3,4),(0,1,2)

OK
AT!GSTATUS?
!GSTATUS:
Current Time: 3052 Temperature: 35
Reset Counter: 1 Mode: ONLINE
System mode: LTE PS state: Attached
LTE band: B66 LTE bw: 20 MHz
LTE Rx chan: 0 LTE Tx chan: 132122
LTE SCC1 state:NOT ASSIGNED
LTE SCC2 state:NOT ASSIGNED
LTE SCC3 state:NOT ASSIGNED
LTE SCC4 state:NOT ASSIGNED
EMM state: Registered Normal Service
RRC state: RRC Idle
IMS reg state: Full Srv IMS mode: Normal

PCC RxM RSSI: -46 PCC RxM RSRP: -76
PCC RxD RSSI: -57 PCC RxD RSRP: -89
Tx Power: – TAC: 2f06 (12038)
RSRQ (dB): -9.8 Cell ID: 054b7d16 (88833302)
SINR (dB): 22.2

OK

Any thoughts on why it is dropping the connection ?

Thanks in advance

/Otto

Hi @otto

Before you enable the data connection with at!scact=1,3, has a data connection existed? If a data connection existed before, you can try to disconnect it and start the data connection with at!scact=1,3.

Thanks.

Hi Donald !

Yes, the connection was present previously. In fact I discovered that if I release the DHCP address and bring the ethernet interface (eth1) down before issuing the at!scact=1,3 command it seems to come back every time (after also restarting udhcpc).

Thanks !

/Otto

Hi @otto

Could you check some information:

  1. List and checked PDP context activation by command AT+CGDCONT?, AT+CGACT? If the 3rd PDP wasn’t activated that means the response has +CGACT: 3,0 then active this PDP by command AT+CGACT=1,3.
    And then check the IP address of the 3rd PDP by command AT+CGPADDR?
  2. On Linux, help to check network interface by command “ifconfig -a” (EM7565 must be mounted to Linux).

Please check it and share your result.

Thanks.

Hi Donald !

In the main loop I now check for the link to be up with at!scact?, and if its down I bring down the Linux network interface (eth1) and run at!scact=1,3 again. In the same loop if I detect that the linux network interface is not in the “Running” state I restart udhcpc. That seems to be able to recover from the situations I have ran into.

My system has two modems and antennas are quite close (1" away). Can that cause one of the modems to go down ? (Due to the other modem seeing a very strong incoming signal/ high noise floor) or something like that…? I’m not sure how to explain why ping test works well but when running full speed one of the modems end up going down after 5-10sec typically. If it was a power problem I would think it would reboot ?

Thanks for you help !

/Otto

Hi @otto

  1. Could you check again and provide some information above?
  2. Does this problem happen on another SIM or network operation?
  3. Have you tried this problem on your system has one modem? Does it happen?

Thanks.

Hi Donald !

I ran speedtest -I [eth1/eth2] in parallel to cause eth2 to stop working. Then I checked the status as you requested

AT+CGDCONT?
+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”,“vzwclass6”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0

OK
AT+CGACT?
+CGACT: 1,1
+CGACT: 2,1
+CGACT: 3,0
+CGACT: 4,0
+CGACT: 5,0
+CGACT: 6,0

OK
AT+CGACT=1,3
OK
AT+CGPADDR?
ERROR
AT+CGACT?
+CGACT: 1,1
+CGACT: 2,1
+CGACT: 3,1
+CGACT: 4,0
+CGACT: 5,0
+CGACT: 6,0

OK
AT+CGPADDR?
ERROR
AT+CGACT=0,1
ERROR
AT+CGACT=0,1
ERROR
AT+CGACT=0,2
ERROR
AT+CGACT?
+CGACT: 1,1
+CGACT: 2,1
+CGACT: 3,1
+CGACT: 4,0
+CGACT: 5,0
+CGACT: 6,0

OK
AT+CGPADDR?
ERROR


Interestingly PDP1 and 2 are enabled, although that is not something I did (first modem, which is still in
a working state had both PDP 2 & 3 enabled after the test). PDP 3 went to 0 after running the test, but even after setting it back to one the CGPADDR? command failed. This time I was not able to get the interface back up by renewing DHCP or ifconfig eth2 down.

2). Running low-speed tests like ping runs for days w/o problems. I have not tested this on any other carrier or SIM at this point, but I can try AT&T shortly.

3). I put one modem to sleep and just ran the test on eth2. Ran 4x in a row w/o any problems. Running in parallel it usually dies first time, although once I’ve seen it get to the second test run. I checked the PDPs and 1-3 are enabled

I checked the voltage with at!pcvolt? and it did not go below 3.247V while the speedtest was running

Is there any command I can use to see reason for disconnect ? Can one of the serial ports be configured for debug logging ?

Thanks for your help Donald !

/Otto