TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register
Cellular Modules LTE CAT 6-18 LTE CAT 6-18 mPCIe

Sierra Wireless MC7430 mPCIe

Article Number: 10397
Supplier number: 1103737

Sierra Wireless MC7430 is a Cat 6 module in the Sierra Wireless MC-series. It supports the latest 4G and 3G networks in Asia and the Pacific's, and will allow a maximum downlink speed of 300 Mbps and a maximum uplink speed of 50 Mbps. Optimized for low power consumption, the MC7430 is ideal for today’s mobile computing, networking, and industrial IoT applications.

The MC7430 supports 3G and 4G global networks, including LTE Advanced, with automatic fallback to 3G networks.

GNSS tracking lets you locate, monitor, and deploy location-based applications and services with module variants supporting GPS, GLONASS, Beidou, and Galileo satellite systems.

End-of-life

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

Quantity Sample Price

No prices available

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

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

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

Subscribe to updates
UMTS Bands
B1 (2100)
B19 (800)
B8 (900)
B5 (850)
B6 (800)
B9 (1700)
MIMO (Multiple-Input Multiple-Output)
Yes
LTE Bands
B1 (2100)
B3 (1800)
B7 (2600)
B8 (900)
B18 (800lower)
B19 (800 upper)
B21 (1500upper)
B5 (850)
B38 (TDD 2600)
B40 (TDD 2300)
B28 (700 APAC)
B39 (TDD 1900)
B41 (TDD 2500)
Manufacturer
Sierra Wireless
LTE Region
Asia
Australia
FOTA Firmware Updates
Yes
Form Factor
mPCIe - full size
Technology
LTE - cat 6
Antenna Interface
IPEX MHF/U.FL
GPS
Yes
GNSS technology
GPS
GLONASS
BeiDou
Max DL Speed
300 Mbps
Max UL Speed
50 Mbps
Chipset
Qualcomm
MDM9230
Operating Temperature Range
-40 °C – 85 °C
Driver Support
Windows 7
Linux
Android
Windows 8
Windows 8.1
Windows 10
Interface
USB 2.0
USB 3.0
Voice Call Support
No
GNSS antenna support
Passive
Active 3.3VDC
SIM interface
Through miniPCIe connector
Dual SIM interface
GPIO
Yes
Carrier Certification
Telstra
KDDI
NTT DOCOMO
Softbank
Extended Operating Temperature Range
-40 °C – 85 °C
Audio interface
Digital PCM signal input/output in socket
Digital I2S signal input/output in socket
Certification
CE
GCF
NCC
CE RED
Size
51 x 30 x 2.7mm
Technical details:
For details on the firmware version related to the manufacturers product number and SKU/BOM codes, please check:
SKU/BOM code vs. firmware version comparison chart

This datasheet shows an comparison overview of the MC-series cellular modules from Sierra Wireless.

Download

Uploaded at
2015-12-10 15:13:54
Last updated
2018-12-03 10:08:20
Related products
Sierra Wireless MC7304
Sierra Wireless MC7354
Sierra Wireless MC7350
Sierra Wireless MC7430 mPCIe
Sierra Wireless MC7455 LTE Cat 6

Technical specification for Sierra Wireless MC7430.

Download

Uploaded at
2016-08-25 17:48:52
Last updated
2018-12-03 10:07:02
Version
R11
Related products
Sierra Wireless MC7430 mPCIe

Sierra Wireless AirPrime MC74-series Migration Guide document describing differences between the previous Sierra Wireless MC73-series modules.

Download

Uploaded at
2017-06-05 17:19:36
Last updated
2018-12-03 10:09:36
Version
1
Related products
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This manual contains the AT Commands for the EM74XX and MC74XX series from Sierra Wireless.

Download

Uploaded at
2016-01-25 10:07:40
Last updated
2019-04-05 11:45:32
Version
R4
Related products
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7455 LTE Cat 6

This document contains the Linux SDK application guide.

Download

Uploaded at
2016-05-25 13:03:27
Last updated
2018-12-03 10:11:48
Version
1.26
Requirements
Linux OS
The following processors are supported:
x86 (32bit & 64bit)
ARM
PPC
MIPS

The following devices are supported:
MC77xx
MC83x5
SL/MC9090
EM/MC73xx
AR7554
EM/MC74xx
Related products
Sierra Wireless MC7710
Sierra Wireless MC7304
Sierra Wireless MC7354
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7355
Sierra Wireless EM7305
Sierra Wireless MC7350
Sierra Wireless MC7700
Sierra Wireless MC7750

Mobile devices using 3G and LTE are equipped with a second receive antenna for improved performance.
This second antenna is required for receive diversity and MIMO.
These concepts, with their associated benefits, requirements and test possibilities, are described in this Application Note in a Q&A format.

Download

This manual describes the Standard AT commands for User Equipment according to the 3GPP TS 27.007 standard
(version 15.4.0 Release 15)

For manual on proprietary model specific extended AT commands please refer to download section of product page.

Download

This document describes services and protocols available over the USB connection, as well as describes the physical USB interface to help developers design host drivers for the AirPrime MC73xx series of embedded modules.

Download

This document provides full description of AT commands for Sierra Wireless AirPrime wireless modules and AirLink Programmable Gateways.
Please refer to the specific Sierra Wireless module AT Command Reference document for list of supported AT commands.

Download

Sierra Wireless MC7430 CE RED Compliance Statement

