Airlink X EV-DO User Manual

Raven X EV-DO

User Guide

Copyright © 1993-2007 AirLink Communications, Inc. All rights reserved.

Version 2.34 - April 2007

Information in this document is subject to change without notice.
©Copyright AirLink Communications, Inc., 1993-2007. All rights reserved.

WARNING

The antenna(s) used for this transmitter must be installed to provide a separation distance of at least 20 cm
from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter.

Important Notice

Because of the nature of wireless communications, trans mission and reception of d ata can never be guar anteed.
Data may be delayed, corrupted (i.e. , ha ve errors) or be to tally lost. Although significant delays or los ses of data
are rare when wireless devices suc h as the AirL ink Communications modem are used in a normal manner with a
well-constructed network, the AirLink modem should not be used in situations where failure to transmit or
receive data could result in damage of any kind to the user or any other party, including but not limited to per
sonal injury, death, or loss of property. AirLink Communications, Inc., accepts no responsibility for damages of
any kind resulting from delays or errors in data transmitted or received using the AirLink Communications
modem, or for failure of the AirLink Communications modem to transmit or receive such data.

Safety and Hazards

Do not operate the AirLink Communications modem in areas where blasting is in progress, where explosive
atmospheres may be present, near medical equipm ent, near life support equipment, or any equipment which
may be susceptible to any form of radio interference. In such areas, the AirLink Communications modem MUST
BE POWERED OFF. The AirLink Communications modem can tr ansmit sign als that could interfere with this equip
ment. Do not operate the AirLink Communications modem in any aircraft, whether the aircraft is on the ground
or in flight. In aircraft, the AirLink Communications modem MUST BE POWERED OFF. When operating, the Air
Link Communications modem can transmit signals that cou ld interfere with v arious on boar d systems. The driv er
or operator of any vehicle should not operate the AirLink Communications modem while in control of a vehicle.
Doing so will detract from the driver or operator's control and operation of that vehicle. In some states and
provinces, operating such communications devices while in control of a vehicle is an offence.

-

Limitation of Liability

The information in this manual is subject to change without notice and does not represent a commitment on the
part of AirLink Communications, Inc. AIRLINK COMMUNICATIONS, INC. SPECIFICALLY DISCLAIMS LIABILITY
FOR ANY AND ALL DIRECT, INDIRECT, SPECIAL, GENERA L, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEM
PLARY DAMAGES INCLUDING, BUT NOT LIMITED TO, LOSS OF PROFITS OR REVENUE OR ANTICIPATED PROFITS
OR REVENUE ARISING OUT OF THE USE OR INABILITY TO USE ANY AIRLINK COMMUNICATIONS, INC. PROD
UCT, EVEN IF AIRLINK COMMUNICATIONS, INC. HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES
OR THEY ARE FORESEEABLE OR FOR CLAIMS BY ANY THIRD PARTY.

-

Warranty Summary

