Raven XT UserGuide PDF

Raven XT GPRS/EDGE
User Guide
20070914
Rev 3.0B
Preface
Important Notice
Duetothenatureofwirelesscommunications,transmission
andreceptionofdatacanneverbeguaranteed.Datamaybe
delayed,corrupted(i.e.,haveerrors)orbetotallylost.
Althoughsignificantdelaysorlossesofdataarerarewhen
wirelessdevicessuchastheSierraWirelessAirLinkRavenXT
areusedinanormalmannerwithawellconstructednetwork,
theSierraWirelessAirLinkRavenXTshouldnotbeusedin
situationswherefailuretotransmitorreceivedatacouldresult
indamageofanykindtotheuseroranyotherparty,including
butnotlimitedtopersonalinjury,death,orlossofproperty.
SierraWirelessacceptsnoresponsibilityfordamagesofany
kindresultingfromdelaysorerrorsindatatransmittedor
receivedusingtheSierraWirelessAirLinkRavenXT,orfor
failureoftheSierraWirelessAirLinkRavenXTtotransmitor
receivesuchdata.
Safety and Hazards
DonotoperatetheSierraWirelessAirLinkRavenXTinareas
whereblastingisinprogress,whereexplosiveatmospheres
maybepresent,nearmedicalequipment,nearlifesupport
equipment,oranyequipmentwhichmaybesusceptibletoany
formofradiointerference.Insuchareas,theSierraWireless
AirLinkRavenXTMUSTBEPOWEREDOFF.TheSierra
WirelessAirLinkRavenXTcantransmitsignalsthatcould
interferewiththisequipment.
DonotoperatetheSierraWirelessAirLinkRavenXTinany
aircraft,whethertheaircraftisonthegroundorinflight.In
aircraft,theSierraWirelessAirLinkRavenXTMUSTBE
POWEREDOFF.Whenoperating,theSierraWirelessAirLink
RavenXTcantransmitsignalsthatcouldinterferewith
variousonboardsystems.
Note: Some airlines may permit the use of cellular phones while the
aircraft is on the ground and the door is open. Sierra Wireless AirLink
Raven XT may be used at this time.
Thedriveroroperatorofanyvehicleshouldnotoperatethe
SierraWirelessAirLinkRavenXTwhileincontrolofavehicle.
Doingsowilldetractfromthedriveroroperatorscontroland
operationofthatvehicle.Insomestatesandprovinces,
operatingsuchcommunicationsdeviceswhileincontrolofa
vehicleisanoffence.
Limitation of
Liability
Rev 3.0B Feb.08
Theinformationinthismanualissubjecttochangewithout
noticeanddoesnotrepresentacommitmentonthepartof
SierraWireless.SIERRAWIRELESSANDITSAFFILIATES
SPECIFICALLYDISCLAIMLIABILITYFORANYANDALL
Preface
DIRECT,INDIRECT,SPECIAL,GENERAL,INCIDENTAL,
CONSEQUENTIAL,PUNITIVEOREXEMPLARYDAMAGES
INCLUDING,BUTNOTLIMITEDTO,LOSSOFPROFITSOR
REVENUEORANTICIPATEDPROFITSORREVENUE
ARISINGOUTOFTHEUSEORINABILITYTOUSEANY
SIERRAWIRELESSPRODUCT,EVENIFSIERRAWIRELESS
AND/ORITSAFFILIATESHASBEENADVISEDOFTHE
POSSIBILITYOFSUCHDAMAGESORTHEYARE
FORESEEABLEORFORCLAIMSBYANYTHIRDPARTY.
Notwithstandingtheforegoing,innoeventshallSierra
Wirelessand/oritsaffiliatesaggregateliabilityarisingunderor
inconnectionwiththeSierraWirelessproduct,regardlessof
thenumberofevents,occurrences,orclaimsgivingriseto
liability,beinexcessofthepricepaidbythepurchaserforthe
SierraWirelessproduct.
Patents
Portionsofthisproductmaybecoveredbysomeorallofthe
followingUSpatents:
5,515,013
5,629,960
5,845,216
5,847,553
5,878,234
5,890,057
5,929,815
6,169,884
6,191,741
6,199,168
6,339,405
6,359,591
6,400,336
6,516,204
6,561,851
6,643,501
6,653,979
6,697,030
6,785,830
6,845,249
6,847,830
6,876,697
6,879,585
6,886,049
6,968,171
6,985,757
7,023,878
7,053,843
7,106,569
7,145,267
7,200,512
D442,170
D459,303
andotherpatentspending.
LicensedunderthefollowingNortelNetworksLimited
patents:
UnitedStatespatentnumbers:5128925,5398247
Francepatentnumbers:2665993,2653959,2659812,2745091
Copyright
2008SierraWireless.Allrightsreserved.
Trademarks
AirCardandHeartoftheWirelessMachineareregistered
trademarksofSierraWireless.Watcherisatrademarkof
SierraWireless,registeredintheEuropeanCommunity.
AirLinkandAceWarearetrademarksofSierraWireless.
SierraWireless,theSierraWirelesslogo,theredwavedesign,
andtheredtippedantennaaretrademarksofSierraWireless.
WindowsisaregisteredtrademarkofMicrosoftCorporation.
Othertrademarksarethepropertyoftherespectiveowners.
Rev 3.0B Feb.08
ii
Preface
Contact
Information
Support Desk:
Phone: 1-877-231-1144
Hours: 5:00 AM to 5:00 PM Pacific Time,
Monday to Friday, except US Holidays
E-mail: support@sierrawireless.com
Sales Desk:
Phone: 1-510-781-4200
1-604-232-1488
Hours: 8:00 AM to 5:00 PM Pacific Time
E-mail: MobileandM2Msales@sierrawireless.com
Post: Sierra Wireless America

3159 Corporate Place
Hayward, CA
USA
94545
Sierra Wireless
13811 Wireless Way
Richmond, BC
Canada
V6V 3A4
Fax: 1-510-781-4299
1-604-231-1109
Web: www.sierrawireless.com
Consultourwebsiteforuptodateproductdescriptions,
documentation,applicationnotes,firmwareupgrades,trouble
shootingtips,andpressreleases:
www.sierrawireless.com
Revision History
Revision
number
Release
date
Changes
1.x
2003-2005
AirLink Communications documentation - CDPD, CDMA, and GPRS.
2.x
Q2: 2005-Q2:
2007
AirLink Communications documentation - CDMA, EV-DO, EDGE, and

HSDPA.
3.0
in draft
Converted documentation from AirLink Communications documentation

