You are on page 1of 141

Raven EDGE

User Guide

20070914 Rev 3.0B

Preface

Important Notice

Duetothenatureofwirelesscommunications,transmission andreceptionofdatacanneverbeguaranteed.Datamaybe delayed,corrupted(i.e.,haveerrors)orbetotallylost. Althoughsignificantdelaysorlossesofdataarerarewhen wirelessdevicessuchastheSierraWirelessAirLinkRavenare usedinanormalmannerwithawellconstructednetwork,the SierraWirelessAirLinkRavenshouldnotbeusedinsituations wherefailuretotransmitorreceivedatacouldresultin damageofanykindtotheuseroranyotherparty,including butnotlimitedtopersonalinjury,death,orlossofproperty. SierraWirelessacceptsnoresponsibilityfordamagesofany kindresultingfromdelaysorerrorsindatatransmittedor receivedusingtheSierraWirelessAirLinkRaven,orforfailure oftheSierraWirelessAirLinkRaventotransmitorreceive suchdata. DonotoperatetheSierraWirelessAirLinkRaveninareas whereblastingisinprogress,whereexplosiveatmospheres maybepresent,nearmedicalequipment,nearlifesupport equipment,oranyequipmentwhichmaybesusceptibletoany formofradiointerference.Insuchareas,theSierraWireless AirLinkRavenMUSTBEPOWEREDOFF.TheSierra WirelessAirLinkRavencantransmitsignalsthatcould interferewiththisequipment. DonotoperatetheSierraWirelessAirLinkRaveninany aircraft,whethertheaircraftisonthegroundorinflight.In aircraft,theSierraWirelessAirLinkRavenMUSTBE POWEREDOFF.Whenoperating,theSierraWirelessAirLink Ravencantransmitsignalsthatcouldinterferewithvarious onboardsystems.
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 may be used at this time.

Safety and Hazards

Thedriveroroperatorofanyvehicleshouldnotoperatethe SierraWirelessAirLinkRavenwhileincontrolofavehicle. Doingsowilldetractfromthedriveroroperatorscontroland operationofthatvehicle.Insomestatesandprovinces, operatingsuchcommunicationsdeviceswhileincontrolofa vehicleisanoffence.

Limitation of Liability

Theinformationinthismanualissubjecttochangewithout noticeanddoesnotrepresentacommitmentonthepartof SierraWireless.SIERRAWIRELESSANDITSAFFILIATES SPECIFICALLYDISCLAIMLIABILITYFORANYANDALL

Rev 3.0B Feb.08

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 Trademarks

2008SierraWireless.Allrightsreserved. AirCardandHeartoftheWirelessMachineareregistered trademarksofSierraWireless.Watcherisatrademarkof SierraWireless,registeredintheEuropeanCommunity. AirLinkandAceWarearetrademarksofSierraWireless. SierraWireless,theSierraWirelesslogo,theredwavedesign, andtheredtippedantennaaretrademarksofSierraWireless. WindowsisaregisteredtrademarkofMicrosoftCorporation. Othertrademarksarethepropertyoftherespectiveowners.

Rev 3.0B Feb.08

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 1.x 2.x Release date 2003-2005 Q2: 2005-Q2: 2007 in draft Changes AirLink Communications documentation - CDPD, CDMA, and GPRS. AirLink Communications documentation - CDMA, EV-DO, EDGE, and HSDPA. Converted documentation from AirLink Communications documentation format into Sierra Wireless documentation format. Phase II of the conversion completed. Raven modem line documentation is revised.

3.0

Rev 3.0B Feb.08

Contents
Introduction to the Raven . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
ALEOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 AceWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
AceManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Simplified Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Monitor and Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 AceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Network Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 AceView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Modem Doctor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Modem Doctor USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

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


Steps of a connection: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Dynamic vs. Static IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

