TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register

SIMCom SIM8202E-M.2 5G

Article Number: 11367
Brand: SIMCom
Supplier number:

The SIM8202E-M2 is a Multi-Band 5G NR/LTE-FDD/LTETDD/HSPA+ module which supports R15 5G NSA/SA up to 2.4Gbps data transfer.
It has strong extension capability with abundant interfaces including PCIe, USB3.1, GPIO etc. The module provides much flexibility and ease of integration forcustomer's applications.

The SIM8202E-M2 adopts M.2 form factor, TYPE 3042-S3-B. AT commands of SIM8202E-M2 are compatible with SIM7912G/SIM8200X-M2 series modules. This also minimizes the investments of customers and enables a short time-to-market.
It is designed for applications that need high throughput data communication in a variety of radio propagation conditions. Due to the unique combination of performance, security and flexibility, this module is ideally suited for many applications.

End-of-life

This product has reached
end-of-life and can not be
ordered any more.

Quantity Price

No prices available

For more information
please contact us at
sales-americas@techship.com

For larger quantities and complete pricing, please sign in or register

Do you need offline data on this product?

Download datasheet

Subscribe to stay up to date with the latest about this product.

Subscribe to updates
Region
Europe
Technology
5G
Form Factor
M.2 3042
5G Sub6 Bands
n1 (FDD 2100)
n3 (FDD 1800)
n5 (FDD 850)
n7 (FDD 2600)
n8 (FDD 900)
n12 (FDD 700)
n20 (FDD 800)
n28 (FDD 700)
n38 (TDD 2600)
n40 (TDD 2300)
n41 (TDD 2500)
n48 (TDD 3600)
n71 (FDD 600)
n77 (TDD 3700)
n78 (TDD 3500)
n79 (TDD 4500)
LTE Bands
B1 (FDD 2100)
B3 (FDD 1800)
B5 (FDD 850)
B7 (FDD 2600)
B8 (FDD 900)
B12 (FDD 700ac)
B13 (FDD 700c)
B14 (FDD 700PS)
B17 (FDD 700bc)
B18 (FDD 800)
B20 (FDD 800DD)
B26 (FDD 850)
B28 (FDD 700)
B29 (SDL 700)
B34 (TDD 2000)
B38 (TDD 2600)
B39 (TDD 1900)
B40 (TDD 2300)
B41 (TDD 2500)
B42 (TDD 3500)
B43 (TDD 3600)
B48 (TDD 3600)
B71 (FDD 600)
UMTS Bands
B1 (2100)
B8 (900)
B3 (1800)
B5 (850)
Max DL Speed
2400 Mbps
Max UL Speed
500 Mbps
GNSS
Yes
GNSS technology
QZSS
GPS
GLONASS
Galileo
BeiDou
Antenna Connectors
IPEX MHF-4
Certification
RoHS
REACH
CE RED
Carrier Certification
Deutsche Telekom
Anatel
Operating Temperature Range
-30 °C – 70 °C
Chipset
Qualcomm
SDX55
Data Interface
PCIe
Serial / UART
GPIO
PCM
USB 3.1
USB 2.0
I2C
Driver Support
Windows 7
Linux
Android
Windows 8
Windows 10
Size
42 x 30 x 2.3 mm
Datasheet for SimCom SIM8202E-M2 5G sub-6 module.

Download

Uploaded at
2021-05-21 11:33:48
Last updated
2021-05-26 09:35:32
Version
20210525
Related products
SIMCom SIM8202E-M.2 5G
Hardware Design Guide for SimCom SIM8202E-M2 5G module.

Download

Uploaded at
2021-05-21 11:38:05
Last updated
2022-03-28 08:11:55
Version
1.02
Related products
SIMCom SIM8202E-M.2 5G
This file describes the pin definitions of the SIM8202E-M2.

Download

Uploaded at
2021-10-21 13:34:39
Last updated
2021-10-21 13:34:39
Version
V1.00
Requirements

Related products
SIMCom SIM8202E-M.2 5G

This guide describes the SIM82xx & SIM83xx Series cellular modules AT control commands available and supported

Download

The SIM8200 Series Linux USB User Guide.

Download

