S2-106S0-Z1X06
Supplier number:
SIMCom SIM5300E is a Dual-Band HSPA/WCDMA and Dual-Band GSM/GPRS/EDGE module in a SMT type which supports HSPA up to 7.2Mbps for downlink and 5.76Mbps for uplink data transfer. It has strong extension capability with rich interfaces including UART, USB2.0, SPI, I2C, etc. With abundant application capability like TCP/UDP/PPP, the module provides much flexibility and ease of integration for your application.
SIMCom SIM5300E Datasheet
This document describes the AT command set for the SimCom SIM5300E module.
Document summarizing and describing the GPS systems epoch roll over dates in Simcom products GPS trackers and how to take precaution for it.
This document describes how to use UART interfaces of SIMCom SIM5300E and SIM5300EA modules.
This archive contains application notes for the SimCom SIM5360 3G cellular modules:
How to use linux driver.pdf
SIM5320 TO SIM5360 MIGRATION GUIDE_Application Note_V1.01.pdf
SIM5360_Audio_Application_Note_V1.01.pdf
SIM5360_Automatic_Power_On_Application_Note_V0.01.pdf
SIM5360_CSD_Application_Note_V0.01.pdf
SIM5360_Current_Leakage_Application_Note_V0.01.pdf
SIM5360_DDET_Application_Note_V0.02.pdf
SIM5360_Delta_Package_Update_Application_Note_V0.01.pdf
SIM5360_EBDAT_Application_Note_V0.01.pdf
SIM5360_ECALL_Application Note_V0.04.pdf
SIM5360_Email_Application_Note_V0.01.pdf
SIM5360_FTP_Application_Note_V0.01.pdf
SIM5360_GPIO_Application_Note_V0.03.pdf
SIM5360_GPS_Application_Note_V0.02.pdf
SIM5360_GPS_Assist_Location_Application_Note_V0.01.pdf
SIM5360_HTTP_Application_Note_V0.01.pdf
SIM5360_Internet_Service_Application_Note_V0.01.pdf
SIM5360_Keypad_Application_Note_V0.01.pdf
SIM5360_LUA_Application_Note_V0.05.pdf
SIM5360_MMS_Application_Note_V0.01.pdf
SIM5360_Network_Cell_Info_Application_Note_V0.01.pdf
SIM5360_SAT_Application_Note_V0.01.pdf
SIM5360_Sleep_Mode_Application_Note_V0.02.pdf
SIM5360_SMS_Application_Note_V0.01.pdf
SIM5360_SPI_Application_Note_V0.01.pdf
SIM5360_SSL_Application_Note_V0.01.pdf
SIM5360_TCPIP_Application_Note_V0.01.pdf
SIM5360_TTS_Application_Note_V0.01.pdf
SIM5360_UART_Application_Note_V0.05.pdf
SIM5360_UART_Multiplexer_Application_Note_V0.01.pdf
SIM5360_USB_AUDIO_Application_Note_V1.01.pdf
SIM7100_SIM5360_SIM800 Compatible Design_V1.01.pdf
This manual gives general guidelines worth considering when designing and selecting main and diversity antennas for cellular applications.
This document is a brief description on how to modify, build and use the driver on Linux issued by Linux kernel in order to use SIMCom 3G modules.
This document describes how to use the internal TCPIP stack of SIM5300E through AT commands.
RED NB certificate for SimCom SIM5300E
CE Certificate for SimCom SIM5300E
USB driver and Windows updating tool for SIMCom SIM5300E cellular module.
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.
Archive containing SimCom SIM5300E 1551B06SIM5300E firmware and release notes.
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:
-Model
-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:
uname -a
lsusb
lsusb -t
ifconfig -a
ls -l /dev/serial/by-id
ls -l /sys/bus/usb-serial/devices
dmesg
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:
AT
Command echo enabled:
ATE1
Basic module info:
ATI
Detailed module version info:
AT+SIMCOMATI
Verbose error reporting:
AT+CMEE=2
Last error report:
AT+CEER
Firmware version:
AT+CGMR
AT+CSUB
IMEI Code:
AT+CGSN
USB endpoint configuration:
AT+CUSBPIDSWITCH?
List current configuration:
AT&V
Operational mode:
AT+CFUN?
Pin status:
AT+CPIN?
Request UE system info:
AT+CPSI?
Preferred network mode:
AT+CNMP?
Preferred band selection:
AT+CNBP?
Preferred acquisition order:
AT+CNAOP?
List network operator info:
AT+COPS?
Network registration status:
AT+CREG?
Network EPS registration status:
AT+CEREG?
Signal strength:
AT+CSQ
Packet domain attach status
AT+CGATT?
List APN details/PDP profiles:
AT+CGDCONT?
AT$QCPDPP?
PDP profiles attach status:
AT+CGACT?
Show PDP IP address:
AT+CGPADDR
AT+CGCONTRDP
RM network interface status:
AT$QCRMCALL?
The support ticket can be created after login at: https://techship.com/technical_support/
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:
CONFIG_USB_SERIAL
CONFIG_USB_SERIAL_GENERIC
CONFIG_USB_SERIAL_WWAN
CONFIG_USB_SERIAL_OPTION
CONFIG_USB_SERIAL_QUALCOMM
CONFIG_USB_ACM
Configs for Modem/PPP support:
CONFIG_PPP
CONFIG_PPP_BSDCOMP
CONFIG_PPP_DEFLATE
CONFIG_PPP_FILTER
CONFIG_PPP_MPPE
CONFIG_PPP_MULTILINK
CONFIG_PPPOE
CONFIG_PPP_ASYNC
CONFIG_PPP_SYNC_TTY
Configs for USB network drivers:
CONFIG_USB_USBNET
CONFIG_USB_NET_QMI_WWAN
CONFIG_USB_NET_CDCETHER
CONFIG_USB_NET_RNDIS_HOST
CONFIG_USB_NET_CDC_NCM
CONFIG_USB_NET_HUAWEI_CDC_NCM
CONFIG_USB_NET_CDC_MBIM
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.