TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS

Register
FAQs /

Recently added

Question

How to collect initial diagnostics data and logs for Telit LN940 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 Telit 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 required also)

The logs from module firmware can be acquired by accessing one of the USB enumerated serial (COM) interfaces accepting AT commands. (In Windows this is generally modem devices or AT commands serial interfaces). Send the following commands to module and capture the text output and include them when creating the the technical support ticket.

AT
Verbose error reporting:
AT+CMEE=2
Module model:
AT+CGMM
Firmware version:
AT+CGMR
IMEI Code:
AT+CGSN
USB endpoint configuration:
AT#USBCFG?
Serial port configuration:
AT#PORTCFG?
Operational mode:
AT+CFUN?
Selected network access techniques:
AT+WS46?
List network operator info:
AT+COPS?
Network registration status:
AT+CREG=2
AT+CREG?
AT+CGREG?
Signal strength:
AT+CSQ
Last serving cell network information:
AT#SERVINFO
Current network status:
AT#RFSTS
List APN details:
AT+CGDCONT?
Attach UE to default PDP Context:
AT+CGATT=1
List default data connection details:
AT+CGCONTRDP=1
List IP addresses:
AT+CGPADDR=

Question

How to activate the data connection for Huawei cellular modules over the USB network interface in Linux?

Solution

The first step is to assure that the Huawei cellular module is properly loaded in the Linux system. Huawei modules are most often automatically detected in recent Linux kernels, this can be verified in different ways by commands bellow:

The lsusb command shows what physical USB devices are detected in the Linux operating system:
lsusb
Bus 001 Device 003: ID 12d1:15c1 Huawei Technologies Co., Ltd.

The lsusb -t command shows the USB endpoints exposed by the detected USB devices and the related drivers loaded for them:
lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 3, If 0, Class=Communications, Driver=cdc_ether, 480M
|__ Port 1: Dev 3, If 1, Class=CDC Data, Driver=cdc_ether, 480M
|__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 1: Dev 3, If 3, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 1: Dev 3, If 4, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 1: Dev 3, If 5, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 1: Dev 3, If 6, Class=Vendor Specific Class, Driver=option, 480M

The dmesg lists all the driver loading logs since system boot up:
dmesg
usb 1-1: new high-speed USB device number 3 using ehci-pci
usb 1-1: New USB device found, idVendor=12d1, idProduct=15c1
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: HUAWEI Mobile V7R11
usb 1-1: Manufacturer: Huawei Technologies Co., Ltd.
usb 1-1: SerialNumber: 0123456789ABCDEF
cdc_ether 1-1:2.0 usb0: register 'cdc_ether' at usb-0000:02:03.0-1, CDC Ethernet Device, 02:1e:10:1f:00:00
option 1-1:2.2: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
option 1-1:2.3: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
option 1-1:2.4: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
option 1-1:2.5: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
option 1-1:2.6: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
cdc_ether 1-1:2.0 ens35u1c2: renamed from usb0
IPv6: ADDRCONF(NETDEV_UP): ens35u1c2: link is not ready
cdc_ether 1-1:2.0 ens35u1c2: kevent 12 may have been dropped

The command ifconfig -a will list all network interfaces loaded in the Linux system, the cellular module interface can be named differently depending on the distribution used but generally named wwan0 initially.
ifconfig -a
ens35u1c2 Link encap:Ethernet HWaddr 02:1e:10:1f:00:00
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

the command ls can list the USB serial interfaces detected:
ls /dev/ttyUSB*
/dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 /dev/ttyUSB3 /dev/ttyUSB4

Once this far we can now start communicate with the cellular module over AT commands. There are different applications available in Linux that enables manual communication with serial interfaces:

minicom -D /dev/ttyUSB2
socat - /dev/ttyUSB2,crnl
etc.

Basic AT commands to set up the data connection:
ATI
Print general information about cellular module

AT+CPIN=1234
Enter the SIM PIN code

AT+CGDCONT=1,"IP","data.tre.se"
Set the operator APN name to use for the data connectivity

AT^NDISDUP=1,1,
Activate the data connection for the network interface exposed to host system with the APN profile previously created.

Once ^NDISSTAT:1,,,"IPV4" is received you now have a active data connection to the network operator.

