TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS
The ME906s-158 is a LTE module with M.2 (NGFF) interface, supporting eight LTE (FDD) B1/B2/B3/B5/B7/B8/B20/B28, Penta-band DC-HSPA+/HSPA+/HSPA/WCDMA for Europe network coverage, all bands with diversity. It has low power consumption, support for Global Navigation Satellite System (GNSS, GPS, GLONASS) and European carrier certifications enabling easier and more flexible design and integration into end devices.
In addition, ME906s-158 supports M.2 (NGFF) features to optimize performance, power consumption and usability.
ME906s-158 is the ideal choice for many applications, including Ultra books, notebooks, tablets and even M2M and other embedded applications.
This guide describes a workaround method for how to enable the serial (AT/NMEA) interfaces in Windows 8 and 10 for Huawei HiSilicon based cellular modules that normally only expose MBIM interface.
This document is intended to provide references for customers to choose appropriate command sequences to start using the ME906s module in a faster manner. This document also contains examples and relevant description.
This archive contains the guide, library and sample code for accessing Huawei extended AT commands over MBIM interface in Microsoft Windows 8 and newer systems where no AT serial ports are available from Huawei Modules.
This guide instructs the kernel driver integration development for Huawei modules based on Linux operating system (OS), such as Android, Ubuntu and Chrome OS. It is intended for the driver developers of the products based on Linux kernel OS.
This document contains the open source notice for the ME909s and ME906s series from Huawei.
This document describes best practices when designing a USB interface for use with Huawei wireless modules with USB interface capabilities.
This document describes the Huawei RIL (Radio Interface Layer) for Android and the deliveries included. It includes description on how to integrate the RIL and what is supported.
Datasheet for Huawei ME906s-158. This document includes an overview of ME906s-158 and it's features. For more detailed technical information, see the Huawei ME906s-158 Hardware Guide.
This document describes certain AT commands (implemented by terminal devices) of international standards, such as 3GPP and ITU-T, according to the requirements of terminal devices.
In addition, this document describes the Huawei proprietary AT command interfaces that are implemented by terminal devices. These Huawei proprietary AT command interfaces help implement a certain function.
This document describes the hardware application interfaces and air interfaces that are provided when HUAWEI ME906s LTE M.2 Module (hereinafter referred to as the ME906s module) is used.
M.2 is the new name for NGFF (Next Generation Form Factor), which is the specification of PCI-SIG (Peripheral Component Interconnect Special Interest Group).
This document helps you to understand the interface specifications, electrical features and related product information of the ME906s module.
This document describes the TRA certificate for the module ME906s-158 in the United Arab Emirates. It's valid until 2018-06-06.
This archive contains the certificates and reports for the module ME906s-158 in Ukraine.
This archive contains the ANATEL certificates and reports for the Huawei module ME906s-158 in Brazil.
This archive contains the Huawei debug drivers V.18.104.22.168 for HiSilicon chipset based Huawei modules containing drivers supporting the additional USB serial end points exposed when module is set in AT^SETMODE=1 instead of default AT^SETMODE=0
This archive contains the Windows drivers for Huawei modules with HiSilicon chipset
This archive contains the Huawei AT commands over MBIM interface tool used for Windows 8-10 systems to send AT commands to cellular modules not exposing the AT/Modem serial interface endpoints.
This archive contains the Windows drivers V.5.06.04.05 for Huawei modules with HiSilicon chipset
This archive contains the drivers for Huawei ME909s series in windows.
It's backwards compatible with older modules.
The Ulog is a log capturing tool for all Huawei modules.
It can work on PCs and various embedded platforms, and supports different operating systems (OS), such as Windows 7, Linux, and Android.
For Windows there's a graphical user interface available. In order to capture logs with Ulog the modules unique shell lock code need to be acquired based on the IMEI.
This archive contains the Huawei ME906s Firmware Package V13.0 (12.500.00.01.00) Windows Updater and Release Notes
It updates the module with the following operator specific image versions:
12.617.08.00.1011 Spark NZ
This archive contains the Huawei ME906s Firmware Package V10.0 (11.500.00.12.00) Windows Updater and Release Notes
It updates the module with the following operator specific image versions:
11.617.09.00.1011 Spark NZ
How to access the serial AT command interfaces for Huawei HiSilicon chipset based modules in systems with Windows 8 and later?
Serial interfaces for cellular modules are recommended to be disabled by default by Microsoft for systems running Windows 8 and later.
The serial interfaces for AT commands etc. can however be exposed again by first using the tool in linked archive: "Huawei AT commands over MBIM interface tool for Windows 8-10 systems and usage guide" and send module the command bellow once (stored in module memory):
(instead of the default value AT^SETMODE=0)
The module will now reboot and new end-points will be visible for the module once re-appearing.
By installing the linked drivers: "Huawei Debug Driver V.22.214.171.124 for HiSilicon" the correct end point drivers can also be loaded for the cellular module when used in this mode.
You should now be able to find AT commands accepting serial interface as following:
Huawei ME909s, and ME906s series:
HUAWEI Mobile Connect - PC UI Interface
How to activate the data connection for Huawei cellular modules over the USB network interface in Linux?
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:
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:
/: 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:
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.
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
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
the command ls can list the USB serial interfaces detected:
/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
Basic AT commands to set up the data connection:
Print general information about cellular module
Enter the SIM PIN code
Set the operator APN name to use for the data connectivity
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 126.96.36.199 on ens35u1c2 to 255.255.255.255 port 67 (xid=0x285e04f1)
DHCPOFFER of 188.8.131.52 from 184.108.40.206
DHCPACK of 220.127.116.11 from 18.104.22.168
bound to 22.214.171.124 -- renewal in 235255 seconds.
You now have a working cellular network data connection in your Linux system.
How to collect initial diagnostics data and logs for Huawei 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 Huawei 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 required also)
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 module firmware can be acquired by accessing one of the USB enumerated serial (COM) interfaces accepting AT commands. (In Windows this is the PC UI serial interface). Send the following commands to module and capture the text output and include them when creating the the technical support ticket.
The support ticket can be created after login at: https://techship.com/technical_support/
How can we establish data connection for cellular modules in Windows 8 and Windows 10 systems?
Microsoft Windows desktop versions starting from Windows 8 and newer have built in data connection manager for WWAN, Wifi etc. that can be used to configure, control and establish the data connection of cellular module that support MBIM interface, which most cellular modules do.
The connection managers settings and controls can be found and accessed on Windows desktop start menu through the network icon (see picture).
The Cellular tab can be found in Windows system settings and if needed the connection APN details can be manually entered through "Advanced options".
Why is there no serial interface for AT-commands available in Microsoft Windows 8/10 and newer, while in Windows 7 all the traditional module serial interfaces are available?
Microsoft demands cellular module vendors to use the Mobile Broadband Interface Model (MBIM) interface for signaling in newer operating systems like Windows 8 and 10 rather than the previous serial based control channels with AT commands.
The serial ports are phased out and enumeration in the host system of these are dropped by many manufacturers because of Microsofts requirements.
The connections can be controlled graphically in Windows by the systems built in connection manager as well as by commands in the command prompt starting with: netsh mbn
Microsoft: Overview of mobile broadband
Antenna Frequency: LTE 790-960/1710-2690, Wifi/Bluetooth 2400, UMTS 2100, GSM 850/900/1800/1900 | Mounting method: Connector | Connector Type: SMA-M | Length: 157 mm | Width: 21 mm | Height: 157 mm | Impedance: 50 Ohm | Polarization: Vertical | Max power: 50 W
SAMPLE PRICE $6.80
GNSS technology: GPS, GLONASS, Galileo | Active/Passive GPS: Passive | Antenna Frequency: LTE 698-960/1710-2690 | Mounting method: Connector | Gain: 3 dBi | VSWR: 3 :1 | Connector Type: SMA-M | Length: 196 mm | Width: 38 mm | Impedance: 50 Ohm | Polarization: Linear
SAMPLE PRICE $9.30