Airlink X EV-DO User Manual

Download

Page 1

Raven X EV-DO

User Guide

Version 2.34 - April 2007

Page 2

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

Page 3

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

Page 4

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

Page 5

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

Page 6

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

Page 7

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

Page 8

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

Page 9

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

Page 10

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

Page 11

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

Page 12

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

Page 13

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

Page 14

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

Page 15

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 representative for more information.

FIGURE 3. AceNet

FIGURE 4. AceNet Charting

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

Page 16

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

Page 17

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

Page 18

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

Page 19

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

Page 20

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

Page 21

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

Page 22

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

Page 23

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 cellular 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 connection (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

Page 24

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 timeout 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 displayed (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

Page 25

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

Page 26

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

Page 27

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

Page 28

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 specified 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 intercharacter 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

Page 29

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 destination 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 clients 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

Page 30

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 initiating 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 intercharacter 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 specified 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

Page 31

Data Communication and Host Modes

255.255.255.0

192.168.0.2

192.168.0.1

1 - Use Private IP

Public and Private Mode

By default, the Raven X is in Public Mode and will pass the IP address assigned by the Verizon network to the devices connected to its ports. If you need more control over which gateway address, device address, and netmask that is given out by the DHCP server, you can use the pri vate host mode, *HOSTPRIVMODE, and set the internal network IP addresses. The Raven X will use NAT to forward packets to the end device.

Note: When using Public mode, connect the modem directly to the computer or

other end device. Using a hub or switch may prevent the modem from updating the IP address of the end device when an IP address is received from the Verizon network.

In Wireless Ace, the Private mode settings are part of the PPP/Ethernet group.

FIGURE 7. Wireless Ace: Private Host Mode

• *HOSTPRIVMODE - Set to 1 to enable the explicit IP addresses.

• *HOSTPRIVIP - Set to the IP address you want the Raven X to give to your device.

• *HOSTPEERIP - Set to the IP address you want for the Raven X.

• *HOSTNETMASK - Set to the subnetmask (generally, 255.255.255.0).

Note: 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. The screenshot shows an example.

Internal DHCP Server

DHCP (Dynamic Host Configuration Protocol) has become a primary component of today’s network environments. DHCP allows one server to automatically and dynamically allocate network IP addresses and other network related settings (such as subnet masks, routers, etc.) to each com puter or device without the need to set up each specifically or keep track of what addresses have already been used.

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

Page 32

Data Communication and Host Modes

DHCP and Routing

DHCP is built on a client-server model. The client broadcasts on the local physical subnet to find available DHCP servers (generally only one active per network). The server, when a request is received, reserves an IP address for the requesting client and then sends an IP lease offer to the client which contains the client's MAC address, followed by the IP address that the server is offer ing, the subnet mask, the lease duration, other IP configuration options, and the IP address of the DHCP server making the offer. Upon receipt of an offer, the client configures its interface accordingly.

Routing, at its most basic level, is the process of forwarding data on to the correct destination. One component of routing is address determination, directing data to the correct address either as its final destination or so it can be forwarded on. Selecting gateways where the data can be directed is another important component of routing.

The Raven X acts as a one to one gateway forwarding messages to and from one device that is connected to it. The Raven X does not provide routing for any more than that one device.

DHCP in the Raven X using Public Mode

1. When the Raven X registers on the cellular network, it is assigned an IP address from V erizon,

let’s say A.B.C.D.

2. Acting as a DHCP server, in Public Mode, when the Raven X receives a DHCP request from

an Ethernet device, it hands off the assigned address to the device and sets up the default gate way address as A.B.C.1. If the fourth octet is already a 1, it assigns A.B.C.2 as the router address.

3. The Raven X also sends a /24 netmask (255.255.255.0) and sets up a static route which maps

192.168.13.31 (or the address configured with *HOSTPEERIP if it is changed) to A.B.C.1 (or A.B.C.2 if that was what the gateway address was given as).

Private Mode allows more direct control of the gateway address, device address, and netmask that is given out by the modem’s DHCP server. The IP Address that would be assigned to the end device is configured in the Private Mode settings (see above). Some applications which rely on specific IP addressing for their operation may have issues working in Private Mode when the modem has a non-static IP address.

PPPoE with DHCP

When PPPoE is used with the Raven X, 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 Raven X’s MAC address to send all outgoing packets. To configure your Raven X and your com puter to work with PPPoE, refer to the appendix for PPPoE, page 103.

The AirLink Modem as a Gateway

The primary purpose of the is to forward data from a single device connected to one of the ports to the network and, ultimately, under most circumstances, to the Internet in a one to one gateway configuration.

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

Page 33

Data Communication and Host Modes

When the Raven X obtains its IP Address from the cellular provider, it also obtains Ve ri zon’s routing information necessary to forward messages to Verizon’s routers which can then forward on from there. The Raven X then acts as a router for the device connected to it, forwarding to or from Verizon’ s network.

Caution: The forwards messages to and from the cellular network for only ONE

device per port. The is a one-to-one gateway and does not have advanced routing features required to do one-to-many routing.

Keepalive

Keepalive is used to test the Raven X’ s connection by pinging an IP address after a s pecified period of inactivity . Keepalive is only recommended for users who have a remote terminated modem that infrequently communicates to the network or if you have experienced issues over time where the modem can no longer be reached remotely.

When Keepalive pings the IP address, an acknowledgement indicates there is an active connection to the network. If the Raven X does not receive a response from the IP address, it will make addi tional attempts according to a backoff algorithm before determining the Internet connection is not functioning properly. If it determines the connection is not fucntioning, the modem will then attempt to reconnect to Verizon to reestablish IP connect ivity.

Configuring Keepalive

You can use Wireless Ace or a terminal connection to configure Keepalive (page 47). In Wireless Ace, select Other from the groups menu on the left.

FIGURE 8. Wireless Ace: Keepalive Configuration

*IPPING sets the interval, in minutes, you want Keepalive to test the network connection. To disable Keepalive, set *IPPING to 0 (default setting).

Note: 60 minutes is the minimum time which can be set for Keepalive.

*IPPINGADDR sets the IP address you want to use for the connection test.

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

Page 34

Data Communication and Host Modes

Data usage using Keepalive

Keepalive is an optional feature. If you frequently pass data with your modem, you most likely do not need to have Keepalive enabled. When using Keepalive, be aware that a ping moves approxi mately 66 bytes of data over the network and is billable by the carrier. The following *IPPING settings will incur approximate monthly data usage in addition to any other data usage:

60 minutes 100k / month 120 minutes 50k / month

Caution: If *IPPINGADDR is left blank or is set to an invalid IP address (exam-

ple, an IP which is unreachable or one which is not a valid IP address), modem performance will be adversely affected.

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

Page 35

CHAPTER 6 Modbus/BSAP Configuration

The Raven X supports Modbus ASCII, Modbus RTU, BSAP, and can also emulate other protocols like DF1 or others using its Modbus Variable feature.

Modbus Overview

The Modbus Protocol, developed by Modicon in 1979, provides for client-server (also referred to as master-slave) communications between intelligent devices. As a de facto standard, it is the most widely used network protocol in the industrial manufacturing environment to transfer discrete/ana log I/O and register data between control devices.

Modbus, BSAP, and other Modbus variations are often used in conjunction with telemetry devices.

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

Telemetry is an automated communications process by which data is collected from instruments located at remote or inaccessible points and transmitted to receiving equipment for measurement, monitoring, display, and recording. Transmission of the information may be over physical pairs of wires, telecommunication circuits, radios or satellite.

Remote Terminal Unit (RTU)

Modbus was originally designed to be used in a radio environment where packets are broadcast from a central station (also called master or host) to a group of remote units. Each remote unit, Remote Terminal Unit (RTU), has a hexidecim al identification number (ID). The first part of the broadcast packet contains an RTU ID which corresponds to the ID of one of th e remote units. The Modbus host looks for the ID and sends to only the unit with the matching ID. The RTU would then reply back to the central station.

The RTU connects to physical equipment such as switches, pumps, and other devices and monitors and controls these devices. The RTU can be part of a network set up for Supervisory Control and Data Acquisition.

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

Page 36

Modbus/BSAP Configuration

Supervisory Control and Data Acquisition (SCADA)

Supervisory Control and Data Acquisition (SCADA) describes solutions across a large variety of industries and is used in industrial and engineering applications to monitor and control distributed systems from a master location. SCADA encompasses multiple RTUs, a central control room with a host computer (or network), and some sort of communication infrastructure.

SCADA allows for “supervisory” control of remote devices as well as acquiring data from the remote locations. Programmable Logic Controllers allow for a higher degree of automated SCADA.

Programmable Logic Controller (PLC)

A Programmable Logic Controller (PLC) is a small industrial computer which generally monitors several connected sensor inputs and controls attached devices (motor starters, solenoids, pi lot lights/displays, speed drives, valves, etc.) according to a user-created program stored in its mem ory. Containing inputs and outputs similar to an RTU, PLCs are frequently used for typical relay control, sophisticated motion control, process control, Distributed Control System and comp lex networking.

Modbus TCP/IP

Modbus TCP/IP simply takes the Modbus instruction set and wraps TCP/IP around it. Since TCP/ IP is the communications standard for the Internet and most networked computers, this provides a simpler installation. Modbus TCP/IP uses standard Ethernet equipment.

Raven Modbus on UDP

When AirLink modems are used in place of radios, a Raven X is connected to the central station (host) and a Raven X is connected to each remote unit. When the Raven X is configured for Mod bus with UDP, the Raven X connected to the host can store a list of IP addresses or names with matching IDs. When the host at the central station sends serial data as a poll request, the Raven X at the host matches the RTU ID to a corresponding IP of a Raven X at a remote unit. A UDP packet is assembled encapsulating the RTU ID and serial data transmitted from the host. The UDP packet is then transmitted to the specific Raven X at the remote unit matching the RTU ID. The remote Raven X then disassembles the packet before transmitting the RTU ID and serial data to the remote unit. The remote unit s opera te in nor mal UDP mode and their data i s sent to the host via the remote Raven X and host modem.

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

Page 37

Modbus/BSAP Configuration

FIGURE 1. Automation and Telemetry

Configuring the Raven X

You can use either Wireless Ace, direct serial communication, or Telnet to configure your modem using AT commands (page

47).

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

This section covers a Polling Host with standard Modbus, variations may need additional AT commands.

Configure the listening/device ports for the host and remotes.

The destination port for the modem at the host needs to match the device port in use on all the modems at the remote sites. For example, if the remote modem’s device port (see below) is “12345”, then the Modbus host modem's S53 destination port should be set to “12345”.

In Wireless Ace, select Misc in the side menu.

FIGURE 2. Wireless Ace: Destination Port

Take note of (or set) the Device Port setting in *DPORT to configure the remote modems.

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

Page 38

Modbus/BSAP Configuration

FIGURE 3. Wireless Ace: Device Port

Configure the default mode for start-up.

The default start-up mode will need to be set. In Wireless Ace, select UDP in the side menu. Select the appropriate MD mode from the drop down menu.

FIGURE 4. Wireless Ace: MD Configuration

• MD13: Modbus ASCII

• MD23: Modbus RTU (Binary)

• MD33: BSAP

• MD63: Variable Modbus (individual parameters are set up manually)

Configure IP addresses for the Modbus IDs.

The last step of configuring the modem at the host is setting the IDs to their specific IPs. In Wireless Ace, select the menu option Addr List.

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

Page 39

Modbus/BSAP Configuration

FIGURE 5. Wireless Ace: Addr List

Addresses can be entered in decimal or hex. Wireless Ace will translate hex entries into decimal. The number before the “=” is ID, the number after is the IP address. There can be a total of 100 remote ID/Local addresses entered into the modem.

When using AT commands via telnet or direct serial connection, use ATMLIST for decimal IDs and ATMLISTX for hexi decimal, ex. if the ID is 27 and the IP is 123.123.123.124, you would enter it as ATMLIST27=123.123.123.124 or ATMLISTX1B=123.123.123.124.

Dynamic IP

If you do not have a static IP, the host modem should be configured to report its current IP to a Dynamic DNS (DDNS) server with IP Manager (page

In the Host modem’s configuration, instead of IP address for the Addr List (ATMLIST or ATMLISTX), substitute a single unique name for each modem, i.e. remote1, remote2, etc.

When you configure IP Manager for the host modem, make note of your modem name and domain setting in Wireless Ace in the menu selection Dynamic IP to be used with the remote modems.

FIGURE 6. Wireless Ace: Modem Name and Domain

11).

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

Page 40

Modbus/BSAP Configuration

With names instead of IP addresses for the Address List, the host modem will query the DNS server for the current IP address assigned to the specific name of a remote modem to send a mes sage corresponding to the ID.

When you use names instead of IP adrresses, to ensure your modems are updated quickly with the correct IP addresses for the names, you will want to set the DNS settings as well. In Wireless Ace, select DNS.

FIGURE 7. Wireless Ace: DNS

Configure *DNSUSER to the same IP address as the IP Manager (*IPMANAGER1). If your modems have dynamic IP addresses and not static (the IP address can change when it is powered up), configure *DNSUPDATE to a low interval to allow frequent updates.

Configuring the Remote Modems for Modbus with UDP

This section covers standard Modbus, variations may need additional commands.

Configure the ports for the host.

The destination port for the modem at the host needs to match the device port in use on all the modems at the remote sites. For example, if the remote modem’s device port (see below) is “12345”, then the Modbus host modem’s S53 destination port should be set to “12345”.

In Wireless Ace, select Misc in the side menu. Set the destination port (S53) to match the device port of the host modem (*DPORT, above). Make sure the device port of the remote modem (*DPORT) matches the destination port of the host modem (S53, above).

Configure the default mode for start-up.

Each modem at the remote locations will need to be configured to communicate with the modem at the host. In Wireless Ace, select UDP in the side menu. Enable S82, UDP auto answer, and set S83 to the idle timeout applicable to your application.

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

Page 41

Modbus/BSAP Configuration

2 - Enable

FIGURE 8. Wireless Ace: UDP Power-up Mode

Configure IP addresses for the host.

If the Host modem has a static IP address, enter it in the Destination Address for S53. In Wireless Ace, select Misc in the side menu.

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.

FIGURE 9. Wireless Ace: Destination IP

Dynamic IPs

If you do not have static IPs, the remote modems need to be configured to report their current IPs to a Dynamic DNS (DDNS) server with IP Manager (page the modem to the names specified in the host modem’s MLIST or MLISTX for the connected RTU.

11). You will need to match the name of

Instead of an IP, for S53, specify the name of the host modem (*MODEMNAME). If the remote modems are using a different DDNS than the host modem, you will need to specify the fully quali fied domain name (*MODEMNAME+*DOMAIN).

With a name instead of IPs for th e host mo dem, t he remo te modems will quer y th e DNS server for the current IP assigned to the host modem before sending data back to the host.

Configure other RTU settings.

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

Page 42

Modbus/BSAP Configuration

Other parameters may need to be changed, but this is dependent on the RTU type being used. As a minimum, this typically involves setting the proper serial settings to match your RTU.

Mount the modem at the host or with the RTU.

FIGURE 10. Raven mounted in an enclosure with an RTU

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

Page 43

Modbus/BSAP Configuration

FIGURE 11. Power Connections

FIGURE 12. RTU to Raven setup

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

Page 44

CHAPTER 7 Hardware Installation

Primary Cellular Receive Diversity

Pow er

Ethernet

Serial

Your AirLink Raven X should be mounted in a position that allows easy access for the cables so they are not bent or constricted. The LEDs on the front panel should be visible for ease of opera tional verification. Y ou should ensure that there is adequate airflow around the modem but that it is kept free from direct exposure to the elements (sun, rain, etc.)

The integrated mounting with keyhole screw mounts on the Raven X will allow you to secure your modem nearly anywhere, quickly and easily, without the need for a seperate bracket.

Modem placement with grounding information and diagrams of the mounting tabs can be found in the Appendix, “Modem Placement” on page

FIGURE 1. Raven X connecters

42.

Connecting the Antennas

Antennas selected should not exceed a maximum gain of 5 dBi under standard installation configuration. In more complex installations (such as those requiring long lengths of cable and/or multiple connections), it’s imperative that the installer follow maximum dBi gain guidelines in accordance with the FFC’s regulations.

Your AirLink Raven X will work with most Dual-Band PCS cellular antennas with a connector that works in the high and low frequencies of EV-DO . Connect the primary antenna or primary RF cable directly to the antenna connector on the back of the Raven X.

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

Rx Div) on the back of the Raven X.

Page 45

Hardware Installation

Connecting Power

Y our Raven X can be used with either DC (available in most automobiles) or 110 AC (standard US wall power) with the appropriate power adapter (available from AirLink).

The power cable positive lead should be connected to the battery or power source positive terminal. The power cable negative lead should be connected to the battery or power source negative terminal.

Use of receive diversity for EV-DO is optional. Data transmission and reception will not be adversely affected if it is not used.

Note: When using a DC power source (such as a car battery or solar cell), AirLink

recommends placing a fuse (1-2 Amp) on the line close to the power source to pro tect your power source from possible surges due to shorts or other line issues.

Connecting the Raven X to a computer or other device

Your Raven X’s Ethernet port can be connected directly to a computer or other Ethernet device with either a cross-over cable or a straight-through cable. The Ethernet port on the Raven X is auto-sensing. The Ethernet port will also auto-detect the speed of the connecting device and com municate at 100baseTX or 10baseT.

Your Raven X’s serial port can be connected directly to most computers or other devices using a standard straight through cable. If you have a DCE device, you will need a null modem or null modem cable.

Note: The serial port on your cannot be used to connect to the Internet.

Raven X Indicator Lights

When your Raven X is connected to power and an antenna, there is a specific pattern to the lights to indicate its operation mode.

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

Page 46

Hardware Installation

Network - Indicates a successful connection to the cellular network with an IP address given and a channel acquired.

Signal - Light shows the strength of the signal and may be nearly solid (strong signal) or flashing (weaker signal). A slow flash indicates a very weak signal.

Activity - Lights will flash as data is transferred to and from the Raven X on the remote network. Service - Indicates when the connection is EV-DO. Unlit indicates 1x. Power- Indicates the power adapter is connected and there is power getting to the modem. .

The Reset button has two funtions. If it is quickly depressed and released, the modem will simply power cycle the internal hardware. If, however, the reset is depressed and held for several sec onds (count 10 slowly), the ALEOS configuration settings will return to the factory defaults.

FIGURE 2. Raven X indicator lights

Caution: If you reset the modem configuration using the reset button, you may

need to reactivate your Raven X with Verizon.

Light Patterns

The LEDs on the front of the modem will respond in different patterns to indicate modem states.

• Normal - Each LED, mentioned above, lit as applicable.

• Start up - The LEDs will cycle from left to right.

• Passthru - Network and Single LEDs will blink in tandem. The Activity LED will blink

when transmitting or receiving data.

• Configuration Reset - The LEDs will cycle left to right and then right to left 4 times.

• Authenication Failure - The Network, Signal, and Activity LEDs blink every 2 seconds.

• Data Retry - The Network, Signal, and Activity LEDs blink every 3 seconds.

• SOS - The Network and Service LEDs will blink alternate to each other.

Trouble Indicators (combined with any of the above)

• Invalid MAC Address or Ethernet Initiation Fail - The Service LED will blink.

Monitoring Power-In Voltage and Internal Temperature

The current status of the power-in voltage and the internal (board) temperature, in Celsius, can be monitored in Wi reless Ace.

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

Page 47

Hardware Installation

FIGURE 3. Wireless Ace: *POWERIN and *BOARDTEMP

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

Page 48

APPENDIX A Modem Placement

Front

A radius: 0.14” (2.5mm) B radius: 0.075” (1.9mm) C to C: 0.565” (14mm) D to D: 0.315” (8mm) E to E: 0.132” (3.3mm)

F to F: 0.315”(8mm) G to G: 2.145” (54.48mm) H to H: 1.895”(48.13mm) I to I: 0.565” (14.35mm) K to K: 0.665”(16.89mm) L to L: 0.257” (6.53mm) M to M: 5.385”(136.7mm) N to N: 4.615” (117mm)

FGHI

5.642”(143mm)

(65mm)

2.5”

When decided on a location to install your Raven X, make sure the modem will be away from direct exposure to the elements (sun, rain, etc.). Excess cables can be bundled and tied with twistties or other appropriate binders, but the less the cable is wrapped and bound together, the better the modem will perform.

Built in Mounting Tabs for Raven X

The Raven X is equipped with mounting tabs so there is no need for a seperate bracket. #6 screws are recommended, though other solutions may be sufficient as well.

FIGURE 1. Diagram of the Raven X bottom, showing the placement of the moun ting holes

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

Page 49

Modem Placement

Installing a Raven with an RTU

The Raven can be installed in the same enclosure with an RTU and share the power supply. The power cable positive lead should be connected to the battery or power source positive terminal. The power cable negative lead should be connected to the battery or power source negative termi nal. The Raven has an internal polysilicon circuit breaker that opens at 0.5 to 1.0 amps of current.

FIGURE 2. Raven / RTU

FIGURE 3. RTU Raven

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

Page 50

Modem Placement

FIGURE 4. Raven mounted in an enclosure with RTU

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

Page 51

APPENDIX B Specifications for the Raven X EV-DO

1. Primary Antenna - 50 Ohm TNC

2. Receive Diversity Antenna - 50 Ohm SMA

3. Ethernet: 10/100 Mbps RJ-45

4. Serial: RS-232 DB9-Female DCE (300230400 baud)

5. Status LEDs: Power, Network, Signal, Activity, Service

Physical Characteristics:

• Weight: 0.7 lbs

• Size: height 1.4" (36mm), length 2.5" (65mm) x width 4.6" (117mm)

width with mounting tabs 5.75” (146mm)

Data Services & RF Features

• Full duplex transceiver

• Dual-band Usupport for both 800 MHz cellular and 1.9 GHz PCS bands

• Dual band Receive Diversity

• EV-DO Rev A

• 1x fall back: Adheres to CDMA authentication as specified in CDMA2000 1X

• EVDO Rev A - Data rates up to 3.1 Mbps downlink (450-850 typical) , 1.8 Mbps uplink 300-

400 Kbps typical)

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

