RG500Q-EA 5G EVB / quectel-CM 1.5 fails to obtain IP


After hours and hours, I decided to post this question so maybe it is a known bug or there is something missing in the documentation in order to make this module work properly in a Linux Ubuntu 20 setup, here it goes:

a) Using qmi_wwan_q and quectel-CM the host fails to obtain IP via DHCP
b) Using qmi_wwan (stock version) and quectel-CM host is able to obtain ip via DHCP BUT performs poorly in terms of throughput (it does never reach beyond 200 mbps , while other test device (phone) gets 450 mbps with the exact same radio conditions)

A priori diagnosis:
-Modem itself gets connected with no problem, obtains IP and everything as reported via AT+CGPADDRR;

-Sometimes when Quectel-CM forces Raw IP mode on the qmi interface and then reinitiates dhcp requests on it, it gets IP… sometimes.

I did SEVERAL tests , I restarted the module , the board , the host , everything… but nothing did work… please help!

OS: Ubuntu 20
Module Platform: 5G EVB via USB-C cable to Host (Linux)
Drivers: quectel_cm 1.5 , qmi_wwan_q 1.2 (as far as I remember)
RF/Operator : Lab conditions in RF BOX , excellent radio conditions with NSA B1+N78 MIMO 2x2, phones do get around 450 to 510 Mbps

Module info:
Revision: RG500QEAAAR10A03M4G

+QSPN: “ViMMOR”,“ViMMOR”,"",0,“00101”

+CGDCONT: 1,“IP”,“default”,“”,0,0,0,0,"",0
+CGDCONT: 2,“IPV4V6”,“ims”,“”,0,at
+CGPADDR: 1,“”
+CGPADDR: 2,""
+CGPADDR: 3,""

qmi_wwan_q log
[ 2957.622486] qmi_wwan_q 2-1:1.4: cdc-wdm0: USB WDM device
[ 2957.622758] qmi_wwan_q 2-1:1.4: Quectel RG500Q-EA work on RawIP mode
[ 2957.622916] qmi_wwan_q 2-1:1.4: rx_urb_size = 31744
[ 2957.628066] qmi_wwan_q 2-1:1.4 rmnet_usb0: register ‘qmi_wwan_q’ at usb-0000:00:15.0-1, RMNET/USB device, 2a:9a:02:30:a0:4a
[ 2957.630177] usbcore: registered new interface driver qmi_wwan_q
[ 2957.637862] qmi_wwan_q 2-1:1.4 enx2a9a0230a04a: renamed from rmnet_usb0

quectel-CM LOG
[04-15_02:27:22:377] Quectel_QConnectManager_Linux_V1.5
[04-15_02:27:22:378] Find /sys/bus/usb/devices/2-1 idVendor=0x2c7c idProduct=0x800
[04-15_02:27:22:379] Auto find qmichannel = /dev/cdc-wdm0
[04-15_02:27:22:379] Auto find usbnet_adapter = enx2a9a0230a04a
[04-15_02:27:22:379] qmap_mode = 1, muxid = 0x81, qmap_netcard = enx2a9a0230a04a
[04-15_02:27:22:379] Modem works in QMI mode
[04-15_02:27:22:380] qmap_mode = 1, muxid = 0x81, qmap_netcard = enx2a9a0230a04a
[04-15_02:27:22:402] cdc_wdm_fd = 7
[04-15_02:27:23:402] QmiThreadSendQMITimeout pthread_cond_timeout_np timeout
[04-15_02:27:24:753] Get clientWDS = 15
[04-15_02:27:24:785] Get clientDMS = 1
[04-15_02:27:24:817] Get clientNAS = 4
[04-15_02:27:24:849] Get clientUIM = 1
[04-15_02:27:24:881] Get clientWDA = 1
[04-15_02:27:24:913] requestBaseBandVersion RG500QEAAAR10A03M4G
[04-15_02:27:24:945] qmap_settings.rx_urb_size = 16384
[04-15_02:27:25:073] requestGetSIMStatus SIMStatus: SIM_READY
[04-15_02:27:25:073] requestSetProfile[1] default///0
[04-15_02:27:25:136] requestGetProfile[1] default///0
[04-15_02:27:25:169] requestRegistrationState2 MCC: 1, MNC: 1, PS: Attached, DataCap: LTE
[04-15_02:27:25:201] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[04-15_02:27:25:201] ifconfig enx2a9a0230a04a down
[04-15_02:27:25:208] ifconfig enx2a9a0230a04a
[04-15_02:27:25:233] requestSetupDataCall WdsConnectionIPv4Handle: 0x4923d800
[04-15_02:27:25:362] ifconfig enx2a9a0230a04a up
[04-15_02:27:25:368] busybox udhcpc -f -n -q -t 5 -i enx2a9a0230a04a
udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: no lease, failing


pd: company QIN Technology - Chile

Dear Raul,
Did you do the test in Chile? RG500Q-EA is for EMEA/APAC market, if it is used in Chile, we recommend choose RM50XQ-AE , which can be used around the world.Thanks!

Hello Peter,

Thanks for the info, next time we will buy that, but in the meantime we only have the rg500q-ea.

I am using a private lte-NR deployment so bands are not a problem, but module’s driver yes.

Do you have any work around to the issue? Is there any benefit from using the qmi_wwan_q module instead of qmi_wwan?


Hi Raul,

Don’t know if it’s the same issue here, but quectel-CM seems to be only a quick testing tool.
To use it, I’d to rework it a lot because when dhcp fail (like in your trace), there is no other try until… I don’t know what…???
For example, if you disconnect antennas (lost signal) and connect them again, it didn’t work for me.
Don’t know if any evolution will be provided by Quectel or if quectel-CM will be kept as a testing tool…