Download

Uploaded at
2017-05-26 12:20:50
Last updated
2017-05-26 12:20:50
Version
1
Related products
Sierra Wireless MC7430 mPCIe

Archive with Sierra Wireless EM/MC74 series certificates for:
MC7455 USA (FCC), Canada (IC), EU (CE), Mexico
EM7455 USA (FCC), Canada (IC), EU (CE), Taiwan (NCC), Mexico, Brazil (Anatel)
MC7430 EU (CE), Taiwan (NCC), Japan, South Korea, Brazil (Anatel)
EM7430 EU (CE), Taiwan (NCC), Japan, South Korea, Brazil (Anatel)

Download

Uploaded at
2017-02-09 12:27:38
Last updated
2017-02-09 12:27:38
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7455 LTE Cat 6

This ZIP archive contains the Sierra Wireless Linux QMI drivers with manual and release notes.
In the Application Developers Guide you find instructions on how to install the drivers.

Linux QMI GobiNet and GobiSerial Drivers - Customer Release Notes
Linux QMI SDK Application Developers Guide.pdf
Sierra Linux QMI drivers

Download

This zip archive contains the Sierra Wireless Linux Lite QMI SDK files:
Linux QMI SDK lite version
Linux QMI SDK Customer Release Note
Sierra Linux QMI drivers
Linux QMI SDK Application Developers Guide
Linux QMI Drivers - Customer Release Notes

Download

Uploaded at
2018-08-08 10:08:01
Last updated
2019-05-27 11:26:17
Version
V.04.00.20
Requirements
Linux kernel compatibility 2.6.32 to 4.19
The following processors are supported:
x86 (32bit & 64bit), ARM, PPC, MIPS

The following Sierra Wireless devices are supported:
EM/MC74xx
EM75xx
EM/MC73xx
Related products
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless WP8548
Sierra Wireless WP7502
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7355
Sierra Wireless EM7305
Sierra Wireless MC7350
Sierra Wireless MC7354
Sierra Wireless MC7304
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe

This zip archive contains the Sierra Wireless Linux QMI SDK files:
Linux QMI SDK Full Version
Linux QMI SDK Customer Release Note
Sierra Linux QMI drivers
Linux QMI SDK Application Developers Guide
Linux QMI Drivers - Customer Release Notes

Download

Uploaded at
2017-02-20 10:14:45
Last updated
2019-05-27 11:25:09
Version
V.04.00.20
Requirements
Linux kernel compatibility 2.6.32 to 4.19
The following processors are supported:
x86 (32bit & 64bit), ARM, PPC, MIPS

The following Sierra Wireless devices are supported:
EM/MC74xx
EM75xx
EM/MC73xx
Related products
Sierra Wireless MC7350
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless WP8548
Sierra Wireless WP7502
Sierra Wireless MC7304
Sierra Wireless MC7354
Sierra Wireless EM7305
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7355
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe

This archive contains the Sierra Wireless Android RIL library with related manuals and release notes.

Download

Uploaded at
2017-10-05 17:57:52
Last updated
2019-07-16 16:18:35
Version
Android RIL_V9.0.4.0_ARM_64_bin_Android RIL_V8.1.2_x86_64_bin
Requirements
The following Android versions are supported:
• x86
▪ 5.0 (Lollipop)
▪ 5.1 (Lollipop)
▪ 6.0 (Marshmallow)
▪ 7.1 (Nougat)
▪ 8.1 (Oreo)

• ARM
▪ 5.0 (Lollipop)
▪ 5.1 (Lollipop)
▪ 6.0 (Marshmallow)
▪ 7.0 (Nougat)
▪ 7.1 (Nougat)
▪ 8.0 (Oreo)
▪ 8.1 (Oreo)
▪ 9.0 (Pie)
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless MC7304
Sierra Wireless MC7354
Sierra Wireless MC7350
Sierra Wireless EM7305
Sierra Wireless EM7355
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless HL8518
Sierra Wireless HL8528
Sierra Wireless HL8548
Sierra Wireless HL8548-G
Sierra Wireless WP8548
Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe

Connection manager to connect AirPrime EM/MC Series modules to your PC running Windows. Please install USB drivers as mentioned in the related items.

Download

This executable file install the Windows drivers for Sierra Wireless EM/MC Series cellular modules

Download

This file contains the Windows driver for Sierra Wireless modules.

Download

Uploaded at
2016-05-06 17:02:00
Last updated
2017-02-20 10:34:18
Version
4464
Requirements
Windows
Related products
Sierra Wireless MC7430 mPCIe
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7354
Sierra Wireless MC7304
Sierra Wireless EM7430 LTE Cat 6

This executable file install the Windows drivers for Sierra Wireless EM/MC Series Modules

Download

Uploaded at
2017-01-09 15:59:22
Last updated
2017-01-09 15:59:22
Version
V.4581
Requirements
Microsoft Windows 7 / Windows 8 / Windows 10 Driver Package
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7355
Sierra Wireless EM7305
Sierra Wireless MC7350
Sierra Wireless MC7354
Sierra Wireless MC7304

This archive contains the Sierra Wireless MC/EM7430 firmware file with generic operator PRI configuration plus related release notes.
One click firmware update application for Windows and firmware update binaries for Linux systems.

Download

