Sierra Wireless EM9291 5G Sub6 M.2

Article Number: 11468
Brand: Sierra Wireless
Supplier number: 1104898

Optimized 5G NR performance for applications requiring Gibabit speed, the EM9291 module is part of the EM Series offering global 5G connectivity.

Designed in an M.2 form factor, the EM9291 is compatible with Sierra Wireless's EM9191 module for a simple upgrade path to get the latest standards compliance and bands, 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.9Gbps 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 EM9291 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.

Key Benefits

  • Certified by the FCC for CBRS private networks

  • Worldwide coverage on a single module

  • Dual Sim Single Standby (DSSS)

  • Industrial grade

  • Optional Embedded Consumer eUICC to simplify and add flexibility to IoT deployment

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


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

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
North America
South America
Primary Technology
Form Factor
M.2 3052
5G Sub6 Bands
n1 (FDD 2100)
n2 (FDD 1900)
n3 (FDD 1800)
n5 (FDD 850)
n7 (FDD 2600)
n8 (FDD 900)
n12 (FDD 700)
n13 (FDD 700)
n14 (FDD 700)
n18 (FDD 850)
n20 (FDD 800)
n25 (FDD 1900)
n26 (FDD 850)
n28 (FDD 700)
n29 (SDL 700)
n30 (FDD 2300)
n38 (TDD 2600)
n39 (TDD 1900)
n40 (TDD 2300)
n41 (TDD 2500)
n48 (TDD 3600)
n66 (FDD 1700 / AWS-3)
n70 (FDD 2000 / AWS)
n71 (FDD 600)
n75 (SDL 1500)
n76 (SDL 1500)
n77 (TDD 3700)
n78 (TDD 3500)
n79 (TDD 4500)
LTE Bands
B1 (FDD 2100)
B2 (FDD 1900)
B3 (FDD 1800)
B4 (FDD 1700 / AWS)
B5 (FDD 850)
B7 (FDD 2600)
B8 (FDD 900)
B9 (FDD 1800)
B12 (FDD 700ac)
B13 (FDD 700c)
B14 (FDD 700PS)
B17 (FDD 700bc)
B18 (FDD 800)
B19 (FDD 800)
B20 (FDD 800DD)
B25 (FDD 1900)
B26 (FDD 850)
B28 (FDD 700)
B29 (SDL 700)
B30 (FDD 2300)
B32 (SDL 1500)
B38 (TDD 2600)
B39 (TDD 1900)
B40 (TDD 2300)
B41 (TDD 2500)
B42 (TDD 3500)
B43 (TDD 3600)
B46 (TDD 5200)
B48 (TDD 3600)
B66 (FDD 1700 / AWS-3)
B71 (FDD 600)
UMTS Bands
B1 (2100)
B2 (1900)
B4 (AWS)
B8 (900)
B19 (800)
B5 (850)
B6 (800)
Max DL Speed
4900 Mbps
Max UL Speed
660 Mbps
GNSS technology
Antenna Connectors
Operating Temperature Range
-30 °C – 70 °C
Extended Operating Temperature Range
-40 °C – 85 °C
Data Interface
USB 3.1
Driver Support
Windows 10
MIMO (Multiple-Input Multiple-Output)
SIM interface
Dual SIM interface

How do we connect to a 5G NR network?


To be able to connect to a 5G network both the module and SIM card need to have 5G technology support. If you have problems with NSA or SA for a specific band make sure that your module actually supports this as well. Read through your product’s hardware guide which can be found on the product’s page. 

Support for 5G NSA/SA on a specific band can also be firmware dependent. Make sure that you have the latest firmware installed on your module. 

This FAQ includes many different AT commands, both 3GPP standard and vendor specific commands, so it’s recommended to have your module’s AT guide with you while troubleshooting.

Perform a network scan with AT+COPS=? and check if your module can find any 5G networks. You can see if it’s a 5G network by looking at the last value in the quadruple. Depending on which technology you use this should be set to:

  • 11 - NR_5GCN (NR connected to a 5G core Network)

  • 12 - NGRAN (NG-RAN access technology)

  • 13 - EUTRA_NR (Dual connectivity of LTE with NR)