• EVDO Rev 0 - Data rates up to 2.4 Mbps downlink (300-500 Kbps typical), 153.6 Kbps uplink

(60-90 Kbps typical)

• CDMA/1x - Data rates up to 153.6 Kbps downlink (60-90 Kbps typical), 153.6 Kbps uplink (60-90 Kbps

typical)

Page 52

Specifications for the Raven X EV-DO

< - > GND (Ground) < - DTR Data Terminal Ready)

< - Rx (Receive)

- > Tx (Transmit)

- > DCD (Data Carrier Detect)

Unused

CTS (Clear to Send)

< -

RTS (Request to Send) - >

DSR (Data to Send) < -

Environmental:

• Certifications: Class 1 Div 2, parts A, B, C, & D

Power Management:

• Low power consumption

• Dormant connection (idle for 10-20 seconds): 104 mA at 12 VDC

• Input Voltage: 9 VDC to 28 VDC

• Input Current: 20 mA to 350 mA

Power consumption

Modem

Raven X 85/104 mAh 239-270 mAh 239-270 mAh

Serial Port Pinouts

The cable between the Raven X and a computer or other serial device needs to be wired straightthrough (pin 1 goes to pin 1, pin 2 to pin 2, etc.). If your end device connected to the Raven X is a DCE device, you will need a null-modem cable.

