Telit LN941 LTE CAT-6, M.2

Article Number: 10820
Manufacturer: Telit
Supplier number: LN941A6E127T011000

Telit LN941 is a CAT-6 module for the European market in M.2 format.
Compliant with 3GPP Category 6 releases LN941 is the most affordable LTE module, with the capability of 2CC Carrier Aggregation, reaching up to 300Mbps DL.

The Telit M.2 family of modules supports the latest LTE Advanced networks with 3G fallback.
The industrial-grade PCIe M.2 form factor allows for easy integration into mobile computing, networking, and industrial IoT device platforms that command a smaller and thinner footprint.


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

Quantity Sample Price

No prices available

For more information
please contact us at

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

Do you need offline data on this product?

Download datasheet

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

Subscribe to updates
UMTS Bands
B1 (2100)
B8 (900)
MIMO (Multiple-Input Multiple-Output)
LTE Bands
B1 (2100)
B3 (1800)
B7 (2600)
B8 (900)
B20 (800DD)
B28 (700 APAC)
B32 (1500)
LTE Region
Form Factor
M.2 3042
LTE - cat 6
Antenna Interface
Max DL Speed
300 Mbps
Max UL Speed
50 Mbps
Operating Temperature Range
-40 °C – 85 °C

Datasheet for Telit LN94x series M.2 module.


Uploaded at
2017-11-01 17:54:58
Last updated
2018-12-03 10:31:12
Related products
Telit LN940 A11 LTE CAT-11 M.2
Telit LN940 A9 LTE CAT-9 M.2
Telit LN941 LTE CAT-6, M.2

Datasheet for 10820 Telit LN941 CAT-6 M.2


Uploaded at
2018-09-19 11:43:36
Last updated
2018-12-03 10:30:31
Related products
Telit LN941 LTE CAT-6, M.2

This user guide describes the AT commands supported by the Telit LN940 series cellular modules.


Uploaded at
2018-04-17 10:45:07
Last updated
2018-12-03 09:38:47
Related products
Telit LN940 A11 LTE CAT-11 M.2
Telit LN940 A9 LTE CAT-9 M.2
Telit LN941 LTE CAT-6, M.2

This user guide describes how the intergration of Telit LN940 series cellular modules are performed in Linux environments.


Uploaded at
2018-04-17 10:43:16
Last updated
2018-12-03 10:32:45
Related products
Telit LN940 A11 LTE CAT-11 M.2
Telit LN940 A9 LTE CAT-9 M.2
Telit LN941 LTE CAT-6, M.2

This archive contains the Telit LN94x series Linux drivers Driver Package and patching guides if needed due to kernel versions and feature support


Uploaded at
2018-05-07 15:21:28
Last updated
2018-10-23 17:25:57
Linux host operating system
Related products
Telit LN940 A9 LTE CAT-9 M.2
Telit LN940 A11 LTE CAT-11 M.2
Telit LN941 LTE CAT-6, M.2

This archive contains the Telit LN94x Series AT Commands over MBIM Interface Helper Tool and manual


Uploaded at
2018-07-18 16:38:52
Last updated
2018-07-18 16:38:52
Microsoft Windows 8
Microsoft Windows 8.1
Microsoft Windows 10
Telit LN94x series drivers
Related products
Telit LN940 A11 LTE CAT-11 M.2
Telit LN940 A9 LTE CAT-9 M.2
Telit LN941 LTE CAT-6, M.2

This archive contains the LN940 driver installer for Windows 10 systems.


Uploaded at
2018-04-17 10:28:37
Last updated
2018-07-13 08:22:53
Microsoft Windows 10
WHQL certified
Related products
Telit LN940 A9 LTE CAT-9 M.2
Telit LN940 A11 LTE CAT-11 M.2
Telit LN941 LTE CAT-6, M.2

How to collect initial diagnostics data and logs for Telit cellular modules needed when requesting Techship 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 Telit module when creating a technical support ticket.

Problem description of what exact problem is and in what precise situations present.

Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux release, kernel...)
-Drivers and driver versions

Identify the precise details of cellular module found on label:
-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 -t
ifconfig -a
ls -l /dev/serial/by-id
ls -l /sys/bus/usb-serial/devices

The logs from module firmware can be acquired by accessing one of the USB enumerated serial (COM) interfaces accepting AT commands. (In Windows this is generally modem devices or AT commands serial interfaces). Send the following commands to module and capture the text output and include them when creating the the technical support ticket.

Test that you get a OK reply:
Enable AT command echo:
Verbose error reporting:
Module model:
Firmware version:
IMEI Code:
USB endpoint configuration:
Serial port configuration:
Operational mode:
Selected network access techniques:
List network operator info:
Network registration status:
Signal strength:
Last serving cell network information:
Current network status:
List APN details:
List Packet switch enable/disable status:
Enable Packet Switched functionality:
List PDP profiles status:
List default data connection details:
List bearers and IP addresses:

Additional test commands for Telit LM940/LM960:


The support ticket can be created after login at:


We cannot acquire an DHCP address over qmi_wwan driver when using Raspbian Linux OS?


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.


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


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

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

A selection of cellular modules can be supported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Additional useful commands:

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

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

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

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

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

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

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

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

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

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