Qconnect Manager?

I’m currently testing on a Raspberry Pi 5 and looking for QConnectManager. (kernel 6.12.47)

I found a Git repo that has version 1.6.7—Is this repository official?

Previously, with version 1.6.5, I connected using quectel-CM as a QMI device and it worked,
but it doesn’t work on 1.6.7.
Could you help with this?

Please try the 1.6.8.
q_drivers/Quectel_QConnectManager_Linux_V1.6.8 at master · QuectelWB/q_drivers

1 Like

Thanks for your reply.

Currently, I am testing with quectel-CM 1.6.8 and the RM520N module.

I want to test a 5G connection, and when I run the following AT command:
AT+QENG=“servingcell”

+QENG: “servingcell”,“LIMSRV”,“NR5G-SA”,“TDD”,450,08,060F84010,980,A0205C,636672,78,12,-65,-11,24,1,29

And then run quectel-CM, I get the following output:
[11-20_11:11:01:384] QConnectManager_Linux_V1.6.8
[11-20_11:11:01:384] Find /sys/bus/usb/devices/5-1 idVendor=0x2c7c idProduct=0x801, bus=0x005, dev=0x002
[11-20_11:11:01:384] network interface ‘’ or qmidev ‘’ is not exist
[11-20_11:11:01:385] netcard driver = pcie_mhi, driver version = V1.3.8
[11-20_11:11:01:385] qmap_mode = 1, qmap_version = 9, qmap_size = 15360, muxid = 0x81, qmap_netcard = rmnet_mhi0.1
[11-20_11:11:01:385] Modem works in QMI mode
[11-20_11:11:01:422] cdc_wdm_fd = 7
[11-20_11:11:01:492] Get clientWDS = 14
[11-20_11:11:01:494] Get clientDMS = 1
[11-20_11:11:01:498] Get clientNAS = 3
[11-20_11:11:01:501] Get clientUIM = 2
[11-20_11:11:01:504] Get clientWDA = 1
[11-20_11:11:01:507] requestBaseBandVersion RM520NGLAAR03A02M4G_KR
[11-20_11:11:01:510] qmap_settings.rx_urb_size = 15360
[11-20_11:11:01:510] qmap_settings.ul_data_aggregation_max_datagrams = 11
[11-20_11:11:01:510] qmap_settings.ul_data_aggregation_max_size = 8192
[11-20_11:11:01:510] qmap_settings.dl_minimum_padding = 0
[11-20_11:11:01:522] requestGetSIMStatus SIMStatus: SIM_READY
[11-20_11:11:01:527] requestGetProfile[pdp:1 index:1] lte.ktfwing.com///0/IPV4
[11-20_11:11:01:530] requestRegistrationState2 MCC: 450, MNC: 8, PS: Attached, DataCap: UNKNOW
[11-20_11:11:01:532] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[11-20_11:11:01:532] ip link set dev rmnet_mhi0 down
[11-20_11:11:01:539] ip addr flush dev rmnet_mhi0.1
[11-20_11:11:01:541] ip link set dev rmnet_mhi0.1 down
[11-20_11:11:01:550] requestSetupDataCall QMUXResult = 0x1, QMUXError = 0xe
[11-20_11:11:01:550] call_end_reason is 3
[11-20_11:11:01:550] call_end_reason_type is 3
[11-20_11:11:01:550] call_end_reason_verbose is 2001
[11-20_11:11:01:550] try to requestSetupDataCall 5 second later

I am wondering if quectel-CM cannot connect to 5G (SA)

It means that it is not registerred.
It is better to use the AT command checking first.

1 Like

I tested

at+qnwprefcfg=“nr5g_band”
+QNWPREFCFG: “nr5g_band”,78:79

at+qeng=“servingcell”
+QENG: “servingcell”,“LIMSRV”,“NR5G-SA”,“TDD”,450,08,060F84010,980,A0205C,636672,78,12,-65,-11,23,1,29

at+creg=1
OK

at+creg?
+CREG: 1,0

at+cgact=1,1
+CME ERROR: 30

For the command AT+CGACT=1,1, I’m getting +CME ERROR: 30.
Is this error caused by something I missed in the AT configuration commands,
or is it occurring because the device is not registered on the network?

DataCap: UNKNOW
means it is not registtered.

at+qeng=“servingcell”
+QENG: “servingcell”,“LIMSRV”,“NR5G-SA”,“TDD”,450,08,060F84010,980,A0205C,636672,78,12,-65,-11,23,1,29

has the same meaning.

So it cannot actiave the PDP context.

1 Like