FIGURE 1. : Female DB-9 DCE

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

Page 53

APPENDIX C AT Commands

Using Wireless Ace

With Wireless Ace, you only need to find the command listed and then enter the new value in the space provided. For those commands which have specific parameters, the choices will be in a drop down menu.

FIGURE 1. Wireless Ace: Entering new configuration values

To set or commit the changes in the modem, use the Write button at the top of Wireless Ace interface.

FIGURE 2. Wireless Ace: Tool bar

For more information on using Wireless Ace, please refer to the Wireless Ace User Guide.

With Wireless Ace, you can create a template from one modem and then use that template to configure other modems in the exact same way. You can use the tem

plate in AceNet, too, to configure several modems at the same time with the same parameters.

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

Page 54

AT Commands

FIGURE 3. Wireless Ace: Save / Load a Template

FIGURE 4. AceNet: Load a Template

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

Page 55

AT Commands

Using Telnet Terminal Emulation

It is possible to communicate with the Raven X across a TCP/IP network. Telnet provides a terminal style connection to the Raven X.

Most installations of Microsoft Windows come with a version of HyperTerminal (used here for specific directions), but you can use any other Telnet application, such as Putty, Terra Term, etc.

Start>All Programs>Accessories>Communications>HyperTerminal

1. Choose a name for your connection, such as Raven X or AirLink. The name and icon are only

