Always get "requestQueryDataCall err = 110" after obtained IP address

I used quectel-CM v1.5.9 with busybox udhcpc v1.30.1 trying to get assess to LTE network but failed.

According to log, after it obtained an IP, next step is querying data call, but always failed here.

Following is the full log

root@imx6ul-var-dart:~# /tmp/quectel-CM -s internet -4
[06-10_10:03:06:089] Quectel_QConnectManager_Linux_V1.5.9
[06-10_10:03:06:093] Find /sys/bus/usb/devices/2-1 idVendor=0x2c7c idProduct=0x125, bus=0x002, dev=0x004
[06-10_10:03:06:094] Auto find qmichannel = /dev/cdc-wdm0
[06-10_10:03:06:094] Auto find usbnet_adapter = wwan0
[06-10_10:03:06:094] netcard driver = qmi_wwan, driver version = 22-Aug-2005
[06-10_10:03:06:095] Modem works in QMI mode
[06-10_10:03:06:126] /proc/1426/fd/7 -> /dev/cdc-wdm0
[06-10_10:03:06:127] /proc/1426/exe -> /usr/libexec/qmi-proxy
[06-10_10:03:08:133] cdc_wdm_fd = 7
[06-10_10:03:08:208] Get clientWDS = 17
[06-10_10:03:08:241] Get clientDMS = 2
[06-10_10:03:08:273] Get clientNAS = 2
[06-10_10:03:08:304] Get clientUIM = 2
[06-10_10:03:08:336] Get clientWDA = 1
[06-10_10:03:08:368] requestBaseBandVersion EG25GGBR07A08M2G
[06-10_10:03:08:496] requestGetSIMStatus SIMStatus: SIM_READY
[06-10_10:03:08:497] requestSetProfile[1] internet///0
[06-10_10:03:08:560] requestGetProfile[1] internet///0
[06-10_10:03:08:592] requestRegistrationState2 MCC: 466, MNC: 89, PS: Attached, DataCap: LTE
[06-10_10:03:08:624] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[06-10_10:03:08:625] ifconfig wwan0 down
[06-10_10:03:08:659] ifconfig wwan0 0.0.0.0
[06-10_10:03:08:720] requestSetupDataCall WdsConnectionIPv4Handle: 0x872db360
[06-10_10:03:08:848] ifconfig wwan0 up
[06-10_10:03:08:877] busybox udhcpc -f -n -q -t 5 -i wwan0
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending select for 10.150.64.12
udhcpc: lease of 10.150.64.12 obtained, lease time 7200
[06-10_10:03:54:060] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:03:54:061] requestQueryDataCall err = 110
[06-10_10:04:39:113] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:04:39:113] requestQueryDataCall err = 110
[06-10_10:05:24:192] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:05:24:193] requestGetIPAddress err = 110
[06-10_10:05:24:193] requestDeactivateDefaultPDP WdsConnectionIPv4Handle
[06-10_10:05:54:194] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:05:54:195] requestDeactivateDefaultPDP err = 110
[06-10_10:05:54:195] ifconfig wwan0 down
[06-10_10:05:54:232] ifconfig wwan0 0.0.0.0
[06-10_10:07:54:249] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:07:54:250] requestSetupDataCall err = 110
[06-10_10:07:54:250] try to requestSetupDataCall 5 second later
[06-10_10:08:24:251] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:08:24:252] requestRegistrationState2 err = 110
[06-10_10:08:54:253] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:08:54:253] requestQueryDataCall err = 110
[06-10_10:08:54:289] requestRegistrationState2 MCC: 466, MNC: 89, PS: Attached, DataCap: LTE
[06-10_10:09:24:290] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:09:24:291] requestQueryDataCall err = 110
[06-10_10:09:24:305] requestRegistrationState2 MCC: 466, MNC: 89, PS: Attached, DataCap: LTE
[06-10_10:09:24:336] requestSetupDataCall WdsConnectionIPv4Handle: 0x872db360
[06-10_10:09:54:337] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:09:54:338] requestGetIPAddress err = 110
[06-10_10:09:54:338] try to requestSetupDataCall 10 second later
[06-10_10:09:54:353] requestRegistrationState2 MCC: 466, MNC: 89, PS: Attached, DataCap: LTE
[06-10_10:10:24:354] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:10:24:355] requestQueryDataCall err = 110
[06-10_10:10:24:369] requestQueryDataCall IPv4ConnectionStatus: CONNECTED
[06-10_10:10:54:370] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:10:54:371] requestGetIPAddress err = 110
[06-10_10:10:54:371] requestDeactivateDefaultPDP WdsConnectionIPv4Handle
[06-10_10:10:54:448] requestSetupDataCall WdsConnectionIPv4Handle: 0x872db360
[06-10_10:11:24:513] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:11:24:514] requestQueryDataCall err = 110
[06-10_10:11:24:528] ifconfig wwan0 up
[06-10_10:11:24:552] busybox udhcpc -f -n -q -t 5 -i wwan0
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending select for 10.150.64.12
udhcpc: lease of 10.150.64.12 obtained, lease time 7200
[06-10_10:12:09:752] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:12:09:752] requestQueryDataCall err = 110
[06-10_10:12:54:793] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:12:54:793] requestQueryDataCall err = 110
[06-10_10:13:39:873] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:13:39:874] requestGetIPAddress err = 110
[06-10_10:13:39:874] requestDeactivateDefaultPDP WdsConnectionIPv4Handle
[06-10_10:13:39:888] ifconfig wwan0 down
[06-10_10:13:39:917] ifconfig wwan0 0.0.0.0
[06-10_10:15:39:935] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:15:39:936] requestSetupDataCall err = 110
[06-10_10:15:39:936] try to requestSetupDataCall 5 second later
[06-10_10:16:09:937] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:16:09:937] requestQueryDataCall err = 110
[06-10_10:18:09:938] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:18:09:939] requestSetupDataCall err = 110
[06-10_10:18:09:939] try to requestSetupDataCall 10 second later
[06-10_10:18:39:940] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:18:39:941] requestQueryDataCall err = 110
[06-10_10:19:09:942] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:19:09:943] requestQueryDataCall err = 110
[06-10_10:19:39:944] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:19:39:944] requestRegistrationState2 err = 110
[06-10_10:19:39:951] requestRegistrationState2 MCC: 466, MNC: 89, PS: Attached, DataCap: LTE
[06-10_10:20:09:953] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:20:09:953] requestQueryDataCall err = 110
[06-10_10:20:09:968] requestRegistrationState2 MCC: 466, MNC: 89, PS: Attached, DataCap: LTE
[06-10_10:22:09:969] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:22:09:970] requestSetupDataCall err = 110
[06-10_10:22:09:970] try to requestSetupDataCall 20 second later
[06-10_10:22:39:971] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[06-10_10:22:39:972] requestRegistrationState2 err = 110

