quectel-CM not showing status CONNECTED

IoT Modules 5G Module
1

Dear Experts,

I’m having some trouble making a connection using quectel-CM after following the guide.

System details:

Module: RM502Q-AE
OS: Ubuntu 20.04

CM Logs:

root@ubuntu:/quectel-CM# ./quectel-CM
[03-02_13:52:37:463] Quectel_QConnectManager_Linux_V1.5
[03-02_13:52:37:463] Find /sys/bus/usb/devices/4-1 idVendor=0x2c7c idProduct=0x800
[03-02_13:52:37:463] Auto find qmichannel = /dev/cdc-wdm0
[03-02_13:52:37:463] Auto find usbnet_adapter = wwx02449bff8836
[03-02_13:52:37:464] Modem works in QMI mode
[03-02_13:52:37:477] cdc_wdm_fd = 7
[03-02_13:52:37:555] Get clientWDS = 15
[03-02_13:52:37:587] Get clientDMS = 5
[03-02_13:52:37:619] Get clientNAS = 4
[03-02_13:52:37:651] Get clientUIM = 1
[03-02_13:52:37:683] Get clientWDA = 1
[03-02_13:52:37:716] requestBaseBandVersion RM502QAEAAR11A03M4G
[03-02_13:52:37:844] requestGetSIMStatus SIMStatus: SIM_READY
[03-02_13:52:37:875] requestGetProfile[1] fast.t-mobile.com///0
[03-02_13:52:37:907] requestRegistrationState2 MCC: 310, MNC: 260, PS: Attached, DataCap: LTE
[03-02_13:52:37:939] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[03-02_13:52:37:939] ifconfig wwx02449bff8836 down
[03-02_13:52:37:946] ifconfig wwx02449bff8836 0.0.0.0
[03-02_13:52:38:196] requestSetupDataCall WdsConnectionIPv4Handle: 0x66560b30
[03-02_13:52:38:323] ifconfig wwx02449bff8836 up
[03-02_13:52:38:325] busybox udhcpc -f -n -q -t 5 -i wwx02449bff8836
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending select for 192.0.0.2
udhcpc: lease of 192.0.0.2 obtained, lease time 7200

Other:

#ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:0c:29:61:e7:49  txqueuelen 1000  (Ethernet)
        RX packets 1008  bytes 121531 (121.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 552  bytes 52623 (52.6 KB)
        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<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 35824  bytes 2986917 (2.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 35824  bytes 2986917 (2.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wwx02449bff8836: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1472
        inet6 fe80::6542:8fa6:3fae:e7a5  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 22  bytes 6644 (6.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 120  bytes 11920 (11.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I’m not seeing the final lines shown in the documentation:

[07-03_06:56:29:924] /etc/udhcpc/default.script: Resetting default routes
[07-03_06:56:29:936] /etc/udhcpc/default.script: Adding DNS 211.138.180.2

Also my device is named wwx02449bff8836 rather than wwan0 like the documentation.

I am on T-Mobile, and I have copied the pre-packaged default script to the proper location, and I am running as root. I’ve copied default.script from the driver package to: /usr/share/udhcpc/default.script

Any help is greatly appreciated!

Thanks

M

2

Dear Customer,
Thanks for your question, can you send a mail with some logs to us(support@quectel.com) .
By the way, in order to provide a better customer service ,can you fill in below details:

  • Company name:
  • Project name (so we can refer to it in the future):
  • Application type:
  • Estimated Annual Units (for series production):
  • Project timeline:
  • Current status:
  • From which distributor do you buy Quectel modules & EVB kits?
  • Do you have EVB kit for this application?
3

I have similar problem on TMO.
Try restricting LTE band to B66 and NR band to N41(if it is available). If not, we use use N71.
After hard-coding, I got the data connection working.