MC7430: Unable to activate data connection after driver update

[MarkusHaerer]

Greetings,

on our device running Windows 7 Embedded, 32 bit, Build 7601, I updated the modem drivers from GenericDriverSetup_Build4743.exe to GenericDriverSetup_5087.exe and since then I’m unable to activate the data connection. Poking the device with AT commands I don’t see anything unusual:

at+ccid?
+CCID: 8964050087211866392F


OK
at+cimi
530058721186639

OK
at!sku?
SKU: 1104645

OK
at!hwid?
Revision: 1.0


OK
at!impref?
!IMPREF:
 preferred fw version:    02.33.03.00
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_002.072_000
 preferred subpri index:  000
 current fw version:      02.33.03.00
 current carrier name:    GENERIC
 current config name:     GENERIC_002.072_000
 current subpri index:    000

OK
at!priid?
PRI Part Number: 9909771
Revision: 001.001
Customer: Generic-M2M

Carrier PRI: 9999999_9904609_SWI9X30C_02.33.03.00_00_GENERIC_002.072_000
Carrier PRI: 9999999_9905214_SWI9X30C_02.33.03.00_00_DOCOMO_001.049_000
Carrier PRI: 9999999_9905378_SWI9X30C_02.33.03.00_00_KDDI_001.047_000
Carrier PRI: 9999999_9906079_SWI9X30C_02.33.03.00_00_SOFTBANK_001.047_000
Carrier PRI: 9999999_9904890_SWI9X30C_02.33.03.00_00_TELSTRA_002.067_000

OK
at!usbcomp?
Config Index: 1
Config Type:  1 (Generic)
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0)

OK
at!gstatus?
!GSTATUS:
Current Time:  70722            Temperature: 45
Reset Counter: 1                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
LTE band:      B40              LTE bw:      20 MHz
LTE Rx chan:   39052            LTE Tx chan: 39250
LTE CA state:  NOT ASSIGNED
EMM state:     Registered       Normal Service
RRC state:     RRC Idle
IMS reg state: No Srv

PCC RxM RSSI:  -54              RSRP (dBm):  -84
PCC RxD RSSI:  -89              RSRP (dBm):  -122
Tx Power:      --               TAC:         6E15 (28181)
RSRQ (dB):     -10.1            Cell ID:     0493EB76 (76802934)
SINR (dB):     20.8


OK
at+cops?
+cops: 0,0,"Spark NZ",7

OK
at+cgdcont?
+CGDCONT: 1,"IP","redacted_private_apn","0.0.0.0",0,0,0,0

OK
at!uims?
!UIMS: 0

OK
at!band?
Index, Name,                        GW Band Mask     L Band Mask      TDS Band Mask
00, All bands,                      100600000C400000 000001E0081600D5 0000000000000020


OK
at+creg?
+CREG: 0,1

OK
at+cgreg?
+CGREG: 0,1

OK
at+cereg?
+CEREG: 0,1

OK
at+cgpaddr
+CGPADDR: 1,10.211.7.191

OK
at!scact?
!SCACT: 1,0

OK
at!scact=1,1
+CME ERROR: no network service

So it seems the modem has an IP address. This is also confirmed when I check the SIM status in Sparks online diagnosis tool:

So why does the at!scact=1,1 command fail and I don’t have a data connection in Windows?

[jyijyi]

How about using skylight tool?

Skylight Windows Connection Manager for EM/MC series modules

https://source.sierrawireless.com/resources/#tags=Skylight|Development+Tools|legacy+content

[MarkusHaerer]

Hi, thanks for looking into this Using the skylight tool I’m able to connect:

But even while connected with skylight at!scact? reports !SCACT: 1,0 which means data is not active, right? How can that be the explained? Also, while it’s nice that it works with skylight, this is an embedded device and being able to control the modem from our application through AT commands is crucial for us.

In case it helps here is the skylight log from a successful connect:

Skylight 2024-11-15_22.56.39.909.txt

