TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register
Product list

Sierra Wireless EM7565 LTE CAT-12 M.2

Article Number: 10692
Supplier number: 1103520

The Sierra Wireless EM7565 module is part of the EM Series offering global 4G coverage, unprecedented LTE speeds, bandwidth, and network performance on the M.2 form factor commonly used in networking equipment. This is the last 4G module you will need before migrating to 5G.

Leveraging carrier aggregation, this LTE-Advanced Pro Cat-12 embedded module delivers up to 600Mbps downlink speed and 150Mbps uplink speed, offering global 4G coverage on a single module. With automatic fallback to 3G networks and integrated GNSS receiver (GPS, GLONASS, Beidou, and Galileo satellite systems supported), the EM7565 is ideal for mobile computing, networking, and industrial M2M applications.

Coupled with the most operator certifications in the industry and network switching capability, EM7565 allows customers to change their network provider anytime, providing more flexibility in manufacturing.

Please note:
This Product Number (SKU) of Sierra Wireless EM7565 have the CBRS LTE bands 42, 43, 48 disabled due to previous regulatory conditions. Please find direct link bellow to the version enabling the CBRS LTE bands also:
10839 Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled

Quantity Sample Price
≥ 1 $164.70
≥ 1 €148.20

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
LTE Region
Europe
North America
Asia
Australia
South America
Japan
Africa
LTE Bands
B1 (2100)
B2 (1900)
B3 (1800)
B4 (AWS)
B7 (2600)
B8 (900)
B9 (1800)
B12 (700ac)
B13 (700c)
B18 (800lower)
B19 (800 upper)
B20 (800DD)
B5 (850)
B26 (US 850 Ext)
B28 (700 APAC)
B29 (US 700de Lower)
B41 (TDD 2500)
B30 (2300 WCS)
B66 (AWS-3)
B32 (1500)
B46 (TDD 5200)
UMTS Bands
B1 (2100)
B2 (1900)
B19 (800)
B8 (900)
B4 (AWS)
B5 (850)
B6 (800)
B9 (1700)
Manufacturer
Sierra Wireless
Form Factor
M.2 3042
Technology
LTE - cat 12
Antenna Interface
IPEX MHF-4
Size
42 x 30 x 2.3 mm
Carrier Certification
AT&T
GPS
Yes
GNSS technology
GPS
GLONASS
BeiDou
Galileo
MIMO (Multiple-Input Multiple-Output)
Yes
GPIO
Yes
Max DL Speed
600 Mbps
Max UL Speed
150 Mbps
Chipset
Qualcomm
MDM9x50
Driver Support
Linux
Android
Windows
Windows 8
Windows 8.1
Windows 10
Interface
USB 2.0
USB 3.0
SIM card
Operating Temperature Range
-30 °C – 70 °C
Module KEY
B
Certification
FCC
GCF
NCC
PTCRB
CE RED
Voice Call Support
No
Audio interface
Digital PCM signal input/output in socket
Digital I2S signal input/output in socket
GNSS antenna support
Passive
Active
Extended Operating Temperature Range
-40 °C – 85 °C
FOTA Firmware Updates
Yes
SIM interface
Through M.2 connector
Dual SIM interface
Technical details:
For details on the firmware version related to the manufacturers product number and SKU/BOM codes, please relate to:
SKU/BOM code vs. firmware version comparison chart

This Product Number (SKU) of Sierra Wireless EM7565 have the CBRS LTE bands 42, 43, 48 disabled due to previous regulatory conditions. Please find direct link bellow to the version enabling the CBRS LTE bands also:
10839 Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled

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

Download

Hardware guide and product specifications for the Sierra Wireless EM7565 cellular M.2 Key B module.

Download

Uploaded at
2017-11-09 10:26:15
Last updated
2018-12-19 10:17:18
Version
41110788 r8
Related products
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled

This guide compares and describes the hardware differences between the Sierra Wireless AirPrime EM cellular modules based on the M.2 key B form factor.

Download

Uploaded at
2018-06-11 14:49:40
Last updated
2018-12-03 11:53:37
Version
41112212 R1
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7511 LTE CAT-12

This document describes proprietary, password-protected AT commands available for Sierra Wireless AirPrime® 9x50-based intelligent embedded modules.

Download

Uploaded at
2018-04-03 16:50:50
Last updated
2019-03-04 11:00:30
Version
R2
Related products
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled

This guide describes differences in how the the single Rmnet USB endpoint can be used to separate and support multiple PDN connections for Sierra Wireless modules based on Qualcomm chipset MDM9x06, MDM9x07, MDM9x50 with the GobiNet and GobiSerial drivers.

Download

Uploaded at
2018-01-12 15:10:07
Last updated
2018-12-03 11:54:04
Version
2174187 - Rev1.0
Requirements
Linux GobiNet, GobiSerial drivers
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7511 LTE CAT-12

RohS Declaration of Conformity Document for Sierra Wireless EM7565

Download

Uploaded at
2018-11-27 15:12:42
Last updated
2018-11-27 15:12:42
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12

CE RED Compliance Statement Sierra Wireless EM7565 cellular module

Download

Uploaded at
2018-11-27 15:11:14
Last updated
2018-11-27 15:11:14
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12

Microsoft Windows desktop driver installer application for Sierra Wireless AirPrime EM/MC series.

Download

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-01-29 10:45:58
Version
V.04.00.18
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 EM7511 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
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 WP7502
Sierra Wireless WP8548
Sierra Wireless EM7565 LTE CAT-12

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-01-29 10:44:06
Version
V.04.00.18
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 EM7511 LTE CAT-12
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 EM7305
Sierra Wireless MC7354
Sierra Wireless MC7304
Sierra Wireless WP7502
Sierra Wireless WP8548
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless MC7350

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