For the full and complete text, refer to the warranty appendix in the modem user guide or to the AirLink website
(http://www.airlink.com) for the full text of the warranty.

Software: Software is warrantied for 90 days to work in substantial conformance to applicable software specifi­cations. AirLink’s sole obligation is to , at their op tion, refund the lisce nse fee or repl ace th e softw are with othe r
software.

Hardware: All equipment is warr antied for one y ear after delivery to conform with AirLink’ s specific ations and be
free from manufacturing defect. Optional warranty extensions can be purchased for two and four years which
would increase the warranty period to three and five years respectively. If under normal use, the hardware
proves to have any such defect and the Customer notifies AirLink of such defect within the warranty period, Air
Link, at its option, will either repair or replace the same without charge but only upon written authorization and
in accordance with instructions of AirLink using a Return Material Authorization ("RMA") process (details of the
process are in the full warranty statement).

THIS WARRANTY DOES NOT COVER PRODUCTS THAT DO NOT CONFORM TO SPECIFICATIONS BECAUSE OF
ACCIDENT, ALTERATIONS, FAILURE TO FOLLOW INSTRUCTIONS, USE OUTSIDE THE SCOPE OF ANY OTHER
PROVIDED DOCUMENTATION (E.G., USER GUIDE, INSTALLATION GUIDE, QUICK START GUIDE), MISUSE,
ABUSE, NEGLECT, FIRE, FLOOD OR ACTS OF GOD.

-

-

-

-

Raven X EV-DO for Verizon - User Guide, version 2.34 ii

Contents

Introduction to Raven X EV-DO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

EV-DO Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Establishing an Internet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Dynamic vs. Static IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Using Your Raven X to Connect to the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Common Uses for the Raven X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Activating the Raven X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Automatic Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Quick Start Guide and Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Activating the Raven X using AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Utilities for the Raven X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

AceView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Wireless Ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

AceNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Modem Doctor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

IP Manager and DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Fully Qualified Domain Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Dynamic Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Configuring the Raven X for IP Manager and a Dynamic IP Domain Name . . . . . . . . .13

Data Usage for IP Manager Server Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Eairlink.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

DNS: Using Names Instead of IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Configuring DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Data Communication and Host Modes . . . . . . . . . . . . . . . . . . . . . . . . .17

AT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

PassThru Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

TelnetMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

PPP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Slip Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

UDP Pad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

UDP Auto Answer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Reliable UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

UDP Multicast Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Raven X EV-DO for Verizon - User Guide, version 2.34 iii

Contents

TCP PAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Hybrid Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Public and Private Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Internal DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

DHCP and Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

DHCP in the Raven X using Public Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

PPPoE with DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

The AirLink Modem as a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Keepalive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Configuring Keepalive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Data usage using Keepalive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Modbus/BSAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Modbus Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Telemetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Remote T erminal Unit (RTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Supervisory Control and Data Acquisition (SCADA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Programmable Logic Controller (PLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Modbus TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Raven Modbus on UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring the Raven X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Configuring the Raven X at the Polling Host for Modbus on UDP . . . . . . . . . . . . . . . . .31

Dynamic IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuring the Remote Modems for Modbus with UDP . . . . . . . . . . . . . . . . . . . . . . . .34

Dynamic IPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Connecting the Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Connecting Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Connecting the Raven X to a computer or other device . . . . . . . . . . . . . . . . . . . . . . . . . .39

Raven X Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Light Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Monitoring Power-In Voltage and Internal Temperature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Modem Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Built in Mounting Tabs for Raven X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Installing a Raven with an RTU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Specifications for the Raven X EV-DO . . . . . . . . . . . . . . . . . . . . . . . . . .45

Physical Characteristics: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Environmental: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Power Management: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Serial Port Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

AT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Using Wireless Ace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Using Telnet Terminal Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Direct Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Using AT Commands with a Terminal Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Raven X EV-DO for Verizon - User Guide, version 2.34 iv

Contents

AT Command Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Information and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Misc (Miscellaneous) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Serial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

TCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Dynamic IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

PPP/Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

PassThru. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

SMTP (including SMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Other. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Friends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Telemetry and Addr List (Address List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

CDMA/EV-DO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Simple Network Management Protocol (SNMP) . . . . . . . . . . . . . . . . .94

SNMP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Management Information Base (MIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Raven X SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Listening Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Security Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Trap Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Community String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

SNMP MIB Definition for AirLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

PPPoE: Point to Point Protocol over Ethernet . . . . . . . . . . . . . . . . . .103

PPPoE (PPP over Ethernet) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Configuring your Raven X for PPPoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring a PPPoE Connection in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Connecting to the Internet with PPPoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Configuring your router for PPPoE with the Raven X . . . . . . . . . . . . . . . . . . . . . . . . . .112

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

Installing the Modem Driver in Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Dial-Up Networking (PPP) Configuration for Microsoft Windows . . . . . . . . . . . . . . . .116

Making a DUN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122

Establishing a DUN Connection with Windows Networking . . . . . . . . . . . . . . . . . . . . . . . . 123

Warranty Terms and Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Warranty Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Standard Software Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

One Year Standard Equipment Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Optional T wo Year Extended Equipment Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Optional Four Year Extended Equipment Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Warranty Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Remedy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

WARRANTY DISCLAIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Raven X EV-DO for Verizon - User Guide, version 2.34 v

Contents

LIMIT ATION OF LIABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

General Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Frequently Asked Questions and Technical Support . . . . . . . . . . . . . 128

FAQ Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Power, Antennas, and Signal Strength . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

The Raven X’s IP Addresses and Local Network ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Security for the Raven X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Activation (Registering on the Verizon Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Prefered Roaming List (PRL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

AirLink Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

AirLink Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

AirLink Documentation and Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Raven X EV-DO for Verizon - User Guide, version 2.34 vi

CHAPTER 1 Introduction to Raven X EV-DO

The Raven X's rugged form factor is ideal for industrial and commercial applications that require
real-time communications. The Raven X provides cellular data communications for a variety of
applications, such as primary or backup Internet connectivity, public safety, traffic control, traffic
metering, and more.

FIGURE 1. Raven X front and back

EV-DO Overview

EV -DO (Evolution Data Optimized) provides a broadband-like cellular data connections that is 10
times faster than 1xRTT (CDMA) service. With the high-speed connection, users can experience
faster downloading when accessing the Internet and retrieving e-mails, including large attach
ments and other bandwidth-intensive applications. EV-DO is often refered to as Mobile Broad­band and Cellular Broadband.

EV-DO revision A is an evolution of revision 0, adding expanded upload capabilities and a more
robust connection overall. In addition to increasing the downlink speed, revision A also increases
the uplink speed. In addition, it is backwards compatible and automatically connects with existing
and broadly deployed EV-DO Rev. 0 and CDMA 1x networks ensuring reliable and pervasive
connectivity.

Raven X EV-DO for Verizon - User Guide, version 2.34 1

-

Introduction to Raven X EV-DO

Internet

In addition to the primary broadcast and receive antenna port (SMA, labeled Antenna), the Raven
X EV-DO is equipped with a secondary receive diversity antenna port (SMA, labeled Rx Div).
While use of the receive diversity antenna is optional, receive diversity can provide improved
bandwidth throughput and increased coverage, particularly in fringe network areas or mobile
environments.

Use of receive diversity is optional. Data transmission and reception will not be
adversely affected if it is not used. Diversity can, however, provide a more consis
tent signal. To work correctly, receive diversity requires the two antennas to be
placed at least six inches apart.

CDMA (Code Division Multiple Access) is the underlying digital radio network technology used
by many cellular providers across the globe and is prevalent in North America. CDMA/1x pro
vides a digital cellular telephony system and can provide wireless Internet access at speeds
between 60 and 80 kbps, with bursts up to 144 kbps. 1x is a data standard built on CDMA.

1x and EV-DO data transmission is highly secure. Originally developed based upon the “spread
spectrum” pioneered by the US Department of Defense, security in 1x is obtained by spreading
the digital information contained in a particular signal of interest over multiple coded paths, ov er
a much greater bandwidth than the original signal.

-

-

Establishing an Internet Connection

The Raven X uses Veri zon as an ISP (Internet Service Provider) to connect you to the Internet.

Steps of a connection:

1. When your Raven X is powered on, it automatically searches for cellular service using EV-

DO.

2. Your Raven X establishes a PPP (Point to Point Protocol or “dial” up connection) link to Ver-

izon’s network, also called registering on the network, and receives an IP address.

3. When your Raven X has received its IP address from Verizon, then it is ready to allow you to

connect to the Internet.

FIGURE 2. Using the Raven X to connect to the Internet

Raven X EV-DO for Verizon - User Guide, version 2.34 2

Introduction to Raven X EV-DO

Dynamic vs. Static IP Addresses

As stated above, when your Raven X registers on Verizon’s netw ork , it receives an IP address.
There are two types of addresses on networks: dynamic and static.

• Dynamic addresses are assigned on a “need to have” basis. Your Raven X might not always

receive the same address each time it connects with Verizon.

• Static addresses are permanently assigned to a particular account and will always be used

whenever your Raven X connects to the Internet. The IP address will not be given to anyone
else.

Most ISPs (cellular included) use dynamic IP addresses rather than static IP addresses since it
allows them to reuse a smaller number of IP addresses for a large number of customers. A
dynamic IP address is suitable for many common Internet uses, such as web browsing, looking up
data on another computer system, or other client functions (such as data only being sent out or only
being received after an initial request).

If you need to contact your Raven X, a device connected to the modem, or a host system using the
modem from the Internet, you need to have a known IP (such as one which is static) or domain
name (an IP address which is converted by a DNS server into a word based name). If you have a
dynamic IP address for your modem, you can use a Dynamic DNS service (such as IP Manager,
page

11) to translate your IP address into to a domain name.

Caution: If you want to connect remotely to your Raven X using TCP/IP, the IP

address given to your modem by the network cannot be a private or internal IP
address (such as a special private network) unless you are on the same network or
inside that network’s firewall (such as with frame relay).

Using Your Raven X to Connect to the Internet

In Public Mode, your Raven X will pass the IP address from Verizon’ s network to your device or
computer. In Private Mode, your modem will assign configured, static local network IP addresses
for the modem and your device.

The modem will perform a one-to-one routing for all internet traffic to and from the computer or
other end device.

If you need to have more than one device connected to the Internet through the modem, you will
need to have a router connected to the modem. The modem would provide the one-to-one con
nection to the router with the router configured to provide a broader NAT service to the other
devices connected to it.

You can connect directly through your Raven X to the Internet using the Ethernet port or use
PPPoE for a password protected connection. For a direct connection, the Raven X features DHCP
(enabled by default) so you don’t need to worry about setting up an IP address on your computer.
DHCP works with both Private and Public Modes.

-

Raven X EV-DO for Verizon - User Guide, version 2.34 3

Introduction to Raven X EV-DO

Common Uses for the Raven X

The Raven X’s rugged construction and cellular connection make it ideal for use in remote and/or
industrial locations.

FIGURE 3. Backup connection to the Internet

FIGURE 4. Financial Point of Sale and Kiosk

FIGURE 5. Automation and Telemetry

Raven X EV-DO for Verizon - User Guide, version 2.34 4

CHAPTER 2 Activating the Raven X

Your Raven X needs specific parameters before it can operate on the EV-DO network.

Automatic Activation

One of the special features of your Raven X EV-DO and the Verizon network is the ability to acti­vate itself automatically. When you first power on the Raven X, the modem will check to see if it
has been activated with account data. If it finds that it has not yet been activated, it will attempt to
retrieve the account data from the Verizon network using Over-the-Air Service Provisioning
(OTASP).

Note: You need to have an account with before you attempt automatic activation.

If you have not ordered an account from for your Raven X, it will not succeed at
activating itself.

Attach the antenna to your modem before you plug in the power.

1. The Raven X will cycle the LED lights in its power on self test.

2. All the lights will go out except the power light. At this point, the modem is attempting to

download its account information. The download process may take about a minute or two.

3. When the download is complete, the Raven X will reset itself, the power light will go out and

the LED lights will cycle once more.

4. When the Network light illuminates, your Raven X has successfully completed OTASP and is

registered on the Verizon network.

.If you need to update the ALEOS firmware, change the account information, or want to test your
Raven X’s account settings, you can use the Setup Wizard. If the automatic activation was suc

-

cessful, you do not need to do anything additional to activate your Raven X for Verizon.

Caution: Before you power up the the first time, be sure to have the antenna con-

nected. Do not move your while it is being programmed.

Quick Start Guide and Setup Wizard

A quick and easy way to activate and configure your Raven X to connect to the cellular network is
via the AirLink Setup Wizard for Verizon. The Quick Start Guide will lead you through using the
Setup Wizard.

Raven X EV-DO for Verizon - User Guide, version 2.34 5

Activating the Raven X

If Automatic Activation was successful, you do not need to use the Wizard to activate your
modem.

FIGURE 1. Once it has been installed, to use the Wizard, select Start, then All Programs, then

AirLink Communications, and then select Setup Wizard. Setup Wizard

The latest Raven X Setup Wizard and Quick Start guide are on the product CD
included with your modem and are available from the AirLink web site, http://

www.airlink.com/support.

Note: T o run the Setup Wizard, you will need the Microsoft .NET framework v.1.1

and Microsoft Windows 98, Microsoft Windows 2000, Microsoft Windows XP, or
later.

Activating the Raven X using AT Commands

An alternate method to configure and activate your Raven X is by using AT commands sent
directly to the modem with a terminal application (refer to the troubleshooting section, page
This method is recommended only in situations where the Setup Wizard is not available and/or
the configuration for the Raven X is unusual.

Caution: While you can configure your Raven X using Wireless Ace or AceNet, it

is not possible to activate the Raven X using either Wireless Ace or AceNet.

128).

Raven X EV-DO for Verizon - User Guide, version 2.34 6

CHAPTER 3 Utilities for the Raven X

AirLink offers a suite of utilities to optimize your Raven X’s performance, allowing you to
remotely view status and make changes to the configuration as needed.

• AceView • AceNet

• Wireless Ace • Modem Doctor

This section of the Raven X User Guide covers basic information about these utilities. For addi­tional information on a specific application and how to use it, please refer to the user guide for the
specific utility.

AirLink modem utilities, except AceNet, are free of charge to those who own AirLink modems.
You can download the applications and their user guides from the AirLink web site: http://www.air

link.com/support. Contact your dealer or AirLink representative for information on AceNet.

-

Note: AceV iew, Wireless Ace, 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/.

AceView

AceView is a low-profile monitoring tool to view the status of your AirLink Raven X and display
network status, IP address, RSSI strength, and other basic connection information.

FIGURE 1. AceView

You can connect to your Raven X locally using a DUN connection or Ethernet across a LAN or
connected directly. The display is dynamically updated with the current status of the modem.

The GPS features are available only for PinPoint X, PinPoint-E, and PinPoint modems.

Raven X EV-DO for Verizon - User Guide, version 2.34 7

Utilities for the Raven X

When you use DUN to connect to your Raven X, AceView can monitor and maintain the DUN
connection.

The DUN connection features are not available with W indows NT or Windows 98. Refer to the
AceView Guide for information on how to connect using serial for Windows NT or Windows

98.

Wireless Ace

Wireless Ace enables modems equipped with ALEOS to be monitored and configured locally or
remotely.

As long as your Raven X is online and publicly accessible, support personnel can access your
modem from anywhere at any time to see how it is operating and how it is configured. Parameter
changes can be made instantly over-the-air.

Once your modem is configured and installed correctly, a template can be made to program other
modems with the same parameter values. This enables quick, accurate deployment of large pools
of modems.

Most configuration screen shots in this guide are using Wireless Ace. Connecting
to the modem using Wireless Ace is covered in the “AT C ommands” chapter on
page 47.

FIGURE 2. Wireless Ace

Raven X EV-DO for Verizon - User Guide, version 2.34 8

Utilities for the Raven X

AceNet

AceNet is a full featured application that you can use to monitor several AirLink modems at the
same time, use a template from Wireless Ace to change the configuration in all of them simulta
neously, keep the modems up-to-date with the latest firmware and/or PRL by updating them over
the air, periodically log the modems’ Status parameters, and even graphically chart the logged
parameters to see trends or other over time information.

AceNet’s remote connections use TCP/IP, UDP, or SMS.

AceNet is a separate product which can be purchased from AirLink. Contact your AirLink repre­sentative for more information.

FIGURE 3. AceNet

-

FIGURE 4. AceNet Charting

Raven X EV-DO for Verizon - User Guide, version 2.34 9

Utilities for the Raven X

Modem Doctor

Modem Doctor is a troubleshooting and diagnostics utility. This utility will allow you to get a log
file of the
ration completely, and temporarily set the Raven X to a known configuration to aid in trouble
shooting (SOS mode).

FIGURE 5. Modem Doctor

Raven X activity which you can then send to AirLink support, erase the current configu-

Raven X EV-DO for Verizon - User Guide, version 2.34 10

CHAPTER 4 IP Manager and DNS

If you have a fleet of AirLink modems or even if you only have one, it can be difficult to keep track
of the current IP addresses, especially if the addresses aren’t static but change every time the
modems connect to Verizon. If you need to connect to a modem, or the device behind it, it is so
much easier when you have a domain name (car54.mydomain.com, where are you?).

Reasons to contact the modem and/or the connected device:

• Contacting a surveillance camera to download logs or survey a specific area.

• An oil derek that needs to be triggered to begin pumping.

• Sending text to be displayed by a road sign.

• Updating the songs to be played on a juke box.

• Updating advertisements to be displayed in a cab.

• Remote access to a computer, a PLC, an RTU, or other system.

• Monitoring and troubleshooting the status of the modem itself without needing to bring it in or

go out to it.

A dynamic IP address is suitable for many Internet activities such as web browsing, looking up data
on another computer system, data only being sent out, or data only being received after an initial
request (also called Mobile Originated). However, if you need to contact your Raven X directly, a
device connected to the modem, or a host system using your Raven X (also called Mobile Termi
nated), a dynamic IP won’t give you a reliable address to contact (since it may have changed since
the last time it was assigned).

Domain names are often only connected to static IP addresses because of the way most domain
name (DNS) servers are set-up. Dynamic DNS servers require notification of IP Address changes
so they can update their DNS records and link a dynamic IP address to the correct name.

-

• Dynamic IP addresses are granted only when your Raven X is connected and can change each

time the modem reconnects to the network.

• Static IP addresses are granted the same address every time your Raven X is connected and are

not in use when your Raven X is not connected.

Since many cellular providers, like wire-based ISPs, do not offer static IP addresses or static
address accounts cost a premium vs. dynamic accounts, AirLink developed IP Manager to work
with a Dynamic DNS server to receive notification from AirLink modems to translate the modem’s
dynamic IP address to a fully qualified domain name. Thus, you can contact your Raven X directly
from the Internet using a domain name.

Raven X EV-DO for Verizon - User Guide, version 2.34 11

IP Manager and DNS

Fully Qualified Domain Name

A domain name is a name of a server or device on the Internet which is associated with an IP
address. Similar to how the street address of your house is one way to contact you and your phone
number is another, both the IP address and the domain name can be used to contact a server or
device on the Internet. While contacting you at your house address or with your phone number
employ different methods, using a domain name instead of the IP address actually uses the same
method, just a word based name is commonly easier to remember for most people than a string of
numbers.

Understanding the parts of a domain name can help to understand how IP Manager works and what
you need to be able to configure the modem. A fully qualified domain name (FQDN) generally has
several parts.

• Top Level Domain (TLD): The TLD is the ending suffix for a domain name (.com, .net, .org,

• Country Code Top Level Domain (ccTLD): This suffix is often used after the TLD for most

• Domain name: This is the name registered with ICANN (Internet Corporation for Assigned

• Sub-domain or server name: A domain name can have many sub-domain or server names

etc.)

countries except the US (.ca, .uk, .au, etc.)

Names and Numbers) or the registry for a the country of the ccTLD (i.e. if a domain is part of
the .ca TLD, it would be registered with the Canadian domain registry). It is necessary to have
a name registered before it can be used.

associated with it. Sub-domains need to be registered with the domain, but do not need to be
registered with ICANN or any other registry. It is the responsibility of a domain to keep track
of its own subs.

car54.mydomain.com

• .com is the TLD

• mydomain is the domain (usually noted as mydomain.com since the domain is specific to the

TLD)

• car54 is the subdomain or server name associated with the device, computer, or modem regis-

tered with mydomain.com

car54.mydomain.com.ca

This would be the same as above, but with the addition of the country code. In this example, the
country code (.ca) is for Canada.

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.airlink.com. www.airlink.com is a fully qualified
domain name, but the http://, the protocol identifier, is what makes the whole thing
a URL.

Raven X EV-DO for Verizon - User Guide, version 2.34 12

IP Manager and DNS

car54-2007

eairlink.com
edns2.eairlink.com

eairlink.com

Dynamic Names

When an IP address is not expected to change, the DNS server can indicate to all queries that the
address can be cached and not looked up for a long period of time. Dynamic DNS servers, con
versely, have a short caching period for the domain information to prevent other Internet sites or
queries from using the old information. Since the IP address of a modem with a dynamic account
can change frequently, if the old inform atio n was used ( su ch as w ith a DNS server which indicates
the address can be cached for a long period of time) when the IP address changed, the domain
would no longer point to the new and correct IP address of the modem.

If your Raven X is configured for Dynamic IP, when it first connects to the Internet, it sends a IP
change notification to IP Manager. IP Manger will acknowledge the change and update the
Dynamic DNS server. The new IP address will then be the address for your Raven X’s configured
name.

Once your Raven X’s IP address has been updated in IP Manager, it can be contacted via name. If
the IP address is needed, you can use the domain name to determine the IP address.

-

Note: The fully qualified domain name of your Raven X will be a subdomain of the

domain used by the IP Manager server.

Configuring the Raven X for IP Manager and a Dynamic IP Domain Name

To configure the Dynamic IP settings in your Raven X so that it will use IP Manager, you can use
Wireless Ace or a terminal application to enter the commands (page

To configure your AirLink modem to be addressed by name, the modem needs to have 4 elements
configured. Y ou can configure a second dynamic server as a backup, secondary , or alternate server .
In Wireless Ace, select Dynamic IP.

FIGURE 1. Wireless Ace: Dynamic IP

47).

Raven X EV-DO for Verizon - User Guide, version 2.34 13

IP Manager and DNS

Restrictions for Modem Name

For the Modem Name, you should use something which is unique but also easy to remember. Your
company name or the intended function of the modem are recommended. If you have more than
one modem and want to name them the same, you can append a number for each. Since it is an
Internet domain name, there are some restrictions for the name.

*MODEMNAME: The name you want for the modem.
*DOMAIN: The domain name to be used by the modem.
*IPMANAGER1 and *IPMANAGER2: The IP address or domain name of the dynamic DNS

server which is running IP Manager.

Note: To use the name here instead of the IP, you need to have DNS set up in your

Raven X (page

*IPMGRUPDATE1 and *IPMGRUPDATE2: How often, in minutes, you want the address
sent to IP Manager. If this is set to zero, the modem will only send an update if the IP address
changes (example, if your Raven X modem is reset or is assigned a different IP address).

*IPMGRKEY1 and *IPMGRKEY2: User defined password key which is used instead of Air­Link secret key when using an IP Manager server other than the one provided by AirLink.

15).

• Must begin with a letter or number

• Can include a hyphen (-)

• Cannot contain spaces

• Must be no longer than 20 characters total

Data Usage for IP Manager Server Updates

The IP Manager update is a small packet sent to the server with a response sent back to the modem.
If you have *IPMGRUPDATE1 or *IPMGRUPDATE2 set to any number but zero, the modem
will send the update not only when it receives a new IP address but at the time interval as well. The
data traffic could be billed by your carrier.

Each update is a total of 68 bytes from the modem with a 50 byte total response from the server for
a round trip update of 118 bytes.

interval
(minutes)

10 16992 bytes 60 2832 bytes
30 5664 bytes 500 339.84 bytes

total bytes per
day (24 hours)

interval
(minutes)

total bytes per
day (24 hours)

Eairlink.com

As a service, Airlink maintains a IP Manager servers which can be used for any AirLink modem.

• *DOMAIN: eairlink.com

• *IPMANAGER1 : edns2.eairlink.com

• *IPMANAGER2 : eairlink.com

Raven X EV-DO for Verizon - User Guide, version 2.34 14

IP Manager and DNS

DNS: Using Names Instead of IP addresses

The Raven X has the ability to query DNS servers in order to translate domain names into IP
addresses. This allows you to use domain names in place of IP addresses for most of the configu
ration options requiring IP addresses. This is important if your Raven X will need to contact
another modem or other device that has a domain name but an unknown or dynamic IP address
(such as another remote Raven X using IP Manager).

Configuring DNS

Generally, when your Raven X receives its IP address from Verizon, it will also receive Verizon’s
DNS servers to use for resolving (or translating) names to IP addresses which it will automatically
configure in the modem settings. Unless your Raven X will be used on a network with other
modems or devices which have names internal to the local network or frequently changing IP
addresses, the DNS servers provided by Verizon should be all you need.

Note: The IP Manager service from AirLink is currently not a guaranteed service

though every effort is made to keep it operational 24/7.
When using AirLink’s IP Manager servers, since there are many AirLink modems
using the service, it is even more imperative to have a unique name for your
modem.

-

If the Raven X will be communicating with a device that has a domain name but changes its IP
address frequently (such as another AirLink modem using IP Manager) or is on a network where
devices are accessed by names rather than IP addresses, you will want to put in an alternate DNS
(*DNSUSER) where that domain is updated, such as the IP Manager server the remote modem is
using or the listing of IP addresses to names is kept.

FIGURE 2. Wireless Ace: DNS

*DNS1 and *DNS2 - The primary and secondary DNS servers set by Verizon when your Raven
X gets its IP address.

*DNSUSER - Set this, if desired, to an additional DNS server to query first before the primary
or secondary (just as a hosts file is queried first on a computer). If *DNSUSER is set to 0.0.0.0,
it will be ignored.

*DNSUPDATE - This command sets how often you want DNS Updates to be requested. Oth­erwise the Raven X will only send updates when it is reset, powered up, or the IP address is
granted by network changes.

Raven X EV-DO for Verizon - User Guide, version 2.34 15

IP Manager and DNS

PPP-Peer

The Raven X uses the unqualified domain name of “ppp-peer” when it is in PPP or SLIP address
mode to resolve the address of the device or computer connected via PPP or SLIP address. If the
Raven X is not in PPP or SLIP address mode, “ppp-peer” will resolve to 0.0.0.0.

Note: If you will be using your Raven X to communicate with another AirLink

modem and both are using IP Manager to translate dynamic IP addresses to
domain names, it is recommended that you set *DNSUSER to the IP address for
IP Manager. IP Manager’s updates occur more frequently than Verizon’s DNS
servers decreasing the time between IP address change and address resolution.
Likewise, if your Raven X routinely needs to contact another modem or device
with a Dynamic DNS domain and that modem or device frequently changes its IP
address, you may need to set *DNSUPDATE for frequent updates.

Raven X EV-DO for Verizon - User Guide, version 2.34 16

CHAPTER 5 Data Communication and Host Modes

The Raven X plays the part of a HOST when a computer or another device is connected to its
serial or Ethernet port. The Raven X can also route data to/from the connected device to the cellu­lar network.

Note: The Raven X 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. If you need to have one-to-many routing, you can connect the

Raven X to
a router. The router would provide the multiple routing and the Raven X would
provide one-to-one for the router to the cellular network and the Internet.

As the host, the Raven X can use different communication modes. Some communication modes
are not available for specific port types, explained with the description of the mode type.

AT: The Raven X accepts and responds to standard AT commands.
PassThru: Direct connection to internal hardware (OEM Module) of the Raven X.
Telnet: The Raven X auto-answers TCP connections to allow terminal emulation using either the

Ethernet port or remotely via the cellular connection.
PPP Mode: The Raven X uses PPP to communicate with a device or computer connected to the

serial port.
SLIP Mode: The Raven X uses SLIP to communicate with a device or computer connected to the

serial port.
UDP and UDP PAD: Any data received on the serial port is assembled into UDP packets and sent

to the session’s associated IP address and Port (described later). Any responses received from the
associated IP address and port destined for the modem's Device Port are unwrapped and sent out
the serial port.

TCP and TCP PAD: Any data received on the serial port is packaged into TCP messages and
sent to the associated connection’s IP address and Port (described later). Any data received from
the TCP peer is unwrapped and sent out the port.

By default, the Raven X is in AT Mode and al lows AT Commands to be entered via terminal con­nection (through the local port connection) or remotely (through the cellular network). PassThru
Mode can only be exited by resetting the Raven X. All other modes are entered, for their specific
port, by use of a startup mode command.

Raven X EV-DO for Verizon - User Guide, version 2.34 17

Data Communication and Host Modes

The serial port of the Raven X can be configured to enter any of the modes automatically on
power up (in most cases, this is also after it has registered on the cellular network). This is done
by setting the Startup Mode Default (refer to MD in the AT Command listing, page
desired mode. If this setting is non-zero, the modem will enter the specified mode after 5 seconds.
If you want to cancel this behavior, the ATMD0 command can be used before the 5-second time­out expires.

FIGURE 1. Wireless Ace: MD

87) to the

If the serial port of the Raven X is in any mode other than AT or PassThru, the AT command
mode can be re-entered by:

• Deactivating DTR (if &D2 or Ignore DTR, S211, is not set).

• Issuing the +++ escape sequence (if Disable AT Escape, DAE, is not set).

• Resetting or Power cycling the modem.

Note: DTR needs to be asserted (S211=1 or &D0) by the host before PPP Mode,

SLIP Mode, UDP PAD Mode, or TCP PAD Mode can be entered.

AT Mode

Using a terminal connection, AT commands are used to configure the modem, command it to do
something, or query a setting. For a full listing of the AT commands, refer to page
Ace is a graphical user interface for most AT Commands.

AT commands must always be terminated by <CR> (ASCII character 0x0D), a carriage return
(pressing enter on the keyboard). Some may also include a new line or line feed <LF>.

If E=1 (Echo On), the AT command (including the terminating <carriage return) will be dis­played (output) before any responses.

47. Wireless

Two settings affect the format of AT command output: V (Verbose) and Q (Quiet).

Raven X EV-DO for Verizon - User Guide, version 2.34 18

Data Communication and Host Modes

If Q=1 (Quiet On), no result codes are output whatsoever, so there is no response generated by
a (non query) command.

If Q=0 (Quiet Off), result codes are output. The format of this output is then affected by the
Verbose setting.

If Quiet mode is off, the result code is affected as follows:

For V=1 (Verbose mode), the tex tual resu lt code is surrounded by a carriage return and new
line. Any AT query response is also surrounded by a carriage return and new line.

For V=0 (T erse mode), a numeric result code is output with a single trailing carriage return (no
new line is output), while any AT query response is followed by a carriage return and new line
(there is no preceding output).

For example, possible output to the AT command "AT" with carriage return (assuming quiet mode
is not on) is:

carriage return - if V=0
carriage return and new line OK another carriage return and new line - if V=1

Note: These commands work for the port on which they are executed. For exam-

ple, if the user types ATE1 and then AT&W using a serial port connection, it will
set the serial port to Echo On.

PassThru Mode

In PassThru mode, the Raven X does not behave normally, all port communication is passed
directly between the internal hardware and the computer connected directly to the modem. This
mode can be used to configure hardware-specific settings (for example, provisioning, trouble
shooting, etc.).

Issuing the "AT\APASSTHRU" from a terminal emulation enters this mode. The modem responds
with OK, at which point a direct connection to the internal hardware is established.

With Wireless Ace, you can configure a string of AT commands to be sent to the Raven X when it
enters PassThru and other PassThru settings.

FIGURE 2. Wireless Ace: PassThru

-

Raven X EV-DO for Verizon - User Guide, version 2.34 19

Data Communication and Host Modes

You can configure MD to have the Raven X enter PassThru on start up.

FIGURE 3. Wireless Ace: MD

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.

Caution: PassThru can only be exited by resetting or power-cycling the modem.

This mode cannot be entered via a remote Telnet session.

PassThru Mode allows only specific AT commands. Some ALEOS commands will be unavailable
when the modem is in PassThru mode. The commands usable also depend heavily on the modem
model number (found on the label on the top of the modem).

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 Wireless Ace to connect with the Raven X.

TelnetMode

In Wireless Ace you can configure Telnet operation.

FIGURE 4. Wireless Ace: Telnet Configuration

If you need to change the port for Telnet (for example, you have the default port blocked on your
firewall), the option is on the Other tab. The default telnet port is 2332. You can also change the
T elnet timeout, if the connection is idle, default 2 minutes.

Raven X EV-DO for Verizon - User Guide, version 2.34 20

Data Communication and Host Modes

FIGURE 5. Wireless Ace: Telnet Configuration

PPP Mode

In PPP mode, the Raven X acts as a PPP server, providing an IP address, and DNS servers (if
available) to the Host. PPP mode is entered from the AT mode by using any of the following com
mands:

AT\APPP
ATDT10.0.0.1
ATDT10001
ATD#19788 or #777
CLIENT

-

In response to any of the preceding commands, the modem will respond with CONNECT a car­riage return and new line and is ready for the host to begin PPP negotiations. The IP received by
the host in the resulting negotiation will either be a private (non-routable) IP address or a public
(network-routable) IP address provided by the network, depending on the settings of *HOST

­PRIVMODE. If *HOSTPRIVMODE=1, the value of the private IP address can be determined
beforehand by querying S110. The private IP address to be used can be defined with the command
AT*HOSTPRIVIP=192.168.100.33 substituting the desired IP ad dress.

FIGURE 6. Wireless Ace: PPP/Ethernet

Using a private IP insulates the PPP client from changes in IP addresses of the underlying net­work. The will perform basic NAT-like address translation on all packets.

If a public IP address is being used, any changes in the IP (as determined by the wireless network)
will result in the PPP link to the host being disconnected, requiring the host to reinitiate it. The
public IP is passed to the host in the PPP negotiations, so when the network forces a change, the
modem has to force the host to renegotiate the PPP link to make this happen.

Raven X EV-DO for Verizon - User Guide, version 2.34 21

Data Communication and Host Modes

Slip Mode

SLIP mode is entered be using the "AT\ASLIP" command. As in PPP Mode, the IP address that
the host assumes is affected by the setting of *HOSTPRIVMODE. SLIP does not negotiate the
IP with the host, so before making a SLIP connection, the host SLIP driver must be configured to
use the IP specified by querying S110.

UDP Pad

When the modem is in UDP PAD (Packet Assembly and Disassembly) Mode, all characters
received on the seial port are assembled into UDP packets and sent to the Raven X’s remote IP
address/port, and any packets received from the same IP/port-destined for the Raven X’s device
port (see *DPORT)--are disassembled and dumped onto the serial line.

A UDP session is initiated by one of the following events:

• Using the Dial UDP (DP) AT command (example, ATDP192.168.3.23/3456).

• Setting the Startup Mode Default (MD) to 3 (UDP) so that a UDP session is entered automati-

cally when the modem registers onto the network. Serial data will be sent to the IP/port speci­fied in S53.

• Incoming UDP packets will be processed out the serial port if

• UDP auto answer is enabled (S82=2);

• The destination IP address matches that in S53 (if Friends Mode is enabled, the IP address
also needs to be present on the Friends List);

• Or allow any IP is set (AIP=1);

• The modem is in AT mode (not in a current UDP or TCP session).

UDP packet assembly is affected by the values of S50 (PAD Forwarding Time-out) and S51 (P AD
Forwarding Character). Data received in the serial buffer will be transmitted when the idle inter­character time-out specified in S50 (in tenths of seconds) occurs or when a character is received
that matches S51 (if non-zero).

UDP Auto Answer

UDP auto answer (previously called UDP half-open) is set with S82=2. When set, the Raven X
will automatically establish a UDP session to the source IP address and port of the UDP packet
received. The Raven X will remain "locked" to this one remote IP/port until no data is sent or
received for the time interval defined in the UDP auto answer time-out (S83). During this session,
packets from other IP/port addresses will be rejected, unless *UALL is set. Whether or not an
incoming packet will cause the modem to enter a UDP session is always dependent on the S53
and AIP settings.

The Normal UDP Mode (MD3) can be combined with UDP auto answer to cause the incoming
serial data to be sent in UDP packets (instead of being treated as AT commands), while allowing
sessions to be established from different UDP sources. A UDP session will be initiated either by
incoming serial data or by an incoming UDP packet. The session, started by either method, will
be terminated when no data has been sent or received for the S82 period. Once the session termi
nates, another may be initiated by either means.

Raven X EV-DO for Verizon - User Guide, version 2.34 22

-

Data Communication and Host Modes

When idle, after the time-out has occurred, the modem is in A T command mode on the serial port,
and any valid AT command may be entered during this time.

Note: It is best to ensure the idle time-outs for TCP and UDP are never 0 if you're

going to be using auto-answer, or either PAD mode. In those circumstances, you
will want the modem to close the socket if the connection goes idle for too long,
particularly if the other side doesn’t normally close the connection.

When the session is initiated by serial data, the new session will be established using the destina­tion address specified in S53. The S53 setting can be changed if the connect to last UDP setting
(*UDPLAST=1) is set. The address in S53 will be updated to reflect the address of the last ses
sion initiated by an incoming UDP packet. So that when new data is received over the host serial
port while in the idle state, a session will be re-established with the last address. (This behavior is
the same as the previous Hybrid2 (MD6) mode).

Note: TCP auto answer (S0) may also be set simultaneously with UDP auto

answer. Then, when in the idle state, the modem will accept either a TCP or UDP
incoming packet, and enter a TCP or UDP session as appropriate.

Reliable UDP

-

Reliable UDP adds a simple protocol on top of UDP to provide reliable delivery of data. When
data is received from the host serial port, a 2 byte header is added to the data, containing a mes
sage type and a sequence number. The Raven X will continue to send this data (buffering any
received data in the meantime) until it receives an acknowledgement with this sequence number.
If an acknowledgement is not received within the time-out period (specified in S7), the data will
be retransmitted. This will continue until an acknowledgement is received or the modem is reset.
Likewise any UDP packets received by the Raven X are expected to have this simple header. The
Raven X will issue an acknowledgement for any valid packets which are received.

T o configure the Raven X for a normal UDP session, you need to set the Startup Mode Default to
73 (ATMD73). If you are using two modems, configure the Destination IP and Port in each to
point to each other. Serial data will then be sent reliably between the two.

Note: Although it adds reliability, the simple implementation of the Reliable UDP

mode in the does not check for duplicate packets.

-

UDP Multicast Mode

UDP Multicast mode results in any data received from the host serial port being sent to all the cli­ents in the address list. The remote port number is taken from S53. To avoid flooding the network,
the packets are sent to each client with a 20ms pause in between. The receipt of UDP packets
works as in normal UDP mode (i.e. bound by the value S53 and/or AIP). Since it may take a while
to transmit the data to all hosts (especially if all 20 Modbus entries are used and name resolutions
are required), new data received from the host port is buffered until current transmissions to all
hosts are finished.

Enter the list of target IPs in the address list (ADDR LIST). The index numbers in the list aren't
used. Configure for a normal UDP session. Set the Startup Mode Default to 83 (ATMD83). Con
figure the Destination port to match the device port of the remote modems.

Raven X EV-DO for Verizon - User Guide, version 2.34 23

-

Data Communication and Host Modes

TCP PAD

When the Raven X is in a TCP session, all characters received on the serial port are assembled
into TCP packets and sent to the mode's remote IP address/port, and any packets received from
the remote end of the TCP connection are disassembled and dumped onto the serial line.

A TCP connection is established by one of the following methods:

• Using the Dial TCP (DT) AT command (for example, ATDT192.168.3.23/3456)

• TCP auto answer is enabled (S1), a TCP connection request is received, and the modem is not

in a data session.

• Data is received on the serial port and

• The Startup Mode Default (MD) is 4 (auto TCP)

• The remote TCP destination, as defined in S53, successfully responds to the TCP connection
request.

The value of S7 (TCP Connection Time-out) specifies the number of seconds to wait, after initiat­ing a TCP connection attempt, for a successful connection to be established. If the connection has
not been successfully established before the time-out occurs, ERROR/BUSY is returned.

TCP packet assembly is affected by the values of S50 (PAD Forwarding Time-out) and S51 (PAD
Forwarding Character). Data received in the serial buffer will be transmitted when the idle inter­character time-out specified in S50 (in tenths of seconds) occurs or when a character is received
that matches S51 (if non-zero).

The TCP session will be terminated if no data is transmitted or received for the time interval spec­ified in TCPT and TCPS. TCPT is the number of minutes (TCPS=0) or seconds (TCPS=1) used
for this idle time-out.

Hybrid Modes

Some previous hybrid modes (MD=5, 6) are no longer implemented as special, unique modes.
Now that UDP auto answer (UDP Half-open, S82=2) can be enabled in conjunction with UDP
PAD mode (MD3), effectively this is the same as MD5 and MD6 previously accomplished. Set
ting MD5 and MD6 are still supported, but not recommended.

AT
Command

MD 3 3
S82 2 2
S0 1 1
*UDPLAST 0 1

Hybrid Mode

(MD5)

Hybrid Mode2

(MD6)

-

Raven X EV-DO for Verizon - User Guide, version 2.34 24