Nov-15 23:15:12.440 130495.106438 00000ba4 t :   772 UICMD_CONNECT
Nov-15 23:15:12.440 130495.106619 00000ba4 h : + CWirelessServicesFsm::OnCmdConnect()
Nov-15 23:15:12.440 130495.106936 00000ba4 i :   Profile ID: 34
Nov-15 23:15:12.440 130495.107125 00000ba4 i :   Start WirelessData (03ED0E68) session
Nov-15 23:15:12.440 130495.107918 00000ba4 h : + CGuiMgr::UpdateState()
Nov-15 23:15:12.440 130495.108090 00000ba4 t :   WirelessData -> WirelessDataConnecting
Nov-15 23:15:12.456 130495.114335 00000ba4 t :   DisplayIdle (H1H2) "Spark NZ-"
Nov-15 23:15:12.456 130495.114622 00000ba4 h : + CGuiMgr::UpdateMenus
Nov-15 23:15:12.456 130495.114801 00000ba4 i :   UpdateMenus: WirelessDataConnecting
Nov-15 23:15:12.456 130495.116721 00000ba4 h : - CGuiMgr::UpdateMenus (Duration: 0ms, Total time: 0ms, Calls: 25)
Nov-15 23:15:12.456 130495.116987 00000ba4 h : - CGuiMgr::UpdateState() (Duration: 16ms, Total time: 250ms, Calls: 46)
Nov-15 23:15:12.456 130495.117172 00000ba4 h : - CWirelessServicesFsm::OnCmdConnect() (Duration: 16ms, Total time: 77ms, Calls: 8)
Nov-15 23:15:12.456 130495.117447 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:2)
Nov-15 23:15:12.456 130495.117657 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:12.456 130495.117843 00000ba4 t :   WDMGR_NOTIF_SessionState _Sessionstate 1
Nov-15 23:15:12.456 130495.119025 00000ba4 h : + CGuiMgr::UpdateState()
Nov-15 23:15:12.456 130495.119280 00000ba4 t :   WirelessDataConnecting -> WirelessDataConnecting
Nov-15 23:15:12.456 130495.119463 00000ba4 h : - CGuiMgr::UpdateState() (Duration: 0ms, Total time: 250ms, Calls: 47)
Nov-15 23:15:12.456 130495.119645 00000ba4 t :   DisplayDataConnecting (H1M2) "Spark NZ-Verbindung zu Spark NZ wird hergestellt"
Nov-15 23:15:12.909 130495.565591 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:2)
Nov-15 23:15:12.909 130495.565792 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:12.909 130495.565970 00000ba4 t :   WDMGR_NOTIF_SessionState _Sessionstate 1
Nov-15 23:15:12.909 130495.567403 00000ba4 h : + CGuiMgr::UpdateState()
Nov-15 23:15:12.909 130495.568283 00000ba4 t :   WirelessDataConnecting -> WirelessDataConnecting
Nov-15 23:15:12.909 130495.568482 00000ba4 h : - CGuiMgr::UpdateState() (Duration: 0ms, Total time: 250ms, Calls: 48)
Nov-15 23:15:12.909 130495.568671 00000ba4 t :   DisplayDataConnecting (H1M2) "Spark NZ-Verbindung zu Spark NZ wird hergestellt"
Nov-15 23:15:13.315 130495.981819 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:7)
Nov-15 23:15:13.315 130495.982027 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:13.315 130495.982246 00000ba4 i :   TYPE_WSMGR_DataCapability eDataCapability: 9, eTechnology: 2, attached: 1
Nov-15 23:15:13.315 130495.983497 00000ba4 i :   SetIndDataCovgEvdo eIconState: 25
Nov-15 23:15:13.402 130496.055105 00000ba4 t :   CWaMainDlg::OnHandleNetworkAccessNotification(type:1)
Nov-15 23:15:13.402 130496.055347 00000ba4 i :   WS: WirelessData E_NetworkAccess
Nov-15 23:15:13.403 130496.055533 00000ba4 i :   WS: NetworkCapable E_NetworkAccess
Nov-15 23:15:13.403 130496.056140 00000ba4 t :   1- LteRsrp: -82 Rsrq: -11 Snr: 20.400000 NetworkId: 5
Nov-15 23:15:13.403 130496.056370 00000ba4 t :   arrRsrpSnr[i].iRsrp: -85 arrRsrpSnr[i].iSnr: 13.000000
Nov-15 23:15:13.404 130496.056554 00000ba4 t :   arrRsrpSnr[i].iBars: 5
Nov-15 23:15:14.420 130497.074450 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:7)
Nov-15 23:15:14.420 130497.074662 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:14.420 130497.074880 00000ba4 i :   TYPE_WSMGR_DataCapability eDataCapability: 9, eTechnology: 2, attached: 1
Nov-15 23:15:14.421 130497.075566 00000ba4 i :   SetIndDataCovgEvdo eIconState: 25
Nov-15 23:15:15.159 130497.812566 00000ba4 t :   CWaMainDlg::OnHandleNetworkAccessNotification(type:1)
Nov-15 23:15:15.159 130497.812809 00000ba4 i :   WS: WirelessData E_NetworkAccess
Nov-15 23:15:15.159 130497.812986 00000ba4 i :   WS: NetworkCapable E_NetworkAccess
Nov-15 23:15:15.160 130497.813609 00000ba4 t :   1- LteRsrp: -81 Rsrq: -10 Snr: 19.800000 NetworkId: 5
Nov-15 23:15:15.160 130497.813845 00000ba4 t :   arrRsrpSnr[i].iRsrp: -85 arrRsrpSnr[i].iSnr: 13.000000
Nov-15 23:15:15.160 130497.814016 00000ba4 t :   arrRsrpSnr[i].iBars: 5
Nov-15 23:15:16.084 130498.738676 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:2)
Nov-15 23:15:16.084 130498.738885 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:16.084 130498.739060 00000ba4 t :   WDMGR_NOTIF_SessionState _Sessionstate 3
Nov-15 23:15:16.085 130498.739397 00000ba4 h : + CGuiMgr::UpdateState()
Nov-15 23:15:16.085 130498.739583 00000ba4 t :   WirelessDataConnecting -> WirelessDataSession
Nov-15 23:15:16.093 130498.747353 00000ba4 t :   DisplayIdle (H1H2) "Spark NZ-"
Nov-15 23:15:16.095 130498.749041 00000ba4 h : + CGuiMgr::UpdateMenus
Nov-15 23:15:16.095 130498.749258 00000ba4 i :   UpdateMenus: WirelessDataSession
Nov-15 23:15:16.098 130498.752687 00000ba4 h : - CGuiMgr::UpdateMenus (Duration: 0ms, Total time: 0ms, Calls: 26)
Nov-15 23:15:16.099 130498.752968 00000ba4 h : - CGuiMgr::UpdateState() (Duration: 16ms, Total time: 266ms, Calls: 49)
Nov-15 23:15:16.099 130498.753600 00000ba4 i :   TYPE_WSMGR_DataCapability eDataCapability: 9, eTechnology: 2, attached: 1
Nov-15 23:15:16.100 130498.754324 00000ba4 i :   SetIndDataCovgEvdo eIconState: 26
Nov-15 23:15:16.101 130498.755627 00000ba4 t :   DisplayDataConnected(): in 0, out 0
Nov-15 23:15:16.103 130498.757598 00000ba4 h : + CWirelessServicesFsm::RunAutoLaunchOption()
Nov-15 23:15:16.104 130498.757860 00000ba4 t :   WaGetAutoLaunchSettings szIMEI: 359074061814622, Profile 34
Nov-15 23:15:16.104 130498.758375 00000ba4 h : + CAutoLaunchHelper::ExecuteAutoLaunchOption()
Nov-15 23:15:16.104 130498.758586 00000ba4 h : - CAutoLaunchHelper::ExecuteAutoLaunchOption() (Duration: 0ms, Total time: 0ms, Calls: 3)
Nov-15 23:15:16.105 130498.758787 00000ba4 h : - CWirelessServicesFsm::RunAutoLaunchOption() (Duration: 0ms, Total time: 0ms, Calls: 3)
Nov-15 23:15:16.167 130498.821876 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:3)
Nov-15 23:15:16.167 130498.822090 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:16.168 130498.822354 00000ba4 t :   DisplayDataConnected(): in 323, out 1396
Nov-15 23:15:16.169 130498.824038 00000ba4 t :   DisplayDataConnected (H1H2) "Spark NZ-"
Nov-15 23:15:17.661 130500.314418 00000ba4 t :   CWaMainDlg::OnHandleNetworkAccessNotification(type:1)
Nov-15 23:15:17.661 130500.314825 00000ba4 i :   WS: WirelessData E_NetworkAccess
Nov-15 23:15:17.661 130500.315006 00000ba4 i :   WS: NetworkCapable E_NetworkAccess
Nov-15 23:15:17.662 130500.315629 00000ba4 t :   1- LteRsrp: -82 Rsrq: -11 Snr: 13.800000 NetworkId: 5
Nov-15 23:15:17.662 130500.315861 00000ba4 t :   arrRsrpSnr[i].iRsrp: -85 arrRsrpSnr[i].iSnr: 13.000000
Nov-15 23:15:17.662 130500.316032 00000ba4 t :   arrRsrpSnr[i].iBars: 5
Nov-15 23:15:17.745 130500.398751 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:2)
Nov-15 23:15:17.745 130500.398956 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:17.745 130500.399132 00000ba4 t :   WDMGR_NOTIF_SessionState _Sessionstate 3
Nov-15 23:15:17.746 130500.399470 00000ba4 h : + CGuiMgr::UpdateState()
Nov-15 23:15:17.746 130500.399655 00000ba4 t :   WirelessDataSession -> WirelessDataSession
Nov-15 23:15:17.746 130500.399835 00000ba4 t :   DisplayIdle (H1H2) "Spark NZ-"
Nov-15 23:15:17.748 130500.401361 00000ba4 h : - CGuiMgr::UpdateState() (Duration: 0ms, Total time: 266ms, Calls: 50)
Nov-15 23:15:17.836 130500.490435 00000ba4 t :   CWaMainDlg::OnHandleWirelessDataNotification(type:3)
Nov-15 23:15:17.836 130500.490648 00000ba4 i :   WS: WirelessData E_WirelessData
Nov-15 23:15:17.836 130500.490865 00000ba4 t :   DisplayDataConnected(): in 323, out 2149
Nov-15 23:15:17.838 130500.492546 00000ba4 t :   DisplayDataConnected (H1H2) "Spark NZ-"