format into Sierra Wireless documentation format. Phase II of the conversion
completed.
Raven modem line documentation is revised.
Rev 3.0B Feb.08
iii
Contents
Introduction to the Raven XT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
ALEOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
AceWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
AceManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Simplified Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Monitor and Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
AceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Network Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
AceView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Modem Doctor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Modem Doctor USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Connecting to the your cellular provider Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Steps of a connection: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Dynamic vs. Static IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
EDGE Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
EDGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Consumption: (@12V DC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standards/Approvals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
10
10
10
10
11
11
11
11
Interface Port Pin-Outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Activating Raven XT on your cellular provider Network . . . . . . . . . . . . . . . .13

Installating the SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Cellular Account Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
13
14
Configuring the APN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Rev 3.0B Feb.08
Contents
Hardware Installation of the Raven XT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Connecting to Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Connecting to a Computer or other Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Light Patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring your Raven XT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Using AceManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Using Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Using a Terminal Application with AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Universal Serial Bus (USB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Changing the USB port communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Installing the USB driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Virtual Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Virtual Serial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Using the Virtual Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using USB Ethernet with AceManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Using USB Ethernet with a Terminal Emulation Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Using the Virtual Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Using the USB virtual serial port with AceManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Using the USB virtual serial port with a Terminal Emulation Utility . . . . . . . . . . . . . . . . . . . . 47
Data Communication and Host Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Basic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Serial Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Data Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Basic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Start up Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
AT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
PassThru Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Telnet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Serial Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
SLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
UDP and UDP Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
UDP Auto Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Reliable UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Rev 3.0B Feb.08
Contents
UDP Multicast Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

TCP and TCP Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
TCP Auto Answer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Hybrid Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Data Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Public and Private Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Internal DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Keepalive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring Keepalive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Data usage using Keepalive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
IP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Reasons to contact the modem and/or the connected device: . . . . . . . . . . . . . . . . . . . . . . . . . 63
Understanding Domain Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

car54.mydomain.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
car54.mydomain.com.ca. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Dynamic Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Using IP Manager with your Raven XT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Restrictions for Modem Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Data Usage for IP Manager Server Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Eairlink.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Understanding DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configuring DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
The PPP-Peer Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Configuring Modbus/BSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Modbus Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Telemetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Remote Terminal Unit (RTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Supervisory Control and Data Acquisition (SCADA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Programmable Logic Controller (PLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Modbus TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Raven Modbus on UDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configuring the Raven XT at the Polling Host for Modbus on UDP . . . . . . . . . . . . . . . . . . . . 72

Configuring the Remote Raven XTs for Modbus with UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
SNMP : Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . .80

Management Information Base (MIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Rev 3.0B Feb.08
Contents
SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Listening Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Security Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Trap Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Community String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
SNMP MIB Definition Sample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Display Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Product ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Info (information). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
*DEVICEID? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
*NETPHONE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
&V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Information Displayed in AceManager without AT Commands Listed . . . . . . . . . . . . . . . . . . . . . . . 90
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
*BOARDTEMP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
*HOSTMODE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
*NETERR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
*NETIP?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
*NETOP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
*NETRSSI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
*NETSERV?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
*NETSTATE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
*POWERIN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
+ICCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
+RCIQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Information Displayed in AceManager without AT Commands Listed . . . . . . . . . . . . . . . . . . . . . . . 93
AT Commands Requiring PassThru mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
+CCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Misc (Miscellaneous) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
+++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
A/ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
D[method][d.d.d.d][/ppppp] or D[method][@name][/ppppp] . . . . . . . . . . . . . . . . . . . . . . . . . . 95
DS=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Hn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
OPRG=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
S53=[method][d.d.d.d][/ppppp] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
&W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
*DATE=[mm/dd/yyyy],[hh:mm:ss]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
*DPORT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Rev 3.0B Feb.08
Contents
*HOSTPAP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
*NETALLOWZEROIP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
*NETPW=pw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
*NETPHONE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
*NETUID=uid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
*STATICIP=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
*STATUSCHK=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
En . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
With more than one connection types (serial, Telnet, and USB) the echo command can be set
differently on each interface. Qn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
S3=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
S4=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
S5=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
S6=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
S8=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
S9=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
S10=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
S23=[speed],[databits][parity][stop bits] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
S50=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
S51=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
S211=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Vn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Xn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
&Cn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
&Dn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
&Sn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
\APPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Set modem operation to PPP mode. Cannot be configured in AceManager.\ASLIP . . . . . . 102
\Qn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
*CTSE=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
*MODEMHISPEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
*NUMTOIP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
*PPPNOCARRIER=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
S0=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
S7=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
S60=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
S221=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
TCPS=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
TCPT=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
*ENQ=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
AIP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
HOR=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
MDhh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
S82=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
S83=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
*DU=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
*UALL=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
*UDPLAST=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
*USD=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Rev 3.0B Feb.08
Contents
*DNSn=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
*DNSUPDATE=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
*DNSUSER=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Dynamic IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
*DOMAIN=name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
*IPMANAGERn=[name][IP address]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
*IPMGRKEYn=key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
*IPMGRUPDATEn=m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
*MODEMNAME=name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
PPP/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
*DHCPSERVER=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
*HOSTAUTH=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
*HOSTNETMASK=n.n.n.n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
*HOSTPEERIP=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
*HOSTPRIVIP=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
*HOSTPRIVMODE=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
*HOSTPW=string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
*HOSTUID=string. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
PassThru . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
\APASSTHRU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
*CSX1=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
*PTINIT=string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
*PTREFRESH=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
*RESETPERIOD=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
*NETSMS2EMAIL=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
*SMTPADDR=[d.d.d.d][name] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
*SMTPFROM=email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
*SMTPPW=pw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
*SMTPSEND=email[body] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
*SMTPSTATUS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
*SMTPSUBJ=subject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
*SMTPUSER=user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
DAE=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
*DATZ=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
*IPPING=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
*IPPINGADDR=[d.d.d.d][name]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
*MSCIUPDADDR=name[/port] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
*MSCIUPDPERIOD=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
*NETWDOG=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
*RESETCFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
*SNMPCOMMUNITY=string. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
*SNMPPORT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
*SNMPSECLVL=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
*SNMPTRAPDEST=host/[port] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
*SNTP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
*SNTPADDR=[d.d.d.d][name] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
*TELNETTIMEOUT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
*TPORT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
*TQUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Friends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Rev 3.0B Feb.08
Contents
FM=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Fn=[d.d.d.d] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
*DBGCOMMLVL=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
*DBGIPLVL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
*DBGPPPLVL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Telemetry/Addr List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

IPL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
MVLEN=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
MVMSK=hh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
MVOFF=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
MVOPT=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
MVTYP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
RKEY=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Addr List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
MLISTid=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
MLISTXhexid=d.d.d.d. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Edge/HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
*NETAPN=apn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+CGQMIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+CGQREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+COPS=mode,[format][,oper] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
124
124
124
125
Windows Dial-up Networking (DUN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Installing a modem driver for Raven XT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Creating a Dial-Up Networking (PPP) Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Connecting to the Internet Using DUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AceView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Windows DUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Rev 3.0B Feb.08
1: Introduction to the Raven XT

ALEOS
AceWare
Connecting to the your
cellular provider
Network
EDGE Communication
PoweredbyALEOS,RavenXTmodemsaredesignedto
maintainareliable,consistentnetworkconnection.Witha
serialinterfaceandavastlibraryofmachineprotocols,the
RavenXTisaworkhorseforindustrialandmissioncritical
applications.ClassIDivison2certifiedasnonincendive
equipment,theRavenSeriesisideallysuitedforusein
hazardousenvironments.
Keyapplicationsincludeutilities,manufacturing,automation,
oilandgas,SCADA,telemetry,HomelandSecurityandasset
monitoring.
Figure 1-1: Sierra Wireless AirLink Raven XT
ALEOS
ALEOS,theembeddedcoretechnologyoftheSierraWireless
AirLinkproductssimplifiesinstallation,operationandmainte
nanceofanysolution,andprovidesanalwayson,always
awareintelligentconnectionformissioncriticalapplications.
ALEOSenables:
Rev 3.0B Feb.08
PersistentNetworkConnectivity
OverTheAir(OTA)Upgrades
Introduction to the Raven XT
WirelessOptimizedTCP/IP
RealTimeNotification
ExtensiveMachineProtocols
PacketLevelDiagnostics
DeviceManagement&Control
ProtocolSpoofing
Figure 1-2: Powered by ALEOS
AceWare
Awirelesssolutionisnotcompleteuntilyouhavesoftware
toolstomanagethedevicesmonitoringyourvaluable
equipment.AceWareisthedevicemanagementand
monitoringapplicationsuiteforSierraWirelessAirLink
productspoweredbyALEOS.
AceManager
AceNet
AceView
ModemDoctor
Thesemodemutilities,exceptAceNet,arefreeofchargeto
thosewhoownSierraWirelessAirLinkmodems.Youcan
downloadtheapplicationsandtheiruserguidesfromthe
SierraWirelessAirLinkSolutionswebsite:http://
www.sierrawireless.com/support.Contactyourdealeror
SierraWirelessrepresentativeforinformationonAceNet.
Note: AceView, AceManager, and AceNet require the Microsoft .NET
Framework v. 1.1 and Microsoft Windows 98, Windows 2000,
Windows XP, or later. You can obtain the Microsoft .NET Framework
from Microsoft at: http://www.microsoft.com/.
AceManager
AceManager,theAceWareremoteconfigurationand
monitoringtool,simplifiesdeploymentandprovidesextensive
monitoring,controlandmanagementcapabilities.
Rev 3.0B Feb.08
AceManagergivesyouthepowertomonitorandcontrolyour
SierraWirelessAirLinkcommunicationsplatformsinreal
time.
Figure 1-3: AceManager
Simplified Deployment
AceMangerprovidestheabilitytoremotelysetupand
configureyourSierraWirelessAirLinkproducts.Remote
devicesetupandconfigurationreducesthedeployment
timelineofyourwirelesssolutionandprovidesaquickerpath
toROI.
Templatesallowyoutoeasilyconfigureotherdevicesinyour
fleetwithidenticalsettings,ensuringasimple,accurate
deployment.
Monitor and Control
AceMangerallowsanadministratortoremotelymonitora
modemsstatus,healthandconfigurationsettings.Theuser
interfacedisplayssignalstrength,cellsiteinformation,byte
countersanderrorconditions,enablingyoutopinpointany
issuesandtroubleshootimmediately.
AceManagerenablesremoteconfigurationandparameter
settingstobechangedorresetinstantlyovertheair,changea
devicesportconfiguration,IPaddresssettings,andmuch
more.Afterconfiguringonemodem,usethetemplatefeature
tocopythatdeviceconfigurationtoothermodems.
Tip: Configuration steps and examples in this guide use
AceManager.
Rev 3.0B Feb.08
AceNet
AceNet,theenterprisegradeproductivityenhancingtool,
enablesyoutoefficientlydeployandmonitorSierraWireless
AirLinkproductsonalargescale.
Figure 1-4: AceNet
Network Monitoring
AceNetallowsyoutoefficientlydeploy,monitor,andmaintain
wirelessnetworksofanysizebyenablingyoutoquickly
configureanentiregroupofSierraWirelessAirLinkmodems
tothesameparametersettingsusingtemplatesbuiltwith
AceManger.
Toensureyourimplementationisoptimal,userscaneasilysee
whenmodemsareoutofcontactandperiodicallypolleach
deviceforperformancestatistics.
AceView
AceViewisanefficientstatusandconnectionmonitoring
applicationwithalowprofile,easytoreadinterface.
Figure 1-5: AceView
Rev 3.0B Feb.08
Modem Doctor
ModemDoctorisatroubleshootinganddiagnosticsutility.
ThisutilitywillallowyoutogetalogfileoftheRavenXT
activitywhichyoucanthensendtoSierraWirelesssupport,
erasethecurrentconfigurationcompletely.,andtemporarily
settheRavenXTtoaknownconfigurationtoaidintrouble
shooting(SOSmode).
Rev 3.0B Feb.08
Figure 1-6: Modem Doctor
Modem Doctor USB

1.
OpentheModemDoctorUSB.exe.
2.
Selectanyoneoption.
Note: If you are using USB port as serial, then USB device is set to
o and if you are using the default option then the USB device is set
to 1.
Theavailableportisautomaticallydetected.Passswordisthe
faultpassword.
3.
PressErase.Themodemwillthenreset.
Note: If you erase the fatory defaults will be restored. USBnet is the
factory default port.
Rev 3.0B Feb.08
Figure 1-7: Modem Doctor: USB connection
Connecting to the your cellular

provider Network
TheRavenXTusesyourcellularproviderasanISP(Internet
ServiceProvider)toconnectyoutotheInternet.
Steps of a connection:
1.
WhenyourRavenXTispoweredon,itautomatically
searchesforcellularserviceusingEDGE.
2.
YourRavenXTestablishesaPPP(PointtoPointProtocol
ordialupconnection)linktotheyourcellularprovider
network,alsocalledregisteringonthenetwork,and
receivesanIPaddress.
3.
WhenyourRavenXThasreceiveditsIPaddressfrom
yourcellularprovider,aconnectiontotheInternetorthe
cellularnetworkisalsoavailableforacomputerorother
deviceconnecteddirectlytotheRavenXT.
Figure 1-8: Connecting to the Internet
TheRavenXTwillperformaonetooneroutingforall
internettraffictoandfromthecomputerorotherenddevice.
OnetoonemeansthatyourRavenXTwillprovidea
connectionforonedevicetotheInternetatatime.InPrivate
Mode,theRavenXTwillprovideNAT(NetworkAddress
Translation)forthecomputerorotherenddevice.
Rev 3.0B Feb.08
Note: The Raven XT does not provide advanced routing required by

one-to-many (several devices connected to one port). If you need to
have more than one device connected to the Internet through your
Raven XT, you will need to have a router connected to the modem.
The modem would provide the one-to-one connection to the router
with the router configured to provide a broader NAT service to the
other devices connected to it.
Dynamic vs. Static IP Addresses

Therearetwotypesofaddressesonnetworks:dynamicand
static.
Dynamicaddressesareassignedonaneedtohavebasis.
YourRavenXTmightnotalwaysreceivethesameaddress
eachtimeitconnectswithyourcellularprovider.
Staticaddressesarepermanentlyassignedtoaparticular
accountandwillalwaysbeusedwheneveryourRavenXT
connectstotheInternet.TheIPaddresswillnotbegiven
toanyoneelse.
MostISPs(cellularincluded)usedynamicIPaddressesrather
thanstaticIPaddressessinceitallowsthemtoreuseasmaller
numberofIPaddressesforalargenumberofcustomers.A
dynamicIPaddressissuitableformanycommonInternet
uses,suchaswebbrowsing,lookingupdataonanother
computersystem,orotherclientfunctions(suchasdataonly
beingsentoutoronlybeingreceivedafteraninitialrequest).
Tip: If your account with your cellular provider includes a dynamic IP
address and you need a static IP, please consult your your cellular
provider Representative for more information about changing your
account for static IP support.
IfyouneedtocontactyourRavenXT,adeviceconnectedto
theRavenXT,orahostsystemusingtheRavenXTfromthe
Internet,youneedtohaveaknownIP(suchasonewhichis
static)ordomainname(anIPaddresswhichisconvertedbya
DNSserverintoawordbasedname).IfyouhaveadynamicIP
addressforyourmodem,youcanuseaDynamicDNSservice
(suchasIPManager)totranslateyourIPaddressintotoa
domainname.
Rev 3.0B Feb.08
Caution: If you want to connect remotely to your Raven XT using

TCP/IP, the IP address given to your modem by your cellular provider
cannot be a private or internal IP address (such as a custom APN)
unless you are on the same network or inside that networks firewall
(such as with frame relay).
EDGE Communication
GSMNetworksuseSIMcardswhicharesmartcards
containingtheaccountholdersdetails.ASIMcangenerallybe
movedfromonedevicetoanotherallowingforaccountporta
bilityandflexibility.
EDGE
EDGE(EnhancedDataratesforGSMEvolution)providesend
toendpacketdataserviceswithanenhancedconnectivity
buildingonGPRStechnologyandusingtheestablishedGSM
networks.EDGEprovideshighertransmissionratesandbetter
transmissionqualityfordatathanGPRS.EDGEcancarrydata
atspeedstypicallyupto384kbit/sinpacketmode.
WhenEDGEisnotavailable,yourRavenXTwillfallbackto
GPRSfortheconnectiontoyourcellularprovidertoprovide
continuedconnectivity.
GPRS
GeneralPacketRadioService(GPRS)ispacketswitchedwith
manyuserssharingthesametransmissionchannel,butonly
transmittingwhentheyhavedatatosend.Thismeansthatthe
totalavailablebandwidthcanbeimmediatelydedicatedto
thoseuserswhoareactuallysendingatanygivenmoment,
providinghigherutilizationwhereusersonlysendorreceive
dataintermittently.GPRSprovidesspeedsof3070kbpswith
burstsupto170kbps.
Rev 3.0B Feb.08
2: Specifications
Interface Port Pin-Outs

Power Connector
Features and Benefits
EmbeddedIntelligence
LowPowerConsumption
HighSpeedProcessor
HighSpeed2wayData
SerialandUSBPort
MachineProtocols
SimpleIntegrationwithLegacyEquipment
PersistentNetworkConnectivity
RemoteManagementandConfiguration
SuitableforuseinClassI,Division2,GroupsA,B,C,Dor
unclassifiedornonhaardouslocations
Technology
GSMEDGE
WithFallbackto:
GPRS(MS12)
Bands
QuadBandGPRS/EDGE
850MHz,900MHz,1800MHzand1900MHz
Environmental
OperatingTemperature:
30to70Celsius
StorageTemperature:
40to85Celsius
Power Consumption: (@12V DC)
Transmit/Receive(Typical/Max)350/450mA
Idle104mA
InputVoltage928VDC
Standards/Approvals
Rev 3.0B Feb.08
Carrierspecificapprovals
FCC
IndustryCanada
10
Specifications
ThisapparatusissuitableforuseinClassI,Division2,
GroupsA,B,C,Dorunclassifiedornonhazardous
locations.
Warning: Explosion Hazard - Substitution of any

components may impair suitability for Class I,
Division 2.
Host Interfaces
USBTypeB5Pinmini
RS232:DB9DCE(300230400baud)
AntennaConnection:
Cellular50OhmSMA
Dimensions
76mmx25mmx100mm
317grams
Application Interfaces
TCP/IP,UDP/IP,DHCP,HTTP,SNMP,SMTP,SMS,MSCI,
Binary,Modbus,andmore
LED Indicators
Network
Signal
Activity
Power
Interface Port Pin-Outs

Serial Port
Unused
CTS (Clear to Send) < RTS (Request to Send) - >
DSR (Data to Send) < -
4
8
3
7
2
6
1
< - > GND (Ground)

< - DTR Data Terminal Ready)
< - Rx (Receive)
- > Tx (Transmit)
- > DCD (Data Carrier Detect)
Figure 2-1: Serial Port Diagram: Female DB-9 DCE (not to scale)
Power Connector
Rev 3.0B Feb.08
11
Specifications
Not Used
Ground (black)
Not Used
Power (red)
Figure 2-2: Power Connector (not to scale)
Warning: Explosion Hazard - Do not disconnect

equipment unless power has been switched off or
the area is known to be non-hazardous.
Rev 3.0B Feb.08
12
3: Activating Raven XT on your

cellular provider Network
Installating the SIM

Configuring the APN
Thischapterprovidesstepbystepdirectionsforactivating
yourRavenXTontheyourcellularprovidercellularnetwork.
Installating the SIM

TheSIMintheRavenXTisasmartcardsecurelystoringthe
keyidentifyingacellularsubscriber.Generally,youwillonly
needtoinstallaSIMonceinthelifeofthemodemanditmay
bepreinstalledbyyourSierraWirelessRepresentative.
1. Before you start

IftheSIMwaspreinstalled,unlessyouneedtosetacustom
APN,activationofyourmodemiscomplete.
Cellular Account Required
CellularaccountTouseyourmodemyouneedtohavea
SIM(SubscriberIdentityModule)withanactiveaccount
withanEDGEcellularprovider.
Software Required
AceManagerGraphicalinterfaceforenteringmostAT
Commands.YoucandownloadAceManagerfromthe
SierraWirelessAirLinkSolutionswebsite:http://
www.airlink.com/support/.Adefaultinstallationofthis
utilityisassumedlaterinthesedirections
Hardware Required
SerialcableAstraightthroughserialcable.
Note: Until you install a driver for the USB port, you cannot use your
USB port to configure the modem.
Rev 3.0B Feb.08
PoweradapterandapowersourceYouwillneeda
powersupplyandpowersourceforthemodem.
PCorLaptopToconfigurethemodem,youwillneeda
computerwithanavailableserialport.
13
Activating Raven XT on your cellular provider Network
Tools Required
SmallPhillipsscrewdriverThePhillipsscrewdriveris
theonewhichisalsocalledaplus(+)orXscrewdriver.
1. Removing the faceplate

a. UnplugtheRavenXTpowerandallcables.
b. Usingasmallphillipsheadscrewdriver,removethe
screwsonthefront.
c.
Setthefaceplateaside.
Figure 3-1: Faceplate
2. Remove the SIM from the card

a. CarefullyremovetheSIMcardfromthecardyougot
fromyourcellularprovider.
Figure 3-2: Sample of the SIM card
Rev 3.0B Feb.08
14
3. Insert the SIM

Note: The card and SIM may be
a different color than these
examples.
a. RemovetheSIMfromthecardyouobtainedfrom
youryourcellularprovider.
Figure 3-3: Insert SIM in to the modem
b. GentlypresstheSIMcardtosecureinplace.
Tip: The top of the card faces the bottom of the modem.
4. Finishing the SIM installation

Whenthefaceplateisreplacedandsecured,theinstallationof
theSIMiscomplete.
Configuring the APN

TheAPN(AccessPointName)isthewayyourmodemknows
howitwillbecommunicatingwiththenetwork.TheAPN
allowscustomIPaddressingandtailoringyourcompanys
wirelessIPsolutiontomeetthesecurityandIPaddressing
requirementsofyourapplications.
Note: Most accounts use the default addressing solution of Private or
Public IP addresses supplied by the Internet and Proxy APNs. Only if
you have a Static or Custom IP address should you need to configure
a custom APNs.
ThedefaultAPNisInternet.IfyouneedadifferentAPN,use
canuseAceManagertoconfigureit.
Rev 3.0B Feb.08
15
1. Start AceManager
Start>AllPrograms>AirLinkCommunications>AceManager3G
>AceManager3G
2. Connect to the Modem

a. ClicktheConnectbutton.
b. SelectPPP.
c. Entertheconnectioninformation.
ForPPP,selecttheCOMporttowhichthemodemis
connected.
d. Enterthepassword.Thedefaultpasswordwillbe
enteredforyou.
e. SelectOK.
Rev 3.0B Feb.08
16
3. Enter the APN

a. SelectEDGE/HSDPAfromthemenuontheleftsideof
AceManager(underGroups)
Figure 3-5: AceManager : EDGE/HSDPA
b. TypeyourAPNintheNewValuefieldof*NETAPN.
Figure 3-6: AceManager : EDGE/HSDPA - *NETAPN
Optional:Ifyouneedtoconfigureyourmodemforacus
tomAPN,afterenteringtheAPN,thereisadditionalinfor
mationyouwillneedtoenter.
1.
SelectMiscfromthemenuontheleftsideunder
theCommongroup.
Figure 3-7: AceManager : Misc
Rev 3.0B Feb.08
17
2.
EntertheNAIintothenewvaluefieldfor
*NETUIDandenteryournetworkpasswordinto
thenewvaluefieldfor*NETPW.
Figure 3-8: AceManager : Misc - *NETUID, *NETPW
4. Write the Settings to the Raven XT

a. ClicktheWritebuttononthetoolbarofAceManager.
b. WaitforthemessageWriteSuccessfultoappearin
thestatusbar.
Figure 3-9: AceManager : Write
c.
Rev 3.0B Feb.08
ResettheRavenXT.
18
4: Hardware Installation of the

Raven XT
Connecting to Power
Connecting to a
Computer or other
Device
Indicator Lights
Mounting
YourRavenXTshouldbemountedinapositionthatallows
easyaccessforthecablessotheyarenotbent,constricted,in
closeproximitytohighamperage,orexposedtoextreme
temperatures.TheLEDsonthefrontpanelshouldbevisible
foreaseofoperationalverification.Youshouldensurethat
thereisadequateairflowaroundthemodembutthatitiskept
freefromdirectexposuretotheelements,suchassun,rain,
dust,etc.
Inamobilelocation,suchasacarortruck,ensurethelocation
issecurebothagainstabruptmovementsofthevehicleand
fromotheritemscomingintocontactwiththemodem.
Caution: The Raven XT is in a hardened case and designed for use
in industrial and extreme environments. However, unless you are
using cables expressly designed for such environments, they can fail
if exposed to the same conditions the Raven XT can withstand.
Cellular
USB
Serial
Power
Figure 4-1: Raven XT Connectors
Rev 3.0B Feb.08
19
Hardware Installation of the Raven XT
Antennasselectedshouldnotexceedamaximumgainof5dBi
understandardinstallationconfiguration.Inmorecomplex
installations(suchasthoserequiringlonglengthsofcableand/
ormultipleconnections),itsimperativethattheinstaller
followmaximumdBigainguidelinesinaccordancewiththe
radiocommunicationsregulationsoftheFederalCommunica
tionsCommission(FCC),Industry Canada, oryourcountrys
regulatorybody(ifusedoutsidetheUS).
YourRavenXTwillworkwithmostDualBandPCScellular
antennaswithaSMAconnectorthatworksinthehighandlow
frequenciesofthecellulartechnologyofyourmodem.Connect
theprimaryantennaorprimaryRFcabledirectlytothe
antennaconnectoronthebackoftheRavenXT.
Tip: When using a cable to an antenna placed away from the
modem, minimize the length of your cable. All gain from a more
advantageous antenna placement can be lost with a long cable to the
modem.
Connecting to Power
YourRavenXTcanbeusedwitheitherDC,availableinmost
automobiles,or110AC,standardUSwallpower,withthe
appropriatepoweradapter.DCcablesandACadaptersare
availableasoptionalaccessoriesinadditiontotheone
includedwithyourRavenXT.
Note: When using a DC power
source (such as a car battery or
solar cell), Sierra Wireless
recommends placing a fuse (1-2
Amp) on the line close to the
power source to protect your
power source from possible
surges due to shorts or other line
issues.
TheDCpowercablepositiveleadshouldbeconnectedtothe
batteryorpowersourcepositiveterminal.Thepowercable
negativeleadshouldbeconnectedtothebatteryorpower
sourcenegativeterminal.
Tip: The DC power cable has a white wire lead in addition to the
power positive and negative. This is for a feature not present in the
Raven line modems. In the Raven XT, the white wire lead has no
function and can be ignored.
Warning: Explosion Hazard - Do not disconnect

equipment unless power has been switched off or
the area is known to be non-hazardous.
Rev 3.0B Feb.08
20
Connecting to a Computer or
other Device
Figure 4-2: Serial
TheserialportofyourRavenXTcanbeconnecteddirectlyto
mostcomputersorotherdevicesusingastandardstraight
throughcable.IfyouhaveaDCEdevice,youwillneedanull
modemornullmodemcable.
Figure 4-3: USB
YourRavenXTsfullspeed(12Mbit)USB2.0portcanbe
connecteddirectlytomostcomputersorotherdevicesusinga
standardfullspeedUSB2.0cable.Ifthecomputerordevice
youareconnectingorthecableisnotratedforfullspeed,the
modemwillcommunicateatareducedspeedtomatch.The
RavenXTfunctionsasadevice,notahost.
Whenitisconnectedtoacomputer,theUSBportshouldbe
seenasaCOMportorEthernetportaftertheapplicabledriver
isinstalled.
TheRavenXThasastandardminiBconnector.
Warning: The USB port can only be used in a nonhazardous environment.
Indicator Lights
WhenyourRavenXTisconnectedtopowerandanantenna,
thereisaspecificpatterntothelightstoindicateitsoperation
mode.
Rev 3.0B Feb.08
21
Figure 4-4: Raven XT Indicator lights
NetworkIndicatesasuccessfulconnectiontothecellular
networkwithanIPaddressgivenandachannelacquired.
SignalLightshowsthestrengthofthesignalandmaybe
nearlysolid(strongsignal)orflashing(weakersignal).A
slowflashindicatesaveryweaksignal.
RSSI LED Ranges

RSSI/Signal LED Status
Ranges of RSSI (dBm)
On Solid
Equal to or stronger than -69
Fast Blink
-70 to -79
Normal blink
-80 to -89
Slow Blink
-90 to -99
Extinguished
Equal to or weaker than -100
ActivityLightswillflashasdataistransferredtoand
fromthePinPointmodemontheremotenetwork.
Srvc(service)IndicateswhentheconnectionisEDGE.
UnlitindicatesGPRS.
PowerIndicatesthepoweradapterisconnectedand
thereispowergettingtotheRavenXT.
TheResetbutton(ontheleftsideoftheRavenXT)hastwo
functions.Ifitisquicklydepressedandreleased,the
modemwillsimplypowercycletheinternalhardware.If,
however,theresetisdepressedandheldforseveral
seconds(count10slowly,andwaitforthepowerlightto
gooffafterthelightpatternstops),theALEOSconfigu
rationsettingswillreturntothefactorydefaults.
Caution: If you reset the modem configuration using the reset button,
you may to reconfigure your APN.
Rev 3.0B Feb.08
22
Light Patterns
TheLEDsonthefrontofthemodemwillrespondindifferent
patternstoindicatemodemstates.
NormalEachLED,mentionedabove,litasapplicable.
StartupTheLEDswillcyclefromlefttoright.
PassThrumodeNetworkandSignalLEDswillblinkin
tandem.TheActivityLEDwillblinkwhentransmittingor
receivingdata.
SOSTheNetworkLEDblinks.
ConfigurationResetTheLEDswillcyclelefttorightand
thenrighttoleft4times.
AuthenticationFailureTheNetwork,Signal,and
ActivityLEDsblinkevery2seconds.
DataRetryTheNetwork,Signal,andActivityLEDsblink
every3seconds.
Mounting
AnoptionalaccessoryforyourRavenXTisamountingkit,
whichincludesabracket.Thebracketisdesignedtosnugly
cradlethemodemandholditinplacewhereyouneedit.You
canuseastraparoundthebracketandmodemforextra
security.Thebracketcanbeattachedtoastationarylocation
using#6screwswiththemountingholediameterapproxi
mately0.150.
Theinstructionstobracketinstallationisfollowing:
Rev 3.0B Feb.08
1.
Mountthebracketusingnumber6screws.Therearetwo
holeseach,tofastenscrews,andminimumofonehole
eachendisrequiredformountingbracket.
2.
PositionRavenXTbetweenAlignmentears.
3.
EngagetopgrooveinbodyofRavenXTwithtwotabs.
4.
PushonfarsideofRavenXTincentersothatittouches
sideofBracket.
5.
Pressdownandreleasewhenuppergrooveonfarsideof
RavenXTalignswithtabs.
6.
Releasetocompleteinstallationintomountingbracket.
7.
Toremove,reversetheprocess(steps16).
23
Figure 4-5: Mounting bracket installation
Rev 3.0B Feb.08
24
Figure 4-6: 100-170-1013 : Mounting Bracket for Raven XT
Rev 3.0B Feb.08
25
5: Configuring your Raven XT

Using AceManager
Using Templates
Using a Terminal
Application with AT
Commands
WithALEOSasitsbrain,theRavenXTisahighlyconfigu
rabledevice,morethanjustadumbmodem.
ToconfigureyourRavenXT,youhavetwooptions.Youcan
usetheconfigurationandmanagementapplicationsofthe
AceWaresuiteoryoucanuseaterminalemulatorapplication
suchasHyperTerminal,PuTTY,ormanyothers.
SincetheAceWareapplicationsaredesignedforeaseofuse,
nearlyalldescriptionsandscreenshotsofRavenXTconfigu
rationinthisguideandApplicationNotesaredonewith
AceManager.Inadditiontothevariouschaptersinthisguide
givinginformationanddirectionsaboutusingthefeaturesof
yourRavenXT,theConfigurationCommandsappendix
brieflydescribesallthecommandsavailable.Togetamore
expandedviewoftheotherAceManagerfeatures,refertothe
AceManagerGuide.
Afulllistingofalltheconfigurationcommandsforyou
modemareinAppendixA.
Using AceManager
AceManagerisafreeutilityandisavailableontheproductCD
orcanbedownloadedfromtheSierraWirelessAmerica
website:http://www.sierrawireless.com/support/AirLink/
default.aspx.
Tip: AceManager is the same application as Wireless Ace. The
name was changed to fit better with its features.
1. Start AceManager
Start>AllPrograms>AirLinkCommunications>AceManager
Rev 3.0B Feb.08
26
Configuring your Raven XT
2. Connect to your Raven XT

a. ClicktheConnectbutton.
Figure 5-2: AceManager : Connect to Modem
b. Selectaconnectionmethod:
Ifyouareconnectingremotely,youcanuseUDP,TCP,or
SMS.
Ifyouareconnectinglocallywiththemodemconnected
directlytoyourcomputerusingaserialcable,youcan
usePPP.
Ifyouareconnectinglocallywiththemodemconnected
directlytoyourcomputerusinganEthernetcable,you
canuseUDP,TCP,orEthernet.
c. Entertheconnectioninformation.
ForUDPorTCP,ifyouareconnectinglocally,usethe
*HOSTPEERIPofthemodemtoconnect.Thedefaultfor
the*HOSTPEERIPis192.168.13.31.
ForSMS,enterthephonenumberofthemodemand
selectyourwirelesscarrier.
ForPPP,selecttheCOMporttowhichthemodemis
connected.
d. Enterthepassword.Thedefaultpasswordwillbe
enteredforyou.
Rev 3.0B Feb.08
27
e. SelectOK.
Figure 5-3: AceManager : Connected
3. Enter the configuration options

a. OntheleftsideofAceManageristheGroupsmenu.
Selecttheappropriategroupasneededordirected.
b. EnteryourchangesintheNewValuecolumnbytyping
inthedesiredchangeorusingthedropdownmenus.
c.
ThecurrentconfigurationisshownintheValue
column.
Figure 5-4: AceManager : Changing values
Rev 3.0B Feb.08
28
4. Write the changes to the modem

a. ClicktheWritebuttononthetoolbarofAceManager.
b. WaitforthemessageWriteSuccessfultoappearin
thestatusbar.
Tip: Some configuration settings will require you to reset the modem
before they will take effect. You can reset the modem by using the
Reset button in AceManager or by using the reset button on the
modem. You can also reset the modem by cycling the power.
Using Templates
Ifyouhaveamodemconfigurationthatworkswellforyour
needs,usingAceManager,youcansavethatmodemsconfigu
rationasatemplateandthenapplyittootherSierraWireless
AirLinkmodems.
1. Creating the Template with

AceManager
a. Configurethemastermodem.
b. ClicktheCopybuttononthetoolbartotransferallthe
configuredsettingstotheNewValuecolumn.
Figure 5-6: AceManager : Copy
c.
Rev 3.0B Feb.08
Removesettingswhicharespecifictoyourmaster
modemorverifysettingsareapplicabletoallyour
modems.
29
Note: Some of the configuration settings are specific to individual

modems. You do not want to have those settings in your saved
template otherwise the modems you configure with the template could
cease to work with the cellular or local network.
CellularTechnologyspecificsettings(EDGE/HSDPA
group)
*MODEMNAME
*HOSTPRIVIP
*HOSTPEERIP
*HOSTUID
*HOSTPW
d. ClicktheSavebuttononthetoolbar.
e. Typeinafilenamethatisdescriptiveofthetemplate
(soyoucanfinditeasilylater)andsaveittoalocation
onyourcomputer.
Figure 5-7: AceManager : Save Template
Rev 3.0B Feb.08
30
2. Applying a Template to one modem

with AceManager
Youcanuseatemplateyoucreatedyourself,usingthesteps
above,oratemplateprovidedbyyourAirLinkrepresentative
orsomeoneinyourcompanywhohassetupamodem
template.Thetemplateyouwishtoapplymustbesavedto
yourharddrive.
a. Loadthetemplate.
1.
Connecttothemodemyouwanttoconfigure
usingAceManager.
2.
ClickontheLoadbuttononthetoolbar.
Figure 5-8: AceManager : Load
3.
Selectthetemplateyouhavesaved(youmayneed
tochangefoldersifyousavedittoadifferent
location).
b. Verifytheconfigurationsettings.
Tip: After you load the template, its best to go back over the
AceManager groups to make sure all the settings are what you
require.
c.
ClicktheWritebuttononthetoolbartowritethe
configurationtothemodem.WaitfortheWrite
Successfulmessage.
d. Resetthemodem.
Caution: Many of the configuration settings will not take effect until
the modem has been reset.
Rev 3.0B Feb.08
31
Tip: You can use common settings on one modem to configure those
same settings on another modem even of a different type. For
example, you can use the serial settings of a modem (such as
PinPoint X or Raven X) to configure the serial settings of a Raven XT.
Settings not applicable to the modem on which you are loading the
template, will be discarded.
3. Optional: Applying one template to

several modems simultaneously with
AceNet
AceNetallowsyoutoconnecttoandmonitorseveralmodems
atthesametime.Foryourconvenience,youcanalsoapplya
singletemplatetoselectedmodemssimultaneously.
ConnectingtothemodemswithAceNetiscoveredinthe
AceNetUserGuide.
Caution: When applying a template in AceNet, it is even more
important to make sure there are no non-general settings in the
template from the master modem.
UnlikeAceManger,AceNetdoesnotcheckthemodemtype
beforeapplyingthetemplate.Settingsnotapplicable,suchas
aUSBsettingfromaRavenXTtemplatebeingappliedtoa
RavenX,arenotreadbythereceivingmodem.Youwillgeta
partialsuccessstatusifallitemsinatemplatecannotbe
appliedbythereceivingmodem.
a. Selectmodemstoconfigurewiththetemplate.
Rev 3.0B Feb.08
32
Figure 5-10: AceNet : Selected modems
Tip: Click on the first with your mouse and, with the control button
held down, click the additional modem.
b. SelecttheModemoptioninthetoolbarandthenselect
ApplyAceManagerTemplate.
Figure 5-11: AceNet : Modem menu
c.
EithertypeintheTemplatefilename,orclickbrowse
andselectthetemplatefileyouwanttoapply(you
mayneedtochangefolders).
Figure 5-12: AceNet : Template select
d. SettheRetryIntervalandcheckifyouwanttohave
themodemsResetwhenthetemplatehasbeen
applied.
Rev 3.0B Feb.08
33
Using a Terminal Application

with AT Commands
YoucanaccessandconfigureyourRavenXTusingaterminal
applicationsuchasMicrosoftHyperTerminal,PuTTY,or
similar.ThefollowingdirectionsareforHyperTerminalwhich
ispartofastandardinstallationofWindowsXP.
Start>AllPrograms>Accessories>Communications>HyperTer
minal
Figure 5-13: HyperTerminal
1. Choose a name and icon for your

connection.
a. Chooseanameforyourconnection,suchasRavenXT
orSierraWirelessAirLinkSolutions.Thenameandicon
areonlyforyourownreferencesoyoucanfindthe
connectionatalaterdate.
Tip: If you want to have a connection saved for both local and
remote, it is recommended the connection name reflect the
connection type, i.e. Raven XT local.
b. SelectOK.
Rev 3.0B Feb.08
34
2. Connect To
a. SelectCOM1,orthecomporttowhichthemodemis
connected,fortheConnectUsing.
Figure 5-14: Connect To
b. Typein192.169.13.31forHostAddress.
c.
ChangethePortNumberto2332.
d. SelectOK.
3. Port Settings (serial only)

a. Changeorverifythesettings:
BitsperSecond:115200(default)
DataBits:8
Parity:None
StopBits:1
Rev 3.0B Feb.08
35
FlowControl:Hardware.
Figure 5-15: Port Settings
Tip: If you have configured the Raven XT for settings different than
the defaults for Bits per Second, Data Bits, Parity, and/or Stop Bits,
you will need to use your changed settings.
b. SelectOK.
4. Connected
Figure 5-16: HyperTerminal : connected
Rev 3.0B Feb.08
36
a. TypeATandpressEnter.Youshouldgetareplyof
OKor0.
b. Toseewhatyouaretypingasyoutypeit,youwill
needtoturnontheechoandverbosemode.Type
ATE1V1andpressEnter.
c.
IfyougetareplyofOK,thenyouenteredthe
commandsuccessfully.Ifyougetareplyof0or
ERROR,tryenteringthecommandagain.
AT Commands
Whenusingaterminalapplication,youwillneedtomanually
typeineachcommand.
Formostcommands,whenyouareenteringthemusinga
terminalconnection,youwillneedtoprefacethe
commandwithAT(exceptionsarenoted),i.e.ATAwhich
islistedasA.
Somecommandshavespecificparameterswhileother
commandswilltakewhateveryoutype.
Requiredvariableparametersaredenotedwithitalicized
text,example,Dn.Thenisvariable.
Acceptableparametersand/orspecificformatsarelisted
witheachcommand.
Mostcommandswithparameterscanbeenteredwith?to
readthecurrentvalue(forexample,AT&D?willrespond
with2ifthedefaulthasnotbeenchanged).
Optionalparametersaredenotedwithsquarebrackets[].
ATCommandsarenotcasesensitive.AcapitalEisthe
sameasalowercasee.
Whenyouareusingaterminalconnection,ifyouentera
commandwhichisrecognizedbytheRavenXT,itwill
respondwithOK.Ifthecommandisnotrecognized,the
responsewillbeERROR.
Thosecommandsapplicableonlytocertainmodel
numbersoftheRavenXTwillbenoted.
Caution: Symbols listed with commands, such as *, /, &, or ?, are

part of the command and must be included. Commands with symbols
other than * may require PassThru mode.
Rev 3.0B Feb.08
37
6: Universal Serial Bus (USB)

Changing the USB
port communication
Installing the USB
driver
Using the Virtual
Ethernet Port
Using the Virtual Serial
Port
TheRavenXTisequippedwithaUSBportwhichincreasesthe
methodsbywhichyoucansendandreceivedata.TheUSB
portcanbesettoworkaseitheranEthernetportoravirtual
serialport.AdriverinstallationisrequiredtousetheUSBport
ineithermode.
Note: It is recommended that you use a USB 2.0 cable with your
Raven XT and connect directly to your computer for best throughput.
Changing the USB port

communication
Thecommandtochangetheportconfigurationis
*USBDEVICEanditisintheUSBgroupofAceManager.
Figure 6-1: AceManager : USB
Bydefault,theportissettoworkasavirtualEthernetport
(*USBDEVICE=1).
TochangetheUSBporttoallowvirtualserialportcommuni
cation,disabletheEthernetportemulation,set*USBDEVICE
to0.
Note: If you use a terminal connection with the USB port to change
*USBDEVICE, the change is immediate. Your connection will be
terminated after inputting the command.
Rev 3.0B Feb.08
38
Universal Serial Bus (USB)
Installing the USB driver

1. Set the Port Type
VirtualEthernetportisthedefaultsettingfortheUSBport.If
youwanttoinstallthevirtualserialport,changetheUSBport
configurationusingthedirectionsabove.
2. Connect the Raven XT to your

computers USB port
WhenyouconnecttheRavenXTforthefirsttimetoaUSB
portonyourcomputer,Windowsshoulddetectanewdevice
andpromptyoutoinstallthedriver.
Note: Windows will see each port type as a different USB device and
will see every port on your computer separately. If you change the port
type on the Raven XT or connect to a different USB port on your
computer or hub, Windows will see it as a new device.
Figure 6-2: Found New Hardware Wizard
a. TostarttheinstalloftheUSBvirtualEthernetdriver,
selectNo,notthistimeandclickNext.
b. SelectInstallfromalistofspecificlocationandclick
Next.
Rev 3.0B Feb.08
39
Figure 6-3: Hardware Wizard : Location options
3. Install the driver from a specific

location
a. Selectand/orenterthelocationofthedriver.
IfthedriverisontheCDandtheCDisinyourdrive,
youcanjustselectSearchremovablemedia.
IfyouhaveinstalledAceManagerortheSetupWizard,
thedrivershavebeenconvenientlycopiedtoyourhard
drive.EnterC:\ProgramFiles\CommonFiles\AirLink
asthelocationtosearch.
Ifyouwillbeinstallingthedriverfromafile
downloadedfromtheSierraWirelesswebsite,select
Includethislocationinthesearchandtypeinthe
locationwhereyoudownloadedthefile.
b. ClickNext.
Figure 6-4: Hardware Wizard : Install location
Afteryouselectthelocation,theinstallationshouldbegin.If
yougetamessageaskingifyouwanttocontinuetheinstal
lation,clickContinueAnyway.
Figure 6-5: Hardware Wizard : Installing
Rev 3.0B Feb.08
40
c.
ClickFinishtocompletetheinstallation.Thedriver
shouldbeenabledwithoutanyneedtorebootyour
computer.
Figure 6-6: Hardware Wizard : Finish
4. Optional: Verify and Configure the

Virtual Port Settings
Virtual Ethernet
TheUSBEthernetconnectionwillshowupinyourNetwork
ConnectionsasaLocalAreaConnection.
Tip: If you also have an Ethernet card on the computer or have
installed the USB Ethernet to more than one USB port on your
computer, the USB Ethernet may show up with a number.
Figure 6-7: Network Connections
YoucanalsoverifytheinstallationbylookingintheDevice
Manager.
a. ClickonStart>ControlPanel.
b. DoubleclickontheSystemicon.
c.
Rev 3.0B Feb.08
SelecttheHardwaretabandclicktheDeviceManager
button.
41
Figure 6-8: System Properties
d. Clickonthe+infrontofNetworkAdapters.
Thenewlyinstalleddriver,AirLinkUSBEthernet/RNDIS,
shouldbedisplayed.Ifthedriverisdisplayedwitha#and
numberbehindthedrivername(suchas,AirLinkUSB
Ethernet/RNDIS#2),itmeansmorethanoneisinstalledon
yourcomputer,mostlikelyfordifferentUSBport.Morethan
onecopyofthedrivershouldnotcauseanyproblemssince
onlytheconnectedportanditsdriverwouldbeactive.
Figure 6-9: Device Manager - Ethernet
Rev 3.0B Feb.08
42
Virtual Serial
YoucanverifytheinstallationbylookingintheDevice
Manager.
a. ClickonStart>ControlPanel.
b. DoubleclickontheSystemicon.
c.
SelecttheHardwaretabandclicktheDeviceManager
button.
Figure 6-10: System Properties
d. Clickonthe+infrontofModems.
Thenewlyinstalleddriver,AirLinkUSBSerialPort,shouldbe
displayed.
Tip: If the driver is displayed with a # and number behind the driver
name (such as, AirLink USB Serial Port #2), it means more than one
is installed on your computer, most likely for different USB port. More
than one copy of the driver should not cause any problems since only
the connected port and its driver would be active.
Rev 3.0B Feb.08
43
Figure 6-11: Device Manager - Serial
ToconnecttothemodemusingtheUSBvirtualserial,most
applicationsorutilitieswillrequireyoutoselectorenterthe
serial(COM)portnumber.TheUSBconnectionwillappearas
astandardserialport,soyouwillneedtodetermineits
numbertoconnecttoit.Thedriverinstallationwillautomati
callyassignaportoryoucanchangeitifyouwishtoanother
unusedport.
a. FromtheDeviceManager,rightclickonthedriver
nameandselectProperties.
Figure 6-12: Device Manager : Driver menu
b. SelecttheAdvancedtabandclicktheAdvancedPort
Settingsbutton.
Rev 3.0B Feb.08
44
Figure 6-13: Driver Properties
c.
Atthebottomofthescreen,thecurrentportusedwill
belisted.Usethedropdownmenutoselectan
availableCOMportnumberifyouneedtochangeit.
Figure 6-14: Advanced Settings
Using the Virtual Ethernet Port

Oncethedriverisinstalled,youcanusetheUSBportjustlike
astandardEthernetport.
Using USB Ethernet with AceManager
InAceManager,usetheUDPorTCPconnectionandenterthe
IPaddressofthemodem(192.168.13.31bydefault)andthe
password(12345bydefault).
Rev 3.0B Feb.08
45
Figure 6-15: AceManager : TCP
Using USB Ethernet with a Terminal Emulation Utility

Configureyourterminalapplicationfortelnetcommunication.
a. InHyperTerminal,selectTCP/IP(Winsock)
b. UsetheIPaddressofthemodem(192.168.13.31by
default)asthedestinationandusethetelnetportof
themodem(2332bydefault).
Figure 6-16: HyperTerminal : TCP
c.
Enterthemodempassword(12345bydefault)when
requested.
Using the Virtual Serial Port

Oncethedriverisinstalled,youcanusetheUSBportjustlike
astandardserialport.
Using the USB virtual serial port with AceManager
InAceManager,theUSBvirtualserialportconnectionwill
appearasastandardserialport.UsethePPPconnectionand
selecttheCOM#serialportoftheUSBconnection.
Rev 3.0B Feb.08
46
Figure 6-17: AceManager : PPP
Tip: You will need to open AceManager after you connect the USB
cable to your computer for AceManager to have access to the USB
Serial PORT.
Using the USB virtual serial port with a Terminal

Emulation Utility
a. SelecttheserialportoftheUSBconnectionwhen
promptedforaCOMport.
b. ChangetheBitsperSecondto115200(default),Data
Bitsto8,ParitytoNone,StopBitsto1,andFlow
ControltoHardware.
c.
Rev 3.0B Feb.08
Youshouldalsoneedtomakesureyourconnection
usesAutoDetectfortheterminalemulation.
47
7: Data Communication and Host

Modes
Basic Modes
Serial Modes
Data Communication
TheRavenXTplaysthepartofaHOSTwhenacomputeror
anotherdeviceisconnecteddirectlytoitsportandroutesdata
to/fromtheconnecteddevicetothecellularnetwork.
Caution: The Raven XT moves data from one port to the cellular
network in a simple one-to-one routing. It does not employ a routing
table or any complicated routing protocol.
Tip: If you need to have one-to-many routing, you can connect the
Raven XT to a router. The router would provide the multiple routing
and the Raven XT would provide one-to-one for the router to the
cellular network and the Internet.
Asthehost,theRavenXTcanusedifferentcommunication
modes:
Basic Modes
AT:TheRavenXTacceptsandrespondstostandardAT
commands.
PassThru:Directconnectiontointernalhardware(OEM
Module)oftheRavenXT.
Telnet:TheRavenXTautoanswersTCPconnectionsto
allowterminalemulationusingeitheralocalUSBEthernet
connectionorremotelyusingthecellularconnection.
Tip: By default, the Raven XT is in AT Mode and allows AT

Commands to be entered via terminal connection (through the local
port connection) or remotely (through the cellular network). PassThru
Mode can only be exited by resetting the Raven XT. All serial modes
are entered by use of a startup mode command.
Serial Modes
Rev 3.0B Feb.08
PPPMode:TheRavenXTusesPPPtocommunicatewitha
deviceorcomputerconnectedtotheserialorUSBport.
SLIPMode:TheRavenXTusesSLIPtocommunicatewith
adeviceorcomputerconnectedtotheserialorUSBport.
48
Data Communication and Host Modes
UDPandUDPPAD:Anydatareceivedontheserialport
isassembledintoUDPpacketsandsenttothesessions
associatedIPaddressandPort(describedlater).Any
responsesreceivedfromtheassociatedIPaddressandport
destinedfortheDevicePortareunwrappedandsentout
theserialport.
TCPandTCPPAD:Anydatareceivedontheserialportis
packagedintoTCPmessagesandsenttotheassociated
connectionsIPaddressandPort(describedlater).Any
datareceivedfromtheTCPpeerisunwrappedandsent
outtheserial.
Data Communication
PublicandPrivateModes:ThemethodusedbytheRaven
XTtopassanIPaddresstoaconnecteddevice.
Keepalive:HowtheRavenXTmaintainsitsconnectionto
thecellularnetwork.
Basic Modes
Start up Mode
TheserialportoftheRavenXTcanbeconfiguredtoenterany
ofthemodesautomaticallyonpowerup(inmostcases,thisis
alsoafterithasregisteredonthecellularnetwork).Thisis
donebysettingtheStartupModeDefaulttothedesiredmode.
Ifthissettingisnonzero,themodemwillenterthespecified
modeafter5seconds.Ifyouwanttocancelthisbehavior,the
ATMD0commandcanbeusedbeforethe5secondtimeout
expires.
YoucanconfiguretheStartupModeinAceManageratpartof
theUDPgroup.
Figure 7-1: AceManager : UDP - MD
Rev 3.0B Feb.08
49
IftheserialportoftheRavenXTisinanymodeotherthanAT
orPassThru,theATcommandmodecanbereenteredby:
DeactivatingDTR(if&D2orIgnoreDTR,S211,isnotset).
Issuingthe+++escapesequence(ifDisableATEscape,
DAE,isnotset).
ResettingorPowercyclingthemodem.
Note: DTR needs to be asserted (S211=1 or &D0) by the host before

PPP Mode, SLIP Mode, UDP PAD Mode, or TCP PAD Mode can be
entered.
AT Mode
Usingaterminalconnection,ATcommandsareusedto
configurethemodem,commandittodosomething,orquerya
setting.ForafulllistingoftheATcommands,refertothe
appendix.AceManagerisagraphicaluserinterfaceformost
ATCommands.
ATcommandsmustalwaysbeterminatedby<CR>(ASCII
character0x0D),acarriagereturn(pressingenteronthe
keyboard).Somemayalsoincludeanewlineorlinefeed
<LF>.
IfE=1(EchoOn),theATcommand(includingthetermi
nating<carriagereturn)willbedisplayed(output)before
anyresponses.
TwosettingsaffecttheformatofATcommandoutput:V
(Verbose)andQ(Quiet).
IfQ=1(QuietOn),noresultcodesareoutputwhatsoever,
sothereisnoresponsegeneratedbya(nonquery)
command.
IfQ=0(QuietOff),resultcodesareoutput.Theformatof
thisoutputisthenaffectedbytheVerbosesetting.
IfQuietmodeisoff,theresultcodeisaffectedasfollows:
ForV=1(Verbosemode),thetextualresultcodeissur
roundedbyacarriagereturnandnewline.AnyAT
queryresponseisalsosurroundedbyacarriagereturn
andnewline.
ForV=0(Tersemode),anumericresultcodeisoutput
withasingletrailingcarriagereturn(nonewlineis
output),whileanyATqueryresponseisfollowedbya
carriagereturnandnewline(thereisnopreceding
output).
Rev 3.0B Feb.08
Forexample,possibleoutputtotheATcommandAT
withcarriagereturn(assumingquietmodeisnoton)is:
50
carriagereturnifV=0
carriagereturnandnewlineOKanothercarriage
returnandnewlineifV=1
Note: These commands work for the port on which they are executed.
For example, if the user types ATE1 and then AT&W using a serial
port connection, it will set the serial port to Echo On.
PassThru Mode
InPassThrumode,theRavenXTdoesnotbehavenormally,all
portcommunicationispasseddirectlybetweentheinternal
hardwareandthecomputerconnecteddirectlytothemodem.
Thismodecanbeusedtoconfigurehardwarespecificsettings.
Forexample,provisioning,troubleshooting,communicating
withlegacyequipment,etc.
Caution: ALEOS is disabled in PassThru Mode. You cannot use
most ALEOS specific commands while the modem is in PassThru
Mode. While in PassThru mode, you also cannot use AceManager to
connect with the PinPoint.
IssuingtheAT\APASSTHRUfromaterminalemulation
entersthismode.ThemodemrespondswithOK,atwhich
pointadirectconnectiontotheinternalhardwareisestab
lished.YoucanalsoconfigurethemodemtoenterPassThru
modeonstartupusingMD.
Tip: PassThru can only be exited by resetting or power-cycling the
modem. This mode cannot be entered via a remote Telnet session.
YoucanconfigureastringofATcommandstobesenttothe
RavenXTwhenitentersPassThruandotherPassThru
settings.
Figure 7-2: AceManager : PassThru
Rev 3.0B Feb.08
51
PassThruModeallowsonlyspecificATcommands.Some
ALEOScommandswillbeunavailablewhentheRavenXTis
inPassThrumode.Thecommandsusablealsodependheavily
onthemodemmodelnumber(foundonthelabelonthetopof
theRavenXT).
Note: Some internal hardware requires upwards of 20 seconds
before AT commands can be entered, so be patient if there seems to
be no response to AT commands.
Telnet Mode
InAceManageryoucanconfigureTelnetoperation.
Figure 7-3: AceManager : S0
IfyouneedtochangetheportforTelnet(forexample,you
havethedefaultportblockedonyourfirewall),theoptionis
ontheOthertab.Thedefaulttelnetportis2332.Youcanalso
changetheTelnettimeout,iftheconnectionisidle,default2
minutes.
Figure 7-4: AceManager : Other - *TPORT, *TELNETTIMEOUT.
Serial Modes
PPP
InPPPmode,theRavenXTactsasaPPPserver,providingan
IPaddress,andDNSservers(ifavailable)totheconnected
deviceorcomputer.
Rev 3.0B Feb.08
52
PPPmodeisenteredfromtheATmodebyusinganyofthe
followingcommands:
AT\APPP
ATDT10.0.0.1
ATDT10001
ATD#19788or#777*99***1#
CLIENT
Inresponsetoanyoftheprecedingcommands,theRavenXT
willrespondwithCONNECTacarriagereturnandnewline
andisreadyforthehosttobeginPPPnegotiations.TheIP
receivedbythehostintheresultingnegotiationwilleitherbea
private(nonroutable)IPaddressorapublic(network
routable)IPaddressprovidedbythenetwork,dependingon
thesettingsof*HOSTPRIVMODE.If*HOSTPRIVMODE=1,
thevalueoftheprivateIPaddresscanbedetermined
beforehandbyqueryingS110.TheprivateIPaddresstobe
usedcanbedefinedwiththecommand
AT*HOSTPRIVIP=192.168.100.33,substitutingthedesiredIP
address.
Figure 7-5: AceManager : PPP/Ethernet
UsingaprivateIPinsulatesthePPPclientfromchangesinIP
addressesoftheunderlyingnetwork.Thewillperformbasic
NATlikeaddresstranslationonallpackets.
IfapublicIPaddressisbeingused,anychangesintheIP(as
determinedbythewirelessnetwork)willresultinthePPPlink
tothehostbeingdisconnected,requiringthehosttoreinitiate
it.ThepublicIPispassedtothehostinthePPPnegotiations,
sowhenthenetworkforcesachange,themodemhastoforce
thehosttorenegotiatethePPPlinktomakethishappen.
Rev 3.0B Feb.08
53
SLIP
SLIPmodeisenteredbeusingtheAT\ASLIPcommand.As
inPPPMode,theIPaddressthatthehostassumesisaffected
bythesettingof*HOSTPRIVMODE.SLIPdoesnotnegotiate
theIPaddresswiththeconnecteddeviceorcomputer,so
beforemakingaSLIPconnection,theSLIPdriveronthat
deviceorcomputermustbeconfiguredtousetheIPaddress
specifiedbyqueryingS110.
UDP and UDP Pad

WhenthemodemisinUDPPAD(PacketAssemblyandDisas
sembly)Mode,allcharactersreceivedontheserialportare
assembledintoUDPpacketsandsenttotheremoteIP
address/portortheRavenXT,andanypacketsreceivedfrom
thesameIP/portdestinedforthedeviceportofRavenXT(see
*DPORT)aredisassembledanddumpedontotheserialline.
AUDPsessionisinitiatedbyoneofthefollowingevents:
UsingtheDialUDP(DP)ATcommand(example,
ATDP192.168.3.23/3456).
SettingtheStartupModeDefault(MD)to3(UDP)sothat
aUDPsessionisenteredautomaticallywhenthemodem
registersontothenetwork.Serialdatawillbesenttothe
IP/portspecifiedinS53.
IncomingUDPpacketswillbeprocessedouttheserialportif
UDPautoanswerisenabled(S82=2);
ThedestinationIPaddressmatchesthatinS53(ifFriends
Modeisenabled,theIPaddressalsoneedstobepresent
ontheFriendsList);
OrallowanyIPisset(AIP=1);
ThemodemisinATmode(notinacurrentUDPorTCP
session).
UDPpacketassemblyisaffectedbythevaluesofS50(PAD
ForwardingTimeout)andS51(PADForwardingCharacter).
Datareceivedintheserialbufferwillbetransmittedwhenthe
idleintercharactertimeoutspecifiedinS50(intenthsof
seconds)occursorwhenacharacterisreceivedthatmatches
S51(ifnonzero).
UDP Auto Answer
UDPautoanswer(previouslycalledUDPhalfopen)isset
withS82=2.Whenset,theRavenXTwillautomatically
establishaUDPsessiontothesourceIPaddressandportof
theUDPpacketreceived.TheRavenXTwillremainlocked
Rev 3.0B Feb.08
54
tothisoneremoteIP/portuntilnodataissentorreceivedfor
thetimeintervaldefinedintheUDPautoanswertimeout
(S83).Duringthissession,packetsfromotherIP/port
addresseswillberejected,unless*UALLisset.Whetherornot
anincomingpacketwillcausethemodemtoenteraUDP
sessionisalwaysdependentontheS53andAIPsettings.
TheNormalUDPMode(MD3)canbecombinedwithUDP
autoanswertocausetheincomingserialdatatobesentin
UDPpackets(insteadofbeingtreatedasATcommands),while
allowingsessionstobeestablishedfromdifferentUDP
sources.AUDPsessionwillbeinitiatedeitherbyincoming
serialdataorbyanincomingUDPpacket.Thesession,started
byeithermethod,willbeterminatedwhennodatahasbeen
sentorreceivedfortheS82period.Oncethesessiontermi
nates,anothermaybeinitiatedbyeithermeans.
Whenidle,afterthetimeouthasoccurred,themodemisinAT
commandmodeontheserialport,andanyvalidATcommand
maybeenteredduringthistime.
Tip: It is best to ensure the idle time-outs for TCP and UDP are never
0 if you're going to be using auto-answer, or either PAD mode. In
those circumstances, you will want the modem to close the socket if
the connection goes idle for too long, particularly if the other side
doesnt normally close the connection.
Whenthesessionisinitiatedbyserialdata,thenewsession
willbeestablishedusingthedestinationaddressspecifiedin
S53.TheS53settingcanbechangediftheconnecttolastUDP
setting(*UDPLAST=1)isset.TheaddressinS53willbe
updatedtoreflecttheaddressofthelastsessioninitiatedbyan
incomingUDPpacket.Sothatwhennewdataisreceivedover
thehostserialportwhileintheidlestate,asessionwillbere
establishedwiththelastaddress.(Thisbehavioristhesameas
thepreviousHybrid2(MD6)mode).
Tip: TCP auto answer (S0) may also be set simultaneously with UDP
auto answer. Then, when in the idle state, the modem will accept
either a TCP or UDP incoming packet, and enter a TCP or UDP
session as appropriate.
Reliable UDP
ReliableUDPaddsasimpleprotocolontopofUDPtoprovide
reliabledeliveryofdata.Whendataisreceivedfromthehost
serialport,a2byteheaderisaddedtothedata,containinga
messagetypeandasequencenumber.TheRavenXTwill
continuetosendthisdata(bufferinganyreceiveddatainthe
Rev 3.0B Feb.08
55
meantime)untilitreceivesanacknowledgementwiththis
sequencenumber.Ifanacknowledgementisnotreceived
withinthetimeoutperiod(specifiedinS7),thedatawillbe
retransmitted.Thiswillcontinueuntilanacknowledgementis
receivedorthemodemisreset.LikewiseanyUDPpackets
receivedbytheRavenXTareexpectedtohavethissimple
header.TheRavenXTwillissueanacknowledgementforany
validpacketswhicharereceived.
ToconfiguretheRavenXTforanormalUDPsession,youneed
tosettheStartupModeDefaultto73(ATMD73).Ifyouare
usingtwomodems,configuretheDestinationIPandPortin
eachtopointtoeachother.Serialdatawillthenbesentreliably
betweenthetwo.
Caution: Although it adds reliability, the simple implementation of the
Reliable UDP mode in the does not check for duplicate packets.
UDP Multicast Mode

UDPMulticastmoderesultsinanydatareceivedfromthehost
serialportbeingsenttoalltheclientsintheaddresslist.The
remoteportnumberistakenfromS53.Toavoidfloodingthe
network,thepacketsaresenttoeachclientwitha20mspause
inbetween.ThereceiptofUDPpacketsworksasinnormal
UDPmode(i.e.boundbythevalueS53and/orAIP).Sinceit
maytakeawhiletotransmitthedatatoallhosts(especiallyif
all20Modbusentriesareusedandnameresolutionsare
required),newdatareceivedfromthehostportisbuffered
untilcurrenttransmissionstoallhostsarefinished.
EnterthelistoftargetIPsintheaddresslist(ADDRLIST).The
indexnumbersinthelistarentused.Configureforanormal
UDPsession.SettheStartupModeDefaultto83(ATMD83).
ConfiguretheDestinationporttomatchthedeviceportofthe
remotemodems.
TCP and TCP Pad

WhentheRavenXTisinaTCPsession,allcharactersreceived
ontheserialportareassembledintoTCPpacketsandsentto
themodesremoteIPaddress/port,andanypacketsreceived
fromtheremoteendoftheTCPconnectionaredisassembled
anddumpedontotheserialline.
ATCPconnectionisestablishedbyoneofthefollowing
methods:
Rev 3.0B Feb.08
UsingtheDialTCP(DT)ATcommand.Forexample,
ATDT192.168.3.23/3456.
56
TCPautoanswerisenabled(S1),aTCPconnectionrequest
isreceived,andthemodemisnotinadatasession.
Dataisreceivedontheserialportand
TheStartupModeDefault(MD)is4(autoTCP)
TheremoteTCPdestination,asdefinedinS53,success
fullyrespondstotheTCPconnectionrequest.
ThevalueofS7(TCPConnectionTimeout)specifiesthe
numberofsecondstowait,afterinitiatingaTCPconnection
attempt,forasuccessfulconnectiontobeestablished.Ifthe
connectionhasnotbeensuccessfullyestablishedbeforethe
timeoutoccurs,ERROR/BUSYisreturned.
TCPpacketassemblyisaffectedbythevaluesofS50(PAD
ForwardingTimeout)andS51(PADForwardingCharacter).
Datareceivedintheserialbufferwillbetransmittedwhenthe
idleintercharactertimeoutspecifiedinS50(intenthsof
seconds)occursorwhenacharacterisreceivedthatmatches
S51(ifnonzero).
TheTCPsessionwillbeterminatedifnodataistransmittedor
receivedforthetimeintervalspecifiedinTCPTandTCPS.
TCPTisthenumberofminutes(TCPS=0)orseconds(TCPS=1)
usedforthisidletimeout.
Caution: TCPT should never be 0 when using the TCP mode. A
broken TCP session can result in the modem being left with a TCP
half-open connection that can only be terminated with a reset.
TCP Auto Answer

TCPautoanswer(S0=1|2)alsoallowsaTCPconnection
requesttobeansweredwhenthemodemisidle,notina
datasession.TheTCPconnectionrequestsdestinationport
hastomatchthemodemsdeviceport.
Note: UDP auto answer may also be set simultaneously with TCP
auto answer. Then, when in the idle state, the modem will accept
either a TCP connection request or UDP incoming packet, and enter a
TCP or UDP session as appropriate.
Hybrid Modes
Hybridmodesaresupportedmainlyforlegacyimplementa
tions.Someprevioushybridmodes(MD=5,6)arenolonger
implementedasspecial,uniquemodes.NowthatUDPauto
answer(UDPHalfopen,S82=2)canbeenabledinconjunction
Rev 3.0B Feb.08
57
withUDPPADmode(MD3),effectivelythisisthesameas
MD5andMD6previouslyaccomplished.SettingMD5and
MD6arestillsupported,butnotrecommended.
AT Command
Rev 3.0B Feb.08
Hybrid Mod
(MD5)
Hybrid Mode2
(MD6)
MD
S82
S0
*UDPLAST
58
Data Communication
Note: The Raven XT forwards
messages to and from the
cellular network for only ONE
device per port. The Raven XT is
a one-to-one gateway and does
not have advanced routing
features required to do one-tomany routing.
TheprimarypurposeoftheRavenXTistoforwarddatafrom
asingledeviceconnectedtooneoftheportstothecellular
networkand,ultimately,undermostcircumstances,tothe
Internetinaonetoonegatewayconfiguration.
WhentheRavenXTobtainsitsIPaddressfromyourcellular
provider,italsoobtainsthenetworkroutinginformation
necessarytoforwardmessagestotheirrouterswhichcanthen
forwardonfromthere.TheRavenXTthenactsasarouterfor
thedeviceconnectedtoit,forwardingtoorfromthecellular
network.
Note: If you have a device connected to he serial port and the USB
port, they will not be able to communicate to each other. Each port is
routed separately to the cellular network with one-to-one routing for
each.
Public and Private Mode

InPublicMode,theRavenXTwillpasstheIPaddress
assignedbythecellularnetworktothedeviceconnectedtoits
port.PublicModeisthedefaultmodefortheRavenXT.
Ifyouneedmorecontroloverwhichgatewayaddress,device
address,andnetmaskthatisgivenoutbytheinternalDHCP
server,youcanusetheprivatehostmode,*HOSTPRIVMODE,
andsettheinternalnetworkIPaddresses.TheRavenXTwill
useNATtoforwardpacketstotheenddevice.
Tip: When using Public mode, Sierra Wireless recommends
connecting the modem directly to the computer or other end device.
Using a hub or switch may prevent the Raven XT from updating the IP
address of the end device when an IP address is received from the
cellular network.
InAceManager,thePrivatemodesettingsarepartofthePPP/
Ethernetgroup.
Rev 3.0B Feb.08
59
*HOSTPRIVMODESetto1toenabletheexplicitIP
addresses.
*HOSTPRIVIPSettotheIPaddressyouwanttheRaven
XTtogivetoyourdevice.
*HOSTPEERIPSettotheIPaddressyouwantforthe
RavenXT.
*HOSTNETMASKSettothesubnetmask,generally
255.255.255.0.
Tip: If you are using Private Mode (*HOSTPRIVMODE=1), you will

need to make sure that *HOSTPRIVIP and *HOSTPEERIP are on the
same subnet. If the subnet mask is 255.255.255.0, it is safe to use
192.168.x.y for each as long as the x is the same number (0 in the
example screen shot above) and the y is different (1 and 2 in the
example) and between 0 and 254.
Note: Regardless if the Raven XT is configured for Public Mode or

Private Mode, the same IP address will be given to all devices
connected to any of the ports. While you can connect with each to the
cellular network and the Internet, you cannot use the Raven XT as a
hub or router to communicate between them.
Internal DHCP Server

DHCP(DynamicHostConfigurationProtocol)hasbecomea
primarycomponentoftodaysnetworkenvironments.DHCP
allowsoneservertoautomaticallyanddynamicallyallocate
networkIPaddressesandothernetworkrelatedsettings(such
Rev 3.0B Feb.08
60
assubnetmasks,routers,etc.)toeachcomputerordevice
withouttheneedtosetupeachspecificallyorkeeptrackof
whataddresseshavealreadybeenused.
Inadefaultconfiguration,theRavenXTactsasaDHCPhost
toanydeviceconnectedtoitsports,providingthatdevicewith
anIPaddresswhichcanbeusedtocommunicateonthe
Internet.InPublicMode,thatwillbetheIPaddressassigned
bythecellularnetwork.InPrivateMode,thatwillbetheIP
addressdefinedin*HOSTPRIVIP.
1.
WhentheRavenXTregistersonthecellularnetwork,itis
assignedanIPaddressfromyourcellularprovider,lets
sayA.B.C.D.
2.
ActingasaDHCPserver,inPublicMode,whentheRaven
XTreceivesaDHCPrequestfromanEthernetdevice
connectedviaUSB,ithandsofftheassignedaddresstothe
deviceandsetsupthedefaultgatewayaddressasA.B.C.1.
Ifthefourthoctetisalreadya1,itassignsA.B.C.2asthe
routeraddress.
3.
TheRavenXTalsosendsa/24netmask(255.255.255.0by
default)andsetsupastaticroutewhichmaps
192.168.13.31(ortheaddressconfiguredwith
*HOSTPEERIPifitischanged)toA.B.C.1(orA.B.C.2if
thatwaswhatthegatewayaddresswasgivenas).
Tip: When PPPoE is used with the Raven XT, DHCP is not needed.
A tunnel is set up connecting a device (such as your computer or a
router) with the modem. The device will then simply use the MAC
address of the Raven XT to send all outgoing packets.
Keepalive
Keepaliveisusedtotesttheconnectiontothecellularnetwork
bypinginganIPaddressafteraspecifiedperiodofinactivity.
Keepaliveisonlyrecommendedforuserswhohavearemote
terminatedmodemthatinfrequentlycommunicatestothe
networkorifyouhaveexperiencedissuesovertimewherethe
modemcannolongerbereachedremotely.
WhenKeepalivepingstheIPaddress,anacknowledgement
indicatesthereisanactiveconnectiontothenetwork.Ifthe
RavenXTdoesnotreceivearesponsefromtheIPaddress,it
willmakeadditionalattemptsaccordingtoabackoffalgorithm
beforedeterminingtheInternetconnectionisnotfunctioning
properly.Ifitdeterminestheconnectionisnotfunctioning,the
modemwillthenattempttoreconnecttoyourcellular
providertoreestablishIPconnectivity.
Rev 3.0B Feb.08
61
Configuring Keepalive
InAceManager,theKeepalivesettingsarepartoftheOther
group.
Figure 7-7: AceManager : Other
*IPPINGsetstheinterval,inminutes,youwantKeepalive
totestthenetworkconnection.TodisableKeepalive,set
*IPPINGto0(defaultsetting).
Note: minutes is the minimum time which can be set for Keepalive. If
you set *IPPING for a value less than the minimum, the minimum
value will be set.
*IPPINGADDRsetstheIPaddressyouwanttouseforthe
connectiontest.
Caution: If *IPPINGADDR is left blank or is set to an invalid IP

address (example, an IP which is unreachable or one which is not a
valid IP address), modem performance will be adversely affected.
Data usage using Keepalive

Keepaliveisanoptionalfeature.Ifyoufrequentlypassdata
withyourmodem,youmostlikelydonotneedtohave
Keepaliveenabled.WhenusingKeepalive,beawarethata
pingmovesapproximately66bytesofdataoverthenetwork
andisbillablebyyourcellularprovider.Thefollowing
*IPPINGsettingswillincurapproximatemonthlydatausage
inadditiontoanyotherdatausage:
Rev 3.0B Feb.08
62
8: IP Manager
Understanding Domain
Names
Using IP Manager with
your Raven XT
Understanding DNS
IfyouhaveafleetofSierraWirelessAirLinkmodemsoreven
ifyouonlyhaveone,itcanbedifficulttokeeptrackofthe
currentIPaddresses,especiallyiftheaddressesarentstatic
butchangeeverytimethemodemsconnecttoProvider.Ifyou
needtoconnecttoamodem,orthedevicebehindit,itisso
mucheasierwhenyouhaveadomainname
(car54.mydomain.com,whereareyou?).
Reasons to contact the modem and/or the connected
device:
Requestingalocationupdatefromadeliverytruck.
Contactingasurveillancecameratodownloadlogsor
surveyaspecificarea.
Anoilderekthatneedstobetriggeredtobeginpumping.
Sendingtexttobedisplayedbyaroadsign.
Updatingthesongstobeplayedonajukebox.
Updatingadvertisementstobedisplayedinacab.
Remoteaccesstoacomputer,aPLC,anRTU,orother
system.
Monitoringandtroubleshootingthestatusofthemodem
itselfwithoutneedingtobringitinorgoouttoit.
AdynamicIPaddressissuitableformanyInternetactivities
suchaswebbrowsing,lookingupdataonanothercomputer
system,dataonlybeingsentout,ordataonlybeingreceived
afteraninitialrequest(alsocalledMobileOriginated).
However,ifyouneedtocontactRavenXTdirectly,adevice
connectedtothemodem,orahostsystemusingyourRaven
XT(alsocalledMobileTerminated),adynamicIPwontgive
youareliableaddresstocontact(sinceitmayhavechanged
sincethelasttimeitwasassigned).
DomainnamesareoftenonlyconnectedtostaticIPaddresses
becauseofthewaymostdomainname(DNS)serversareset
up.DynamicDNSserversrequirenotificationofIPAddress
changessotheycanupdatetheirDNSrecordsandlinka
dynamicIPaddresstothecorrectname.
Rev 3.0B Feb.08
63
IP Manager
DynamicIPaddressesaregrantedonlywhenyourRaven
XTisconnectedandcanchangeeachtimethemodem
reconnectstothenetwork.
StaticIPaddressesaregrantedthesameaddressevery
timeyourRavenXTisconnectedandarenotinusewhen
yourmodemisnotconnected.
Sincemanycellularproviders,likewirebasedISPs,donot
offerstaticIPaddressesorstaticaddressaccountscosta
premiumvs.dynamicaccounts,SierraWirelessAirLink
SolutionsdevelopedIPManagertoworkwithaDynamicDNS
servertoreceivenotificationfromSierraWirelessAirLink
modemstotranslatethemodemsdynamicIPaddresstoa
fullyqualifieddomainname.Thus,youcancontactyour
RavenXTdirectlyfromtheInternetusingadomainname.
Understanding Domain Names

AdomainnameisanameofaserverordeviceontheInternet
whichisassociatedwithanIPaddress.Similartohowthe
streetaddressofyourhouseisonewaytocontactyouand
yourphonenumberisanother,boththeIPaddressandthe
domainnamecanbeusedtocontactaserverordeviceonthe
Internet.Whilecontactingyouatyourhouseaddressorwith
yourphonenumberemploydifferentmethods,usinga
domainnameinsteadoftheIPaddressactuallyusesthesame
method,justawordbasednameiscommonlyeasierto
rememberformostpeoplethanastringofnumbers.
Understandingthepartsofadomainnamecanhelptounder
standhowIPManagerworksandwhatyouneedtobeableto
configurethemodem.Afullyqualifieddomainname(FQDN)
generallyhasseveralparts.
Rev 3.0B Feb.08
TopLevelDomain(TLD):TheTLDistheendingsuffixfor
adomainname(.com,.net,.org,etc.)
CountryCodeTopLevelDomain(ccTLD):Thissuffixis
oftenusedaftertheTLDformostcountriesexcepttheUS
(.ca,.uk,.au,etc.)
Domainname:ThisisthenameregisteredwithICANN
(InternetCorporationforAssignedNamesandNumbers)
ortheregistryforathecountryoftheccTLD(i.e.ifa
domainispartofthe.caTLD,itwouldberegisteredwith
theCanadiandomainregistry).Itisnecessarytohavea
nameregisteredbeforeitcanbeused.
Subdomainorservername:Adomainnamecanhave
manysubdomainorservernamesassociatedwithit.Sub
domainsneedtoberegisteredwiththedomain,butdonot
64
IP Manager
needtoberegisteredwithICANNoranyotherregistry.It
istheresponsibilityofadomaintokeeptrackofitsown
subs.
car54.mydomain.com
.comistheTLD
mydomainisthedomain(usuallynotedasmydomain.com
sincethedomainisspecifictotheTLD)
car54isthesubdomainorservernameassociatedwiththe
device,computer,ormodemregisteredwith
mydomain.com
car54.mydomain.com.ca
Thiswouldbethesameasabove,butwiththeadditionofthe
countrycode.Inthisexample,thecountrycode(.ca)isfor
Canada.
Tip: A URL (Universal Resource Locator) is different from a domain
name in that it also indicates information on the protocol used by a
web browser to contact that address, such as http://
www.sierrawireless.com. www.sierrawireless.com is a fully qualified
domain name, but the http://, the protocol identifier, is what makes the
whole thing a URL.
Dynamic Names
WhenanIPaddressisnotexpectedtochange,theDNSserver
canindicatetoallqueriesthattheaddresscanbecachedand
notlookedupforalongperiodoftime.DynamicDNSservers,
conversely,haveashortcachingperiodforthedomaininfor
mationtopreventotherInternetsitesorqueriesfromusingthe
oldinformation.SincetheIPaddressofamodemwitha
dynamicaccountcanchangefrequently,iftheoldinformation
wasused(suchaswithaDNSserverwhichindicatesthe
addresscanbecachedforalongperiodoftime)whentheIP
addresschanged,thedomainwouldnolongerpointtothe
newandcorrectIPaddressofthemodem.
IfyourRavenXTisconfiguredforDynamicIP,whenitfirst
connectstotheInternet,itsendsaIPchangenotificationtoIP
Manager.IPMangerwillacknowledgethechangeandupdate
theDynamicDNSserver.ThenewIPaddresswillthenbethe
addressforyourmodemsconfiguredname.
OnceyourmodemsIPaddresshasbeenupdatedinIP
Manager,itcanbecontactedvianame.IftheIPaddressis
needed,youcanusethedomainnametodeterminetheIP
address.
Rev 3.0B Feb.08
65
IP Manager
Note: The fully qualified domain name of your Raven XT will be a

subdomain of the domain used by the IP Manager server.
Using IP Manager with your

Raven XT
ToallowyourSierraWirelessAirLinkmodemtobeaddressed
byname,themodemneedstohaveaminimumofthree
elementsconfigured.Youcanalsoconfigureaseconddynamic
serverasabackup,secondary,oralternateserver.
InAceManager,selectDynamicIP.
Figure 8-1: AceManager: Dynamic IP
*MODEMNAME:Thenameyouwantforthemodem.
Therearesomerestrictionslistedbelowforthemodem
name.
*DOMAIN:Thedomainnametobeusedbythemodem.
Thisisthedomainnameoftheserverconfiguredfor
*IPMANAGER1.
*IPMANAGER1:TheIPaddressordomainnameofthe
dynamicDNSserverwhichisrunningIPManager.
*IPMANAGER2:Thesecondaryserverforthedomain.
Whileitisoptionaltohavetwoserversconfigured,itis
highlyrecommended.
Tip: You can use a domain name instead of the IP address for your
IP Manager servers if you have DNS set up in your Raven XT.
Rev 3.0B Feb.08
*IPMGRUPDATE1and*IPMGRUPDATE2:Howoften,
inminutes,youwanttheaddresssenttoIPManager.If
thisissettozero,themodemwillonlysendanupdateif
66
IP Manager
theIPaddresschanges(example,ifyourRavenXTisreset
orisassignedadifferentIPaddress).
*IPMGRKEY1and*IPMGRKEY2:Userdefinedpassword
keywhichisusedinsteadofAirLinksecretkeywhen
usinganIPManagerserverotherthantheoneprovided
bySierraWireless.
Restrictions for Modem Name

FortheModemName,youshouldusesomethingwhichis
uniquebutalsoeasytoremember.Yourcompanynameorthe
intendedfunctionofthemodemarerecommended.Ifyou
havemorethanonemodemandwanttonamethemthesame,
youcanappendanumberforeach.SinceitisanInternet
domainname,therearesomerestrictionsforthename.
Mustbeginwithaletterornumber
Canincludeahyphen()
Cannotcontainspaces
Mustbenolongerthan20characterstotal
Data Usage for IP Manager Server

Updates
TheIPManagerupdateisasmallpacketsenttotheserver
witharesponsesentbacktothemodem.Ifyouhave
*IPMGRUPDATE1or*IPMGRUPDATE2settoanynumber
butzero,themodemwillsendtheupdatenotonlywhenit
receivesanewIPaddressbutatthetimeintervalaswell.The
datatrafficcouldbebilledbyyourcarrier.
Eachupdateisatotalof68bytesfromthemodemwitha50
bytetotalresponsefromtheserverforaroundtripupdateof
118bytes.
interval
(minutes)
total bytes per

day (24 hours)
10
16992 bytes
30
5664 bytes
60
2832 bytes
500
339.84 bytes
Eairlink.com
Asaservice,SierraWirelessmaintainsaIPManagerservers
whichcanbeusedforanyAirLinkmodem.
Rev 3.0B Feb.08
67
IP Manager
Note: The IP Manager service

from Sierra Wireless is currently
not a guaranteed service though
every effort is made to keep it
operational 24/7.
*DOMAIN:eairlink.com
*IPMANAGER1:edns2.eairlink.com
*IPMANAGER2:eairlink.com
Tip: When using the IP Manager service offered by Sierra Wireless,

since there are many modems using the service, it is even more
imperative to have a unique name for your modem.
Understanding DNS
TheRavenXThastheabilitytoqueryDNSserversinorderto
translatedomainnamesintoIPaddresses.Thisallowsyouto
usedomainnamesinplaceofIPaddressesformostofthe
configurationoptionsrequiringIPaddresses.Thisisimportant
ifyourRavenXTwillneedtocontactanothermodemorother
devicethathasadomainnamebutanunknownordynamicIP
address(suchasanotherremoteRavenXTusingIPManager).
Configuring DNS
Generally,whenyourRavenXTreceivesitsIPaddressfrom
Provideraspartoftheconnectionprocess,itwillalsoreceive
theDNSserverstouseforresolving(ortranslating)namesto
IPaddresseswhichitwillautomaticallyconfigureinthe
modemsettings.UnlessyourRavenXTwillbeusedona
networkwithothermodemsordeviceswhichhavenames
internaltothelocalnetworkorfrequentlychangingIP
addresses,theDNSserversprovidedbyProvidershouldbeall
youneed.
IftheRavenXTwillbecommunicatingwithadevicethathasa
domainnamebutchangesitsIPaddressfrequently(suchas
anotherAirLinkmodemusingIPManager)orisonanetwork
wheredevicesareaccessedbynamesratherthanIPaddresses,
youwillwanttoputinanalternateDNS(*DNSUSER)where
thatdomainisupdated,suchastheIPManagerserverthe
remotemodemisusingorthelistingofIPaddressestonames
iskept.
IfyouneedtomanuallyconfigureDNS,inAceManager,select
DNS.
Rev 3.0B Feb.08
68
IP Manager
Figure 8-2: AceManager: DNS
*DNS1and*DNS2TheprimaryandsecondaryDNS
serverssetbyProviderwhenyourRavenXTgetsitsIP
address.
*DNSUSERSetthis,ifdesired,toanadditionalDNS
servertoqueryfirstbeforetheprimaryorsecondary(just
asahostsfileisqueriedfirstonacomputer).If*DNSUSER
issetto0.0.0.0,itwillbeignored.
*DNSUPDATEThiscommandsetshowoftenyouwant
DNSUpdatestoberequested.OtherwisetheRavenXT
willonlysendupdateswhenitisreset,poweredup,orthe
IPaddressisgrantedbynetworkchanges.
The PPP-Peer Domain Name

TheRavenXTusestheunqualifieddomainnameofppp
peerwhenitisinPPPorSLIPaddressmodetoresolvethe
addressofthedeviceorcomputerconnectedviaPPPorSLIP
address.IftheRavenXTisnotinPPPorSLIPaddressmode,
ppppeerwillresolveto0.0.0.0.
Rev 3.0B Feb.08
69
9: Configuring Modbus/BSAP
Configuring the Raven
XT at the Polling
Host for Modbus on
UDP
Configuring the
Remote Raven XTs
for Modbus with UDP
TheRavenXTsupportsModbusASCII,ModbusRTU,BSAP,
andcanalsoemulateotherprotocolslikeDF1orothersusing
itsModbusVariablefeature.
Modbus Overview
TheModbusProtocol,developedbyModiconin1979,
providesforclientserver(alsoreferredtoasmasterslave)
communicationsbetweenintelligentdevices.Asadefacto
standard,itisthemostwidelyusednetworkprotocolinthe
industrialmanufacturingenvironmenttotransferdiscrete/
analogI/Oandregisterdatabetweencontroldevices.Modbus,
BSAP,andotherModbusvariationsareoftenusedin
conjunctionwithtelemetrydevices.
Tip: This section is just a brief overview of Modbus. For more information, refer to your Modbus equipment distributor or manufacturer or
http://www.modbus.org.
Telemetry
Telemetryisanautomatedcommunicationsprocessbywhich
dataiscollectedfrominstrumentslocatedatremoteorinacces
siblepointsandtransmittedtoreceivingequipmentfor
measurement,monitoring,display,andrecording.Trans
missionoftheinformationmaybeoverphysicalpairsofwires,
telecommunicationcircuits,radiosorsatellite.
Remote Terminal Unit (RTU)
Modbuswasoriginallydesignedtobeusedinaradio
environmentwherepacketsarebroadcastfromacentral
station(alsocalledmasterorhost)toagroupofremoteunits.
Eachremoteunit,RemoteTerminalUnit(RTU),hasa
hexidecimalidentificationnumber(ID).Thefirstpartofthe
broadcastpacketcontainsanRTUIDwhichcorrespondstothe
IDofoneoftheremoteunits.TheModbushostlooksforthe
IDandsendstoonlytheunitwiththematchingID.TheRTU
wouldthenreplybacktothecentralstation.
Rev 3.0B Feb.08
70
Raven XT GPRS/EDGE
TheRTUconnectstophysicalequipmentsuchasswitches,
pumps,andotherdevicesandmonitorsandcontrolsthese
devices.TheRTUcanbepartofanetworksetupforSuper
visoryControlandDataAcquisition.
Supervisory Control and Data Acquisition (SCADA)
SupervisoryControlandDataAcquisition(SCADA)describes
solutionsacrossalargevarietyofindustriesandisusedin
industrialandengineeringapplicationstomonitorandcontrol
distributedsystemsfromamasterlocation.SCADAencom
passesmultipleRTUs,acentralcontrolroomwithahost
computer(ornetwork),andsomesortofcommunicationinfra
structure.
SCADAallowsforsupervisorycontrolofremotedevicesas
wellasacquiringdatafromtheremotelocations.Program
mableLogicControllersallowforahigherdegreeof
automatedSCADA.
Programmable Logic Controller (PLC)
AProgrammableLogicController(PLC)isasmallindustrial
computerwhichgenerallymonitorsseveralconnectedsensor
inputsandcontrolsattacheddevices(motorstarters,solenoids,
pilotlights/displays,speeddrives,valves,etc.)accordingtoa
usercreatedprogramstoredinitsmemory.Containinginputs
andoutputssimilartoanRTU,PLCsarefrequentlyusedfor
typicalrelaycontrol,sophisticatedmotioncontrol,process
control,DistributedControlSystemandcomplexnetworking.
Modbus TCP/IP
ModbusTCP/IPsimplytakestheModbusinstructionsetand
wrapsTCP/IParoundit.SinceTCP/IPisthecommunications
standardfortheInternetandmostnetworkedcomputers,this
providesasimplerinstallation.ModbusTCP/IPusesstandard
Ethernetequipment.
Raven Modbus on UDP
WhenSierraWirelessAirLinkmodemsareusedinplaceof
radios,aRavenXTisconnectedtothecentralstation(host)
andaRavenXTisconnectedtoeachremoteunit.Whenthe
RavenXTisconfiguredforModbuswithUDP,theRavenXT
connectedtothehostcanstorealistofIPaddressesornames
withmatchingIDs.Whenthehostatthecentralstationsends
serialdataasapollrequest,theRavenXTatthehostmatches
theRTUIDtoacorrespondingIPofaRavenXTataremote
unit.AUDPpacketisassembledencapsulatingtheRTUID
andserialdatatransmittedfromthehost.TheUDPpacketis
thentransmittedtothespecificRavenXTattheremoteunit
71
20070914
Configuring Modbus/BSAP
matchingtheRTUID.TheremoteRavenXTthendisassembles
thepacketbeforetransmittingtheRTUIDandserialdatato
theremoteunit.TheremoteunitsoperateinnormalUDP
modeandtheirdataissenttothehostviatheremoteRaven
XTandhostRavenXT.
Configuring the Raven XT at the

Polling Host for Modbus on
UDP
ThissectioncoversaPollingHostwithstandardModbus,
variationsmayneedadditionalATcommands.
1. Configure the listening/device ports

InAceManager,selectMiscinthesidemenu.
Figure 9-1: AceManager: Misc
Thedestinationportforthemodematthehostneedstomatch
thedeviceport(*DPORT)inuseonallthemodemsatthe
remotesites.Forexample,iftheremotemodemsdeviceport
(*DPORT)is12345,thentheModbushostmodemsS53
destinationportshouldbesetto12345.
Takenoteof(orset)theDevicePortsettingin*DPORTto
configurethedestinationportontheremotemodems.
Rev 3.0B Feb.08
72
Raven XT GPRS/EDGE
2. Configure the default mode for start-up.

InAceManager,selectUDPinthesidemenu.Selecttheappro
priateMDmodefromthedropdownmenu.
Figure 9-2: AceManager: UDP - MD
MD13:ModbusASCII
MD23:ModbusRTU(Binary)
MD33:BSAP
MD63:VariableModbusindividualparametersareset
upmanually.
3. Configure IP addresses for the Modbus

IDs.
Thelaststepofconfiguringthemodematthehostissetting
theIDstotheirspecificIPs.InAceManager,selectthemenu
optionAddrList.
Figure 9-3: AceManager: Addr List.
73
20070914
Addressescanbeenteredindecimalorhex.AceManagerwill
translatehexentriesintodecimal.Thenumberbeforethe=is
ID,thenumberafteristheIPaddress.Therecanbeatotalof
100remoteID/Localaddressesenteredintothemodem.
WhenusingATcommandsviatelnetordirectserial
connection,useATMLISTfordecimalIDsandATMLISTXfor
hexidecimal.Forexample,iftheIDis27andtheIPis
123.123.123.124,youwouldenteritas
ATMLIST27=123.123.123.124orATMLISTX1B=123.123.123.124.
4. Optional: Dynamic IP Address

IfyoudonothaveastaticIP,thehostmodemshouldbe
configuredtoreportitscurrentIPtoaDynamicDNS(DDNS)
serverwithIPManager.
IntheHostmodemsconfiguration,insteadofIPaddressfor
theAddrList(ATMLISTorATMLISTX),substituteasingle
uniquenameforeachmodem,i.e.remote1,remote2,etc.
WhenyouconfigureIPManagerforthehostmodem,make
noteofyourmodemnameanddomainsettinginAceManager
inthemenuselectionDynamicIPtobeusedwiththeremote
modems.
WithnamesinsteadofIPaddressesfortheAddressList,the
hostmodemwillquerytheDNSserverforthecurrentIP
addressassignedtothespecificnameofaremotemodemto
sendamessagecorrespondingtotheID.
WhenyouusenamesinsteadofIPaddresses,toensureyour
modemsareupdatedquicklywiththecorrectIPaddressesfor
thenames,youwillwanttosettheDNSsettingsaswell.In
AceManager,selectDNS.
Rev 3.0B Feb.08
74
Raven XT GPRS/EDGE
Configure*DNSUSERtothesameIPaddressastheIP
Manager(*IPMANAGER1).IfyourmodemshavedynamicIP
addressesandnotstatic(theIPaddresscanchangewhenitis
poweredup),configure*DNSUPDATEtoalowintervalto
allowfrequentupdates.
Configuring the Remote Raven

XTs for Modbus with UDP
ThissectioncoversstandardModbussettingsfortheRavenXT
attheremoteunit,variationsmayneedadditionalcommands.
1. Configure the ports

InAceManager,selectMiscinthesidemenu.
Figure 9-6: AceManager: Misc
75
20070914
Thedestinationportforthemodematthehostneedstomatch
thedeviceportinuseonallthemodemsattheremotesites.
Forexample,iftheremotemodemsdeviceport(seebelow)is
12345,thentheModbushostmodemsS53destinationport
shouldbesetto12345.
Setthedestinationport(S53)tomatchthedeviceportofthe
hostmodem(*DPORT).Makesurethedeviceportofthe
remotemodem(*DPORT)matchesthedestinationportofthe
hostmodem(S53).
2. Configure IP addresses for the host.

IftheHostmodemhasastaticIPaddress,enteritintheDesti
nationAddressforS53.
Note: With a name instead of
IPs for the host modem, the
remote modems will query the
DNS server for the current IP
assigned to the host modem
before sending data back to the
host.
IfthemodematthehosthasadynamicIPandisusingIP
Manager,insteadofanIPaddressforS53,specifythenameof
thehostmodem(*MODEMNAME).Iftheremotemodemsare
usingadifferentDDNSthanthehostmodem,youwillneedto
specifythefullyqualifieddomainname
(*MODEMNAME+*DOMAIN).
Note: Setting the Host modem IP address as the S53 Destination
Address provides a low level security. The modem will not forward
UDP traffic unless the source IP/port matches what is in S53.
However, if you set *AIP=1, the modem will forward UDP traffic from
any source IP address as long as it is accessing the modem on the
configured *DPORT.
3. Configure the default mode for start-up.

Eachmodemattheremotelocationswillneedtobeconfigured
tocommunicatewiththemodematthehost.InAceManager,
selectUDPinthesidemenu.
Figure 9-7: AceManager: UDP
Rev 3.0B Feb.08
76
Raven XT GPRS/EDGE
a. EnableS82,UDPautoanswer.
b. SetS83totheidletimeoutapplicabletoyourappli
cation,commonly20.
4. Configure other RTU settings.

Otherparametersmayneedtobechanged,butthisis
dependentontheRTUtypebeingused.Asaminimum,this
typicallyinvolvessettingtheproperserialsettingstomatch
yourRTU.
5. Optional: Dynamic IP Address

IfyoudonothaveastaticIP,thehostmodemshouldbe
configuredtoreportitscurrentIPtoaDynamicDNS(DDNS)
serverwithIPManager.
Youwillneedtomatchthenameofthemodemtothenames
specifiedinthehostmodemsMLISTorMLISTXforthe
connectedRTU.
WhenyouconfigureIPManagerforthehostmodem,make
noteofyourmodemnameanddomainsettinginAceManager
inthemenuselectionDynamicIPtobeusedwiththeremote
modems.
WhenyouusenamesinsteadofIPaddresses,toensureyour
modemsareupdatedquicklywiththecorrectIPaddressesfor
thenames,youwillwanttosettheDNSsettingsaswell.In
AceManager,selectDNS.
77
20070914
Configure*DNSUSERtothesameIPaddressastheIP
Manager(*IPMANAGER1).IfyourmodemshavedynamicIP
addressesandnotstatic(theIPaddresscanchangewhenitis
poweredup),configure*DNSUPDATEtoalowintervalto
allowfrequentupdates.
Rev 3.0B Feb.08
78
Raven XT GPRS/EDGE
79
20070914
10: SNMP : Simple Network

Management Protocol
SNMP Configuration
SNMP MIB Definition
Sample
10
TheSimpleNetworkManagementProtocol(SNMP)was
designedtoallowremotemanagementandmonitoringofa
varietyofdevicesfromacentrallocation.TheSNMP
managementsystemisgenerallycomposedofagents(suchas
yourRavenXT,arouter,aUPS,awebserver,afileserver,or
othercomputerequipment)andaNetworkManagement
Station(NMS)whichmonitorsalltheagentsonaspecific
network.Usingthemanagementinformationbase(MIB),an
NMScanincludereporting,networktopologymapping,tools
toallowtrafficmonitoringandtrendanalysis,anddevice
monitoring.
AuthenticationensuresSNMPmessagescomingfromthe
agent,suchastheRavenXT,havenotbeenmodifiedandthe
agentmaynotbequeriedbyunauthorizedusers.SNMPv3
usesaUserBasedSecurityModel(USM)toauthenticateand,
ifdesiredorsupported,messageencryption.USMusesauser
nameandpasswordspecifictoeachdevice.
TheRavenXTcanbeconfiguredasanSNMPagentand
supportsSNMPv2candSNMPv3.
Management Information Base (MIB)

Themanagementinformationbase(MIB)isatypeofdatabase
usedtocompiletheinformationfromthevariousSNMP
agents.Reportsfromvariousagents,suchastheRavenXT,are
sentasdatainformdesignedtobeparsedbytheNMSintoits
MIB.Thedataishierarchicalwithentriesaddressedthrough
objectidentifiers.
SNMP Traps
SNMPtrapsarealertsthatcanbesentfromthemanaged
devicetotheNetworkManagementStationwhenanevent
happens.YourRavenXTiscapableofsendingthelinkUptrap
whenthenetworkconnectionbecomesavailable.
Rev 3.0B Feb.08
80
SNMP : Simple Network Management Protocol
SNMP Configuration
ToconfigureyourRavenXTtoworkasanSNMPagent,you
canuseeitherAceManager,oraterminalconnectionto
configurethemodemusingATcommands.InAceManager,
theSNMPcommandsareallpartoftheOthergroupunderthe
Commongroup.
ThereareonlythreecommandstosetforSNMPintheRaven
XT:thelisteningport,thesecuritylevel,andthetrapdesti
nation.
Figure 10-1: AceManager : Common > Other
Listening Port
*SNMPPORTsetstheportfortheSNMPagenttolistenon.Ifset
tozero,default,SNMPisdisabled.
Tip: SNMP generally uses port 161, however most Internet providers
(including cellular) block all ports below 1024 as a security measure.
You should be able to use a higher numbered port such as 10161.
Security Level
*SNMPSECLVLsetsthesecuritylevelandwhichversionof
SNMPcommunicationsareused.
Rev 3.0B Feb.08
0Nosecurityrequired.SNMPv2candSMNPv3commu
nicationsareallowed.
1Authenticationrequired.SNMPv3isrequiredtodo
authenticationandSNMPv2ctransmissionswillbesilently
discarded.AuthenticationisequivalenttotheauthNoPriv
settinginSNMPv3.
2Authenticationrequiredandmessagesareencrypted.
SNMPv3isrequiredtodoauthentication.SNMPv2cand
SNMPv3authNoPrivtransmissionswillbesilently
discarded.Authenticationandencryptionisequivalentto
theauthPrivsettinginSNMPv3.
81
User Name and Password

Theusernameisuser.Theusernamecannotbechanged.The
RavenXTspasswordisusedastheSNMPpassword(default
is12345).
Tip: The eight-character password requirement for SMNPv3 is not
enforced by the PinPoint X Agent to allow the default password to
function. Your SNMP administrator or MIS may require you to change
to a more secure and/or longer password.
TochangethepasswordintheRavenXT,selectModemfrom
thetopmenulineinAceManager.
Figure 10-2: AceManager : Change Password menu option
Thecurrentpasswordwillbepreentered.Asyoutypethe
newpasswordandconfirmit,thecharactersyoutypewillbe
obscuredbyx.Forthepassword,youcanusenumbers,
letters,and/orpunctuation.
Figure 10-3: Change Password
Caution: The password is case sensitive. drowssaP is not the same

as drowssap.
Rev 3.0B Feb.08
82
Trap Destination
*SNMPTRAPDESTneedstobesetwiththedestinationIPand
port.Ifeitheraresettozeroorempty,SNMPtrapsare
disabled.
Note: Traps are sent out according to the SNMP security level (i.e. if
the security level is 2, traps will be authenticated and encrypted).
Currently, the only trap supported is LinkUp.
Community String
Thecommunitystringcanbeconfiguredusing*SNMPCOM
MUNITY.Thedefaultispublic.
SNMP MIB Definition Sample

AIRLINK-MIB DEFINITIONS ::= BEGIN
IMPORTS
ObjectName FROM SNMPv2-SMI
MODULE-COMPLIANCE FROM SNMPv2-CONF;
org OBJECT IDENTIFIER ::= { iso 3 }
dod OBJECT IDENTIFIER ::= { org 6 }
internet OBJECT IDENTIFIER ::= { dod 1 }
private OBJECT IDENTIFIER ::= { internet 4 }
enterprises OBJECT IDENTIFIER ::= { private 1 }
airlink OBJECT IDENTIFIER ::= { enterprises 20542 }
general OBJECT IDENTIFIER ::= { airlink 1 }
common OBJECT IDENTIFIER ::= { airlink 2 }
status OBJECT IDENTIFIER ::= { airlink 3 }
gps OBJECT IDENTIFIER ::= { airlink 4 }
-- GENERAL -phoneNumber OBJECT-TYPE
SYNTAX DisplayString (SIZE (10))
MAX-ACCESS read-only
STATUS current
::= { general 1 }
deviceID OBJECT-TYPE
SYNTAX DisplayString
STATUS current
::= { general 2 }
Rev 3.0B Feb.08
83
electronicID OBJECT-TYPE
STATUS current
::= { general 3 }
modemType OBJECT-TYPE
STATUS current
::= { general 4 }
aleosSWVer OBJECT-TYPE
STATUS current
::= { general 5 }
aleosHWVer OBJECT-TYPE
STATUS current
::= { general 6 }
modemSWVer OBJECT-TYPE
SYNTAX
DisplayString
STATUS current
::= { general 7 }
modemHWVer OBJECT-TYPE
SYNTAX
DisplayString
STATUS current
::= { general 8 }
-- COMMON -date OBJECT-TYPE
STATUS current
::= { common 1 }
otaProgrammingEnable OBJECT-TYPE
SYNTAX INTEGER {
disabled(0),
enabled(1) }
Rev 3.0B Feb.08
84
STATUS current
::= { common 2 }
devicePort OBJECT-TYPE
SYNTAX INTEGER(0..65535)
STATUS current
::= { common 3 }
netUID OBJECT-TYPE
STATUS
current
::= { common 4 }
netPW OBJECT-TYPE
STATUS current
::= { common 5 }
requestPAP OBJECT-TYPE
SYNTAX
INTEGER {
no(0),
yes(1) }
STATUS current
::= { common 6 }
destinationAddress OBJECT-TYPE
STATUS current
::= { common 7 }
destinationPort OBJECT-TYPE
SYNTAX
INTEGER(0..65535)
STATUS current
::= { common 8 }
serialPortSettings OBJECT-TYPE
STATUS current
::= { common 9 }
serialPortFlowControl OBJECT-TYPE
SYNTAX INTEGER {
Rev 3.0B Feb.08
85
none(0),
hardware(2),
software(4) }
STATUS current
::= { common 10 }
-- STATUS -ipAddress OBJECT-TYPE
SYNTAX IpAddress
STATUS current
::= { status 1 }
netState OBJECT-TYPE
STATUS current
::= { status 2 }
netChannel OBJECT-TYPE
SYNTAX INTEGER
STATUS current
::= { status 3 }
rssi OBJECT-TYPE
SYNTAX
INTEGER(-125..-50)
STATUS current
::= { status 4 }
serialSent OBJECT-TYPE
SYNTAX INTEGER
STATUS current
::= { status 5 }
serialReceived OBJECT-TYPE
SYNTAX INTEGER
STATUS
current
::= { status 6 }
hostMode OBJECT-TYPE
STATUS current
::= { status 7 }
Rev 3.0B Feb.08
86
powerMode OBJECT-TYPE
SYNTAX
DisplayString
STATUS current
::= { status 8 }
fixObtained OBJECT-TYPE
SYNTAX INTEGER {
no(0),
yes(1) }
STATUS current
::= { gps 1 }
satelliteCount OBJECT-TYPE
SYNTAX INTEGER
STATUS current
::= { gps 2 }
latitude OBJECT-TYPE
STATUS current
::= { gps 3 }
longitude OBJECT-TYPE
STATUS current
::= { gps 4 }
END
Display Responses
Thestringthatisdisplayedfortheseobjectsisthesame
displayforthecorrespondingATCommand.
Object
Rev 3.0B Feb.08
AT Command
phoneNumber
*NETPHONE?
deviceID
*DEVICEID?
electronicID
I3
aleosSWVer
I1
87
Object
AT Command
aleosHWVer
I1
modemSWVer
I2
modemHWVer
I2
date
*DATE?
otaProgrammingEnable
OPRG?
devicePort
*DPORT?
netUID
*NETUID?
netPW
*NETPW?
requestPAP
*HOSTPAP?
destinationAddress
S53
destinationPort
S53
serialPortSettings
S23
serialPortFlowControl
\Q
ipAddress
*NETIP?
netState
*NETSTATE?
netChannel
*NETCHAN?
rssi
*NETRSSI?
serialSent
not applicable for Raven-E
serialReceived
not applicable for Raven-E
hostMode
*HOSTMODE?
powerMode
*POWERMODE?
PinPoint line modems only
fixObtained
satelliteCount
latitude
longitude
Product ID
EachmodemtypehasauniqueIDassociatedwithitsoyou
canmoreeasilyidentifythemodemfromitstypeonyour
network.
Rev 3.0B Feb.08
88
A: Configuration Commands
Info (information)
Status
Common
Logging
Telemetry/Addr List
Edge/HSDPA
Theconfigurationcommands(ATcommands)inthischapter
arearrangedaccordingtotheirplacementinAceManager.
ThecommandsavailableinAceManagerwilldependofthe
modelnumberofyourRavenXTand,insomecases,the
versionoftheALEOSfirmwareinstalled.
Note: Some commands can only be configured using a terminal
emulation and typed AT commands. Some commands also require
PassThru mode.
Tip: You can use a fully qualified domain name instead of an IP

address for most configuration options calling for an IP address if your
Raven XT is configured to use DNS. DNS settings frequently come
directly from your cellular provider while your Raven XT is registering
on the cellular network and receiving its IP address.
Info (information)
ThecommandsintheInfogrouphavereadonlyparam
eters.Theyonlyprovideinformationaboutthemodem.Some
oftheinformationdisplayedinthisgroupdoesnotcorrespond
directlytoATcommands.
Rev 3.0B Feb.08
89
Raven XT GPRS/EDGE
Figure 1-1: AceManager : Info
*DEVICEID?
The64bitdeviceIDthemodemusestoidentifyitselftothe
cellularnetwork.
*NETPHONE?
Themodemsphonenumber,ifapplicableorobtainable.
&V
Viewactiveprofile,thecontentsoftheactiveregisters.Not
displayedwithAceManager.
In
n=0:Productname(forexample,RavenXT).
n=1:TheRavenXTsfirmware(ALEOS)version,hardware
ID,andcopyright.
n=2:Theinternalhardwaresfirmwareversionand
relevanthardwareID.
n=3:Thehardwaremodulesuniqueidentificationnumber
orserialnumber.
n=5:Viewactiveprofile(thecontentsoftheactive
registers).NotdisplayedwithAceManager.
Information Displayed in AceManager

without AT Commands Listed
90
VersionsofALEOS,internalhardware,boot,andMSCI:
Versionsofinternallyconfiguredhardwareandsoftware.
20070914
Configuration Commands
Status
MostofthecommandsintheStatusgrouphavereadonly
parametersandprovideinformationaboutthemodem.The
StatusGrouphasmorefieldsthatcanbedisplayedonmost
screens.Youcaneitherresizeyourwindoworusethescroll
baronthesidetodisplaytheremainder.
Figure 1-2: AceManager : Status
*BOARDTEMP?
Thetemperature,inCelsius,oftheinternalhardware.
*HOSTMODE?
Thecurrenthostmode(AT,PPP,UDP,etc.).IftheRavenXTis
notinATmode,telnetintothemodemtoexecutethis
command.
*NETERR?
TheEDGEorGPRSnetworkbiterrorrate.
*NETIP?
Note: If there is no current
network IP address, 0.0.0.0 may
be displayed.
ThecurrentIPaddressofthemodemreportedbytheinternal
module,generallyobtainedfromyourcellularprovider.This
istheaddresscancontacttheRavenXTfromtheInternet.
Tip: Use *NETALLOWZEROIP if you need to allow the display of an
IP ending in a zero.
Rev 3.0B Feb.08
91
Raven XT GPRS/EDGE
*NETOP?
Thecurrentcellularcarrierfromthemodemsfirmware
version,forexample,yourcellularprovider.
*NETRSSI?
ThecurrentRSSI(ReceiveSignalStrengthIndicator)ofthe
RavenXTasanegativedBmvalue.
Tip: The same information is displayed with the command S202?.
*NETSERV?
Thetypeofservicebeingusedbythemodem,forexample
Tech.
*NETSTATE?
Thecurrentnetworkstate:
ConnectingToNetwork:TheRavenXTisintheprocessof
tryingtoconnecttothecellularnetwork.
NetworkAuthenticationFail:Authenticationtothe
cellularnetworkhasfailed.Verifysettingstoactivatethe
RavenXT.
DataConnectionFailed:TheRavenXTfailedtoconnect,
anditisnowwaitingasettimeintervalbeforeitattempts
toreconnect.VerifysettingstoactivatetheRavenXT.
NetworkNegotiationFail:Networkconnectionnegoti
ationfailed.Thisisusuallytemporaryandoftenclearsup
duringasubsequentattempt.
NetworkReady:TheRavenXTisconnectedtothe1x
cellularnetworkandreadytosenddata.
NetworkDormant:TheRavenXTisconnectedtothe1x
cellularnetwork,butthelinkisdormant.Itwillbewoken
upwhendataissentorreceived.
NoService:Thereisnocellularnetworkdetected.
HardwareReset:Theinternalmoduleisbeingreset.This
isatemporarystate.
*POWERIN?
Thevoltageinputtotheinternalhardware.
+ICCID
SubscriberIdentityModuleID..
92
20070914
+RCIQ
CurrentCellInfoInformation.GPRSorEDGEOnly.
Information Displayed in AceManager

without AT Commands Listed
BytesandPacketsReceivedandSent:Networktrafficfor
theapplicableport.
NumberofSystemResets:Counterofthenumberof
systemresetsoverthelifeofthemodemorsincethe
configurationwasreset.
BadPasswordCount:Counterofthenumberofbad
passwordattempts.
IPRejectCountorLog:RejectedIPData.
TemperatureoftheInternalHardwareModule:The
temperatureoftheinternalradiomodule.
AT Commands Requiring PassThru mode

ThesecommandsarenotdisplayedinAceManager.
+CCID
SubscriberIdentityModuleID.
SubscriberIdentityModuleID.
Rev 3.0B Feb.08
93
Raven XT GPRS/EDGE
Common
ThegroupsundertheheadingCommonencompassthose
commandsthatarecommontomostSierraWirelessAirLink
modems.
Misc (Miscellaneous)
ThecommandsoftheMiscgroupareavarietyofcommands
thatdontdirectlyfitinothercategories.
Figure 1-3: AceManager : Misc
+++
Note: +++ is not proceeded by
AT nor does it require a carriage
return (enter). There must be an
idle time (set by S50) on the
serial port before and after this
command.
ATEscapesequence.IftheRavenXTisinadatamode(any
modeotherthanPassThru),thiscommandcausesthemodem
toreenterATcommandmode.The+isASCII0x2B.+++ is
not available in AceManager.
Tip: DAE=1 disables the +++ command.
A/
Note: A/ is not proceeded by AT.
Reexecutelastcommand.A/isnotusedinAceManager.
A
Manuallyansweranincomingconnection.Aisnotusedin
AceManager.
94
20070914
D[method][d.d.d.d][/ppppp] or D[method][@name][/
ppppp]
DialaconnectiontoaremoteIPandPortusingmethod.
CannotbeconfiguredinAceManager.
method=P:EstablishaUDPconnection
method=T:EstablishaTCPconnection
method=N:EstablishaTelnetconnection
d.d.d.d=IPaddresstocontact
ppppp=porttocontact
Examples:
ATD - Dial (establish) default connection.
ATDP192.168.13.31/2332 - Dial (establish) UDP session to
192.168.13.31, at port 2332.
Toendtheconnection,issuethe+++escapesequenceordrop
theDTRline(ifIgnoreDTRS211=0or&D2).Thedefault
connectionissetinS53.
Ifthemethod,IPaddress,orportisomitted,thevaluesfrom
S53areused.Ifatelnetconnectionisrequested(N)andthe
portisnotsupplied,port23willbeusedinsteadofthevalue
fromS53.
Ifadomainnameisspecified,the@symbolcanbeusedto
explicitlyindicatethestartofthename.Forexample,if
ATDPHONYisissued,thiswillbeinterpretedasdialaUDP
connectiontoHONY.Todialusingthedefaultmethodto
hostPHONY,onewouldissueATD@PHONY.
Severalspecialdialingnumbersexisttomakeiteasyto
establishaPPPorSLIPconnectionwiththemodem.
ATD#19788orATDT#19788willestablishaPPPconnection
(see\APPP)andATDT#7547willestablishaSLIPconnection
(see\ASLIP).
Tip: The source port of the session is the Device Port (set by S110 or
*DPORT).
DS=n
AllowsaPPPconnectiontobeinitiatedonthehostport.
n=2:InitiatesthePPPconnection.
Hn
HangUpCommand.
Rev 3.0B Feb.08
n=1:Hangup
95
Raven XT GPRS/EDGE
WithanATtelnetconnection,thiscommandwillterminatethe
hostdatamodeandreturntheRavenXTtoanATmode.
CannotbeaccessedinAceManager.
O
Online(Remote):CausestheRaventogofromCommandState
todatastate.CannotbeconfiguredinAceManager.
OPRG=n
Enables/disablesovertheairfirmwareupgradingoftheRaven
XT.WhenSierraWirelessreleasesanewversionofALEOS,
youcanupgradeyourremotemodemswithOPRGenabled.
n=0:Disables
n=1:Enables
S53=[method][d.d.d.d][/ppppp]
DestinationIPaddress,port,andmethod.Theseareusedas
defaultsfortheD(Dial)ATcommand.
method=P:UDP
method=T:TCP
method=N:Telnet
d.d.d.d=IPaddressordomainname
ppppp=theportaddress
Examples:
ATS53=T192.168.100.23/12345
ATS53=foo.earlink.com
TelnettothespecifiedIPatport12345.
ATS53=192.168.100.23/12345
QuerythespecifiedIPatport12345.
ATS53=/12345
Queryport12345.
Z
ResettheRavenXT.InAceManager,thiscommandis
performedwiththeResetoptiononthetoolbar.
Tip: *DATZ=1 will disable Z.
&W
Writesallchangedmodemsettings.Ifthiscommandisnot
issued,anymodifiedvalueswillrevertbacktotheirprevious
valuesatmodemreset.CannotbeconfiguredinAceManager.
96
20070914
*DATE=[mm/dd/yyyy],[hh:mm:ss]
Setsandqueriestheinternalclock.Eitherthedateandtime
canbespecified,orsimplyoneofthetwocanbespecifiedin
whichcasetheunspecifiedvaluewillremainunchanged.The
dateandtimearealwaysspecified24hournotation.
mm/dd/yyyy=dateinmonth/day/yearnotation
hh:mm:ss=timein24hournotation
*DPORT=n
ThemodemsDevicePortwhichthemodemislisteningonfor
inboundpackets/data/polls.Canalsobesetwiththecommand
S110.
n=165535
*HOSTPAP=n
UsePAPtorequesttheuserloginandpasswordduringPPP
negotiationonthehostconnection.
n=0:DisablePAPrequest(Default).
n=1:TakesuserloginandpasswordfromWindowsDUN
connectionandcopiesto*NETUIDand*NETPW.
*NETALLOWZEROIP=n
AllowsthedisplayedIPaddressin*NETIPtoendinzero(ex.
192.168.1.0).
n=0:Donotallow.
n=1:Allow.
*NETPW=pw
Thepasswordthatisusedtologintothecellularnetwork,
whenrequired.
pw=password(30charactersmaximum)
*NETPHONE?
Themodemsphonenumber,ifapplicableorobtainable.
*NETUID=uid
Theloginthatisusedtologintothecellularnetwork,when
required.
Rev 3.0B Feb.08
uid=userid(upto64bytes)
97
Raven XT GPRS/EDGE
*STATICIP=d.d.d.d
SetthestaticIPrequiredtobereceivedfromthenetwork.Ifthe
modemdoesnotgetthisIPaddressfromthenetwork,itwill
resettheinternalhardwareandtryagain.Thedefaultis0.0.0.0,
whichallowsanyIPaddressfromthenetwork.
d.d.d.d=IPaddress
Example:
AT*STATICIP=192.168.1.23
Caution: STATICIP does not set the IP address of the modem, it

merely tells the modem which IP address to expect. If the expected IP
address is not granted while registering on the cellular network, the
modem will try to register on the network again until it receives that IP
address. If your account is set up for a dynamic IP address and you
set an address for *STATICIP, you may not be able to register on the
network at all since there is no guarantee you will receive the same
dynamic IP address again.
*STATUSCHK=n
ChecksifanSMSmessagehasbeenreceivedbythemodem.
n=1255:Secondsbetweenchecks.
n=0:Nevercheck.
Serial
Thisgroupincludescommandsspecifictogeneraluseofthe
serialport.
Figure 1-4:
AceManager : Serial
98
20070914
En
ToggleATcommandechomode.
n=0:EchoOff.
n=1:EchoOn.
With more than one connection types (serial, Telnet, and USB) the
echo command can be set differently on each interface. Qn
TheATquietmodesetting.Ifquietmodeisset,therewillbe
noresponsestoATcommandsexceptfordataqueried.
n=0:Off(Default).
n=1:Quietmodeon.
S3=n
Thestandardendoflinecharacterusedtoindicatetheendof
anATcommand.Thischaracterisalsousedasthecarriage
returncharacterforframingresponsesandresultcodesin
commandstate.CannotbeconfiguredinAceManager.
n=0127(ASCIIcharacternumber)
S4=n
Thestandardlinefeedcharactersentbythemodemtothehost
attheendofaresponseorreturncodeincommandstate.
S5=n
Thisregistersetsthecharacterrecognizedasabackspace
duringcommandentry.CannotbeconfiguredinAceManager.
S6=n
n=210seconds
S8=n
Wheneveradialcommandcontainsthecommacharacter,the
contentsofthisregisterspecifythepausetimeforeachcomma.
n=0255
S9=n
Specifiesthetimethatthereceivedcarriermustbepresentfor
themodemtorecognizeitandturnonDataCarrierDetect
(DCD)ifapplicable.TheimplementationisentirelyattheIWF
modem.CannotbeconfiguredinAceManager.
Rev 3.0B Feb.08
99
Raven XT GPRS/EDGE
n=0255
S10=n
Specifiestheamountoftimethatthecarrierfromtheremote
modemcanbelostbeforethemodemgoesonhook.This
allowstemporarydisruptionstocarrierwithoutdisconnecting.
Asettingof255causesthemodemtodisableCarrierDetect
andpresumecarrierisalwayspresent.Cannotbeconfigured
inAceManager.
n=12545
S23=[speed],[databits][parity][stop bits]
Seriallineparameters.Thesettingstakeaffectafterreset.
speed=300|1200|2400|4800|9600|19200|38400|
57600|115200|230400
databits=7or8(DatabitsMUSTbe8databitsforPPP
mode.)
parity=O:Odd
parity=E:Even
parity=N:None
parity=M:Mark
stopbits=1|1.5|2
Example:
ATS23=19200,8N1
Setsmodemto19200,8databits,noparity,and1stopbit.
Tip: Can also be set using &L=[speed],[databits] [parity][stop bits]
S50=n
Dataforwardingidletimeout.Ifsetto0,aforwardingtime
outof10msisused.UsedinUDPorTCPPADmode.
n=tenthsofasecond
S51=n
PADdataforwardingcharacter.ASCIIcodeofcharacterthat
willcausedatatobeforwarded.UsedinUDPorTCPPAD
mode.
100
n=0:Noforwardingcharacter.
20070914
S211=n
Forapplicationsorsituationswherehardwarecontrolofthe
DTRsignalisnotpossible,themodemcanbeconfiguredto
ignoreDTR.WhenIgnoreDTRisenabled,themodem
operatesasiftheDTRsignalisalwaysasserted.
n=0:UsehardwareDTR.(default).
n=1:IgnoreDTR.
n=3:IgnoreDTRandassertDSR.Thisvalueisdeprecated,
anditisrecommendedtouse&StocontroltheDSR
instead.Whenthisvalueissetto3,&Swillautomatically
besetto0.Seealso:&Dand&S.
Vn
CommandResponseMode.
n=0:Terse(numeric)commandresponses
n=1:Verbosecommandresponses(Default).
Xn
ExtendedCallProgressResultmode.
n=0:Turnoffextendedresultcodes(Default).
n=1:Turnonresultcodes.Thisaddsthetext19200tothe
CONNECTresponse.
&Cn
SetDCDmode.
n=0:AlwaysassertDCD.
n=1:AssertDCDwheninadatamode(UDP,TCP,PPP,or
SLIP)(Default).
n=2:AssertDCDwhenthemodemhasnetworkcoverage.
&Dn
SetDTRmode.
n=0:IgnoreDTR,sameeffectasHWDTRalwaysasserted
(sameasS211=1).
n=2:UsehardwareDTR(sameasS211=0).
&Sn
SetDSRmode.
Rev 3.0B Feb.08
n=0:AlwaysassertDSR(Default).
n=1:AssertDSRwheninadatamode(UDP,TCP,PPP,or
SLIP)(Default).
n=2:AssertDSRwhenthemodemhasnetworkcoverage.
101
Raven XT GPRS/EDGE
Tip: S211 can also be used to request that DSR is always asserted. If
S211 is set to 3 and &S is changed to a non-zero value, S211 will be
changed to 1.
\APPP
SetmodemoperationtoPPPmode.Cannotbeconfiguredin
AceManager.\ASLIP
SetmodemoperationtoSLIPmode.DTRmustbeasserted
(&D0orS211=1).CannotbeconfiguredinAceManager.
\Qn
Setorquerytheserialportflowcontrolsetting.
n=0:Noflowcontrolisbeingused.
n=1:RTS/CTShardwareflowcontrolisbeingused.
n=4:Transparentsoftwareflowcontrol.Usesescaped
XONandXOFFforflowcontrol.XONandXOFF
charactersindatastreamareescapedwiththe@character
(0x40).@indataissentas@@.
*CTSE=n
ClearToSendEnable:ThisfeatureassertsCTSwhenthereisa
networkconnection.
n=0:Disabled(Default).
n=1:EnableassertionofCTSwhenthereisnetwork
coverage.
RS232voltagelevels:
Positive = Network coverage.
Negative = No coverage.
Tip: Flow control (AT\Q) will override this indication, so if you want to
use CTS to indicate network coverage, flow control has to be off
(AT\Q0).
*MODEMHISPEED
Settheinternalseriallinkspeedtotheinternal(radio)module.
n=0:115200(default)
n=1:230400
*NUMTOIP=n
Convert12digitnumbertoIP.
102
n=0:Useasname.
20070914
n=1:UseasIPaddress.
*PPPNOCARRIER=n
ProvidesaNoCarriermessagetoadeviceconnectedtothe
serialportusingPPPorCHAPwhenthecellularconnection
becomesunavailable.
n=1:Enabled.
TCP
ThisgroupincludescommandsspecifictoTCPserialcommu
nications.
Figure 1-5: AceManager : TCP
S0=n
ThisregisterdetermineshowtheRavenXTrespondstoan
incomingTCPconnectionrequest.TheRavenXTremainsin
ATCommandmodeuntilaconnectionrequestisreceived.
DTRmustbeasserted(S211=1or&D0)andtheRavenXTmust
besetforasuccessfulTCPconnection.TheRavenXTwillsend
aRINGstringtothehost.ACONNECTsenttothehost
indicatesacknowledgementoftheconnectionrequestandthe
TCPsessionisestablished.
n=0:Off(Default).
n=1:On.
n=2:UseTelnetservermodeonTCPconnections.
n=3:WithaTelnetconnection,overridestheclients
defaultecho,allowingtheserveronthehostportto
performtheecho.CRLFsequencesfromthetelnetclient
willalsobeeditedtosimplypassCRstotheserveronthe
hostport.
S7=n
SpecifiesthenumberofsecondstowaitforaTCPconnection
tobeestablishedwhendialingout.
Rev 3.0B Feb.08
103
Raven XT GPRS/EDGE
n=seconds
S60=n
TelnetClientEchoMode.
n=0:NoEcho
n=1:LocalEcho(Default)
n=2:RemoteEcho
S221=n
ConnectDelay:NumberofsecondstodelaytheCONNECT
responseuponestablishingaTCPconnection.ORNumberof
tenthsofsecondstodelaybeforeoutputtingENQontheserial
portaftertheCONNECTwhentheENQfeatureisenabled
n=0255
TCPS=n
TCPconnectiontimeout(TCPS)units.Specifiesatimeinterval
uponwhichifthereisnoinoroutboundtrafficthroughaTCP
connection,theconnectionwillbeterminated.
n=0:minutes
n=1:seconds
TCPT=n
IntervaltoterminateaTCPconnectionwhennoinor
outboundtraffic.ThisvalueaffectsonlytheTCPconnectionin
TCPPADmode.
n=interval
Caution: TCPT should never be 0 when using the TCP mode. A

broken TCP session can result in the modem being left with a TCP
half-open connection that can only be terminated with a reset.
*ENQ=n
OutputsanENQ[0x05]aftertheTCPCONNECTdelayedby
theDelayConnectResponsetime(S221).
n=1:EnableENQonCONNECT.
UDP
ThisgroupincludescommandsspecifictoUDPserialcommu
nications.
104
20070914
Figure 1-6: AceManager : UDP
AIP=n
AllowIPaddress.
n=0:AllowonlytheIPaddressspecifiedinS53toconnect
whenUDPautoanswerisenabled(S82=2).
n=1:AllowanyincomingIPaddresstoconnectwhen
UDPautoanswerisenabled(S82=2).
Note: Always subject to any Friends filters that may be defined.
HOR=n
HalfOpenResponseInUDPautoanswer(halfopen)mode.
n=0:NoresponsecodeswhenUDPsessionisinitiated.
n=1:RINGCONNECTresponsecodessentoutseriallink
beforethedatafromthefirstUDPpacket.
Note: Quiet Mode must be Off.
MDhh
Defaultpowerupmodefortheserialport:WhentheRavenXT
modemispowercycled,theserialportentersthemode
specifiedbythiscommandafter5seconds.Onstartup,typing
ATMD0within5secondschangesthemodetonormal(AT
command)mode.SeealsoS53tosettheportforUDPorTCP.
Rev 3.0B Feb.08
hh(hexbyte)=00:normal
hh=01:SLIP
hh=02:PPP
hh=03:UDP
hh=04:TCP
hh=07:PassThru
hh=0F:PinPointMDT
105
Raven XT GPRS/EDGE
hh=13:ModbusASCII
hh=23:ModbusRTU(Binary)
hh=33:BSAP
hh=63:VariableModbus
hh=73:ReliableUDP
hh=83:UDPMulticast
S82=n
EnablesUDPautoanswer(halfopen)mode.
n=0:Normalmode
n=2:EnableUDPautoanswermode.
S83=n
SetorqueryUDPautoansweridletimeout.Ifnodataissent
orreceivedbeforethetimeoutoccurs,thecurrentUDPsession
willbeterminated.Whileasessionisactive,packetsfrom
otherIPaddresseswillbediscarded(unless*UALLisset).
n=0:Noidletimeout(Default).
n=1255:Timeoutinseconds.
*DU=n
ThedialcommandalwaysusesUDP,evenwhenusingATDT.
n=0:Dialusingthemeansspecified(default).
n=1:DialUDPalways,evenwhenusingATDT.
Note: When this parameter is set you cannot establish a TCP PAD
connection.
*UALL=n
AcceptsUDPpacketsfromanyIPaddresswhenaUDP
sessionisactive.IfthereisnoUDPsessionactive,anincoming
UDPpacketwillbetreatedaccordingtotheUDPautoanswer
andAIPsettings.
106
n=0:Noeffect(Default).
n=1:AcceptUDPdatafromallIPaddresseswhenina
UDPsession.
20070914
*UDPLAST=n
Note: *UDPLAST does not
change the S53 setting in
NVRAM. If the modem is reset,
the original S53 setting will be
restored from NVRAM.
Ifenabled,setsS53tothelastacceptedIPaddressthrough
UDPautoanswer.ThiscanbeusedinconjunctionwithMD3
sothatwhenthereisnoUDPsession,newethernethostdata
willcauseaconnectiontoberestoredtothelastIPaccepted
throughUDPautoanswer.
n=0:DoesnotchangeS53setting.(Default).
n=1:SetS53tothelastacceptedIP.
*USD=n
WaitsthespecifieddelaybeforesendingthefirstUDPpacket
andthesubsequentUDPpacketsouttotheportEthernet.
n=0:NoUDPpacketdelay(Default).
n=1255:Delayin100msunits,from100msto25.5sec.
DNS
Thisgroupincludescommandsspecifictothemodembeing
abletousedomainnamesinsteadofIPaddressesforother
configurationoptions.
Figure 1-7: AceManager : DNS
*DNSn=d.d.d.d
QueriestheDNSaddresses.Yourcellularcarrierprovidesthe
DNSaddresseswhileyourmodemisregisteringontheir
network.
n=1or2:FirstandsecondDNSaddress.
d.d.d.d=IPaddressofdomainserver.
*DNSUPDATE=n
IndicateswhetherthemodemshouldsendDNSupdatestothe
DNSserverspecifiedby*DNSUSER.Theseupdatesareasper
RFC2136.Theyarenotsecureandarerecommendedonlyfora
privatenetwork.Inapublicnetwork,theIPLoggerservices
shouldbeusedinstead.
Rev 3.0B Feb.08
n=0:DNSupdatesdisabled(Default).
n=1:DNSupdatesenabled.
107
Raven XT GPRS/EDGE
*DNSUSER=d.d.d.d
SetsauserprovidedDNStoqueryfirstwhenperforming
nameresolutionsinthemodem.
d.d.d.d=IPaddressofdomainserver
Dynamic IP
ThisgroupincludescommandsspecifictodynamicDNS.
DynamicDNSallowstheRavenXTtouseadynamicIP
addressaccount,withanIPaddressthatcanchangeeachtime
youconnect,andstillallowyoutouseafullyqualifieddomain
nametocontacttheRavenXTusingIPManagerrunningona
serverwithadynamicDNSupdater.
Figure 1-8: AceManager : Dynamic IP
*DOMAIN=name
Domain(ordomainzone)ofwhichtheRavenXTisapart.This
valueisusedduringnameresolutionsifafullyqualifiedname
isnotprovidedandalsoforDNSupdates.Thisvaluecanbe
upto20characterslong.
name=domainname(i.e.eairlink.com)
If*DOMAIN=eairlink.com,thenwhenATDT@remote1is
entered,thefullyqualifiednameremote1.eairlink.comwillbe
usedtoperformaDNSquerytoresolvethenametoanIP
address.
Tip: Only letters, numbers, hyphens, and periods can be used in a
domain name.
108
20070914
*IPMANAGERn=[name][IP address]
SetsadomainnameorIPaddresstosendIPchangenotifica
tionsto.UptotwoindependentIPManagerserverscanbeset,
usingeitherAT*IPMANAGER1orAT*IPMANAGER2.
Updatestoaservercanbedisabledbysettingthatentryto
nothing(forexample,AT*IPMANAGER1=).
n=1:FirstIPManagerserver.
n=2:SecondIPManagerserver.
name=domainname
*IPMGRKEYn=key
Setsthe128bitkeytousetoauthenticatetheIPupdatenotifi
cations.Ifthekeysvalueisallzeros,adefaultkeywillbe
used.IfallthebytesinthekeyaresettoFF,thennokeywillbe
used(i.e.theIPchangenotificationswillnotbeauthenticated).
AT*IPMGRKEY1isusedtosetthekeytousewith
AT*IPMANAGER1,whileAT*IPMGRKEY2isusedtothekey
withAT*IPMANAGER2.
key=128bitkeyinhexadecimal[32hexcharacters]
*IPMGRUPDATEn=m
SetsthenumberofminutestoperiodicallysendanIPupdate
notificationtothecorrespondingserver.Thiswilloccurevenif
theIPaddressoftheRavenXTdoesntchange.
*IPMGRUPDATE1isusedtosettherefreshrateto
*IPMANAGER1,while*IPMGRUPDATE2isusedwith
*IPMANAGER2.Ifthevalueissetto0,thenperiodicupdates
willnotbeissued(i.e.IPchangenotificationswillonlybesent
whentheIPactuallychanges).
m=0,5255:Numberofminutestosendanupdate.
*MODEMNAME=name
NameoftheRavenXT(upto20characterslong)tousewhen
performingIPaddresschangenotificationstoIPManager.The
valuein*DOMAINprovidesthedomainzonetoaddtothis
name.
name=modemname(forexample,mymodem)
Example:if*MODEMNAME=mymodemand
*DOMAIN=eairlink.com,thenthemodemsfullyqualified
domainnameismymodem.eairlink.com.
Rev 3.0B Feb.08
109
Raven XT GPRS/EDGE
AutomaticallyGeneratedNames:
#I3TheESN/IMEIwillbeusedasthename.
#CCIDTheCCIDwillbeusedasthename.
#NETPHONEThephonenumberwillbeusedasthename.
Tip: Each modem using IP Manager needs a unique name. Two
modems cannot be called mymodem. One could be mymodem1
with the other as mymodem.
PPP/Ethernet
ThisgroupincludescommandsspecifictoPPP(serial)or
EthernetconnectionsbetweentheRavenXTandaconnected
device.
*DHCPSERVER=n
110
ActasaDHCPserverforanyEthernetdeviceconnecting
totheRavenXT.DHCP(DynamicHostConfiguration
Protocol)allowsonedevice,theDHCPserver,toprovide
dynamicIPaddressestoanyotherdevicewhichrequests
them.
n=0:DisablestheDHCPserver.
n=1:Enabled.ThemodemwillactastheprimaryDHCP
serverforthenetwork.
n=2:EnabledifnootherDHCPserverisdetected
(default).IfanotherDHCPserverisdetectedonthe
network,theRavenXTwillnotsendoutrepliestoDHCP
requests.n=0:Disabled.TheRavenXwillnotsendout
repliestoDHCPrequests.
20070914
*HOSTAUTH=n
HostAuthenticationMode:UsePAPorCHAPtorequestthe
userloginandpasswordduringPPPorCHAPnegotiationon
thehostconnection.Theusernameandpasswordsetin
*HOSTUIDand*HOSTPWwillbeused.
n=0:DisablePAPorCHAPrequest(Default).
n=1:PAPandCHAP.
n=2:CHAP
*HOSTNETMASK=n.n.n.n
Subnetmaskforthehostinterface.Allowscommunication
withasubnetbehindthehostinterface.
n.n.n.n=subnetmask,example255.255.255.0.
*HOSTPEERIP=d.d.d.d
SetorquerytheIPaddressthatcanbeusedtodirectlycontact
theRavenXTonceacellularconnectionisestablished.Ifthis
valueisnotspecified,192.168.13.31willbeused.
d.d.d.d=localorpeerIPaddressofthemodem.
Note: This is not normally used nor needed by user applications.
*HOSTPRIVIP=d.d.d.d
SetorquerytheprivateIPaddressthatistobenegotiatedby
the1xconnectionif*HOSTPRIVMODE=1.
d.d.d.d=IPAddress
*HOSTPRIVMODE=n
Setorquerywhetheraprivateorpublic(network)IPistobe
usedwhentheHostinitiatesa1xconnectiontothemodem.
n=0:Public(network)IPMode:WhentheHostinitiatesa
PPPconnection,thehostwillbegiventhenetworkIP
addressthatwasobtainedfromthecellularcarrierwhile
registeringonthenetwork.IfthenetworkissuesanewIP
address,thecellularconnectionwillbeclosed(sincetheIP
addresshaschanged)andhastobereinitiated.(default).
n=1:PrivateIPMode:WhentheHostinitiatesa1x
connection,thehostwillbegiventheIPaddressspecified
in*HOSTPRIVIP.Themodemwillthenperform1to1
NATlikeaddresstranslation,whichshieldstheHostfrom
networkIPchanges.
*HOSTPW=string
HostPasswordforPAPorCHAP.
Rev 3.0B Feb.08
111
Raven XT GPRS/EDGE
string=password
*HOSTUID=string
HostUserIDforPAPorCHAP.
string=userid(upto64bytes)
PassThru
PassThruModeisusedtocommunicatedirectlytotheRaven
XTinternalhardware.
Caution: While the modem is in PassThru mode, ALEOS is disabled.
If you need to connect to the Raven XT while it is in PassThru mode,
you will need to do so with a terminal application. Not all commands
are available while the modem is in PassThru mode.
Figure 1-10: AceManager : PassThru
\APASSTHRU
Note: This mode is not available
through the remote AT telnet
server. You will need to connect
to the Raven XT with it
connected directly to your
computer.
Setsthemodemoperationtopassthroughmode.Thismode
willpassanycharactersreceivedontheportEthernetdirectly
totheinternalhardwaremoduleandoutputanycharacters
fromtheinternalhardwaremoduleouttheportEthernet.This
allowsdirectaccess/configurationofthehardwaremodule.
Oncethismodeisentered,theunitmustbephysicallyresetto
returntonormaloperation.Thiscommandisnotavailablein
AceManager.
Note: It may take up to 30 seconds for the hardware module to
respond after CONNECT is output.
*CSX1=n
PassThruEcho:Echodatatothehost.
112
n=0:Datawillbepassedtothehost.
20070914
n=1:PASSTHRUmodewillechoallhostreceiveddata
andwillnotpassthedatatothemodemwhilethemodem
isnotassertingDCD.
Note: If the modem is asserting DCD, data will be passed from the
host to the modem as it normally is when *CSX1=0.
*PTINIT=string
AnyATCommandstringtobepassedtotheOEMmodule
beforeenteringPASSTHRUmode,e.g.AT&S1V1,etc.
string=ATcommand(s)
*PTREFRESH=n
NumberofminutesofinactivityinPASSTHRUmodeto
resendthe*PTINITstringtothehardwaremodule.
n=0:Disabled
n=1255minutes
*RESETPERIOD=n
InPASSTHRUmode,modemwillberesetafterthisperiodif
nodatahasbeensentorreceived.Valueisinhours.
n=0:Disabled
n=1255hours
SMTP
SMTP(SimpleMailTransferProtocol)isthedefactostandard
foremailtransmissionacrosstheInternet.TheRavenXTcan
sendmessagesusingSMTPifithasbeenconfiguredtousea
mailserver.
Note: You cannot send an Email with your Raven XT unless the
Email server you have configured allows your Raven XT as a relay
host. Talk to your network administrator to ensure you can send email
through the email server using your Raven XT.
SMS(ShortMessageService)isanotherwaytosendmessages
viathecellularnetwork.MostSMScommandsrequirethe
modemtobeinPassThrumode.
Note: SMS may not be supported by your account with your cellular
carrier.
Rev 3.0B Feb.08
113
Raven XT GPRS/EDGE
Figure 1-11: AceManager : SMTP
*NETSMS2EMAIL=n
SpecifytheSMS/Emailservernumber.Thismaybenecessary
tosendanSMSmessagetoanemailaddress.Cannotbeused
withAceManager.
n=SMS/Emailservernumber
*SMTPADDR=[d.d.d.d][name]
SpecifytheIPaddressorFullyQualifiedDomainName
(FQDN)oftheSMTPservertouse.
d.d.d.d=IPAddress
name=domainname(maximum:40characters).
*SMTPFROM=email
SetstheemailaddressfromwhichtheSMTPmessageisbeing
sent.
email=emailaddress(maximum:30characters).
*SMTPPW=pw
Setsthepasswordtousewhenauthenticatingtheemail
account(*SMTPFROM)withtheserver(*SMTPADDR).
pw=password
Note: Not required to use SMTP settings but may be required by your
cellular carrier.
*SMTPSEND=email[body]
Sendsanemailtotheaddressspecified,followedbythebody
oftheemailmessage.Theemailmessageisterminatedand
sentbyenteringa.orCtrlZonanemptyline.Cannotbe
configuredwithAceManager.
114
email=emailaddress
body=messagebody
20070914
*SMTPSTATUS?
ReturnsthestatusofthelastissuedSMTPmessage
(*SMTPSEND).Ifnostatusisavailable0isreturned.Once
read,thestatusisclearedout.Thestatuscodesreturnedcome
fromtheSMTPservertowhichthatthemodemsentthe
request.Unlessthereceivingserverisnotstandard,they
followtheRFCforSMTP.CannotbeusedwithAceManager.
Example:
354 = send in progress
250 = sent ok
*SMTPSUBJ=subject
AllowsconfigurationofthedefaultSubjecttouseifoneisnt
specifiedinthemessagebyprovidingaSubject:xxxlineas
theinitialmessageline.
subject=messagesubject
*SMTPUSER=user
TheemailaccountusernametoauthenticatewiththeSMTP
server(*SMTPADDR)forsendingemail.
user=username(maximum:40characters).
Note: Not required to use SMTP settings but may be required by your
cellular carrier.
Remarque :
Rev 3.0B Feb.08
115
Raven XT GPRS/EDGE
Other
Figure 1-12: AceManager : Other
DAE=n
ATEscapeSequencedetection.
n=0:Enable
n=1:Disable
*DATZ=n
EnablesordisablesresetonATZ.
n=0:NormalReset(Default).
n=1:DisableResetonATZ.
*IPPING=n
Settheperiodtoping(ifnovalidpacketshavebeenreceived)a
specifiedaddress(*IPPINGADDR)tokeepthemodemalive
(online).
n=0:Disablepinging(default)
n=15255minutes
Note: 15 minutes is the minimum interval which can be set for

Keepalive. If you set *IPPING for a value between 0 and 15, the
minimum value of 15 will be set.
116
20070914
*IPPINGADDR=[d.d.d.d][name]
SettheIPaddressorvalidinternetdomainnamefortheRaven
XTtopingtokeepitselfalive(online).*IPPINGmusttobeset
toavalueotherthan0toenablepinging.
d.d.d.d=IPaddress
name=domainname
*MSCIUPDADDR=name[/port]
ModemStatusUpdateAddresswhereName/Portisthe
domainnameandportofthemachinewherethemodem
statusupdateswillbesent.ThestatusparametersoftheRaven
XTaresentinanXMLformat.
name=domainname
port=port
*MSCIUPDPERIOD=n
ModemStatusUpdatePeriodwherendefinestheupdate
periodinseconds.
n=0:Disabled.
n=1255seconds
*NETWDOG=n
Networkconnectionwatchdog:Thenumberofminutestowait
foranetworkconnection.Ifnoconnectionisestablished
withinthesetnumberofminutes,theRavenXTmodemresets.
n=0:Disabled.
n=minutes:Default=120min.
*RESETCFG
Wipethenonvolatiledatainthemodem.Cannotbeusedwith
AceManager.
Caution: You may need to reactivate your modem if you erase the
non-volatile data.
*SNMPCOMMUNITY=string
TheSNMPCommunityStringactslikeapasswordtolimit
accesstothemodemsSNMPdata.
string=stringofnomorethan20characters(default=
public).
*SNMPPORT=n
ThiscontrolswhichporttheSNMPAgentlistenson.
Rev 3.0B Feb.08
117
Raven XT GPRS/EDGE
n=0:SNMPisdisabled.
n=165535
*SNMPSECLVL=n
SelectsthesecuritylevelrequirementsforSNMPcommunica
tions.
n=0:Nosecurityrequired.SNMPv2candSNMPv3
communicationsareallowed.
n=1:AuthenticationequivalenttoauthNoPrivsettingin
SNMPv3.SNMPv3isrequiredtodoauthentication,
SNMPv2ctransmissionswillbesilentlydiscarded.
n=2:Authenticationandencryption,equivalentto
authPrivsettinginSNMPv3.SNMPv3isrequiredtodo
authenticationandencryption,SNMPv2candSNMPv3
authNoPrivtransmissionswillbesilentlydiscarded.
Messagesarebothauthenticatedandencryptedtoprevent
ahackerfromviewingitscontents.
*SNMPTRAPDEST=host/[port]
ControlsdestinationforSNMPTrapmessages.Ifportis0or
hostisempty,trapsaredisabled.Trapsaresentoutaccording
totheSNMPsecuritylevel(i.e.ifthesecuritylevelis2,traps
willbeauthenticatedandencrypted).Currently,theonlytrap
thatcanbegeneratedislinkup.
host=IPaddress
port=TCPport
*SNTP=n
EnablesdailySNTPupdateofthesystemtime.
n=0:Off
n=1:On
*SNTPADDR=[d.d.d.d][name]
SNTPServerIPaddress,orfullyqualifieddomainname,to
useif*SNTP=1.Ifblank,time.nist.govisused.
d.d.d.d=IPaddress
name=domainname
*TELNETTIMEOUT=n
Telnetportinactivitytimeout.Bydefault,thisvalueissetto
closetheATtelnetconnectionifnodataisreceivedfor2
minutes.
118
n=minutes
20070914
*TPORT=n
SetsorqueriestheportusedfortheATTelnetserver.If0is
specified,theATTelnetserverwillbedisabled.Thedefault
valueis2332.
n=0:Disabled.
n=165535
Tip: Many networks have the ports below 1024 blocked. It is recommended to use a higher numbered port.
*TQUIT
Disconnectsthetelnetsession.NotavailableinAceManager..
Friends
FriendsModecanlimitaccesstotheRavenXTfromthe
cellularnetworkandtheInternet.Friendsmodeisabasic
firewall.
Caution: If you are using Friends Mode you will not be able to use
AceManager remotely or Telnet to the modem unless you are
contacting the modem from one of the configured IP addresses.
Note: Friends Mode will only prevent the Raven XT modem from
receiving data from those IP addresses not on the Friends List. It
cannot prevent data, such as pings, from traversing the network to the
modem which may billable traffic even though the modem does not
receive the data.
Figure 1-13: AceManager : Friends
Rev 3.0B Feb.08
119
Raven XT GPRS/EDGE
FM=n
FriendsModeOnlyallowspecifiedIPstoaccesstheRaven
XTmodem.
n=0:DisableFriendsmode
n=1:EnableFriendsmodeOnlypacketsfromfriendswill
beaccepted,packetsfromotherIPaddressesareignored.
Fn=[d.d.d.d]
FriendsmodeIPaddress.
n=09Friendslistindex
d.d.d.d=IPaddress
Using255intheIPaddresswillallowanynumber.
Example:166.129.2.255allowsaccessbyallIPsintherange
166.129.2.0166.129.2.255.
Tip: ATF? will return a list of all the current Fn settings.
Logging
Thisgroupincludescommandsspecifictotheinternallog.
Caution: Logging is intended for diagnostic purposes only. Extensive
use of logging features can cause degraded modem performance.
Figure 1-14: AceManager : Logging
*DBGCOMMLVL=n
SetthelogginglevelforthehostormoduleCOMport.
120
n=0:Nologging
n=1:HostCOMPort
n=2:ModuleCOMPort
20070914
*DBGIPLVL=n
SetsthelogginglevelfortheIPsubsystem.
n=0:Nologging
n=1:Logerrors(i.e.invalid/corruptpackets,etc.).
n=2:Logtheheaderofallreceivedpackets.Notethatthis
canquicklyexhaustavailablespacefortheeventlog.
n=3:Logtheheaderofallreceivedandsentpackets.Note
thatthiscanquicklyexhaustavailablespacefortheevent
log.
*DBGPPPLVL=n
SetsthelogginglevelforthePPPstack.
n=0:Nologging
n=1:Logclientevents(default)
n=2:Logserverevents
n=3:LogclientandServerevents
Telemetry/Addr List
Modbus,commonlyusedwithtelemetrydevices,allowsa
connectionviaserialporttothemodem.TelemetryandAddr
Listcommandsareonlyusedwhenthemodemisinoneofthe
Modbusstartupmodes.Further,TelemetryandtheAddrList
areavailablewithallRavenlinemodemswhichhaveaserial
port,suchastheRavenXandtheRavenXT.
Figure 1-15: AceManager : Telemetry
IPL=n
IPListDialallowsaccesstheModbusIPlistusingthefirsttwo
digitsofthedialstring.
Rev 3.0B Feb.08
121
Raven XT GPRS/EDGE
Example:ATDT1234567wouldgotoID12ontheModbus
listandusetheassociatedIPasthedestination.
n=0:Disabled
n=1:Enabled
MVLEN=n
ModbusVariantIDLength:LengthoftheRTUIDina
modbusvariantprotocol,inbytes.
n=1:Thisparameterisusedtodefinethelengthofthe
RTUIDinModbuslikeprotocoldatapackets.
n=2:ThisparameterisusedwhenthewhentheMDisset
tohex63.
MVMSK=hh
ModbusVariantIDMask:Bytehexmasktousewhen
extractingtheID.SpecifywhichbitsintheIDfieldtouse.This
parameterisusedwhenthewhentheModeDefault(MD)is
settohex63.
hh=hexvalue
00nomask,all8bits(default)
0Fonlytheloworder4bits
MVOFF=n
Modbus(variablemode)Offset:Indicatestheoffsetinthedata
ofwheretheModbusIDstarts.
n=0255
MVOPT=n
ModbusVariantOption:Setsvariousbehavioraloptionswhen
dealingwithaModbusvariantprotocol.Thisparameteris
usedwhenthewhenMDissettohex63.Cannotbeconfigured
inAceManager.
n=0:Nospecialaction(Default).
n=1:SkipleadingzeroesinModbuspackets.
MVTYP=n
ModbusVariantType:ThedatatypeoftheRTUIDina
modbusvariantprotocol.Thisparameterisusedtodefinethe
datatypeoftheRTUIDinModbuslikeprotocoldatapackets.
ThisparameterisusedwhenMDissetto63.
122
n=0:Binary(Default)
n=1:ASCIIHex
n=2:ASCIIDecimal
20070914
RKEY=n
Enable/disableMDSRadiotransceiverkeying.Radiokeyingis
designedtoassertCTSwhenapacketisreceived,delaythe
timeasspecified,sendthedataouttheserialport,waitthe
sameamounttime,dropCTS.Thisway,theCTSsignalcanbe
usedtokeyatransmitteronandgiveittimetoreachitspower
levelbeforedataissenttoit.DelayintervalisspecifiedinS221.
n=0:Off(Default).
n=1:On.
Addr List
Figure 1-16: AceManager : Addr List
MLISTandMLISTXareconfiguredbythefieldsavailablein
theAddrListgroup.AceManagerautomaticallydifferentiates
betweenthemtoenterthecorrectcommandforthemodem.
MLISTid=d.d.d.d
EntersanIDandIPaddressintotheModbusList.IDisa
decimalvalue(1to100).
id=ID
d.d.d.d=IPaddressorname
MLISTXhexid=d.d.d.d
EntersanIDandIPaddressintotheModbusList.IDisa
hexadecimalvalue(0to64).
Rev 3.0B Feb.08
hexid=ID
d.d.d.d=IPaddressorname
123
Raven XT GPRS/EDGE
Edge/HSDPA
ThisgroupincludescommandsspecifictoHSDPA,EDGEand
GPRS.Ifyouarenotconnectingtoamodemwhichuses
HSDPA,EDGE,orGPRS,youwillnotseethisgroupinthe
menu.
Figure 1-17: AceManager : EDGE/HSDPA
*NETAPN=apn
EasyentryoftheAPN.Ifleftblank,themodemwillattemptto
usethedefaultsubscribervalueasdefinedbytheaccount.
apn=accesspointname
+CGQMIN
MinimumAcceptableQualityofServiceProfile.Change
shouldbeatcarriersrequest.Normallynotrequiredtobe
changed.
+CGQREQ
SetQualityofServiceProfile.Changeshouldbeatcarriers
request.Normallynotrequiredtobechanged.
124
20070914
+COPS=mode,[format][,oper]
Manuallyspecifyanoperator.Referalsoto*NETOP.
Rev 3.0B Feb.08
mode=0:Automaticanyaffiliatedcarrier[default].
mode=1:Manualuseonlytheoperator<oper>specified.
mode=4:Manual/Automaticifmanualselectionfails,
goestoautomaticmode.
format=0:Alphanumeric(name)(G3x10mustusethis
format).
format=2:Numeric
oper=name
125
Raven XT GPRS/EDGE
126
20070914
B: Windows Dial-up Networking

(DUN)
Installing a modem
driver for Raven XT
Creating a Dial-Up
Networking (PPP)
Connection
Connecting to the
Internet Using DUN
DialupNetworking(DUN)allowsacomputerorotherdevice
tousetheserialportorUSBvirtualserialportonyourRaven
XTtoconnecttotheInternetorprivatenetworkusingPPPjust
likeananalogmodemusingastandardphoneline.
Caution: To install any driver on your computer, you may need to be
logged in as Administrator or have Administrator privileges for your
login.
MicrosoftWindowsXPisusedintheexamplesbelow.The
modemdriverinstallationandDUNsetupandconfiguration
issimilarinMicrosoftWindowsproducts.Examplesarenot
providedhereforinstallingthedriverorconfiguringDUNfor
anyotheroperatingsystem.
Installing a modem driver for

Raven XT
StandardinstallationsofMicrosoftWindowsXPand2000
includeagenericmodemdriverwhichwillworkwithyour
RavenXT.
1. Connect the Raven XT.

a. ConnectthemodemtothecomputerwithaDB9
cableortheUSBportinserialmode..
b. PlugintheACadapter,connecttheantenna(s)and
poweronthemodem.
2. Install the driver.

a. SelectStart>ControlPanel>PhoneandModemOptions
(inClassicView).
Rev 3.0B Feb.08
127
Windows Dial-up Networking (DUN)
Figure 2-1: Phone and Modem Options
b. SelecttheModemstab.
Figure 2-2: Phone and Modem Options: Modems
c.
Rev 3.0B Feb.08
SelectAdd.
128
Figure 2-3: Add Hardware Wizard
d. CheckDontdetectmymodem;Iwillselectitfromalist.
e. SelectNext.
Figure 2-4: Add Hardware Wizard: Install New Modem
f.
Select(StandardModemTypes)fromtheManufacturers
column.
g. SelectStandard33600bpsModemfromtheModels
column.
Rev 3.0B Feb.08
129
Tip: If you have the speed for your modem configured as something
other than the default, use the Standard Modem that matches the
speed you configured.
h. SelectNext.
Figure 2-5: Add Hardware Wizard: Select Ports
i.
CheckSelectedPorts
j.
SelecttheCOMportthemodemisconnectedto
(commonlyCOM1).
k. SelectNext.
Figure 2-6: Add Hardware Wizard: Finish
l.
Rev 3.0B Feb.08
Oncethemodemdriverisinstalled,selectFinish.
130
3. Configure the driver.

WhenyoureturntothePhoneandModemOptionswindow,you
shouldseethenewlyinstalledmodemattachedtothe
correctCOMport.
Figure 2-7: Phone and Modem Options: Modems
a. HighlightthemodemandselectProperties.
Figure 2-8: Modem Properties
Rev 3.0B Feb.08
131
b. SelecttheModemtab.
Figure 2-9: Modem Properties: Modem
c.
MaximumPortSpeedshouldbesetto115200
(default).
d. SelectOKtoexit.
e. SelectOKagaintoexitoutofthePhoneandModem
Options.
Creating a Dial-Up Networking

(PPP) Connection
Onceyouhavethedriverforthemodeminstalledonyour
computer,youcansetupandconfigureDialUpNetworking
(DUN)tousethemodemasyourconnectiontotheInternet
usingPPP.
Note: No other device or program can be using the same COM port
(serial port) configured for the modem driver.
Rev 3.0B Feb.08
132
Caution: If you have an existing LAN connection, installing DUN for

the modem may interfere with the LAN connection. It's recommended
to disconnect your LAN connection before using a PPP connection
with your Raven XT.
OncetheDUNconnectionisinitiated,bydefault,itwilltake
overasthedefaultroutefornetworkcommunicationand
specificallyforInternetaccess.Ifyouwantthetwoconnections
tocoexist,youwillneedtodeselectUsedefaultgatewayon
remotenetwork(describedlater)andusetheroutecommand
inWindowstosetuproutingthroughthemodemproperly.
Thisguidedoesnotprovideinformationontheroute
command.Youmayneedtoconsultwithyournetworkadmin
istratortoproperlyconfigurerouting.
1. Create a new network connection.

a. SelectStart>ConnectTo>ShowAllConnectionstoopen
theNetworkConnectionswindow.
Figure 2-10: Windows : Start menu
Rev 3.0B Feb.08
133
b. SelectCreateaNewConnectionunderNetworkTasksin
themenuareaontheleft.
Figure 2-11: Create New Connection
c.
SelectNexttostartinstallingandconfiguringtheDUN
connection.
Figure 2-12: New Connection Wizard
d. SelectConnecttotheInternet.
e. SelectNext.
Rev 3.0B Feb.08
134
Figure 2-13: New Connection: Type
f.
SelectSetupmyconnectionmanually.
g. SelectNext.
Figure 2-14: New Connection: How do you want to connect?
h. SelectConnectusingadialupmodem.
i.
SelectNext.
Figure 2-15: New Connection: Connect using...
j.
Optional:Ifyouhavemultiplemodemsinstalledon
yourcomputer,youmaybepromptedtoselectthe
modemtobeused.Ifyouonlyhaveonemodem
installed,thisoptionwillbeomitted.
k. CheckStandard33600bpsModem.
l.
Rev 3.0B Feb.08
SelectNext.
135
Figure 2-16: New Connection: Select Modem
m. Typeinanamefortheconnection,suchasSierra
WirelessAirLinkModem.
n. SelectNext.
Figure 2-17: New Connection: Connection Name
Tip: The name provided here will not effect the connection in any
way. It is only a label for the icon. It can be the name of your wireless
service provider (Provider), your modem (Raven XT), or any other
designation for the connection.
o. Typein10001asthephonenumberforthemodemto
dial.
p. SelectNext.
Figure 2-18: New Connection: Phone Number
q. Optional:Ifyouhavemultipleusersconfiguredfor
yourcomputer,youmaybepromptedforConnection
Availability.IfyouselectMyuseonly,theaccount
currentlyloggedonwillbetheonlyoneabletouse
thisDUNconnection.
r.
Rev 3.0B Feb.08
SelectNext.
136
Figure 2-19: New Connection: Permissions
GenerallythemodemtakescareoftheAccountInformation,
UsernameandPassword,fortheconnection,soyoucanleave
thefieldsblank(unlessotherwiseinstructedbySupport).
s.
Ifyouwanttoallowotherstousethesameloginfor
themodem,selectUsethisaccountnameandpassword....
t.
SelectNext.
Figure 2-20: New Connection: Connection Information
Caution: If you have a LAN connection to the Internet and select

Make this the default Internet Connection for the DUN configuration,
you will not be able to use the LAN to connect to the Internet and may
also affect the network connection on your computer to the rest of the
LAN. Select this option ONLY if the Raven XT will be your sole
network connection.
u. IfyouwanttoaddashortcutforthisDUNconnection
toyourdesktop,checkAddashortcut.
v.
Rev 3.0B Feb.08
SelectFinishtoexittheNetworkConnectionWizard.
137
Figure 2-21: New Connection: Finish
2. Configure the DUN connection

AfteryoucompletetheNewConnectionWizard,therearea
fewmorethingsyouwillwanttoconfigureintheconnection.
a. SelectProperties.
Figure 2-22: DUN Connection
b. UncheckUsedialingrules.
Rev 3.0B Feb.08
138
c.
CheckShowicon...whenconnected.
d. SelectConfigure,belowtheConnectusingline.
Figure 2-23: DUN Properties
e. Select115200astheMaximumspeed.
f.
CheckEnablehardwareflowcontrol.
g. Donotcheckanyotheroption.
h. SelectOK.
Rev 3.0B Feb.08
139
Figure 2-24: Modem Configuration
i.
Backatthemainpropertiesscreen,selectthe
Networkingtab.
Figure 2-25: Networking
j.
SelectSettings.
k. RemovethechecksfromallthreePPPsettings.
l.
Rev 3.0B Feb.08
SelectOK.
140
Figure 2-26: PPP Settings
m. Select(highlight)InternetProtocol(TCP/IP)andthen
selectProperties.
Tip: For most configurations, you will be obtaining the IP address and
the DNS server address automatically.
n. SelectAdvanced.
Figure 2-27: TCP/IP Properties
o. UncheckUseIPheadercompression.
p. CheckUsedefaultgatewayonremotenetwork.
q. SelectOK.
Rev 3.0B Feb.08
141
Figure 2-28: Advanced TCP/IP
Tip: You may want to check the Options tab and change the settings
for applications you might be using. The default options are generally
applicable for most uses.
Caution: Unless specifically directed to do so by Support or your

network administrator, you do not need to make any changes to the
options on the Security tab.
r.
SelectOKuntilyoureturntotheConnectwindow.
Connecting to the Internet

Using DUN
TherearetwomethodsyoucanusetoconnectwithRavenXT
totheInternetusingDUN,AceViewandtheWindowsDUN
connectiondirectly.
AceView
AceViewisasmallutilitywhichcanmaintainyourDUN
connectionandmonitortheconnectionofyourRavenXTto
Provider.IfyouhavenotalreadyinstalledAceViewyoucan
obtainthemostrecentversionfromtheSierraWirelessAirlink
website.
Note: The direct DUN
connection features of AceView
are not available in Windows 98
or Windows NT.
ThisguideassumesyouhaveadefaultinstallationofAceView.
1. Start AceView.
Start>AllPrograms>AirLinkCommunications>AceView
Rev 3.0B Feb.08
142
2. Enable the Connection.
Figure 2-29: AceView: Menu
a. RightclickontheAceViewwindowtoopenthemenu.
b. SelectConnectionSettings.
Figure 2-30: AceView: Connection Settings
c.
SelectAutoStartintheDUNsection.
d. SelectMaintainPersistentConnection.
Whenchecked,AceViewwillcontinuallychecktheDUN
connectiontoensureitisnotdown.Ifso,AceViewwill
attempttoconnectagain.
Tip: When using the DUN connection, make sure the IP Address is
set to the local IP address of the modem, 192.168.13.31 by default.
e. SelectOK.
f.
OK.
Windows DUN
YoucandirectlyusetheDialuplinkfortheDUNconnection.
Rev 3.0B Feb.08
143
1. Start the DUN session.

Start>ConnectTo>SierraWirelessAirlinkModem
Ifyounamedtheconnectiondifferently,usethenameofthe
PPPconnectionyoumadeearlier.
Figure 2-31: DUN Connection
Tip: Generally you will not need to enter a Username or Password. If

you do need to enter either, you can enter these parameters
beforehand using *NETUID and *NETPW.
2. Select Dial to connect to the modem

and the cellular network.
Note: The speed shown in the
connection is the speed between
the modem and your computer, it
is not the speed of the modems
connection to Provider or the
Internet.
Whenyoureconnected,aniconshouldappearinthesystem
trayshowingtheconnectionstatus.
Figure 2-32: Connection indicator
Rev 3.0B Feb.08
144
Caution: For DUN connections on a Windows Mobility or other nonpersonal computer, the DNS settings may not be configured with the
DUN connection. You may need to go into the network settings and
add DNS servers manually.
Rev 3.0B Feb.08
145

Raven XT UserGuide PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Raven XT UserGuide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Raven XT GPRS/EDGE

Safety and Hazards

Rev 3.0B Feb.08

Rev 3.0B Feb.08

Post: Sierra Wireless America

AirLink Communications documentation - CDPD, CDMA, and GPRS.

AirLink Communications documentation - CDMA, EV-DO, EDGE, and

Converted documentation from AirLink Communications documentation

Rev 3.0B Feb.08

Connecting to the your cellular provider Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Interface Port Pin-Outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Activating Raven XT on your cellular provider Network . . . . . . . . . . . . . . . .13

Configuring the APN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Rev 3.0B Feb.08

Hardware Installation of the Raven XT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Configuring your Raven XT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Universal Serial Bus (USB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Using the Virtual Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using the Virtual Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Data Communication and Host Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Rev 3.0B Feb.08

UDP Multicast Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Understanding Domain Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Using IP Manager with your Raven XT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuring Modbus/BSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Configuring the Raven XT at the Polling Host for Modbus on UDP . . . . . . . . . . . . . . . . . . . . 72

SNMP : Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . .80

Rev 3.0B Feb.08

SNMP MIB Definition Sample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Rev 3.0B Feb.08

Rev 3.0B Feb.08

Rev 3.0B Feb.08

Telemetry/Addr List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Windows Dial-up Networking (DUN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Rev 3.0B Feb.08

1: Introduction to the Raven XT

Figure 1-1: Sierra Wireless AirLink Raven XT

Rev 3.0B Feb.08

Introduction to the Raven XT

Figure 1-2: Powered by ALEOS

Rev 3.0B Feb.08

Introduction to the Raven XT

Figure 1-3: AceManager

Rev 3.0B Feb.08

Introduction to the Raven XT

Figure 1-4: AceNet

Figure 1-5: AceView

Rev 3.0B Feb.08

Introduction to the Raven XT

Rev 3.0B Feb.08

Introduction to the Raven XT

Figure 1-6: Modem Doctor

Modem Doctor USB

Rev 3.0B Feb.08

Introduction to the Raven XT

Figure 1-7: Modem Doctor: USB connection

Connecting to the your cellular

Figure 1-8: Connecting to the Internet

Rev 3.0B Feb.08

Introduction to the Raven XT

Note: The Raven XT does not provide advanced routing required by

Dynamic vs. Static IP Addresses

Figure 3-8: AceManager : Misc - NETUID, NETPW