TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register
Product list
Quantity Sample Price
≥ 1 $58.90
≥ 1 €53.00

For larger quantities and complete pricing, please sign in or register

Do you need offline data on this product?

Download datasheet

Subscribe to stay up to date with the latest about this product.

Subscribe to updates
LTE Region
North America
LTE Bands
B2 (1900)
B4 (AWS)
B12 (700ac)
UMTS Bands
B2 (1900)
B5 (850)
Manufacturer
SimCom
Form Factor
mPCIe
Technology
LTE - cat 4
Antenna Interface
IPEX U.FL
GPS
Yes
GNSS technology
GPS
GLONASS
MIMO (Multiple-Input Multiple-Output)
Yes
Max DL Speed
150 Mbps
Max UL Speed
50 Mbps
Chipset
Qualcomm
Driver Support
Windows 8.1
Windows 8
Windows
Android
Linux
Windows 7
Windows 10
Interface
USB 2.0
Operating Temperature Range
-40 °C – 85 °C
Certification
FCC
RoHS
PTCRB
Voice Call Support
Yes
Voice call interface
Analog signal input/output in socket
GNSS antenna support
Passive
Active
FOTA Firmware Updates
No
SIM interface
Through miniPCIe connector

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
SIM7X00_Audio_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_SIM7600M22 Series_TTS_Application Note_V1.02.pdf
SIM7500_SIM7600 Series_Compatibility_With_SIM800_HTTP_ATC_V1.00.pdf
SIM7500_SIM7600 Series_MQTT_ATC_V1.01.pdf
SIM7600 Hardware Design Notice V1.02.pdf
SIM7600 Series_HSIC_LAN_Application_Note_V1.00.pdf
SIM7600M22_MIFI_Application Note_V1.00.pdf
SIM7600M22_MIFI_RTL_Application Note_V1.00.pdf
SIM7600_USB-OTG_Application_Note_V1.00.pdf

Download

This document describes the hardware of the SIMCom SIM7600* and SIM7600* -H miniPCIe modules.

Download

Datasheet document for the SIM7600x -H series LTE cat4 modules.

Download

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.

Download

FCC Grant of Equipment Authorization for Simcom SIM7600A-H variants

Download

Uploaded at
2018-08-14 13:30:08
Last updated
2018-08-14 13:42:04
Related products
SIMCom SIM7600A-H LTE CAT-4 Audio US
SIMCom SIM7600A-H CAT-4 mPCIe US

AT&T Network Operator Compatibility Approval Notice for Simcom SIM7600A-H variants

Download

Uploaded at
2018-08-14 13:36:36
Last updated
2018-08-14 13:40:23
Related products
SIMCom SIM7600A-H CAT-4 mPCIe US
SIMCom SIM7600A-H LTE CAT-4 Audio US

PTCRB certificate for the Simcom SIM7600A-H variants

Download

Uploaded at
2018-08-14 13:26:36
Last updated
2018-08-14 13:26:36
Related products
SIMCom SIM7600A-H LTE CAT-4 Audio US
SIMCom SIM7600A-H CAT-4 mPCIe US

This Zip archive contains the Windows operating system drivers for the SIM7xxx series modules. Please refer to the included PDF manual for installation instructions for each system and USB endpoint selection.

Download

Question

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?

Solution

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.

Question

How can we use Simcom SIM7500 and SIM7600 series in Linux with the MBIM control and data interface over USB connectivity?

Solution

The Simcom SIM7500 and SIM7600 series cellular module can expose the Mobile Broadband Interface Model (MBIM) Interface.

There is a open source Linux in-kernel driver supporting MBIM interface and it is called cdc_mbim. The library libmbim can be used to communicate with the cellular devices over the interface and do necessary configurations to trigger the data connection over the cellular network.