GobiApi-Skylight 2024-11-15_22.56.45.534.tbd

Nov-15 23:15:13.315 130495.978574 00000a78 t :   Message received from service type WDS
Nov-15 23:15:13.315 130495.978848 00000a78 i :   WDS: <<<<<-----
Nov-15 23:15:13.315 130495.979025 00000a78 i :      04 05 00 22 00 12 00 01 02 00 02 00 12 01 00 04   ..."............
Nov-15 23:15:13.315 130495.979202 00000a78 i :      13 02 00 80 88 14 01 00 05                        .........
Nov-15 23:15:13.315 130495.979377 00000a78 t :   HandleTransactionIndication TransactionId: 5 MessageId: 34 Length: 18
Nov-15 23:15:13.315 130495.979643 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:13.315 130495.979826 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:13.315 130495.979999 00000ce4 i :      04 0E 00 22 00 12 00 01 02 00 02 00 12 01 00 04   ..."............
Nov-15 23:15:13.315 130495.980173 00000ce4 i :      13 02 00 80 88 14 01 00 05                        .........
Nov-15 23:15:13.315 130495.980349 00000ce4 t :   HandleTransactionIndication TransactionId: 14 MessageId: 34 Length: 18
Nov-15 23:15:13.315 130495.980559 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:13.315 130495.980730 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:13.315 130495.980902 00000ce4 i :      04 0F 00 01 00 04 00 18 01 00 01                  ...........
Nov-15 23:15:13.315 130495.981078 00000ce4 t :   HandleTransactionIndication TransactionId: 15 MessageId: 1 Length: 4
Nov-15 23:15:13.315 130495.981249 00000ce4 h : + m_pDormancyStatusCallback
Nov-15 23:15:13.375 130496.027995 00000ce4 h : - m_pDormancyStatusCallback (Duration: 63ms, Total time: 407ms, Calls: 7)
Nov-15 23:15:13.400 130496.053377 00000b2c t :   Message received from service type NAS
Nov-15 23:15:13.401 130496.053666 00000b2c i :   NAS: <<<<<-----
Nov-15 23:15:13.401 130496.053866 00000b2c i :      04 50 00 51 00 09 00 14 06 00 CC F5 AE FF CC 00   .P.Q............
Nov-15 23:15:13.401 130496.054051 00000b2c i :                                                        
Nov-15 23:15:13.401 130496.054226 00000b2c t :   HandleTransactionIndication TransactionId: 80 MessageId: 81 Length: 9
Nov-15 23:15:13.401 130496.054394 00000b2c h : + NasService::HandleTransactionIndication
Nov-15 23:15:13.402 130496.054609 00000b2c h : + NasService::HandleSigInfoIndication
Nov-15 23:15:13.402 130496.054783 00000b2c h : + m_pSwiSigInfoCallback
Nov-15 23:15:13.404 130496.057168 00000b2c h : - m_pSwiSigInfoCallback (Duration: 0ms, Total time: 579ms, Calls: 39)
Nov-15 23:15:13.404 130496.057407 00000b2c h : - NasService::HandleSigInfoIndication (Duration: 0ms, Total time: 579ms, Calls: 39)
Nov-15 23:15:13.405 130496.057599 00000b2c h : - NasService::HandleTransactionIndication (Duration: 0ms, Total time: 1017ms, Calls: 80)
Nov-15 23:15:14.094 130496.748270 00000950 h : + GetConnectionRate
Nov-15 23:15:14.094 130496.748479 00000950 i :   WDS AddRef: 2
Nov-15 23:15:14.094 130496.748651 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:14.094 130496.748819 00000950 t :   TransactionId: 26
Nov-15 23:15:14.095 130496.749000 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:14.095 130496.749171 00000950 i :      00 1A 00 23 00 00 00                              ...#...
Nov-15 23:15:14.095 130496.749357 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:14.418 130497.073052 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:14.419 130497.073332 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:14.419 130497.073514 00000ce4 i :      04 10 00 01 00 04 00 18 01 00 02                  ...........
Nov-15 23:15:14.419 130497.073692 00000ce4 t :   HandleTransactionIndication TransactionId: 16 MessageId: 1 Length: 4
Nov-15 23:15:14.419 130497.073864 00000ce4 h : + m_pDormancyStatusCallback
Nov-15 23:15:14.482 130497.136304 00000ce4 h : - m_pDormancyStatusCallback (Duration: 63ms, Total time: 470ms, Calls: 8)
Nov-15 23:15:14.681 130497.335164 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:14.681 130497.335434 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:14.681 130497.335613 00000ce4 i :      02 1A 00 23 00 1A 00 02 04 00 00 00 00 00 01 10   ...#............
Nov-15 23:15:14.681 130497.335798 00000ce4 i :      00 FF FF FF FF FF FF FF FF 80 F0 FA 02 00 A3 E1   ................
Nov-15 23:15:14.682 130497.335975 00000ce4 i :      11                                                .
Nov-15 23:15:14.682 130497.336144 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:14.682 130497.336310 00000ce4 t :   Response ID: 26
Nov-15 23:15:14.682 130497.336481 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 26
Nov-15 23:15:14.682 130497.336650 00000ce4 t :   Signal response
Nov-15 23:15:14.722 130497.376099 00000950 t :   Waiting for response
Nov-15 23:15:14.722 130497.376366 00000950 t :   Transaction response received, msgID 35
Nov-15 23:15:14.722 130497.376545 00000950 i :   WDS Release: 1
Nov-15 23:15:14.722 130497.376721 00000950 h : - GetConnectionRate (Duration: 625ms, Total time: 2486ms, Calls: 5)
Nov-15 23:15:14.723 130497.377142 00000950 h : + SwiGetDataBearerTechnologyEx
Nov-15 23:15:14.723 130497.377316 00000950 i :   WDS AddRef: 2
Nov-15 23:15:14.723 130497.377487 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:14.723 130497.377655 00000950 t :   TransactionId: 27
Nov-15 23:15:14.724 130497.377887 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:14.724 130497.378063 00000950 i :      00 1B 00 91 00 00 00                              .......
Nov-15 23:15:14.724 130497.378247 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:14.896 130497.550097 00000950 t :   Waiting for response
Nov-15 23:15:14.983 130497.637585 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:14.984 130497.637833 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:14.984 130497.638009 00000ce4 i :      02 1B 00 91 00 1A 00 02 04 00 00 00 00 00 10 10   ................
Nov-15 23:15:14.984 130497.638207 00000ce4 i :      00 00 00 00 00 03 00 00 00 00 20 00 00 00 00 00   .......... .....
Nov-15 23:15:14.984 130497.638396 00000ce4 i :      00                                                .
Nov-15 23:15:14.985 130497.638576 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:14.985 130497.638744 00000ce4 t :   Response ID: 27
Nov-15 23:15:14.985 130497.638916 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 27
Nov-15 23:15:14.985 130497.639085 00000ce4 t :   Signal response
Nov-15 23:15:14.985 130497.639270 00000950 t :   Transaction response received, msgID 145
Nov-15 23:15:14.985 130497.639447 00000950 i :   WDS Release: 1
Nov-15 23:15:14.986 130497.639786 00000950 h : - SwiGetDataBearerTechnologyEx (Duration: 265ms, Total time: 1827ms, Calls: 5)
Nov-15 23:15:14.987 130497.640577 00000950 h : + GetWds2IPAddress
Nov-15 23:15:14.987 130497.640755 00000950 i :   WDS AddRef: 2
Nov-15 23:15:14.987 130497.640925 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:14.987 130497.641093 00000950 t :   TransactionId: 5
Nov-15 23:15:14.987 130497.641264 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:14.987 130497.641438 00000950 i :      00 05 00 2D 00 07 00 10 04 00 00 81 00 00         ...-..........
Nov-15 23:15:14.988 130497.641635 00000950 i :   Writing to 0x00000678
Nov-15 23:15:15.157 130497.810907 00000b2c t :   Message received from service type NAS
Nov-15 23:15:15.157 130497.811181 00000b2c i :   NAS: <<<<<-----
Nov-15 23:15:15.157 130497.811358 00000b2c i :      04 51 00 51 00 09 00 14 06 00 CC F6 AF FF C6 00   .Q.Q............
Nov-15 23:15:15.158 130497.811546 00000b2c i :                                                        
Nov-15 23:15:15.158 130497.811721 00000b2c t :   HandleTransactionIndication TransactionId: 81 MessageId: 81 Length: 9
Nov-15 23:15:15.158 130497.811889 00000b2c h : + NasService::HandleTransactionIndication
Nov-15 23:15:15.158 130497.812056 00000b2c h : + NasService::HandleSigInfoIndication
Nov-15 23:15:15.158 130497.812224 00000b2c h : + m_pSwiSigInfoCallback
Nov-15 23:15:15.161 130497.814649 00000b2c h : - m_pSwiSigInfoCallback (Duration: 0ms, Total time: 579ms, Calls: 40)
Nov-15 23:15:15.161 130497.814890 00000b2c h : - NasService::HandleSigInfoIndication (Duration: 0ms, Total time: 579ms, Calls: 40)
Nov-15 23:15:15.161 130497.815069 00000b2c h : - NasService::HandleTransactionIndication (Duration: 0ms, Total time: 1017ms, Calls: 81)
Nov-15 23:15:15.162 130497.815868 00000a78 t :   Message received from service type WDS
Nov-15 23:15:15.162 130497.816117 00000a78 i :   WDS: <<<<<-----
Nov-15 23:15:15.163 130497.816304 00000a78 i :      02 05 00 2D 00 12 00 02 04 00 00 00 00 00 1E 04   ...-............
Nov-15 23:15:15.163 130497.816482 00000a78 i :      00 BF 07 D3 0A 2B 01 00 04                        .....+...
Nov-15 23:15:15.163 130497.816655 00000a78 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:15.163 130497.816823 00000a78 t :   Response ID: 5
Nov-15 23:15:15.163 130497.816994 00000a78 t :   Outstanding transaction 0x03f3d090 - Request ID: 5
Nov-15 23:15:15.163 130497.817161 00000a78 t :   Signal response
Nov-15 23:15:15.228 130497.882139 00000950 t :   Waiting for response
Nov-15 23:15:15.228 130497.882413 00000950 t :   Transaction response received, msgID 45
Nov-15 23:15:15.228 130497.882595 00000950 i :   WDS Release: 1
Nov-15 23:15:15.229 130497.882783 00000950 h : - GetWds2IPAddress (Duration: 235ms, Total time: 2236ms, Calls: 5)
Nov-15 23:15:15.357 130498.011078 00000950 h : + GetDNSSettings
Nov-15 23:15:15.357 130498.011287 00000950 h : + _GetDNSSettings
Nov-15 23:15:15.357 130498.011457 00000950 i :   WDS AddRef: 2
Nov-15 23:15:15.358 130498.011637 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:15.358 130498.011806 00000950 t :   TransactionId: 28
Nov-15 23:15:15.358 130498.011978 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:15.358 130498.012151 00000950 i :      00 1C 00 52 00 00 00                              ...R...
Nov-15 23:15:15.358 130498.012359 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:15.645 130498.298867 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:15.645 130498.299140 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:15.645 130498.299329 00000ce4 i :      02 1C 00 52 00 07 00 02 04 00 01 00 10 00         ...R..........
Nov-15 23:15:15.645 130498.299501 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:15.645 130498.299667 00000ce4 t :   Response ID: 28
Nov-15 23:15:15.646 130498.299867 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 28
Nov-15 23:15:15.646 130498.300036 00000ce4 t :   Signal response
Nov-15 23:15:15.684 130498.338637 00000950 t :   Waiting for response
Nov-15 23:15:15.685 130498.338927 00000950 t :   Transaction response received, msgID 82
Nov-15 23:15:15.685 130498.339108 00000950 E :   Device error code: 1016
Nov-15 23:15:15.685 130498.339276 00000950 i :   WDS Release: 1
Nov-15 23:15:15.685 130498.339452 00000950 h : - _GetDNSSettings (Duration: 328ms, Total time: 2891ms, Calls: 9)
Nov-15 23:15:15.685 130498.339628 00000950 h : - GetDNSSettings (Duration: 328ms, Total time: 1798ms, Calls: 5)
Nov-15 23:15:15.686 130498.339805 00000950 h : + GetDNSIPv6Settings
Nov-15 23:15:15.686 130498.339971 00000950 h : + _GetDNSSettings
Nov-15 23:15:15.686 130498.340137 00000950 i :   WDS AddRef: 2
Nov-15 23:15:15.686 130498.340308 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:15.686 130498.340475 00000950 t :   TransactionId: 29
Nov-15 23:15:15.686 130498.340645 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:15.687 130498.340834 00000950 i :      00 1D 00 52 00 00 00                              ...R...
Nov-15 23:15:15.687 130498.341020 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:15.973 130498.627300 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:15.973 130498.627579 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:15.973 130498.627762 00000ce4 i :      02 1D 00 52 00 07 00 02 04 00 01 00 10 00         ...R..........
Nov-15 23:15:15.974 130498.627948 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:15.974 130498.628116 00000ce4 t :   Response ID: 29
Nov-15 23:15:15.974 130498.628288 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 29
Nov-15 23:15:15.974 130498.628457 00000ce4 t :   Signal response
Nov-15 23:15:16.083 130498.736774 00000950 t :   Waiting for response
Nov-15 23:15:16.083 130498.737214 00000950 t :   Transaction response received, msgID 82
Nov-15 23:15:16.083 130498.737396 00000950 E :   Device error code: 1016
Nov-15 23:15:16.083 130498.737567 00000950 i :   WDS Release: 1
Nov-15 23:15:16.083 130498.737744 00000950 h : - _GetDNSSettings (Duration: 406ms, Total time: 3297ms, Calls: 10)
Nov-15 23:15:16.083 130498.737921 00000950 h : - GetDNSIPv6Settings (Duration: 406ms, Total time: 1499ms, Calls: 5)
Nov-15 23:15:16.187 130498.841515 00000950 h : + GetConnectionRate
Nov-15 23:15:16.188 130498.841753 00000950 i :   WDS AddRef: 2
Nov-15 23:15:16.188 130498.841938 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:16.188 130498.842106 00000950 t :   TransactionId: 30
Nov-15 23:15:16.188 130498.842289 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:16.188 130498.842471 00000950 i :      00 1E 00 23 00 00 00                              ...#...
Nov-15 23:15:16.188 130498.842658 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:16.414 130499.067434 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:16.414 130499.067711 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:16.414 130499.067892 00000ce4 i :      02 1E 00 23 00 1A 00 02 04 00 00 00 00 00 01 10   ...#............
Nov-15 23:15:16.414 130499.068064 00000ce4 i :      00 FF FF FF FF FF FF FF FF 80 F0 FA 02 00 A3 E1   ................
Nov-15 23:15:16.414 130499.068242 00000ce4 i :      11                                                .
Nov-15 23:15:16.415 130499.068425 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:16.415 130499.068916 00000ce4 t :   Response ID: 30
Nov-15 23:15:16.415 130499.069112 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 30
Nov-15 23:15:16.416 130499.069308 00000ce4 t :   Signal response
Nov-15 23:15:16.552 130499.206251 00000950 t :   Waiting for response
Nov-15 23:15:16.552 130499.206522 00000950 t :   Transaction response received, msgID 35
Nov-15 23:15:16.552 130499.206701 00000950 i :   WDS Release: 1
Nov-15 23:15:16.552 130499.206878 00000950 h : - GetConnectionRate (Duration: 360ms, Total time: 2846ms, Calls: 6)
Nov-15 23:15:16.553 130499.207342 00000950 h : + SwiGetDataBearerTechnologyEx
Nov-15 23:15:16.553 130499.207518 00000950 i :   WDS AddRef: 2
Nov-15 23:15:16.553 130499.207688 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:16.553 130499.207857 00000950 t :   TransactionId: 31
Nov-15 23:15:16.554 130499.208088 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:16.554 130499.208261 00000950 i :      00 1F 00 91 00 00 00                              .......
Nov-15 23:15:16.554 130499.208446 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:16.767 130499.421738 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:16.768 130499.422024 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:16.768 130499.422204 00000ce4 i :      02 1F 00 91 00 1A 00 02 04 00 00 00 00 00 10 10   ................
Nov-15 23:15:16.768 130499.422378 00000ce4 i :      00 00 00 00 00 03 00 00 00 00 20 00 00 00 00 00   .......... .....
Nov-15 23:15:16.768 130499.422552 00000ce4 i :      00                                                .
Nov-15 23:15:16.769 130499.423201 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:16.770 130499.424171 00000ce4 t :   Response ID: 31
Nov-15 23:15:16.771 130499.425222 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 31
Nov-15 23:15:16.772 130499.426268 00000ce4 t :   Signal response
Nov-15 23:15:16.854 130499.508107 00000950 t :   Waiting for response
Nov-15 23:15:16.854 130499.508381 00000950 t :   Transaction response received, msgID 145
Nov-15 23:15:16.854 130499.508559 00000950 i :   WDS Release: 1
Nov-15 23:15:16.855 130499.508746 00000950 h : - SwiGetDataBearerTechnologyEx (Duration: 297ms, Total time: 2124ms, Calls: 6)
Nov-15 23:15:16.855 130499.509518 00000950 h : + GetWds2IPAddress
Nov-15 23:15:16.856 130499.509705 00000950 i :   WDS AddRef: 2
Nov-15 23:15:16.856 130499.509877 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:16.856 130499.510045 00000950 t :   TransactionId: 6
Nov-15 23:15:16.856 130499.510217 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:16.856 130499.510390 00000950 i :      00 06 00 2D 00 07 00 10 04 00 00 81 00 00         ...-..........
Nov-15 23:15:16.856 130499.510577 00000950 i :   Writing to 0x00000678
Nov-15 23:15:17.297 130499.952014 00000a78 t :   Message received from service type WDS
Nov-15 23:15:17.298 130499.952297 00000a78 i :   WDS: <<<<<-----
Nov-15 23:15:17.298 130499.952474 00000a78 i :      02 06 00 2D 00 12 00 02 04 00 00 00 00 00 1E 04   ...-............
Nov-15 23:15:17.298 130499.952648 00000a78 i :      00 BF 07 D3 0A 2B 01 00 04                        .....+...
Nov-15 23:15:17.298 130499.952819 00000a78 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:17.298 130499.952986 00000a78 t :   Response ID: 6
Nov-15 23:15:17.299 130499.953167 00000a78 t :   Outstanding transaction 0x03f3d090 - Request ID: 6
Nov-15 23:15:17.299 130499.953335 00000a78 t :   Signal response
Nov-15 23:15:17.338 130499.992407 00000950 t :   Waiting for response
Nov-15 23:15:17.338 130499.992676 00000950 t :   Transaction response received, msgID 45
Nov-15 23:15:17.338 130499.992858 00000950 i :   WDS Release: 1
Nov-15 23:15:17.338 130499.993035 00000950 h : - GetWds2IPAddress (Duration: 484ms, Total time: 2720ms, Calls: 6)
Nov-15 23:15:17.362 130500.015729 00000950 h : + GetDNSSettings
Nov-15 23:15:17.362 130500.015935 00000950 h : + _GetDNSSettings
Nov-15 23:15:17.362 130500.016105 00000950 i :   WDS AddRef: 2
Nov-15 23:15:17.362 130500.016298 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:17.362 130500.016479 00000950 t :   TransactionId: 32
Nov-15 23:15:17.363 130500.016660 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:17.363 130500.016831 00000950 i :      00 20 00 52 00 00 00                              . .R...
Nov-15 23:15:17.363 130500.017016 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:17.510 130500.164392 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:17.510 130500.164664 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:17.510 130500.164844 00000ce4 i :      02 20 00 52 00 07 00 02 04 00 01 00 10 00         . .R..........
Nov-15 23:15:17.511 130500.165028 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:17.511 130500.165195 00000ce4 t :   Response ID: 32
Nov-15 23:15:17.511 130500.165366 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 32
Nov-15 23:15:17.511 130500.165535 00000ce4 t :   Signal response
Nov-15 23:15:17.559 130500.213114 00000950 t :   Waiting for response
Nov-15 23:15:17.559 130500.213383 00000950 t :   Transaction response received, msgID 82
Nov-15 23:15:17.559 130500.213559 00000950 E :   Device error code: 1016
Nov-15 23:15:17.559 130500.213728 00000950 i :   WDS Release: 1
Nov-15 23:15:17.560 130500.213915 00000950 h : - _GetDNSSettings (Duration: 188ms, Total time: 3485ms, Calls: 11)
Nov-15 23:15:17.560 130500.214092 00000950 h : - GetDNSSettings (Duration: 188ms, Total time: 1986ms, Calls: 6)
Nov-15 23:15:17.560 130500.214259 00000950 h : + GetDNSIPv6Settings
Nov-15 23:15:17.560 130500.214425 00000950 h : + _GetDNSSettings
Nov-15 23:15:17.560 130500.214592 00000950 i :   WDS AddRef: 2
Nov-15 23:15:17.560 130500.214762 00000950 t :   Processing QmiTransaction: 0x03f3d090
Nov-15 23:15:17.561 130500.214992 00000950 t :   TransactionId: 33
Nov-15 23:15:17.561 130500.215165 00000950 i :   WDS: ----->>>>>
Nov-15 23:15:17.561 130500.215338 00000950 i :      00 21 00 52 00 00 00                              .!.R...
Nov-15 23:15:17.561 130500.215521 00000950 i :   Writing to 0x0000065c
Nov-15 23:15:17.659 130500.312724 00000b2c t :   Message received from service type NAS
Nov-15 23:15:17.659 130500.313016 00000b2c i :   NAS: <<<<<-----
Nov-15 23:15:17.659 130500.313192 00000b2c i :      04 52 00 51 00 09 00 14 06 00 CC F5 AE FF 8A 00   .R.Q............
Nov-15 23:15:17.659 130500.313367 00000b2c i :                                                        
Nov-15 23:15:17.660 130500.313554 00000b2c t :   HandleTransactionIndication TransactionId: 82 MessageId: 81 Length: 9
Nov-15 23:15:17.660 130500.313722 00000b2c h : + NasService::HandleTransactionIndication
Nov-15 23:15:17.660 130500.313888 00000b2c h : + NasService::HandleSigInfoIndication
Nov-15 23:15:17.660 130500.314058 00000b2c h : + m_pSwiSigInfoCallback
Nov-15 23:15:17.663 130500.316667 00000b2c h : - m_pSwiSigInfoCallback (Duration: 0ms, Total time: 579ms, Calls: 41)
Nov-15 23:15:17.663 130500.316913 00000b2c h : - NasService::HandleSigInfoIndication (Duration: 0ms, Total time: 579ms, Calls: 41)
Nov-15 23:15:17.663 130500.317091 00000b2c h : - NasService::HandleTransactionIndication (Duration: 0ms, Total time: 1017ms, Calls: 82)
Nov-15 23:15:17.703 130500.356907 00000ce4 t :   Message received from service type WDS
Nov-15 23:15:17.703 130500.357181 00000ce4 i :   WDS: <<<<<-----
Nov-15 23:15:17.703 130500.357376 00000ce4 i :      02 21 00 52 00 07 00 02 04 00 01 00 10 00         .!.R..........
Nov-15 23:15:17.704 130500.357550 00000ce4 t :   QmiService::HandleTransactionResponse
Nov-15 23:15:17.704 130500.357718 00000ce4 t :   Response ID: 33
Nov-15 23:15:17.704 130500.357890 00000ce4 t :   Outstanding transaction 0x03f3d090 - Request ID: 33
Nov-15 23:15:17.704 130500.358059 00000ce4 t :   Signal response
Nov-15 23:15:17.743 130500.396988 00000950 t :   Waiting for response
Nov-15 23:15:17.743 130500.397257 00000950 t :   Transaction response received, msgID 82
Nov-15 23:15:17.744 130500.397447 00000950 E :   Device error code: 1016
Nov-15 23:15:17.744 130500.397641 00000950 i :   WDS Release: 1
Nov-15 23:15:17.744 130500.397825 00000950 h : - _GetDNSSettings (Duration: 187ms, Total time: 3672ms, Calls: 12)
Nov-15 23:15:17.744 130500.398002 00000950 h : - GetDNSIPv6Settings (Duration: 187ms, Total time: 1686ms, Calls: 6)

