Qisda M-series - wless.ru

M2M User Guide
Qisda M-series
GSM / GPRS Wireless Modules
M2M User Guide
Rev. 1.0.8
2009/03/13
Document ID: M8-21-0012-108
Copyright © 2007, 2008 Qisda Corporation. All rights reserved.
This document contains proprietary technical information which is the property of Qisda
Corporation and is issued in strict confidential and shall not be disclosed to others parties in
whole or in parts without written permission of Qisda Corporation.
The documents contain information on a product, which is under development and is issued
for customer evaluation purposes only.
Qisda may make changes to product specifications at any time, without notice.
Module Business Division
Mobile Communications BU
Qisda Corporation
18 Jihu Road, Nei-Hu, Taipei 114, Taiwan
Tel: +886-2-2799-8800
Fax: +886-2-2656-6398
http://Qisda.com
Copyright ©2007, 2008 Qisda Corporation.
Confidential Property

M2M User Guide
Date Originator Reviewer
04-JAN-2008
Joey Ni
12-MAR-2008
Joy Lai
03-AUG-2008
Bruce Wang
01-SEP-2008
Joey Ni
13-MAR-2009
Joey Ni
History
Version Date Note
VER: 1.0.0 04-JAN-2008 First release
VER: 1.0.1 18-JAN-2008 Modify $NWRX
VER: 1.0.2 01-FEB-2008 1. Add new feature of $NWTX
2. Modify $NWDR
3. Modify $NWRX
4. Modify chapter 4 - example
VER: 1.0.3 12-FEB-2008 1. Modify $NWTX
2. Add query function of $NWTX
VER: 1.0.4 15-FEB-2008
VER: 1.0.5 03-AUG-2008 Add new module-id
VER: 1.0.6 01-SEP-2008
VER: 1.0.7 26-SEP-2008 Add multi-session feature
Add $NWSO
Add $NWDW
Modify $NWTX
VER: 1.0.8 13-MAR-2009 Modify $NWACT
Modify $NWCN
Modify $NWTX
Modify example
M8-21-0012-108 - 2 - Version: 1.0.8 – 2009/03/13

M2M User Guide
Contents
1 ABOUT M2M .................................................................................................................. 4
1.1 INTRODUCTION OF M2M .................................................................................................... 4
1.2 M2M IN QISDA M-SERIES MODULES .................................................................................... 4
1.3 MODULE SUPPORT LIST......................................................................................................... 4
2 PREPARATION FOR M2M............................................................................................... 5
2.1 EQUIPMENT ......................................................................................................................... 5
2.2 PROCEDURE BEFORE M2M AT COMMANDS........................................................................ 5
2.3 NETWORK INFORMATION ..................................................................................................... 5
3 M2M AT COMMANDS................................................................................................... 6
3.1 $NWACT: M2M ACTIVATE OR DEACTIVATE ....................................................................... 6
3.2 $NWSO: OPEN OR CLOSE A SESSION ................................................................................. 8
3.3 $NWDF: SELECT M2M DATA FORMAT .............................................................................. 10
3.4 $NWDW: WRITE DATA INTO THE TX-BUFFER....................................................................... 12
3.5 $NWDR: READ DATA FROM THE RX-BUFFER ...................................................................... 14
3.6 $NWCN: ESTABLISH OR CLOSE THE CONNECTION TO A SERVER ......................................... 17
3.7 $NWTX: SEND DATA TO A SERVER..................................................................................... 19
3.8 $NWRX: INDICATION OF RECEIVING DATA........................................................................ 22
4 COMPLETE EXAMPLES ..................................................................................................24
4.1 EXAMPLE 1: TRANSMIT UCP DATA (HEX MODE) ................................................................ 24
4.2 EXAMPLE 2: TRANSMIT TCP DATA (TEXT MODE).................................................................. 25
4.3 EXAMPLE 3: SEND TCP DATA SPEEDILY (TEXT MODE) .......................................................... 27
4.4 EXAMPLE 4: SEND LARGE SIZE TCP DATA (TEXT MODE) ....................................................... 29
5 M2M SPECIFIC ERROR RESULT CODE...........................................................................31
M8-21-0012-108 - 3 - Version: 1.0.8 – 2009/03/13