for your own reference so you can find the connection at a later date (if you want to have a con nection saved for both local and remote, it is recommended the connection name reflect the connection type (example, Raven X Remote).

FIGURE 5. HyperTerminal: Connection Name

2. Select TCP/IP (Winsock) for Connect Using. If the modem is connected directly to your com-

puter’s Ethernet port, put in the host address of 192.168.13.31 or the *HOSTPEERIP. If the modem is remote, the host address will be the current Internet IP of the Raven X. Change the port number to 2332 (default telnet port for the Raven X).

FIGURE 6. HyperTerminal: TCP/IP Settings

3. When HyperTerminal connects to the Raven X, you will be prompted for a password. The

default password is 12345. When you press Enter, you should get back a reply of “OK”.

FIGURE 7. HyperTerminal: AT mode via Telnet

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

Page 56

AT Commands

4. Type AT and press Enter. You should get a reply of “OK” or “0”.

5. T o see what you are typing as you type it, you will need to turn on the echo and verbose mode.

Type ATE1V1 and press Enter.

If you get a reply of “OK”, then you entered the command successfully. If you get a reply of “0” or “ERROR”, try entering the command again.

Note: You may need to enable Telnet Echo in your terminal emmulation applica-

tion in order to see the commands you type as you type. In HyperTerminal, select

File > Properties. Select the Settings tab. Click the ACSII Setup button. Check Echo typed characters locally.

Direct Serial Connection

Using HyperTerminal, included with most installations of Microsoft Windows:

Start>All Programs>Accessories>Communications>HyperTerminal

1. Choose a name for your connection, such as Raven X or AirLink (if you want to have a con-

nection saved for both local and remote, it is recommended the connection name reflect the connection type, i.e. Raven X local). The name and icon are only for your own reference so you can find the connection at a later date.

FIGURE 8. HyperTerminal: Connection Name

2. Select COM1 (or the comport to which the modem is connected) for the Connect Using.

FIGURE 9. HyperTerminal: Comport Setting

3. Change the Bits per Second to 115200 (default), Data Bits to 8, Parity to None, Stop Bits to

1, and Flow Control to Hardware.

Note: If you have configured the Raven X for settings different than the defaults

for Bits per Second, Data Bits, Parity, and/or Stop Bits, you will need to use your changed settings.

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

Page 57

AT Commands

FIGURE 10. HyperTerminal: Comport Settings

4. Type AT and press Enter. You should get a reply of “OK” or “0”. .

5. T o see what you are typing as you type it, you will need to turn on the echo and verbose mode.

Type ATE1V1 and press Enter.

If you get a reply of “OK”, then you entered the command successfully. If you get a reply of “0” or “ERROR”, try entering the command again.

Using AT Commands with a Terminal Application

• The following pages list the AT commands, their parameters, and explain what they do. For

most commands, when you are entering them using a terminal connection, you will need to preface the command with AT (exceptions are noted), i.e. ATA which listed as A

• Some commands have specific parameters while other commands will take whatever you type.

• Acceptable parameters and/or specific formats are in the parameters column.

• Required variable parameters are denoted with italicized text, example, Dn. The n is variable

and noted in the parameters column.

• Optional parameters are denoted with square brackets [ ].

• Most commands with parameters can be entered with ? to read the current value (for example,

AT&D? will respond with “2” if the default has not been changed).

• AT Commands are not case sensitive. A capital “E” is the same as a lower-case “e”.

• When you are using a terminal connection, if you enter a command which is recognized by the

Raven X, it will respond with “OK”. If the command is not recognized, the response will be “ERROR”.

• Those commands applicable only to certain model numbers of the Raven X will be noted.

Caution: Symbols listed with commands, such as /, &, or ?, are part of the com-

mand and must be included.

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

Page 58

AT Commands

AT Command Listing

Symbols

$QCMIP . . . . . . . . . .91

. . . . . . . . . . . . .63

. . . . . . . . . . . . .64

. . . . . . . . . . . . .56

. . . . . . . . . . . . .64

*AUTOPRL *CSX1 *DATE *DATZ *DBGCOMLVL *DBGDHCPLVL *DBGETHLVL *DBGIPLVL *DBGPPPLVL *DNS *DNSUPDATE *DNSUSER *DOMAIN *DPORT *DU *ENQ *ETHMAC *EVDODIVERSITY *HOSTAUTH *HOSTMODE *HOSTNETMASK *HOSTPAP *HOSTPEERIP *HOSTPRIVIP *HOSTPRIVMODE *HOSTPW *HOSTUID *IPMANAGER *IPMGRKEY *IPMGRUPDATE *IPPING *IPPINGADDR *MODEMNAME *MSCIUPDADDR *MSCIUPDPERIOD *NETALLOWZEROIP *NETCHAN *NETIP *NETOK *NETOP *NETPHONE *NETPHONE? *NETPW *NETROAMPREF *NETRSSI *NETSERV *NETSMS2EMAIL *NETSTATE

. . . . . . . .54

. . . . . . . . . . .75

. . . . . . . . . . .59

. . . . . . . . . . .79

. . . . .84

. . . . . .84

. . . . . . .84

. . . . . .85

. . . . . . . . . . .70

. . . . . .70

. . . . . . .70

. . . . . . . .71

. . . . . . . . . .59

. . . . . . . . . . . .68

. . . . . . . . . . .66

. . . . . . . .55

. . .92

. . . . . . .73

. . . . . .55

. . . .73

. . . . . . . .59

. . . . .73

. . . . . .73

. . .74

. . . . . . . .74

. . . . . .71

. . . . . . .72

. . . .72

. . . . . . . . .80

. . . . .80

. . . . .72

. . . .80

. .80

.59

. . . . . . . .55

. . . . . . . . . .5 5

. . . . . . . . .55

. . . . . . . . . .55

. . . . . . .55

. . . . . .59

. . . . . . . . .59

. . . .92

. . . . . . . .55

. . .78

. . . . . . .55

*NETUID *NETWDOG *PPPNOCARRIER *PRLDIAL *PRLSTATUS *PROVISION *PROVISION2 *PTINIT *PTREFRESH *RESETPERIOD *SMTPADDR *SMTPFROM *SMTPSEND *SMTPSTATUS *SMTPSUBJ *SMTPUSER *SNMPPORT *SNMPSECLVL *SNMPTRAPDEST *SNTP *SNTPADDR *STATICIP *STATUSCHK *TELNETTIMEOUT *TPORT *UALL *UDPLAST *USD +++ +CSQ +CTA +ECIO +PRL ~NAMLCK ~NAMVAL

A . . . . . . . . . . . . . 62

A/ AIP APASSTHRU

D . . . . . . . . . . . . . 62

DAE

E . . . . . . . . . . . . . . 62

FM . . . . . . . . . . . . 82

H . . . . . . . . . . . . . 62

HOR

I . . . . . . . . . . . . . . 54

IPL

. . . . . . . . 59

. . . . . . 80

. . . 64

. . . . . . . . 60

. . . . . 56

. . . . . 92

. . . . . . . . . 75

. . . . . 75

. . . . 75

. . . . . . 77

. . . . . . 78

. . . . 78

. . . . . . 77

. . . . . . 80

. . . . 81

. . 81

. . . . . . . . . . 81

. . . . . . 81

. . . . . . . 60

. . . . . 60

. . 81

. . . . . . . . . 81

. . . . . . . . . . 68

. . . . . . . 69

. . . . . . . . . . 69

. . . . . . . . . . . 61

. . . . . . . . . . 56

. . . . . . . . . . 91

. . . . . . . . . . 56

. . . . . . . . . . . 56

. . . . . . . 91

. . . . . . . 92

. . . . . . . . . . . . . 62

. . . . . . . . . . . . 67

. . . . . . 76

. . . . . . . . . . . . 79

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

. . . . . . . . . . . 67

. . . . . . . . . . . . 87

MDhh . . . . . . . . . . . 67

MLIST

. . . . . . . . . . 87

MLISTX MVLEN MVMSK MVOFF MVOPT MVTYP

OPRG . . . . . . . . . . . 58

Q . . . . . . . . . . . . . . 63

RKEY . . . . . . . . . . . 88

S0 . . . . . . . . . . . . . 65

S221 S23 S53 S60 S7 S82 S83

TCPS . . . . . . . . . . . 66

TCPT

V . . . . . . . . . . . . . . 63

X . . . . . . . . . . . . . . 63

Z . . . . . . . . . . . . . . 63

. . . . . . . . . 87

. . . . . . . . . . 87

. . . . . . . . . . 88

. . . . . . . . . . . 66

. . . . . . . . . . . . 63

. . . . . . . . . . . . 58

. . . . . . . . . . . . 65

. . . . . . . . . . . . . 65

. . . . . . . . . . . . 68

. . . . . . . . . . . 66

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

Page 59

AT Commands: Information and Status

Information and Status

Most of the commands in the “Info” and “Status” groups as well as other groups have read-only parameters. They only provide information and cannot be changed using Wireless Ace (some can be changed using AT Commands with a terminal application).

Note: Those commands which are not displayed with Wireless Ace may require

PassThru mode.

FIGURE 1. Info Group

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

Page 60

AT Commands: Information and Status

FIGURE 2. Status Group

I[n]

n=0 Product name (for example, Raven X Raven-E). n=1 The Raven X’s firmware (ALEOS) version, hardware ID, and copyright. n=2 The internal hardware's firmware version and relevant hardware ID. n=3 The hardware module's unique ID (ESN). n=5 View active profile (the contents of the active registers).

N=5 is not displayed with Wireless Ace.

*AUTOPRL

Next Scheduled PRL Update.

*DEVICEID?

The 64-bit device ID the modem uses to identify itself to the cellular network.

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

Page 61

AT Commands: Information and Status

*ETHMAC?

Ethernet Mac Address.

*HOSTMODE?

The current host mode (AT, PPP, UDP, etc.). If the Raven X is not in AT mode, telnet into the modem to execute this command.

*NETCHAN?

The current active EV-DO/CDMA channel number.

*NETERR?

The EVDO or CDMA network frame error rate.

*NETIP?

The current IP address of the modem reported by the embedded OEM module (generally obtained from Verizon your cellular carrier). This is the address to which packets can be sent in order to contact the

Raven X modem from the Internet.

Use *NETALLOWZEROIP if you need to allow the display of an IP ending in a zero . Note: If there is no current network IP, 0.0.0.0 may be displayed .

*NETOP?

The current cellular carrier (for example, Verizon) from th e mod em's fir mw a re versi on.

*NETPHONE?

The modem's phone number (if applicable or obtainable).

*NETRSSI?

The current RSSI (Receive Signal Strength Indicator) of the Raven X as a negative dBm value. The same information is displayed with the command S202?.

*NETSERV?

The type of service being used by the modem (for example EV-DO).

*NETSTATE?

The current network state:

• Connecting To Network

The Raven X is in the process of trying to connect to the EV-DO network.

• Network Authentication Fail

Authentication to the EV-DO network has failed. Verify settings to activate the Raven X.

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

Page 62

AT Commands: Information and Status

• Data Connection Failed

The Raven X failed to connect, and it is now waiting a set time interval before it attempts to reconnect.

Verify settings to activate the Raven X.

• Network Negotiation Fail

Network connection negotiation failed. This is usually temporary and often clears up during a subsequent attempt.

• Network Ready

The Raven X is connected to the EV-DO network and ready to send data.

• Network Dormant

The Raven X is connected to the EV-DO network, but the link is dormant. It will be woken up when

data is sent or received.

• No Service

There is no EV-DO network detected.

• Hardware Reset

The hardware module is being reset. This is a temporary state.

*PRLSTATUS

The status of the most recent PRL Update.

• 0 : None

• 1 : In Progress

• 2 : Success

• Any other value : Failure

View active profile (the contents of the active registers).

Not displayed with Wireless Ace.

+ECIO?

The CDMA EC/IO value.

+PRL?

Preferred Roaming List (PRL) version.

Information Displayed in Wireless Ace without AT Commands Listed

• Bytes and Packets Received and Sent

Network traffic for the applicable port.

• Number of System Resets

Counter of the number of system resets over the life of the modem or since the configuration was reset.

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

Page 63

AT Commands: Information and Status

• Bad Password Count

Counter of the number of bad password attempts.

• IP Reject Count or Log

Rejected IP Data.

• Versions of ALEOS, internal hardware, boot, and MSCI

Versions of internally configured hardware and software.

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

Page 64

AT Commands: Misc (Miscellaneous)

Misc (Miscellaneous)

This group includes configuration commands which are not specific to other groups.

The commands displayed in Wireless Ace and the results of those commands depends on the model of the modem.

FIGURE 1. Common : Misc

OPRG=n

Enables/disables over-the-air firmware upgrading of the Raven X.

When AirLink releases a new verison of ALEOS, you can upgrade your remote modems with OPRG enabled.

n=0 : Disables n=1: Enables

S53=[method][d.d.d.d][/ppppp]

Destination IP address, port, and method. These are used as defaults for the D (Dial) AT command.

method= P : UDP method=T : TCP method=N : Telnet d.d.d.d=IP address or name ppppp=the port address

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

Page 65

AT Commands: Misc (Miscellaneous)

Examples:

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

Telnet to the specified IP at port 12345.

ATS53=192.168.100.23/12345

Query the specified IP at port 12345.

ATS53=/12345

Query port 12345.

*DATE=[mm/dd/yyyy],[hh:mm:ss]

Sets and queries the clock in the unit. Either the date and time can be specified, or simply one of the two can be specified in which case the unspecified value will remain unchanged. The date and time are always specified 24-hour notation.

mm/dd/yyyy = month, day, year hh:mm:ss = time in 24-hour notation

*DPORT=n

The modem's Device Port which the modem is listening on for inbound packets/data/polls.. Can also be set with the command S110.

n=1-65535

*HOSTPAP=n

Use PAP to request the user login and password during PPP negotiation on the host connection.

n=0 : Disable PAP request (Default). n=1 : Takes user login and password from Windows DUN connection and copies to *NETUID and

*NETPW.

*NETALLOWZEROIP=n

Allows the displayed IP address in *NETIP to end in zero (ex. 192.168.1.0).

n=0 : Do not allow n=1 : Allow

*NETPW=pw

The password that is used to login to Verizon’s cellular network, when required. pw=password

*NETPHONE?

The modem’s phone number, if applicable or obtainable.

*NETUID=uid

The login that is used to login to Verizon’s cellular network, when required.

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

Page 66

AT Commands: Misc (Miscellaneous)

uid=user id (up to 64 bytes)

*PRLDIAL=n

Update the PRL by contacting Verizon.

n=0 : Disabled n=1 : Update PRL.

*STATICIP=d.d.d.d

Set the static IP required to be received from the network. If the modem does not get this IP address from the network, it will reset the internal hardware and try again. The default is

0.0.0.0, which allows any IP address from the network. d.d.d.d=IP address

Example: AT*STATICIP=192.168.1.23

Caution: *STATICIP does not set the IP address of the modem, it merely tells the

modem which IP address to expect. If the expected IP address is not granted while registering on the cellular network, the modem will try to register on the network again until it receives that IP address. If your account is set up for a dynamic IP address and you set an address for *STATICIP, you may not be able to register on the network at all since there is no guarentee you will receive the same dynamic IP address again.

*STATUSCHK=n

Checks if an SMS message has been received by the modem.

n=1-255 : Seconds between checks. n=0 : Never check.

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

Page 67

AT Commands: Serial

Serial

This group includes commands specific to the serial port.

FIGURE 1. Common : Serial

+++

Note: This command 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.

The “+” is ASCII 0x2B.

AT Escape sequence.

If the Raven X is in a data mode (any mode other than PassThru), this command causes the modem to re-enter AT command mode.

Cannot be configured in Wireless Ace.

Note: This command does nothing if DAE=1.

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

Page 68

AT Commands: Serial

D[method ][d.d.d.d][/ppppp] or D[method][@name][/ppppp]

Note: This command is not proceeded by AT.

Re-execute last command.

Cannot be configured in Wireless Ace.

Manually answer an incoming connection.

Cannot be configured in Wireless Ace.

Dial a connection to a remote IP and Port using method.

Cannot be configured in Wireless Ace.

method=P : Establish a UDP connection method=T : Establish a TCP connection method=N : Establish a Telnet connection d.d.d.d=IP address to contact ppppp=IP port to contact

Examples:

ATD - Dial (establish) default connection. ATDP192.168.13.31/2332 - Dial (establish) UDP session to 192.168.13.31, at port 2332.

To end the connection, issue the +++ escape sequence or drop the DTR line (if Ignore DTR S211=0 or &D2).

The defualt connetion is set in S53.

Toggle AT command echo mode.

n=0 : Echo Off n=1 : Echo On

Note: All connections types (serial and Telnet) are affected by the echo command.

Hang-Up Command.

n=1: Hang-up

Cannot be configured in Wireless Ace.

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

Page 69

AT Commands: Serial

S23=[speed],[databits][parity][stop bits]

The AT quiet-mode setting. If quiet mode is set, there will be no responses to AT commands except for data queried.

n=0 : Off (Default) n=1 : Quiet-mode on

Serial line parameters. The settings take affect after reset.

speed=300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200 | 230400 databits=7 or 8 parity=O : Odd parity=E : Even parity=N : None parity=M: Mark stopbits=1 | 1.5 | 2

Example: ATS23=19200,8N1 (sets modem to 19200, etc.) Can also be set using &L=[speed],[databits] [parity][stop bits]

Note: Databits MUST be 8 data bits for PPP mode.

Command Response Mode.

n=0 : Terse (numeric) command responses n=1 : Verbose command responses (Default).

Extended Call Progress Result mode.

n=0 : Turn off extended result codes (Default). n=1 : Turn on result codes. This adds the text 19200 to the CONNECT response.

Reset the Raven X.

In Wireless Ace, this command is performed with the Reset option on the toolbar.

Note: This command does nothing if *DATZ=1.

&Cn

Set DCD mode.

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

Page 70

AT Commands: Serial

&Dn

&Sn

n=0 : Always assert DCD. n=1 : Assert DCD when in a data mode (UDP, TCP, PPP, or SLIP) (Default). n=2 : Assert DCD when the modem has network coverage.

Set DTR mode.

n=0 : Ignore DTR, same effect as HW DTR always asserted (same as S211=1). n=2 : Use hardware DTR (same as S211=0).

Set DSR mode.

n=0 : Always assert DSR (Default). n=1 : Assert DSR when in a data mode (UDP, TCP, PPP, or SLIP) . n=2 : Assert DSR when the modem has network coverage.

Writes all changed modem settings. If this command is not issued, any modified values will revert back to their previous values at modem reset.

Cannot be configured in Wireless Ace.

*PPPNOCARRIER=n

Provides a “No Carrier” message to a device connected to the serial port using PPP or CHAP when the cellular connection becomes unavailable.

n=0 : Disabled (Default). n=1 : Enabled.

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

Page 71

AT Commands: TCP

TCP

This group includes commands specific to TCP communications.

FIGURE 1. Common : TCP

S0=n

This register determines how the Raven X responds to an incoming TCP connection request. The Raven X remains in AT Command mode until a connection request is received. DTR must be asserted (S211=1 or &D0) and the Raven X must be set for a successful TCP connection. The Raven X will send a “RING” string to the host. A “CONNECT” sent to the host indicates acknowledgement of the connection request and the TCP session is established.

n=0 : Off (Default) n=1 : On n=2 : Use Telnet server mode on TCP connections. n=3 : With a Telnet connection, overrides the client's default echo, allowing the server on the host port to

perform the echo. CRLF sequences from the telnet client will also be edited to simply pass CRs to the server on the host port.

S7=n

Specifies the number of seconds to wait for a TCP connection to be establish e d when di aling out.

n=seconds

S60=n

T elnet Client Echo Mode.

n=0 : No Echo n=1 : Local Echo (Default) n=2 : Remote Echo

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

Page 72

AT Commands: TCP

S221=n

Connect Delay:

n= 0 - 255

Number of seconds to delay the “CONNECT' response upon establishing a TCP connection.

Number of tenths of seconds to delay before outputting ENQ on the serial port after the CONNECT when the ENQ feature is enabled (see *ENQ).

TCPS=n

TCP connection time-out (TCPS) units. Specifies a time interval upon which if there is no in or outbound traffic through a TCP connection, the connection will be terminat ed.

n=minutes (TCPS=0) or seconds (TCPS=1)

TCPT=n

TCP connection time-out (TCPT) units. Specifies a time interval upon which if there is no in or outbound traffic through a TCP connection, the connection will be terminat ed.

n=minutes (TCPT=0) or seconds (TCPT=1)

Note: This value only affects the TCP connection in TCP PAD mode.

*ENQ=n

Outputs an ENQ [0x05] after the TCP CONNECT delayed by the Delay Connect Response time (S221).

n=0 : Disabled (Default). n=1 : Enables ENQ on CONNECT.

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

Page 73

AT Commands: UDP

UDP

This group includes commands specific to UDP communications.

FIGURE 1. Common : UDP

AIP=n

Allow IP address.

n=0 Allow only the IP address specified in S53 to connect when UDP auto answer is enabled (S82=2). n=1 Allow any incoming IP address to connect when UDP auto answer is enabled (S82=2).

Note: Always subject to any Friends filters that may be defined.

HOR=n

Half-Open Response - In UDP auto answer (half-open) mode:

n=0 No response codes when UDP session is initiated. n=1 RING CONNECT response codes sent out serial link before the data from the first UDP packet.

Note: Quiet Mode must be Off.

MDhh

Default power-up mode for the serial port. When the Raven X is power-cycled, the serial port enters the mode specified by this command

after 5 seconds. On startup, typing ATMD0 within 5 seconds changes the mode to normal (AT command) mode.

hh (hex byte)=00 : normal mode

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

Page 74

AT Commands: UDP

hh=01 : SLIP mode hh=02 : PPP mode hh=03 : UDP mode hh=04 : TCP mode hh=07 : PassThru mode hh=0F : PinPoint MDT hh=13 : Modbus ASCII hh=23 : Modbus RTU (Binary) hh=33 : BSAP hh=63 : Variab le M odbu s hh=73 : Reliable UDP hh=83 : UDP Multicast

See also S53 to set the port for UDP or TCP.

S82=n

Enables UDP auto answer (half-open) mode.

n=0 : Normal mode n=2 : Enable UDP auto answer mode.

S83=n

Set or query UDP auto answer idle time-out. If no data is sent or received before the time-out occurs, the current UDP session will be terminated. While a session is active, packets from other IP addresses will be discarded (unless *UALL is set).

n=1 - 255 Time-out in seconds. n=0 : No idle time-out (Default).

*DU=n

The dial command always uses UDP, even when using ATDT.

n=0 : Dial using the means specified (default). n=1 : Dial UDP always, even when using ATDT.

Note: When this parameter is set you cannot establish a TCP PAD connection.

*UALL=n

Accepts UDP packets from any IP address when a UDP session is active. If there is no UDP session active, an incoming UDP packet will be treated according to the UDP auto answer and AIP settings.

n=0 : No effect (Default). n=1 : Accept UDP data from all IP addresses when in a UDP session.

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

Page 75

AT Commands: UDP

*UDPLAST=n

If enabled, sets S53 to the last accepted IP address through UDP auto answer. This can be used in conjunction with MD3 so that when there is no UDP session, new ethernet host data will cause a connection to be restored to the last IP accepted through UDP auto answer. .

n=0 : Does not change S53 setting. (Default). n=1 : Set S53 to the last accepted IP.

Note: This does not change the S53 setting in NVRAM. If the modem is reset, the

original S53 setting will be restored from NVRAM.

*USD=n

W aits the specified delay before sending the first UDP packet and the subsequent UDP packets out to the Ethernet port.

n=1 - 255 Delay in 100ms units, from 100 ms to 25.5 sec. n=0 : No UDP packet delay (Default).

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

Page 76

AT Commands: DNS

DNS

This group includes commands specific to the modem being able to use domain names instead of IP addresses for other configuration options.

FIGURE 1. Common : DNS

*DNSn

Queries the DNS addresses. Verizon provides the DNS addresses while your modem is registring on their network.

n=1 or 2 First and second DNS address.

d.d.d.d = IP of domain server

*DNSUPDATE=n

Indicates whether the modem should send DNS updates to the DNS server specified by *DNSUSER. These updates are as per RFC2136. They are not secure and are recommended only for a private network. In a public network, the IP Logger services should be used instead.

n=0 : DNS updates disabled (Default). n=1 : DNS updates enabled.

*DNSUSER=d.d.d.d

Sets a user-provided DNS to query first when performing name resolutions in the modem. d.d.d.d = IP of domain server

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

Page 77

AT Commands: Dynamic IP

Dynamic IP

This group includes commands specific to dynamic DNS. Dynamic DNS allows the Raven X to use a dynamic IP (can change each time you connect) account but still allow you to use a fully qualified domain name to contact the Raven X using IP Manager (page with a dynamic DNS updater.

FIGURE 1. Common : Dynamic IP

11) running on a server

*DOMAIN=[name]

Domain (or domain zone) of which the Raven X is a part. This value is used during name resolutions if a fully qualified name is not provided and also for DNS updates. This value can be up to 20 characters long.

name = domain name (i.e. eairlink.com) If *DOMAIN=eairlink.com, then when ATDT@remote1 is entered, the fully qualified name

remote1.eairlink.com wil l be used to perform a DNS query to resolve the name to an IP address.

Note: Only letters, numbers, hyphens, and periods can be used in a domain name.

*IPMANAGERn=[name]

Sets a domain name or IP address to send IP change notifications to. Up to two independent IP Manager servers can be set, using either AT*IPMANAGER1 or AT*IPMANAGER2. Updates to a server can be disabled by setting that entry to nothing (for example, “AT*IPMANAGER1=”).

n=1 : First IP Manager server. n=2 : Second IP Manager server.

name = domain name

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

Page 78

AT Commands: Dynamic IP

*IPMGRKEYn=[key]

Sets the 128-bit key to use to authenticate the IP update notifications. If the key's value is all zeros, a default key will be used. If all the bytes in the key are set to FF, then no key will be used (i.e. the IP change notifications will not be authenticated). AT*IPMGRKEY1 is used to set the key to use with AT*IPMANAGER1, while AT*IPMGRKEY2 is used to the key with AT*IPMANAGER2.

n=1 : First IP Manager server. n=2 : Second IP Manager server.

key=128-bit key in hexadecimal [32 hex characters]

*IPMGRUPDATEn=m

Sets the number of minutes to periodically send an IP update notification to the corresponding server. This will occur even if the IP address of the Raven X doesn't change. *IPMGRUPDATE1 is used to set the refresh rate to *IPMANAGER1, while *IPMGRUPDATE2 is used with *IPMANAGER2.

n=1 : First IP Manager server. n=2 : Second IP Manager server.

m=0, 5-255 Number of minutes to send an update.

If the value is set to 0, then periodic updates will not be issued (i.e. IP change notifications will only be sent when the IP actually changes).

*MODEMNAME=[name]

Name of the Raven X (up to 20 characters long) to use when performing IP address change notifications to IP Manager. The value in *DOMAIN provides the domain zone to add to this name.

name = domain name (i.e. eairlink.com)

Example: if *MODEMNAME=mymodem and *DOMAIN=eairlink.com, then the modem's fully qualified domain name is mymodem.eairlink.com.

Automatically Generated Names:

• #I3 - The ESN/IMEI will be used as the name.

• #NETPHONE - The phone number will be used as the name.

Note: Each modem using IP Manager needs a unique name. Two modems cannot

be called “mymodem”. One could be “mymodem1” with the other as “mymo dem”.

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

Page 79

AT Commands: PPP/Ethernet

PPP/Ethernet

This group includes commands specific to PPP or Ethernet connections between the Raven X and a connected device.

FIGURE 1. Common : PPP/Ethernet

*HOSTAUTH=n

Host Authentication Mode: Use PAP or CHAP to request the user login and password during PPP or

CHAP negotiation on the host connection. The username and password set in *HOSTUID and *HOSTPW will be used.

n=0 : Disable PAP or CHAP request (Default). n=1 : PAP and CHAP. n=2 : CHAP

*HOSTNETMASK=n.n.n.n

Subnet mask for the host interface. Allows communication with a subnet behind the host interface.

n.n.n.n = subnet mask, example 255.255.255.0

*HOSTPEERIP=d.d.d.d

Set or query the IP address that can be used to directly contact the Raven X once a EV-DO connection is established. If this value is not specifi ed, 192.168.13.31 will be used.

d.d.d.d=local or peer IP of modem

Note: This is not normally used nor needed by user applications.

*HOSTPRIVIP=d.d.d.d

Set or query the private IP address that is to be negotiated by the EV-DO con nection if *HOSTPRIVMODE =1.

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

Page 80

AT Commands: PPP/Ethernet

d.d.d.d=IP Address

*HOSTPRIVMODE=n

Set or query whether a private or public (network) IP is to be used when the Host initiates a EV-DO connection to the modem.

n=0 : Public (network) IP Mode: When the Host initiates a PPP connection, the host will be given the network IP address that was obtained from Verizon while registering on the network. If the network issues a new IP address, the has to be re-initiated. (default).

n=1 : Private IP Mode: When the Host initiates a EV-DO connection, the host will be given the IP address specified in *HOSTPRIVIP. The modem will then perform 1 to 1 NAT-like address translation, which shields the Host from network IP changes.

*HOSTPW=string

Host Password for PAP, or CHAP, or PPPoE. string=password

*HOSTUID=string

EV-DO connection will be closed (since the IP address has changed) and

Host User ID for PAP, or CHAP, or PPPoE. string=user id (up to 64 bytes)

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

Page 81

AT Commands: PassThru

PassThru

PassThru Mode is used to communicate directly to the Raven X’s internal hardware.

FIGURE 1. Common : PassThru

Caution: While the modem is in PassThru mode, ALEOS is disabled. If you need

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

*CSX1=n

n=0 : Data will be passed to the host. n=1 : PASSTHRU mode will echo all host received data and will not pass the data to the modem while

the modem is not asserting DCD.

Note: If the modem is asserting DCD, data will be passed from the host to the modem as it normally is when *CSX1=0.

*PTINIT=string

Any AT Command string to be passed to the OEM module before entering PASSTHRU mode, e.g. AT&S1V1, etc.

string=AT command(s)

*PTREFRESH=n

Number of minutes of inactivity in PASSTHRU mode to resend the *PTINIT string to the hardware module.

n=1-255 minutes n=0 : Disabled

*RESETPERIOD=n

In PASSTHRU mode, modem will be reset after this period if no data has been sent or received. Value is in hours.

n=1-255 hours n=0 : Disabled

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

Page 82

AT Commands: PassThru

\APASSTHRU

Sets the modem operation to pass through mode. This mode will pass any characters received on the Ethernet port directly to the internal hardware module and output any characters from the internal hardware module out the Ethernet port. This allows direct access/configuration of the hardware module. Once this mode is entered, the unit must be physically reset to return to normal operation.

This command is not available in Wireless Ace.

Caution: This mode is not available through the remote AT telnet server. You will need to connect to the Raven X with it connected directly to your computer.

Note: It may take up to 30 seconds for the hardware module to respond after CONNECT is output.

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

Page 83

AT Commands: SMTP (including SMS)

SMTP (including SMS)

This group includes commands specific to messaging.

SMS (Short Message Service) is a way to send messages via Verizon’s cellular network.

Caution: Your account with Verizon may not support message sending with SMS.

FIGURE 1. Common : SMTP

*SMTPADDR=name]

