TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS
SIMCom SIM7020E is a Multi-Band NB-IoT module solution in a SMT format for the European market. It has strong extension capability with rich interfaces including UART, GPIO etc.
The package of SIM7020 is compatible with SIM800C.
It is designed for applications that need low latency, low throughput data communication in a variety of radio propagation conditions. It is ideally suited for M2M applications, such as metering, asset tracking, remote monitoring, E-health etc.
● With Power Save Mode(PSM) and Extended Discontinuous Reception(eDRX), SIM7020
can extend battery life to 10 years
● SIM7020 provides deeper coverage enhancement compared to GSM
● The package and AT commands of SIM7020 mostly are compatible with SIM800C.
Also see SIMCom's developer kit for SIMCom SIM7020E .
This document is targeted for customers to understand the differences between SIM7080G and SIM7020X. Users can use SIM7080G or SIM7020X module to design and develop applications quickly.
The SIM7020X series include SIM7020C, SIM7020E and SIM7020G.
This manual describes the AT commands valid for controlling the Simcom SIM7000 Series modules.
Document summarizing and describing the GPS systems epoch roll over dates in Simcom products GPS trackers and how to take precaution for it.
SimCom SIM7020-series archive containing Ayla,CoAP, CTBURST, EAT, FOTA, HTTP, Low Power Mode, LWM2M, MQTT, NVRAM, SAT, SNTP, TCPIP, NIDD and TLS application notes.
This archive contains the windows based firmware update tool and usage guide for Simcom SIM7020 series cellular modules.
This archive contains the Microsoft Windows serial drivers for the MediaTek chipset based SIM7020 series modules where drivers are not automatically detected. Microsoft Windows 7, Vista, XP and older.
Firmware update binary archive and release notes for Simcom SIM7020E module
This archive contains the SIM7020E B12 version firmware and related release notes.
This archive contains the SIM7020E B11 version firmware and related release notes.
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.