M2M User Guide
1 About M2M
1.1 Introduction of M2M
M2M (machine to machine) is a technology which enables machines talking to each
other. M2M is often referred as wireless but can also operate through the wired
infrastructure, like Internet, leased lines or the telephone network. M2M can be used
for both fixed and mobile objects.
There are many communication methods can be a bearer for wireless M2M
application. The common methods are GSM/GPRS/3G, IEEE 802.11, and Bluetooth.
1.2 M2M in Qisda M-series modules
Qisda M-series module can apply M2M to send data to the remote server.
The feature of Qisda M-series module:
Embedded TCP/IP
Connect to a TCP/UDP server on Internet over GPRS
AT Commands interface
1.3 Module support list
The Qisda M-series modules which support M2M are:
Module ID M25 M26 M27 M33G
M2M supported ○ ○ ○ ○
M8-21-0012-108 - 4 - Version: 1.0.8 – 2009/03/13

M2M User Guide
2 Preparation for M2M
2.1 Equipment
A SIM with GPRS capability
Device connected with UART connector (UART connects module and device.)
TCP/UDP server with public IP address in Internet Network
2.2 Procedure before M2M AT commands
1. Plug in a SIM card, which with enabled GPRS function, into the SIM card slot.
2. Turn on the power.
3. Set module to full functionality mode, thus we can execute all AT commands in
module.
AT Command: +CFUN=1
4. Register GSM network.
AT Command: +COPS=0
5. In order to use the GPRS service, we must register GPRS network.
AT Command : +CGATT=1
6. After 5. We can execute M2M AT commands. The complete example of M2M
application will be described in chapter 4.
2.3 Network information
Before setting up module to access the GPRS network, we must contact the
network provider to obtain the following information:
APN (access point name)
User ID & password (optional)
M8-21-0012-108 - 5 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3 M2M AT Commands
3.1 $NWACT: M2M activate or deactivate
This command is used to activate or deactivate M2M.
When M2M is activated:
GPRS service will be attached
The PDP context will be activated
Before executing “$NWACT=1”, setting “+COPS=0” and “+CGATT=1” are
recommended. If both of them are executed successfully, we can guarantee the
GSM and GPRS network has camped on.
GPRS attachment procedure may take place if it has not already been performed
using the +CGATT commands.
Syntax
AT$NWACT=[,[,,]]
(if activating M2M)
AT$NWACT=1,[,,]
(if deactivating M2M)
AT$NWACT=0
Response(s) OK
+CME ERROR:
AT$NWACT
Response(s) $NWACT: [,[,,]]
OK
AT$NWACT=
Response(s) $NWACT: (list of supported s)
OK
Unsolicited Result Codes
When network deactivate PDP context:
$NWACT: 0
Parameter(s)
State of M2M activation Numeric
0 Deactivated
1 Activated
2 M2M suspended (when enter no signal region or be in GSM voice call)
M8-21-0012-108 - 6 - Version: 1.0.8 – 2009/03/13