First install the libmbim Linux library using your system package manager like apt etc. (more details about libmbim here: https://www.freedesktop.org/wiki/Software/libmbim/)

First check with lsusb that you have the Simcom module set to expose MBIM interface, this can be verified with command lsusb and you should the vid:pid value 1e0e:9003.
lsusb
Bus 001 Device 003: ID 1e0e:9003 Qualcomm / Option

If this is not the case, you will have to change what USB end points the cellular module exposes and the vid:pid values. This can be done through AT commands sent to one of the modules serial interfaces accepting AT commands. dev/ttyUSB2 is often the correct one.
AT+CUSBPIDSWITCH=9003,1,1

Applications like Minicom or Picocom can be used to send AT commands over the serial interfaces.

Should you have no serial interfaces loaded, it is because the driver has not been loaded for the USB serial endpoints due to missing vid:pid values in the option driver, you can then use the commands bellow to temporarily load the driver for the vid:pid combination the module expose. e.g:
modprobe option
echo 1e0e 9001 > /sys/bus/usb-serial/drivers/option1/new_id

After you have changed the cellular modules USB endpoint configuration to expose MBIM interface, you can verify with lsusb -t that the Linux in-kernel cdc_mbim driver is correctly loaded for the cellular module. It can look e.g. like this:
lsusb -t
...
|__ Port 4: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 3, If 6, Class=CDC Data, Driver=cdc_mbim, 480M
|__ Port 4: Dev 3, If 4, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 3, If 5, Class=Communications, Driver=cdc_mbim, 480M
|__ Port 4: Dev 3, If 3, Class=Vendor Specific Class, Driver=, 480M

if you have no option drivers loaded for the serial interfaces, these can be loaded temporarily with commands:
modprobe option
echo 1e0e 9003 > /sys/bus/usb-serial/drivers/option1/new_id

Using libmbim with the command line interface mbimcli:
List all available options for mbimcli:
mbimcli --help-all

Check version
mbimcli --version

The cellular modules mbim interface is usually named cdc-wdm* among the devices. For mbimcli this is defined by --device=/dev/cdc-wdm0 parameter. You should also use the proxy function to enable parallel commands to be sent to module even if the interface already is in use by a data connection. This is done by including --device-open-proxy or -p in every mbimcli requst to module.
Command example to query device capabilities and information (firmware & IMEI code etc.):
mbimcli --device=/dev/cdc-wdm0 --device-open-proxy --query-device-caps

The libmbim tool: mbim-network can be used to establish a simple data connection.
First create a config file containing your network operators APN details. Save it in the default location where mbim-network searches for the file: /etc/mbim-network.conf .
The parameter --profile=[PATH] can be used to alter this path when executing mbim-network.

Save the APN details, (and username, password and authentication type if necessary) into the configuration file:
APN=
APN_USER=
APN_PASS=
APN_AUTH=
PROXY=yes

How to start a data connection after configuration file is in place:
Enter SIM PIN (if necessary for SIM card):
mbimcli -d /dev/cdc-wdm0 -p --enter-pin=1234

Start the mbim data connection with command bellow, if successful it will print "Network started successfully"
mbim-network /dev/cdc-wdm0 start

You can now execute the mbim-set-ip script (download found bellow related to this FAQ) with sufficient system privileges:
./mbim-set-ip /dev/cdc-wdm0 wwan0

This script will collect the network interface IP configurations from the cellular module over MBIM interface using mbimcli, parse them and apply them to the network interface in Linux, this because DHCP requests are generally not supported over MBIM interfaces.

Once you have started the data connection and set the details with the mbim-set-ip script you should be able to ping the data connection:
IPv4 ping: (only supported if IPv4 address was acquired from cellular module)
ping -4 -I wwan0 8.8.8.8
ping -4 -I wwan0 google.com

IP v6 ping: (only supported if IPv6 address was acquired from cellular module)
ping -6 -I wwan0 2001:4860:4860::8888
ping -6 -I wwan0 google.com

The cellular data connection can be disconnected by commands:
Stop mbim data connection:
mbim-network /dev/cdc-wdm0 stop
Set network interface down:
ip link set wwan0 down

Other useful commands:
Query device capabilities and information (firmware & IMEI code etc.):
mbimcli -d /dev/cdc-wdm0 -p --query-device-caps

Query SIM card information:
mbimcli -d /dev/cdc-wdm0 -p --query-subscriber-ready-status

Query network registration state:
mbimcli -d /dev/cdc-wdm0 -p --query-registration-state

Query connection ip information:
mbimcli -d /dev/cdc-wdm0 -p --query-ip-configuration=0

Test setup:
Software: Ubuntu server 18.04 LTS with kernel 4.15.0-23-generic and mbimcli 1.14.2
Hardware: SIM7600E-h miniPCIe firmware LE11B08SIM7600M22 on Aaeon UP Squared host board

Question

How do we enable basic standalone GPS tracking with the SIMcom cellular modules that include GNSS tracking feature?

Solution

The SIM7100 series, SIM7500 series SIM7600 series and SIM7600 -H series cellular modules that include a GNSS tracker can be used to acquire current accurate location data with and active or passive GNSS antenna connected to the module.

Details of the available AT commands related to GNSS functionality are described in the AT command reference manuals under GPS section. The AT command reference manuals can be found under our product web pages under technical documentation tab.

Depending on if an GNSS antenna with or without low noise amplifier (active/passive antenna) are used, the AT+CVAUXV and AT+CVAUXS command can be used to adjust if the antenna power supply of 3 VDC should be enabled or disabled on the GNSS antenna connector.

Module configured for active GNSS antenna with 3VDC power supply enabled directly from module:
AT+CVAUXV=3050
AT+CVAUXS=1

Module configured for passive GNSS antenna and antenna voltage supply from cellular module is disabled:
AT+CVAUXS=0

A basic standalone GNSS tracking session outputting the location data on the dedicated NMEA virtual serial interface can be started with the following AT command:
AT+CGPS=1,1

Other useful commands:
(Please note that GNSS configuration parameters can only be changed when tracking is not active)

Stop ongoing GNSS tracking:
AT+CGPS=0

Clear GNSS fix related data stored in module:
AT+CGPSDEL

Set minimum accuracy threshold in meters for location fix (default value 50 meters):
AT+CGPSHOR=50

Enable autostart of GNSS tracking at module start up:
AT+CGPSAUTO=1

The latest GNSS fix can also be requested by AT command:
AT+CGPSINFO
And the output is in the form:
+CGPSINFO: [lat],[N/S],[log],[E/W],[date],[UTC time],[alt],[speed],[course]

For details on how to configure the GPS for different application and scenarios, such as using Assisted GPS, or changing output formats etc. please relate to the AT commands reference manuals for the specific SIMcom module.

Question

How to change USB composition mode to Mobile Broadband Interface (MBIM) that is used by Windows 8 and 10 systems for data connectivity and enabling support for the built-in connection manager in Windows?

Solution

This is done by sending AT commands to the Modem or AT serial interfaces that are accepting AT commands and changing the USB endpoint composition:

Sierra Wireless EM74xx, MC74xx series module:
AT!ENTERCND=”A710”
AT!USBCOMP=1,1,100D
AT!RESET

Sierra Wireless EM73xx, MC73xx series module:
AT!ENTERCND=”A710”
AT!UDUSBCOMP=8
AT!RESET

Simcom SIM7xxx series modules:
AT+CUSBPIDSWITCH=9003,1,1
AT+CRESET

ZTE Welink ME3630 series:
AT+ZSWITCH=8
AT+ZRST

Telit LM940:
AT#USBCFG=2
AT#REBOOT

Telit LE910x V2:
AT#USBCFG=3
AT#REBOOT

On Huawei modules the USB mode changing is done automatically by the Windows drivers and otherwise defaults to the modules standard endpoint interfaces.

Question

How to collect initial diagnostics data and logs for Simcom 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 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:
-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
Module model:
AT+CGMM
Firmware version:
AT+CGMR
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?
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/