wip_bearerStart() times out - no ADL_GPRS_EVENT_ACTIVATE_OK

Has anyone seen an issue where the bearer connection attempt times out and the ADL_GPRS_EVENT_ACTIVATE_OK event never happens?

I’m finding approximately 4 in 10 requests timeout. Restarting the module doesn’t always clear the problem as subsequent connections can fail as well. I’ve spoken to the APN provider who cannot find an issue. The problem can be reproduced in multiple static locations with very high signal strength.

Normally I see the ADL_GPRS_EVENT_ACTIVATE_OK event after 2 - 3 seconds. My timeout is currently 8 seconds but it still fails to connect even if I set the timeout to 60 seconds. If it fails to connect within a few seconds then it seems it’s not going to.

I’d really appreciate any input from people who have seen this before and hopefully worked around it.


22:09:02:257;001;ADL;4;(Gprs) Registered on GSM network.
22:09:02:257;002;ADL;4;(Gprs) SIM initialised, going online
22:09:02:351;004;ADL;1;Issued wip_bearerSetOpts()
22:09:02:351;005;ADL;31;[ADL] Gprs subs 107A900B : 0
22:09:02:351;006;ADL;16;[ADL port] IsAvailable(80) : 1
22:09:02:351;007;ADL;31;[ADL] Gprs setup 1 : 0
22:09:02:351;008;ADL;1;Issued wip_bearerStart()
22:09:02:351;010;ADL;16;[ADL port] IsAvailable(80) : 1
22:09:02:429;001;PWRMGR;1;Index 3 not found for Dlci = 6
22:09:02:429;002;PWRMGR;1;Index 4 not found for Dlci = 2
22:09:02:429;003;L3SMG;1;smg_vOpenDlcCnf 6 0 
22:09:02:429;004;L3SMG;1;smg_vOpenDlcCnf 2 0 
22:09:02:429;005;L3SMG;1;=============>Send MDM Data Link Sync Indication
22:09:02:429;006;L3SMG;1;45 43 4d 31 00 04 00 02 00 00 20 00 
22:09:02:429;007;L3SMG;1;=============>1st sync msg write return: 0xc
22:09:02:429;008;L3SMG;1;=============>2nd sync msg write return: 0xc
22:09:02:429;009;L3SMG;1;DLC 2 sync'd
22:09:02:772;001;L3SMG;1;smg_psSelectCtxFromCid - ctx not found in queue
22:09:02:772;002;L3SMG;1;smg_psSelectCtxFromCid - ctx not found in queue
22:09:03:068;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:03:271;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:05:283;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:05:486;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:07:499;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:07:701;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:09:714;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:09:917;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:11:929;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:12:132;001;IOB;1;bsp_io_SetLev 0x00008000-0x00008000
22:09:12:272;001;ADL;1;Bearer restart timed out after 8 seconds
"DWL"," S4_1_0_13BT R2032 CNSZXD00000132 2014/02/26 09:41:35","","Sierra Wireless",0,"","00000000","00000000"
"FW","FW_752_68.SL808Fx","R7.52.0.201404040850.SL8082T","Sierra Wireless",1790532,"040414 08:50","298b2dad","10002020"
"MODEM 3G+","Revision: S4_1_0_13AP R2032 CNSZXD00000132 2014/02/26 09:41:35"
 -"Developer Studio",""
 -"Open AT OS Package",""
 -"Firmware Package",""
 -"Internet Library Package",""
 -"Location Library Package",""

Hi David,

my comments say that 4-5 seconds are normal, sometimes 10 is not enough, now the limit is 100s.
After some tweaking I’d say 80 seconds is a good timeout for anything related to GPRS.
Always be prepared to restart bearer, WIP or module if something fails several times in a row.
Also, first sending AT+CGATT=1 catches most errors (weak signal, no GPRS, long timeout, …?) before entering the WIP jungle.