Uploaded at
2021-07-09 14:02:55
Last updated
2021-07-09 14:02:55
Version
1.00
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8200-M2-EVB2-KIT
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8202E-M.2 5G
SIMCom SIM8202G-M.2 5G
This application notes archive contains the following application notes:
FOTA v1.00
FTP(S) v1.00
HTTP(S) v1.00
Linux USB User Guide v1.00
MQTT(S) 1.00
Open Linux Sleep&Wakeup v1.00
SSL v1.00
TCPIP v1.00
TTS v1.00

Download

Uploaded at
2021-07-09 14:01:05
Last updated
2021-07-12 10:40:13
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8200-M2-EVB2-KIT
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8202E-M.2 5G
SIMCom SIM8202G-M.2 5G
Antenna port mapping and design guide for SimCom SIM8202E-M2 5G module.

Download

Uploaded at
2021-07-02 14:38:59
Last updated
2021-07-02 14:38:59
Version
V 1.01
Related products
SIMCom SIM8202E-M.2 5G
Simcom SIM820x / SIM830x Series 5G Module Windows USB Drivers V1.01

Download

Uploaded at
2021-02-26 17:19:30
Last updated
2021-02-26 17:19:30
Version
V1.01
Requirements
Microsoft Windows 10 Desktop systems
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8202G-M.2 5G
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8300G-M.2 5G mmWave
SIMCom SIM8202E-M.2 5G
Archive containing the Simcom SIM820x and SIM830x series Linux driver integration files, connection manager and guide

Download

Uploaded at
2021-02-26 17:09:54
Last updated
2021-02-26 17:09:54
Version
1
Related products
SIMCOM SIM8200EA-M.2 5G
SIMCom SIM8202G-M.2 5G
SIMCom SIM8200G 5G Sub-6 LGA
SIMCom SIM8300G-M.2 5G mmWave
SIMCom SIM8202E-M.2 5G
Question

Which antenna ports should I connect antennas to on the LTE or 5G module?

Solution

It is important to understand the functionality of the different antenna ports on the cellular module when deciding which ports to use. There is a risk of underutilizing the module by not connecting antennas to the right ports. This guide aims to explain some general terms and abbreviations used to label and describe antenna ports and their different functionalities.

Some antenna port labels that are commonly used on cellular modules are listed below:

  • MAIN – Primary transmit and receive antenna port. Required for basic functionality.

  • DIV – Diversity receive port. This port is used to receive the same signal as the primary port, but at a different spatial point. By receiving the same signal at two different spatial points, the module can mitigate destructive effects that might be present on one of the different spatial points. The diversity receive functionality is especially useful in urban environments where the interference environments may be radically different between two spatial points. It is always recommended to use the diversity receive port as this functionality improves the quality and reliability of the overall link.

  • GNSS – GNSS receive port. GNSS stands for Global Navigation Satellite System, examples of such systems are GPS, Galileo, GLONASS and BeiDou. The available systems may differ between different modules. To see what systems are available for a specific module, please consult the modules hardware documentation. As this antenna port is used for positioning applications, a suitable GNSS antenna needs to be connected to this port in order to utilize this functionality.

  • MIMO – MIMO port. MIMO stands for Multiple Input Multiple Output and refers to the amount of antennas used at each side of the link. For example, 4x4 DL MIMO means that the base station and the module each use 4 antennas for the modules downlink. Usually, the MIMO label is used to denote antenna ports that are used for spatial multiplexing which is a technique used for increasing the bitrate. This is achieved by splitting the signal into different streams that are transmitted and received on spatially separated antennas on each side of the link. For the majority of cellular modules, spatial multiplexing is only available for the module's downlink.

  • AUX – Auxiliary antenna port. The available functions on this port may differ between modules. Examples of functionalities that can be present on this port are diversity receive, DL-MIMO and GNSS. Please consult the module's hardware documentation to see which functionalities are present on this port.

Some cellular modules have numeric, non-descriptive labels on their antenna ports. These modules can have different functionalities for different frequency intervals/bands, on one single antenna port. For these modules, consult the hardware documentation to find what functionalities are present for which frequency intervals/bands one the different antenna ports. Please note that antenna ports with transmit functionality for certain frequency bands need to have a antenna connected in order to utilize these frequency bands.

If you have further inquiries regarding antenna ports on cellular modules, please create a Support Ticket by visiting the following link: https://techship.com/support/new/

Question

How to collect initial diagnostics data for Simcom 5G cellular modules when creating a Techship technical support ticket?

Solution

In order to troubleshoot and solve a technical problem, we ask you to please provide information about your host system and logs from the related Simcom 5G module when creating a technical support ticket.