Specify the IP address or Fully Qualified Domain Name (FQDN) of the SMTP server to use.

d.d.d.d=IP Address name=domain name

Maximum: 40 characters.

*SMTPFROM=email

Sets the email address from which the SMTP message is being sent. email= email address

Maximum: 30 characters.

*SMTPSUBJ=subject

Allows configuration of the default Subject to use if one isn't specified in the message by providing a “Subject: xxx” line as the initial message line.

subject= SMTP message subject

*SMTPUSER=user

The email account username to authenticate with the SMTP server (*SMTPADDR) for sending email.

user= username

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

Page 84

AT Commands: SMTP (including SMS)

Maximum: 40 characters.

Note: Not required to use SMTP settings but may be required by Verizon.

Messaging related AT Commands not Available through Wireless Ace

*NETSMS2EMAIL=n

Specify the SMS/E-mail server number. This maybe necessary to send an SMS message to an email address .

n=SMS/E-mail server

*SMTPSEND=[email][body]

Sends an email to the address specified, followed by the body of the email message.

email= email address body= message body

The email message is terminated and sent by entering a . or Ctrl-Z on an empty line. See also *SMTPSUBJ, *SMYPFROM, and *SMTPADDR.

*SMTPSTATUS?

Returns the status of the last issued SMTP message (*SMTPSEND). If no status is available 0 is returned. Once read, the status is cleared out.

