TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register

Telit LM960 LTE CAT-18, GPS, mPCIe

Article Number: 10819
Manufacturer: Telit
Supplier number: LM960AIW201T0W2000

The Telit LM960 Mini PCIe (mPCIe) data card delivers high speed data rates via Advanced LTE and offers a cellular connection for products in network appliance environments. This data card is well-suited for products that demand high throughput such as routers, mobile gateways and access points, to provide the most advanced 4G LTE connectivity, ensuring a rich and seamless user experience.

Based on LTE Category 18, the LM960 mPCIe data card achieves download rates up to 1.2 Gbps. It supports 4x4 MIMO, 5x downlink carrier aggregation and 2x uplink carrier aggregation. The product supports multiple RF frequency bands and band combinations to accommodate
global deployments.

Web pricing for samples only. For project pricing please contact us at
Techship sales


Currently production ready and certified for North America target region with firmware 32.00.041, on bands:
LTE: B2, B4, B5, B12, B14, B29, B30, B46, B66, UMTS/HSPA: 850, 1900 MHz.
FCC, IC, GCF and PTCRB certification plus AT&T operator approval completed.

Generic all bands enabled firmware only available for early testing and design in, this due to CE RED and Generic/EU firmware not yet finalized.

4x4 MIMO antenna information for Telit LM960:
There are two primary and two secondary antenna RF connectors for the cellular connectivity on the LM960 module.
The first set of primary and secondary antennas (#0) serve the lower and middle cellular bands while the second set of primary and secondary antennas (#1) serve the high and ultra high frequency bands.
Please ensure to match the antenna frequency range as specified in the Telit LM960 Hardware guide section 7 and 7.5 Antenna requirements and connections.

End-of-life

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
sales@techship.com

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)
B2 (1900)
B8 (900)
B4 (AWS)
B5 (850)
MIMO (Multiple-Input Multiple-Output)
Yes
LTE Bands
B1 (2100)
B3 (1800)
B7 (2600)
B8 (900)
B12 (700ac)
B13 (700c)
B14 (700PS)
B20 (800DD)
B25 (1900)
B42 (TDD 3500)
B38 (TDD 2600)
B40 (TDD 2300)
B43 (TDD 3600)
B26 (US 850 Ext)
B28 (700 APAC)
B29 (US 700de Lower)
B39 (TDD 1900)
B41 (TDD 2500)
B30 (2300 WCS)
B66 (AWS-3)
B32 (1500)
B46 (TDD 5200)
B48 (3600)
B71 (600)
Manufacturer
Telit
LTE Region
Europe
North America
Asia
Australia
APAC
Form Factor
mPCIe
Technology
LTE - cat 18
Antenna Interface
IPEX MHF-4
GPS
Yes
GNSS technology
GPS
GLONASS
BeiDou
Galileo
Max DL Speed
1200 Mbps
Max UL Speed
150 Mbps
Chipset
Qualcomm
SDX20
Operating Temperature Range
-40 °C – 85 °C
Driver Support
Linux
Windows 10
in kernel
Interface
USB 2.0
USB 3.0
Voice Call Support
No
GNSS antenna support
Passive
Active
SIM interface
Through miniPCIe connector
Dual SIM interface
Carrier Certification
AT&T
Extended Operating Temperature Range
-40 °C – 85 °C
Certification
FCC
RoHS
GCF
PTCRB
IC
Technical details:
Currently shipped with:
Host firmware version: 32.00.001 and default firmware version set to ATT operator config.
Generic: 32.00.011
ATT: 32.00.041

Should you not be able to detect the SIM card interface, please ensure that the hotswap feature is disabled if your host board do not implement the SIM detect pin routing. Do so by AT commands bellow, after module reboot it should work correctly.
AT#HSEN=0,0
AT#HSEN=0,1
AT#REBOOT

Datasheet for 10819 Telit LM960 CAT-18 mPCIe

Download

Uploaded at
2018-09-19 11:42:15
Last updated
2019-04-05 15:17:16
Version
12 2018
Related products
Telit LM960 LTE CAT-18, GPS, mPCIe

Hardware user guide for the Telit LM960 cellular module

Download

Uploaded at
2018-11-07 16:02:55
Last updated
2019-08-07 09:42:18
Version
R7
Related products
Telit LM960 LTE CAT-18, GPS, mPCIe

This guide describes the Telit LM960 cellular modules AT control commands available and supported

Download

Uploaded at
2018-11-07 16:01:23
Last updated
2018-12-03 09:33:47
Version
R1
Related products
Telit LM960 LTE CAT-18, GPS, mPCIe

This guide describes the Telit LM940 and LM960 series cellular modules accepted (raw) QMI commands.

Download

Uploaded at
2018-11-07 16:10:54
Last updated
2018-12-03 09:35:54
Version
R3
Related products
Telit LM940 LTE CAT-11, GPS, mPCIe
Telit LM960 LTE CAT-18, GPS, mPCIe

Software user guide for the Telit LM960 cellular module

Download

Uploaded at
2018-11-07 16:04:22
Last updated
2018-11-07 16:04:22
Version
R1
Related products
Telit LM960 LTE CAT-18, GPS, mPCIe

Zip archive with Telit cellular modules USB drivers installers for Windows 7, 8.x, 10 both x86 and x64 system architectures.
(Non WHQL certified drivers).

Download

Windows based multi image firmware updater tool for the Telit LM960 cellular module.

Use AT command AT#FIRMWARE to list loaded firmware images and select active firmware image with: AT#FIRMWARE=(LIST ORDER ID)