This allows us to get a better understanding of what could relate to the experienced behaviour.

Please provide a detailed problem description and in what situations the problem is present or how it can be reproduced. Please also attach pictures showing the module assembled in your host device with RF interface cables connected between cellular module and the casing and provide datasheets for the antennas used if the problem appears to be a RF related problem such as no network registrations seen, or data throughputs not meeting your expectations etc.

Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux release, kernel version...)
-Drivers and driver versions

Identify the precise details of cellular module found on label (if not visible in attached picture)
-Model
-SKU / BOM or P/N code
-Serial / IMEI number

If your system is Linux based, please capture the terminal logs bellow:
uname -a
lsusb
lsusb -t
usb-devices
ifconfig -a
ls -l /dev/serial/by-id
ls -l /sys/bus/usb-serial/devices
dmesg

The log outputs from AT commands below can be collected from the cellular module by accessing the USB enumerated serial interfaces that accept AT commands. These are typically found as Modem or Serial type of interfaces in Window device manager, check their related COM port numbers from device manager and use a terminal software like Teraterm, Sscom or similar to send the AT commands to the cellular module. typically the default 115200 bitrate and 8N1 parity settings works well for collecting these details.

In Linux systems the USB serial ports are typically found in path /dev/ and named ttyUSB0, ttyUSB1, ttyUSB2, not all serial ports accept AT commands so you might have to check which of them are the correct one. Please note that if you have Modemmanager process running in your system, it likely already communicate on the USB serial interfaces so you should stop the Modemmanager service prior to attempting to collect the diagnostic logs. Minicom or other terminal software can be used to send the AT commands to the cellular module.

Start by sending an plain AT command followed by enter key to confirm that you get a OK reply and knowing that the AT communication is working.

Now start sending the following AT commands to the module and capture the output into a log text file and include them when creating the technical support ticket at Techship.com. If possible, provide the logs with a SIM card inserted and PIN unlocked, to allow the module to be in normal operational mode and registered in network.

Test that you have a working AT interface opened:
AT

Enabled AT command echo:
ATE1

Basic module info:
ATI

Display V.25TER configurations
AT&V

Detailed module version info:
AT+SIMCOMATI

Verbose error reporting:
AT+CMEE=2

Firmware version:
AT+CGMR

Additional details:
AT+CSUB

Serial number / IMEI:
AT+CGSN

USB endpoint configuration:
AT+CUSBCFG?

PCIe interface configuration:
AT+CPCIEMODE?

SIM card interface, SIM card detect signal and active SIM slot:
AT+UIMHOTSWAPON?
AT+UIMHOTSWAPLEVEL?
AT+SMSIMCFG?

Operational mode:
AT+CFUN?

Pin status:
AT+CPIN?

Active technologies, RF bands, and scan orders:
AT+CNMP?
AT+CSYSSEL=?
AT+CSYSSEL="nr5g_disable"
AT+CSYSSEL="nr5g_band"
AT+CSYSSEL="nsa_nr5g_band"
AT+CSYSSEL="lte_band"
AT+CSYSSEL="w_band"
AT+CSYSSEL="rat_acq_order"

Request UE network system info:
AT+CPSI?
AT+CNSMOD?
AT+CNWINFO?

List network operator info:
AT+COPS?

Network registration status:
AT+CREG=2
AT+CREG?

Network GPRS registration status:
AT+CGREG=2
AT+CGREG?

Network (4G/LTE) EPS registration status:
AT+CEREG=2
AT+CEREG?

Network 5G SA
AT+C5GREG=2
AT+C5GREG?

Signal strength:
AT+CSQ

List APN details/PDP profiles:
AT+CGDCONT?
AT+CGAUTH?

Packet domain attach status:
AT+CGATT?

PDP profiles attach status:
AT+CGACT?

Show PDP IP address:
AT+CGPADDR
AT+CGCONTRDP

Device temperature:
AT+CPMUTEMP
AT+CCPUTEMP=2

Supply voltage:
AT+CBC

The support ticket can be created after login at Techship.com: https://techship.com/technical_support/

Question

How to collect initial diagnostics data and logs for Simcom cellular modules, needed when requesting Techship technical support?

Solution

In order to troubleshoot and solve a technical problem, we ask you to please provide information about your host system and logs from the related Simcom module when creating a technical support ticket.

