Ublox LISA-C200 Installation and operating instructions

LISA-C200 & FW75-C200
AT commands examples
u-blox CDMA 1xRTT wireless modules
Application Note
locate, communicate, accelerate
www.u-blox.com
Abstract
This document provides detailed examples of using the AT
commands for u-blox LISA-C200 and FW75-C200 CDMA 1xRTT
wireless modules.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 2 of 41
Document Information
Title
LISA-C200 & FW75-C200
AT commands examples
Subtitle
u-blox CDMA 1xRTT wireless modules
Document type
Application Note
Document number
CDMA-CS-12000
Document status
Preliminary
Document status information
Objective
Specification
This document contains target values. Revised and supplementary data will be published
later.
Advance
Information
This document contains data based on early testing. Revised and supplementary data will
be published later.
Preliminary
This document contains data from product verification. Revised and supplementary data
may be published later.
Released
This document contains the final product specification.
This document and the use of any information contained therein, is subject to the acceptance of the u-blox terms and conditions. They
can be downloaded from www.u-blox.com.
u-blox makes no warranties based on the accuracy or completeness of the contents of this document and reserves the right to make
changes to specifications and product descriptions at any time without notice.
u-blox reserves all rights to this document and the information contained herein. Reproduction, use or disclosure to third parties without
express permission is strictly prohibited. Copyright © 2012, u-blox AG.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 3 of 41
Contents
Contents..............................................................................................................................3
1Introduction..................................................................................................................5
2Service provisioning.....................................................................................................5
2.1 Service provisioning in Verizon networks .............................................................................................. 5
2.1.1 Module activation ......................................................................................................................... 5
2.1.2 PRL Update.................................................................................................................................... 6
2.2 Service Provisioning in Sprint networks ................................................................................................. 6
2.2.1 Module Activation ......................................................................................................................... 6
2.2.2 Firmware Upgrade......................................................................................................................... 7
2.2.3 PRL Update.................................................................................................................................. 10
3Storing parameters ....................................................................................................10
4Network registration and Idle State .........................................................................11
4.1 CDMA registration.............................................................................................................................. 11
4.1.1 Network Registration................................................................................................................... 11
4.1.2 Low Power Mode Registration..................................................................................................... 11
4.1.3 Power Down registration ............................................................................................................. 12
5TCP/IP AT commands..................................................................................................13
5.1 Socket Connect .................................................................................................................................. 13
5.2 Socket Write....................................................................................................................................... 13
5.2.1 Binary mode ................................................................................................................................ 13
5.2.2 Base syntax.................................................................................................................................. 14
5.2.3 CDMA network coverage lost...................................................................................................... 14
5.3 Socket operations with “Keep Alive” option....................................................................................... 16
5.4 Socket Read........................................................................................................................................ 17
5.5 Socket Close....................................................................................................................................... 18
5.5.1 By the module ............................................................................................................................. 18
5.5.2 By the remote host ...................................................................................................................... 18
6UDP/IP AT commands.................................................................................................19
6.1 Socket write (+USOST)........................................................................................................................ 19
6.1.1 Base syntax.................................................................................................................................. 19
6.1.2 Binary mode ................................................................................................................................ 19
6.2 Socket Read (+USORF) ........................................................................................................................ 20
6.3 Direct Link (+USODL) .......................................................................................................................... 20
6.3.1 Enter and exit from Direct Link Mode .......................................................................................... 20
6.3.2 Closing the Connection............................................................................................................... 21
7FTP AT Commands......................................................................................................22

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 4 of 41
8HTTP AT commands....................................................................................................25
9GPIO AT commands....................................................................................................26
10 Multiplexer AT commands.........................................................................................26
11 File System AT commands .........................................................................................27
12 SMS AT Commands ....................................................................................................28
12.1 Reading a single message ............................................................................................................... 28
12.2 Listing all messages......................................................................................................................... 28
12.3 Delete one single message or multiple messages............................................................................. 29
12.4 Deleting all messages...................................................................................................................... 32
12.5 Write and/or send one single message ............................................................................................ 34
12.6 Storing an SMS message................................................................................................................. 34
12.7 Sending a Stored SMS message ...................................................................................................... 35
Appendix ..........................................................................................................................37
AList of Acronyms.........................................................................................................37
BError Codes for Sprint’s OMADM..............................................................................39
Related documents...........................................................................................................40
Revision history................................................................................................................40
Contact..............................................................................................................................41

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 5 of 41
1Introduction
This document provides examples of using AT commands with u-blox LISA-C200 and FW75-C200 CDMA 1xRTT
wireless modules. Refer to u-blox LISA-C200 and FW75-C200 AT Commands Manual [1] for the command
descriptions. The following symbols are used to highlight important information within the document:
An index finger points out key information pertaining to integration and performance.
A warning symbol indicates actions that could negatively impact or damage the module.
This document applies to the following products:
oFW75-C200 series
oLISA-C200 series
These icons will be used to indicate applicability to the related products:
: FW75-C200 series
: LISA-C200 series
If the subchapter applies to a specific product the related icon will be provided there.
2Service provisioning
2.1 Service provisioning in Verizon networks
Some logistic preparation is required prior to activating a module on Verizon Networks, we recommend
that customers directly contact their Verizon Customer Representative to properly setup the wireless
accounts. Once the lines have been provisioned, proceed with the activation steps as noted below.
2.1.1 Module activation
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT$MDN?
0000002423
OK
Review the actual MDN in the module, if the response
is similar to the example, then the module isn’t active
yet.
AT+CDV=*22899
NO CARRIER
+UACTIND: 0
OK
Starts the Over-The-Air activation process, use the
code *22899 for module activation, make sure it has
been provisioned by Verizon prior to this step,
otherwise it will be unsuccessful.
+UACTIND: 0 indicates a successful OTA provisioning
session.
If the response is +UACTIND: 1, the terminal is either
not activated or the OTA session failed.
AT$MDN?
8584726201
OK
Reviews the new MDN stored in the module
LISA-C
FW-75
LISA-C
FW-75

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 6 of 41
Command
Response
Description
AT$QCMIPGETP=0
Profile:0 Enabled
NAI:[email protected]
Home Addr:0.0.0.0
Primary HA:255.255.255.255
Secondary HA:0.0.0.0
MN-AAA SPI:2
MN-HA SPI:300
Rev Tun:1
MN-AAA SS:Set
MN-HA SS:Set
OK
Allows seeing the MIP settings of the module, please
note the NAI profile has been populated with the
values of the new MDN.
AT+CDV=”8588885623”
OK
Make a phone call to verify the cell line has been
setup correctly
NO CARRIER
Hung up call from the receiving party.
2.1.2 PRL Update
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT$PRL?
57001
OK
Checks the actual PRL name loaded into the module
AT+CDV=*22891
NO CARRIER
+UACTIND: 0
OK
Use AT+CDV to start an OTA call, use the code
*22891 to update the PRL version of the module, it
will take approximately 50 sec until the session ends,
the “NO CARRIER” indicator and the +UACTIND: 0
URC will show after this time.
If the response is +UACTIND: 1, the terminal is either
not activated or the OTA session failed.
AT$PRL?
52743
OK
Use this AT command again to verify that the new PRL
has been loaded into the module.
2.2 Service Provisioning in Sprint networks
OMA Device Management is a device management protocol specified by the Open Mobile Alliance
(OMA) Device Management (DM) Working Group and the Data Synchronization (DS) Working Group,
this procedure is used by Sprint on their Over-The-Air Provisioning implementation to activate the
modules.
The OMADM procedure is triggered after the module acquires Service within CDMA Sprint coverage, it
is recommended to allow the module to complete this procedure to have it properly provisioned as this
is an interactive protocol between the terminal and the Service Provider. The data that is updated in this
procedure is:
oConfiguration of the device (including first time use), enabling and disabling features
oAllow changes to settings and parameters of the device
oProvide for new PRL in case the loaded one is out-of-date
oUpdate the module’s FirmWare
2.2.1 Module Activation
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 7 of 41
Command
Response
Description
+UOMASTAT:1,0,0
OK
Start of DC session. It should start with 15-20 seconds
after the power up.
+UOMASTAT:1,1,0
OK
End of DC session. Should take around 50 seconds.
+UOMASTAT:1,0,0
OK
Start of PRL session. It should start within 20-30
seconds after the end of previous session.
+UOMASTAT:1,1,0
OK
End of PRL session. Should take around 40 seconds.
+UOMASTAT:1,0,0
OK
Start of FUMO session. It should start within 20-30
seconds after the end of previous session.
+UOMASTAT:1,1,0
OK
End of FUMO session. Should take around 25
seconds.
This step occurs as there is no Firmware
Upgrade available for this module
In case there is a new Firmware upgrade
available, additional URC’s will be shown
(see next chapter for additional URC’s)
AT$MDN?
9132354027
OK
This command allows reading the new MDN
programmed into the module
AT$QCMIPGETP=1
Profile:1 Enabled
NAI:customerequipmen39@sprint
pcs.com
Home Addr:0.0.0.0
Primary HA:255.255.255.255
Secondary HA:68.28.89.76
MN-AAA SPI:1234
MN-HA SPI:1234
Rev Tun:1
MN-AAA SS:Set
MN-HA SS:Set
OK
Allows seeing the new NAI values assigned to the
module, in FW75/LISA-C modules, those values are
populated and updated internally once they are
provisioned by the service provider.
2.2.2 Firmware Upgrade
In this stage, take the same precautions as the Service Provisioning stage
2.2.2.1 Firmware Upgrade as part of the Module Activation Process
This step will be the continuation of the above process.
No user (client) interaction is needed
Command
Response
Description
+UOMASTAT:2,0,0
OK
Start of Downloading session.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 8 of 41
Command
Response
Description
+UOMASTAT:2,1,0
OK
End of Downloading session.
At this moment, the module enters into
“Download Mode” and is being
programmed, it will come back to Service
after the programming is finished
Most Terminal Emulators will disconnect the
module once it enters into “Download
Mode”, so in order to see the additional
incoming URC, it will be necessary to
reconnect the module to the terminal
emulator.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports new Firmware
version to the server.
+UOMASTAT:1,1,0
OK
End of reporting session.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports the Firmware
Version and checks if there is an update available.
+UOMASTAT:1,1,0
OK
End of Session. Provided there is no more FW upgrade
packages available.
If there is additional packages available,
then it will start a new process from the
“Download Session” stage.
2.2.2.2 User-Initiated Firmware Upgrade
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+FUMO=2
OK
This command starts a Firmware Upgrade Session,
given, there is a new FW available to upgrade the
module to.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports new Firmware
version available.
+UOMASTAT:1,1,0
OK
End of reporting session.
If there is no package available, the session
will end at this stage.
+UOMASTAT:2,0,0
OK
Start of Downloading session.
+UOMASTAT:2,1,0
OK
End of Downloading session.
At this moment, the module enters into
“Download Mode” and is being
programmed, it will come back to Service
after the programming is finished
Most Terminal Emulators will disconnect the
module once it enters into “Download
Mode”, so in order to see the additional
incoming URC, it will be necessary to
reconnect the module to the terminal
emulator.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports new Firmware
version to the server.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 9 of 41
Command
Response
Description
+UOMASTAT:1,1,0
OK
End of reporting session.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports the Firmware
Version and checks if there is an update available.
+UOMASTAT:1,1,0
OK
End of Session. Provided there is no more FW upgrade
packages available.
2.2.2.3 Network initiated Firmware Upgrade
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages.
As the network update will come without
notification, this step can be avoided.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports new Firmware
version available.
+UOMASTAT:1,1,0
OK
End of reporting session.
If there is no additional packages available,
the session will end at this stage.
+UOMASTAT:2,0,0
OK
Start of Downloading session.
+UOMASTAT:2,1,0
OK
End of Downloading session.
At this moment, the module enters into
“Download Mode” and is being
programmed, it will come back to Service
after the programming is finished
Most Terminal Emulators will disconnect the
module once it enters into “Download
Mode”, so in order to see the additional
incoming URC, it will be necessary to
reconnect the module to the terminal
emulator.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports new Firmware
version to the server.
+UOMASTAT:1,1,0
OK
End of reporting session.
+UOMASTAT:1,0,0
OK
Start of session. Checks and reports the Firmware
Version and checks if there is an update available.
+UOMASTAT:1,1,0
OK
End of Session. Provided there is no more FW upgrade
packages available.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 10 of 41
2.2.3 PRL Update
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT$PRL?
50587
OK
This command will return the PRL ID that is currently
in use by the module.
AT+PRL=?
PRL update enabled
OK
This command will notify whether or not it is possible
to perform a PRL update using OMADM.
AT+PRL=1
OK
This command enables the PRL update
using OMADM.
This command is the default mode.
This command enables the network
initiated PRL update.
This command isn’t necessary for AT+PRL=2
to apply.
AT+PRL=2
OK
+UOMASTAT:1,0,0
OK
User initiated PRL update session.
The URC indicates an OMADM session has started.
+UOMASTAT:1,1,0
OK
URC that shows the PRL OMADM session has ended.
AT$PRL?
60780
OK
Read the new PRL ID just loaded into the module.
3Storing parameters
FW75 and LISA-C modules both have an internal algorithm that stores the CDMA RF internal parameters as they
work in different scenarios. To facilitate this behavior, a proper Power down of the module is recommended, the
values saved in this process are:
Cristal Oscillator calibration
Most Recently Used Channels
Radio Frequency values of Power/Temperature performance
It is highly recommended to properly power down the module, as important RF data is stored in this
process.
Command
Response
Description
AT+CPWROFF
OK
Switches off the module and saves current module
settings.
LISA-C
FW-75

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 11 of 41
4Network registration and Idle State
4.1 CDMA registration
The module initial registration in CDMA occurs automatically.
Idle State is defined as the stage in which the CDMA terminal goes into “sleeping mode”, this behavior helps for
energy saving implementation. This will be treated as “Low Power Mode” in order to harmonize the definitions.
The module needs 30 s from the time it was powered up to allow proper registration.
The application should wait until this process is successfully finished before sending AT commands that
may interrupt the process.
4.1.1 Network Registration
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+CREG=1
OK
Turns on the unsolicited registration messages.
This step will help visualize any type of
registration performed by the module.
+CREG:4,54,1
OK
This URC confirms the module has registered with the
operator.
AT+CREG?
+CREG:1,4,54,1
OK
Reports the operator in which the module has
registered (4).
+CREG:4,54,0
OK
Module loses CDMA service and reports the URC.
+CREG:4,54,1
OK
The module re-acquires CDMA service and reports
another URC
4.1.2 Low Power Mode Registration
Forcing the module to work in Low Power Mode, will require it to send a registration to the network, this
registration communicates to the network that the module isn’t in service and that all incoming messages should
be kept until the module returns to service again.
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+CREG=1
OK
Turns on the unsolicited registration messages
This step will help visualize any type of
registration performed by the module.
AT+CREG?
+CREG:1,4,54,1
OK
Returns the System Identification number in which the
module has registered, the last digit reports a
registration in its “Home” system
LISA-C
FW-75
LISA-C
FW-75

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 12 of 41
Command
Response
Description
AT+CFUN=2
OK
+CREG:4,54,0
OK
Sends the module into Low Power Mode.
The reported message specifies the module is now in
Low Power Mode.
The last digit reports the module is “Not
registered,” and requests that all incoming
messages should be kept within the
network until the module registers back as
in “Normal Operation.”
AT+CFUN=0
OK
+CREG:4,54,1
OK
Sends the module back into “Normal Operation.”
Automatically, the module will register back into the
network.
It will return a new URC registration message.
4.1.3 Power Down registration
The CDMA standard defines a “Power Down” registration as a normal procedure to allow the module
to go off the network and disconnect itself. This procedure also requires a new registration in which the
terminal reports to the network that is going out of service, and therefore, all messaging directed to this
device should be kept within the network.
Allow at least 10 s from the time the +CPWROFF command was sent to disconnect the power source to
the module.
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+CREG=1
OK
Enables the Unsolicited Registration Message.
AT+CREG?
+CREG:1,4,54,1
OK
Reports back the registration status of the device.
AT+CPWROFF
OK
Switches off the module.
Allow at least 10 s before disconnecting the
power supply.
LISA-C
FW-75

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 13 of 41
5TCP/IP AT commands
The CDMA cellular device activation procedure performs some automatic changes to the Non-Volatile Items of
the device. These changes are programmed and stored in the module for use while interacting with the Cellular
carrier. As part of the update of the values, some IP settings are also updated at the same time, these IP settings
become the Identification values the terminal uses while accessing Data services. There is no need for any
additional steps.
5.1 Socket Connect
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+USOCR=6
+USOCR:18
OK
TCP socket creation. In this example Socket #18 is
created.
The command response returns the created socket
identifier (in this case #18). If a new socket is created
(without closing the already existent), a new socket
identifier will be returned.
AT+USOCO=18,"195.34.89.241",7
OK
Connect socket #18 to port 7 of a remote host with IP
address 195.34.89.241.
The connection is now uniquely associated to the
socket. Socket is now ready for read/write operations.
AT+USOCL=18
OK
Closes the TCP socket number 18.
5.2 Socket Write
For TCP connectivity, creating a socket connection is required before proceeding to write a TCP Socket. Follow
the steps in section 5.1 to create a TCP Connection.
5.2.1 Binary mode
Command
Response
Description
AT+USOWR=18,2
@
Requests writing 2 data bytes into socket #18. Wait
“@” symbol indicating the data prompt is now open
(AT commands are not allowed in data prompt).
hi
+USOWR: 18,2
OK
Write data bytes.
It will not be possible to write fewer bytes than
the number specified by the AT+USOWR
command.
If more bytes are written than the threshold, the
remaining bytes will be truncated.
The interface is blocked until all bytes are
written.
If the command response is returned, then the data is
sent to lower level of protocol stack.
This is not an acknowledgment received from
the remote host confirming the data was
received.
LISA-C
FW-75

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 14 of 41
5.2.2 Base syntax
Command
Response
Description
AT+USOWR=18,2,”hi”
+USOWR:18,2
OK
Writes 2 data bytes into socket #18, the data should
be written within quotations.
If the command response is returned then the data is
sent to a lower level of the protocol stack. This is not
a notification of an acknowledgment received
from the remote host data bytes have been sent
to.
Some characters are not allowed in base
syntax mode. Check the u-blox AT
command manual [1] for the allowed
characters.
5.2.3 CDMA network coverage lost
First scenario: Network coverage lost after AT+USOWR command, base syntax
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+CREG=1
OK
Enables the URC for registration.
AT+USOCR=6
+USOCR:19
OK
Creates a TCP socket, the created ID socket is 19.
AT+USOCO=19,"195.34.89.241",7
OK
Creates a connection between Socket ID 19 and Port
7 of the IP Address 195.34.89.241.
AT+USOWR=19,25,”qwerty0122345
6poiuyt15969”
+USOWR:19,25
OK
Writing 25 bytes of data into socket ID 19.
+CREG:4,54,0
OK
Registration URC reporting the module is no longer in
cellular coverage.
Please refer to the LISA-C/FW75 AT
Commands Manual [1] for a complete
reference of the +CREG command.
+CREG:4,54,1
OK
Registration URC reporting the module is back into
CDMA cellular coverage.
AT+USOWR=19,30,”zxcvb01234lkj
hg45698rtyui32145”<CR>
In this case, the module lost again CDMA coverage
whilst typing the message, no response was possible
+CREG:4,54,0
OK
Again, the module lost CDMA coverage.
+CREG:4,54,1
OK
Registration URC reporting the module has recovered
CDMA coverage
+USOWR:19,30
OK
URC for the previous AT command prior to loose
CDMA coverage, the data was saved into the module
and sent to the network after it re-acquired CDMA
service.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 15 of 41
Second scenario: Network coverage lost after AT+USOWR command, binary mode
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+CREG=1
OK
+CREG=1 enables the URC notification for terminal
registration
AT+USOCR=6
+USOCR:18
OK
+USOCR=6 creates a TCP socket, the response is that
a Socket 18 was created.
at+usoco=18,"108.217.247.74",
1505
OK
Connect socket 18 to the port 1505 of the IP address
108.217.247.74
AT+USOWR=18,15
@
Request to write 15 bytes of information into socket
18, the @ prompt sign is returned allowing the user to
enter the characters.
Test number 001
After the @ sign, the user can start typing the
message, the message will be truncated at the length
specified at the +USOWR command.
+CREG:4145,7,0
OK
The +CREG URC is reported with the last digit
showing the terminal isn’t registered to the current
network
+CREG:4145,7,1
OK
A new +CREG URC is reported back, showing the
terminal has re-acquired CDMA coverage and is now
back in service.
+USOWR:18,15
OK
The new +USOWR URC is reported back, this time
showing the 15 earlier characters were successfully
written into TCP Socket 18.
Third scenario: Network coverage lost during AT+USOWR command, binary mode
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+CREG=1
OK
+CREG=1 enables the URC notification for terminal
registration
AT+USOCR=6
+USOCR:19
OK
+USOCR=6 creates a TCP socket, the response is a
Socket 19 was created.
at+usoco=19,"108.217.247.74",
1505
OK
Connect socket 19 to the port 1505 of the IP address
108.217.247.74
AT+USOWR=19,120
@
Request to write 120 bytes of information into socket
19, the @ prompt sign is returned allowing the user to
enter the characters.
qwertqwertqwertqwertqwertqwer
tqwertqwertqwertqwertqwertqwe
rtqwertqwert
After the @ prompt sign, the user can start typing the
message.
+CREG:4145,7,0
OK
The +CREG URC is reported with the last digit
showing the terminal isn’t registered to the current
network
qwertqwertqwertqwertqwertqwer
tqwertqwertqwertqwert
The user can still keep writing the message into the
terminal emulator. The message will be truncated at
the length specified in the +USOWR command.
+CREG:4145,7,1
OK
A new +CREG URC is reported back, showing the
terminal has re-acquired CDMA coverage and is now
back into CDMA service.
+USOWR:19,120
OK
The new +USOWR URC is reported back, this time
showing the total amount of characters were
successfully written into TCP Socket 19.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 16 of 41
5.3 Socket operations with “Keep Alive” option
In “Keep Alive” mode, the module periodically sends dummy TCP packets to prevent the network from
closing the inactive context.
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+USOCR=6
+USOCR:78
OK
Creates a TCP socket, the return was that a socket
number 78 was created.
AT+USOSO=78,65535,8,1
OK
This step enables the “Keep Alive” mode for the TCP
socket:
78: Socket number
65535: Specifies the chosen mode will be
set at Socket level
8: Specifies the mode selected was “Keep
Alive”
1: Enabled the selected mode (in this case
“Keep Alive”).
AT+USOSO=78,6,2,5000
OK
This step configures the inactivity timeout after which
the module will start to send “Keep Alive” packets:
78: Socket number
6: Settings at TCP Protocol level
2: Chooses the “Keep Alive” option
5000: Timeout in milliseconds configured in
the ”Keep Alive” mode

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 17 of 41
5.4 Socket Read
First scenario
Command
Response
Description
+UUSORD: 33,5
Remote host sends the module 5 data bytes. The
module notifies via URC that there are 5 bytes of data
information stored for socket ID 33.
AT+USORD=33,5
+USORD: 33,5,"hello"
OK
Retrieves the total amount of data received.
Second scenario
Command
Response
Description
+UUSORD: 48,32
Remote host sends the module 32 data bytes. The
module notifies via URC that there are 32 bytes of
data information stored for socket ID 48.
AT+USORD=48,15
+USORD: 48,15,"u-blox AG
TCP/U"
OK
With this command, the device is retrieving only 15
out of the 32 bytes of data originally reported for
Socket ID 48.
+UUSORD: 48,17
Remote host sends another URC indicating there is
still 17 bytes of data pending to be retrieved for
Socket ID 48.
AT+USORD=48,17
+USORD: 48,17,"DP test
service"
OK
This command will retrieve the remaining 17 bytes of
data still pending in the host server.
No additional URC has been received after reading all
remaining data, therefore all data has been recovered.
Third scenario
Command
Response
Description
+UUSORD: 63,15
Remote host sends the module 15 data bytes. The
module notifies via URC that there are 15 bytes of
data information stored for socket ID 63.
AT+USORD=63,5
+USORD: 63,5,"good "
OK
This command requests to read only 5 out of the 15
bytes of data stored in host server.
+UUSORD: 63,10
Remote host sends the module the URC that there are
still 10 bytes of data pending to be read for socket ID
63.
AT+USORD=63,5
+USORD: 63,5,"morni"
OK
This command requests to read only 5 out of the 10
bytes of data stored in host server.
+UUSORD: 63,20
A new URC notifies the host server has increased the
amount of data stored for this Socket ID, from the
reamining 5 to a new size of 20 bytes of data
available.
AT+USORD=63,20
+USORD: 63,20,"ng tostill
warm an"
OK
With this command, the module is requesting the
host server to send all the 20 remaining bytes of data
to the Socket ID 63.
No additional URC has been received after reading all
remaining data, therefore all data has been recovered.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 18 of 41
5.5 Socket Close
5.5.1 By the module
Command
Response
Description
AT+USOCL=18
OK
Socket closed by the module (socket #18).
No URC notification is returned.
5.5.2 By the remote host
Command
Response
Description
+UUSOCL: 18
URC notifying the user that socket number 18 has
been disconnected by the remote host.
At this point, user has to close the socket.
at+usocl=18
OK
User closes socket number 18 as a consequence of
the previous URC.

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 19 of 41
6UDP/IP AT commands
6.1 Socket write (+USOST)
6.1.1 Base syntax
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+USOCR=17
+USOCR: 18
OK
UDP socket creation. In this example Socket #18 is
created.
The response returns the new socket identifier (in this
example #18). If a new socket is created, a new
socket identifier will be returned.
AT+USOST=18,"108.217.247.74",
1500,15,”0123456789qwert”
OK
Request to write 15 bytes of data into socket #18
specifying IP address and UDP port of the remote host
UDP packet has to be sent to. It is necessary to specify
the length of data to be written and the data to be
written.
If more bytes are written with respect to the
threshold, the remaining data will be
truncated.
The interface is blocked until all data is written.
The command response is returned. This means the
data is sent to lower level of protocol stack. This is not
an acknowledgment, UDP is a connectionless
protocol.
6.1.2 Binary mode
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+USOCR=17
+USOCR: 108
OK
UDP socket creation. In this example Socket #108 is
created.
The response returns the new socket identifier (in this
example #108). If a new socket is created, a new
socket identifier will be returned.
at+usost=108,"108.217.47.74",
1500,4
@
Create the UDP connection to “108.217.247.74” on
port 1500
Prompt @ is waiting for data to be entered
LISA-C
FW75

LISA-C200 & FW75-C200
AT commands examples - Application Note
CDMA-CS-12000 Preliminary Page 20 of 41
Command
Response
Description
main
+USOST: 108,4
OK
Write data bytes.
It is not possible to write fewer bytes than the
number specified with AT+USOWR.
If more bytes are written than specified in the
threshold, the remaining bytes will be truncated.
The interface is blocked until all bytes are
written.
If the command response is returned, then the data is
sent to lower level of protocol stack.
This is not an acknowledgment received from
the remote host confirming the data was
received.
at+usocl=108
OK
Closing the socket.
6.2 Socket Read (+USORF)
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+USOCR=17
+USOCR:18
OK
A UDP socket has been created (#18)
+UUSORF: 18,15
The URC +UUSORF notifies that there is a packet of
15 bytes ready to be read in socket #18.
AT+USORF=18,15
+USORF:
18,"108.217.247.74",220,15,"0
123456789qwert"
OK
A request to read 15 characters of data to socket #18
is sent.
The command response indicates:
Read socket identifier (#18)
Remote IP address
Remote UDP port
Number of read data bytes
Read data bytes (between quotation marks)
AT+USOCL=18
OK
Closing the UDP socket, terminal goes back to idle
state
For UDP Socket implementation it is highly recommended to use AT commands +USOST and +USORF
instead of +USOCO, +USOWR and +USORD.
6.3 Direct Link (+USODL)
6.3.1 Enter and exit from Direct Link Mode
Command
Response
Description
AT+CMEE=2
OK
Set verbose error messages
AT+USOCR=17
+USOCR:18
OK
A UDP socket has been created (#18)
AT+USOCO=18,"108.217.247.74",1
500
OK
A socket connection is made to the IP Address
108.217.247.74 port 1500
AT+USODL=18
CONNECT
With this command, a Direct Link Socket connection is
established, the URC confirms the connection.
1234567890
qwerty
1234567890
qwerty
The prompt stays idle waiting for information, in this
case, the user entered characters and the terminal
emulator showed the characters back.