Page 2
SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE NOTICE While reasonable efforts have been made to assure the accuracy of this document, Telit assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been carefully checked and is believed to be reliable.
Page 3
USAGE AND DISCLOSURE RESTRICTIONS License Agreements The software described in this document is the property of Telit and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement.
Page 4
APPLICABILITY TABLE PRODUCTS ME910C1 SERIES ME910G1 SERIES ML865C1 SERIES ML865G1 SERIES ME310G1 SERIES 4 of 33 Reproduction forbidden without Telit Communications PLC written authorization – All Rights Reserved...
CONTENTS INTRODUCTION ................6 Scope ....................6 Audience ..................6 Contact Information, Support ............6 Related Documents ...............6 GENERAL DESCRIPTION ............7 ME910C1, ML865C1 Main Features ..........7 ME910G1, ML865G1,ME310G1 Main Features ......8 USB/UART port configuration ............9 Warning on Windows Cellular connection ........10 APPLICATION MAIN FLOW ............11 NETWORK REGISTRATION ............
Introduction Scope Scope of this document is to give an overview and basic instructions of how to start using the follwing product series: ME910C1, ME910G1, ML865C1, ML865G1, ME310G1. Audience This document is intended for customers who want to use and test the NE866 product. Contact Information, Support For general contact, technical support services, technical questions and report documentation errors contact Telit Technical Support at:...
USB/UART port configuration ME910C1, ME910G1, ML865C1, ML865G1, ME310G1 are equipped with 2 asynchronous serial port (CMOS 1.8) and one integrated universal serial bus (USB 2.0 HS) transceiver with the following composition: • 2 Telit USB Modem ports • 1 Telit HS-USB WWAN •...
Warning on Windows Cellular connection When the module is recognized as a Cellular device, Windows uses the WWAN interface to set up internet connection (NCSI). This could lead to connectivity issues using the module AT interface: registration to the network, APN management, socket creation and data exchange, PSM and eDRX functionalities can be affected.
Application Main Flow POWER ON & CONFIGURATION Bad signal Loop “Check_n CHECK NETWORK NETWORK et_timer” SHUTDOWN REGISTRATION REGISTRATION or others expired? “data_ser ACTIVATE DATA vice_timer CHECK DATA SERVICE AND ” is REGISTRATION SEND DATA expired? 11 of 33 Reproduction forbidden without Telit Communications PLC written authorization – All Rights Reserved...
Network Registration Here below a brief overview of 4G (CAT M1, NB IoT) and 2G (GPRS) registration process, IP stack setup and related commands. 4G registration (CAT-M1, NB-IoT) and IP stack setup: the module performs Attach and EPS Bearer activation automatically. When the procedure ends an IP address is assigned by the network to the module.
Page 13
New attach is needed to use the new APN. A way to do this is to turn the radio off and on using AT+CFUN AT+CFUN=4 AT+CEREG? +CEREG: 0,0 AT+CFUN=1 AT+CEREG? +CEREG: 0,0 AT+CEREG? +CEREG: 0,2 AT+CEREG? +CEREG: 0,1 AT+COPS? +COPS: 0,1,"I TIM",9 AT+CGCONTRDP +CGCONTRDP: 1,5,"nbiot.tids.tim.it","10.16.13.162",,"192.168.200.43","192.168.200.42"...
2G Registration AT script example The module is turned on and attached, APN on context 1 is required by MNO for data traffic AT+CREG? +CREG: 0,1 AT+CGREG? +CGREG: 0,1 AT+CGDCONT=1,"IP","internet.wind.biz" There’s no need to trigger new registration since the APN will be used in the next step: the PDP context activation request AT#SGACT=1,1 #SGACT: 10.34.234.204...
4.3 Access technology selection AT+WS46=[<n>] command selects the cellular netwrok to operate with. • 4G/2G products support <n> parameter values 12, 28 and 30. 30 is factory default • 4G only products support <n> parameter value 28 Values [<n>]: 12 : GSM Digital Cellular Systems, GERAN only 28 : E-UTRAN only 30 : GERAN and E-UTRAN AT#WS46=[<n>] command selects the IoT E-UTRAN technology to operate with.
4.4 Speed up registration The registration process in CAT-M1 and NB-IoT technologies could require some minutes to complete. This happens especially in the case of very first registration: new SIM, new location, new module. This is due to the IoT technology itself and cellular network deployment factors. To speed up the process you can reduce the set of supported technologies and bands.
5 Check/Set data service When registration is completed you can activate data services and set up the internal IP stack with the AT#SGACT command: AT#SGACT=<cid>,<stat>[,<userId>[,<pwd>]] E.g. if we want to activate context 1, issue AT#SGACT=1,1; in case we want to use the <cid> 3 (e.g.
6 UDP script An example of UDP communication over NB-IoT is reported below; in this scenario, APN is not required and it set automatically by the network. The module enables NB IoT only. A UDP socket is opened in command mode on xxx.telit.com echo server. “echo_test_UDP” string is sent to the server and echoed back to the module.
7 TCP script An example of TCP communication over NB-IoT is reported below; in this scenario, APN is not required and it is set automatically by the network. The module enables NB IoT only. A TCP socket is opened in command mode on xxx.telit.com echo server. “echo_test_TCP” is the data sent to the server and echoed back to the module.
Page 21
AT#SS #SS: 1,2,10.18.15.165,36410,185.xxx.xxx.218,10510 #SS: 2,0 … #SS: 10,0 AT#SSEND=1 > echo_test_TCP<CTRL-Z> SRING: 1 AT#SRECV=1,1500 #SRECV: 1,13 echo_test_TCP AT#SI #SI: 1,13,13,0,0 #SI: 2,0,0,0,0 … #SI: 10,0,0,0,0 AT#SH=1 21 of 33 Reproduction forbidden without Telit Communications PLC written authorization – All Rights Reserved...
8 PSM and eDRX PSM/eDRX overview RRC Connection RRC Connection RRC Connection Release Release Release (Paging Time Window) (Discontinuous Reception) USER DATA IDLE PSM sleep eDRX T3324 (Active Time) T3412 (TAU Timer) PSM and eDRX are two different features defined in the latest 3GPP releases. The goal of these features is to reduce the power consumption of IoT devices.
Both features require a negotiation with the network to be enabled. The negotiation happens during the Attach procedure and the Tracking Area Update (TAU). PSM script The module supports 3GPP command AT+CPSMS and custom Telit command AT#CPSMS that simplifies and improve PSM management. On ME910C1 and ML865C1: AT#CPSMS=[<mode>[,<ReqPeriodicRAU>[,<ReqGPRSreadyTimer>[,<ReqPeriodicTAU >[,<ReqActiveTime>]]]]]...
Page 24
On ME910G1, ML865G1 and ME310G1: AT#CPSMS=[<mode>[,<ReqPeriodicRAU>[,<ReqGPRSreadyTimer>[,<ReqPeriodicTAU >[,<ReqActiveTime>[,<psmVersion>[,<psmThreshold>]]]]]]] The command has two additional parameters compared to the implementation on ME910C1 and ML865C1: <psmVersion> and <psmThreshold>. The other parameters have the same meaning and functionality as defined for ME910C1 and ML865C1. <psmVersion>: integer N/A bitmask to indicate PSM modes. Each bit is configured independently.
Page 25
Here below a simple script shows the AT#CPSMS functionalities. AT+COPS? +COPS: 1,0,"Vodafone@",9 Module is NB-IoT registered AT#CPSMS? PSM feature is OFF #CPSMS: 0 AT#CPSMS=1,0,0,120,20 Enable PSM feature: T3412=120s, T3324=20s A TAU (Tracking Area Update) is triggered, timer negotiation with the network starts; the procedure is fast, unsolicited are disabled we suggest to wait about 2s before proceeding with the next step AT#CPSMS?
Page 26
AT#SD=1,0,20510,"2xx.xxx.xxx.xx3" Module now move from IDLE to CONNECTED CONNECT echo test message SRING: 1 Echo is received AT#SS #SS: 1,3,10.21.115.40,32468,2xx.xxx.xxx.xx3,20510 … AT#SH=1 Socket shut down New TIMERS START POINT: the module was in CONNECTED state, after RRC Connection Release from the network it moves to IDLE state, this reset the two timers TIMERS START POINT (RRC Connection release) .
eDRX script The modules support 3GPP commands AT+CEDRXS, AT+CEDRXRDP and custom Telit command AT#CEDRXS that simplifies and improve eDRX management. AT#CEDRXS=[<mode>[,<AcTtype>[,<Req_eDRX>[,<ReqPagTimeWindow>]]]] Set command controls the setting of the UEs eDRX parameters. The command controls whether the UE wants to apply eDRX or not, as well as the requested eDRX value for each specified type of access technology.
Page 28
Here below a simple script shows the AT#CEDRXS functionalities. The test is performed using a network simulator but the same can be applied on live network. AT+CEREG? +CEREG: 0,1 AT+COPS? +COPS: 0,0,"Test 001 01",8 The module is registered to CAT M test network AT#RFSTS #RFSTS: "001 01",1575,-85,-65,-3.0,0001,00,,256,3,0,0000100,"001012345678901","Test 001 01",3,3,720,3240,249...
Page 29
AT#CEDRXS=1,4,"0001","0001" eDRX enabled with some specific values, but test network is setup to support only: eDRX 20,48s Paging Time Window 1,28s TAU is triggered and values are exchanged with the network AT#CEDRXS? #CEDRXS: 2,0,"0000","0000" #CEDRXS: 4,1,"0001","0001",1,"0010","0000" #CEDRXS: 5,0,"0000","0000" The network applies the supported values <NW_prov_eDRX>...
8.4 PSM in between eDRX script Within the eDRX modality the modules can activate a proprietary powersave mananagement to fully enhance eDRX power consumptions when eDRX cycle is greater that a specific value (tipically above 2-3 minutes). The solution is using “PSM power state” in between eDRX PTWs in order to lower the current consumption to 3uA.
Page 31
AT#REBOOT AT#CEDRXS? eDRX is disabled on all access technologies #CEDRXS: 2,0,"0000","0000" #CEDRXS: 4,0,"0000","0000" #CEDRXS: 5,0,"0000","0000" AT#CEDRXS=1,4 eDRX enabled without specifying timings that will be assigned by the network (Network Simulator) A TAU (Tracking Area Update) is triggered, values negotiation with the network starts; the procedure is fast but we suggest to wait about 2s before proceed with next step AT+CEDRXRDP +CEDRXRDP: 4,"0101","0101","1111"...
Need help?
Do you have a question about the ME910C1 Series and is the answer not in the manual?
Questions and answers