Sierra Wireless EM7565 LTE CAT-12 M.2
Supplier number: 1103520
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
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.
- UMTS Bands
- B1 (2100)
B2 (1900)
B19 (800)
B8 (900)
B4 (AWS)
B5 (850)
B6 (800)
B9 (1700)
- MIMO (Multiple-Input Multiple-Output)
- Yes
- 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)
- Manufacturer
- Sierra Wireless
- LTE Region
- Europe
North America
Asia
Australia
South America
Japan
Africa
- Module KEY
- B
- FOTA Firmware Updates
- Yes
- Form Factor
- M.2 3042
- Technology
- LTE - cat 12
- Antenna Interface
- IPEX MHF-4
- GPS
- Yes
- GNSS technology
- GPS
GLONASS
BeiDou
Galileo
- Max DL Speed
- 600 Mbps
- Max UL Speed
- 150 Mbps
- Chipset
- Qualcomm
MDM9x50
- Operating Temperature Range
- -30 °C – 70 °C
- Driver Support
- Linux
Android
Windows
Windows 8
Windows 8.1
Windows 10
- Interface
- USB 2.0
USB 3.0
SIM card
- Voice Call Support
- No
- GNSS antenna support
- Passive
Active
- SIM interface
- Through M.2 connector
Dual SIM interface
- GPIO
- Yes
- Carrier Certification
- AT&T
- 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
- FCC
GCF
NCC
PTCRB
CE RED
- Size
- 42 x 30 x 2.3 mm
- 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.
- Uploaded at
- 2015-12-10 15:03:51
- Last updated
- 2018-12-03 10:16:14
- Version
- 20170901
- Related products
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
- Sierra Wireless EM7305
- Sierra Wireless EM7355
- Sierra Wireless EM7430 LTE Cat 6
- Sierra Wireless EM7455 LTE Cat 6
Hardware guide and product specifications for the Sierra Wireless EM7565 cellular M.2 Key B module.
- Uploaded at
- 2017-11-09 10:26:15
- Last updated
- 2019-07-16 13:35:31
- Version
- 41110788 r10
- 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.
- 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 and protected AT commands available for Sierra Wireless AirPrime® EM75xx - EM74x1 - MC74x1 Series intelligent embedded modules.
- Uploaded at
- 2018-04-03 16:50:50
- Last updated
- 2020-09-29 13:48:40
- Version
- R3
- Related products
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless MC7431 Japan
- Sierra Wireless EM7431 Japan
- Sierra Wireless MC7421 EMEA/APAC
- Sierra Wireless EM7421 EMEA/APAC
- Sierra Wireless MC7411 NAM
- Sierra Wireless EM7411 NAM
This guide describes the USB interface mapping in host system for the Sierra Wireless EM75** series cellular modules
- Uploaded at
- 2019-06-10 09:12:02
- Last updated
- 2019-06-10 09:12:02
- Version
- 41113322 R1
- Related products
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
This technical note describes the thermal mitigation for Sierra Wireless AirPrime EM75 series.
- Uploaded at
- 2019-07-16 13:47:45
- Last updated
- 2020-05-12 09:59:29
- Version
- 41112528 r2
- Related products
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
Antenna Basics Guide for Sierra Wireless AirPrime Products IoT Applications
- Uploaded at
- 2019-11-11 08:44:37
- Last updated
- 2019-11-11 08:44:37
- Version
- Rev. 1.1
- Related products
- 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 MC9090RD
- Sierra Wireless EM7430 LTE Cat 6
- Sierra Wireless HL8518
- Sierra Wireless HL8528
- Sierra Wireless HL8548
- Sierra Wireless HL8548-G
- Sierra Wireless WP7502
- Sierra Wireless WP8548
- Sierra Wireless EM7565 LTE CAT-12
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
- Sierra Wireless WP7702 LTE CAT-M/NB-IoT LGA
- Sierra Wireless MC-WP7610 LTE CAT-4 mPCIe
- Sierra Wireless MC7431 Japan
- Sierra Wireless EM7431 Japan
- Sierra Wireless MC7421 EMEA/APAC
- Sierra Wireless EM7421 EMEA/APAC
- Sierra Wireless MC7411 NAM
- Sierra Wireless EM7411 NAM
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.
- 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
This guide describes the process of acquiring regulatory and operator required certificates in North America
- Uploaded at
- 2018-01-12 14:33:28
- Last updated
- 2018-12-03 10:15:54
- Version
- 2174182 - Rev1.0
- Related products
- 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 HL8518
- Sierra Wireless HL8528
- Sierra Wireless HL8548
- Sierra Wireless HL8548-G
- Sierra Wireless WP7502
- Sierra Wireless EM7565 LTE CAT-12
- Sierra Wireless WP8548
- Sierra Wireless EM7511 LTE CAT-12
EU Certificate for EM7565
- Uploaded at
- 2019-09-19 13:58:10
- Last updated
- 2019-09-19 13:58:10
- Related products
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
IC Certificate for EM7565
- Uploaded at
- 2019-09-19 14:01:06
- Last updated
- 2019-09-19 14:01:06
- Related products
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
Reach Letter for Sierra Wireless AirPrime products from March 2019
- Uploaded at
- 2019-09-19 12:05:43
- Last updated
- 2019-09-19 12:05:43
- Related products
- Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
- Sierra Wireless EM7430 LTE Cat 6
- Sierra Wireless MC7430 mPCIe
- Sierra Wireless EM7455 LTE Cat 6
- Sierra Wireless MC7455 LTE Cat 6
- Sierra Wireless MC7304
NCC Certificate for EM7565
- Uploaded at
- 2019-09-19 13:56:37
- Last updated
- 2019-09-19 13:56:37
- Related products
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
RohS Declaration of Conformity Document for Sierra Wireless EM7565
- 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
- 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 for the Sierra Wireless AirPrime EM/MC series cellular modules.
- Uploaded at
- 2020-09-29 14:07:07
- Last updated
- 2020-09-29 14:07:07
- Version
- Build 5087
- Requirements
- Microsoft Windows 10, Windows 8 or Windows 7 desktop systems
- Related products
- Sierra Wireless MC7431 Japan
- Sierra Wireless EM7431 Japan
- Sierra Wireless MC7421 EMEA/APAC
- Sierra Wireless EM7421 EMEA/APAC
- Sierra Wireless MC7411 NAM
- Sierra Wireless EM7411 NAM
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
- Sierra Wireless EM7430 LTE Cat 6
- Sierra Wireless MC7430 mPCIe
- Sierra Wireless EM7455 LTE Cat 6
- Sierra Wireless MC7455 LTE Cat 6
Microsoft Windows desktop driver installer application for Sierra Wireless AirPrime EM/MC series.
- Uploaded at
- 2018-07-11 16:05:09
- Last updated
- 2018-12-06 09:10:36
- Version
- V.4836
- Requirements
- Microsoft Windows desktop 7, 8, 8.1 and 10
- Related products
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless EM7565 LTE CAT-12
- 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 MC-WP7607 LTE CAT-4 mPCIe
- Sierra Wireless WP7502
This zip archive contains the Sierra Wireless Linux QMI SDK files:
Linux QMI SDK Full Version
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
- Uploaded at
- 2017-02-20 10:14:45
- Last updated
- 2020-09-28 16:25:31
- Version
- V.04.00.26
- Requirements
-
Usage of Sierra Wireless GobiNet and GobiSerial drivers.
Compatible with kernel versions 2.6.32 to 5.6.
Processors supported: x86, ARM, PPC, MIPS.
Sierra Wireless devices supported:
EM/MC74xx
EM75xx
EM/MC73xx
WP76xx
WP7702 - Related products
- Sierra Wireless WP7702 LTE CAT-M/NB-IoT LGA
- Sierra Wireless MC-WP7610 LTE CAT-4 mPCIe
- Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
- 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
- Sierra Wireless MC7431 Japan
- Sierra Wireless EM7431 Japan
- Sierra Wireless MC7421 EMEA/APAC
- Sierra Wireless EM7421 EMEA/APAC
- Sierra Wireless MC7411 NAM
- Sierra Wireless EM7411 NAM
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
Sierra Linux QMI drivers
- Uploaded at
- 2016-11-15 15:15:48
- Last updated
- 2020-09-28 16:18:34
- Version
- S2.42 N2.63
- Requirements
- Linux kernel version between 2.6.32 and 5.6
- Related products
- Sierra Wireless EM7411 NAM
- Sierra Wireless MC7411 NAM
- Sierra Wireless EM7421 EMEA/APAC
- Sierra Wireless MC7421 EMEA/APAC
- Sierra Wireless EM7431 Japan
- Sierra Wireless MC7431 Japan
- 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 MC7350
- Sierra Wireless EM7305
- Sierra Wireless EM7430 LTE Cat 6
- Sierra Wireless MC7455 LTE Cat 6
- Sierra Wireless EM7355
- Sierra Wireless MC7430 mPCIe
- Sierra Wireless EM7455 LTE Cat 6
- Sierra Wireless EM7511 LTE CAT-12
- Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
- Sierra Wireless MC-WP7610 LTE CAT-4 mPCIe
This archive contains the Sierra Wireless Android RIL library with related manuals and release notes.
- 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
This executable file install the Windows drivers for Sierra Wireless EM/MC Series cellular modules
- Uploaded at
- 2017-10-27 18:06:09
- Last updated
- 2017-11-29 14:24:18
- Version
- V.4773
- Requirements
- Microsoft Windows 7 / Windows 8 / Windows 10 operating systems
- Related products
- 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 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 and changes.
- Uploaded at
- 2019-11-22 14:18:30
- Last updated
- 2019-11-22 14:18:31
- Version
- SWI9X50C_01.11.00.00_GENERIC_002.023_000
- Requirements
-
Sierra Wireless Windows drivers
Sierra Wireless Linux Gobinet 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 based platforms. Please relate to the release notes prior to update regarding update instructions.
- Uploaded at
- 2019-07-16 14:09:17
- Last updated
- 2019-07-16 14:10:12
- Version
- SWI9X50C_01.09.04.00_GENERIC_002.019_000
- Requirements
-
Sierra Wireless Windows drivers
Sierra Wireless Linux Gobinet 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 Sprint 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 and changes.
- Uploaded at
- 2020-03-18 09:43:58
- Last updated
- 2020-03-18 09:44:26
- Version
- SWI9X50C_01.08.04.00_SPRINT_000.001_001
- Requirements
-
Sierra Wireless Windows drivers
Sierra Wireless Linux Gobinet 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 Telstra 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 and changes.
- Uploaded at
- 2019-11-22 14:21:00
- Last updated
- 2019-11-22 14:21:13
- Version
- SWI9X50C_01.11.00.00_TELSTRA_002.007_000
- Requirements
-
Sierra Wireless Windows drivers
Sierra Wireless Linux Gobinet 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 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.
- Uploaded at
- 2018-11-09 10:06:46
- Last updated
- 2019-07-16 14:37:27
- 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.
- 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, CAT-12, M.2 CBRS Enabled
- Sierra Wireless EM7565 LTE CAT-12
This application note describes the requirement for configuring RF band mask correctly when using the Generic firmware 01.08.04.00 002.012_000 (Generic PRI) with US Cellular network operator on the Sierra Wireless EM75 series modules.
- Uploaded at
- 2019-07-16 15:11:34
- Last updated
- 2019-07-16 15:11:34
- Version
- v1.0
- Requirements
-
Generic firmware 01.08.04.00 002.012_000
US Cellular network operator - Related products
- Sierra Wireless EM7511 LTE CAT-12
- 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 Softbank network operator 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.
- Uploaded at
- 2019-07-16 14:42:15
- Last updated
- 2019-07-16 14:42:15
- Version
- SWI9X50C_01.09.04.00_00_SOFTBANK_002.017_000
- Requirements
-
Sierra Wireless Windows drivers
Sierra Wireless Linux Gobinet 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 Docomo network operator 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.
- Uploaded at
- 2019-07-16 14:31:42
- Last updated
- 2019-07-16 14:31:42
- Version
- SWI9X50C_01.09.04.00_00_DOCOMO_002.015_000
- Requirements
-
Sierra Wireless Windows drivers
Sierra Wireless Linux Gobinet 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 based platforms. Please relate to the release notes prior to update regarding update instructions.
- Uploaded at
- 2018-11-09 10:11:21
- Last updated
- 2019-07-16 14:38:28
- 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 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.
- 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 firmware binaries and config files for the Sierra Wireless EM7565 module.
- Uploaded at
- 2018-03-19 16:14:19
- Last updated
- 2019-07-16 14:12:17
- 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
This archive contains the Sierra Wireless EM7565 Windows firmware update packages V.01.05.01.00
- Uploaded at
- 2018-03-02 17:22:07
- Last updated
- 2019-07-16 14:11:56
- Version
- 01.05.01.00
- Requirements
-
Microsoft Windows 8+
- Related products
- Sierra Wireless EM7565 LTE CAT-12
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/
Related products
Sierra Wireless MC7455 LTE Cat 6Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless EM7565 LTE CAT-12
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
Sierra Wireless EM7411 NAM
Sierra Wireless MC7411 NAM
Sierra Wireless EM7421 EMEA/APAC
Sierra Wireless MC7421 EMEA/APAC
Sierra Wireless EM7431 Japan
Sierra Wireless MC7431 Japan
Sierra Wireless MC-WP7610 LTE CAT-4 mPCIe
Question
How-to change the cellular modulesUSB composition mode to Mobile Broadband Interface Model (MBIM) used by Windows 8 and 10 systems for controlling and establishing data connectivity through the built-in connection manager in Windows?
Solution
This is done by sending a set of AT commands to the cellular modules Modem or AT serial interface found in Windows Device Manager. Please see list below for associated AT commands.
(For additional details, refer to the product specific software, ports, and AT commands guides found on the Techship product web pages under technical documentation tab).
After the AT commands have been received by the module and has restarted, the USB interface endpoint composition should have changed to include MBIM interface as well.
You can find the correct Serial COM port number by checking Windows Device Manager, under the Modems drop down -> (right click and see properties for selected COM port info) or under the Ports (COM & LPT) drop down.
Vendor specific commands to use:
Sierra Wireless EM74xx, MC74xx series module:
AT!ENTERCND=”A710”
AT!USBCOMP=1,1,100D
AT!RESET
(See test command AT!USBCOMP=? for full usage description)
Sierra Wireless EM75xx series module:
AT!ENTERCND=”A710”
AT!USBCOMP=1,3,100D
AT!RESET
(See test command AT!USBCOMP=? for full usage description)
Sierra Wireless EM73xx, MC73xx series module:
AT!ENTERCND=”A710”
AT!UDUSBCOMP=8
AT!RESET
Simcom SIM7100, SIM7500 and SIM7600 series modules:
AT+CUSBPIDSWITCH=9003,1,1
AT+CRESET
ZTE Welink ME3630 series:
AT+ZSWITCH=8
AT+ZRST
Telit LE910C1 and LE910C4 series:
AT#USBCFG=2
AT#REBOOT
Telit LM940 and LM940A11:
AT#USBCFG=2
AT#REBOOT
Telit LM960 and LM960A18:
AT#USBCFG=2
AT#REBOOT
Telit LE910 V2 series:
AT#USBCFG=3
AT#REBOOT
On Huawei and Telit LN94x series modules the USB mode changing is done automatically by the modules Windows drivers based on current Windows version.
Please be aware that some USB mode configurations do not include any serial interfaces, making it impossible to revert the changes using AT commands.
Related products
Sierra Wireless MC7304Sierra Wireless MC7354
Sierra Wireless MC7350
Sierra Wireless EM7305
Sierra Wireless EM7355
Huawei MU709s-2 LGA
Huawei MU709s-2 mPCIe
Huawei ME909s-821 mPCIe
Huawei ME909s-821 LGA
Huawei ME909s-120 mPCIe EU
Huawei ME909s-120 LGA EU
Huawei MU709s-6 mPCIe
SimCom SIM7100E LTE SMT EU
SimCom SM7100A LTE SMT US
SimCom SIM7100E LTE mPCIe EU
SimCom SIM7100A LTE mPCIe US
SimCom SIM7100C LTE mPCIe China
Huawei ME906s-158 M.2 EU
Huawei ME909s-120 LGA dev.kit
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
SimCom SIM7100E LTE mPCIe SIM
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6
ZTE ME3610 E1A LCC
Techship Starter kit Huawei ME909s
SIMCom SIM7500A LTE SMT US
SIMCom SIM7500E LTE SMT EU
Huawei MU709s-2 LGA TTS
Welink ME3630 E1C LCC EU
Welink ME3630 E1C mPCIe EU
SIMCom SIM7500E LTE mPCIe EU
Welink ME3630 U1A LCC (US)
Welink ME3630 U1A mPCIe (US)
SIMCom SIM7500SA LTE mPCIe Audio
Telit LM940A11 LTE CAT-11, GPS, mPCIe
Telit LE910-EU V2 LTE CAT-4, mPCIe
Telit LE910-SV V2 LTE CAT-4, Verizon, mPCIe
Telit LE910-NA V2 LTE CAT-4, AT T, TM, mPCIe
Telit LE910-AU V2 LTE CAT-4, Telstra, mPCIe
Telit LE910-NA1 LTE CAT-1 LGA
Telit LE910-EU1 LTE CAT-1 LGA
Telit LE910-SV1 LTE CAT-1 LGA
Telit LE910-EU V2 LTE CAT-4 LGA
Telit LE910-NA V2 LTE CAT-4 LGA
Telit LE910D1-E1 LTE CAT-1 LGA
SIMCom SIM7600E-H LTE SMT EU
SIMCom SIM7600E-H LTE CAT-4 mPCIe EU
Sierra Wireless EM7565 LTE CAT-12
Welink ME3630 C1C mPCIe CN
SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
SIMCom SIM7600A-H LTE CAT-4 mPCIe Audio
Welink ME3630 E1C M.2 EU
Welink ME3630 E2C CAT-1 M.2 EU
Telit LE910-NA V2 LTE CAT-4, S.SKU, mPCIe
SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SIMCom SIM7600A-H LTE CAT-4 mPCIe US
SIMCom SIM7600V-H LTE CAT-4 mPCIe Audio Verizon
SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SIMCom SIM7600E LTE CAT-1 mPCIe
SIMCom SIM7600SA LTE CAT-1 mPCIe
SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
Telit LM960 LTE CAT-18, GPS, mPCIe
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
SIMCom SIM7600A-H LTE CAT-4 mPCIe-SIM
Telit LE910C4-NF LTE CAT-4 mPCIe
Telit LE910-NA V2 LTE CAT-4, S.SKU LGA
Telit LE910B1-NA S.SKU
Telit LE910C1-NS LTE CAT-1 Sprint mPCIe
Telit LE910C1-NA LTE CAT-1 AT&T LGA
Telit LE910C1-NS LTE CAT-1 Sprint LGA
SIMCom SIM7600G-H LTE CAT-4 mPCIe
Telit LE910-NA1 S.SKU
Telit LE910-JN1
Telit LE910C1-AP
Telit LE910C1-EU
Telit LE910B1-NA
Telit LE910B1-SA
Telit LE910-AU V2
Telit LE910-SV V2
Telit LE910B4-NA
Telit LE910C4-NF
Telit LE910-PCI (LE910-SV1)
Telit LE910-PCI (LE910-EU1)
Telit LE910-PCI (LE910-JN1)
Telit LE910-PCI (LE910-NA1)
Telit LE910-PCI (LE910C1-AP)
Telit LE910-PCI (LE910C1-NA)
Telit LE910C1-EU LTE CAT-1 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe SIM
Telit LE910C1-NF
Telit LM940A11, HW Rev. 2, LTE CAT-11, GPS, mPCIe
Telit LE910C4-NF LTE CAT-4 mPCIe SIM
Telit LM960A18 LTE CAT-18 mPCIe
Telit LE910C1-EU LTE CAT-1 mPCIe SIM
Telit LE910C1-AP LTE CAT-1 mPCIe SIM
Telit LE910C1-NF LTE CAT-1 mPCIe
Telit LE910C4-AP LTE CAT-4 mPCIe SIM
Telit LE910C4-CN LTE CAT-4 mPCIe
Gosuncn GM500 U1A mPCIe (US)
SIMCom SIM7600G-H R2 mPCIe
SIMCom SIM7600NA-H mPCIe
Question
What Linux kernel modules and configs are commonly used for communicating with cellular modules over their USB interface?
Solution
Most cellular modules can be supported in Linux by using som of the in-kernel drivers. The physical data interface to the host Linux system is usually done over USB which enumerates a set of different endpoints/interfaces. A set of serial interfaces for Modem/PPP, AT commands, NMEA location data and chipset debug information are almost always available in all configurations.
In addition some type of network endpoint/interface are also available and exposed. This can vary between manufacturers and chipset vendors and can also commonly be configurable by using USB configuration mode switching or through vendor specific AT commands.
Recommended kernel configurations to enable are listed bellow. Many cellular modules base their Linux support on these modules and drivers. Once included in the kernel build, the USB interfaces will be detected and bound correctly out-of-the-box or after applying source code patches to the driver modules.
Configs for USB serial drivers:
CONFIG_USB_SERIAL
CONFIG_USB_SERIAL_GENERIC
CONFIG_USB_SERIAL_WWAN
CONFIG_USB_SERIAL_OPTION
CONFIG_USB_SERIAL_QUALCOMM
CONFIG_USB_ACM
Configs for Modem/PPP support:
CONFIG_PPP
CONFIG_PPP_BSDCOMP
CONFIG_PPP_DEFLATE
CONFIG_PPP_FILTER
CONFIG_PPP_MPPE
CONFIG_PPP_MULTILINK
CONFIG_PPPOE
CONFIG_PPP_ASYNC
CONFIG_PPP_SYNC_TTY
Configs for USB network drivers:
CONFIG_USB_USBNET
CONFIG_USB_NET_QMI_WWAN
CONFIG_USB_NET_CDCETHER
CONFIG_USB_NET_RNDIS_HOST
CONFIG_USB_NET_CDC_NCM
CONFIG_USB_NET_HUAWEI_CDC_NCM
CONFIG_USB_NET_CDC_MBIM
Please relate to the Techship product specific web pages for vendor specific Linux integration guides.
Below is a selection of kernel commits relating to cellular module support in Linux kernels:
qmi_wwan: Add support for Fibocom NL678 series
qmi_wwan: Added support for Telit LN940 series
qmi_wwan: Added support for Fibocom NL668 series
USB: serial: option: add support for GosunCn ME3630 RNDIS mode
USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
USB: serial: option: add Simcom SIM7500/SIM7600 (MBIM mode)
USB: serial: option: add Fibocom NL678 series
USB: serial: option: add Telit LN940 series
USB: serial: option: add Fibocom NL668 series
USB: serial: option: add GosunCn ZTE WeLink ME3630
qmi_wwan: apply SET_DTR quirk to the SIMCOM shared device ID
If you use any of the listed cellular modules, drivers and specified USB modes in the commits above, ensure that your kernel version already include the patch or apply it to your build.
Related products
Huawei ME909u-521 - EU/ASIAHuawei ME909u-523D - US - AT&T
Huawei ME909u-521 Mini PCI Express - EU/ASIA
Huawei ME909u-523D Mini PCI Express - US - AT&T
Sierra Wireless MC7710
Huawei ME909u-521 developer kit
Sierra Wireless MC7750
Sierra Wireless MC7700
Sierra Wireless MC7304
Sierra Wireless MC7354
Sierra Wireless MC7350
Sierra Wireless EM7305
Sierra Wireless EM7355
Huawei MU709s-2 LGA
Huawei MU709s-2 devkit
Huawei MS2131i-8 USB-stick
Huawei MU709s-2 mPCIe
Huawei ME909s-821 mPCIe
Huawei ME909s-821 LGA
Huawei ME909s-120 mPCIe EU
Huawei ME909s-120 LGA EU
Huawei MU709s-6 mPCIe
SimCom SIM5360E HSPA+ mPCie EU
SimCom SIM7100E LTE SMT EU
SimCom SIM7100E LTE mPCIe EU
SimCom SIM7100A LTE mPCIe US
SimCom SIM7100C LTE mPCIe China
SimCom SIM7230 LTE mPCIe EU
Huawei ME906s-158 M.2 EU
Huawei ME909s-120 LGA dev.kit
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
SimCom SIM7100E LTE mPCIe SIM
SimCom SIM5360E HSPA+ mPCie Audio/GPS
Sierra Wireless MC7430 mPCIe
SimCom SIM5360E-mPCIe SIM
Sierra Wireless EM7430 LTE Cat 6
Techship Starter kit Huawei ME909s
SIMCom SIM7500A LTE SMT US
SIMCom SIM5300E HSPA SMT
SIMCom SIM7500A Development kit
Sierra Wireless WP7502
SIMCom SIM7500E LTE SMT EU
SIMCom SIM7500E Development Kit
Huawei MU709s-2 LGA TTS
Welink ME3630 E1C LCC EU
Welink ME3630 E1C mPCIe EU
SIMCom SIM7500E LTE mPCIe EU
Welink ME3630 U1A LCC (US)
Welink ME3630 U1A mPCIe (US)
SIMCom SIM5320A mPCIe
SIMCom SIM7500SA LTE mPCIe Audio
SIMCom SIM7000E CAT-M/NB-IoT SMT
Telit HE910-G HSPA+, GPS, mPCIe
Telit HE910-G-SIM HSPA+, GPS, miniPCIe, SIM card holder
Telit HE910-D HSPA+, miniPCIe, Global
Telit HE910-D-SIM HSPA+, miniPCIe, SIM card holder
Telit LM940A11 LTE CAT-11, GPS, mPCIe
Telit LE910-EU V2 LTE CAT-4, mPCIe
Telit LE910-SV V2 LTE CAT-4, Verizon, mPCIe
Telit LE910-NA V2 LTE CAT-4, AT T, TM, mPCIe
Telit LE910-AU V2 LTE CAT-4, Telstra, mPCIe
Telit HE910-GL SIM UMTS, miniPCIe, SIM card holder
Telit HE910-G (Voice) HSPA+ LGA
Telit HE910-DG HSPA+ LGA
Telit HE910-EUD HSPA LGA
Telit LE910-NA1 LTE CAT-1 LGA
Telit LE910-EU1 LTE CAT-1 LGA
Telit LE910-SV1 LTE CAT-1 LGA
Telit LE910-EU V2 LTE CAT-4 LGA
Telit LE910-NA V2 LTE CAT-4 LGA
Telit LE910D1-E1 LTE CAT-1 LGA
Telit LN940 A11 LTE CAT-11 M.2
Telit LN940 A9 LTE CAT-9 M.2
SIMCom SIM7000E Development Kit
Huawei MS2372h-153 LTE USB Dongle EU
SIMCom SIM7600E-H LTE SMT EU
SIMCom SIM7600E-H LTE CAT-4 mPCIe EU
Sierra Wireless EM7565 LTE CAT-12
Welink ME3630 C1C mPCIe CN
SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
Huawei MS2372h-517 LTE USB Dongle US
SIMCom SIM7600A-H LTE CAT-4 mPCIe Audio
Huawei MS2372h-607 LTE USB Dongle Asia
Welink ME3630 E1C M.2 EU
Welink ME3630 E2C CAT-1 M.2 EU
Telit LE910-NA V2 LTE CAT-4, S.SKU, mPCIe
SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SIMCom SIM7600A-H LTE CAT-4 mPCIe US
SIMCom SIM7600V-H LTE CAT-4 mPCIe Audio Verizon
Telit LE910-NA1 LTE CAT-1 Developer Kit
Telit LE910-EU1 LTE CAT-1 Developer Kit
Telit LE910-SV1 LTE CAT-1 Developer Kit
SIMCom SIM7020E-SUB KIT Developer kit
SIMCom SIM7000G
SIMCom SIM7020E NB-IoT SMT
SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SIMCom SIM7600E LTE CAT-1 mPCIe
SIMCom SIM7600SA LTE CAT-1 mPCIe
SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
Telit LM960 LTE CAT-18, GPS, mPCIe
Telit LN941 LTE CAT-6, M.2
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
SIMCom SIM7000G Development Kit
SIMCom SIM7000E CAT-M/NB-IoT PCIE
SIMCom SIM7000G CAT-M/NB-IoT/GSM miniPCIe
SIMCom SIM7600E Development Kit
SIMCom SIM7600A-H LTE CAT-4 mPCIe-SIM
SIMCom SIM7020G-SUB KIT
Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
Telit LE910C4-NF LTE CAT-4 mPCIe
Telit LE910-NA V2 LTE CAT-4, S.SKU LGA
Telit LE910B1-NA S.SKU
Telit LE910C1-NS LTE CAT-1 Sprint mPCIe
Telit LE910-SVL LTE CAT-1
Telit HE910-GL HSPA+ LGA
SIMCom SIM7000A CAT-M/NB-IoT SMT Verizon
SIMCom SIM7000A CAT-M/NB-IoT SMT AT&T
SIMCom SIM7906E LTE CAT-6 M.2
SIMCom SIM7906E LTE CAT-6 mPCIe
SIMCom SIM7000A CAT-M/NB-IoT mPCIe
Telit HE910-NAD HSPA+ LGA
Telit LE910-SVG LTE CAT-3 LGA
Telit HE910-NAR HSPA LGA
Telit HE910-D HSPA+ LGA
Telit LE910C1-NA LTE CAT-1 AT&T LGA
Telit LE910C1-NS LTE CAT-1 Sprint LGA
Telit LE910-NAG LTE CAT-3 AT&T LGA
Telit LE910-SVG LTE CAT-3 mPCIe
Telit LE910-NVG LTE CAT-3 LGA
SIMCom SIM7600G-H LTE CAT-4 mPCIe
Telit LE910-NA1 S.SKU
Telit LE910-JN1
Telit LE910C1-AP
Telit LE910C1-EU
Telit LE910B1-NA
Telit LE910B1-SA
Telit LE910-AU V2
Telit LE910-SV V2
Telit LE910B4-NA
Telit LE910C4-NF
Telit LE910-PCI (LE910-SV1)
Telit LE910-PCI (LE910-EU1)
Telit LE910-PCI (LE910-JN1)
Telit LE910-PCI (LE910-NA1)
Telit LE910-PCI (LE910C1-AP)
Telit LE910-PCI (LE910C1-NA)
Telit LE910C1-EU LTE CAT-1 mPCIe
Telit LE910-SV V2 (Reel)
Telit LE910C4-EU LTE CAT-4 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe SIM
GosuncnWelink GM500 U1A CAT-4 M.2
Telit LE910C1-NF
SIMCom SIM7070E CAT-M/NB2
SIMCom SIM7070E Development Kit
Telit LM940A11, HW Rev. 2, LTE CAT-11, GPS, mPCIe
SIMCom SIM7070E mPCIe
Telit LE910C4-NF LTE CAT-4 mPCIe SIM
SIMCom SIM7912G LTE CAT-12 M.2
Sierra Wireless WP7702 LTE CAT-M/NB-IoT LGA
Telit LM960A18 LTE CAT-18 mPCIe
Gosuncn GM500 U1A mPCIe (US)
SIMCom SIM7600G-H R2 mPCIe
SIMCom SIM7600NA-H mPCIe
Question
How-to guide: How can we control, configure and establish a simple data connection for a cellular module in Linux systems using the open source ModemManager tool for modem control and connection management.
Solution
ModemManager is a open source tool for Linux that can be used to communicate with cellular devices for configuration, status check, connection triggering etc. It is capable of communicate over several types of device control channels such as QMI/RMNET, MBIM, MODEM / AT command etc.
It is hosted by the Freedesktop.org community and driven by Aleksander Morgado and other contributors, please visit https://www.freedesktop.org/wiki/Software/ModemManager/ for latest information, source code, API reference manuals, debugging tips, contribution, mailing list etc.
Keep in mind that ModemManager is not directly developed or driven by cellular device vendors and the compatibility cannot be guaranteed for the specific device you aim to use. Some vendors contribute with code to make their devices fully compatible, while others don't. However many cellular devices can be set to expose standardized types of USB network interface and control channel such as MBIM interface by USB-IF or the Qualcomm proprietary interface QMI that ModemManager will try to identify, and often manage to work successfully with.
Before continuing with ModemManager, a good thing to ensure is that you have common Linux driver modules available in your kernel build.
You can compare your own systems kernel config with the ones listed in the following FAQ:
Common Linux kernel modules and configs necessary for communicating with cellular modules over USB interface
Selections of these are commonly used by cellular devices and need to be available in order to have device drivers correctly loaded when devices are detected.
Start by installing ModemManager and its dependencies to your Linux system.
You can build it from source code release tarball found at freedesktop.org (install instructions included in the archive)
If you have a package manager in your Linux distribution, it can usually be installed through them also.
E.g. on Ubuntu using apt to install it and related dependencies:
apt install modemmanager libmbim-utils libqmi-utils
Keep in mind that Linux distributions sometimes rely on fairly old releases in their repositories and the development of ModemManager, libqmi and libmbim are on-going continuously. So is also the development of the cellular devices when the cellular technologies evolve. It is therefore recommended that you have a fairly recent version of ModemManager, libqmi and libmbim running in your system as well as when it comes to kernel version since the driver modules sometimes acquire patch fixes to be compatible with new chipset features etc.
Check Freedesktop.org pages for details on the latest ModemManager, NetworkManager, Libqmi and Libmbim releases.
Once you've installed ModemManager and rebooted your system, the service daemon should be running already in background.
Mmcli is the related command line interface tool which can be used to interact with ModemManager daemon through command line commands.
Check the version by command:
mmcli -V
<< mmcli 1.13.0
<< Copyright (2011 - 2020) Aleksander Morgado
<< License GPLv2+: GNU GPL version 2 or later
<< This is free software: you are free to change and redistribute it.
<< There is NO WARRANTY, to the extent permitted by law.
Print general mmcli help message:
mmcli --help
ModemManager normally listen, probes and detects cellular devices automatically when operating correctly but a forced scan can be triggered with command:
mmcli --scan-modems
<< successfully requested to scan devices
To list detected cellular devices use command:
mmcli --list-modems
<< /org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless, Incorporated] MC7455
Here ModemManager have detected a Sierra Wireless cellular device and it has here been given the the identifier number 0 by ModemManager.
To acquire more device information and status use the --modem command and identifier value.
mmcli --modem=0
<< -----------------------------
<< General | dbus path: /org/freedesktop/ModemManager1/Modem/0
<< | device id: 3a2f5fad8e91dbf417694f23165017c1f8a6e061
<< -----------------------------
<< Hardware | manufacturer: Sierra Wireless, Incorporated
<< | model: MC7455
<< | firmware revision: SWI9X30C_02.32.11.00 r8042 CARMD-EV-FRMWR2 2019/05/15 21:52:20
<< | carrier config: default
<< | h/w revision: 1.0
<< | supported: gsm-umts, lte
<< | current: gsm-umts, lte
<< | equipment id: 359072066171840
<< -----------------------------
<< System | device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-2
<< | drivers: qcserial, qmi_wwan
<< | plugin: sierra
<< | primary port: cdc-wdm0
<< | ports: cdc-wdm0 (qmi), wwan1 (net), ttyUSB2 (at), wwan0 (net),
<< | cdc-wdm1 (qmi), ttyUSB1 (gps), ttyUSB0 (qcdm)
<< -----------------------------
<< Status | lock: sim-pin
<< | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (0), sim-puk2 (10)
<< | state: locked
<< | power state: on
<< | signal quality: 0% (cached)
<< -----------------------------
<< Modes | supported: allowed: 3g; preferred: none
<< | allowed: 4g; preferred: none
<< | allowed: 3g, 4g; preferred: 4g
<< | allowed: 3g, 4g; preferred: 3g
<< | current: allowed: 3g, 4g; preferred: 4g
<< -----------------------------
<< Bands | supported: utran-1, utran-3, utran-4, utran-5, utran-8, utran-2,
<< | eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8,
<< | eutran-12, eutran-13, eutran-20, eutran-25, eutran-26, eutran-29,
<< | eutran-30, eutran-41
<< | current: utran-1, utran-3, utran-4, utran-5, utran-8, utran-2,
<< | eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8,
<< | eutran-12, eutran-13, eutran-20, eutran-25, eutran-26, eutran-29,
<< | eutran-30, eutran-41
<< -----------------------------
<< IP | supported: ipv4, ipv6, ipv4v6
<< -----------------------------
<< SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0
A detailed summary of device status, configs and system drivers, paths and IDs are returned.
Currently the device status indicates that inserted SIM card is PIN locked, so a unlock by --pin command is necessary:
mmcli --modem=0 --sim=0 --pin=****
<< successfully sent PIN code to the SIM
Now we can change device state to enabled using command:
mmcli --modem=0 --enable
<< successfully enabled the modem
if we're check device status again we can see that device:
mmcli --modem=0
…
<< --------------------------------
<< Status | lock: sim-puk2
<< | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (0), sim-puk2 (10)
<< | state: registered
<< | power state: on
<< | access tech: lte
<< | signal quality: 96% (recent)
…
<< 3GPP | imei: 359072066171840
<< | operator id: 24002
<< | operator name: 3
<< | registration: home
<< --------------------------------
<< 3GPP EPS | ue mode of operation: csps-2
<< --------------------------------
<< SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0
The status output shows that devices is registered in network using LTE technology with a good signal strength.
It is now time to activate the data connection with --simple-connect command.
ModemManager will tie the data bearer for our given subscription APN to the qmi_wwan network interface, typically named wwan0 (unless renamed by Linux distribution or user)
Fill in the details as below but for your modem number, subscription APN and the IP type it can work with (ipv4 / ipv6 ipv4v6)
mmcli -m 0 --simple-connect='apn=data.tre.se,ip-type=ipv4v6'
<< successfully connected the modem
if we check modem status again we can see that a bearer have been established.
mmcli --modem=0
…
<< --------------------------------
<< Bearer | dbus path: /org/freedesktop/ModemManager1/Bearer/0
…
The bearer have got identifier number 0 so we can request more details for it to acquire the IP details:
mmcli --modem=0 --bearer=0
<< ------------------------------------
<< General | dbus path: /org/freedesktop/ModemManager1/Bearer/0
<< | type: default
<< ------------------------------------
<< Status | connected: yes
<< | suspended: no
<< | interface: wwan1
<< | ip timeout: 20
<< ------------------------------------
<< Properties | apn: data.tre.se
<< | roaming: allowed
<< | ip type: ipv4v6
<< ------------------------------------
<< IPv4 configuration | method: static
<< | address: 2.68.206.100
<< | prefix: 29
<< | gateway: 2.68.206.101
<< | dns: 80.251.201.177, 80.251.201.178
<< | mtu: 1500
<< ------------------------------------
<< IPv6 configuration | method: static
<< | address: 2a02:aa1:1010:b6bb:6d12:d0dc:978e:3982
<< | prefix: 64
<< | gateway: 2a02:aa1:1010:b6bb:21ea:c721:62c3:9760
<< | dns: 2a02:aa0::55, 2a02:aa0::56
<< | mtu: 1500
<< ------------------------------------
<< Statistics | duration: 450
<< | bytes rx: 6693
<< | attempts: 1
<< | total-duration: 450
<< | total-bytes rx: 6693
From here we can see the IP details we've been assigned by the cellular network.
ModemManager does not assign IPv4 address details to the cellular modules network interface in Linux by itself.
When ModemManager is used in conjunction with NetworkManager and the cellular connection is managed by it, then the IPv4 address details will be collected by NetworkManager through ModemManager and automatically assigned to network interface when connection is established.
If the system does not implement NetworkManager, then the IP and routing configuration needs to be handled by user software/scripting.
Example:
Enable network interface in Linux:
ip link set wwan0 up
Set the IPv4 address acquired from bearer information above, the CIDR subnet mask can always be set to 32:
ip addr add 2.68.206.100/32 dev wwan0
Disable ARP:
ip link set dev wwan0 arp off
Set MTU value acquired from network:
ip link set dev wwan0 mtu 1500
Add a default or other type of route to the cellular network device (e.g. with a metric to set which route to prefer)
ip route add default dev wwan0 metric 200
Add the DNS servers reported by cellular network or use other public/desired ones.
DNS server addresses are handled in different ways depending on the Linux distribution and network manager used. Therefore please refer to related dist documentation for best practice to add / maintain DNS server addresses in your specific system.
sh -c "echo 'nameserver 80.251.201.177' >> /etc/resolv.conf"
sh -c "echo 'nameserver 80.251.201.178' >> /etc/resolv.conf"
We should now have a network interface passing data successfully, we can try it out by doing ping requests:
IPv4 data:
ping -4 -c 4 -I wwan0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 2.68.206.100 wwan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=50.8 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=48.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=24.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=44.8 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 23.979/42.115/50.840/10.694 ms
IPv6 data:
ping -6 -c 4 -I wwan0 2600::
PING 2600::(2600::) from 2a02:aa1:1010:b6bb:8962:7405:b81c:7627 wwan0: 56 data bytes
64 bytes from 2600::: icmp_seq=1 ttl=47 time=179 ms
64 bytes from 2600::: icmp_seq=2 ttl=47 time=176 ms
64 bytes from 2600::: icmp_seq=3 ttl=47 time=175 ms
64 bytes from 2600::: icmp_seq=4 ttl=47 time=177 ms
--- 2600:: ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 175.411/176.935/179.268/1.446 ms
Related products
Huawei ME909s-821 mPCIeHuawei ME909s-821 LGA
Huawei ME909s-120 mPCIe EU
Huawei ME909s-120 LGA EU
SimCom SIM7100E LTE SMT EU
SimCom SIM7100E LTE mPCIe EU
SimCom SIM7100A LTE mPCIe US
SimCom SIM7100C LTE mPCIe China
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
SimCom SIM7100E LTE mPCIe SIM
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6
SIMCom SIM7500A LTE SMT US
SIMCom SIM7500E LTE SMT EU
SIMCom SIM7500E LTE mPCIe EU
SIMCom SIM7500SA LTE mPCIe Audio
SIMCom SIM7000E CAT-M/NB-IoT SMT
Telit LM940A11 LTE CAT-11, GPS, mPCIe
SIMCom SIM7600E-H LTE SMT EU
SIMCom SIM7600E-H LTE CAT-4 mPCIe EU
Sierra Wireless EM7565 LTE CAT-12
SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
SIMCom SIM7600A-H LTE CAT-4 mPCIe Audio
SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SIMCom SIM7600A-H LTE CAT-4 mPCIe US
SIMCom SIM7600V-H LTE CAT-4 mPCIe Audio Verizon
SIMCom SIM7000G
SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SIMCom SIM7600E LTE CAT-1 mPCIe
SIMCom SIM7600SA LTE CAT-1 mPCIe
SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
Telit LM960 LTE CAT-18, GPS, mPCIe
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
SIMCom SIM7000E CAT-M/NB-IoT PCIE
SIMCom SIM7000G CAT-M/NB-IoT/GSM miniPCIe
SIMCom SIM7600A-H LTE CAT-4 mPCIe-SIM
Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
Telit LE910C4-NF LTE CAT-4 mPCIe
Telit LE910C1-NS LTE CAT-1 Sprint mPCIe
SIMCom SIM7000A CAT-M/NB-IoT SMT Verizon
SIMCom SIM7000A CAT-M/NB-IoT SMT AT&T
SIMCom SIM7906E LTE CAT-6 M.2
SIMCom SIM7906E LTE CAT-6 mPCIe
SIMCom SIM7000A CAT-M/NB-IoT mPCIe
Telit LE910C1-NA LTE CAT-1 AT&T LGA
Telit LE910C1-NS LTE CAT-1 Sprint LGA
SIMCom SIM7600G-H LTE CAT-4 mPCIe
Telit LE910C1-AP
Telit LE910C1-EU
Telit LE910C4-NF
Telit LE910-PCI (LE910C1-AP)
Telit LE910-PCI (LE910C1-NA)
Telit LE910C1-EU LTE CAT-1 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe SIM
Telit LE910C1-NF
Telit LM940A11, HW Rev. 2, LTE CAT-11, GPS, mPCIe
Telit LE910C4-NF LTE CAT-4 mPCIe SIM
SIMCom SIM7912G LTE CAT-12 M.2
Telit LM960A18 LTE CAT-18 mPCIe
Telit LE910C1-EU LTE CAT-1 mPCIe SIM
Telit LE910C1-AP LTE CAT-1 mPCIe SIM
Telit LE910C1-NF LTE CAT-1 mPCIe
Telit LE910C4-AP LTE CAT-4 mPCIe SIM
Telit LE910C4-CN LTE CAT-4 mPCIe
Huawei ME909s-120p V2 mPCIe
Huawei ME909s-120 V2 LGA
Sierra Wireless MC-WP7610 LTE CAT-4 mPCIe
SIMCom SIM7600G-H R2 mPCIe
Question
How to set up a simple data connection over Qualcomm QMI interface using libqmi and driver qmi_wwan in Linux?
Solution
Several cellular modules based on Qualcomm chipsets implements the Qualcomm MSM QMI RMNET Interface.
There is a open source Linux in-kernel driver supporting this interface called qmi_wwan. The helper library libqmi can be used to communicate with the cellular devices over the interface and do cellular module configurations to control and trigger the data connection over the cellular network.
Install the libqmi Linux library using e.g. your OS package manager like apt etc.
(Check out the official libqmi page here: https://www.freedesktop.org/wiki/Software/libqmi/)
Please be aware that libqmi is a 3rd party software not distributed by the chipset or module vendors. So full compatibility on all available commands should not be expected.
There are Qualcomm chipset standard QMI commands and in addition vendors specific custom QMI commands not supported by all manufacturers, but still available in libqmi. There are also new QMI commands not supported in older chipsets and vice versa, old QMI commands no longer supported in new chipset series.
Verify that you have the Linux in-kernel qmi_wwan driver installed and loaded for the cellular modules QMI interface endpoint over USB:
lsusb -t
Can look like this:
...
|__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=qmi_wwan, 480M
...
If the driver is not loaded correctly, please verify that the cellular module is set to expose QMI RMNET network interface endpoint in its configuration. How to do so can often be found in AT commands guides, Linux implementation guides and similar from the cellular module vendors.
Libqmi library include a command line tool qmicli that can be used in a more convenient way communicate directly with the module over QMI interface for testing, scripting and troubleshooting.
The qmicli help will output information about all commands available:
qmicli --help-all
The qmi_wwan network control interfaces for modules are usually named like cdc-wdm# under /dev/ path.
Use the attribute --device or -d to specify it for qmicli in your command execution:
qmicli --device=/dev/cdc-wdm0
qmicli -d /dev/cdc-wdm0
In order to ease usage of the QMI interface and handle parallell command requests, libqmi include a proxy function to handle it correctly on the QMI interface, To use it, make sure to have the the attribute present in the qmicli command:
-p
--device-open-proxy
Example commands on how to communicate
Request module manufacturer:
qmicli -p -d /dev/cdc-wdm0 --dms-get-manufacturer
Get module model:
qmicli -p -d /dev/cdc-wdm0 --dms-get-model
Get firmware version:
qmicli -p -d /dev/cdc-wdm0 --dms-get-revision
Get module IDs (IMEI etc.):
qmicli -p -d /dev/cdc-wdm0 --dms-get-ids
Get SIM card status:
qmicli -p -d /dev/cdc-wdm0 --uim-get-card-status
The script qmi-network can be used to establish a simple data connection, it will automatically try to verify the IP framing type match them correctly between qmi_wwan driver and module (Raw-IP vs. 802.3 IP framing).
Create a config file containing your network operator APN details and if needed, the username and password.
Save it e.g. in the default location /etc/qmi-network.conf
The parameter --profile=[PATH] can be used to define the path to config when executing qmi-network.
Example config file content: APN details and enabling of proxy usage.
Add the username and password lines if it is needed for your APN:
APN=my-network-operators-apn
APN_USER=my-apn-username
APN_PASS=my-apn-password
PROXY=yes
Once the APN information is saved, you can start the network connection with the command:
qmi-network /dev/cdc-wdm0 start
The name of the related network interface in the Linux system can be acquired with the command:
qmicli -p -d /dev/cdc-wdm0 --get-wwan-iface
Once you see "Network started successfully" message, you can send a DHCP request on the network interface.
Please note that not all DHCP clients in Linux can handle Raw-IP format but udhcpc support it.
udhcpc -q -f -i wwan0
The IP information from the cellular network can also be acquired and set manually to the network interface by the user or scripting, the correct address details can be acquired from the cellular module over QMI with command:
qmicli -p -d /dev/cdc-wdm0 --wds-get-current-settings
If the connection was successfully set up and established, you now have a data connection. Ping request to a remote server using the cellular network interface can prove this:
ping -I wwan0 8.8.8.8
The ifconfig Linux tool can show the current details for the network interface:
ifconfig wwan0
To bring down and stop the cellular network connection, please use the stop command bellow:
qmi-network /dev/cdc-wdm0 stop
The ModemManager tool for Linux is based on libqmi. NetworkManager and ModemManager . 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 several commands only working on selected devices and not necessarily on supported in the specific device you use, resulting in an error message.
Related products
Sierra Wireless MC7304Sierra Wireless MC7354
SimCom SIM7100E LTE SMT EU
SimCom SIM7100E LTE mPCIe EU
SimCom SIM7100A LTE mPCIe US
SimCom SIM7100C LTE mPCIe China
Sierra Wireless MC7455 LTE Cat 6
Sierra Wireless EM7455 LTE Cat 6
SimCom SIM7100E LTE mPCIe SIM
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6
SIMCom SIM7500A LTE SMT US
SIMCom SIM7500E LTE SMT EU
SIMCom SIM7500E LTE mPCIe EU
SIMCom SIM7500SA LTE mPCIe Audio
Telit LM940A11 LTE CAT-11, GPS, mPCIe
SIMCom SIM7600E-H LTE SMT EU
SIMCom SIM7600E-H LTE CAT-4 mPCIe EU
Sierra Wireless EM7565 LTE CAT-12
SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
SIMCom SIM7600A-H LTE CAT-4 mPCIe Audio
SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SIMCom SIM7600A-H LTE CAT-4 mPCIe US
SIMCom SIM7600V-H LTE CAT-4 mPCIe Audio Verizon
Fibocom NL668-EAU mPCIe LTE CAT-4
SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SIMCom SIM7600E LTE CAT-1 mPCIe
SIMCom SIM7600SA LTE CAT-1 mPCIe
SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
Telit LM960 LTE CAT-18, GPS, mPCIe
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
Fibocom NL678-E mPCIe LTE CAT-6
SIMCom SIM7600E Development Kit
SIMCom SIM7600A-H LTE CAT-4 mPCIe-SIM
Sierra Wireless MC-WP7607 LTE CAT-4 mPCIe
Telit LE910C4-NF LTE CAT-4 mPCIe
Telit LE910C1-NS LTE CAT-1 Sprint mPCIe
SIMCom SIM7906E LTE CAT-6 M.2
SIMCom SIM7906E LTE CAT-6 mPCIe
Telit LE910C1-NA LTE CAT-1 AT&T LGA
Telit LE910C1-NS LTE CAT-1 Sprint LGA
SIMCom SIM7600G-H LTE CAT-4 mPCIe
Telit LE910C1-AP
Telit LE910C1-EU
Telit LE910C4-NF
Telit LE910C1-EU LTE CAT-1 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe SIM
Telit LE910C1-NF
Telit LM940A11, HW Rev. 2, LTE CAT-11, GPS, mPCIe
Telit LE910C4-NF LTE CAT-4 mPCIe SIM
SIMCom SIM7912G LTE CAT-12 M.2
Telit LM960A18 LTE CAT-18 mPCIe
Telit LE910C1-EU LTE CAT-1 mPCIe SIM
Telit LE910C1-AP LTE CAT-1 mPCIe SIM
Telit LE910C1-NF LTE CAT-1 mPCIe
Telit LE910C4-AP LTE CAT-4 mPCIe SIM
Telit LE910C4-CN LTE CAT-4 mPCIe
Question
We cannot acquire an DHCP address over qmi_wwan driver when using Raspbian Linux OS?
Solution
Raspbian uses dhcpd to probe all available network interfaces found in the system, which is problematic for the qmi_wwan driver interface, if it is done before being configured properly when using cellular modules supporting only Raw-IP.
This can be avoided by setting dhcpd to deny the related cellular module network interface (most often named wwan0 by the system).
Add to the /etc/dhcpcd.conf file in Raspbian the following line (in the end):
denyinterfaces wwan0
Now, restart the system (preferably re-power it) so cellular module fully restarts also.
At next startup, the settings should be applied and you can now configure and use the qmi interface as described in some of the others faq's, found on the Techship webpage.
Related products
Sierra Wireless MC7455 LTE Cat 6Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7430 LTE Cat 6
SIMCom SIM7500A LTE SMT US
SIMCom SIM7500E LTE SMT EU
SIMCom SIM7500E LTE mPCIe EU
SIMCom SIM7500SA LTE mPCIe Audio
Telit LM940A11 LTE CAT-11, GPS, mPCIe
Telit LN940 A11 LTE CAT-11 M.2
Telit LN940 A9 LTE CAT-9 M.2
SIMCom SIM7600E-H LTE SMT EU
SIMCom SIM7600E-H LTE CAT-4 mPCIe EU
Sierra Wireless EM7565 LTE CAT-12
SIMCom SIM7600E-H LTE CAT-4 mPCIe SIM
SIMCom SIM7600A-H LTE CAT-4 mPCIe Audio
SIMCom SIM7600SA-H LTE CAT-4 mPCIe
SIMCom SIM7600A-H LTE CAT-4 mPCIe US
SIMCom SIM7600V-H LTE CAT-4 mPCIe Audio Verizon
SIMCom SIM7600SA-H LTE CAT-4 mPCIe with SIM holder
SIMCom SIM7600E LTE CAT-1 mPCIe
SIMCom SIM7600SA LTE CAT-1 mPCIe
SIMCom SIM7600E-H LTE CAT 4 -mPCIE with Audio
Telit LM960 LTE CAT-18, GPS, mPCIe
Telit LN941 LTE CAT-6, M.2
Sierra Wireless EM7511 LTE CAT-12
Sierra Wireless EM7565, CAT-12, M.2 CBRS Enabled
SIMCom SIM7600E Development Kit
SIMCom SIM7600A-H LTE CAT-4 mPCIe-SIM
Telit LE910C4-NF LTE CAT-4 mPCIe
Telit LE910C1-NS LTE CAT-1 Sprint mPCIe
Telit LE910C1-NA LTE CAT-1 AT&T LGA
Telit LE910C1-NS LTE CAT-1 Sprint LGA
SIMCom SIM7600G-H LTE CAT-4 mPCIe
Telit LE910C1-AP
Telit LE910C1-EU
Telit LE910C4-NF
Telit LE910-PCI (LE910C1-AP)
Telit LE910-PCI (LE910C1-NA)
Telit LE910C1-EU LTE CAT-1 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe
Telit LE910C4-EU LTE CAT-4 mPCIe SIM
Telit LE910C1-NF
Telit LM940A11, HW Rev. 2, LTE CAT-11, GPS, mPCIe
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
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.
Related products
Telit LM940A11 LTE CAT-11, GPS, mPCIeSierra Wireless MC7455 LTE Cat 6
Sierra Wireless MC7430 mPCIe
Sierra Wireless EM7455 LTE Cat 6
Sierra Wireless EM7430 LTE Cat 6
Sierra Wireless EM7565 LTE CAT-12
Telit LN940 A11 LTE CAT-11 M.2
Telit LN940 A9 LTE CAT-9 M.2
M.2 to USB adapter with casing and external power
M.2 to USB adapter with external voltage
USB3.0 M.2 Adapter with enclosure
You might also be interested in
RF Interface Cable SMA/IPEX MHF, 20 cm
Connector Type: IPEX MHF/U.FL, SMA-F | Cable length: 20 cm | Cable Specification: 1.13 mm coax
1 PCS PRICE $4.40
Compex WLE900VX
Manufacturer: Compex | Wifi Standard: 802.11a/b/g/n/ac | Wifi Frequency: 2.4 GHz, 5 GHz | Form Factor: mPCIe - full size | Wifi Antenna: 3T3R MIMO | Max output power: 19 dBm | Chipset: Qualcomm, Atheros, QCA9880 | Operating Temperature Range: -20 °C – 70 °C | Driver Support: Linux, OpenWRT, In-kernel ath10k | Width: 30 mm | Interface: PCIe | Length: 50 mm
1 PCS PRICE $33.50
LTE/UMTS Swivel Antenna
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, Wifi/Bluetooth 2400, LTE 790-960/1710-2690 | Mounting method: Connector | Antenna Location: External | Connector Type: SMA-M | Impedance: 50 Ohm | Polarization: Vertical | Max power: 50 W | Width: 21 mm | Length: 157 mm | Height: 157 mm
1 PCS PRICE $7.30
Compex WLE600VX
Manufacturer: Compex | Wifi Standard: 802.11a/b/g/n/ac | Wifi Frequency: 2.4 GHz, 5 GHz | Form Factor: mPCIe - full size | Wifi Antenna: 2T2R MIMO | Antenna Interface: IPEX MHF/U.FL | Max output power: 18 dBm | Chipset: Qualcomm, Atheros, QCA9882 | Operating Temperature Range: -20 °C – 70 °C | Driver Support: OpenWRT, In-kernel ath10k | Width: 30 mm | Interface: PCIe | Length: 51 mm | Certification: FCC, CE, RoHS, CE RED
1 PCS PRICE $29.50
RF Interface Cable RPSMA/IPEX MHF, 20 cm
Connector Type: IPEX MHF/U.FL, RPSMA-F | Cable length: 20 cm | Cable Specification: 1.13 mm coax
1 PCS PRICE $4.60
LTE Rubber Swivel Antenna, SMA-M
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, LTE 790-960/1710-2690 | Mounting method: Connector | Antenna Location: External | VSWR: 2.5 :1 | Gain: 5 dBi | Connector Type: SMA-M | Impedance: 50 Ohm | Polarization: Vertical | Radiation pattern: Omnidirectional | Max power: 50 W | Length: 195 mm | Diameter: 12.8 mm
1 PCS PRICE $6.00
GPS / GLONASS / LTE / WiFi Antenna, 3m, SMA-M
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, LTE 698-960/1710-2690, Wifi/Bluetooth 2400, GPS 1575.42, GLONASS, Combination Antenna | Active/Passive GPS: Active | Mounting method: Screw | Antenna Location: Outdoor, External | VSWR: 2 :1 | Gain: 2 dBi | Connector Type: SMA-M | Impedance: 50 Ohm | Cable length: 300 cm | Cable Specification: RG174 | Polarization: Linear, RHCP (GPS) | IP Class: IP67 | Operating Temperature Range: -40 °C – 85 °C | Height: 48 mm | Diameter: 50 mm
1 PCS PRICE $34.20
Internal GSM/UMTS/WiFi Antenna, 10cm, IPEX/U.FL
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, Wifi/Bluetooth 2400, LTE 791-862/1710-2690 | Mounting method: Screw, Other | Antenna Location: Internal | VSWR: 2 :1 | Gain: 2.14 dBi | Connector Type: IPEX MHF/U.FL | Impedance: 50 Ohm | Cable length: 10 cm | Polarization: Linear | Max power: 25 W | Operating Temperature Range: -40 °C – 85 °C | Width: 8.5 mm | Length: 113 mm | Height: 113 mm
1 PCS PRICE $6.70
SimCom SIM7100E LTE mPCIe EU
UMTS Bands: B1 (2100), B8 (900) | MIMO (Multiple-Input Multiple-Output): Yes | LTE Bands: B1 (2100), B3 (1800), B7 (2600), B8 (900), B20 (800DD), B38 (TDD 2600), B40 (TDD 2300) | GSM/EDGE Bands: B8 (900), B3 (1800) | Manufacturer: SIMCom | LTE Region: Europe | FOTA Firmware Updates: No | Form Factor: mPCIe - full size | Technology: LTE - cat 3 | Antenna Interface: IPEX MHF/U.FL | GPS: Yes | GNSS technology: GPS, GLONASS | Max DL Speed: 100 Mbps | Max UL Speed: 50 Mbps | Chipset: MDM9215 | Operating Temperature Range: -30 °C – 80 °C | Driver Support: Windows 7, Windows XP, Windows Vista, Linux, Android, Windows 8, Windows CE, Windows 8.1 | Interface: USB 2.0 | Voice Call Support: Yes | GNSS antenna support: Passive, Active 3.05VDC | SIM interface: Through miniPCIe connector | GPIO: Yes | Extended Operating Temperature Range: -30 °C – 80 °C | Audio interface: Digital PCM signal input/output in socket, Digital PCM signal over USB interface | Certification: CE, CE RED | Size: 30x30x2.9 mm
1 PCS PRICE $59.00
RF Interface Cable SMA/IPEX MHF, 15 cm
Connector Type: IPEX MHF/U.FL, SMA-F | Cable length: 15 cm | Cable Specification: 1.13 mm coax
1 PCS PRICE $4.30