EDGE Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
EDGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Consumption: (@12V DC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards/Approvals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 16 16 16 16 16 16 17 17 17

Activating Raven on your cellular provider Network . . . . . . . . . . . . . . . . . . . .18


Installating the SIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Cellular Account Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 18 18 18

Configuring the APN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Hardware Installation of the Raven . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25


Connecting to Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Connecting to a Computer or other Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Rev 3.0B Feb.08

Contents

Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Light Patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring your Raven . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32


Using AceManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Using Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Using a Terminal Application with AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Data Communication and Host Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43


Basic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Data Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Basic Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
AT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 PassThru Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Telnet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 UDP and UDP Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 TCP and TCP Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Hybrid Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Data Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Public and Private Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Internal DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Keepalive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Configuring Keepalive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Data usage using Keepalive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

IP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Reasons to contact the modem and/or the connected device: . . . . . . . . . . . . . . . . . . . . . . . . . 52

Understanding Domain Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


car54.mydomain.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 car54.mydomain.com.ca. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Dynamic Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Using IP Manager with your Raven . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55


Restrictions for Modem Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Data Usage for IP Manager Server Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Eairlink.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Understanding DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configuring DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 The PPP-Peer Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Rev 3.0B Feb.08

Contents

Configuring Modbus/BSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59


Modbus Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Telemetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Remote Terminal Unit (RTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Supervisory Control and Data Acquisition (SCADA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Programmable Logic Controller (PLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Modbus TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Raven Modbus on UDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring the Raven at the Polling Host for Modbus on UDP . . . . . . . . . . . . . . . . . . . . . . . 61 Configuring the Remote Ravens for Modbus with UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

SNMP : Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . .69


Management Information Base (MIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Listening Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Security Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Trap Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Community String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

SNMP MIB Definition Sample. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


Display Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Product ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Info (information). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
*DEVICEID? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 *ETHMAC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 *NETPHONE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 &V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Information Displayed in AceManager without AT Commands Listed . . . . . . . . . . . . . . . . . . . . . . . 80

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
*HOSTMODE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 *NETERR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 *NETIP?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 *NETOP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 *NETRSSI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 *NETSERV?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 *NETSTATE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 +ICCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 +RCIQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Information Displayed in AceManager without AT Commands Listed . . . . . . . . . . . . . . . . . . . . . . . 82 AT Commands Requiring PassThru mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 +CCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Rev 3.0B Feb.08

Contents

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Misc (Miscellaneous) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 +++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 A/ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 D[method][d.d.d.d][/ppppp] or D[method][@name][/ppppp] . . . . . . . . . . . . . . . . . . . . . . . . . . 84 DS=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Hn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 OPRG=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 S53=[method][d.d.d.d][/ppppp] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Vn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 &W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 *DATE=[mm/dd/yyyy],[hh:mm:ss]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 *DPORT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 *HOSTPAP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 *NETALLOWZEROIP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 *NETPW=pw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 *NETPHONE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 *NETUID=uid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 *STATICIP=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 *STATUSCHK=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 *MODEMHISPEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 *DNSn=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 *DNSUPDATE=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 *DNSUSER=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Dynamic IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 *DOMAIN=name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 *IPMANAGERn=[name][IP address]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 *IPMGRKEYn=key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 *IPMGRUPDATEn=m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 *MODEMNAME=name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 PPP/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 *DHCPSERVER=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 *HOSTAUTH=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 *HOSTNETMASK=n.n.n.n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 *HOSTPEERIP=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 *HOSTPRIVIP=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 *HOSTPRIVMODE=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 *HOSTPW=string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 *HOSTUID=string. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 PassThru . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 \APASSTHRU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 *CSX1=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 *PTINIT=string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 *PTREFRESH=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 *RESETPERIOD=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 *NETSMS2EMAIL=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Rev 3.0B Feb.08

Contents

*SMTPADDR=[d.d.d.d][name] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 *SMTPFROM=email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 *SMTPPW=pw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 *SMTPSEND=email[body] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 *SMTPSTATUS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 *SMTPSUBJ=subject. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 *SMTPUSER=user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 DAE=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 *DATZ=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 *IPPING=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 *IPPINGADDR=[d.d.d.d][name]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 *MSCIUPDADDR=name[/port] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 *MSCIUPDPERIOD=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 *NETWDOG=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 *RESETCFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 *SNMPCOMMUNITY=string. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 *SNMPPORT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 *SNMPSECLVL=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 *SNMPTRAPDEST=host/[port] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 *SNTP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 *SNTPADDR=[d.d.d.d][name] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 *TELNETTIMEOUT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 *TPORT=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 *TQUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Friends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FM=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Fn=[d.d.d.d] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
*DBGCOMMLVL=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . *DBGDHCPLVL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . *DBGETHLVL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . *DBGIPLVL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . *DBGPPPLVL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 102 102 102 102

Telemetry/Addr List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102


IPL=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 MVLEN=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 MVMSK=hh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 MVOFF=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 MVOPT=n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 MVTYP=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 RKEY=n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Addr List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 MLISTid=d.d.d.d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 MLISTXhexid=d.d.d.d. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Edge/HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
*NETAPN=apn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +CGQMIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +CGQREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +COPS=mode,[format][,oper] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 106 106 106

Rev 3.0B Feb.08

Contents

Circuit Switch Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108


Configuring Circuit-Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
AT Commands and the Command String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Common AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Raven LEDs in Circuit-Switched Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Step by Step Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110


Hardware Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Software Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

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


Installing a modem driver for Raven. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Creating a Dial-Up Networking (PPP) Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Connecting to the Internet Using DUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
AceView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Windows DUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Rev 3.0B Feb.08

1: Introduction to the Raven


ALEOS AceWare Connecting to the your cellular provider Network EDGE Communication
TheRavenisanintelligentwirelessgateway,poweredby ALEOS,andoptimalforprovidingprimaryorbackup networkconnectivityforanyhighreliability/highavailability applications. TheRavenistheperfectsolutionforanydevicewithan Ethernetconnectionthatrequirespervasiveconnectivity includingPCs,routers,networkequipmentandPOS/ATMsas wellascommercialautomationequipment.

Figure 1-1: Sierra Wireless AirLink Raven

ALEOS
ALEOS,theembeddedcoretechnologyoftheSierraWireless AirLinkproductssimplifiesinstallation,operationandmainte nanceofanysolution,andprovidesanalwayson,always awareintelligentconnectionformissioncriticalapplications. ALEOSenables: PersistentNetworkConnectivity OverTheAir(OTA)Upgrades WirelessOptimizedTCP/IP RealTimeNotification PacketLevelDiagnostics DeviceManagement&Control ProtocolSpoofing

Rev 3.0B Feb.08

Introduction to the Raven

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. AceManagergivesyouthepowertomonitorandcontrolyour SierraWirelessAirLinkcommunicationsplatformsinreal time.

Rev 3.0B Feb.08

Introduction to the Raven

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

Introduction to the Raven

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

10

Introduction to the Raven

Modem Doctor
ModemDoctorisatroubleshootinganddiagnosticsutility. ThisutilitywillallowyoutogetalogfileoftheRavenactivity whichyoucanthensendtoSierraWirelesssupport,erasethe currentconfigurationcompletely.

Rev 3.0B Feb.08

11

Introduction to the Raven

Figure 1-6: Modem Doctor

Modem Doctor USB


1. 2. OpentheModemDoctorUSB.exe. 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

12

Introduction to the Raven

Figure 1-7: Modem Doctor: USB connection

Connecting to the your cellular provider Network


TheRavenusesyourcellularproviderasanISP(Internet ServiceProvider)toconnectyoutotheInternet. Steps of a connection: 1. 2. WhenyourRavenispoweredon,itautomaticallysearches forcellularserviceusingEDGE. YourRavenestablishesaPPP(PointtoPointProtocolor dialupconnection)linktotheyourcellularprovider network,alsocalledregisteringonthenetwork,and receivesanIPaddress. WhenyourRavenhasreceiveditsIPaddressfromyour cellularprovider,aconnectiontotheInternetorthe cellularnetworkisalsoavailableforacomputerorother deviceconnecteddirectlytotheRaven.

3.

Cellular

Rev 3.0B Feb.08

13

Introduction to the Raven

Figure 1-8: Connecting to the Internet

TheRavenwillperformaonetooneroutingforallinternet traffictoandfromthecomputerorotherenddevice.Oneto onemeansthatyourRavenwillprovideaconnectionforone devicetotheInternetatatime.InPrivateMode,theRavenwill provideNAT(NetworkAddressTranslation)forthecomputer orotherenddevice.


Note: The Raven does not provide advanced routing required by oneto-many (several devices connected to one port). If you need to have more than one device connected to the Internet through your Raven, 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. YourRavenmightnotalwaysreceivethesameaddress eachtimeitconnectswithyourcellularprovider. Staticaddressesarepermanentlyassignedtoaparticular accountandwillalwaysbeusedwheneveryourRaven 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.

IfyouneedtocontactyourRaven,adeviceconnectedtothe Raven,orahostsystemusingtheRavenfromtheInternet,you needtohaveaknownIP(suchasonewhichisstatic)or domainname(anIPaddresswhichisconvertedbyaDNS serverintoawordbasedname).IfyouhaveadynamicIP

Rev 3.0B Feb.08

14

Introduction to the Raven

addressforyourmodem,youcanuseaDynamicDNSservice (suchasIPManager)totranslateyourIPaddressintotoa domainname.


Caution: If you want to connect remotely to your Raven 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 or special private network) 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,yourRavenwillfallbackto GPRSfortheconnectiontoyourcellularprovidertoprovide continuedconnectivity. GPRS GeneralPacketRadioService(GPRS)ispacketswitchedwith manyuserssharingthesametransmissionchannel,butonly transmittingwhentheyhavedatatosend.Thismeansthatthe totalavailablebandwidthcanbeimmediatelydedicatedto thoseuserswhoareactuallysendingatanygivenmoment, providinghigherutilizationwhereusersonlysendorreceive dataintermittently.GPRSprovidesspeedsof3070kbpswith burstsupto170kbps.

Rev 3.0B Feb.08

15

2: Specifications
Power Connector
Features and Benefits EmbeddedIntelligence LowPowerConsumption HighSpeed2wayData EthernetPort PersistentNetworkConnectivity RemoteManagementandConfiguration ClassIDiv2Certified

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 InputCurrent40mAto350mA InputVoltage928VDC

Standards/Approvals Carrierspecificapprovals FCC IndustryCanada ThisapparatusissuitableforuseinClassI,Division2, GroupsA,B,C,Dorunclassifiedornonhazardous locations.

Host Interfaces Ethernet:10BaseTRJ45

Rev 3.0B Feb.08

16

Specifications

AntennaConnection: Cellular50OhmTNC

Dimensions 76mmx25mmx129mm 317grams

Application Interfaces TCP/IP,UDP/IP,DHCP,HTTP,SNMP,SMTP,SMS,MSCI, andmore

LED Indicators Channel Link Registration RSSI Transmission/Receive Service Power

Power Connector
Power (red) Ground (black)
Figure 2-1: Power Connector (not to scale)

Rev 3.0B Feb.08

17

3: Activating Raven on your cellular provider Network


Installating the SIM Configuring the APN
Thischapterprovidesstepbystepdirectionsforactivating yourRavenontheyourcellularprovidercellularnetwork.

Installating the SIM


TheSIMintheRavenisasmartcardsecurelystoringthekey identifyingacellularsubscriber.Generally,youwillonlyneed toinstallaSIMonceinthelifeofthemodemanditmaybe preinstalledbyyourSierraWirelessRepresentative.

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 EthernetcableAnEthernetcable. PoweradapterandapowersourceYouwillneeda powersupplyandpowersourceforthemodem. PCorLaptopToconfigurethemodem,youwillneeda computerwithanavailableEthernetport.

Tools Required SmallPhillipsscrewdriverThePhillipsscrewdriveris theonewhichisalsocalledaplus(+)orXscrewdriver.

Rev 3.0B Feb.08

18

Activating Raven on your cellular provider Network

SlimstylusAPDAstylus,anunbentpaperclip,orother suchitem.

1. Opening the Case


a. UnplugtheRavenpowerandallcables. b. Usingasmallphillipsheadscrewdriver,removethe screwsonthebackoftheRaven. c. SlidethecaseoffoftheRavenandsetitaside.

Figure 3-1: Partially removed case

2.
a. CarefullyremovetheSIMcardfromthecardyougot fromyourcellularprovider.

3. Ejecting the SIM tray


Tip: The button is between two boards.

Figure 3-2: SIM tray button

Rev 3.0B Feb.08

19

Activating Raven on your cellular provider Network

4. Insert the SIM into the Tray


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. PlacetheSIMintothetrayandgentlypresstoclickit intoplace.

Figure 3-4: Empty SIM Tray and a Tray with a Sample SIM

5. Insert the Tray and SIM


a. Slidethetraybackintothemodem. b. Gentlypresstoclickitintoplace.
Tip: The top of the card faces the bottom of the modem.

Rev 3.0B Feb.08

20

Activating Raven on your cellular provider Network

Figure 3-5: Inserting the SIM

6. Finishing the SIM installation


a. SlidetheRavenbackintothecase. b. SecurethebackoftheRavenwiththescrews.

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.

1. Start AceManager
Start>AllPrograms>AirLinkCommunications>AceManager3G >AceManager3G

Rev 3.0B Feb.08

21

Activating Raven on your cellular provider Network

Figure 3-6: AceManager

2. Connect to the Modem


a. ClicktheConnectbutton.

b. SelectTCPorUDP. c. Entertheconnectioninformation. ForUDPorTCP,enter192.168.13.31astheIPaddress. d. Enterthepassword.Thedefaultpasswordwillbe enteredforyou. e. SelectOK.

3. Enter the APN


a. SelectEDGE/HSDPAfromthemenuontheleftsideof AceManager(underGroups)

Rev 3.0B Feb.08

22

Activating Raven on your cellular provider Network

Figure 3-7: AceManager : EDGE/HSDPA

b. TypeyourAPNintheNewValuefieldof*NETAPN.

Figure 3-8: AceManager : EDGE/HSDPA - *NETAPN

Optional:Ifyouneedtoconfigureyourmodemforacus tomAPN,afterenteringtheAPN,thereisadditionalinfor mationyouwillneedtoenter. 1. SelectMiscfromthemenuontheleftsideunder theCommongroup.

Figure 3-9: AceManager : Misc

2.

EntertheNAIintothenewvaluefieldfor *NETUIDandenteryournetworkpasswordinto thenewvaluefieldfor*NETPW.

Figure 3-10: AceManager : Misc - *NETUID, *NETPW

Rev 3.0B Feb.08

23

Activating Raven on your cellular provider Network

4. Write the Settings to the Raven


a. ClicktheWritebuttononthetoolbarofAceManager. b. WaitforthemessageWriteSuccessfultoappearin thestatusbar.

Figure 3-11: AceManager : Write

c.

ResettheRaven.

Rev 3.0B Feb.08

24

4: Hardware Installation of the Raven


Connecting to Power Connecting to a Computer or other Device Indicator Lights Mounting
YourRavenshouldbemountedinapositionthatallowseasy accessforthecablessotheyarenotbent,constricted,inclose proximitytohighamperage,orexposedtoextremetempera tures.TheLEDsonthefrontpanelshouldbevisibleforeaseof operationalverification.Youshouldensurethatthereis adequateairflowaroundthemodembutthatitiskeptfree fromdirectexposuretotheelements,suchassun,rain,dust, etc. Inamobilelocation,suchasacarortruck,ensurethelocation issecurebothagainstabruptmovementsofthevehicleand fromotheritemscomingintocontactwiththemodem.
Caution: The Raven 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 can withstand.

Power

Cellular

Ethernet

Figure 4-1: Raven Connectors

Rev 3.0B Feb.08

25

Hardware Installation of the Raven

Antennasselectedshouldnotexceedamaximumgainof5dBi understandardinstallationconfiguration.Inmorecomplex installations(suchasthoserequiringlonglengthsofcableand/ ormultipleconnections),itsimperativethattheinstaller followmaximumdBigainguidelinesinaccordancewiththe radiocommunicationsregulationsoftheFederalCommunica tionsCommission(FCC),Industry Canada, oryourcountrys regulatorybody(ifusedoutsidetheUS). RSS102(...HealthCanadasSafetyCode6forExposureof HumanstoRFFields) RSS129(800MHzDualModeCDMACellular Telephones)(Analogue&CDMA) RSS133r1(2GHzPersonalCommunications) http://www.industrycanada.ca.

YourRavenwillworkwithmostDualBandPCScellular antennaswithaTNCconnectorthatworksinthehighandlow frequenciesofthecellulartechnologyofyourmodem.Connect theprimaryantennaorprimaryRFcabledirectlytothe antennaconnectoronthebackoftheRaven.


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
YourRavencanbeusedwitheitherDC,availableinmost automobiles,or110AC,standardUSwallpower,withthe appropriatepoweradapter.DCcablesandACadaptersare availableasoptionalaccessoriesinadditiontotheone includedwithyourRaven.
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.

Rev 3.0B Feb.08

26

Hardware Installation of the Raven

Connecting to a Computer or other Device

Figure 4-2: Ethernet

TheEthernetportofyourRavencanbeconnecteddirectlytoa computerorotherEthernetdevicewitheitheracrossover cableorastraightthroughcable.TheEthernetportonthe Ravenisautosensingandconnectsat10baseT.Ifyouare connectingthemodemtoahuborswitchyoushouldusea straightthroughcableorusetheuplinkportonthehubor switchwithacrossovercable.


Tip: On some computers, the TCP receive window may be set to 16 kbytes. To optimize the throughput of your Raven, it is recommended that you change the TCP window to 128 kbytes to 256 kbytes using a TCP Optimizer.

Indicator Lights
WhenyourRavenisconnectedtopowerandanantenna,there isaspecificpatterntothelightstoindicateitsoperationmode.

Figure 4-3: Raven Indicator lights

Chan(channel)Indicatesthemodemhasacquireda networkchannel. LinkIndicatesasuccessfulconnectiontothecellular network. Reg(registration)IndicatestheRavenhasacquiredanIP fromyourcellularprovider.

Rev 3.0B Feb.08

27

Hardware Installation of the Raven

RSSI(signallevel)Lightshowsthestrengthofthesignal andmaybenearlysolid(strongsignal)orflashing(weaker signal).Aslowflashindicatesaveryweaksignal.

RSSI LED Ranges RSSI/Signal LED Status On Solid Fast Blink Normal blink Slow Blink Extinguished Ranges of RSSI (dBm) Equal to or stronger than -69 -70 to -79 -80 to -89 -90 to -99 Equal to or weaker than -100

TxRx(transmit/receive)Thelightwillflashasdatais transferredtoandfromtheRavenEmodemontheremote network. Srvc(service)IndicateswhentheconnectionisEDGE. UnlitindicatesGPRS. Pwr(power)Indicatesthepoweradapterisconnected andthereispowergettingtotheRaven. TheResetbuttonperformsthesamefunctionas unpluggingpowerfromthemodemandpluggingitback in.Resetwillnotalteranysavedconfigurationsettings.

Light Patterns TheLEDsonthefrontofthemodemwillrespondindifferent patternstoindicatemodemstates. NormalEachLED,mentionedabove,litasapplicable. StartupTheLEDswillcyclefromlefttoright. PassThrumodeTheChan,Reg,andLinkLEDswillblink intandem.TheTxandRxLEDswillblinkwhentrans mittingorreceivingdata.

Mounting
AnoptionalaccessoryforyourRavenisamountingkit,which includesabracket.Thebracketisdesignedtosnuglycradlethe modemandholditinplacewhereyouneedit.Youcanusea

Rev 3.0B Feb.08

28

Hardware Installation of the Raven

straparoundthebracketandmodemforextrasecurity.The bracketcanbeattachedtoastationarylocationusing#6screws withthemountingholediameterapproximately0.150.

Figure 4-4: Optional Mounting Bracket

Rev 3.0B Feb.08

29

Hardware Installation of the Raven

Figure 4-5: 100-170-1009 : Mounting Bracket for Raven

Rev 3.0B Feb.08

30

Hardware Installation of the Raven

Figure 4-6: 100-170-1006 : Mounting Bracket for Raven

Rev 3.0B Feb.08

31

5: Configuring your Raven


Using AceManager Using Templates Using a Terminal Application with AT Commands
WithALEOSasitsbrain,theRavenisahighlyconfigurable device,morethanjustadumbmodem. ToconfigureyourRaven,youhavetwooptions.Youcanuse theconfigurationandmanagementapplicationsofthe AceWaresuiteoryoucanuseaterminalemulatorapplication suchasHyperTerminal,PuTTY,ormanyothers. SincetheAceWareapplicationsaredesignedforeaseofuse, nearlyalldescriptionsandscreenshotsofRavenconfiguration inthisguideandApplicationNotesaredonewith AceManager.Inadditiontothevariouschaptersinthisguide givinginformationanddirectionsaboutusingthefeaturesof yourRaven,theConfigurationCommandsappendixbriefly describesallthecommandsavailable.Togetamoreexpanded viewoftheotherAceManagerfeatures,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

32

Configuring your Raven

Figure 5-1: AceManager

2. Connect to your Raven


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

33

Configuring your Raven

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

34

Configuring your Raven

4. Write the changes to the modem


a. ClicktheWritebuttononthetoolbarofAceManager. b. WaitforthemessageWriteSuccessfultoappearin thestatusbar.

Figure 5-5: AceManager : Write

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.

Removesettingswhicharespecifictoyourmaster modemorverifysettingsareapplicabletoallyour modems.

Rev 3.0B Feb.08

35

Configuring your Raven

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

36

Configuring your Raven

2. Applying a Template to one modem with AceManager


Youcanuseatemplateyoucreatedyourself,usingthesteps above,oratemplateprovidedbyyourAirLinkrepresentative orsomeoneinyourcompanywhohassetupamodem template.Thetemplateyouwishtoapplymustbesavedto yourharddrive. a. Loadthetemplate. 1. 2. Connecttothemodemyouwanttoconfigure usingAceManager. 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.

Figure 5-9: AceManager : Write

d. Resetthemodem.
Caution: Many of the configuration settings will not take effect until the modem has been reset.

Rev 3.0B Feb.08

37

Configuring your Raven

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. 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

38

Configuring your Raven

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

39

Configuring your Raven

Using a Terminal Application with AT Commands


YoucanaccessandconfigureyourRavenusingaterminal 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,suchasRavenor SierraWirelessAirLinkSolutions.Thenameandiconare onlyforyourownreferencesoyoucanfindthe 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 local.

b. SelectOK.

Rev 3.0B Feb.08

40

Configuring your Raven

2. Connect To
a. SelectTCP/IP(Winsock)forConnectUsing. b. Typein192.169.13.31forHostAddress. c. ChangethePortNumberto2332.

d. SelectOK.

3. Connected

Figure 5-14: HyperTerminal : TCP/IP connected

a. Ifyouarepromptedforapassword,enter12345.

Rev 3.0B Feb.08

41

Configuring your Raven

b. TypeATandpressEnter.Youshouldgetareplyof OKor0. c. Toseewhatyouaretypingasyoutypeit,youwill needtoturnontheechoandverbosemode.Type ATE1V1andpressEnter.

d. 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 commandwhichisrecognizedbytheRaven,itwill respondwithOK.Ifthecommandisnotrecognized,the responsewillbeERROR. Thosecommandsapplicableonlytocertainmodel numbersoftheRavenwillbenoted.

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

42

6: Data Communication and Host Modes


Basic Modes Data Communication
TheRavenplaysthepartofaHOSTwhenacomputeror anotherdeviceisconnecteddirectlytoitsportandroutesdata to/fromtheconnecteddevicetothecellularnetwork.
Caution: The Raven 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 to a router. The router would provide the multiple routing and the Raven would provide one-to-one for the router to the cellular network and the Internet.

Asthehost,theRavencanusedifferentcommunication modes: Basic Modes AT:TheRavenacceptsandrespondstostandardAT commands. PassThru:Directconnectiontointernalhardware(OEM Module)oftheRaven. Telnet:TheRavenautoanswersTCPconnectionstoallow terminalemulationusingeitheralocalEthernet connectionorremotelyusingthecellularconnection.

Tip: By default, the Raven 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. All serial modes are entered by use of a startup mode command.

Data Communication PublicandPrivateModes:ThemethodusedbytheRaven topassanIPaddresstoaconnecteddevice. Keepalive:HowtheRavenmaintainsitsconnectiontothe cellularnetwork.

Rev 3.0B Feb.08

43

Data Communication and Host Modes

Basic Modes
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). Forexample,possibleoutputtotheATcommandAT withcarriagereturn(assumingquietmodeisnoton)is: 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.

Rev 3.0B Feb.08

44

Data Communication and Host Modes

PassThru Mode
InPassThrumode,theRavendoesnotbehavenormally,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 RavenwhenitentersPassThruandotherPassThrusettings.

Figure 6-1: AceManager : PassThru

PassThruModeallowsonlyspecificATcommands.Some ALEOScommandswillbeunavailablewhentheRavenisin PassThrumode.Thecommandsusablealsodependheavilyon themodemmodelnumber(foundonthelabelonthetopof theRaven).


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.

Rev 3.0B Feb.08

45

Data Communication and Host Modes

Telnet Mode
InAceManageryoucanconfigureTelnetoperation.

Figure 6-2: AceManager : S0

IfyouneedtochangetheportforTelnet(forexample,you havethedefaultportblockedonyourfirewall),theoptionis ontheOthertab.Thedefaulttelnetportis2332.Youcanalso changetheTelnettimeout,iftheconnectionisidle,default2 minutes.

Figure 6-3: AceManager : Other - *TPORT, *TELNETTIMEOUT.

UDP and UDP Pad TCP and TCP Pad Hybrid Modes
AT Command Hybrid Mod (MD5) 3 2 1 0 Hybrid Mode2 (MD6) 3 2 1 1

MD S82 S0 *UDPLAST

Rev 3.0B Feb.08

46

Data Communication and Host Modes

Data Communication
Note: The Raven forwards messages to and from the cellular network for only ONE device per port. The Raven is a one-to-one gateway and does not have advanced routing features required to do one-tomany routing.

TheprimarypurposeoftheRavenistoforwarddatafroma singledeviceconnectedtooneoftheportstothecellular networkand,ultimately,undermostcircumstances,tothe Internetinaonetoonegatewayconfiguration. WhentheRavenobtainsitsIPaddressfromyourcellular provider,italsoobtainsthenetworkroutinginformation necessarytoforwardmessagestotheirrouterswhichcanthen forwardonfromthere.TheRaventhenactsasarouterforthe deviceconnectedtoit,forwardingtoorfromthecellular network.

Public and Private Mode


InPublicMode,theRavenwillpasstheIPaddressassignedby thecellularnetworktothedeviceconnectedtoitsport.Public ModeisthedefaultmodefortheRaven. Ifyouneedmorecontroloverwhichgatewayaddress,device address,andnetmaskthatisgivenoutbytheinternalDHCP server,youcanusetheprivatehostmode,*HOSTPRIVMODE, andsettheinternalnetworkIPaddresses.TheRavenwilluse NATtoforwardpacketstotheenddevice.
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 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

47

Data Communication and Host Modes

Figure 6-4: AceManager : PPP/Ethernet

*HOSTPRIVMODESetto1toenabletheexplicitIP addresses. *HOSTPRIVIPSettotheIPaddressyouwanttheRaven togivetoyourdevice. *HOSTPEERIPSettotheIPaddressyouwantforthe Raven. *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.

Internal DHCP Server DHCP(DynamicHostConfigurationProtocol)hasbecomea primarycomponentoftodaysnetworkenvironments.DHCP allowsoneservertoautomaticallyanddynamicallyallocate networkIPaddressesandothernetworkrelatedsettings(such assubnetmasks,routers,etc.)toeachcomputerordevice withouttheneedtosetupeachspecificallyorkeeptrackof whataddresseshavealreadybeenused. Inadefaultconfiguration,theRavenactsasaDHCPhostto anydeviceconnectedtoitsports,providingthatdevicewith anIPaddresswhichcanbeusedtocommunicateonthe Internet.InPublicMode,thatwillbetheIPaddressassigned bythecellularnetwork.InPrivateMode,thatwillbetheIP addressdefinedin*HOSTPRIVIP.

Rev 3.0B Feb.08

48

Data Communication and Host Modes

1.

WhentheRavenregistersonthecellularnetwork,itis assignedanIPaddressfromyourcellularprovider,lets sayA.B.C.D. ActingasaDHCPserver,inPublicMode,whentheRaven receivesaDHCPrequestfromanEthernetdevice,ithands offtheassignedaddresstothedeviceandsetsupthe defaultgatewayaddressasA.B.C.1.Ifthefourthoctetis alreadya1,itassignsA.B.C.2astherouteraddress. TheRavenalsosendsa/24netmask(255.255.255.0by default)andsetsupastaticroutewhichmaps 192.168.13.31(ortheaddressconfiguredwith *HOSTPEERIPifitischanged)toA.B.C.1(orA.B.C.2if thatwaswhatthegatewayaddresswasgivenas).

2.

3.

Tip: When PPPoE is used with the Raven, 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 to send all outgoing packets.

Keepalive
Keepaliveisusedtotesttheconnectiontothecellularnetwork bypinginganIPaddressafteraspecifiedperiodofinactivity. Keepaliveisonlyrecommendedforuserswhohavearemote terminatedmodemthatinfrequentlycommunicatestothe networkorifyouhaveexperiencedissuesovertimewherethe modemcannolongerbereachedremotely. WhenKeepalivepingstheIPaddress,anacknowledgement indicatesthereisanactiveconnectiontothenetwork.Ifthe RavendoesnotreceivearesponsefromtheIPaddress,itwill makeadditionalattemptsaccordingtoabackoffalgorithm beforedeterminingtheInternetconnectionisnotfunctioning properly.Ifitdeterminestheconnectionisnotfunctioning,the modemwillthenattempttoreconnecttoyourcellular providertoreestablishIPconnectivity. Configuring Keepalive InAceManager,theKeepalivesettingsarepartoftheOther group.

Rev 3.0B Feb.08

49

Data Communication and Host Modes

Figure 6-5: AceManager : Other

*IPPINGsetstheinterval,inminutes,youwantKeepalive totestthenetworkconnection.TodisableKeepalive,set *IPPINGto0(defaultsetting).

Note: 15 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

50

Data Communication and Host Modes

*IPPING 15 minutes 30 minutes 60 minutes 120 minutes

Estimated Usage 400k / month 200k / month 100k / month 50k / month

Rev 3.0B Feb.08

51

7: IP Manager
Understanding Domain Names Using IP Manager with your Raven 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,ifyouneedtocontactRavendirectly,adevice connectedtothemodem,orahostsystemusingyourRaven (alsocalledMobileTerminated),adynamicIPwontgiveyoua reliableaddresstocontact(sinceitmayhavechangedsincethe lasttimeitwasassigned). DomainnamesareoftenonlyconnectedtostaticIPaddresses becauseofthewaymostdomainname(DNS)serversareset up.DynamicDNSserversrequirenotificationofIPAddress changessotheycanupdatetheirDNSrecordsandlinka dynamicIPaddresstothecorrectname.

Rev 3.0B Feb.08

52

IP Manager

DynamicIPaddressesaregrantedonlywhenyourRaven isconnectedandcanchangeeachtimethemodemrecon nectstothenetwork. StaticIPaddressesaregrantedthesameaddressevery timeyourRavenisconnectedandarenotinusewhen yourmodemisnotconnected.

Sincemanycellularproviders,likewirebasedISPs,donot offerstaticIPaddressesorstaticaddressaccountscosta premiumvs.dynamicaccounts,SierraWirelessAirLink SolutionsdevelopedIPManagertoworkwithaDynamicDNS servertoreceivenotificationfromSierraWirelessAirLink modemstotranslatethemodemsdynamicIPaddresstoa fullyqualifieddomainname.Thus,youcancontactyour RavendirectlyfromtheInternetusingadomainname.

Understanding Domain Names


AdomainnameisanameofaserverordeviceontheInternet whichisassociatedwithanIPaddress.Similartohowthe streetaddressofyourhouseisonewaytocontactyouand yourphonenumberisanother,boththeIPaddressandthe domainnamecanbeusedtocontactaserverordeviceonthe Internet.Whilecontactingyouatyourhouseaddressorwith yourphonenumberemploydifferentmethods,usinga domainnameinsteadoftheIPaddressactuallyusesthesame method,justawordbasednameiscommonlyeasierto rememberformostpeoplethanastringofnumbers. Understandingthepartsofadomainnamecanhelptounder standhowIPManagerworksandwhatyouneedtobeableto configurethemodem.Afullyqualifieddomainname(FQDN) generallyhasseveralparts. 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

Rev 3.0B Feb.08

53

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. IfyourRavenisconfiguredforDynamicIP,whenitfirst connectstotheInternet,itsendsaIPchangenotificationtoIP Manager.IPMangerwillacknowledgethechangeandupdate theDynamicDNSserver.ThenewIPaddresswillthenbethe addressforyourmodemsconfiguredname. OnceyourmodemsIPaddresshasbeenupdatedinIP Manager,itcanbecontactedvianame.IftheIPaddressis needed,youcanusethedomainnametodeterminetheIP address.

Rev 3.0B Feb.08

54

IP Manager

Note: The fully qualified domain name of your Raven will be a subdomain of the domain used by the IP Manager server.

Using IP Manager with your Raven


ToallowyourSierraWirelessAirLinkmodemtobeaddressed byname,themodemneedstohaveaminimumofthree elementsconfigured.Youcanalsoconfigureaseconddynamic serverasabackup,secondary,oralternateserver. InAceManager,selectDynamicIP.

Figure 7-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.

*IPMGRUPDATE1and*IPMGRUPDATE2:Howoften, inminutes,youwanttheaddresssenttoIPManager.If thisissettozero,themodemwillonlysendanupdateif

Rev 3.0B Feb.08

55

IP Manager

theIPaddresschanges(example,ifyourRavenisresetor isassignedadifferentIPaddress). *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 30 60 500

16992 bytes 5664 bytes 2832 bytes 339.84 bytes

Eairlink.com
Asaservice,SierraWirelessmaintainsaIPManagerservers whichcanbeusedforanyAirLinkmodem.

Rev 3.0B Feb.08

56

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
TheRavenhastheabilitytoqueryDNSserversinorderto translatedomainnamesintoIPaddresses.Thisallowsyouto usedomainnamesinplaceofIPaddressesformostofthe configurationoptionsrequiringIPaddresses.Thisisimportant ifyourRavenwillneedtocontactanothermodemorother devicethathasadomainnamebutanunknownordynamicIP address(suchasanotherremoteRavenusingIPManager).

Configuring DNS
Generally,whenyourRavenreceivesitsIPaddressfrom Provideraspartoftheconnectionprocess,itwillalsoreceive theDNSserverstouseforresolving(ortranslating)namesto IPaddresseswhichitwillautomaticallyconfigureinthe modemsettings.UnlessyourRavenwillbeusedonanetwork withothermodemsordeviceswhichhavenamesinternalto thelocalnetworkorfrequentlychangingIPaddresses,the DNSserversprovidedbyProvidershouldbeallyouneed. IftheRavenwillbecommunicatingwithadevicethathasa domainnamebutchangesitsIPaddressfrequently(suchas anotherAirLinkmodemusingIPManager)orisonanetwork wheredevicesareaccessedbynamesratherthanIPaddresses, youwillwanttoputinanalternateDNS(*DNSUSER)where thatdomainisupdated,suchastheIPManagerserverthe remotemodemisusingorthelistingofIPaddressestonames iskept. IfyouneedtomanuallyconfigureDNS,inAceManager,select DNS.

Rev 3.0B Feb.08

57

IP Manager

Figure 7-2: AceManager: DNS

*DNS1and*DNS2TheprimaryandsecondaryDNS serverssetbyProviderwhenyourRavengetsitsIP address. *DNSUSERSetthis,ifdesired,toanadditionalDNS servertoqueryfirstbeforetheprimaryorsecondary(just asahostsfileisqueriedfirstonacomputer).If*DNSUSER issetto0.0.0.0,itwillbeignored. *DNSUPDATEThiscommandsetshowoftenyouwant DNSUpdatestoberequested.OtherwisetheRavenwill onlysendupdateswhenitisreset,poweredup,ortheIP addressisgrantedbynetworkchanges.

The PPP-Peer Domain Name


TheRavenusestheunqualifieddomainnameofppppeer whenitisinPPPorSLIPaddressmodetoresolvetheaddress ofthedeviceorcomputerconnectedviaPPPorSLIPaddress. IftheRavenisnotinPPPorSLIPaddressmode,ppppeer willresolveto0.0.0.0.

Rev 3.0B Feb.08

58

8: Configuring Modbus/BSAP
Configuring the Raven at the Polling Host for Modbus on UDP Configuring the Remote Ravens for Modbus with UDP
TheRavensupportsModbusASCII,ModbusRTU,BSAP,and canalsoemulateotherprotocolslikeDF1orothersusingits ModbusVariablefeature.

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

59

Raven 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,aRavenisconnectedtothecentralstation(host)and aRavenisconnectedtoeachremoteunit.WhentheRavenis configuredforModbuswithUDP,theRavenconnectedtothe hostcanstorealistofIPaddressesornameswithmatching IDs.Whenthehostatthecentralstationsendsserialdataasa pollrequest,theRavenatthehostmatchestheRTUIDtoa correspondingIPofaRavenataremoteunit.AUDPpacketis assembledencapsulatingtheRTUIDandserialdatatrans mittedfromthehost.TheUDPpacketisthentransmittedto thespecificRavenattheremoteunitmatchingtheRTUID.

60

20070914

Configuring Modbus/BSAP

TheremoteRaventhendisassemblesthepacketbeforetrans mittingtheRTUIDandserialdatatotheremoteunit.The remoteunitsoperateinnormalUDPmodeandtheirdatais senttothehostviatheremoteRavenandhostRaven.

Configuring the Raven at the Polling Host for Modbus on UDP


ThissectioncoversaPollingHostwithstandardModbus, variationsmayneedadditionalATcommands.

1. Configure the listening/device ports


InAceManager,selectMiscinthesidemenu.

Figure 8-1: AceManager: Misc

Thedestinationportforthemodematthehostneedstomatch thedeviceport(*DPORT)inuseonallthemodemsatthe remotesites.Forexample,iftheremotemodemsdeviceport (*DPORT)is12345,thentheModbushostmodemsS53 destinationportshouldbesetto12345. Takenoteof(orset)theDevicePortsettingin*DPORTto configurethedestinationportontheremotemodems.

Rev 3.0B Feb.08

61

Raven EDGE

2. Configure the default mode for start-up.


InAceManager,selectUDPinthesidemenu.Selecttheappro priateMDmodefromthedropdownmenu.

Figure 8-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 8-3: AceManager: Addr List.

62

20070914

Configuring Modbus/BSAP

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.

Figure 8-4: AceManager: Dynamic IP

WithnamesinsteadofIPaddressesfortheAddressList,the hostmodemwillquerytheDNSserverforthecurrentIP addressassignedtothespecificnameofaremotemodemto sendamessagecorrespondingtotheID. WhenyouusenamesinsteadofIPaddresses,toensureyour modemsareupdatedquicklywiththecorrectIPaddressesfor thenames,youwillwanttosettheDNSsettingsaswell.In AceManager,selectDNS.

Rev 3.0B Feb.08

63

Raven EDGE

Figure 8-5: AceManager: DNS

Configure*DNSUSERtothesameIPaddressastheIP Manager(*IPMANAGER1).IfyourmodemshavedynamicIP addressesandnotstatic(theIPaddresscanchangewhenitis poweredup),configure*DNSUPDATEtoalowintervalto allowfrequentupdates.

Configuring the Remote Ravens for Modbus with UDP


ThissectioncoversstandardModbussettingsfortheRavenat theremoteunit,variationsmayneedadditionalcommands.

1. Configure the ports


InAceManager,selectMiscinthesidemenu.

Figure 8-6: AceManager: Misc

64

20070914

Configuring Modbus/BSAP

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 8-7: AceManager: UDP

Rev 3.0B Feb.08

65

Raven 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.

Figure 8-8: AceManager: Dynamic IP

WhenyouusenamesinsteadofIPaddresses,toensureyour modemsareupdatedquicklywiththecorrectIPaddressesfor thenames,youwillwanttosettheDNSsettingsaswell.In AceManager,selectDNS.

66

20070914

Configuring Modbus/BSAP

Figure 8-9: AceManager: DNS

Configure*DNSUSERtothesameIPaddressastheIP Manager(*IPMANAGER1).IfyourmodemshavedynamicIP addressesandnotstatic(theIPaddresscanchangewhenitis poweredup),configure*DNSUPDATEtoalowintervalto allowfrequentupdates.

Rev 3.0B Feb.08

67

Raven EDGE

68

20070914

9: SNMP : Simple Network Management Protocol


SNMP Configuration SNMP MIB Definition Sample
TheSimpleNetworkManagementProtocol(SNMP)was designedtoallowremotemanagementandmonitoringofa varietyofdevicesfromacentrallocation.TheSNMP managementsystemisgenerallycomposedofagents(suchas yourRaven,arouter,aUPS,awebserver,afileserver,orother computerequipment)andaNetworkManagementStation (NMS)whichmonitorsalltheagentsonaspecificnetwork. Usingthemanagementinformationbase(MIB),anNMScan includereporting,networktopologymapping,toolstoallow trafficmonitoringandtrendanalysis,anddevicemonitoring. AuthenticationensuresSNMPmessagescomingfromthe agent,suchastheRaven,havenotbeenmodifiedandthe agentmaynotbequeriedbyunauthorizedusers.SNMPv3 usesaUserBasedSecurityModel(USM)toauthenticateand, ifdesiredorsupported,messageencryption.USMusesauser nameandpasswordspecifictoeachdevice. TheRavencanbeconfiguredasanSNMPagentandsupports SNMPv2candSNMPv3.

Management Information Base (MIB)


Themanagementinformationbase(MIB)isatypeofdatabase usedtocompiletheinformationfromthevariousSNMP agents.Reportsfromvariousagents,suchastheRaven,are sentasdatainformdesignedtobeparsedbytheNMSintoits MIB.Thedataishierarchicalwithentriesaddressedthrough objectidentifiers.

SNMP Traps
SNMPtrapsarealertsthatcanbesentfromthemanaged devicetotheNetworkManagementStationwhenanevent happens.YourRaveniscapableofsendingthelinkUptrap whenthenetworkconnectionbecomesavailable.

Rev 3.0B Feb.08

69

SNMP : Simple Network Management Protocol

SNMP Configuration
ToconfigureyourRaventoworkasanSNMPagent,youcan useeitherAceManager,oraterminalconnectiontoconfigure themodemusingATcommands.InAceManager,theSNMP commandsareallpartoftheOthergroupundertheCommon group. ThereareonlythreecommandstosetforSNMPintheRaven: thelisteningport,thesecuritylevel,andthetrapdestination.

Figure 9-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. 0Nosecurityrequired.SNMPv2candSMNPv3commu nicationsareallowed. 1Authenticationrequired.SNMPv3isrequiredtodo authenticationandSNMPv2ctransmissionswillbesilently discarded.AuthenticationisequivalenttotheauthNoPriv settinginSNMPv3. 2Authenticationrequiredandmessagesareencrypted. SNMPv3isrequiredtodoauthentication.SNMPv2cand SNMPv3authNoPrivtransmissionswillbesilently discarded.Authenticationandencryptionisequivalentto theauthPrivsettinginSNMPv3.

Rev 3.0B Feb.08

70

SNMP : Simple Network Management Protocol

User Name and Password


Theusernameisuser.Theusernamecannotbechanged.The RavenspasswordisusedastheSNMPpassword(defaultis 12345).
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.

TochangethepasswordintheRaven,selectModemfromthe topmenulineinAceManager.

Figure 9-2: AceManager : Change Password menu option

Thecurrentpasswordwillbepreentered.Asyoutypethe newpasswordandconfirmit,thecharactersyoutypewillbe obscuredbyx.Forthepassword,youcanusenumbers, letters,and/orpunctuation.

Figure 9-3: Change Password

Caution: The password is case sensitive. drowssaP is not the same as drowssap.

Rev 3.0B Feb.08

71

SNMP : Simple Network Management Protocol

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 MAX-ACCESS read-only STATUS current ::= { general 2 }

Rev 3.0B Feb.08

72

SNMP : Simple Network Management Protocol

electronicID OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { general 3 } modemType OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { general 4 } aleosSWVer OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { general 5 } aleosHWVer OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { general 6 } modemSWVer OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { general 7 } modemHWVer OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { general 8 } -- COMMON -date OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { common 1 } otaProgrammingEnable OBJECT-TYPE SYNTAX INTEGER { disabled(0), enabled(1) } MAX-ACCESS read-only

Rev 3.0B Feb.08

73

SNMP : Simple Network Management Protocol

STATUS current ::= { common 2 } devicePort OBJECT-TYPE SYNTAX INTEGER(0..65535) MAX-ACCESS read-only STATUS current ::= { common 3 } netUID OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { common 4 } netPW OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { common 5 } requestPAP OBJECT-TYPE SYNTAX no(0), yes(1) } MAX-ACCESS read-only STATUS current ::= { common 6 } destinationAddress OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { common 7 } destinationPort OBJECT-TYPE SYNTAX INTEGER(0..65535) MAX-ACCESS read-only STATUS current ::= { common 8 } serialPortSettings OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { common 9 } serialPortFlowControl OBJECT-TYPE SYNTAX INTEGER { INTEGER {

Rev 3.0B Feb.08

74

SNMP : Simple Network Management Protocol

none(0), hardware(2), software(4) } MAX-ACCESS read-only STATUS current ::= { common 10 } -- STATUS -ipAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current ::= { status 1 } netState OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { status 2 } netChannel OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current ::= { status 3 } rssi OBJECT-TYPE SYNTAX INTEGER(-125..-50) MAX-ACCESS read-only STATUS current ::= { status 4 } serialSent OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current ::= { status 5 } serialReceived OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current ::= { status 6 } hostMode OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { status 7 }

Rev 3.0B Feb.08

75

SNMP : Simple Network Management Protocol

powerMode OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { status 8 } fixObtained OBJECT-TYPE SYNTAX INTEGER { no(0), yes(1) } MAX-ACCESS read-only STATUS current ::= { gps 1 } satelliteCount OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current ::= { gps 2 } latitude OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { gps 3 } longitude OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current ::= { gps 4 } END

Display Responses
Thestringthatisdisplayedfortheseobjectsisthesame displayforthecorrespondingATCommand.
Object phoneNumber deviceID electronicID aleosSWVer AT Command *NETPHONE? *DEVICEID? I3 I1

Rev 3.0B Feb.08

76

SNMP : Simple Network Management Protocol

Object aleosHWVer modemSWVer modemHWVer date otaProgrammingEnable devicePort netUID netPW requestPAP destinationAddress destinationPort serialPortSettings serialPortFlowControl ipAddress netState netChannel rssi serialSent serialReceived hostMode powerMode fixObtained satelliteCount latitude longitude I1 I2 I2 *DATE? OPRG?

AT Command

*DPORT? *NETUID? *NETPW? *HOSTPAP? S53 S53 S23 \Q *NETIP? *NETSTATE? *NETCHAN? *NETRSSI? not applicable for Raven-E not applicable for Raven-E *HOSTMODE? *POWERMODE? PinPoint line modems only PinPoint line modems only PinPoint line modems only PinPoint line modems only PinPoint line modems only

Product ID
EachmodemtypehasauniqueIDassociatedwithitsoyou canmoreeasilyidentifythemodemfromitstypeonyour network.

Rev 3.0B Feb.08

77

A: Configuration Commands
Info (information) Status Common Logging Telemetry/Addr List Edge/HSDPA
Theconfigurationcommands(ATcommands)inthischapter arearrangedaccordingtotheirplacementinAceManager. ThecommandsavailableinAceManagerwilldependofthe modelnumberofyourRavenand,insomecases,theversion oftheALEOSfirmwareinstalled.
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 is configured to use DNS. DNS settings frequently come directly from your cellular provider while your Raven is registering on the cellular network and receiving its IP address.

Info (information)
ThecommandsintheInfogrouphavereadonlyparam eters.Theyonlyprovideinformationaboutthemodem.Some oftheinformationdisplayedinthisgroupdoesnotcorrespond directlytoATcommands.

Rev 3.0B Feb.08

78

Raven EDGE

Figure 1-1: AceManager : Info

*DEVICEID? The64bitdeviceIDthemodemusestoidentifyitselftothe cellularnetwork. *ETHMAC? TheMACaddressoftheEthernetport. *NETPHONE? Themodemsphonenumber,ifapplicableorobtainable. &V Viewactiveprofile,thecontentsoftheactiveregisters.Not displayedwithAceManager. In n=0:Productname(forexample,Raven). n=1:TheRavensfirmware(ALEOS)version,hardwareID, andcopyright. n=2:Theinternalhardwaresfirmwareversionand relevanthardwareID. n=3:Thehardwaremodulesuniqueidentificationnumber orserialnumber. n=5:Viewactiveprofile(thecontentsoftheactive registers).NotdisplayedwithAceManager.

79

20070914

Configuration Commands

Information Displayed in AceManager without AT Commands Listed


VersionsofALEOS,internalhardware,boot,andMSCI: Versionsofinternallyconfiguredhardwareandsoftware.

Status
MostofthecommandsintheStatusgrouphavereadonly parametersandprovideinformationaboutthemodem.The StatusGrouphasmorefieldsthatcanbedisplayedonmost screens.Youcaneitherresizeyourwindoworusethescroll baronthesidetodisplaytheremainder.

Figure 1-2: AceManager : Status

*HOSTMODE? Thecurrenthostmode(AT,PPP,UDP,etc.).IftheRavenisnot inATmode,telnetintothemodemtoexecutethiscommand. *NETERR? TheEDGEorGPRSnetworkbiterrorrate. *NETIP?


Note: If there is no current network IP address, 0.0.0.0 may be displayed.

ThecurrentIPaddressofthemodemreportedbytheinternal module,generallyobtainedfromyourcellularprovider.This istheaddresscancontacttheRavenfromtheInternet.

Rev 3.0B Feb.08

80

Raven EDGE

Tip: Use *NETALLOWZEROIP if you need to allow the display of an IP ending in a zero.

*NETOP? Thecurrentcellularcarrierfromthemodemsfirmware version,forexample,yourcellularprovider. *NETRSSI? ThecurrentRSSI(ReceiveSignalStrengthIndicator)ofthe RavenasanegativedBmvalue.


Tip: The same information is displayed with the command S202?.

*NETSERV? Thetypeofservicebeingusedbythemodem,forexample Tech. *NETSTATE? Thecurrentnetworkstate: ConnectingToNetwork:TheRavenisintheprocessof tryingtoconnecttothecellularnetwork. NetworkAuthenticationFail:Authenticationtothe cellularnetworkhasfailed.Verifysettingstoactivatethe Raven. DataConnectionFailed:TheRavenfailedtoconnect,and itisnowwaitingasettimeintervalbeforeitattemptsto reconnect.VerifysettingstoactivatetheRaven. NetworkNegotiationFail:Networkconnectionnegoti ationfailed.Thisisusuallytemporaryandoftenclearsup duringasubsequentattempt. NetworkReady:TheRavenisconnectedtothe1xcellular networkandreadytosenddata. NetworkDormant:TheRavenisconnectedtothe1x cellularnetwork,butthelinkisdormant.Itwillbewoken upwhendataissentorreceived. NoService:Thereisnocellularnetworkdetected. HardwareReset:Theinternalmoduleisbeingreset.This isatemporarystate.

+ICCID SubscriberIdentityModuleID..

81

20070914

Configuration Commands

+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

82

Raven 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.IftheRavenisinadatamode(anymode otherthanPassThru),thiscommandcausesthemodemtore enterATcommandmode.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.

83

20070914

Configuration Commands

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
ATD - Dial (establish) default connection. ATDP192.168.13.31/2332 - Dial (establish) UDP session to 192.168.13.31, at port 2332.

Examples:

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. CannotbeconfiguredinAceManager. Hn HangUpCommand. n=1:Hangup

Rev 3.0B Feb.08

84

Raven EDGE

WithanATtelnetconnection,thiscommandwillterminatethe hostdatamodeandreturntheRaventoanATmode.Cannot beaccessedinAceManager. O Online(Remote):CausestheRaventogofromCommandState todatastate.CannotbeconfiguredinAceManager. OPRG=n Enables/disablesovertheairfirmwareupgradingofthe Raven.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


ATS53=T192.168.100.23/12345 ATS53=foo.earlink.com

Examples:

TelnettothespecifiedIPatport12345.
ATS53=192.168.100.23/12345

QuerythespecifiedIPatport12345.
ATS53=/12345

Queryport12345. Vn CommandResponseMode. Z ResettheRaven.InAceManager,thiscommandisperformed withtheResetoptiononthetoolbar.


Tip: *DATZ=1 will disable Z.

n=0:Terse(numeric)commandresponses n=1:Verbosecommandresponses(Default).

85

20070914

Configuration Commands

&W Writesallchangedmodemsettings.Ifthiscommandisnot issued,anymodifiedvalueswillrevertbacktotheirprevious valuesatmodemreset.CannotbeconfiguredinAceManager. *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.

Rev 3.0B Feb.08

86

Raven EDGE

*NETUID=uid Theloginthatisusedtologintothecellularnetwork,when required. uid=userid(upto64bytes)

*STATICIP=d.d.d.d SetthestaticIPrequiredtobereceivedfromthenetwork.Ifthe modemdoesnotgetthisIPaddressfromthenetwork,itwill resettheinternalhardwareandtryagain.Thedefaultis0.0.0.0, whichallowsanyIPaddressfromthenetwork. d.d.d.d=IPaddress


AT*STATICIP=192.168.1.23

Example:

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.

*MODEMHISPEED Settheinternalseriallinkspeedtotheinternal(radio)module. n=0:115200(default) n=1:230400

DNS
Thisgroupincludescommandsspecifictothemodembeing abletousedomainnamesinsteadofIPaddressesforother configurationoptions.

87

20070914

Configuration Commands

Figure 1-4: 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. n=0:DNSupdatesdisabled(Default). n=1:DNSupdatesenabled.

*DNSUSER=d.d.d.d SetsauserprovidedDNStoqueryfirstwhenperforming nameresolutionsinthemodem. d.d.d.d=IPaddressofdomainserver

Dynamic IP
ThisgroupincludescommandsspecifictodynamicDNS. DynamicDNSallowstheRaventouseadynamicIPaddress account,withanIPaddressthatcanchangeeachtimeyou connect,andstillallowyoutouseafullyqualifieddomain nametocontacttheRavenusingIPManagerrunningona serverwithadynamicDNSupdater.

Rev 3.0B Feb.08

88

Raven EDGE

Figure 1-5: AceManager : Dynamic IP

*DOMAIN=name Domain(ordomainzone)ofwhichtheRavenisapart.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.

*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. n=1:FirstIPManagerserver.

89

20070914

Configuration Commands

n=2:SecondIPManagerserver. key=128bitkeyinhexadecimal[32hexcharacters]

*IPMGRUPDATEn=m SetsthenumberofminutestoperiodicallysendanIPupdate notificationtothecorrespondingserver.Thiswilloccurevenif theIPaddressoftheRavendoesntchange.*IPMGRUPDATE1 isusedtosettherefreshrateto*IPMANAGER1,while *IPMGRUPDATE2isusedwith*IPMANAGER2.Ifthevalueis setto0,thenperiodicupdateswillnotbeissued(i.e.IPchange notificationswillonlybesentwhentheIPactuallychanges). n=1:FirstIPManagerserver. n=2:SecondIPManagerserver. m=0,5255:Numberofminutestosendanupdate.

*MODEMNAME=name NameoftheRaven(upto20characterslong)tousewhen performingIPaddresschangenotificationstoIPManager.The valuein*DOMAINprovidesthedomainzonetoaddtothis name. name=modemname(forexample,mymodem) Example:if*MODEMNAME=mymodemand *DOMAIN=eairlink.com,thenthemodemsfullyqualified domainnameismymodem.eairlink.com. 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 EthernetconnectionsbetweentheRavenandaconnected device.

Rev 3.0B Feb.08

90

Raven EDGE

Figure 1-6: AceManager : PPP/Ethernet

*DHCPSERVER=n ActasaDHCPserverforanyEthernetdeviceconnecting totheRaven.DHCP(DynamicHostConfiguration Protocol)allowsonedevice,theDHCPserver,toprovide dynamicIPaddressestoanyotherdevicewhichrequests them. n=1:Enabled.ThemodemwillactastheprimaryDHCP serverforthenetwork. n=2:EnabledifnootherDHCPserverisdetected (default).IfanotherDHCPserverisdetectedonthe network,theRavenwillnotsendoutrepliestoDHCP requests.n=0:Disabled.TheRavenXwillnotsendout repliestoDHCPrequests.

Tip: For PPPoE, set *DHCPSERVER=0.

*HOSTAUTH=n HostAuthenticationMode:UsePAPorCHAPtorequestthe userloginandpasswordduringPPPorCHAPnegotiationon thehostconnection.Theusernameandpasswordsetin *HOSTUIDand*HOSTPWwillbeused. n=0:DisablePAPorCHAPrequest(Default). n=1:PAPandCHAP. n=2:CHAP

Tip: For PPPoE, set *HOSTAUTH=1 or *HOSTAUTH=2.

91

20070914

Configuration Commands

*HOSTNETMASK=n.n.n.n Subnetmaskforthehostinterface.Allowscommunication withasubnetbehindthehostinterface. n.n.n.n=subnetmask,example255.255.255.0.

*HOSTPEERIP=d.d.d.d SetorquerytheIPaddressthatcanbeusedtodirectlycontact theRavenonceacellularconnectionisestablished.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 HostPasswordforPAP,CHAP,orPPPoE. string=password

*HOSTUID=string HostUserIDforPAP,CHAP,orPPPoE. string=userid(upto64bytes)

Rev 3.0B Feb.08

92

Raven EDGE

PassThru
PassThruModeisusedtocommunicatedirectlytotheRaven internalhardware.
Caution: While the modem is in PassThru mode, ALEOS is disabled. If you need to connect to the Raven 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-7: AceManager : PassThru

\APASSTHRU
Note: This mode is not available through the remote AT telnet server. You will need to connect to the Raven 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. n=0:Datawillbepassedtothehost. 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.

93

20070914

Configuration Commands

*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.TheRavencansend messagesusingSMTPifithasbeenconfiguredtouseamail server.


Note: You cannot send an Email with your Raven unless the Email server you have configured allows your Raven as a relay host. Talk to your network administrator to ensure you can send email through the email server using your Raven.

SMS(ShortMessageService)isanotherwaytosendmessages viathecellularnetwork.MostSMScommandsrequirethe modemtobeinPassThrumode.


Note: SMS may not be supported by your account with your cellular carrier.

Rev 3.0B Feb.08

94

Raven EDGE

Figure 1-8: 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. email=emailaddress body=messagebody

95

20070914

Configuration Commands

*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

96

Raven EDGE

Other

Figure 1-9: 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.

97

20070914

Configuration Commands

*IPPINGADDR=[d.d.d.d][name] SettheIPaddressorvalidinternetdomainnamefortheRaven topingtokeepitselfalive(online).*IPPINGmusttobesettoa valueotherthan0toenablepinging. d.d.d.d=IPaddress name=domainname

*MSCIUPDADDR=name[/port] ModemStatusUpdateAddresswhereName/Portisthe domainnameandportofthemachinewherethemodem statusupdateswillbesent.ThestatusparametersoftheRaven aresentinanXMLformat. name=domainname port=port

*MSCIUPDPERIOD=n ModemStatusUpdatePeriodwherendefinestheupdate periodinseconds. n=0:Disabled. n=1255seconds

*NETWDOG=n Networkconnectionwatchdog:Thenumberofminutestowait foranetworkconnection.Ifnoconnectionisestablished withinthesetnumberofminutes,theRavenmodemresets. 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

98

Raven 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. n=minutes

99

20070914

Configuration Commands

*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
FriendsModecanlimitaccesstotheRavenfromthecellular networkandtheInternet.Friendsmodeisabasicfirewall.
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 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-10: AceManager : Friends

Rev 3.0B Feb.08

100

Raven EDGE

FM=n FriendsModeOnlyallowspecifiedIPstoaccesstheRaven modem. 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-11: AceManager : Logging

*DBGCOMMLVL=n SetthelogginglevelforthehostormoduleCOMport. n=0:Nologging n=1:HostCOMPort n=2:ModuleCOMPort

101

20070914

Configuration Commands

*DBGDHCPLVL=n EnableordisableinternalDHCPlogging. n=0:Nologging n=1:LogDHCPevents.

*DBGETHLVL=n SetsthelogginglevelfortheEthernetport. n=0:Nologging n=1:Logerrors:invalid/corruptpackets,etc. n=2:Logtheheaderofallreceivedpackets.Notethatthis canquicklyexhaustavailablespacefortheeventlog.

*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.

Rev 3.0B Feb.08

102

Raven EDGE

Figure 1-12: AceManager : Telemetry

IPL=n IPListDialallowsaccesstheModbusIPlistusingthefirsttwo digitsofthedialstring. 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

103

20070914

Configuration Commands

MVOPT=n ModbusVariantOption:Setsvariousbehavioraloptionswhen dealingwithaModbusvariantprotocol.Thisparameteris usedwhenthewhenMDissettohex63.Cannotbeconfigured inAceManager. n=0:Nospecialaction(Default). n=1:SkipleadingzeroesinModbuspackets.

MVTYP=n ModbusVariantType:ThedatatypeoftheRTUIDina modbusvariantprotocol.Thisparameterisusedtodefinethe datatypeoftheRTUIDinModbuslikeprotocoldatapackets. ThisparameterisusedwhenMDissetto63. n=0:Binary(Default) n=1:ASCIIHex n=2:ASCIIDecimal

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-13: AceManager : Addr List

Rev 3.0B Feb.08

104

Raven EDGE

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). hexid=ID d.d.d.d=IPaddressorname

Edge/HSDPA
ThisgroupincludescommandsspecifictoHSDPA,EDGEand GPRS.Ifyouarenotconnectingtoamodemwhichuses HSDPA,EDGE,orGPRS,youwillnotseethisgroupinthe menu.

105

20070914

Configuration Commands

Figure 1-14: AceManager : EDGE/HSDPA

*NETAPN=apn EasyentryoftheAPN.Ifleftblank,themodemwillattemptto usethedefaultsubscribervalueasdefinedbytheaccount. apn=accesspointname

+CGQMIN MinimumAcceptableQualityofServiceProfile.Change shouldbeatcarriersrequest.Normallynotrequiredtobe changed. +CGQREQ SetQualityofServiceProfile.Changeshouldbeatcarriers request.Normallynotrequiredtobechanged. +COPS=mode,[format][,oper] Manuallyspecifyanoperator.Referalsoto*NETOP. 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

Rev 3.0B Feb.08

106

Raven EDGE

107

20070914

B: Circuit Switch Communications B


Step by Step Configuration Step by Step Configuration
CircuitswitchcommunicationrequirestheRaventobein PassThrumode,communicatingdirectlywiththeinternal hardware. PassThrumodedisablestheuseofALEOSinthemodem.Any featuresavailableusingALEOSarenotusablewhenthe modemisinPassThrumode.InPassThrumode,thesettings availablearethoseoftheinternalhardware.TheRavenin PassThrumodecannot. Thebestmachinesforuseincircuitswitchedmodeareones thatcanprovidetheirownINITorsetupstringsand/orissue ATcommands.Forcustomerswhohaveunintelligent machineswhostillneedtohavethemodemreadytobehave inacertainway(suchasAutoAnsweringcircuitswitched datacalls),thereisafeatureinthemodemcalledtheINIT STATE.

Note: When the Raven is used for circuit switch, the circuit switch configuration will disable all ALEOS features except for serial port communication.

Configuring Circuit-Switch
TheRavenneedstobeconfiguredtoenterintoPassThruafter startup.YoucanuseAceManager(preferred)ordirectserial communicationtoconfiguretheRaventoworkinPassThru modeandforcircuitswitchedcommunications.IntheUDP group,selecttheMDcommandandchoose07PassThru.

Figure 2-1: AceManager : UDP > MD

Rev 3.0B Feb.08

108

Raven EDGE

TheRavenneedsacommandstringsenttothemodemafterit isinitialized.Thecommandstringwillneedtobetailoredfor yourapplication.DifferentmodelsoftheRavenmayrespond differentlytosomeofthecommands.InthePassThrugroup, typeyourcommandstringintheinputfieldfor*PTINIT.

Figure 2-2: AceManager: PassThru

AT Commands and the Command String


Eachmodemrequiresacommandstringthatisacombination ofATcommandslimitedtoamaximumof40characters.The commandstringwillvarydependingontheneedsofthe connecteddevice.Forexample,somedevicesneedDTRtobe highwhileothersneedDTRtobeignored.Forafulllistingas wellasparametersanddefaults,refertheATCommand appendix.
Caution: The only commands that can be used in the string are those which do not require ALEOS. All AT Commands beginning with an * (asterix) require ALEOS.

Common AT Commands EEcho QQuietMode &CDCDControl &DDTROptions &SDSROptions S0Autoanswermode S7WaitforCarrier S8CommaPauseTime S9CarrierDetectResponseTime

109

20070914

Circuit Switch Communications

Raven LEDs in Circuit-Switched Mode


WhentheRavenisinCircuitSwitchedmode,theLEDsonthe frontwillbehavedifferently.TheChan,Link,andRegLEDswill flashintandem,likewithPassThrumode,whileallother LEDs(exceptforPower)willbeoff.

Step by Step Configuration


Foryourconvenience,thesedirectionsusepreconfigured template.

1. Gather the required hardware and software


Hardware Required ApersonalcomputerwithafunctioningserialportorUSB portandaUSBtoserialconverterconfiguredtoworkwith yourcomputer. AstraightthroughRS232cable(DB9MDB9F). AsuitablepowersupplyandantennafortheRaven. Withoutsuitablesignalstrengththemodemwillnot function.Betterthanatleast100dBMisrequired.

Software Required ModemDoctorUtilitytoconductdiagnosticsandto bringyourmodemtoabaselevelofconfiguration.You candownloadModemDoctorfromtheSierraWireless AirLinkSolutionswebsite:http://www.airlink.com.This utilitydoesnotneedtobeinstalled;itisrundirectly. Rememberwhereyoudownloadeditto,soyoucanrunit aspartoftheinstructionsbelow. AceManagerGraphicalinterfaceforenteringmostAT Commands.YoucandownloadAceManagerfromthe SierraWirelessAirLinkSolutionswebsite:http:// www.airlink.com/.Adefaultinstallationofthisutilityis assumedlaterinthesedirections. RavenTemplatesforCircuitSwitchThesetemplatesare providedbyyourSierraWirelessAirLinkSolutionsrepre sentativeandhavea.xmlextension.Youcanalso downloadtheappropriatetemplatefrom:http:// www.airlink.com/docs/AppNotes/CircuitSwitchTem plates/.Youshouldonlydownloadthetemplatewhich matchesyourmodemmodeland/orconfigurationneeds.

Rev 3.0B Feb.08

110

Raven EDGE

2. Connect the modem to your computer


UsingtheRS232cable,connectthemodemtothecomputer andapplypowertothemodem.

3. Erase the internal memory


TheRavenshouldhavetheinternalmemoryerasedtobring themodemtoaknownstartingpointwithoutanyconfigu rationoraccountprogramming. a. StartModemDoctor. b. SelectErasethemodemsnonvolatiledata.

Figure 2-3: Modem Doctor

c.

SelectSerialfromtheInterfaceoptionsandselectthe PortonyourcomputertowhichtheRavenis connected.LeavetheBaudsettingat115200.

Figure 2-4: Modem Doctor: Interface

d. ClicktheNextbuttonandpressthemodemReset buttonwhenprompted.ThemodemResetbuttonis locatedonthefrontpanelofthemodemandcanbe accessedwiththepointofapenorsimilartool.

111

20070914

Circuit Switch Communications

Figure 2-5: Raven: Reset button

e. ClicktheExitbuttoninModemDoctorwhenthe processiscomplete.

4. Activate the Raven 5. Start AceManager.


Start>AllPrograms>AirLinkCommunications>AceManager3G >AceManager3G a. ClicktheConnectbutton.

Figure 2-6: AceManager

b. SelectPPP. c. SelectCOM1forthePort. d. Enter12345forthePassword. e. ClickOK.

Figure 2-7: AceManager : Connect to Modem using PPP

6. Configure serial port speed.


a. Ontheleft,undertheGROUPSheading,selectSerial.

Rev 3.0B Feb.08

112

Raven EDGE

Figure 2-8: AceManager : Serial - *MODEMHISPEED

b. Changethe*MODEMHISPEEDsettingto0.

7. Save the serial setting.


a. ClicktheWritebuttononthetoolbarofAceManager andwaitforthemessageWriteSuccessfultoappear inthestatusbar.

Figure 2-9: AceManager : Write

b. ClicktheClearbutton.

Figure 2-10: AceManager : Clear

c.

ClicktheDisconnectbutton.

Figure 2-11: AceManager : Disconnect

d. PressthemodemResetbuttononthefrontofthe modem.

113

20070914

Circuit Switch Communications

Figure 2-12: Raven: Reset

e. WaituntilthemodemREGindicatorislitandthen proceedtothenextstep.

8. Configure the Raven using a AceManager template.


Caution: Do not proceed to this step before the REG indicator light is lit.

a. ClicktheRefreshAllbuttononthetoolbarof AceManagerandwaituntilallofthemodeminfor mationisloadedintotheAceManagerapplication.

Figure 2-13: AceManager : Refresh All

b. ClicktheLoadbuttononthetoolbar.

Figure 2-14: AceManager : Load

c.

Changetothefolder(directory)whereyou downloadedthetemplate(s)andselectthetemplate foryourmodemmodeland/orpreferredmode.

Figure 2-15: AceManager : Template

Rev 3.0B Feb.08

114

Raven EDGE

9. Configure additional PassThru settings.


a. Ontheleft,undertheGROUPSheading,select PassThru.

Figure 2-16: AceManager : PassThru

b. For*PTREFRESH,enteravalueof15. c. For*RESETPERIOD,enteravalueof6.

10. Save the configuration settings.


ClicktheWritebuttononthetoolbarofAceManagerandwait forthemessageWriteSuccessfultoappearinthestatusbar.

11. Configure the Raven for your equipment.


a. Makeanyappropriatechangestotheserialport parameterstomatchyourequipment.Thesechanges aremadeunderthegroupSerial.
Caution: Do not under any circumstances change the *MODEMHISPEED setting from the template configuration, the only recommended setting to change is the S23 setting.

b. FollowthedirectionsabovetoWritethechangestothe modem.

12. Reset the Raven.


a. ClicktheDisconnectbutton. b. PressthemodemResetbuttononthefrontofthe modem. c. WaituntilthemodemREGindicatorislit. d. DisconnecttheRavenfromyourcomputer.

115

20070914

Circuit Switch Communications

13. Test the Raven Configuration.


Oncethemodemhasbeenactivatedandyouvebuiltthe commandstringitisrecommendedthattheRavenmodembe testedprevioustofieldinstallation. a. VerifythatthemodemChan,LinkandRegindicators areblinkinginunisonconfirmingthatthemodemis nowoperatingincircuitswitched(IS95)mode.
Note: The dial test should be completed with the serial cable disconnected to verify that no signaling is required by the modem.

b. DialtheRavenmodemtelephonenumberfromaland lineandverifythatthemodemautomaticallyanswers thecallwithmodemtones. c. Verifyoutgoingcalls. 1. Connectthemodemtoyourcomputerwitha serialcable.Usingaterminalemulationprogram (HyperTerminal)setupfor9600bps,8databits,no parityand1stopbit. Enterthecommand:ATD[phone number].Forthe [phonenumber],enteraknownphonenumber includingtheareacodeforwhichyoucanhear ring(suchasyourofficephone).

2.

14. Commission the Raven Modem on Site.


Thefollowingstepsrepresentaguidelineandmakesassump tionsthatthemodemhasbeenverifiedpreviouslyina controlledenvironment. a. InstalltheRavenmodemverifyingthatallpowerand antennacablesarecorrectlysecured. b. VerifythattheRavenmodempowersupandthatthe Chan,LinkandReglightsblinkinunison. c. ConnecttheRavenmodemtothelaptopcomputervia astraightthroughRS232cableorconnecttheserial cablefromthemodemtoaUSBtoserialdevicethat hasbeenpreviouslyinstalledonthelaptop.

d. RemovetheconnectiontotheLaptopPCandconnect yourequipmenttotheRavenModem. e. Havetheactualapplicationcallyourequipmentvia themodemtelephonenumberandverifycommunica tions.

Rev 3.0B Feb.08

116

Raven EDGE

117

20070914

C: Windows Dial-up Networking (DUN)


Installing a modem driver for Raven Creating a Dial-Up Networking (PPP) Connection Connecting to the Internet Using DUN
DialupNetworking(DUN)allowsacomputerorotherdevice tousetheonyourRaventoconnecttotheInternetorprivate networkusingPPPjustlikeananalogmodemusinga standardphoneline.
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


StandardinstallationsofMicrosoftWindowsXPand2000 includeagenericmodemdriverwhichwillworkwithyour Raven.

1. Connect the Raven.


a. ConnectthemodemtothecomputerwithaDB9 cableortheUSBportinserialmode.. b. PlugintheACadapter,connecttheantenna(s)and poweronthemodem.

2. Install the driver.


a. SelectStart>ControlPanel>PhoneandModemOptions (inClassicView).

Rev 3.0B Feb.08

118

Windows Dial-up Networking (DUN)

Figure 3-1: Phone and Modem Options

b. SelecttheModemstab.

Figure 3-2: Phone and Modem Options: Modems

c.

SelectAdd.

Rev 3.0B Feb.08

119

Windows Dial-up Networking (DUN)

Figure 3-3: Add Hardware Wizard

d. CheckDontdetectmymodem;Iwillselectitfromalist. e. SelectNext.

Figure 3-4: Add Hardware Wizard: Install New Modem

f.

Select(StandardModemTypes)fromtheManufacturers column.

g. SelectStandard33600bpsModemfromtheModels column.

Rev 3.0B Feb.08

120

Windows Dial-up Networking (DUN)

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 3-5: Add Hardware Wizard: Select Ports

i. j.

CheckSelectedPorts SelecttheCOMportthemodemisconnectedto (commonlyCOM1).

k. SelectNext.

Figure 3-6: Add Hardware Wizard: Finish

l.

Oncethemodemdriverisinstalled,selectFinish.

Rev 3.0B Feb.08

121

Windows Dial-up Networking (DUN)

3. Configure the driver.


WhenyoureturntothePhoneandModemOptionswindow,you shouldseethenewlyinstalledmodemattachedtothe correctCOMport.

Figure 3-7: Phone and Modem Options: Modems

a. HighlightthemodemandselectProperties.

Figure 3-8: Modem Properties

Rev 3.0B Feb.08

122

Windows Dial-up Networking (DUN)

b. SelecttheModemtab.

Figure 3-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

123

Windows Dial-up Networking (DUN)

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.

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 3-10: Windows : Start menu

Rev 3.0B Feb.08

124

Windows Dial-up Networking (DUN)

b. SelectCreateaNewConnectionunderNetworkTasksin themenuareaontheleft.

Figure 3-11: Create New Connection

c.

SelectNexttostartinstallingandconfiguringtheDUN connection.

Figure 3-12: New Connection Wizard

d. SelectConnecttotheInternet. e. SelectNext.

Rev 3.0B Feb.08

125

Windows Dial-up Networking (DUN)

Figure 3-13: New Connection: Type

f.

SelectSetupmyconnectionmanually.

g. SelectNext.

Figure 3-14: New Connection: How do you want to connect?

h. SelectConnectusingadialupmodem. i. SelectNext.

Figure 3-15: New Connection: Connect using...

j.

Optional:Ifyouhavemultiplemodemsinstalledon yourcomputer,youmaybepromptedtoselectthe modemtobeused.Ifyouonlyhaveonemodem installed,thisoptionwillbeomitted. SelectNext.

k. CheckStandard33600bpsModem. l.

Rev 3.0B Feb.08

126

Windows Dial-up Networking (DUN)

Figure 3-16: New Connection: Select Modem

m. Typeinanamefortheconnection,suchasSierra WirelessAirLinkModem. n. SelectNext.

Figure 3-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), or any other designation for the connection.

o. Typein10001asthephonenumberforthemodemto dial. p. SelectNext.

Figure 3-18: New Connection: Phone Number

q. Optional:Ifyouhavemultipleusersconfiguredfor yourcomputer,youmaybepromptedforConnection Availability.IfyouselectMyuseonly,theaccount currentlyloggedonwillbetheonlyoneabletouse thisDUNconnection. r. SelectNext.

Rev 3.0B Feb.08

127

Windows Dial-up Networking (DUN)

Figure 3-19: New Connection: Permissions

GenerallythemodemtakescareoftheAccountInformation, UsernameandPassword,fortheconnection,soyoucanleave thefieldsblank(unlessotherwiseinstructedbySupport). s. t. Ifyouwanttoallowotherstousethesameloginfor themodem,selectUsethisaccountnameandpassword.... SelectNext.

Figure 3-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 will be your sole network connection.

u. IfyouwanttoaddashortcutforthisDUNconnection toyourdesktop,checkAddashortcut. v. SelectFinishtoexittheNetworkConnectionWizard.

Rev 3.0B Feb.08

128

Windows Dial-up Networking (DUN)

Figure 3-21: New Connection: Finish

2. Configure the DUN connection


AfteryoucompletetheNewConnectionWizard,therearea fewmorethingsyouwillwanttoconfigureintheconnection. a. SelectProperties.

Figure 3-22: DUN Connection

b. UncheckUsedialingrules.

Rev 3.0B Feb.08

129

Windows Dial-up Networking (DUN)

c.

CheckShowicon...whenconnected.

d. SelectConfigure,belowtheConnectusingline.

Figure 3-23: DUN Properties

e. Select115200astheMaximumspeed. f. CheckEnablehardwareflowcontrol. g. Donotcheckanyotheroption. h. SelectOK.

Rev 3.0B Feb.08

130

Windows Dial-up Networking (DUN)

Figure 3-24: Modem Configuration

i.

Backatthemainpropertiesscreen,selectthe Networkingtab.

Figure 3-25: Networking

j. l.

SelectSettings. SelectOK.

k. RemovethechecksfromallthreePPPsettings.

Rev 3.0B Feb.08

131

Windows Dial-up Networking (DUN)

Figure 3-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 3-27: TCP/IP Properties

o. UncheckUseIPheadercompression. p. CheckUsedefaultgatewayonremotenetwork. q. SelectOK.

Rev 3.0B Feb.08

132

Windows Dial-up Networking (DUN)

Figure 3-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


TherearetwomethodsyoucanusetoconnectwithRavento theInternetusingDUN,AceViewandtheWindowsDUN connectiondirectly.

AceView
AceViewisasmallutilitywhichcanmaintainyourDUN connectionandmonitortheconnectionofyourRavento 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

133

Windows Dial-up Networking (DUN)

2. Enable the Connection.

Figure 3-29: AceView: Menu

a. RightclickontheAceViewwindowtoopenthemenu. b. SelectConnectionSettings.

Figure 3-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

134

Windows Dial-up Networking (DUN)

1. Start the DUN session.


Start>ConnectTo>SierraWirelessAirlinkModem Ifyounamedtheconnectiondifferently,usethenameofthe PPPconnectionyoumadeearlier.

Figure 3-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 3-32: Connection indicator

Rev 3.0B Feb.08

135

Windows Dial-up Networking (DUN)

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

136

You might also like