Download

Uploaded at
2019-09-19 09:19:56
Last updated
2019-09-19 09:21:03
Version
V.32.00.0x1 (Generic and AT&T)
Requirements
Windows 8, 10,
Telit Windows drivers
Related products
Telit LM960 LTE CAT-18, GPS, mPCIe
Question

How to collect initial diagnostics data and logs for Telit cellular modules needed when requesting Techship technical support?

Solution

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:
-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 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:
AT
Enable AT command echo:
ATE1
Verbose error reporting:
AT+CMEE=2
Module model:
AT+CGMM
Firmware version:
AT+CGMR
IMEI Code:
AT+CGSN
USB endpoint configuration:
AT#USBCFG?
Serial port configuration:
AT#PORTCFG?
Operational mode:
AT+CFUN?
Selected network access techniques:
AT+WS46?
List network operator info:
AT+COPS?
Network registration status:
AT+CREG=2
AT+CREG?
AT+CGREG?
Signal strength:
AT+CSQ
Last serving cell network information:
AT#SERVINFO
Current network status:
AT#RFSTS
List APN details:
AT+CGDCONT?
List Packet switch enable/disable status:
AT+CGATT?
Enable Packet Switched functionality:
AT+CGATT=1
List PDP profiles status:
AT+CGACT?
List default data connection details:
AT#BND?
List bearers and IP addresses:
AT+CGCONTRDP=
AT+CGPADDR=

Additional test commands for Telit LM940/LM960:
AT#FIRMWARE
AT#FIRMWARE?
AT#GETFW
AT#ACTIVEFW?
AT#CACTL?
AT#RXDIV?
AT#RXTOGGLE?
AT#LRXDIV?
AT#LCFC
AT#TEMPSENS?
AT#GPIO?
AT#HWREV
AT#QSS?
AT#USB3TUNE?

AT#USBSWITCH?


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

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.

Question

How to change USB composition mode to Mobile Broadband Interface (MBIM) that is used by Windows 8 and 10 systems for data connectivity and enabling support for the built-in connection manager in Windows?

Solution

This is done by sending AT commands to the Modem or AT serial interfaces that are accepting AT commands. The module will then change the USB endpoint composition it exposes. You can find the correct Serial COM port number by checking in the 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.

Commands to use:
Sierra Wireless EM75xx series module:
AT!ENTERCND="A710"
AT#USBCOMP=1,3,100D
AT!RESET

Sierra Wireless EM74xx, MC74xx series module:
AT!ENTERCND=”A710”
AT!USBCOMP=1,1,100D
AT!RESET

Sierra Wireless EM73xx, MC73xx series module:
AT!ENTERCND=”A710”
AT!UDUSBCOMP=8
AT!RESET

Simcom SIM7xxx series modules:
AT+CUSBPIDSWITCH=9003,1,1
AT+CRESET

ZTE Welink ME3630 series:
AT+ZSWITCH=8
AT+ZRST

Telit LM940:
AT#USBCFG=2
AT#REBOOT

Telit LM960:
AT#USBCFG=2
AT#REBOOT

Telit LE910x V2:
AT#USBCFG=3
AT#REBOOT

On Huawei modules the USB mode changing is done automatically by the Windows drivers and otherwise defaults to the modules standard endpoint interfaces.

Question

MiniPCIe based cellular modules supporting both USB2 and USB3 are not detected in the host system? Such as Sierra Wireless MC74** series, and Telit LM940/LM960 series modules.

Solution

From start the PCI-SIG miniPCIe form factor standard only included support for PCIe + USB2 data interface and had designated signal lines for these between host system and the miniPCIe module. Since revision 2.1 of the PCI-SIG miniPCIe standard it is defined that the PCIe data lanes can be shared/used for USB3 also.

Cellular modules mainly rely on USB2 interface but as the cellular throughput speeds have increased, the USB2 can become a bottleneck on LTE Cat 6 modules and higher. To address this, USB3 data interface was introduced on the higher data throughput mobile broadband cellular modules and made available in parallel to USB2 interface. However due to limited amount of pin lanes available in the miniPCIe socket they share location with the PCIe data interface pin lanes.

When the host system and module are powered on, the cellular module will try to probe if USB3 interface is present on the pin lanes and if communication can be established, otherwise the module will revert to using the USB2 data interface instead.

However, in some host systems where PCIe data interface also is implemented on the shared pin lanes, the signals will interfere with the cellular modules probing for USB3 interface making it not fall back to USB2 data interface. This usually result in the cellular module not being detected at all in the host operating system.

The USB3 auto-sensing functionality is enabled by default but can be disabled by using AT commands to write the memory changes to the internal NV memory which is stored between restarts. After the module is restarted it will use only the USB2 pin lanes for data interface. Please also check and validate if the host system BIOS support disabling of the PCIe interface in the miniPCIe socket.

Related AT commands for configuring USB3/USB2 modes:

Telit LM940/LM960 modules:
AT#USBSWITCH=1
AT#REBOOT

For Sierra Wireless MC74 series: (firmware version dependent)
AT!ENTERCND="A710"
AT!USBSPEED=0
AT!RESET

For troubleshooting this issue in hardware, you can try isolating the USB3 data interface pins #23, 25, 31, 33 on the top side of the miniPCIe data cards card socket so no signalling to and from the hosts can occur. This could be done in the board design or with adapter.

Question

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

Solution

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: https://www.freedesktop.org/wiki/Software/libqmi/

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,apn=data.tre.se" --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 8.8.8.8

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.

You might also be interested in