Download

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

Download

Uploaded at
2017-10-05 17:57:52
Last updated
2017-10-05 17:57:52
Version
V7.1.3.0
Requirements
The following Android versions are supported:
x86
4.4 (KitKat)
5.0 (Lollipop)
5.1 (Lollipop)
6.0 (Marshmallow)
7.1 (Nougat)

ARM
2.2 (Froyo)
2.3 (Gingerbread)
3.1 (Honeycomb)
4.0 (Ice cream sandwich)
4.2 (Jelly bean)
4.4 (KitKat)
5.0 (Lollipop)
5.1 (Lollipop)
6.0 (Marshmallow)
7.0 (Nougat)
Related products
Sierra Wireless WP8548
Sierra Wireless HL8548-G
Sierra Wireless HL8548
Sierra Wireless HL8528
Sierra Wireless HL8518
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 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled

This archive contains the Sierra Wireless EM7565 Windows firmware update package for Generic PRI as well as the firmware binary files for update on Linux based platforms. Please relate to the release notes prior to update regarding update instructions.

Download

Uploaded at
2018-11-09 10:11:21
Last updated
2018-12-06 09:05:19
Version
SWI9X50C_01.08.04.00_GENERIC_002.012_000
Requirements
For Windows systems:
Microsoft Windows 8+
Sierra Wireless Windows driver package

For Linux systems:
Sierra Wireless GobiNet and GobiSerial drivers
Sierra Wireless QMI SDK firmware update sample applications
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12

This archive contains the Sierra Wireless EM7565 Windows firmware update package for AT&T operator PRI (002.008_004) as well as the firmware binary files for update on Linux based platforms. Please relate to the release notes prior to update regarding update instructions.

Download

Uploaded at
2018-11-09 10:06:46
Last updated
2019-03-15 09:55:45
Version
V.01.07.02.00 (ATT PRI: 002.008_004)
Requirements
For Windows systems:
Microsoft Windows 8+
Sierra Wireless Windows driver package

For Linux systems:
Sierra Wireless GobiNet and GobiSerial drivers
Sierra Wireless QMI SDK firmware update sample applications
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12

This archive contains the Sierra Wireless EM7565 Windows firmware update package for
Verizon operator (PRI: 002.015.001) as well as the firmware binary files for update on Linux based platforms. Please relate to the release notes prior to update regarding update instructions.

Download

Uploaded at
2018-12-04 10:49:30
Last updated
2019-03-15 09:43:28
Version
V. 01.08.04.00 (VERIZON PRI: 002.015.001)
Requirements
For Windows systems:
Microsoft Windows 8+
Sierra Wireless Windows driver package

For Linux systems:
Sierra Wireless GobiNet and GobiSerial drivers
Sierra Wireless QMI SDK firmware update sample applications
Related products
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled

This archive contains the Sierra Wireless EM7565 Windows firmware update package for Generic PRI as well as the firmware binary files for update on Linux based platforms. Please relate to the release notes prior to update regarding update instructions.

Download

Uploaded at
2018-07-19 10:57:53
Last updated
2018-12-06 09:08:51
Version
EM7565_SWI9X50C_01.07.02.00_00_GENERIC_002.004_000
Requirements
For Windows systems:
Microsoft Windows 8+
Sierra Wireless Windows driver package

For Linux systems:
Sierra Wireless GobiNet and GobiSerial drivers
Sierra Wireless QMI SDK firmware update sample applications
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12

This archive contains the Sierra Wireless EM7565 Windows firmware update package for Generic PRI as well as the firmware binary files for update on Linux platforms.

Download

Uploaded at
2018-06-27 10:39:19
Last updated
2018-12-06 09:08:31
Version
EM7565_SWI9X50C_01.07.00.00_GENERIC_002.002_000
Requirements
For Windows systems:
Microsoft Windows 8+
Sierra Wireless Windows driver package

For Linux systems:
Sierra Wireless GobiNet and GobiSerial drivers
Sierra Wireless QMI SDK firmware update sample applications
Related products
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless EM7565 LTE CAT-12

This archive contains the firmware binaries and config files for the Sierra Wireless EM7565 module.

Download

Uploaded at
2018-03-19 16:14:19
Last updated
2018-12-06 09:07:52
Version
01.05.01.00
Requirements
Linux,
GobiNet and GobiSerial drivers
Sierra Wireless QMI SDK firmware update tool sample application
Related products
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled

This archive contains the Sierra Wireless EM7565 Windows firmware update packages V.01.05.01.00

Download

Uploaded at
2018-03-02 17:22:07
Last updated
2018-12-06 09:06:57
Version
01.05.01.00
Requirements
Microsoft Windows 8+
Related products
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
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!PCINFO?
AT!PCTEMP?
AT!PCVOLT?
AT!USBCOMP?
AT!USBCOMP=?
AT!CUSTOM?
AT!CUSTOM=?
AT!ERR
AT!BCFWUPDATESTATUS
AT!SELRAT?
AT!SELRAT=?

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

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

The Sierra Wireless EM73, EM74 and EM75 series M.2 modules are not detected in the host system when used with the M.2 to USB adapter board? (USBM2, USB3M2)

Solution

For Sierra Wireless EM73, EM74 and EM75 series M.2 modules you will have to change the state of the jumper JP1 on the USB adapter board. This controls the Dynamic Power Control (DPR) pin in M.2 socket to the cellular module.

Please remove the pin jumper piece and leave all 3 pins not connected / floating. This will allow the module to operate normally.

After changing this jumper state and powering on the module and adapter board, you should see the module appear and boot up normally in the host system device.

For further details, please relate to the Sierra Wireless related product technical specification as well as the assembly guide for the adapter boards.

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.

You might also be interested in