If your module can find the 5G network, check your current network configuration with the read command AT+COPS? to make sure it’s set to the correct value. Similarly you can check the NR5G network registration status with the following AT command sequence (note this command only applies for 5G SA) :



You can select the Wireless Data Service with AT+WS46:

  • 36 - NG-RAN only

  • 37 - NG-RAN and E-UTRAN

  • 38 - NG-RAN, E-UTRAN and UTRAN

  • 40 - NG-RAN and UTRAN

Telit 5G related AT commands:

  • Enable your 5G band with AT#BND

  • To enable/disable only the 5G bands AT#5GCTL can be used

FN980 does not have SA enabled by default. To enable it run the following commands:

AT#BND=(Fill in you bands here, see AT guide)

If you are using a Windows PC change the USBCFG to option 2 

SIMCom 5G related AT commands:

  • Enable both SA and NSA with AT+CSYSSEL=”nr5g_disable”,0

  • Disable SA with AT+CSYSSEL="nr5g_disable",1

  • Disable NSA with AT+CSYSSEL=”nr5g_disable”,2

  • Configure 5G NSA bands with AT+CSYSSEL=”nsa_nr5g_band”

  • Configure 5G SA bands with AT+CSYSSEL=”nr5g_band”

  • Set your preferred mode with AT+CNMP

    • 55 - WCDMA+LTE+NR5G

    • 71 - NR5G

    • 109 - LTE+NR5G

Sierra Wireless 5G related AT commands:

  • Display your 5GNR information with AT!NRINFO?

  • Enable/disable ENDC (NSA) and SA with AT!RTCA (note that these settings are not persistent across power cycles)

AT!GSTATUS not responding with NR5G fields and looks similar to:

NR5G RSRP (dBm): --- NR5G RSRQ (dB): ---

NR5G SINR (dB): —

The response details are dependent on the network providing the necessary information to the modem. To be sure you get these values the modem has to be in a data call in SA mode

Fibocom 5G related AT commands:

  • Select RAT with AT+GTRAT or RAT and Bands with AT+GTACT

    • 14 - NR-RAN

    • 16 - NR-RAN/WCDMA

    • 17 - NR-RAN/LTE

    • 20 - NR-RAN/WCDMA/LT

For more general information about 5G see FAQ “What is 5G NR?”.

If you are still encountering problems connecting to a 5G network you can create a support ticket: Please describe your problem and set up thoroughly and include the logs from this troubleshooting.


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


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

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

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


How do I set USB-interface modes on my Sierra Wireless module?


Sierra Wireless modules can expose different USB interfaces, like MBIM, MODEM, NMEA or RMNET. The different interfaces can be combined or used individually, depending on the specific need for your project.
Here is how to set the different USB interface configurations. (In this example we use a Sierra Wireless EM7421, but it will be similar for many other Sierra Wireless modules.)

Make sure you get an OK after every AT command sent.
We start by typing:
To be able to view what we just sent to the module we type:
Since this feature is password protected we need to type:
To see what USB interface we are currently using, just type AT!USBCOMP? and you should receive something like this:

Config Index: 1
Config Type: 3 (Generic)
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0)

Config index is what the type applies to and should be set to 1.
The config type means what USB composition is used. For this module USBIF-MBIM (1), PCIE USBIF (2), Legacy Generic (3) or RNDIS (4) are available.
Interface bitmask is the part where we see what USB interface our module is set to.