Uploaded at
2018-09-14 12:01:34
Last updated
2019-01-07 11:05:40
Version
V.02.30.03.00
Requirements
Windows: Sierra Wireless Windows drivers
Linux: GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the release notes for Firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk)can be acquired by extracting/unzip this Windows executable file with e.g. 7-Zip or similar software.

Download

Uploaded at
2017-04-03 17:35:55
Last updated
2019-02-14 14:00:06
Version
V.02.30.03.00
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6

Archive containing the one click executable application file for updating the Sierra Wireless modules firmware in Windows as well as the related release notes.

The Linux firmware update files (.cwe, .nvu, or .spk)can be acquired by extracting/unzip this Windows executable file with e.g. 7-Zip or similar software.

Download

Uploaded at
2019-01-04 12:14:42
Last updated
2019-02-14 13:55:51
Version
V.02.30.03.00
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the release notes for firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk) are also included.

Download

Uploaded at
2017-08-07 18:37:01
Last updated
2019-01-04 14:34:36
Version
V.02.30.03.00
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the relase notes for Firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk)can be acquired by extracting/unzip this Windows executable file with e.g. 7-Zip or similar software.

Download

Uploaded at
2017-04-03 17:39:19
Last updated
2019-01-04 14:18:35
Version
V.02.30.03.00
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the Linux firmware update files (.cwe, .nvu, or .spk) for updating the Sierra Wireless modules firmware.
Release notes are also included.

Download

Uploaded at
2017-11-06 15:32:26
Last updated
2017-11-06 15:32:27
Version
SWI9X30C_02.26.01.00_Generic_002.027_000
Requirements
Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the release notes for Firmware and operator config file.

Download

Uploaded at
2017-11-06 15:25:53
Last updated
2017-11-06 15:25:53
Version
SWI9X30C_02.26.01.00_00_GENERIC_002.027_000
Requirements
Microsoft Windows operating system and Sierra Wireless drivers
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the release notes for Firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk) are also included.

Download

Uploaded at
2017-08-07 19:32:19
Last updated
2017-08-07 19:32:20
Version
V.02.24.05.06
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the release notes for Firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk)can be acquired by extracting/unzip this Windows executable file with e.g. 7-Zip or similar software.

Download

Uploaded at
2017-04-21 16:05:33
Last updated
2017-04-21 16:05:33
Version
V.02.24.03.00 Generic
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the relase notes for Firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk)can be acquired by extracting/unzip this Windows executable file with e.g. 7-Zip or similar software.

Download

Uploaded at
2017-02-10 14:15:26
Last updated
2017-04-03 17:40:13
Version
V.02.23.00.00 Generic
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the relase notes for Firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk)can be acquired by extracting/unzip this Windows executable file with e.g. 7-Zip or similar software.

Download

Uploaded at
2017-04-03 17:26:22
Last updated
2017-04-03 17:33:56
Version
V.02.14.03.00 Telstra
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe

This archive contains the one click executable application file for updating the Sierra Wireless modules firmware in Windows and the relase notes for Firmware and operator config file.

The Linux firmware update files (.cwe, .nvu, or .spk)can be acquired by extracting/unzip this Windows executable file with e.g. 7-Zip or similar software.

Download

Uploaded at
2017-04-03 17:28:30
Last updated
2017-04-03 17:31:21
Version
V.02.20.03.01 Telstra
Requirements
Microsoft Windows operating system or Linux with GobiNet, GobiSerial drivers and the firmware download sample application from Sierra Wireless QMI SDK package.
Related products
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Question

How to collect initial diagnostics data for Sierra Wireless EM/MC74xx and EM75xx series cellular modules when requesting technical support?

Solution

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

Please provide a problem description of what exact problem is and in what precise situations it is present.

Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux dist, 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 required also)

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 log output requested from the commands bellow, can be acquired from the module by accessing one of the USB enumerated serial (COM) interfaces accepting AT commands. (In Windows this is generally found listed as a Modem interface or AT commands serial interface in the device manager and in Linux it is usually found on /dev/ttyUSB2 interface). Send the following commands to the module and capture the text output and include them when creating the the technical support ticket.

Sierra Wireless :
AT
ATE1
ATI
AT!ENTERCND="A710"
AT!PRIID?
AT!IMPREF?
AT!IMAGE?
AT+CFUN?
AT!UIMS?
AT+CPIN?
AT+CREG?
AT+CGREG?
AT+CEREG?
AT+COPS?
AT!GSTATUS?
AT+CGDCONT?
AT$QCPDPP?
AT+CGATT?
AT+CGACT?
AT+CGCONTRDP
AT+CGPADDR
AT!BAND?
AT!BAND=?
AT!LTEINFO?
AT!LTECA?
AT!RXDEN?
AT!PCINFO?
AT!USBCOMP?
AT!USBCOMP=?
AT!SELRAT?
AT!SELRAT=?
AT!USBSPEED?
AT!PCOFFEN?
AT!CUSTOM?
AT!CUSTOM=?
AT!PCTEMP?
AT!PCVOLT?
AT!PCVOLTLIMITS?
AT!HWID?
AT!ERR
AT!BCFWUPDATESTATUS
AT!TMSTATUS?

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

Question

How to step by step set up a data connection over QMI interface using qmicli and in-kernel driver qmi_wwan in Linux?

Solution

Several cellular modules based on Qualcomm chipsets implements the Qualcomm Qualcomm MSM (QMI) Interface.
There is a open source Linux in-kernel driver supporting this interface and it is called qmi_wwan. This driver can be used together with ModemManager and NetworkManager to automate connection establishment and as a connection manager.