The status codes returned come from the SMTP server to which that the modem sent the request. Unless the receiving server is not standard, they follow the RFC for SMTP.

Example: 354 = send in progress, 250 = sent ok.

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

Page 85

AT Commands: Other

Other

The commands in this group are not specific to the other group categories.

The commands displayed in Wireless Ace and the results of those commands depends on the model of the modem.

FIGURE 1. Common : Other

DAE=n

Disable AT Escape Sequence detection.

n=0 : Enable +++ AT escape sequence detection. n=1 : Disable +++ AT escape sequence detection.

*DATZ=n

Enables or disables reset on AT Z.

n=0 : Normal Reset (Default) n=1 : Disable Reset on ATZ

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

Page 86

AT Commands: Other

*IPPING=n

*IPPINGADDR=[d.d.d.d][name]

*MSCIUPDADDR=name[/port]

Set the period to ping (if no valid packets have been received) a specified address (*IPPINGADDR) to keep the modem alive (online).

n=15-255 minutes n=0 : Disable pinging (default)

15 minutes is the minimum interval which can be set for Keepalive. See also *MINXMIT which can override this value.

Set the IP address or valid internet domain name for the Raven X to ping to keep itself alive (online). *IPPING must to be set to a value other than 0 to enable pinging.

d.d.d.d=IP address name= domain name