[jyijyi]

Is your end product run in embedded linux or windows?

Can you try in linux?
I remember at!scact should be working in linux.
At least this can prove if your module has problem.

You can see the instruction in linux here

Example on establishing data connection by AT!SCACT via MBPL R20 driver

Here is an example to establish data connection by AT!SCACT via MBPL R20 driver: Module: WP7609 FW: R13 MBPL: R20 PC Environment: Ubuntu 18 need to install the MBPL R20 driver for qmi_wwan and qcserial (MBPL_Drivers_USB_R20_ENG1-src.tar.gz) avoid the Ubuntu changing the network name: ln -s /dev/null /etc/systemd/network/99-default.link sudo apt-get install libqmi-utils sudo apt-get install udhcpc now insert the USB to PC sudo chmod 777 /sys/class/net/wwan0/qmi/raw_ip …

[MarkusHaerer]

Our target runs Windows 7 Embedded, 32 bit, Build 7601. All test happen on the real device, including the test to run skylight.

@jyijyi

Can you try in linux?

Unfortunately that’s not an option. I would also be surprised if the modem has a problem, it worked for years until we performed the driver update. Also the at!scact=1,1 command has been working so far.

If we could we would simply stay on the old driver. But from time to time we see devices that are unable to send data after some time while the provider says the modem is still in a data session. We are hoping a driver update would fix this issue.