The library libqmi which ModemManager uses can also be used to communicate in a more direct way with the cellular devices over the QMI interface and to step by step do necessary configurations and trigger the data connection over the cellular network.

A selection of cellular modules can be supported:

Using RAW IP kernel configuration:
Sierra Wireless MC74 series, EM74 series, EM75** series
Telit LM940, LM960
Telit LN94x series (requires USB mode switch)
Simcom SIM7500 series, SIM7600 series, SIM7600 -H series
(can be supported in qmi_wwan driver from kernel 4.18 or by applying the following one line qmi_wwan source code patch on previous kernel builds: qmi_wwan: apply SET_DTR quirk to the SIMCOM shared device ID)

Using 802.3 IP framing kernel configuration:
Simcom SIM7100 series
Sierra Wireless MC73**/EM73** series

ModemManager combined with NetworkManager will detect the cellular modules automatically in most cases, please refer to their respective documentations on how to establish a data connection using them.

Example on how to set up the data connection step by step manually with libqmi:
First install the libqmi Linux library e.g. by using your system package manager like apt or preferably latest version from source on the Freedesktop pages for libqmi project: https://www.freedesktop.org/wiki/Software/libqmi/

Verify that you have the Linux in-kernel qmi_wwan driver installed and attached for the cellular modules QMI interface over USB:
lsusb -t
Can look e.g. like this:
...
|__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=qmi_wwan, 480M
...

If the driver is not correctly loaded, please verify that the module is set to expose the correct USB endpoints configuration toward the host system and that you have followed the provided guides from the cellular module vendors, regarding how to implement the module in Linux.

Libqmi expose a command line interface that can be used to communication with the module over QMI interface.
The qmicli help will output information about all commands available:
qmicli --help-all

The cellular modules QMI control interface are usually named cdc-wdm* e.g.:
qmicli --device=/dev/cdc-wdm0

In order to allow parallel commands to be execute on the module over QMI interface, it is recommended to use the libqmi proxy function. This can be done by including the attribute -p or --device-open-proxy in every qmicli command.

If a SIM pin is required for the SIM card, use command bellow:
qmicli --device=/dev/cdc-wdm0 -p --dms-uim-verify-pin=PIN,1234

The name of the related network interface to QMI control channel can be acquired with the command:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --get-wwan-iface

The most recent Qualcomm based cellular modules only expose QMI interfaces that can support Raw-IP mode. Sierra Wireless EM/MC74 and EM75 series modules, Telit LM940 and LN940 series for example require this.
Check what IP-mode the host system is configured for:
qmicli --device=/dev/cdc-wdm0 --get-expected-data-format
Check what IP-mode the cellular module require:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wda-get-data-format

to change qmi_wwan driver to use Raw-IP.
Disable the network interfaces exposed by the cellular module:
ip link set dev wwan0 down
Trigger the Raw-IP support:
echo Y > /sys/class/net/wwan0/qmi/raw_ip
Enable the network interfaces again:
ip link set dev wwan0 up

Now the data connection in the cellular module can be activated e.g. with a IPv4 type configuration on the specified APN:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wds-start-network="ip-type=4,apn=data.tre.se" --client-no-release-cid

Once "Network started" is displayed, you can send a DHCP request on the network interface.
Please note that not all DHCP clients in Linux can support Raw-IP format, udhcpc however support this for IPv4 over Raw-IP.
udhcpc -q -f -n -i wwan0

Disconnect the data bearer and data connection over QMI by command bellow and providing the network handle and CID returned at connection activation:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --wds-stop-network=NETWORK_HANDLE --client-cid=CID

Additional useful commands:

Request module manufacturer:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-manufacturer

Get module model:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-model

Get firmware version:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-revision

Get module IDs (IMEI etc.):
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --dms-get-ids

Get SIM card status:
qmicli --device=/dev/cdc-wdm0 --device-open-proxy --uim-get-card-status

Recent cellular modules like Sierra Wireless EM7565 require at least libqmi V1.20. Check version with command:
qmicli --version

If the connection was successfully set up established, you now have data connectivity. A ping to a remote server using the cellular network interface can for example prove this:
ping -I wwan0 8.8.8.8

The ifconfig Linux tool can show the current details for the network interface:
ifconfig wwan0

libqmi is well integrated and supported in ModemManager tool for Linux. ModemManager again is well integrated and supported when using NetworkManager tool in Linux. Please note however that these two tools expect the cellular module interfaces to only be used by them so if you manually want to use the libqmi library or AT commands interfaces, please turn off/disable ModemManager and NetworkManager first.

The libqmi is a generic open source library for Linux systems and QMI protocol from Qualcomm, therefor there are commands only working on selected devices and not necessarily supported on the device you use, resulting in an error message.

Question

What firmware versions are related to the specific SKU/BOM codes of cellular modules?

Solution

Sierra Wireless
10839 Sierra Wireless EM7565, CAT-12, M.2 CBRS ENABLED
SKU: 1104207 Firmware: 01.07.02.00 GENERIC

10692 Sierra Wireless EM7565 LTE CAT-12 M.2
SKU: 1103520 Firmware: 01.07.02.00 GENERIC