Modem Status Update Address - where Name/Port is the domain name and port of the machine where the modem status updates will be sent. The Raven X's status parameters are sent in an XML format.

name=domain name port=port

*MSCIUPDPERIOD=n

Modem Status Update Period - where n defines the update period in seconds.

n=1-255 seconds n=0 : Disabled.

*NETWDOG=n

Network connection watchdog: The number of minutes to wait for a network connection. If no connection is established within the set number of minutes, the Raven X resets.

n=minutes Default = 20 min. n=0 : Disabled.

*SNMPCOMMUNITY=n

The SNMP Community String acts like a password to limit access to the modem’ s SNMP data.

n=a string of no more than 20 characters (default = public).

*SNMPPORT=n

This controls which port the SNMP Agent listens on.

n=1-65535 n=0 : SNMP is disabled.

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

Page 87

AT Commands: Other

*SNMPSECLVL=n

*SNMPTRAPDEST=host/[port]

Selects the security level requirements for SNMP communications as follows:

n=0 : No security required. SNMPv2c and SNMPv3 communications are allowed. n=1 : Authentication equivalent to “authNoPriv” setting in SNMPv3. SNMPv3 is required to do authen-

tication, SNMPv2c transmissions will be silently discarded. n=2 : Authentication and encryption, equivalent to “authPriv”' setting in SNMPv3. SNMPv3 is required

to do authentication and encryption, SNMPv2c and SNMPv3 authNoPriv transmissions will be silently discarded. Messages are both authenticated and encrypted to prevent a hacker from viewing its contents.

Controls destination for SNMP Trap messages.

host=IP address port=TCP port

If port is 0 or host is empty, traps are disabled. 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 that can be generated is linkup.

*SNTP=n

Enables daily SNTP update of the system time.

n=0 : Off n=1 : On

*SNTPADDR=[d.d.d.d][name]

SNTP Server IP address, or fully-qualified domain name, to use if *SNTP=1.

d.d.d.d=IP name=domain name

If blank, time.nist.gov is used.

*TELNETTIMEOUT=n

Telnet port inactivity time out.

n=minutes

By default, this value is set to close the AT telnet connection if no data is received for 2 minutes.

*TPORT=n

Sets or queries the port used for the AT Telnet server . If 0 is specified, the AT Telnet server will be disabled. The default value is 2332. .

n=1-65535 n=0 : Disabled.

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

Page 88

AT Commands: Friends

Friends

Friends Mode can limit access to the Raven X from Verizon’s network and the Internet. Friends Mode is a basic firewall.

Note: Friends mode does not block any traffic from the cellular network, wanted or

not. Friends Mode will only prevent the not on the Friends List. It does not prevent data from traversing the network to the modem which may billable traffic.

Caution: If you are using Friends Mode you will not be able to use Wireless Ace

remotely or Telnet to the modem unless you are contacting the modem from one of the configured IP addresses.

FIGURE 1. Common : Friends

Raven X from receiving data from those

FM=n

Friends Mode - Only allow specified IPs to access the Raven X.

n=0 : Disable Friends mode n=1 : Enable Friends mode - Only packets from friends will be accepte d (see below); packets from other

IP addresses are ignored.

Fn=[d.d.d.d]

Friends mode IP address.

n=0 - 9 Friends list index .

d.d.d.d =IP address

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

Page 89

AT Commands: Friends

ATF? will return a list of all the current Fn settings.

255 = allow any number 0-255

Example: 166.129.2.255 allows access by all IPs in the range 166.129.2.0-166.129.2.255.

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

Page 90

AT Commands: Logging

Logging

This group includes commands specific to the internal log.

The commands displayed in Wireless Ace and the results of those commands depends on the model of the modem.

FIGURE 1. Logging

Caution: Logging is intended for diagnostic purposes only. Extensive use of log-

ging features can cause degraded modem performance.

*DBGCOMMLVL=n

Set the logging level for the host or module COM port.

n=0 : No logging n=1 : Host COM n=2 : Module COM

*DBGDHCPLVL=n

Enable or disable internal DHCP logging.

n=0 : n=1 :

*DBGETHLVL=n

Sets the logging level for the Ethernet port.

n=0 : n=1 : n=2 :