[jyijyi]

Then can the skylight with new driver fix the issue?

Btw, did you try the latest firmware with old usb driver?

Lastly, you might also need to check whether mbim can be a workaround for your issue:

EM7455 disconnected, no network connection

Yes there is a sim card in it, the provider is detected but I don’t have internet

[MarkusHaerer]

@jyijyi

Then can the skylight with new driver fix the issue?

Sorry, I can’t follow here. Skylight is able to establish an IP connection using the new driver, the AT command can’t do it. Rolling out skylight to our devices doesn’t look like a good fit as it’s a desktop application and we have an embedded device.

@jyijyi

Btw, did you try the latest firmware with old usb driver?

Originally all our modes were running on SWI9X30C_02.20.03.00 r6691 CARMD-EV-FRMWR2 2016/06/30 10:54:05 and we updated some of them to SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30 hoping that fixes the issue. Unfortunately it didn’t. That’s the latest version approved for Telstra, we didn’t want to switch to a generic configuration fearing worse compatibility with telcos in New Zealand.

@jyijyi

Lastly, you might also need to check whether mbim can be a workaround for your issue:

From the documentation:

Looks like tat would kill at!scact for sure. And migrating away from using AT commands would be a considerable challenge and risk for our operation.

Are there any possibilities to further investigate the root cause of at!scact not working anymore? Any AT commands that could reveal more information? I also have access to more devices that are still on the old driver to compare the outputs with if it would help.