10375 Sierra Wireless EM7455 LTE Cat 6
SKU: 1103582 Firmware: 02.24.05.06 GENERIC/AT&T/SPRINT/VERIZON
SKU: 1103780 Firmware: 02.24.05.06 GENERIC/AT&T/SPRINT/VERIZON

10427 Sierra Wireless EM7430
SKU: 1103733 Firmware: 02.24.05.06 GENERIC/DOCOMO/KDDI/SOFTBANK/TELSTRA

10374 Sierra Wireless MC7455 LTE Cat 6
SKU: 1103789 Firmware: 02.24.05.06 GENERIC/AT&T/BELL/ROGERS/SPRINT/TELUS/US CELLULAR/VERIZON/VODAFONE

10397 Sierra Wireless MC7430 mPCIe
SKU: 1103737 Firmware: 02.24.05.06 GENERIC/DOCOMO/KDDI/SOFTBANK/TELSTRA

10840 Sierra Wireless EM7511
SKU: 1103989 Firmware: 01.07.02.00 AT&T/GENERIC

Huawei:
10278 Huawei ME909s-120 mPCIe:
SKU: 55010273 Firmware: 11.617.01.00.00
SKU: 55010782 Firmware: 11.617.09.00.00
SKU: 55010946 Firmware: 11.617.14.00.00
SKU: 55010983 Firmware: 11.617.15.00.00

10279 Huawei ME909s-120 LGA EU:
SKU: 55010781 Firmware: 11.617.09.00.00
SKU: 55010782 Firmware: 11.617.15.00.00

Simcom:
10689 SIMCom SIM7600E-H LTE SMT EU
SKU: S2-107EQ-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107EQ-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107EQ-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107EQ-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107EQ-Z1W51 Firmware: LE11 B11 SIM7600M22

10690 SIMCom SIM7600E-H LTE mPCIe EU
SKU: S2-107ER-Z1W2L Firmware: LE11 B07 SIM7600M22
SKU: S2-107ER-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107ER-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107ER-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107ES-Z1W51 Firmware: LE11 B11 SIM7600M22

10818 SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
SKU: S2-107ES-Z1W27 Firmware: Firmware: LE11B07SIM7600M22
SKU: S2-107ES-Z1W2L Firmware: LE11B08SIM7600M22
SKU: S2-107ES-Z1W3S Firmware: LE11B09SIM7600M22
SKU: S2-107ES-Z1W4J Firmware: LE11B10SIM7600M22
SKU: S2-107ES-Z1W51 Firmware: LE11B11SIM7600M22

10710 SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
SKU: S2-107Q0-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107Q0-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107Q0-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107Q0-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107Q0-Z1W51 Firmware: LE11 B11 SIM7600M22

SIM7600SA-H SMT type
SKU: S2-107BH-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107BH-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107BH-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107BH-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107BH-Z1W51 Firmware: LE11 B11 SIM7600M22

10757 SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SKU: S2-107KX-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107KX-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107KX-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107KX-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107KX-Z1W51 Firmware: LE11 B11 SIM7600M22

SIM7600SA-H LTE CAT 4 -mPCIE with Audio
SKU: S2-107KY-Z1W27 Firmware: LE11 B07 SIM7600M22
SKU: S2-107KY-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107KY-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107KY-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107KY-Z1W51 Firmware: LE11 B11 SIM7600M22

10810 SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SKU: S2-107QZ-Z1W2L Firmware: LE11 B08 SIM7600M22
SKU: S2-107QZ-Z1W3S Firmware: LE11 B09 SIM7600M22
SKU: S2-107QZ-Z1W4J Firmware: LE11 B10 SIM7600M22
SKU: S2-107QZ-Z1W51 Firmware: LE11 B11 SIM7600M22

SIM7600E SMT type
SKU: S2-107EP-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107EP-Z1W4D Firmware: LE11 B02 SIM7600M21-A

10812 SIMCom SIM7600E CAT-1 mPCIe
SKU: S2-107ET-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107ET-Z1W4D Firmware: LE11 B02 SIM7600M21-A

SIM7600E LTE CAT 1 -mPCIE with Audio
SKU: S2-107EV-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107EV-Z1W4D Firmware: LE11 B02 SIM7600M21-A

10813 SIMCom SIM7600SA LTE CAT-1 mPCIe
SKU: S2-107KV-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107KV-Z1W4D Firmware: LE11 B02 SIM7600M21-A

SIM7600SA SMT type
SKU: S2-107BG-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107BG-Z1W4D Firmware: LE11 B02 SIM7600M21-A

SIM7600SA LTE CAT 1 -mPCIE with Audio
SKU: S2-107KW-Z1W2P Firmware: LE11 B01 SIM7600M21-A
SKU: S2-107KW-Z1W4D Firmware: LE11 B02 SIM7600M21-A

10305 SimCom SIM7100 LTE mPCIe US
SKU: S2-106EW-Z1L7X Firmware: 4534B03SIM7100A
SKU: S2-106EW-Z1L72 Firmware: 4534B03SIM7100A

Question

How can we use Sierra Wireless MC/EM74 and EM75 series cellular modules in Linux with the MBIM control and data interface?

Solution

The Sierra Wireless MC/EM74 and EM75 series cellular modules can expose the Mobile Broadband Interface Model (MBIM) Interface.

There is a open source Linux in-kernel driver supporting MBIM interface and it is called cdc_mbim. The library libmbim can be used to communicate with the cellular devices over the interface and do necessary configurations to trigger the data connection over the cellular network.