Detailed problem description and in what situations it present or can be reproduced.

Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux release, kernel...)
-Drivers and driver versions

Identify the precise details of cellular module found on label:
-Model
-SKU/BOM or P/N code
(For RMA returns the IMEI number is mandatory)

If you are running on a Linux based system, please capture the terminal logs bellow:
uname -a
lsusb
lsusb -t
ifconfig -a
ls -l /dev/serial/by-id
ls -l /sys/bus/usb-serial/devices
dmesg

The logs from the cellular module firmware can be acquired by accessing the USB enumerated serial (COM) interfaces accepting AT commands. They can be named modem, AT, PC UI etc. (In Windows device manager, found under modem or serial interfaces). Send the following AT commands bellow to module and capture the output and include them when creating the the technical support ticket.

Test that you get a reply with command:
AT
Command echo enabled:
ATE1
Basic module info:
ATI
Detailed module version info:
AT+SIMCOMATI
Verbose error reporting:
AT+CMEE=2
Last error report:
AT+CEER
Firmware version:
AT+CGMR
AT+CSUB
IMEI Code:
AT+CGSN
USB endpoint configuration:
AT+CUSBPIDSWITCH?
List current configuration:
AT&V
Operational mode:
AT+CFUN?
Pin status:
AT+CPIN?
Request UE system info:
AT+CPSI?
Preferred network mode:
AT+CNMP?
Preferred band selection:
AT+CNBP?
Preferred acquisition order:
AT+CNAOP?
List network operator info:
AT+COPS?
Network registration status:
AT+CREG?
Network EPS registration status:
AT+CEREG?
Signal strength:
AT+CSQ
Packet domain attach status
AT+CGATT?
List APN details/PDP profiles:
AT+CGDCONT?
AT$QCPDPP?
PDP profiles attach status:
AT+CGACT?
Show PDP IP address:
AT+CGPADDR
AT+CGCONTRDP
RM network interface status:
AT$QCRMCALL?

The support ticket can be created after login at: https://techship.com/technical_support/

Question

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using QMI Rmnet over USB interface

Solution

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using QMI Rmnet over USB interface

5G technology introduces new requirements on the interface links between the host systems and cellular modules.
The Linux community continuously commit necessary changes to the kernel drivers and interface management tools to improve the compatibility and performance.
Because of this, it is important that you base your Linux system builds on up-to-date kernel versions, avoiding many problems already solved.

Ensure that you have up-to-date firmware version in the cellular module. Check the dedicated product page here at Techship and the firmware downloads tab or open a technical support ticket.

Early devices and engineering samples came with a older baseline firmware version and need to be update in Windows systems.

This guide specifically only describes how to establish the QMUX data connection part of the QMI rmnet USB interface for the SIM8202x-M2 series modules.
The qmi_wwan kernel driver module and libqmi library is used.

Ensure that you have the module in QMI Rmnet usb mode and qmi_wwan network kernel driver and option usb-serial driver properly loaded to the module interfaces.
Can be checked e.g. through dmesg, usb-devices or lsusb -t commands.

usb-devices
T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
D: Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 1
P: Vendor=1e0e ProdID=9001 Rev=04.14
S: Manufacturer=QCOM
S: Product=SDXPRAIRIE-MTP _SN:
S: SerialNumber=
C: #Ifs= 7 Cfg#= 1 Atr=a0 MxPwr=896mA
I: If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=techship_serial
I: If#=0x1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=60 Driver=techship_serial
I: If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=50 Driver=qmi_wwan
I: If#=0x6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=usbfs

If the qmi_wwan and option drivers do not get correctly loaded in your current system build and kernel version, please refer to the manufacturer Linux integration guide.

Alternatively you can try compile our modified out-of-kernel driver module variants: techship_qmi_wwan and techship_serial and load them in your system.
See the git readme files for details on pre-requirements, how to clone, compile and use the make file options to install the drivers.

They are available in the following git repository: https://bitbucket.org/storjor/techship_linux_drivers/

Once you have drivers correctly loaded, start by disabling the related qmi_wwan network interface name:
ip link set dev wwan0 down

Ensure RAW IP configuration is enabled:
sh -c "echo 'Y' > /sys/class/net/wwan0/qmi/raw_ip"
(observe the path name including the network interface name, update to match the interface name used in your system)

Create a virtual mux interface for the qmi network interface:
sh -c "echo '1' > /sys/class/net/wwan0/qmi/add_mux"
(observe the path name including the network interface name, update to match the interface name used in your system)

