TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS
Telit LE910C4-EU is intended for the European market.
It is 3GPP release 10 compliant and comes with simultaneous support of GPS, Glonass, Bei-dou, Galileo, QZSS.
• Standard Mini PCIe Data-card form factor
• Best-in class 3GPP rel10 platform
• Easy to integrate with peripherals and actuators using USB 2.0 HS, UART and user definable GPIOs
• Battery-friendly 1.8V GPIO
• Ideal platform for IoT applications and mobile data
and computing devices with ultra-compact design and extended operating temperature range
• Internet friendly with integrated TCP/IP and UDP/IP stacks,
• Simple drop-in migration and technology design reuse path to 2G and 3G with any xE910 module
• Over-the-Air firmware update
Designers looking to add LTE capabilities to commercial
and industrial computing devices benefit from the
simple, yet powerful mPICe form factor with the
flexibility to choose another technology best suited for
the application environment from any one of the other
models in the xE910 mPCIe series.
Purpose of this document is providing a detailed specification and a comprehensive listing as a reference for the whole set of AT command for the LE910Cx-series
This document describes the integration steps of the cellular modules USB endpoints in Linux systems.
This archive contains the Windows 10 WHQL certified Telit module drivers for both x86 and x64 system platforms.
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).
What Linux kernel modules and configs are commonly used for communicating with cellular modules over their USB interface?
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:
Configs for Modem/PPP support:
Configs for USB network drivers:
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.
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:
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:
USB endpoint configuration:
Serial port configuration:
Selected network access techniques:
List network operator info:
Network registration status:
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: https://techship.com/technical_support/
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):
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.
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
SAMPLE PRICE $59.00