First install the libmbim and libmbim-utils Linux library using your system package manager like apt etc. (more details about libmbim here: https://www.freedesktop.org/wiki/Software/libmbim/)

Check with lsusb that you have the Sierra wireless module loaded, vid:pid value 1199:9091 or 1199:9071 should be present.
lsusb
Bus 002 Device 003: ID 1199:9091 Sierra Wireless, Inc.
or:
Bus 002 Device 003: ID 1199:9071 Sierra Wireless, Inc.

Verify with lsusb -t that the Linux in-kernel cdc_mbim driver is correctly loaded for the cellular module. It can look e.g. like this:
lsusb -t
...
|__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=qcserial, 5000M
|__ Port 3: Dev 3, If 2, Class=Vendor Specific Class, Driver=qcserial, 5000M
|__ Port 3: Dev 3, If 3, Class=Vendor Specific Class, Driver=qcserial, 5000M
|__ Port 3: Dev 3, If 12, Class=Communications, Driver=cdc_mbim, 5000M
|__ Port 3: Dev 3, If 13, Class=CDC Data, Driver=cdc_mbim, 5000M
...

If this is not the case, you will have to change USB end points the cellular module exposes. This can be done through AT commands sent to the modules serial interfaces accepting AT commands. Usually located at dev/ttyUSB2 if the qcserial drivers are correctly loaded.

MC74xx/EM74xx series:
AT!ENTERCND="A710"
AT#USBCOMP=1,1,100D
AT!RESET

EM75xx series:
AT!ENTERCND="A710"
AT#USBCOMP=1,3,100D
AT!RESET

(Applications like Minicom or Picocom can be used to send AT commands over the serial interfaces)

Should you have no serial interface loaded, it is because the driver has not been loaded for the USB serial endpoints due to missing vid:pid values in the qcserial driver. You can then use the commands bellow to temporarily load the driver for new vid:pid combinations.
modprobe qcserial
EM75 series:
echo 1199 9091 > /sys/bus/usb-serial/drivers/qcserial/new_id
MC74xx/EM74xx series:
echo 1199 9071 > /sys/bus/usb-serial/drivers/qcserial/new_id

When you have changed the cellular modules USB endpoint configuration to expose MBIM interface and module have restarted, then you can use libmbim's command line interface to control the cellular module.

Using libmbim with the command line interface mbimcli:
List all available options for mbimcli:
mbimcli --help-all

Check version
mbimcli --version

The cellular modules mbim interface is usually named cdc-wdm* among the devices. For mbimcli this is defined by --device=/dev/cdc-wdm0 parameter. You should also use the proxy function to enable parallel commands to be sent to module even if the interface already is in use by a data connection. This is done by including --device-open-proxy or -p in every mbimcli requst to module.
Command example to query device capabilities and information (firmware & IMEI code etc.):
mbimcli --device=/dev/cdc-wdm0 --device-open-proxy --query-device-caps

The libmbim tool: mbim-network can be used to establish a simple data connection.
First create a config file containing your network operators APN details. Save it in the default location where mbim-network searches for the file: /etc/mbim-network.conf .
The parameter --profile=[PATH] can be used to alter this path when executing mbim-network.

Save the APN details, (and username, password and authentication type if necessary) into the configuration file:
APN=
APN_USER=
APN_PASS=
APN_AUTH=
PROXY=yes

How to start a data connection after configuration file is in place:
Enter SIM PIN (if necessary for SIM card):
mbimcli -d /dev/cdc-wdm0 -p --enter-pin=1234

Start the mbim data connection with command bellow, if successful it will print "Network started successfully"
mbim-network /dev/cdc-wdm0 start

You can now execute the mbim-set-ip script (download found bellow related to this FAQ) with sufficient system privileges:
./mbim-set-ip /dev/cdc-wdm0 wwan0

This script will collect the network interface IP configurations from the cellular module over MBIM interface using mbimcli, parse them and apply them to the network interface in Linux, this because DHCP requests are generally not supported over MBIM interfaces.

Once you have started the data connection and set the details with the mbim-set-ip script you should be able to ping the data connection:
IPv4 ping: (only supported if IPv4 address was acquired from cellular module)
ping -4 -I wwan0 8.8.8.8
ping -4 -I wwan0 google.com

IP v6 ping: (only supported if IPv6 address was acquired from cellular module)
ping -6 -I wwan0 2001:4860:4860::8888
ping -6 -I wwan0 google.com

The cellular data connection can be disconnected by commands:
Stop mbim data connection:
mbim-network /dev/cdc-wdm0 stop

Set network interface down:
ip link set wwan0 down

Other useful commands:
Query device capabilities and information (firmware & IMEI code etc.):
mbimcli -d /dev/cdc-wdm0 -p --query-device-caps

Query SIM card information:
mbimcli -d /dev/cdc-wdm0 -p --query-subscriber-ready-status

Query network registration state:
mbimcli -d /dev/cdc-wdm0 -p --query-registration-state

Query connection ip information:
mbimcli -d /dev/cdc-wdm0 -p --query-ip-configuration=0

Test setup:
Software: Ubuntu server 18.04 LTS with kernel 4.15.0-23-generic and mbimcli 1.14.2
Hardware: Sierra Wireless EM7565 with firmware SWI9X50C_01.07.00.00 on Aaeon UP Squared host board with 10703 M.2 to USB 3.0 Adapter.

Question

How can we use the Linux NetworkManager and ModemManager applications that are built into many recent Linux desktop distributions (such as Ubuntu) with Sierra Wireless MC/EM74 and EM75 series cellular module to establish and set up a data connection?

Solution

When using NetworkManager and ModemManager that are pre-installed in many common Linux distributions, best compatibility can be reached when the cellular module is set to expose the MBIM interface endpoints to the host system over the USB interface. The MBIM interface driver is often automatically detected and loaded without the need to configure and add additional drivers to the kernel via rebuild.

In factory default configuration the Sierra Wireless modules do expose the QMI interfaces as well as a set of serial interfaces, this is the correct USB endpoints if the modules are used with the Sierra Wireless recommended GobiNet and GobiSerial drivers.

However if you want to use the module with MBIM interface instead, you can change the exposed USB endpoint configuration by sending the module the following AT command on the Modem serial interface (usually dev/ttyUSB2 in Linux systems):

MC74xx/EM74xx series:
AT!ENTERCND="A710"
AT#USBCOMP=1,1,100D
AT!RESET

EM75xx series:
AT!ENTERCND="A710"
AT#USBCOMP=1,3,100D
AT!RESET

(please note ModemManager can occupy and interfere on the Modem/AT serial interface so it is recommended to stop its process first)
This will configure and reset the module and when module is re-detected in the host system again, the endpoints exposed have changed and the cdc_mbim driver should have been automatically loaded for the cellular module, this can be verified with the command:
lsusb -t

By restarting ModemManager and NetworkManager or the complete host system, the Sierra Wireless cellular module should be automatically detected by both ModemManager as well as NetworkManager.

The graphical user interface in the Linux operating system can now be used to configure the PIN code and your network operators APN connection details and establish the data connection.

If you want to control NetworkManager by Linux command line, a guide and example is well documented in the following guides:

ModemManager:
https://docs.ubuntu.com/core/en/stacks/network/modem-manager/docs/configuring-cellular-connections

NetworkManager:
https://docs.ubuntu.com/core/en/stacks/network/network-manager/docs/configure-cellular-connections

Please note that DHCP clients are most often not supported for the cellular modules when MBIM interface is used, therefore this IP connection information should be collected via the ModemManager from the modules data bearer details. NetworkManager will do this automatically for you, so it is recommended to use NetworkManager together with ModemManager also when possible.

Question

How to change USB composition mode to Mobile Broadband Interface (MBIM) that is used by Windows 8 and 10 systems for data connectivity and enabling support for the built-in connection manager in Windows?

Solution

This is done by sending AT commands to the Modem or AT serial interfaces that are accepting AT commands and changing the USB endpoint composition:

Sierra Wireless EM74xx, MC74xx series module:
AT!ENTERCND=”A710”
AT!USBCOMP=1,1,100D
AT!RESET

Sierra Wireless EM73xx, MC73xx series module:
AT!ENTERCND=”A710”
AT!UDUSBCOMP=8
AT!RESET

Simcom SIM7xxx series modules:
AT+CUSBPIDSWITCH=9003,1,1
AT+CRESET

ZTE Welink ME3630 series:
AT+ZSWITCH=8
AT+ZRST

Telit LM940:
AT#USBCFG=2
AT#REBOOT

Telit LE910x V2:
AT#USBCFG=3
AT#REBOOT

On Huawei modules the USB mode changing is done automatically by the Windows drivers and otherwise defaults to the modules standard endpoint interfaces.

Question

How do we use the GNSS location tracking (GPS) functionality of the Sierra Wireless EM/MC74** series cellular modules?

Solution

The Sierra Wireless EM/MC74 series modules include a GNSS tracker that can be enabled to acquire location data.

Pre-requirements:
EM/MC74 series module:
Connected to host system with sufficient power supply and correct drivers installed in the host system.

GNSS/GPS antenna:
The GNSS antenna should have clear sky view without obstacles in the way and be connected to the cellular modules antenna connector marked "GPS". If a passive antenna is used the antenna cable should be kept very short (preferably bellow 1 meter) as GNSS signals are very weak and not placed near interference sources.

Details of the available AT commands related to GNSS functionality are described in the "Sierra Wireless EM74XX and MC74XX AT Command Reference Manual" chapter 7: GNSS Commands.

The serial interface accepting AT commands is usually found under /dev/ttyUSB2 in Linux systems and under Modem tab in Windows Device manager (opening the device properties and Modem tab will show its given COM port number in the Windows system).

A basic GNSS tracking session outputting the location data on the NMEA serial interface can be started with the following AT command
AT!GPSTRACK=fixType,maxTime,maxDist,fixCount,fixRate

Bellow command starts a standalone tracking with 255 seconds timeout value, 250 meter accuracy, continuous tracking, fixed data output rate every second on the NMEA virtual serial interface:
AT!GPSTRACK=1,255,250,1000,1

Depending on if an GNSS antenna with or without low noise amplifier (active/passive antenna) are used, the AT+WANT command can adjust if the antenna power supply of 3 volt should be enabled or disabled.
Passive GPS antenna:
AT+WANT=0
Active GPS antenna:
AT+WANT=1

A GNSS tracking session can be interrupted and ended with the command:
AT!GPSEND

In Linux applications it is recommended to use the Sierra Wireless provided GobiNet and GobiSerial drivers for optimal performance. If the Linux in-kernel drivers are used, it might be needed also to send the bellow sentence to the ttyUSBx that represents the NMEA serial interface in order to activate the data stream on the interface:
$GPS_START

The antenna connector used by the GPS tracker can be either through the dedicated GNSS port or it can be combined with the Rx Diversity antenna located on the AUX marked connector. This is selected by changing a parameter with the AT!CUSTOM command:

To select usage of the dedicated GNSS antenna connector on cellular module, execute:
AT!ENTERCND="A710"
AT!CUSTOM="GPSSEL",0
This will select usage of the dedicated GPS antenna slot (Default value)

For further details on how to configure the GPS for different application and scenarios, such as using Assisted GPS, or changing output formats etc. please relate to the AT commands reference.

Question

Why should we use USB3 instead of USB2 as host system data interface if the cellular module can support both?

Solution

Cellular modules supporting higher data throughput rates like LTE Advanced, category 6 and above (300Mbps downlink and 50Mbps uplink) often support both USB3 interface as well as USB2 interface towards the host system.

It is recommended to implement and use the USB3 data interface rather than the older USB2 interface on these modules between host system and the cellular module. This because USB3 can support around 10 times higher data throughput rate compared to USB2 and avoid a possible bottleneck / limitation in the data interface between host and cellular module.

If a miniPCIe based cellular module implementing USB3 are used, please verify that conflicts don't occur towards your hosts miniPCIe socket, as the USB3 interface is not implemented by default in the miniPCIe standard and therefore signal collisions can happen between USB3 pins and PCIe data interface pins situated on same locations. Refer to the cellular module hardware guides and host system hardware guides to verify this.

Question

How can we establish data connection for cellular modules in Windows 8 and Windows 10 systems?

Solution

Microsoft Windows desktop versions starting from Windows 8 and newer have built in data connection manager for WWAN, Wifi etc. that can be used to configure, control and establish the data connection of cellular module that support MBIM interface, which most cellular modules do.

The connection managers settings and controls can be found and accessed on Windows desktop start menu through the network icon (see picture).

The Cellular tab can be found in Windows system settings and if needed the connection APN details can be manually entered through "Advanced options".

Question

How can we capture DM serial port logs for Sierra Wireless EM/MC series cellular modules in Linux?

Solution

In the Sierra Wireless QMI SDK downloadable archive there is a a DM log tool in the tools folder.
Run the dmcapture.sh script with desired filter, and the ttyUSB0 (DM port) device selected.

E.g. like this:
sudo ./dmcapture.sh -l -d /dev/ttyUSB0 -o testlog -f ./filters/v11026_Generic_GSM_WCDMA_LTE_IP.sqf

This will create a log file that can be sent for analyze and debug to Sierra Wireless.

Question

MiniPCIe based cellular modules supporting both USB2 and USB3 are not detected in the host system? Such as Sierra Wireless MC74** series, and Telit LM940/LM960 series modules.

Solution

From start the PCI-SIG miniPCIe form factor standard only included support for PCIe + USB2 data interface and had designated signal lines for these between host system and the miniPCIe module. Since revision 2.1 of the PCI-SIG miniPCIe standard it is defined that the PCIe data lanes can be shared/used for USB3 also.

Cellular modules mainly rely on USB2 interface but as the cellular throughput speeds have increased, the USB2 can become a bottleneck on LTE Cat 6 modules and higher. To address this, USB3 data interface was introduced on the higher data throughput mobile broadband cellular modules and made available in parallel to USB2 interface. However due to limited amount of pin lanes available in the miniPCIe socket they share location with the PCIe data interface pin lanes.

When the host system and module are powered on, the cellular module will try to probe if USB3 interface is present on the pin lanes and if communication can be established, otherwise the module will revert to using the USB2 data interface instead.

However, in some host systems where PCIe data interface also is implemented on the shared pin lanes, the signals will interfere with the cellular modules probing for USB3 interface making it not fall back to USB2 data interface. This usually result in the cellular module not being detected at all in the host operating system.

The USB3 auto-sensing functionality is enabled by default but can be disabled by using AT commands to write the memory changes to the internal NV memory which is stored between restarts. After the module is restarted it will use only the USB2 pin lanes for data interface. Please also check and validate if the host system BIOS support disabling of the PCIe interface in the miniPCIe socket.

Related AT commands for configuring USB3/USB2 modes:

Telit LM940/LM960 modules:
AT#USBSWITCH=1
AT#REBOOT

For Sierra Wireless MC74 series: (firmware version dependent)
AT!ENTERCND="A710"
AT!USBSPEED=0
AT!RESET

For troubleshooting this issue in hardware, you can try isolating the USB3 data interface pins #23, 25, 31, 33 on the top side of the miniPCIe data cards card socket so no signalling to and from the hosts can occur. This could be done in the board design or with adapter.

Question

How can I enable DC voltage output for active GPS/GNSS antennas on modules that support this feature?

Solution

The 3 volt DC Low Noise Amplifier voltage supply from the cellular module can be enabled according to AT commands bellow:

For Sierra Wireless EM/MC74 series:
AT!ENTERCND="A710"
AT+WANT=1

For Sierra Wireless MC73 series:
AT!ENTERCND="A710"
AT+WANTGNSSPWR=1

For Simcom SIM7100, SIM7500, SIM7600 and SIM7600 -H series:
AT+CVAUXV=3050
AT+CVAUXS=1

You might also be interested in