TECHSHIP IS A GLOBAL SUPPLIER OF WIRELESS COMPONENTS
S2-10B5K ES SAMPLESupplier number:
SIMCom SIM8262A-M2 5G sub6 is a multi-band 5G NR / LTE / HSPA+ module with support for Rel-16 5G NSA/SA. It comes with strong extension capabilities with abundant interfaces including PCIe, USB3.1, GPIO and more. Designed for applications with high throughput needs in a variety of radio propagation conditions. Due to the unique combination of performance, security and flexibility, this module is suited for many applications such as routers and gateways, POS and mobile computing. Key Features 3GPP Release 16 compliant M.2 30x42mm matching previous generation M.2 modules. NSA & SA mode Linux, Windows and Android support. Dev.kit can be found here - SIMCom SIM8200-M2-EVB2-KIT
SIMCom SIM8262A-M2 5G sub6 is a multi-band 5G NR / LTE / HSPA+ module with support for Rel-16 5G NSA/SA.
It comes with strong extension capabilities with abundant interfaces including PCIe, USB3.1, GPIO and more.
Designed for applications with high throughput needs in a variety of radio propagation conditions. Due to the unique combination of performance, security and flexibility, this module is suited for many applications such as routers and gateways, POS and mobile computing.
3GPP Release 16 compliant
M.2 30x42mm matching previous generation M.2 modules.
NSA & SA mode
Linux, Windows and Android support.
Dev.kit can be found here - SIMCom SIM8200-M2-EVB2-KIT
This guide describes the SIM82xx & SIM83xx Series cellular modules AT control commands available and supported
How to collect initial diagnostics data for Simcom 5G cellular modules when creating a Techship technical support ticket?
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 5G module when creating a technical support ticket.
This allows us to get a better understanding of what could relate to the experienced behaviour.
Please provide a detailed problem description and in what situations the problem is present or how it can be reproduced. Please also attach pictures showing the module assembled in your host device with RF interface cables connected between cellular module and the casing and provide datasheets for the antennas used if the problem appears to be a RF related problem such as no network registrations seen, or data throughputs not meeting your expectations etc.
Describe the host system:
-Hardware (system board, peripherals...)
-Operating system and detailed versions (E.g. Windows, Linux release, kernel version...)
-Drivers and driver versions
Identify the precise details of cellular module found on label (if not visible in attached picture)
-SKU / BOM or P/N code
-Serial / IMEI number
If your system is Linux based, please capture the terminal logs bellow:
ls -l /dev/serial/by-id
ls -l /sys/bus/usb-serial/devices
The log outputs from AT commands below can be collected from the cellular module by accessing the USB enumerated serial interfaces that accept AT commands. These are typically found as Modem or Serial type of interfaces in Window device manager, check their related COM port numbers from device manager and use a terminal software like Teraterm, Sscom or similar to send the AT commands to the cellular module. typically the default 115200 bitrate and 8N1 parity settings works well for collecting these details.
In Linux systems the USB serial ports are typically found in path /dev/ and named ttyUSB0, ttyUSB1, ttyUSB2, not all serial ports accept AT commands so you might have to check which of them are the correct one. Please note that if you have Modemmanager process running in your system, it likely already communicate on the USB serial interfaces so you should stop the Modemmanager service prior to attempting to collect the diagnostic logs. Minicom or other terminal software can be used to send the AT commands to the cellular module.
Start by sending an plain AT command followed by enter key to confirm that you get a OK reply and knowing that the AT communication is working.
Now start sending the following AT commands to the module and capture the output into a log text file and include them when creating the technical support ticket at Techship.com. If possible, provide the logs with a SIM card inserted and PIN unlocked, to allow the module to be in normal operational mode and registered in network.
Test that you have a working AT interface opened:
Enabled AT command echo:
Basic module info:
Display V.25TER configurations
Detailed module version info:
Verbose error reporting:
Serial number / IMEI:
USB endpoint configuration:
PCIe interface configuration:
SIM card interface, SIM card detect signal and active SIM slot:
Active technologies, RF bands, and scan orders:
Request UE network system info:
List network operator info:
Network registration status:
Network GPRS registration status:
Network (4G/LTE) EPS registration status:
Network 5G SA
List APN details/PDP profiles:
Packet domain attach status:
PDP profiles attach status:
Show PDP IP address:
The support ticket can be created after login at Techship.com: https://techship.com/technical_support/