Dear Qiao,
Thanks for your inquiry in Quectel forum.
About your issue, please double check whether the module already register on network successful. And confirm the PAN you used is correct or not. Thanks!

Hi Kyson,

Thanks for the reply. But how could I check whether the module is already registered on the network?
Following is the ifconfig -a result

root@imx6ul-var-dart:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether f8:dc:7a:39:d5:cb txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 103 bytes 18394 (17.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether f8:dc:7a:39:d5:ca txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 112 bytes 9920 (9.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 112 bytes 9920 (9.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.105 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 2001:b011:1003:3dc4:bf10:4bfb:a3bb:4db5 prefixlen 64 scopeid 0x0
inet6 fe80::9b66:b2c8:abd7:837a prefixlen 64 scopeid 0x20
ether 00:25:ca:17:96:4c txqueuelen 1000 (Ethernet)
RX packets 613 bytes 196425 (191.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 398 bytes 57497 (56.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wwan0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet6 fe80::c677:5417:e6c2:7686 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 2 bytes 612 (612.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15 bytes 1280 (1.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

As you can see the wwan0 is the network device I want to use for LTE connection.

And I think you meant PIN, not PAN, right? This sim card no need PIN to unlock, as you can see in the log

[06-10_10:03:08:496] requestGetSIMStatus SIMStatus: SIM_READY

which means the SIM is not locked.

Thanks.

You can send the following AT command via ttyUSB2 port. And you can check the AT command to find the following commands. Thanks!
ATI
AT+COPS?
AT+CSQ
AT+CEREG?
AT+QNWINFO

Hi Kyson,

Thanks for the instruction.
I followed the step and got the following response:


ATI
Quectel
EG25
Revision: EG25GGBR07A08M2G

OK
AT+COPS?
+COPS: 0,0,“T Star”,7

OK
AT+CSQ
+CSQ: 17,99

OK
AT+CEREG?
+CEREG: 2,1,“279F”,“1C5AE34”,7

OK
ATAT+CIND?
NO CARRIER

OK
AT+CIND?
+CIND: 0,3,1,0,0,0,1,0

OK
AT+CSQ
+CSQ: 17,99

AAT+CSQ
+CSQ: 17,99

OK
AT+QNINFO
+QNWINFO: “FDD LTE”,“46689”,“LTE BAND 7”,2850


But I’m not familiar with AT commands…, what’s the above responses mean?

Hi Qiao,
Thanks for your updating.From the log you provided, we can confirm the module already register on network successful. Thanks!
About your issue it is better to confirm whether the APN you used is correct, and confirm you have follow up the following user guide to modify the kernel code. Thanks!
Quectel_WCDMA_LTE_Linux_USB_Driver_User_Guide_V1.9-20190212.pdf (948.1 KB)

Hi Kyson,

Thanks for the reply. I already followed another document Quectel_LTE&5G_Linux_USB_Driver_User_Guide_V2.0.pdf to modify the driver, what’s the different between these 2 documents regarding the kernel driver modification?

Quectel_LTE&5G_Linux_USB_Driver_User_Guide_V2.0.pdf
The document you followed can support 5G module, and the document i have send to you cannot support 5G module. That is the difference. Thanks!

Thanks for the clarification. However, the product list in section 2 doesn’t contain my module EG25-G, is it still applicable?

Yes, you can use the same VID/PID as EC25 module. Thanks!
image

Unfortunately, I follow the document you provide, but the result doesn’t change.
Any idea? What should I try next?

If that, please email to support@quectel.com to get the debug log tool, it may need to catch module debug log to analyze the reason. Thanks!

Try to copy the default.script to the directory :slight_smile:
/usr/share/udhcpc/
/etc/udhcpc/
if the directory does not exist, create one.
uninstall the modemmanager if it exists.
Send email to support@quectel.com for the latest qmi driver, driver version 22-Aug-2005 seems too old.