Configure the data format on module side:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wda-set-data-format=link-layer-protocol=raw-ip,ul-protocol=qmap,dl-protocol=qmap,dl-max-datagrams=32,dl-datagram-max-size=31744,ep-type=hsusb,ep-iface-number=5

Here in-between you should perform necessary operations to the module prior to having the cellular network data connection established.
Things like SIM state and PIN code entry, module device registration in the cellular network, APN profile management etc.

Refer to the qmicli manual pages for details on the control commands that can be supported by the libqmi library and qmicli command line interface. Note however that not all qmi commands are supported by all cellular module vendors and might be dependant on chipset families, firmware versions and additional vendor specific command etc.
https://www.freedesktop.org/wiki/Software/libqmi/

Once module is ready and registered in cellular network we can proceed to configure and set up the data connection.

Bind the virtual mux network interface we created earlier to the client ID (CID) that gets opened, the CID id is given back in the reply:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-bind-mux-data-port=mux-id=1,ep-iface-number=5 --client-no-release-cid

It is important to use the --client-no-release-cid attribute here to keep the tunnel open at all time while the data connection is established.
If the client id CID linked to the network connection is closed, then the data connection on the qmux virtual network interface will also be closed.

Start the cellular network data connection in the normal way now, include the --client-no-release-cid attribute and use the already open CID ID you got back from previous command reply. E.g. like this:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-start-network=apn=data.tre.se,ip-type=4 --client-no-release-cid --client-cid=##
Store the packet data handle id from the command reply, to re-use when stopping the network data connection.

Request the cellular data connection IP details from the module and network with command:
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-get-current-settings --client-no-release-cid --client-cid=##

Bring up the main QMI RMNET network interface:
ip link set dev wwan0 up

Apply the IP address to the qmux interface that you acquired through qmicli --wds-get-current-settings above, e.g.:
ip addr add 2.64.116.145 dev qmimux0

Apply the given MTU size to the qmux interface that you acquired through qmicli --wds-get-current-settings above, e.g.:
ip link set mtu 1500 dev qmimux0

Bring up the QMUX virtual network interface:
ip link set dev qmimux0 up

You should now have a working cellular network data connection.

Test it e.g. by sending a ping over the qmux interface:
ping -I qmimux0 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) from 2.68.152.91 qmimux0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=31.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=29.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=36.7 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=36.0 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 29.821/33.494/36.690/2.911 ms

Apply appropriate network interface routing suitable for your use-case, e.g:
ip route add default dev qmimux0

the qmicli --wds-get-current-settings give back DNS server addresses also if they are defined by the cellular network.
Depending on how your Linux distribution handle DNS servers you can add them or instead use a public DNS server.

To stop the cellular data network connection:
Bring down the virtual mux interface:
ip link set qmimux0 down

Flush the ip addresses:
ip -4 -6 address flush dev qmimux0

Use the --wds-stop-network attribute to stop the data connection in module, include the packet data handle and the client ID from when establishing the connection.
qmicli -p -d /dev/cdc-wdm0 --device-open-qmi --wds-stop-network=########## --client-cid=##
Note: by not adding the --client-no-release-cid attribute this client ID will be closed after command execution.

It is up to the host application to manage and poll the connection state of the cellular module.
E.g. it the connection is lost temporarily due to no network coverage in the current location, the host application should tear down and re-establish the data connection when cellular module is registered in network again.

If the data connection fails for some reason several times, ensure that the connect retry attempts do not take place continuously without some extended delays in-between. Depending on the cellular network operator, they can enforce lock-out on your subscription/device for certain time periods in order to protect the network.

Question

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using MBIM network interface over USB

Solution

Example on how to establish a data connection with Simcom SIM8202x-M2 series in Linux using MBIM network interface over USB

5G technology introduces new requirements on the interface links between the host systems and cellular modules.
The Linux community continuously commit necessary changes to the kernel drivers and interface management tools to improve the compatibility and performance.
Because of this, it is important that you base your Linux system builds on up-to-date kernel versions, avoiding many problems already solved.

Ensure that you have up-to-date firmware version in the cellular module. Check the dedicated product page here at Techship and the firmware downloads tab or open a technical support ticket.

Early devices and engineering samples came with a older baseline firmware version and typically need to be updated in a Windows system.