Now you can use a DHCP client in your host system to request an IP address from the cellular network:
dhclient -v ens35u1c2
Listening on LPF/ens35u1c2/02:1e:10:1f:00:00
Sending on LPF/ens35u1c2/02:1e:10:1f:00:00
Sending on Socket/fallback
DHCPDISCOVER on ens35u1c2 to 255.255.255.255 port 67 interval 3 (xid=0xf1045e28)
DHCPREQUEST of 2.64.107.209 on ens35u1c2 to 255.255.255.255 port 67 (xid=0x285e04f1)
DHCPOFFER of 2.64.107.209 from 2.64.107.210
DHCPACK of 2.64.107.209 from 2.64.107.210
bound to 2.64.107.209 -- renewal in 235255 seconds.

You now have a working cellular network data connection in your Linux system.

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)

The logs from module firmware can be acquired by accessing the USB enumerated serial (COM) interfaces accepting AT commands, can be named modem, AT, PC UI etc. (In Windows device manager, found under modem or serial interfaces). Send the following commands 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:
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
AT+CGATT?
List APN details/PDP profiles:
AT+CGDCONT?
PS attached status:
AT+CGATT?
Show PDP IP address:
AT+CGPADDR
RM network interface status:
AT$QCRMCALL?

The support ticket can be created after login at: https://techship.com/technical_support/

Question

What are the main differences between the different types of coaxial cables used in Techship's RF cable assemblies?

Solution

The 0.81mm coax cable is very flexible and with minimum bend radius 9mm it is most often used for mini connectors such as IPEX MHF-4, U.FL, W.FL.

1.13~1.37mm cables are flexible with good attenuation. These cables are often used for connectors such as IPEX MHF, U.FL, SMA, SMB, SMC, MCX, MMCX and QMA.
We can also provide 1.13mm low loss cables and 1.32mm double shielding cables for even better performance.

RG178 cables provides good attenuation data and good tensile strength and are often used with IPEX MHF, SMA, SMB, SMC, MCX, MMCX,QMA, TNC, BNC, N-type connectors.

RG174 offers a more cost effective alternative to RG178. The RG174 cables offers a good mix of pricing and reliable performance for the same type of connectors.

Question

How do we use the GPS functionality of the Sierra Wireless EM/MC7455 modules?

Solution

The Sierra Wireless EM/MC74 series modules include a GNSS tracker that can be enabled to acquire location data.

Details of the available AT commands related to GNSS functionality are described in the AT commands reference manuals chapter 7: GNSS Commands.

A basic GNSS tracking session outputting the location data on the NMEA virtual serial interface can be started with the following AT command
AT!GPSTRACK=fixType,maxTime,maxDist,fixCount,fixRate

Bellow command starts a standalone tracking with 255 seconds timeout value, 50 meter accuracy, continuous fixing, fixed data output rate every second on the NMEA virtual serial interface:
AT!GPSTRACK=1,255,50,1000,1

Depending on if an GNSS antenna with or without low noise amplifier (active/passive antenna) are used, the AT+WANT command can adjust if the antenna power supply of 3 volt should be enabled or disabled. Configure GNSS port for a passive GPS antenna:
AT+WANT=0

A GNSS tracking session can be interrupted and ended with the command:
AT!GPSEND

In Linux applications it is recommended to use the Sierra Wireless provided GobiNet and GobiSerial drivers for optimal performance. If the Linux in-kernel drivers are used, it might be needed also to send the bellow sentence to the ttyUSBx that represents the NMEA serial interface in order to activate the data stream on the interface:
$GPS_START


The antenna connector used by the GPS tracker can be either through the dedicated GNSS port or it can be combined with the Rx Diversity antenna located on the AUX marked connector. This is selected by changing a parameter with the AT!CUSTOM command:

To select usage of the dedicated GNSS antenna connector on cellular module, execute:
AT!ENTERCND="A710"
AT!CUSTOM="GPSSEL",0
This will select usage of the dedicated GPS antenna slot (Default value)

For further 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.

Question

How to collect initial diagnostics data for Sierra Wireless EM/MC73 series cellular modules when requesting 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 module when creating a technical support ticket.

Please provide a problem description of what exact problem is and in what precise situations it is present.

Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux dist, 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 required also)

