TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS
The SIMCom SIM7600SA is Multi-Band LTE-TDD/LTE-FDD module solution in a mPCIe form factor. SIM7600SA is a LTE CAT-1 module with support of up to 10Mbps downlink data transfer intended for the Australian, New Zealand and South American markets.
With abundant application capability like TCP/UDP/FTP/FTPS/HTTP/HTTPS/DNS, the module provides much flexibility and ease of integration for customer's application
This document describes the electronic specifications, RF specifications, interfaces, mechanical characteristics and testing results of the SIMCom SIM7600E and SIM7600E-H module. With the help of this document and other software application notes/user guides, users can understand and use module to design and develop applications quickly.
This document describes the hardware of the SIMCom SIM7600* and SIM7600* -H miniPCIe modules.
Simcom SIM7500 series and SIM7600 series AT commands manual
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 archive contains the SIMCOM:
SIM7X00 Series_GPIO_Application Note_V1.00.pdf
SIM7X00 Series_GPS_Application Note_V1.00.pdf
SIM7X00 Series_SAT_Application Note_V1.00.pdf
SIM7X00 Series_Sleep Mode_Application Note_V1.00.pdf
SIM7X00 Series_SMS_Application Note_V1.00.pdf
SIM7X00 Series_TCPIP_Application Note_V1.00.pdf
SIM7X00 Series_UART_Application Note_V1.00.pdf
SIM7100_SIM7500_SIM7600 Series_LBS_Application Note_V1.00.pdf
SIM7100_SIM7500_SIM7600 Series_UIM HOT SWAP_Application Note_V1.01.pdf
SIM7100_SIM7500_SIM7600 Series_USB AUDIO_Application Note_V1.03.pdf
SIM7100_SIM7500_SIM7600_Sleep Mode_Application Note_V1.01.pdf
SIM7100_SIM7600M22 Series_TTS_Application Note_V1.02.pdf
SIM7500_SIM7600 Series_Delta_Package_Update_Application Note_V1.02.pdf
SIM7500_SIM7600_SIM7800 Series_FTPS_AT Command Manual_V1.00.pdf
SIM7500_SIM7600_SIM7800 Series_HTTP_AT Command Manual_V1.00.pdf
SIM7500_SIM7600_SIM7800 Series_MQTT_AT Command Manual_V1.00.pdf
SIM7500_SIM7600_SIM7800 Series_SSL_AT Command Manual_V1.00.pdf
SIM7500_SIM7600_SIM7800 Series_TCPIP_AT Command Manual_V1.00.pdf
SIM7600 Hardware Design Notice V1.02.pdf
This document is a reference guide to all the AT commands defined for FTP(S). Through these FTP AT commands, you can download files from FTP(S) server or upload files to FTP(S) server.
This document is a reference guide to all the AT commands defined for HTTP(S). Through these HTTP AT commands, you can send HTTP GET/POST request to HTTP server and read HTTP response from HTTP server.
This archive contains REACH reports for Simcom SIM7600 and SIM7600 -H series variants cellular modules, both for SMT and miniPCIe variants.
This archive contains ROHS reports for Simcom SIM7600 and SIM7600 -H series variants cellular modules, both for SMT and miniPCIe variants.
This archive contains the SIMcom SIM7500 and SIM7600 series modules Linux base firmware update tool and source code and update 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 Simcom SIM7500 and SIM7600 Series Linux Network NDIS driver installation files and guide on how to install them without rebuilding the kernel.
Please relate to FAQ "How to integrate Simcom SIM7500/SIM7600 Series Linux NDIS driver without rebuilding kernel" for further details.
This archive contains the Windows firmware update tool for SIM7500 and SIM7600-series modules.
Please follow the included instructions regarding usage.
This archive contains the SIMCom SIM7500 - SIM7600 series modules Linux NDIS driver and system integration guide
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.
How-to use automated connection establishment with SIM7600E-h when using RNDIS USB mode
Both Windows and Linux systems can support RNDIS host drivers for the SIM7600 series modules, this example is done in Linux. There is a open source Linux in-kernel driver supporting rndis host USB endpoints called rndis_host.
By default the Simcom modules are delivered with QMI/RMNET interface enabled, so you will have to change the default USB mode with AT command on the Modem/AT serial ports available over USB.
Bus 001 Device 006: ID 1e0e:9001 Qualcomm / Option
Switch from 9001 to mode 9011 for RNDIS:
The module should restart automatically and re-enumerate with the new USB IDs
Check with lsusb that you have the Simcom SIM7600 module loaded, VID PID value: 1e0e 9011
Bus 001 Device 006: ID 1e0e:9011 Qualcomm / Option
Verify with lsusb -t that the Linux in-kernel driver rndis_host or cdc-ecm drivers are loaded correctly for interface 0 and 1.
It can look e.g. like this:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 4: Dev 6, If 3, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 1, Class=CDC Data, Driver=rndis_host, 480M
|__ Port 4: Dev 6, If 6, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 4, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 6, If 0, Class=Communications, Driver=rndis_host, 480M
|__ Port 4: Dev 6, If 5, Class=Vendor Specific Class, Driver=option, 480M
If your system don't load the option serial interfaces correctly, then they can be forcefully loaded as bellow:
echo 1e0e 9011 > /sys/bus/usb-serial/drivers/option1/new_id
See the following Linux kernel commit for details on how to modify the option.c driver in order to auto load the driver:
USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
For the modules network connection and interface to automatically activate you should have the SIM PIN deactivated or script it so host system provides it to module at every startup.
A APN name provided by the network carrier which is used to establish a packet data connection to the cellular network is required. If you define a empty string as its default value, will make the module try to subscribe for correct APN name from network, however this works in many cases but not always. If so it has to be configured with commands as bellow:
Check configured APN profiles:
You should have minimum the following defined to have module try request details from cellular network:
+CGDCONT Profile 1 is used for cellular network registration and profile 6 for the RNDIS network interface data connection.
Define both APN profiles according to the details you have obtained with your cellular subscription. Most often the APN details are same for both registration and data connection, define them to profile 1 and 6.
Some APN names require additional authentication also, please refer to the AT command: AT+CGAUTH in the AT commands guide on how to define it correctly. Current auth configurations can be checked with command:
Most often no auth details are needed for the profiles and they should be empty, profile 1 can be cleared with command:
If you have modified the APN information, username and passwords it is needed to re-attach to the packet switched network or re-register in the cellular network to activate the new settings. It can be done e.g. with AT+CFUN=0 command followed by AT+CFUN=1 to switch module operation mode (SIM card will be re-initialized also so PIN code have to be given again if PIN check activated).
The module will now establish the data connection according to the new settings.
If everything is working correctly and connection established you can now run a dhcp client on the network interface.
dhclient -v usb0
Listening on LPF/usb0/4a:de:a7:7e:46:07
Sending on LPF/usb0/4a:de:a7:7e:46:07
Sending on Socket/fallback
DHCPREQUEST of 192.168.225.46 on usb0 to 255.255.255.255 port 67 (xid=0xaabce35)
DHCPACK of 192.168.225.46 from 192.168.225.1
RTNETLINK answers: File exists
bound to 192.168.225.46 -- renewal in 21475 seconds.
ping -I usb0 188.8.131.52
PING 184.108.40.206 (220.127.116.11) from 192.168.225.46 usb0: 56(84) bytes of data.
64 bytes from 18.104.22.168: icmp_seq=1 ttl=52 time=167 ms
64 bytes from 22.214.171.124: icmp_seq=2 ttl=52 time=37.6 ms
64 bytes from 126.96.36.199: icmp_seq=3 ttl=52 time=44.4 ms
64 bytes from 188.8.131.52: icmp_seq=4 ttl=52 time=33.6 ms
--- 184.108.40.206 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 33.600/70.635/166.972/55.753 ms
Tested on firmware release LE11B12SIM7600M22
Useful Linux kernel configs to have enableb when integrating cellular modules in the Linux kernel
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 either as part of kernel or modules are listed bellow. Many cellular modules base their Linux support on these, either supported out-of-the-box or by applying source code modifications to them.
Configs for USB serial drivers:
Configs for Modem/PPP support:
Configs for USB network drivers:
Please relate to our product specific web pages for vendor details on Linux integration.
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 system and logs from the related Simcom 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 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 can we integrate the Simcom SIM7500/SIM7600 Series Linux NDIS driver in Linux kernel without rebuilding it?
The Simcom SIM7500/SIM7600 series Linux NDIS network driver can be built and installed without rebuilding the complete Linux kernel your OS distribution uses. Please see steps and pre-requirements bellow and download the attached "Simcom SIM7500 and SIM7600 Series Linux Network NDIS driver installation files and guide (without kernel rebuild)" archive to get started.
Should you instead want to include the NDIS driver into your customized Linux kernel build, please relate to "SIMCom SIM7500 - SIM7600 series modules Linux NDIS driver and system integration guide V2.01" attached to the FAQ.
All commands are supposed to be executed with elevated system privileges/as root user.
Ensure that your original kernel was built with the following config options enabled, this will allow the option and usbnet driver pre-requirments to be included in kernel. (usually already included in larger distributions)
Build-tools and Linux header files for your kernel version are also required, these can be installed e.g. through your OS distributions package manager, on Debian/Ubuntu systems:
apt-get install build-essential make gcc
apt-get install linux-headers-`uname -r`
The in-kernel qmi_wwan driver should be blacklisted and prevented from loading as it will block the Simcom wwan driver, this is how it can be done e.g. in Ubuntu systems:
grep -q -F 'blacklist qmi_wwan' /etc/modprobe.d/blacklist-modem.conf || echo 'blacklist qmi_wwan' >> /etc/modprobe.d/blacklist-modem.conf
Build and install the driver:
Unzip the archive and copy the folder sim7600 to your selected working directory.
Navigate to it, e.g.:
Build and install the drivers:
Some warnings might appear, but verify that no errors are reported.
Restarting the host system should now result in the correct network drivers being loaded for the cellular module once the USB device is detected in the system.
It can be verified by finding lsusb -t listing "Driver=simcom_wwan" for a USB endpoint:
Bus 001 Device 005: ID 1e0e:9001 Qualcomm / Option
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 5, If 1, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 5, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 5, If 3, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 5, If 4, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 4: Dev 5, If 5, Class=Vendor Specific Class, Driver=simcom_wwan, 480M
dmesg | grep 'simcom_wwan'
simcom_wwan 1-4:1.5 wwan0: register 'simcom_wwan' at usb-0000:00:15.0-4, SIMCOM wwan/QMI device, 8a:d8:ff:c2:87:11
Additional make options and information:
If you've built the driver previously already, first clean out any old builds with:
If you only want to build the driver but not install it into /lib/modules/`uname -r`/kernel/drivers/net/usb/, use make without install parameter:
Testing of the cellular connection can easily be done by first performing the necessary initiation AT commands to the cellular module over Modem/AT commands serial interface normally located on /dev/ttyUSB2. Use e.g. minicom tool to communicate with it.
Can be installed e.g. through the distributions package manager:
apt-get install minicom
Access the serial interface:
minicom -D /dev/ttyUSB2
Please relate to AT commands guide for full details on what commands are supported.
Issue AT and check that you get OK as reply.
Enable echo on characters sent to module:
Request general info about module:
Enter the SIM pin code (if necessary for SIM card)
Enter your operators APN details:
Enter APN authentication details (if necessary) further details found in the AT commands guide.
Check network registration:
Activate and connect the cellular data connection to the network interface installed in Linux system:
When you get the reply $QCRMCALL: 1, V4 from cellular module it means that the data connection to your network operator is fully established and you can now exit the minicom tool (CTRL+A followed by Z key and Q key and select yes to exit).
Once here you can now perform a DHCP request on the cellular network interface in the Linux system by using your favorite DHCP client in Linux e.g. dhclient or udhc e.g.:
dhclient -v wwan0
The cellular network interfaces are normally named starting from wwan0 but might get renamed by some Linux distributions automatically. All available network interfaces can be listed with command:
ip link show
The network interface can be tested e.g. by sending ping requests to a remote server over the selected network interface:
ping -I wwan0 220.127.116.11
PING 18.104.22.168 (22.214.171.124) from 10.163.183.209 wwan0: 56(84) bytes of data.
64 bytes from 126.96.36.199: icmp_seq=1 ttl=120 time=191 ms
64 bytes from 188.8.131.52: icmp_seq=2 ttl=120 time=46.1 ms
64 bytes from 184.108.40.206: icmp_seq=3 ttl=120 time=52.8 ms
64 bytes from 220.127.116.11: icmp_seq=4 ttl=120 time=43.3 ms
--- 18.104.22.168 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 43.350/83.407/191.281/62.376 ms
Technology / Antenna Frequency: GSM 850/900/1800/1900, UMTS 2100, Wifi/Bluetooth 2400 | Mounting method: Other | Antenna Location: Internal | VSWR: 2 :1 | Gain: 0 dBi | Connector Type: IPEX MHF/U.FL | Impedance: 50 Ohm | Cable length: 10.5 cm | Polarization: Vertical | Radiation pattern: Omnidirectional | Max power: 25 W | Operating Temperature Range: -40 °C – 85 °C | Width: 22 mm | Length: 62 mm | Height: 2.7 mm
SAMPLE PRICE $6.70