[jyijyi]

I have no idea why the new driver does not work with AT!SCACT…
Does it work for profile 2 for AT!SCACT=1,2 ?

@MarkusHaerer

If we could we would simply stay on the old driver. But from time to time we see devices that are unable to send data after some time while the provider says the modem is still in a data session. We are hoping a driver update would fix this issue.

i would suggest you also to see any AT command to fix this when issue happens.
e.g. restart telecom stack by AT+CFUN=0 and AT+CFUN=1

[MarkusHaerer]

@jyijyi

Does it work for profile 2 for AT!SCACT=1,2 ?

Unfortunately not but the error is a simple ERROR:

@jyijyi

i would suggest you also to see any AT command to fix this when issue happens.
e.g. restart telecom stack by AT+CFUN=0 and AT+CFUN=1

This would be an alternative if the update is a dead end. However, finding out what fixes the problem will be difficult as we are unable to replicate the problem in the lab

[jyijyi]

if you cannot replicate the problem, how can you verify the new driver is fixing the issue or not?

with the old driver, if we change the USB speed to lower speed by AT!USBSPEED command, can it fix the problem?

[MarkusHaerer]

@jyijyi

if you cannot replicate the problem, how can you verify the new driver is fixing the issue or not?

The plan was to perform a limited rollout in production and using monitoring to see if the situation improved.

@jyijyi

with the old driver, if we change the USB speed to lower speed by AT!USBSPEED command, can it fix the problem?

Good suggestion, but our modems are connected through an USB2.0 hub so the speed has always been limited.

[jyijyi]

Since you cannot reproduce the issue in lab, probably only method left is trial and error.

You can try different version of usb driver and see which one can use at!scact

https://source.sierrawireless.com/resources/airprime/software/airprime-mc-series-windows-drivers-qmi-build-history/

After that you can use that version and test in field to see if there is any improvement

[MarkusHaerer]

It looks like build 4836 is working in our initial tests, at least the at!scact=1,1 part is working. We’ll use that to perform our field testing.