The logs from module firmware can be acquired by accessing one of the USB enumerated serial (COM) interfaces accepting AT commands. (In Windows this is generally modem devices or AT commands serial interfaces). Send the following AT commands to module and capture the text output and include them when creating the the technical support ticket.

Sierra Wireless :
ATI
AT!ENTERCND="A710"
AT!PRIID?
AT!HWID?
AT+CPIN?
AT+CREG?
AT+COPS?
AT!GSTATUS?
AT+CGDCONT?
AT!GOBIIMPREF?
AT!IMAGE?
AT!CUSTOM?
AT!CUSTOM=?
AT!BAND?
AT!PCINFO?
AT!PCTEMP?
AT!PCVOLT?
AT!UDUSBCOMP?
AT!ERR
AT!BCFWUPDATESTATUS
AT!SELRAT?
AT!SELRAT=?
AT+CFUN?

The support ticket can be created after login at: https://techship.com/technical_support/

Question

Why should we use USB3 instead of USB2 as host system data interface if the cellular module can support both?

Solution

Cellular modules supporting higher data throughput rates like LTE Advanced, category 6 and above (300Mbps downlink and 50Mbps uplink) often support both USB3 interface as well as USB2 interface towards the host system.

It is recommended to implement and use the USB3 data interface rather than the older USB2 interface on these modules between host system and the cellular module. This because USB3 can support around 10 times higher data throughput rate compared to USB2 and avoid a possible bottleneck / limitation in the data interface between host and cellular module.

If a miniPCIe based cellular module implementing USB3 are used, please verify that conflicts don't occur towards your hosts miniPCIe socket, as the USB3 interface is not implemented by default in the miniPCIe standard and therefore signal collisions can happen between USB3 pins and PCIe data interface pins situated on same locations. Refer to the cellular module hardware guides and host system hardware guides to verify this.

Question

How to collect initial diagnostics data for Sierra Wireless EM/MC74xx and EM75xx series cellular modules when requesting 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 module when creating a technical support ticket.

Please provide a problem description of what exact problem is and in what precise situations it is present.

Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux dist, 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 required also)

The logs from module firmware can be acquired by accessing one of the USB enumerated serial (COM) interfaces accepting AT commands. (In Windows this is generally modem devices or AT commands serial interfaces). Send the following AT commands to module and capture the text output and include them when creating the the technical support ticket.

Sierra Wireless :
ATI
AT!ENTERCND="A710"
AT!PRIID?
AT+CPIN?
AT+CREG?
AT+COPS?
AT!GSTATUS?
AT+CGDCONT?
AT!IMPREF?
AT!IMAGE?
AT!CUSTOM?
AT!CUSTOM=?
AT!BAND?
AT!PCINFO?
AT!PCTEMP?
AT!PCVOLT?
AT!USBCOMP?
AT!USBCOMP=?
AT!ERR
AT!BCFWUPDATESTATUS
AT!SELRAT?
AT!SELRAT=?
AT+CFUN?

The support ticket can be created after login at: https://techship.com/technical_support/

Images
10374_MC7455_1 10375_EM7455_1
Question

How to collect initial diagnostics data and logs for Telit cellular modules needed when requesting Techship technical support?

Solution

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 Telit 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 required also)

The logs from module firmware can be acquired by accessing one of the USB enumerated serial (COM) interfaces accepting AT commands. (In Windows this is generally modem devices or AT commands serial interfaces). Send the following commands to module and capture the text output and include them when creating the the technical support ticket.

AT
Verbose error reporting:
AT+CMEE=2
Module model:
AT+CGMM
Firmware version:
AT+CGMR
IMEI Code:
AT+CGSN
USB endpoint configuration:
AT#USBCFG?
Serial port configuration:
AT#PORTCFG?
Operational mode:
AT+CFUN?
Selected network access techniques:
AT+WS46?
List network operator info:
AT+COPS?
Network registration status:
AT+CREG=2
AT+CREG?
AT+CGREG?
Signal strength:
AT+CSQ
Last serving cell network information:
AT#SERVINFO
Current network status:
AT#RFSTS
List APN details:
AT+CGDCONT?
Attach UE to default PDP Context:
AT+CGATT=1
List default data connection details:
AT+CGCONTRDP=1
List IP addresses:
AT+CGPADDR=


The support ticket can be created after login at: https://techship.com/technical_support/

Images
Telit logo