This guide describes how to establish a MBIM data connection in Linux using libmbim library and mbimcli command line interface for SIM8202x-M2 series modules when connected over USB to the host system.
The cdc_mbim kernel driver module and libmbim library is used.

Ensure that you have the Simcom module in MBIM usb mode and cdc_mbim network kernel driver and option usb-serial driver properly loaded to the module interfaces.
It can be checked e.g. through dmesg, usb-devices or lsusb -t commands.

usb-devices
T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 3 Spd=5000 MxCh= 0
D: Ver= 3.20 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs= 1
P: Vendor=1e0e ProdID=901e Rev=04.14
S: Manufacturer=QCOM
S: Product=SDXPRAIRIE-MTP _SN:
S: SerialNumber=
C: #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=896mA
I: If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=techship_serial
I: If#=0x1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=techship_serial
I: If#=0x2 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I: If#=0x3 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
I: If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=60 Driver=techship_serial
I: If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=usbfs

If the option serial drivers are not correctly loaded in your current system build and kernel version, you can try compile our modified option kernel driver module techship_serial from git link below and load them into your system build.
See the git readme files for details on pre-requirements, how to clone, compile and use the make file options to install the drivers.

They are available in the following git repository: https://bitbucket.org/storjor/techship_linux_drivers/

Refer to the mbimcli manual pages for details on the control commands that can be supported by the libmbim library and mbimcli command line interface. Note however that not all mbim commands are supported by all cellular module vendors and might be dependant on chipset families, firmware versions and additional vendor specific command etc.
https://www.freedesktop.org/wiki/Software/libmbim/

Example of how to set up a cellular data connection:
Note! A working MBIM network interface data connection requires that the MBIM control message tunnel is kept open at all time also.
To keep it open, start a new session with a mbimcli command, and keep the session open after the command execution by the --no-close attribute.
The Session ID / Transaction ID number (TRID) that is opened with the mbimcli command will be given back in the reply, save it for use in the next mbimcli command.
If the session ID linked to the network data connection is closed, then the data connection on the network interface will also be closed.

Check cellular RF radio status:
mbimcli -p -d /dev/cdc-wdm0 --query-radio-state --no-close
If not enabled, set it active:
mbimcli -p -d /dev/cdc-wdm0 --set-radio-state=on --no-close --no-open=##

Check SIM card subscriber state:
mbimcli -p -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --no-open=##
If pin is needed, enter it using --enter-pin command:
mbimcli -p -d /dev/cdc-wdm0 --enter-pin=#### --no-close --no-open=##

Check cellular network registration state:
mbimcli -p -d /dev/cdc-wdm0 --query-registration-state --no-close --no-open=##

If not registered already, try using register automatic:
mbimcli -p -d /dev/cdc-wdm0 --register-automatic --no-close --no-open=##

Check the packet data service state:
mbimcli -p -d /dev/cdc-wdm0 --query-packet-service-state --no-close --no-open=##

If packet service state is not attached, use attach command:
mbimcli -p -d /dev/cdc-wdm0 --attach-packet-service --no-close --no-open=##

To to start a data connection use the connect command, with the desired parameters for PDP APN, IP type, auth details, etc.
mbimcli -p -d /dev/cdc-wdm0 --connect=apn='data.tre.se',ip-type='ipv4v6' --no-close --no-open=##

Bring down the MBIM network interface:
ip link set dev wwan0 down

Clear any existing IP address and routes:
ip -4 -6 address flush dev wwan0
ip -4 -6 route flush dev wwan0

The mbimcli connect command returns the IP, gateway, DNS, and MTU details for the data connection if established successfully.
Enter the IPv4 details to the network interface in the Linux host system, e.g.:
ip address add 2.70.103.209/30 dev wwan0
ip link set mtu 1500 dev wwan0

Enter the IPv6 details to the network interface in the Linux host system, e.g.:
ip -6 addr add 2a02:aa1:1021:b9d1:4fb:e1c9:589c:d53f/64 dev wwan0
ip -6 link set mtu 1500 dev wwan0

Enable the network interface:
ip link set dev wwan0 up

Apply appropriate network interface routing suitable for your use-case, e.g:
ip route add default dev
ip -6 route add default dev wwan0

You should now have a working cellular network data connection.

Test it e.g. by sending ping requests over the interface:
ping -I wwan0 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) from 2.70.103.209 wwan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=224 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=42.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=30.7 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=38.4 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 30.657/84.031/224.373/81.140 ms