M2M User Guide
(Access Point Name) a logical name that is used to String
select the GGSN or the external packet data network.
User ID String
User password String
Example(s)
Activate M2M only with
AT$NWACT=1,"internet"
OK
AT$NWACT
$NWACT: 1,"internet","",""
OK
1. Activate M2M only with
2. Query
AT$NWACT=0
3. Deactivate M2M
OK
Activate M2M with , ,
AT$NWACT=1,"internet","user_A","pw"
OK
1. Activate M2M with , ,
AT$NWACT
$NWACT: 1,"internet","user_A","pw"
OK
2. Query
M8-21-0012-108 - 7 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3.2 $NWSO: Open or close a session
This command is used to open a session or close a session.
Before executing $NWSO, M2M must be activated. ($NWACT:1)
When a session is open, $NWDF, $NWDW, $NWDR, $NWCN can be executed on this
session.
The read command returns the current opened sessions.
Syntax
AT$NWSO=,
Response(s) OK
+CME ERROR:
AT$NWSO
Response(s) $NWSO: ,1
[$NWSO: ,1]
…
OK
AT$NWSO=
Response(s) $ NWSO: (list of supported s),(list of supported s)
OK
Parameter(s)
(M2M session identifier) Specifies a particular M2M Numeric
session.
1-5 Support at most 5 sessions.
State of session Numeric
0 Closed
1 Open
Example(s)
AT$NWACT=1,”internet”
OK
AT$NWSO=1,1
OK
AT$NWSO=2,1
OK
1. Activate M2M with APN
2. Open session-1
3. Open session-2
M8-21-0012-108 - 8 - Version: 1.0.8 – 2009/03/13

M2M User Guide
AT$NWSO=3,1
OK
AT$NWSO
$NWSO: 1,1
$NWSO: 2,1
$NWSO: 3,1
OK
AT$NWSO=2,0
OK
AT$NWSO
$NWSO: 1,1
$NWSO: 3,1
OK
4. Open session-3
5. List current opened sessions
6. Close session-2
7. List current opened sessions
M8-21-0012-108 - 9 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3.3 $NWDF: Select M2M data format
This command is used to select format of transmission data.
Before executing $NWDF on a session, the session must be opened. ($NWSO: ,1)
The read command returns the current data format of all opened sessions.
Syntax
AT$NWDF=,
Response(s) OK
+CME ERROR:
$NWDF
Response(s) $NWDF: ,
[$NWDF: ,]
…
OK
$NWDF=
Response(s) $NWDF: (list of supported s), (list of supported s)
OK
Parameter(s)
(M2M session identifier) Specifies a particular M2M
session.
1-5 Support at most 5 sessions.
The format of data.
Numeric
Numeric
When hex mode, the one byte is displayed as two
characters in hexadecimal format. For example, the
byte 0x36 (decimal 54) is displayed as "36" (two
characters).
In hex mode, only characters '0'..'9', 'A'..F' and 'a'..'f'
are valid.
0 HEX mode
1 Text mode
Example(s)
AT$NWACT=1,”internet”
OK
AT$NWSO=1,1
OK
1. Activate M2M with APN
2. Open session-1
M8-21-0012-108 - 10 - Version: 1.0.8 – 2009/03/13

