TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register

Sierra Wireless EM9191 5G sub-6 M.2

Article Number: 11169
Brand: Sierra Wireless
Supplier number: 1104629

The Sierra Wireless EM9191 is a 5G module offering global connectivity. Designed in an M.2 form factor, the EM9191 is compatible with Sierra Wireless's EM9190 module for a simple upgrade path to mmWave, as well as the EM7690 module to help facilitate the migration and differentiation between 4G LTE and 5G.

This 5G NR Sub-6 GHz embedded module delivers up to 4.5Gbps downlink speed and 660Mbps uplink speed. With automatic 4G and 3G fallback networks and integrated GNSS receiver (GPS, GLONASS, BeiDou, and Galileo satellite systems supported), the EM9191 is applicable to a wide range of IoT applications such as industrial routers, home gateways, industrial and consumer laptops, rugged tablet PCs, video surveillance and digital signage.

To speed up development, we recommend you also buy a developer kit:
11131, Sierra Wireless M.2 Developer Kit EM9/EM76 Series

End-of-life

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

Quantity Price

No prices available

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

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

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

Subscribe to updates
LTE Bands
B1 (FDD 2100)
B2 (FDD 1900)
B3 (FDD 1800)
B4 (FDD 1700 / AWS)
B7 (FDD 2600)
B8 (FDD 900)
B12 (FDD 700ac)
B13 (FDD 700c)
B14 (FDD 700PS)
B18 (FDD 800lower)
B19 (FDD 800 upper)
B20 (FDD 800DD)
B21 (FDD 1500upper)
B5 (FDD 850)
B25 (FDD 1900)
B42 (TDD 3500)
B38 (TDD 2600)
B40 (TDD 2300)
B43 (TDD 3600)
B26 (FDD 850 Ext)
B28 (FDD 700 APAC)
B29 (US 700de Lower)
B34 (TDD 2000)
B39 (TDD 1900)
B41 (TDD 2500)
B30 (FDD 2300 WCS)
B66 (FDD 1700 / AWS-3)
B32 (SDL 1500)
B46 (TDD 5200)
B48 (TDD 3600)
B71 (FDD 600)
Region
Europe
North America
Australia
Japan
Africa
APAC
5G Sub6 Bands
n1 (2100)
n2 (1900)
n3 (1800)
n5 (850)
n7 (2600)
n12 (700)
n20 (800)
n28 (700)
n41 (TDD 2500)
n71 (600)
n77 (TDD 3700)
n78 (TDD 3500)
n79 (TDD 4500)
n8 (900)
n25 (1900)
n38 (2600)
n40 (2300)
n66 (1700)
n48 (3600)
Form Factor
M.2 3052
Technology
5G
Antenna Connectors
IPEX MHF-4
GNSS
Yes
GNSS technology
GPS
GLONASS
BeiDou
Galileo
Max DL Speed
4500 Mbps
Max UL Speed
660 Mbps
Chipset
Qualcomm
SDX55
Operating Temperature Range
-30 °C – 70 °C
Driver Support
Linux
Windows 10
Data Interface
PCIe
USB 3.1
Carrier Certification
AT&T
Verizon
T-Mobile
NTT DOCOMO
Extended Operating Temperature Range
-40 °C – 85 °C
Certification
FCC
GCF
PTCRB
Jate
Telec
KC
CE RED

Product technical specification for the Sierra Wireless AirPrime EM919x series 5G cellular module series and the EM7690 4G LTE-A cat 20 cellular module.

Download

Uploaded at
2020-09-28 15:23:31
Last updated
2020-12-08 09:04:03
Version
Rev. 2
Related products
Sierra Wireless EM9190 5G NR M.2
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM7690 LTE CAT-20

AT commands guide for the Sierra Wireless AirPrime EM919x series 5G cellular module series and the EM7690 4G LTE-A cat 20 cellular module.

Download

Uploaded at
2020-09-28 15:29:06
Last updated
2021-07-12 11:51:18
Version
Rev2
Related products
Sierra Wireless EM7690 LTE CAT-20
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless M.2 Developer Kit EM9/EM76 Series
Sierra Wireless EM9190 5G NR M.2

User guide for the Sierra Wireless AirPrime EM919x - EM7690 series modules development kit.

Download

Uploaded at
2020-09-28 15:34:27
Last updated
2021-07-12 11:55:41
Version
Rev1.1
Related products
Sierra Wireless M.2 Developer Kit EM9/EM76 Series
Sierra Wireless EM7690 LTE CAT-20
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM9190 5G NR M.2

Current consumption application note Sierra Wireless AirPrime EM9190 - EM7690 Series modules.

Download

Uploaded at
2020-09-28 15:45:34
Last updated
2021-07-12 11:57:30
Version
Rev1.1
Related products
Sierra Wireless EM9190 5G NR M.2
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM7690 LTE CAT-20

Application note for the Sierra Wireless AirPrime EM919x - EM7690 series sleep modes.

Download

Uploaded at
2020-09-28 15:54:33
Last updated
2021-07-12 11:56:16
Version
Rev1.1
Related products
Sierra Wireless EM9190 5G NR M.2
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM7690 LTE CAT-20

Thermal mitigation guide for Sierra Wireless AirPrime EM919x-EM7690 series M.2 key B modules.