ping -6 -I wwan0 2600:: -c 4
PING 2600::(2600::) from 2a02:aa1:1021:b9d1:8847:afd4:e35a:aa29 wwan0: 56 data bytes
64 bytes from 2600::: icmp_seq=1 ttl=52 time=173 ms
64 bytes from 2600::: icmp_seq=2 ttl=52 time=153 ms
64 bytes from 2600::: icmp_seq=3 ttl=52 time=152 ms
64 bytes from 2600::: icmp_seq=4 ttl=52 time=208 ms

--- 2600:: ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 152.108/171.523/208.073/22.623 ms

To stop the cellular data network connection use mbimcli disconnect command.
Use the Session ID from the previous mbimcli command reply in --no-open=## attribute, but do not include the --no-close attribute, doing so closes the session afterwards.
mbimcli -p -d /dev/cdc-wdm0 --disconnect --no-open=##


Bring down the interface:
ip link set dev wwan0 down

Clear any remaining IP address and routes:
ip -4 -6 address flush dev wwan0
ip -4 -6 route flush dev wwan0

It is up to the host application to manage and poll the connection state of the cellular module.
E.g. if the connection is lost temporarily due to no network coverage in the current location, the host application should tear down and re-establish the data connection when cellular module is registered in network again.

If the data connection fails for some reason several times, ensure that the connect retry attempts do not take place continuously without some extended delays in-between.
Depending on the cellular network operator, they can enforce lock-out on your subscription/device for certain time periods in order to protect the network from being flooded by requests.

Question

How-to guide for setting up a always on data connection over the Simcom SIM8202x-M2 series modules network interface when used in USB RNDIS mode

Solution

Both Windows and Linux systems can support RNDIS interface drivers for the SIM8202 series modules, this example demonstrates how it can be set up in a Linux environment.

There is a open source Linux in-kernel driver supporting RNDIS USB network interfaces called rndis_host.
Make sure to have the kernel config for rndis host driver support enabled.

Read more about the kernel configs in this FAQ:
Common Linux kernel modules and configs necessary for communicating with cellular modules over USB interface

By default the Simcom modules are delivered with QMI/RMNET network interface enabled, lsusb output can look like following:
Bus 002 Device 002: ID 1e0e:9001 Qualcomm / Option SDXPRAIRIE-MTP

So you will need to change the USB mode by sending a AT commands on the Modem/AT serial ports exposed over the USB interface, typically found as ttyUSB devices if option driver is loaded correctly.
E.g. minicom serial terminal tool can be used to open the USB serial interface and send AT commands to the module:
minicom -D /dev/ttyUSB2

Switch the module from USB PID 9001 to USB PID 9011 mode for RNDIS interface by sending below command followed by enter (CR LF):
AT+CUSBCFG=USBID,1E0E,9011

The module will now restart automatically and re-enumerate with a new USB ID.
Check dmesg or with lsusb that you have the Simcom SIM7600 module detected with VID: 1e0e PID: 9011
lsusb
Bus 002 Device 003: ID 1e0e:9011 Qualcomm / Option SDXPRAIRIE-MTP

Verify with lsusb -t that the Linux in-kernel driver rndis_host driver is loaded correctly for interface 0 and 1.
It can look e.g. like this:
lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 5000M
|__ Port 4: Dev 3, If 0, Class=Miscellaneous Device, Driver=rndis_host, 5000M
|__ Port 4: Dev 3, If 1, Class=CDC Data, Driver=rndis_host, 5000M
|__ Port 4: Dev 3, If 2, Class=Vendor Specific Class, Driver=option, 5000M
|__ Port 4: Dev 3, If 3, Class=Vendor Specific Class, Driver=option, 5000M
|__ Port 4: Dev 3, If 4, Class=Vendor Specific Class, Driver=option, 5000M
|__ Port 4: Dev 3, If 5, Class=Vendor Specific Class, Driver=option, 5000M
|__ Port 4: Dev 3, If 6, Class=Vendor Specific Class, Driver=option, 5000M

If your system don't load the option serial interfaces correctly, then they can be forcefully loaded as bellow (not reboot persistent):
modprobe option
echo 1e0e 9011 > /sys/bus/usb-serial/drivers/option1/new_id

Relate to the following Linux kernel commit for details on how to modify the usb serial option driver source code in order to auto load the drivers:
USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode

In order to enable the automatic network connection establishment, the SIM card should have PIN code check disabled. If it isn't disabled, the Linux host system need to provide the PIN code over AT commands to module after each modem restart.
Refer to AT command: AT+CPIN=xxxx for further details.

The Access Point Name (APN) related to your cellular subscription needs to be configured once to the module so the automatic connection establishment can be established on the correct data bearer.

Defining an empty string as value on the AT+CGDCONT profile, will make the module try to subscribe for a APN, however this may not always work e.g. in roaming conditions, so best procedure is to always configure the correct APNs for the network and your subscription.

Check the currently configured APN profiles:
AT+CGDCONT?
If you do not know the correct APN for your network and subscription, you should at least have profile 1 and 6 defined to empty strings ("") so the module will try to subscribe for the correct APN details from network:
AT+CGDCONT=1,"IPV4V6",""
AT+CGDCONT=6,"IPV4V6",""

+CGDCONT Profile 1 is used for the cellular network registration process and APN at profile 6 will be tied to the RNDIS network interface for the data connection to host system.
Define both APN profiles according to the details you have obtained for your cellular subscription.
Most often the APN details are same for both network registration and the actual data connection, then you define same details to both profile 1 and 6:
AT+CGDCONT=1,"IPV4V6","MY-SUBSCRIPTION-APN"
AT+CGDCONT=6,"IPV4V6","MY-SUBSCRIPTION-APN"

Some APN names require additional authentication also, please refer to the AT command: AT+CGAUTH in the AT commands guide for details on how to define auth details correctly.
Current auth configurations can be checked with AT command:
AT+CGAUTH?

Typically no auth details are needed for the profiles and they should be empty, profiles can be cleared by defining the profile number in question and zero in the second parameter:
AT+CGAUTH=1,0
AT+CGAUTH=6,0

If you have modified the APN information, username and passwords it is necessary to disconnect and reconnect to cellular network and packet data service to activate the new settings.
It can easily be done with toggling AT+CFUN=0 command followed by AT+CFUN=1 to switch modules operation mode (SIM card will also be re-initialized, so PIN code have to be given again if the PIN code check is activated).

The module will now try to establish and maintain the data connection automatically with the new settings.

The cellular module is now configured. The Linux RNDIS host system drivers should also have been detected already and a network interface is available. The interface name given can be checked e.g. from dmesg out:
dmesg | grep "RNDIS device"
rndis_host 2-4:1.0 usb0: register 'rndis_host' at usb-0000:00:15.0-4, RNDIS device, b2:44:25:5d:21:86

Typically it is named usb0 and disabled by default, activate the interface with command:
ip link set usb0 up

To acquire an NAT IP address from the module, please activate a dhcp client on the network interface (if not already running), for example here using dhclient:
dhclient -v usb0

It will bind to a IP address if successful:
Listening on LPF/usb0/b2:44:25:5d:21:86
Sending on LPF/usb0/b2:44:25:5d:21:86
Sending on Socket/fallback
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 3 (xid=0x386d3770)
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 7 (xid=0x386d3770)
DHCPOFFER of 192.168.225.23 from 192.168.225.1
DHCPREQUEST for 192.168.225.23 on usb0 to 255.255.255.255 port 67 (xid=0x70376d38)
DHCPACK of 192.168.225.23 from 192.168.225.1 (xid=0x386d3770)
bound to 192.168.225.23 -- renewal in 20968 seconds.

If everything was configured correctly and the connection established successfully on the given APN, then the host system will have internet access on the RNDIS network interface now:

It can be tested e.g. by pinging a remote host over the RNDIS network interface:
ping -4 -I usb0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 192.168.225.46 usb0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=167 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=37.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=44.4 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=33.6 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 33.600/70.635/166.972/55.753 ms

ping -6 -I usb0 2600::
PING 2600::(2600::) from 2a02:aa1:1021:2c5e:552b:a8cb:532c:bcac usb0: 56 data bytes
64 bytes from 2600::: icmp_seq=1 ttl=51 time=179 ms
64 bytes from 2600::: icmp_seq=2 ttl=51 time=171 ms
64 bytes from 2600::: icmp_seq=3 ttl=51 time=171 ms
^C
--- 2600:: ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 170.776/173.535/178.854/3.761 ms

Tested on:
Simcom SIM8202G-M2 with firmware version LE13B02SIM8202M44A-M2

You might also be interested in