Now, to see what our USB interface options are we need to type:
Here we can see that for this module we have the following options:
DIAG - 0x00000001
NMEA - 0x00000004
MODEM - 0x00000008
RMNET0 - 0x00000100
MBIM - 0x00001000
These values are hexadecimal. So, for an example, if we wanted to activate all the options (DIAG, NMEA, MODEM and MBIM) we just add these values together.
If we open the Windows Calculator in Programmer mode (and make sure you have “HEX” selected!) and add all the values together like this 1 + 4+ 8 +1000, we will get 100D. (Please note, RMNET0 and MBIM cannot be used simultaneous for this module. Refer to the manual of your specific module to when setting up the USB interface.)
If we then send the following AT command to the module, we will set it to DIAG, NMEA, MODEM and MBIM:

Again, type AT!USBCOMP? to confirm we have the new settings selected, it should look like this:

Config Index: 1
Config Type: 3 (Generic)
Interface bitmask: 0000100D (diag,nmea,modem,mbim)

For further information please take a look at the AT command user guide available on the product's specific page under "technical documentation", which is available for download once logged in.


How do I select specific bands on my Sierra Wireless module?


The AT command AT!BAND can be used to select what specific GSM and LTE bands that you want to be active on your module.

If you are experiencing poor DL or UL speeds, one solution may be to only select the bands that you know are available, which can increase the transfer speeds.

(Please note that the following examples are when using a Sierra Wireless EM7421)

First, see that you get an “OK” with command:
Then, to make sure you can see what command has been sent, type:

Since what we are about to do is password protected, we need to type:

When entering AT!BAND? it will return a reply looking like (for example):
Index, Name, GW Band Mask L Band Mask 1 TDS Band Mask L Band Mask 2 L Band Mask 3 L Band Mask 4
00, All Bands 000200000C400000 000007A0880800C5 0000000000000000 0000000000000000 0000000000000000 0000000000000000

The "00" is referring to the selected preset, "All Bands" to the preset name, "000200000C400000" to GSM bands and "000007A0880800C5" to selected LTE bands in hexadecimal.

To get information on all available bands, we need to type:

Starting at the GSM band (at chapter "AT!BAND - Select/return frequency band set" in the AT command reference manual) we can see that 000200000C400000 corresponds to “0002000000000000 - B8 (900) + 0000000008000000 - B6 (800) + 0000000004000000 - B5 (850) + 0000000000400000 - B1 (2100) = 000200000C400000 (All GSM Bands)”

Now for LTE, which is probably what is a little tricky to understand. Let’s start the Windows Calculator and change it to Programmer mode. If you copy the "000007A0880800C5" into the calculator window it should convert it to binary.
HEX: 0000 07A0 8808 00C5
BIN: 0111 1010 0000 1000 1000 0000 1000 0000 0000 1100 0101

If you look at the line of BIN above you can see what bands are active (1) and which are not (0). Looking from right to left, the first bit corresponds to B1, second bit to B2, third bit B3, and so on…

HEX: 0000 07A0 8808 00C5
BIN: 0111 1010 0000 1000 1000 0000 1000 0000 0000 1100 0101
Selected bands: B1+B3+B7+B8+B20+B28+B32+B38+B40+B41+B42+B43

So if I, for example, only want the GSM bands "GSM 900MHz + GSM 850MHz", and LTE bands "B3, B4, B7, B28" we enter the following:
AT!BAND= 11,"Custom User Preset",0002000004000000,000000000800004C

Now we have created a new preset slot “11”, a name for the preset “Custom User Preset” and selected bands for GSM “GSM 900MHz + GSM 850MHz” and also selected bands for LTE "B3, B4, B7, B28", see explanation below:

Bands: B3, B4, B7, B28
Binary: 1000 0000 0000 0000 0000 0100 1100
Hexadecimal: 800 004C

Now we want to make sure our newly created preset is selected, so we type:

And finally to check that we have selected the preset we again type AT!BAND? and should get the following response:
Index, Name, GW Band Mask L Band Mask 1 TDS Band Mask L Band Mask 2 L Band Mask 3 L Band Mask 4
11, Custom User Preset 0002000004000000 000000000800004C 0000000000000000 0000000000000000 0000000000000000 000000000000000

For further information please take a look at the AT command user guide available on the product's specific page under "technical documentation", which is available for download once logged in.