M2M User Guide
AT$NWSO=2,1
OK
AT$NWDF
$NWDF: 1,0
$NWDF: 2,0
OK
AT$NWDF=2,1
OK
AT$NWSO
$NWDF: 1,0
$NWDF: 2,1
OK
3. Open session-2
4. Query data format of the opened
sessions.
5. Set data format to Text mode of
session-2.
6. Query data format of the opened
sessions.
M8-21-0012-108 - 11 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3.4 $NWDW: Write data into the TX-buffer
This command is used to write data into the TX-buffer.
Before executing $NWDW on a session, the session must be opened.
($NWSO: ,1)
Every session has its own TX-buffer. The size of a TX-buffer is 1470 bytes. The data stored
in TX-buffer will not be influenced when executing $NWCN. All data stored in TX-buffer
will be cleared when the session is closed.
The read command returns the current length of stored data in TX-buffer of all
opened sessions.
Syntax
AT$NWDW=,[,]
Response(s) OK
+CME ERROR:
AT$NWDW
Response(s) $NWDW: ,
[$NWDW: ,]
…
OK
Parameter(s)
(M2M session identifier) Specifies a particular M2M
session.
1-5 Support at most 5 sessions.
A string parameter which is sent to the server.
Numeric
String
If $NWDF is text mode:
The maximum length of is 600. The
content of must be visible character
(ASCII 20~7E), but no semicolon(;) and double
quote(").
If $NWDF is HEX mode:
The maximum length of is 600. Only
characters '0'..'9', 'A'..F' and 'a'..'f' are valid.
0 Clear old data.
1 New data is appended to old data.
Numeric
M8-21-0012-108 - 12 - Version: 1.0.8 – 2009/03/13

M2M User Guide
The length of stored data in TX-buffer. Numeric
0-1470
Example(s)
Write data into the TX-buffer of session-1 (HEX mode)
AT$NWSO=1,1
OK
1. Open session-1
(Default data format is HEX mode)
AT$NWDW=1,"313233616263",0
OK
2. Write 6 bytes data into TX-buffer.
(“123abc”)
AT$NWDW
$NWDW: 1,6
OK
Write data into the TX-buffer of session-2 (text mode)
AT$NWSO=2,1
1. Open session-2
OK
3. Query length of stored data in
TX-buffer.
AT$NWDF=2,1
OK
AT$NWDW=2,"aaaaabbbbb",0
OK
AT$NWDW
$NWDW: 2,10
OK
AT$NWDW=2,”cccccdddddeeeee”,1
OK
AT$NWDW
$NWDW: 2,25
OK
2. Set data format to text mode.
3. Write 10 bytes data into TX-buffer.
4. Query length of stored data in
TX-buffer.
5. Write 15 bytes data into TX-buffer.
(append mode)
6. Query length of stored data in
TX-buffer.
M8-21-0012-108 - 13 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3.5 $NWDR: Read data from the RX-buffer
This command is used to read data from the RX-buffer.
Before executing $NWDR on a session, the session must be opened.
($NWSO: ,1)
Every session has its own RX-buffer. The size of a RX-buffer is 1470 bytes. The data
stored in RX-buffer will not be influenced when executing $NWCN. All data stored in
RX-buffer will be cleared when the session is closed.
The read command returns the current length of stored data in RX-buffer of all
opened sessions.
Syntax
AT$NWDR=,
Response(s) $NWDR: ,,[,]
OK
+CME ERROR:
AT$NWDR
Response(s) $NWDR: ,0,
[$NWDR: ,0,]
…
OK
Parameter(s)
(M2M session identifier) Specifies a particular M2M Numeric
session.
1-5 Support at most 5 sessions.
The length of received data. Numeric
0-1470
The length of total data in the RX-buffer. Numeric
0-1470
A string parameter read from the RX-buffer.
Max length is 1470.
String
M8-21-0012-108 - 14 - Version: 1.0.8 – 2009/03/13

M2M User Guide
Read data (HEX mode)
AT$NWDF=1,0
OK
$NWRX: 1,10,10
Example(s)
(In the beginning, length of stored data in
RX-buffer is 0)
1. Set data format to HEX mode
2. (URC) Receive 1 st data from server (10
bytes)
(the content of new received data:
“11111aaaaa”)
AT$NWDR= 1,10
$NWDR: 1,10,0,”31313131316161616161”
OK
Read data (text mode)
AT$NWDF=1,1
OK
$NWRX: 1,15,15
AT$NWDR=1,10
$NWDR: 1,10,5,“aaaaabbbbb”
OK
$NWRX: 1,25,30
AT$NWDR=1,10
$NWDR: 1,10,20,”ccccc11111”
OK
AT$NWDR=1,1470
$NWDR: 1,20,0,”22222333334444455555”
OK
Query remain data length in RX-buffer
$NWRX: 1,20,20
3. Request read data (10 bytes)
(In the beginning, length of stored data in
RX-buffer is 0)
1. Set data format to text mode
2. (URC) Receive 1 st data from server (15
bytes)
(the content of new received data:
“aaaaabbbbbccccc”)
3. Request read data (10 bytes)
4. (URC)Receive 2 nd data from server (25
bytes)
(the content of new received data:
“1111122222333334444455555”)
5. Request read data (10 bytes)
6. Request read data.
(request 1470 bytes, but only 20 bytes in
RX-buffer)
(In the beginning, length of stored data in
RX-buffer is 0)
1. (URC) Receive data from server (20
bytes)
M8-21-0012-108 - 15 - Version: 1.0.8 – 2009/03/13

M2M User Guide
(the content of new received data:
“12345123451234512345”)
AT$NWDR= 1,0
$NWDR: 1,0,17
OK
2. Query length of stored data in RX-buffer
of session-1.
M8-21-0012-108 - 16 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3.6 $NWCN: Establish or close the connection to a server
This command is used to establish or close the connection to a server.
Before executing $NWCN on a session, the session must be opened.
($NWSO: ,1)
When execute $NWCN:
If server type is TCP server, AT$NWCN will establish the connection to a TCP server
actually.
If server type is UDP server, AT$NWCN just records remote IP & port for preparing
to send data to a UDP server.
When a connection is established, $NWTX & $NWRX are ready to use on this session.
The read command returns the current connection state of all opened sessions.
Syntax
AT$NWCN=,[,,,]
(if connect to M2M server)
AT$NWCN =,1,,,
(if disconnect to M2M server)
AT$NWCN =,0
Response(s) OK
+CME ERROR:
AT$NWCN
Response(s) $NWCN: ,,,,
[$NWCN: ,,,,]
…
OK
AT$NWCN=
Response(s) $NWCN: (list of supported s),(list of supported s),(list
of supported s)
OK
Unsolicited Result Codes
When connection is established successfully:
$NWCN: ,1
When connection with server is closed or becomes unworkable:
$NWCN: ,0
M8-21-0012-108 - 17 - Version: 1.0.8 – 2009/03/13

M2M User Guide
Parameter(s)
(M2M session identifier) Specifies a particular M2M Numeric
session.
1-5 Support at most 5 sessions.
State of M2M connection Numeric
0 Disconnection
1 Connection
2 Connection is being established or being closed.
Protocol of M2M connection Numeric
0 TCP connection
1 UDP connection
Ip address of the remote server String
Port of the remote server Numeric
Example(s)
Connect to a server
AT$NWACT=1,”internet”
OK
AT$NWSO=1,1
OK
AT$NWCN=1,1,0,”111.222.333.444”,1234
OK
AT$NWCN
$NWCN:1,2
OK
$NWCN:1,1
AT$NWCN
$NWCN: 1,1,0,”111.222.333.444”,1234
OK
AT$NWCN=1,0
OK
$NWCN:1,0
AT$NWCN
$NWCN: 1,0
OK
1. Activate M2M with APN
2. Open session-1
3. Request module to connect to a TCP
server on session-1.
4. Query state of connection.
(Because the connection establishment
is not finished, the M2M connection
state is 2)
5. (URC) Connection is established
successfully. Session-1 is ready to
transmit data.
6. Query connection state and connection
information of all opened sessions.
7. Request module to close the connection
to the server on session-1.
8. (URC) Closing connection is finished.
9. Query state of connection.
M8-21-0012-108 - 18 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3.7 $NWTX: Send data to a server
This command is used to send data to a server.
Before executing “$NWTX”, the server must be connected. ($NWCN: ,1)
The can be omitted. In this case, the default of is 0.
The TX-buffer is a memory pool with 1470 bytes.
Syntax
AT$NWTX=,[,]
Response(s) OK
+CME ERROR:
AT$NWTX=
Response(s) $NWTX: (list of supported s),,(list of supported s)
OK
Unsolicited Result Codes
When all sent data bytes are acknowledged from the TCP server:
(only for TCP connection)
$NWTX: ,0
Parameter(s)
(M2M session identifier) Specifies a particular M2M
session.
1-5 Support at most 5 sessions.
A string parameter which is sent to the server.
Numeric
String
If $NWDF is text mode:
The maximum length of is 600. The
content of must be visible character
(ASCII 20~7E), but no semicolon(;) and double
quote(").
If $NWDF is HEX mode:
The maximum length of is 600. Only
characters '0'..'9', 'A'..F' and 'a'..'f' are valid.
0 Send to the server.
1 Send all stored data in TX-buffer to the server.
In this mode, must be omitted.
Numeric
M8-21-0012-108 - 19 - Version: 1.0.8 – 2009/03/13

M2M User Guide
Example(s)
Send data to a UDP server (HEX mode)
AT$NWTX=1,"313131323232"
OK
AT$NWTX=1,"333333343434"
OK
(Assume the connection is established,
and the data format is HEX mode)
1. Send data to the server.
(server will receive “111222”)
2. Send data to the server.
(server will receive “333444”)
Send data to a TCP server (text mode)
AT$NWTX=1,"aaabbb"
OK
$NWTX:1,0
AT$NWTX=1,"cccddd"
OK
$NWTX:1,0
(Assume the connection is established,
and the data format is text mode)
1. Request to send data to the server.
2. (URC) The TCP server received
“aaabbb” and sent acknowledgment
back. Qisda module receives the
acknowledgment.
3. Request to send data to the server.
4. (URC) Qisda module receives the
acknowledgment of all sent data from
TCP server.
Send data to a TCP server speedily (text mode)
(Assume the connection is established,
and the data format is text mode)
AT$NWTX=1,"aaabbb"
OK
(0.7 sec )
AT$NWTX=1,"cccddd"
OK
1. Request to send data to the server.
2. Qisda module not receives the
acknowledgment from TCP server
yet.
3. Request to send data to the server.
(0.7 sec )
AT$NWTX=1,"eeefff"
OK
$NWTX:1,0
4. Request to send data to the server.
5. (URC) Qisda module receives the
acknowledgment of all sent data from
TCP server.
M8-21-0012-108 - 20 - Version: 1.0.8 – 2009/03/13

M2M User Guide
Send large size data to a server from TX-buffer (text mode)
(Assume the connection is established,
and the data format is text mode)
AT$NWDW=1,"1111111111222222222233333
3333344444444445555555555666666666677
7777777788888888889999999999000000000
0111111111122222222223333333333444444
4444555555555566666666667777777777888
8888888999999999900000000001111111111
2222222222333333333344444444445555555
5556666666666777777777788888888889999
9999990000000000111111111122222222223
3333333334444444444555555555566666666
6677777777778888888888999999999900000
0000011111111112222222222333333333344
4444444455555555556666666666777777777
7888888888899999999990000000000111111
1111222222222233333333334444444444555
5555555666666666677777777778888888888
99999999990000000000",0
OK
AT$NWDW=1,"1111111111222222222233333
3333344444444445555555555666666666677
7777777788888888889999999999000000000
0111111111122222222223333333333444444
4444555555555566666666667777777777888
888888899999999990000000000",1
OK
AT$NWDW
$NWDW: 1,800
OK
AT$NWTX=1,,1
OK
$NWTX:1,0
AT$NWDW
$NWDW: 1,0
OK
1. Write 600 bytes data into TX-buffer.
2. Write next 200 bytes data into
TX-buffer.
3. Query length of data stored in
TX-buffer.
4. Send all 800 bytes data in TX-buffer
to the server.
5. (URC) Qisda module receives the
acknowledgment of all sent data from
TCP server.
6. TX-buffer is clear.
M8-21-0012-108 - 21 - Version: 1.0.8 – 2009/03/13

M2M User Guide
3.8 $NWRX: Indication of receiving data
This command is an unsolicited result code. It is indicated when the server send data
to the module.
When RX data is received, it will be stored in the RX-buffer. Every session has its own
Rx-buffer. The size of a RX-buffer is 1470 bytes.
When new data is received, front part of old data will be discarded if RX-buffer’s free
space is not enough.
Syntax
Unsolicited Result Codes
$NWRX: ,,
Parameter(s)
(M2M session identifier) Specifies a particular M2M Numeric
session.
1-5 Support at most 5 sessions.
The length of received data. Numeric
1-1470
The length of total data in the RX-buffer. Numeric
0-1470
M8-21-0012-108 - 22 - Version: 1.0.8 – 2009/03/13

M2M User Guide
Example(s)
(In the beginning, data in RX-buffer is 0)
(buffer size: 1470 bytes)
$NWRX: 1,300,300
1. Receive 1st data from server (300 bytes)
$NWRX: 1,400,700
2. Receive 2nd data from server (400 bytes)
$NWRX: 1,500,1200
3. Receive 3rd data from server (500 bytes)
$NWRX: 1,500,1470
4. Receive 4th data from server (500 bytes)
M8-21-0012-108 - 23 - Version: 1.0.8 – 2009/03/13

M2M User Guide
4 Complete Examples
4.1 Example 1: transmit UCP data (HEX mode)
AT+CFUN=1
OK
AT+COPS=0
OK
AT+CGATT=1
OK
AT$NWACT=1,"INTERNET" // Note: "INTERNET" is a example APN
OK
AT$NWSO=1,1
OK
AT$NWCN=1,1,1,"168.95.100.100",3000
OK // Not really connect to UDP server, just record remote IP & port for preparing to send
data to a UDP server.
$NWCN:1,1 // (URC) Connection is established successfully. This session is ready to transmit
data.
AT$NWTX=1,"5544502074657374" // "UDP test"
OK
(Server receives "UDP test" and responses "Data received!")
$NWRX: 1,14,14 // (URC, module receives 14 bytes data
AT$NWDR=1,14
$NWDR: 1,14,0,"4461744120726563656976656421" // "Data received!"
OK
M8-21-0012-108 - 24 - Version: 1.0.8 – 2009/03/13

M2M User Guide
4.2 Example 2: transmit TCP data (text mode)
AT+CFUN=1
OK
AT+COPS=0
OK
AT+CGATT=1
OK
AT$NWACT=1,"INTERNET"
OK
AT$NWSO=1,1
OK
AT$NWDF=1,1
OK
AT$NWCN=1,1,0,"168.95.100.100",5000
OK
$NWCN:1,1 // (URC) Connection is established successfully. This session is ready to transmit
data.
AT$NWTX=1,"TCP test 1"
OK
(Server receives "TCP test 1")
$NWTX:1,0 // (URC) Module receives the acknowledgment of all sent data from TCP server.
(Server responses "10 bytes data received!")
M8-21-0012-108 - 25 - Version: 1.0.8 – 2009/03/13

M2M User Guide
$NWRX: 1,23,23 // (URC, module receives 23 bytes data
AT$NWDR=1,23
$NWDR: 1,23,0,"10 bytes data received!"
OK
AT$NWTX=1,"TCP test 2"
OK
(Server receives "TCP test 2")
$NWTX:1,0 // (URC) Module receives the acknowledgment of all sent data from TCP server.
(Server responses "10 bytes data received!")
$NWRX: 1,23,23 // (URC, module receives 23 bytes data
AT$NWDR=1,23
$NWDR: 1,23,0,"10 bytes data received!"
OK
M8-21-0012-108 - 26 - Version: 1.0.8 – 2009/03/13

M2M User Guide
4.3 Example 3: send TCP data speedily (text mode)
AT+CFUN=1
OK
AT+COPS=0
OK
AT+CGATT=1
OK
AT$NWACT=1,"INTERNET"
OK
AT$NWSO=1,1
OK
AT$NWDF=1,1
OK
AT$NWCN=1,1,0,"168.95.100.100",5000
OK
$NWCN:1,1 // (URC) Connection is established successfully. This session is ready to transmit
data.
AT$NWTX=1,"TCP data 1"
OK
(Sent next data before URC "$NWTX:1,0")
AT$NWTX=1,"TCP data 2"
OK
(Sent next data before URC "$NWTX:1,0")
AT$NWTX=1,"TCP data 3"
M8-21-0012-108 - 27 - Version: 1.0.8 – 2009/03/13

M2M User Guide
OK
(Sent next data before URC "$NWTX:1,0")
AT$NWTX=1,"TCP data 4"
OK
(Server receives "TCP data 1", "TCP data 2", "TCP data 3" & "TCP data 4")
$NWTX:1,0 // (URC) Module receives the acknowledgment of all sent data from TCP server.
M8-21-0012-108 - 28 - Version: 1.0.8 – 2009/03/13

M2M User Guide
4.4 Example 4: send large size TCP data (text mode)
AT+CFUN=1
OK
AT+COPS=0
OK
AT+CGATT=1
OK
AT$NWACT=1,"INTERNET"
OK
AT$NWSO=1,1
OK
AT$NWDF=1,1
OK
AT$NWCN=1,1,0,"168.95.100.100",5000
OK
$NWCN:1,1 // (URC) Connection is established successfully. This session is ready to transmit
data.
AT$NWDW=1,"1111111111222222222233333333334444444444555555555566666666667
77777777788888888889999999999000000000011111111112222222222333333333344444
44444555555555566666666667777777777888888888899999999990000000000111111111
12222222222333333333344444444445555555555666666666677777777778888888888999
99999990000000000111111111122222222223333333333444444444455555555556666666
66677777777778888888888999999999900000000001111111111222222222233333333334
44444444455555555556666666666777777777788888888889999999999000000000011111
11111222222222233333333334444444444555555555566666666667777777777888888888
899999999990000000000",0
M8-21-0012-108 - 29 - Version: 1.0.8 – 2009/03/13

M2M User Guide
OK // Write 600 bytes data into TX-buffer. there are 600 bytes data in TX-buffer.
AT$NWDW=1,"1111111111222222222233333333334444444444555555555566666666667
77777777788888888889999999999000000000011111111112222222222333333333344444
44444555555555566666666667777777777888888888899999999990000000000111111111
12222222222333333333344444444445555555555666666666677777777778888888888999
99999990000000000111111111122222222223333333333444444444455555555556666666
66677777777778888888888999999999900000000001111111111222222222233333333334
44444444455555555556666666666777777777788888888889999999999000000000011111
11111222222222233333333334444444444555555555566666666667777777777888888888
899999999990000000000",1
OK // Write next 600 bytes data into TX-buffer. Totally, there are 1200 bytes data in TX-buffer.
AT$NWDW=1,"1111111111222222222233333333334444444444555555555566666666667
77777777788888888889999999999000000000011111111112222222222333333333344444
44444555555555566666666667777777777888888888899999999990000000000111111111
1222222222233333333334444444444555555555566666666667777777777",0
OK // Write next 270 bytes data into TX-buffer. Totally, there are 1470 bytes data in TX-buffer.
AT$NWTX=1,,1
OK
(Server receives 1470 bytes data)
$NWTX:1,0 // (URC) Module receives the acknowledgment of all sent data from TCP server.
M8-21-0012-108 - 30 - Version: 1.0.8 – 2009/03/13

M2M User Guide
5 M2M specific error result code
+CME ERROR:
Syntax
Result Code
201 parameter not allowed
202 GPRS suspended
203 M2M already activated
204 M2M not activated
205 internal error
206 M2M session is in use
207 No free M2M session
208 M2M session not open
209 other process is running
210 connection already established
211 connection not established
212 TX-buffer space insufficient
213 No data in TX-buffer
214 data format error in hex mode
215 GPRS busy temporarily
216 address or port is already in use
217 server cannot be reached
218 connection is refused by peer
219 size of the data is too large
220 connection has been reset
221 connection has been abort
222 bearer has been disconnected
223 GPRS not ready
224 GPRS bear not ready
225 a similar operation is in progress
226 GPRS connection is already open
M8-21-0012-108 - 31 - Version: 1.0.8 – 2009/03/13