TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS
SIMCom presents an ultra compact and reliable wireless module SIM7100E which is based on Qualcomm MDM9215 multiple-mode LTE platform. SIM7100E is a complete multi-band TDD-LTE/FDD-LTE/WCDMA/GSM/GNSS SMT type module designed with very powerful processors integrating application core: CortexTM A5(550MHz),three QDSP6 cores (Up to 500Mhz), allowing customer to benefit from small dimensions and cost-effective product solutions.
It has strong extension capability with rich interfaces including UART, USB2.0, SPI, I2C,Keypad, PCM, etc. With abundant application capabilities like TCP/UDP/FTP/FTPS/HTTP/HTTPS/SMTP/POP3 and MMS, the module provides much flexibility and ease of integration for customer’s applications.
To develop applications and to test the mPCIe module separately the article 10069 Techship MiniPCIe Developer Kit incl. Technical support could be very helpful
Please note the firmware version below.
This document describes the electronic specifications, RF specifications, interfaces, mechanical characteristics and testing results of the SIMCom SIM7100 miniPCIe modules. With the help of this document and other related software application notes/user guides, users can understand and use SIM7100-PCIE modules to design and develop applications quickly.
AT Commands manual for SIMCOM SIM7100 series cellular modules
This Application Note PDF document describes how the USB Voice/Audio feature for Simcom SIM7x00 series modules.
This manual gives general guidelines worth considering when designing and selecting main and diversity antennas for cellular applications.
This PDF document describes the Audio Application for SIM7X00 series modules.
This guide explains how to make a NDIS connection using the SIM7100 in Linux.
Datasheet for SimCom SIM7100 European version. This document includes an overview of SIM7100 and it's features. For more detailed technical information, see the SimCom SIM7100 Hardware Design guide.
This archive contains application guides for the module SIM7100. These guides will give the user information about how to use the functions of the module. Contains guides for CDC, Delta package update, ECALL, Email, FTP, GPIO, GPS, HTTP, Internet Service, MIFI, MMS, Network Cell Info, SAT, Sleep Mode, SMS, TCPIP, UART, USB Audio and ECALL AT Commands.
Datasheet for SimCom SIM7100 mPCIe European version. This document includes an overview of SIM7100E mPCIe and it's features. For more detailed technical information, see the SimCom SIM7100 Hardware Design guide.
This archive contains the Windows operating system drivers for the SIM7xxx series Qualcomm chipset based cellular modules. Please refer to the included PDF manual for installation instructions for each system and USB endpoint selection.
This archive contains the RIL library and drivers for Android versions 4.0, 4.2, 4.4, 5 ,6 ,7 and 8
Included is also the related user guide.
This archive contains the Windows firmware update tool for SIM53-series, SIM7-series and SIM89-series modules.
Please follow the included instructions regarding installation and usage.
This archive contains the Simcom SIM7100 series Linux firmware update tools and related step by step guide applying the firmware update.
This archive contains the firmware update tool, QPST tool and a firmware upgrade guide. Please follow instructions carefully.
This archive contains the Qualcomm Product Support Tools V.2.7.438.3 for SimCom SIM7-series modules.
This archive contains the Simcom SIM7100 QMI NDIS Linux driver and installation manual.
This archive contains the SIM7100E B07 version firmware and related release notes.
This archive contains the SIM7100E B06 version firmware and related release notes.
This archive contains the firmware updater and the release notes for the module SIM7100E that will update the module to firmware 4534B05SIM7100E.
This archive contains the firmware updater and the release notes for the module SIM7100E that will update the module to firmware 4534B03SIM7100E.
How to collect initial diagnostics data and logs for Simcom cellular modules, needed when requesting Techship technical support?
In order to troubleshoot and solve a technical problem, we ask you to please provide information about your host system and logs from the related Simcom module when creating a technical support ticket.
Detailed problem description and in what situations it present or can be reproduced.
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 mandatory)
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 the cellular module firmware can be acquired by accessing the USB enumerated serial (COM) interfaces accepting AT commands. They can be named modem, AT, PC UI etc. (In Windows device manager, found under modem or serial interfaces). Send the following AT commands bellow to module and capture the output and include them when creating the the technical support ticket.
Test that you get a reply with command:
Command echo enabled:
Basic module info:
Detailed module version info:
Verbose error reporting:
Last error report:
USB endpoint configuration:
List current configuration:
Request UE system info:
Preferred network mode:
Preferred band selection:
Preferred acquisition order:
List network operator info:
Network registration status:
Network EPS registration status:
Packet domain attach status
List APN details/PDP profiles:
PDP profiles attach status:
Show PDP IP address:
RM network interface status:
The support ticket can be created after login at: https://techship.com/technical_support/
How-to change the cellular modulesUSB composition mode to Mobile Broadband Interface Model (MBIM) used by Windows 8 and 10 systems for controlling and establishing data connectivity through the built-in connection manager in Windows?
This is done by sending a set of AT commands to the cellular modules Modem or AT serial interface found in Windows Device Manager. Please see list below for associated AT commands.
(For additional details, refer to the product specific software, ports, and AT commands guides found on the Techship product web pages under technical documentation tab).
After the AT commands have been received by the module and has restarted, the USB interface endpoint composition should have changed to include MBIM interface as well.
You can find the correct Serial COM port number by checking 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.
Vendor specific commands to use:
Sierra Wireless EM75xx series module:
Sierra Wireless EM74xx, MC74xx series module:
Sierra Wireless EM73xx, MC73xx series module:
Simcom SIM7100, SIM7500 and SIM7600 series modules:
ZTE Welink ME3630 series:
Telit LE910C1 and LE910C4 series:
Telit LM940 and LM940A11:
Telit LM960 and LM960A18:
Telit LE910 V2 series:
On Huawei and Telit LN94x series modules the USB mode changing is done automatically by the modules Windows drivers based on current Windows version.
Please be aware that some USB mode configurations do not include any serial interfaces, making it impossible to revert the changes using AT commands.
How can we establish data connection for cellular modules in Windows 8 and Windows 10 systems?
Microsoft Windows desktop versions starting from Windows 8 and newer have built in data connection manager for WWAN, Wifi etc. that can be used to configure, control and establish the data connection of cellular module that support MBIM interface, which most cellular modules do.
The connection managers settings and controls can be found and accessed on Windows desktop start menu through the network icon (see picture).
The Cellular tab can be found in Windows system settings and if needed the connection APN details can be manually entered through "Advanced options".
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 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: 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:
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:
The cellular modules QMI control interface are usually named cdc-wdm* e.g.:
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:
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 220.127.116.11
The ifconfig Linux tool can show the current details for the network interface:
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.
How do we configure the Simcom SIM7100, SIM7500 and SIM7600 series cellular modules for usage in Windows 8 and 10 systems and support Windows built-in connection manager?
The Simcom modules comes default set in a USB configuration used by Linux and Windows 7 systems. If you want the module to be fully supported in Windows 8, 8.1, 10 systems and later and take advantage of the Windows integrated connection manager you have to do a one time configuration and set the module to expose Mobile Broadband Interface Model (MBIM) interface as bellow:
Start by installing the latest Simcom SIM7 series Windows drivers (instructions included in download package). They can be found on on our dedicated product web pages.
In Windows device manager you can now find a serial interface called "SimTech HS-USB AT Port 9001 (COM5)" Memorize the COM* interface number in your system.
Open a command prompt with admin rights (right click Windows icon in bottom left corner). Copy and paste the command bellow, edit port number to match the one in your system and hit enter. The command will then be sent to module overt the serial interface.
ECHO AT+CUSBPIDSWITCH=9004,1,1 >\\.\COM5
If the command is received successfully by module, a restart of the cellular module will be performed and it appears with the new USB endpoints supporting Windows 8 systems and later.
Make sure that all Simcom module end points are correctly loaded in Windows device manager, a system restart might be necessary also.
By clicking the Windows network connection symbol in the start bar or navigating to the "Cellular" topic in Windows system settings you can now activate the connection and configure APN details and enter PIN code if it is necessary for the cellular connection and subscription you have.
How can I enable DC voltage output for active GPS/GNSS antennas on modules that support this feature?
The 3 volt DC Low Noise Amplifier voltage supply from the cellular module can be enabled according to AT commands bellow:
For Sierra Wireless EM/MC74 series:
For Sierra Wireless MC73 series:
For Simcom SIM7100, SIM7500, SIM7600 and SIM7600 -H series:
Technology / Antenna Frequency: Wifi/Bluetooth 2400, Wifi 5000 | VSWR: 2 :1 | Gain: 1 dBi | Connector Type: IPEX MHF/U.FL | Impedance: 50 Ohm | Cable length: 10 cm | Cable Specification: 1.13 mm coax | Polarization: Vertical, Linear | Operating Temperature Range: -10 °C – 55 °C | Width: 25 mm | Length: 45 mm
SAMPLE PRICE $6.70
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, LTE 698-960/1710-2170/2500-2700 MHz | Mounting method: Adhesive | Antenna Location: External | VSWR: 3 :1 | Gain: 2.14 dBi | Connector Type: SMA-M | Impedance: 50 Ohm | Cable length: 30 cm | Cable Specification: RG174 | Polarization: Linear | Max power: 35 W | Operating Temperature Range: -40 °C – 85 °C | Width: 60 mm | Length: 112.5 mm | Height: 11.3 mm
SAMPLE PRICE $6.80
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, LTE 698-960/1710-2690, Wifi/Bluetooth 2400 | Mounting method: Screw, Other | Antenna Location: Internal | VSWR: 2 :1 | Gain: 2.14 dBi | Connector Type: IPEX MHF/U.FL | Impedance: 50 Ohm | Cable length: 10 cm | Polarization: Linear | Max power: 25 W | Operating Temperature Range: -40 °C – 85 °C | Width: 8.5 mm | Length: 113 mm | Height: 113 mm
SAMPLE PRICE $6.70
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, Wifi/Bluetooth 2400, LTE 790-960/1710-2690 | Mounting method: Connector | Antenna Location: External | Connector Type: SMA-M | Impedance: 50 Ohm | Polarization: Vertical | Max power: 50 W | Width: 21 mm | Length: 157 mm | Height: 157 mm
SAMPLE PRICE $7.30
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, LTE 698-960/1710-2690, Wifi/Bluetooth 2400 | Mounting method: Other | Antenna Location: Internal | VSWR: 3 :1 | Gain: 2.14 dBi | Connector Type: IPEX MHF/U.FL | Impedance: 50 Ohm | Cable length: 12 cm | Polarization: Linear | Max power: 35 W | Operating Temperature Range: -40 °C – 85 °C | Width: 52 mm | Length: 112.5 mm | Height: 105 mm
SAMPLE PRICE $6.80
UMTS Bands: B1 (2100), B2 (1900), B8 (900), B5 (850) | MIMO (Multiple-Input Multiple-Output): Yes | LTE Bands: B1 (2100), B2 (1900), B3 (1800), B4 (AWS), B7 (2600), B8 (900), B20 (800DD), B5 (850) | GSM/EDGE Bands: B5 (850) , B8 (900), B3 (1800), B2 (1900) | Manufacturer: Huawei | LTE Region: Europe, Asia | FOTA Firmware Updates: Yes | Form Factor: mPCIe - full size | Technology: LTE - cat 4 | Antenna Interface: IPEX MHF/U.FL | GPS: No | GNSS technology: | Max DL Speed: 150 Mbps | Max UL Speed: 50 Mbps | Chipset: Hisilicon, Balong 711 | Operating Temperature Range: -40 °C – 85 °C | Driver Support: Windows 7, Linux, Android, Windows 8, Windows CE, Windows Mobile, Windows 8.1 | Interface: USB 2.0 | Voice Call Support: Yes | SIM interface: Through miniPCIe connector | GPIO: No | Extended Operating Temperature Range: -40 °C – 85 °C | Audio interface: Digital PCM signal input/output in socket | Certification: CE, RoHS, GCF, WEEE, CE RED
SAMPLE PRICE $59.00