How to use RG520N QuecOpen QMAP API

This video shows how to use the QMAP API.

0:17~0:20: List QMAP General Configuration API
0:22~0:27: List QMAP LAN Configuration API
0:30~0:33: List QMAP WAN Configuration API
You can refer to Quectel_RG520N_Series_QuecOpen_QMAP_Interface_Usage_Reference_Manual_V1.0.0_Preliminary to check detail information about each QMAP API.

[0:35~1:45] How to use qmap_test command (QMAP API) in AP Linux to establish data call in router mode.
0:38~0:57: Check WWAN profile, PDN to VLAN mapping table, and VLAN ID 0 router mode.
1:00~1:09: Use wwan_handle 1 (APN 1) to dial data call.
1:12~1:29: Confirm wwan_profile 1 dial successfully and check related interfaces in AP Linux and ETH PC.
1:30~1:45: Check if PC can ping to the Internet in IP based and DNS based.

[1:46~3:08] How to use qmap_test command (QMAP API) in AP Linux to establish data call in IPPT (IP Passthrough) mode.
1:46~2:27: Set VLAN ID 0 to IPPT adaptive mode.
2:28~2:38: Use wwan_handle 1 (APN 1) to dial data call.
2:39~2:54: Confirm wwan_profile 1 dial successfully and check related interfaces in AP Linux and ETH PC.
2:55~3:08: Check if PC can ping to the Internet in IP based and DNS based.

[3:09~5:20] How to use qmap_test command (QMAP API) in AP Linux to establish data call in multiple PDN VLAN with with router mode.
3:09~3:43: Add VLAN (ID 2) interface with IPA offload. Module will reboot automatically to take effect for adding first VLAN.
3:44~3:59: Confirm VLAN added successfully and check VLAN ID 0 and VLAN ID 2 are in router mode.
4:00~4:25: Add new WWAN profile. Map wwan_handle with corresponding VLAN ID.
4:26~4:38: Use wwan_handle 1 (APN 1) and wwan_handle 2 (APN2) to dial data call.
4:39~5:07: Confirm VLAN and bridge interfaces are existed. check related interfaces in AP Linux and ETH PC.
5:08~5:20: Check if PC can ping to the Internet in IP based and DNS based.

[5:21~7:34] How to use qmap_test command (QMAP API) in AP Linux to establish data call in multiple PDN VLAN with IPPT (IP Passthrough) mode.
5:21~5:48: Add VLAN (ID 2) interface with IPA offload. Module will reboot automatically to take effect for adding first VLAN.
5:49~6:12: Confirm VLAN added successfully. Set VLAN ID 0 and VLAN ID 2 to IPPT adaptive mode.
6:13~6:29: Add new WWAN profile and Map wwan_handle with corresponding VLAN ID.
6:30~6:44: Use wwan_handle 1 (APN 1) and wwan_handle 2 (APN2) to dial data call.
6:45~6:54: Confirm VLAN and bridge interfaces are existed. check related interfaces in AP Linux and ETH PC.
6:55~7:07: Confirm public IP of wwan_handle 1 with APN 1 pass through to PC’s ethernet interface with VLAN ID 0.
7:08~7:19: Confirm public IP of wwan_handle 2 with APN 2 pass through to PC’s ethernet interface with VLAN ID 2.
7:20~7:34: Check if PC can ping to the Internet in IP based and DNS based.

1 Like

can you share how we can install this software? we’re using 520N on an openwrt router (connected via USB port), and we have to use gcom (with AT cmd) to manage the module settings, which is very tedious. your method looks very simple.

Hi Randy,

This QuecOpen solution module is made for host applications. If you have a host CPU connected 520N module USB interface, you must use the QMI WWAN connection network.

How can we get qmap_test added to my rm520n? qmap_test not found via adb shell.

Hi JT,

qmap_test is our QuecOpne function. The QuecOpen solution is usually implemented on an LGA module such as the RG520N due to the RM520N M.2 memory size limitations.