*DBGIPLVL=n

Sets the logging level for the IP subsystem.

n=0 : No logging

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

Page 91

AT Commands: Logging

n=1 : Log errors (i.e. invalid/corrupt packets, etc.). n=2 : Log the header of all received packets. Note that this can quickly exhaust available space for the

event log. n=3 : Log the header of all received and sent packets. Note that this can quickly exhaust available space

for the event log.

*DBGPPPLVL=n

Sets the logging level for the PPP stack. Enables logging at different levels of detail.

n=0 : No logging n=1 : Log client events (default) n=2 : Log server events n=3 : Log client and Server events

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

Page 92

AT Commands: Telemetry and Addr List (Address List)

Telemetry and Addr List (Address List)

Modbus, commonly used with telemetry devices, allows a connection via serial port to the modem (page

29). Telemetry and Addr List commands are only used when the modem is in one of the

Modbus start-up modes.

FIGURE 1. Telemetry

FIGURE 2. Addr List (detail)

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

Page 93

AT Commands: Telemetry and Addr List (Address List)

FIGURE 3. Addr List

IPL=n

IP List Dial This allows access the Modbus IP list using the first two digits of the dial string. Example:

ATDT1234567 would go to ID "12" on the Modbus list and use the associated IP as the destination.

n=0 : Disabled n=1 : Enabled

MLISTid=d.d.d.d

This command is configured by the fields avaialble in the Addr List group.

Enters an ID and IP address into the Modbus List. ID is a decimal value (1 to 100).

id=ID d.d.d.d=IP or name adresse

MLISTXhexid=d.d.d.d

This command is configured by the fields avaialble in the Addr List group.

Enters an ID and IP address into the Modbus List. ID is a hexadecimal value (0 to 64).

hexid=ID d.d.d.d=IP or name adresse

MVLEN=n

Modbus Variant ID Length: Length of the RTU ID in a modbus-variant protocol, in bytes.

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

Page 94

AT Commands: Telemetry and Addr List (Address List)

n=1 This parameter is used to define the length of the RTU ID in Modbus-like protocol data

packets.

n=2 This parameter is used when the when the MD is set to hex 63.

MVMSK=hh

Modbus Variant ID Mask: Byte hex mask to use when extracting the ID. Specify which bits in the ID field to use. This parameter is used when the when the Mode Default (MD) is set to hex

63.

hh=hex value 00 - no mask, all 8 bits (default) 0F - only the low order 4 bits

MVOFF=n

Modbus (variable mode) Offset : Indicates the offset in the data of where the Modbus ID starts.

n= 0 - 255

MVOPT=n

Modbus Variant Option: Sets various behavioral options when dealing with a Modbus-variant protocol. This parameter is used when the when MD is set to hex 63.

n=0 : No special action (Default). n=1 : Skip leading zeroes in Modbus packets.

Cannot be configured in Wireless Ace.

MVTYP=n

Modbus Variant Type: The data-type of the RTU ID in a modbus-variant protocol. This parameter is used to define the data-type of the RTU ID in Modbus-like protocol data packets. This parameter is used when MD is set to 63.

n=0 : Binary (Default) n=1 : ASCII Hex n=2 : ASCII Decimal

RKEY=n

Radio Transceiver Keying.

n=0 : Off (Default) n=1 : On

Enable/disable MDS Radio transceiver keying. Radio keying is designed to assert CTS when a packet is received, delay the time as specified, send the data out the serial port, wait the same amount time, drop CTS. This way, the CTS signal can be used to key a transmitter on and give it time to reach its power level before data is sent to it. Delay interval is specified in S221.

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

Page 95

AT Commands: Telemetry and Addr List (Address List)

Commands in other groups associtated with Telemetry

Only the settings associated with telemetry are explained in this section.

MDn

This command can be found in the UDP group.

Set to the appropriate start up mode for your telemetry configuration.

FIGURE 4. MD menu

n=03 : UDP n=13 : Modbus ASCII n=23 : Modbus RTU n=33 : BSAP n=63 : Variable Modbus n=73 : Reliable UDP n=83 : UDP Multicast

S53=[method][d.d.d.d][/ppppp] and *DPORT=n

These commands are in the Misc group.

FIGURE 5. S53 and *DPORT

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

Page 96

AT Commands: Telemetry and Addr List (Address List)

Destination Address

For the remote Ravens, set the destination address to the IP address or domain name (if you are using IP Manager with a dynamic IP) of the host Raven.

Destination Port and *DPORT

The destination port (S53) for the Raven at the host needs to match the device port in use on all the Ravens at the remote sites (*DPORT), and the destination port (S53) for all the Ravens at the remote sites need to match the device port in use on the Ravens at the host (*DPORT).

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

Page 97

AT Commands: CDMA/EV-DO

CDMA/EV-DO

This group includes commands specific to CDMA/1x and EV-DO.

FIGURE 1. CDMA/EV-DO

+CTA=n

Inactivity timer, in seconds.

n=seconds (maximum 20 seconds) n=0 : Allows the Verizon network to determine the inactivy timer.

Typical network settings cause a link to go dormant after 10 to 20 seconds of inactivity, no packets transmitted or received. This time can be shortened to release the physical RF link sooner when the application only transmits short bursts.

$QCMIP=n

Mobile IP (MIP) Preferences.

n=0 : Disabled, SIP only n=1 : MIP preferred n=2 : MIP only

On a Mobile IP network, a device connects to the network using PPP. During the negotiation process the Raven X is NOT required to present a username and password to authenticate because the authentication parameters are stored in the modem itself.

Note: Your account with Verizon may not support Mobile IP.

~NAMLCK=nnnnnn

The NAMLCK is the modem's 6-digit OTSL (One Time Subsidy Lock), MSL (Master Subsidy Lock), or SPC (Service Provisioning Code). Verizon will provide the unlock code.

nnnnnn=6 digit unlock code If the number is accepted by the modem, the OK result code is returned. If the number is

rejected, the ERROR result is returned. If three successive Errors are returned, the modem must be reset to allow any further attempts.

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

Page 98

AT Commands: CDMA/EV-DO

*EVDODIVERSITY=n

EV-DO Diversity allows two antennas to provide more consistent connection.

n=0 : Disabled (Default). n=1 : Allow

CDMA and EV-DO related AT Commands not Available through Wireless Ace

Indicates PRL update schedule.

n=1-255

n=0 : Disabled

Caution: The modem permits 99 failures of this command during its lifetime. After

that, the modem becomes permanently disabled.

Note: You will need to put the modem in PassThru mode to use many of these com-

mands and are reliant on the model number of your modem. Commands which begin with an * (asterisk) do not require PassThru.

*PROVISION=[MSL],[MDN/MIN],[SID],[NID]

Caution: It is recommended to use the Setup Wizard for Verizon to provision the modem.

Provision the modem with the lock code and phone number.

MSL=master lockcode MDN/MIN= phone number SID=system ID* NID=network ID*

*Verizon may not support this function.

*PROVISION2=[MSL],[MDN],[MIN],[SID],[NID]

A second set of modem provision parameters, when the MDN and MIN (MSID) are different or “split”.

MSL=master lockcode MDN/MIN= phone number SID=system ID* NID=network ID*

*SID and NID are optional, however if you include SID you must include NID.

~NAMVAL=nam[,num,min,sid,nid]

Write account activation data. C310 only.

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

Page 99

AT Commands: CDMA/EV-DO

nam=0 num=phone number min=second number sid=0 or the system ID nid=63355 or the network ID

Following writing the values, the modem must be reset. Note: If ~NAMLCK has not been successfully executed, the modem returns ERROR.

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

Page 100

APPENDIX D Simple Network Management

Protocol (SNMP)

The Raven X can be configured as an SNMP agent and supports SNMPv2c and SNMPv3.

SNMP Overview

The Simple Network Management Protocol (SNMP) was designed to allow remote management and monitoring of a variety of devices from a central location. The SNMP management system is generally composed of agents (such as your other computer equipment) and a Network Management Station (NMS) which monitors all the agents on a specific network. Using the management information base (MIB), an NMS can include reporting, network topology mapping, tools to allow traffic monitoring and trend analysis, and device monitoring.

Raven X, a router, a UPS, a web server, a file server, or

Authentication ensures SNMP messages coming from the agent, such as the Raven X, have not been modified and the agent may not be queried by unauthorized users. SNMPv3 uses a UserBased Security Model (USM) to authenticate and, if desired or supported, message encryption. USM uses a user name and password specific to each device.

Management Information Base (MIB)

The management information base (MIB) is a type of database used to compile the information from the various SNMP agents. Reports from various agents, such as the in form designed to be parsed by the NMS into its MIB. The data is hierarchical with entries addressed through object identifiers.

Raven X, are sent as data

SNMP Traps

SNMP traps are alerts that can be sent from the managed device to the Network Management Station when an event happens. Your Raven X is capable of sending the linkUp trap when the network connection becomes available.

Raven X SNMP Configuration

T o configure your Raven X to work as an SNMP agent, you can use either Wireless Ace, or a terminal connection to configure the modem using AT commands. In Wireless Ace, the SNMP commands are all on the Other menu option.

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