Download

Uploaded at
2020-09-28 15:38:56
Last updated
2021-07-12 11:56:05
Version
Rev1.2
Related products
Sierra Wireless EM7690 LTE CAT-20
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM9190 5G NR M.2

Customer production test mode application note for Sierra Wireless AirPrime EM919x - EM7690 series cellular modules.

Download

Uploaded at
2020-09-28 15:59:33
Last updated
2020-11-11 10:36:14
Version
Rev1.4
Related products
Sierra Wireless EM9190 5G NR M.2
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM7690 LTE CAT-20

Non-mmWave smart transmit application note for Sierra Wireless AirPrime EM919x - EM7690 series cellular modules.

Download

Uploaded at
2020-09-28 15:57:09
Last updated
2020-09-28 15:57:09
Version
Rev1.0
Related products
Sierra Wireless EM7690 LTE CAT-20
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM9190 5G NR M.2

Declaration of conformity document for CE RED.

Download

Uploaded at
2021-03-01 10:11:39
Last updated
2021-03-01 10:11:39
Version
EM919120201218
Related products
Sierra Wireless EM9191 5G sub-6 M.2

Microsoft Windows desktop driver installer for the Sierra Wireless AirPrime EM91xx/EM7690 series cellular modules.

Download

Uploaded at
2021-06-21 15:21:51
Last updated
2021-06-21 15:21:51
Version
5154
Requirements
Microsoft Windows 10 desktop system.
Related products
Sierra Wireless EM7690 LTE CAT-20
Sierra Wireless EM9191 5G sub-6 M.2
Sierra Wireless EM9190 5G NR M.2
Question

How to establish a data connection with Sierra Wireless EM9190, EM9191 and EM7690 in Linux using MBIM network interface over USB

Solution

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

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

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

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

Ensure that the cdc_mbim network kernel driver and qcserial usb-serial driver is properly loaded to the module interfaces, refer to Sierra Wireless Mobile broadband package for Linux for more details. Binary version and guide linked below.
It can be checked e.g. through dmesg, usb-devices or lsusb -t commands.

usb-devices
T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
D: Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 1
P: Vendor=1199 ProdID=90d3 Rev=00.06
S: Manufacturer=Sierra Wireless, Incorporated
S: Product=Sierra Wireless EM9190
S: SerialNumber=
C: #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=896mA
I: If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I: If#=0x1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=techship_serial
I: If#=0x4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=techship_serial
I: If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)

Should you not have the qcserial drivers loaded correctly, you can try compile our modified option usb-serial kernel driver module techship_serial from git link below and load them into your system build, it is however always recommended that you use the vendor provided or recommended drivers.

See the git readme files for details on pre-requirements, how to clone, compile and use the make file options to install the drivers.

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

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

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

Check cellular module device version and capability details:
mbimcli -p -d /dev/cdc-wdm0 --query-device-caps --no-close

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

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

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

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

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

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

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

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

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

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

Enter the IPv6 details to the network interface in the Linux host system, e.g.:
ip -6 addr add 2a02:aa1:1019:50b6:a5b0:ade:8531:b178/64 dev wwan0
ip -6 link set mtu 1500 dev wwan0

Enable the network interface:
ip link set dev wwan0 up

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

You should now have a working cellular network data connection.

Test it e.g. by sending ping requests over the interface:
ping -I wwan0 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) from 2.67.32.120 wwan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=38.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=36.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=43.5 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=41.5 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 36.374/39.975/43.500/2.728 ms

ping -6 -I wwan0 2600:: -c 4
PING 2600::(2600::) from 2a02:aa1:1019:50b6:e59e:4d4a:e778:f24e wwan0: 56 data bytes
64 bytes from 2600::: icmp_seq=1 ttl=52 time=156 ms
64 bytes from 2600::: icmp_seq=2 ttl=52 time=171 ms
64 bytes from 2600::: icmp_seq=3 ttl=52 time=169 ms
64 bytes from 2600::: icmp_seq=4 ttl=52 time=167 ms

--- 2600:: ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 156.153/165.508/170.577/5.576 ms

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

Bring down the interface:
ip link set dev wwan0 down

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

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

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

Question

Why does not our EM9190/EM9091/EM7690 appear in our system when connected to our host board?

Solution

The Sierra 5G (EM919x) modules and EM7690 has the PCIe host interface as default, as compared to the USB interface. This differs from most other modules on today's market and can be a reason as to why the module is not appearing in your system.

First, make sure that there are no pin-conflicts between the adapter/host board and the module. To avoid any incompatibilities we recommend the Sierra Wireless development Kit (11131)).

To change the host interface from PCIe to USB using the development kit please do the following;
Slide SW201 to the USB connector (CN204).
Change CN203 jumper from 2-3 to 1-2.

What happens when slide SW201 is switched is that pin #20 (PCIE_DIS) is set to high (1.8V) and selects USB as host interface. Changing the jumper on the CN203 sets pin #22 (VBUS_SENSE) to high (3.135 - 4.2 V) which is used to detect USB during USB connection.

This is further explained in the Sierra Development Kit User Guide and the EM919X-EM7690 Product Technical Specification. These documents are linked to this FAQ and can also be found on the product pages under the "technical documentation" tab.

You might also be interested in