Intermec 6980, 6985 Programmer's Manual

6980/6985 Network Manager

PROGRAMMER’S GUIDE

"""""""""""""""""""""

P/N 977-055-002

Revision B

May 2000

" NOTICE The information contained herein is proprietary and is provided solely for the purpose of allowing customers to

operate and service Intermec manufactured equipment and is not to be released, reproduced, or used for any
other purpose without written permission of Intermec.

Disclaimer of Warranties. The sample source code included in this document is presented for reference only.
The code does not necessarily represent complete, tested programs. The code is provided AS IS WITH ALL

FAULTS." ALL WARRANTIES ARE EXPRESSLY DISCLAIMED, INCLUDING THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

We welcome your comments concerning this publication. Although every effort has been made to keep it free of
errors, some may occur. When reporting a specific problem, please describe it briefly and include the book title
and part number, as well as the paragraph or figure number and the page number.

Send your comments to:
Intermec Technologies Corporation
Publications Department
550 Second Street SE
Cedar Rapids, IA 52401

ANTARES, INTERMEC, NORAND, NOR*WARE, PEN*KEY, ROUTEPOWER, TRAKKER, and TRAKKER
ANTARES are registered trademarks and ENTERPRISE WIRELESS LAN, INCA, TE 2000, UAP, and
UNIVERSAL ACCESS POINT are trademarks of Intermec Technologies Corporation.

 2000 Intermec Technologies Corporation. All rights reserved.

This publication printed on recycled paper.

Acknowledgments

Hayes is a registered trademark of Hayes Microcomputer Products Inc.

Microsoft, MS, and MSĆDOS, and Windows, are registered trademarks and Visual Basic for Windows, and
Windows for Pen are trademarks of Microsoft Corporation.

FCC Computer Compliance

"

NOTICE This equipment meets Class A digital device limits per Part 15 of FCC Rules. These limits protect against

interference in a commercial area. It emits, uses, and can radiate radio frequency energy. If you do not install
and use the equipment according to its instructions, it may interfere with radio signals. Using it in a residential
area is likely to cause interference. If this occurs, you must correct the interference at your expense.

Canadian Computer Compliance

This Class A digital apparatus meets all requirements of the Canadian InterferenceĆCausing Equipment
Regulations.

Cet appareil numérique de la classe A respecte toutes les exigences du Reglèment sur le material boilleur du
Canada

CONTENTS

""""""""""""""""""""

SECTION 1

Introduction

About this Guide 1Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Publications 1Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Customer Support 1Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Customer Response Center 1Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Factory Service 1Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Web Site 1Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bulletin Board Service 1Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2

Getting Started

Modem Support 2Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Codes 2Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Enhancements 2Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communication Session 2Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Configurations 2Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Physical Ports 2Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logical Channels 2Ć4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Compact Flash 2Ć4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Channel Option 2Ć5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3

Host-to-Network Manager Records

EM311 Protocol Interface 3Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Record Types 3Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Download Data Record (Type 0) 3Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EndĆofĆData Record (Type 1) 3Ć4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initialization Record (Type 2) 3Ć5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Mode Parameters 3Ć6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Host Parameters 3Ć7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Activate Autoanswer (Type 3) 3Ć8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Activate Autodial (Type 4) 3Ć9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deactivate for One Minute (Type 5) 3Ć10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Host Directive (Type 6) 3Ć11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

File Upload Directive 1" 3Ć12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

File Create or Load Directive 2" 3Ć13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

File Delete Directive 3" 3Ć14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

File Download Directive 4" 3Ć15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

File Processing Abort 6" 3Ć16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Special Commands 3Ć17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Type ? Ċ Host Ready Command 3Ć17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Type * Ċ Reinitialization Command 3Ć17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6980/6985 Network Manager Programmer’s Guide i

CONTENTS

SECTION 4

Network Manager-to-Host Records

Record Formats with 2Ćbyte Channel ID 4Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Record Types 4Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upload Data (Type 0) 4Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

End of Session Status (Type 1) 4Ć4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Request (Type 2) 4Ć5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inactive Status (Type 3) 4Ć5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Active Status (Type 4) 4Ć6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Activation Request (Type 5) 4Ć6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Special Request (Type 6) 4Ć8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Directive Status (Type 7) 4Ć9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Begin of Call (Type C) 4Ć10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network ManagerĆBased File Processing 4Ć11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 5

EM611 IP Header Information

Local 6980 Network Manager (NPCMux Functionality) 5Ć2. . . . . . . . . . . . . . . . . . . . . .

Host Interface to 6980 NPCMux" 5Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX A

4980-to-6980 Conversion

Communication and Application Diagram AĆ2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AS/400 or 4980 Conversion to 6980 AĆ2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4980 Interface on an AS/400 AĆ2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6980 Interface on an AS/400 AĆ3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX B

Adapting Programs Used with the 4980 Protocol Converter

Record Types BĆ1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4980 Record Types BĆ1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communications ControllerĆtoĆHost BĆ1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HostĆtoĆCommunications Controller BĆ1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6980/6985 Record Types BĆ2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network ManagerĆtoĆHost BĆ2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HostĆtoĆNetwork Manager Records BĆ3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Special Commands BĆ4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX C

Asynchronous Hosts C-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX D

Pseudo Host Communications Program D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FIGURES

Figure 5Ć1 EM611 Structure and Definition 5Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure AĆ1 Architecture between 6980 Socket Manager and AS/400 AĆ2. . . . . . . . . . .

Figure AĆ2 AS/400 Programming Architecture AĆ3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ii 6980/6985 Network Manager Programmer’s Guide

CONTENTS

TABLES

Table 2Ć1 Network Manager Environments 2Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2Ć2 Physical Ports for Client Connections 2Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć1 HostĆtoĆNetwork Manager Records 3Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć2 Type 0 Ċ Download Data Record 3Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć3 Type 1 Ċ EndĆofĆData Record 3Ć4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć4 Type 2 Ċ Initialization Record 3Ć5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć5 System Mode Parameters 3Ć6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć6 Host Parameters 3Ć7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć7 Type 3 Ċ Activate (AutoĆAnswer) Record 3Ć8. . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć8 Type 4 Ċ Activate (AutoĆDial) Record 3Ć9. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć9 Type 5 Ċ Deactivate for One Minute Record 3Ć10. . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć10 Type 6 Ċ Host Directive Record 3Ć11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć11 File Upload Directive 1" 3Ć12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć12 File Create or Load Directive 2" 3Ć13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć13 File Delete Directive 3" 3Ć14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć14 File Download Directive 4" 3Ć15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć15 File Processing Abort 6" 3Ć16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć16 Type ? Ċ Host Ready Command 3Ć17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3Ć17 Type * Ċ Reinitialization Command 3Ć17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć1 2ĆByte Channel ID 4Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć2 Network ManagerĆtoĆHost Record Types 4Ć2. . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć3 Type 0 Ċ Upload Data Record 4Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć4 Type 1 Ċ End of Session Status Record 4Ć4. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć5 End of Session Status Codes 4Ć4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć6 Type 2 Ċ Data Request Record 4Ć5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć7 Type 3 Ċ Inactive Status Record 4Ć5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć8 Type 4 Ċ Active Status Record 4Ć6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć9 Type 5 Ċ Activation Request Record 4Ć6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć10 Activation Request Status Codes 4Ć7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć11 Type 6 Ċ Special Request Record 4Ć8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć12 Special Request Subtypes 4Ć8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć13 Type 7 Ċ Directive Status Record 4Ć9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć14 Host File Directive Status Codes 4Ć10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć15 Type C Ċ Begin of Call Record 4Ć10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 4Ć16 NETRPL.LST File 4Ć11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5Ć1 EM611 Packet and Header 5Ć1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 5Ć2 6980 NPCMux Commands 5Ć3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GLOSSARY

INDEX

6980/6985 Network Manager Programmer’s Guide iii

CONTENTS

iv 6980/6985 Network Manager Programmer’s Guide

Section 1

Introduction

""""""""""""""""""""

"

NOTE: This publication supersedes the 4980 Network Controller Programmer’s Guide (P/N:

977-028-001) and the 4985 Network Controller Programmer’s Guide (P/N: 977-028-006).

The 6980/6985 Network Manager provides a data communications interface beĆ
tween the host computer and INTERMEC

R

devices. The network manager is
programmable and can be configured many ways. The two functions in this reĆ
lease of the 6980/6985 Network Manager are:

" An asynchronous (async) or IPĆbased communications gateway to a host

computer

" A handĆheld computer network manager.

In the first function, the network manager is directly connected to a customer's
host computer and provides a gateway through which data and data requests
pass from handĆheld computers to the host on logical channels.

In the second function, the network manager is usually located at a remote site
and provides an interface between handĆheld computers and a host. Section 2
provides illustrations of several possible system configurations.

A host telecommunication program and associated support programs are reĆ
quired to interface to a 6980/6985 Network Manager. This function can be proĆ
vided by the Norand

R

6920 Communications Server or some other host applicaĆ

tion.

The RSĆ232 host link can be configured for speeds up to 115,200 bps async or a
10 Mbps TCP/IP interface. See Section 4 for more on developing your host interĆ
face.

The network manager initiates the session placing the host in a loop reading
data and request records from network managers.

6980/6985 Network Manager Programmer’s Guide 1-1

About this Guide

These paragraphs detail topics discussed in each section:

Section 1 Ċ Introduction

Introduces the manual and provides customer support information.

Section 2 Ċ Getting Started

Covers the hardware configuration of the network, the physical port assignments
on the network manager, and the logical port assignments.

Section 3 Ċ HostĆtoĆNetwork Manager Records

Lists hostĆtoĆnetwork manager records and other processing information from
the host.

Section 4 Ċ Network ManagerĆtoĆHost Records

Contains networkĆtoĆmanager records and other processing information, and staĆ
tus and error codes returned from the network manager.

Section 5 Ċ EM611 Header Information

Defines the EM611 IP framing structure.
The appendixes have several program examples and 4980ĆtoĆ6980 conversion

information.

SECTION 1Introduction

Related Publications

The following publications have information related to the 6980/6985 Network
Manager.

6980/6985 Network Manager User's Guide

P/N: 961Ć055Ć003

R

Norand

P/N: 962Ć055Ć005

Norand

P/N: 961Ć021Ć014

Norand

P/N: 977Ć021Ć001

6920 Communications Server Installation Guide

R

6920 Communications Server User's Guide

R

6920 Communications Server Reference Manual

Customer Support

Customer Response Center

The Customer Response Center (technical support) telephone number is
800Ć755Ć5505 (U.S.A. or Canada) or 425Ć356Ć1799. The facsimile number is
425Ć356Ć1688. Email is [e-mail].

If you email or fax a problem or question include the following information in
your message: your name, the company name and address, phone number and
email to respond to, and problem description or question (the more specific, the
better). If the equipment was purchased through a ValueĆAdded Reseller (VAR),
please include that information.

Factory Service

If your unit is faulty, you can ship it to the nearest authorized Service Center for
factoryĆquality service. The addresses and telephone numbers are included in
the Warranty Card shipped with your product.

1-2 6980/6985 Network Manager Programmer’s Guide

SECTION 1 Introduction

Web Site

The Customer Support File Libraries, including Hot Tips and Product Awareness
Bulletins, are available on the Internet. New users start at the Intermec web
site: http://corp.intermec.com. Choose Support," then Product Support," then
Conference Area." Look on the main page for a link to register new customers.

A PDF version of this manual is available at:
http://corp.intermec.com/manuals/english.htm or choose products," manuals,"
english" via the home page.

Bulletin Board Service

The Customer Support Bulletin Board (BBS), maintained by the Intermec
Technologies Corporation, provides software and documentation:

Phone number:

319Ć369Ć3515 (14.4 Kbps modem)
319Ć369Ć3516 (28.8 Kbps modem)

Protocol:
Full duplex, ANSI or ANSIĆBBS; 300 to 28,800 bps; v.32bis; 8 bits, no parity, 1
stop bit. For highĆspeed modems, disable XON/XOFF and enable RTS/CTS.

This is the same location available via the internet site. If you have highĆspeed
access, the web interface provides a faster response.

6980/6985 Network Manager Programmer’s Guide 1-3

SECTION 1Introduction

1-4 6980/6985 Network Manager Programmer’s Guide

Section 2

Getting Started

""""""""""""""""""""

Modem Support

The 6980/6985 Network Manager supports a number of HayesĆcompatible conĆ
figuration and autodial modem types. Support provided is subject to changes
made in the modem interface by the modem vendor.

Error Codes

Error codes via the LED display and PowerĆUp SelfĆTest errors are located in the
6980/6985 Network Manager User's Guide (P/N: 961Ć055Ć003).

Enhancements

The network manager provides a number of new features:

File support

The network manager allows the host computer to download a limited number of
files that can be stored on the network manager compact flash. These files can
include customer data files, which can be forwarded to a handĆheld computer at
the direction of the host computer; or boot files, which can boot a handĆheld comĆ
puter independently of the host computer. The host may upload or delete data or
boot file from the network manager.

Line disciplines

The network manager supports a variety of line disciplines, including Norand
TTY, Async, and Norand

Autodial/Autoanswer

Ports on the network manager can be toggled as either autodial or autoanswer.
A timeout can be specified for autoanswer ports.

Data Record Length

The network manager data record length is 256 bytes for Async or 256 or 1024
for IP, not including channel and record type bytes. The 4980 data record length
is 256 bytes.

Booting HandĆHeld Computers

Boot files can be downloaded from the host into a DATA" directory in the 6980
Network Manager CompactFlash flash.

R

Portable Communications Protocol (NPCP).

(Future release)

Modifying System and Port Configurations

The network manager system and port configurations can be modified using the
6980 Web Interface. See the 6980/6985 Network Manager User's Guide for deĆ
tails.

6980/6985 Network Manager Programmer’s Guide 2-1

Communication Session

The 6980/6985 Network Manager uses the hostĆtoĆhandĆheld computer commuĆ
nications sessions. The network manager provides the physical connection for
the communications session and maintains the session on a logical channel.

A logical channel between a handĆheld computer and the host computer will alĆ
ways pass through a network manager. All data sent to the host from a network
manager is prefixed by a device ID and logical channel identifier.

Table 2Ć1 summarizes the communication abilities of each of the handĆheld comĆ
puter types in specific environments. Other environments may be possible with
special adapters.

Network Manager Environments

SECTION 2Getting Started

Table 2Ć1

HandĆHeld
Computer Type

4000/6000 Series TTY

601 and 602
(DOS only)

"

NOTE: The network manager supports only full-duplex modems.

Protocol
Option Environment

Modem (single dock)

NPCP

TTY
NPCP

Single or multidock directlyĆconnected to a network
manager

Modem (single dock)
Single or multidock directlyĆconnected to a network

manager

As an example, Table 2Ć1 indicates that a 4000 or 6000 Series handĆheld computĆ
er can communicate using TTY or NPCP. If NPCP is used, the handĆheld comĆ
puter must be in a dock which is directly cabled to a network manager.

The network manager minimizes the differences between Norand handĆheld
computers. After the physical connection is established, the communications sesĆ
sions for all of the handĆheld computer types are identical.

The communication session for a handĆheld computer, currently, consists of:

" An upload" file transfer from handĆheld computer to host computer.
" A download" file transfer from host computer to handĆheld computer.
" An endĆofĆsession" from the handĆheld computer.

Typically, the handĆheld computer sends identification information in the first
upload record, which can be used by the host to tie a specific set of download
data files to the unique route or driver assigned to that particular handĆheld
computer. This download part is optional.

EXAMPLE: The host receives upload records from a hand-held computer, on a device ID and logical

channel, until the upload is complete. After the upload is complete, the host receives down­load data requests, on the same device ID and logical channel, for the hand-held computer.
The host responds with download data until finished, then an end-of-data record is sent. The
host then receives an end-of-session record with the hand-held computer session status.

The user must be aware of handĆheld computer differences in the INTERMEC
Wide Area Network (WAN) to make the correct physical connection to a given
remote site.

See the 6980/6985 Network Manager User's Guide for a table that specifies the
possible configurations for network manager ports and the environments to
which the ports can connect.

2-2 6980/6985 Network Manager Programmer’s Guide

SECTION 2 Getting Started

Network Configurations

Each 6980/6985 Network Manager is treated as a unique connection to the host
application allowing a single host application to simultaneously communicate
with several network managers. The 6980/6985 Network Manager, using NPCP
as its main connection protocol, allows the host to make a high speed connection
to each network manager.

This type of configuration allows for a simple migration from a 4980 CommuĆ
nications Controller to a 6980 Network Manager. See Section 5 to learn about
the 6980 NPCMux application.

See the 6980/6985 Network Manager User's Guide for sample configurations.
Contact your account representative for more detailed information.

Physical Ports

The 6980 Network Manager has five possible physical ports for client connecĆ
tions. The 6985 Network Manager has one physical port.

Table 2Ć2

Physical Ports for Client Connections

Physical
Port Hardware Type

6980 Network Manager

Port A1 RSĆ485 Connections NPCP 1ć5

Port A2 RSĆ485 Connections NPCP 1ć5

Port B1 RSĆ232 Connections TTY 1

Port B1 RSĆ232 Connections TTY 1

Port C1 PC Card Modem TTY 1

6985 Network Manager

Port A1 RSĆ485 Connection NPCP 1ć5

Supported
Client Protocol

Logical
Channels

The 6980 Network Manager configuration connects with a maximum of 13 handĆ
held computer (client) channels simultaneously. The 6985 Network Manager
connects with a maximum of 5 channels. Thus, when a network manager is
communicating to a host computer, clients will send their upload and receive
their download on 1 of 5 or 13 possible logical channels. There is no correlation
between what logical channel is assigned to a client and the physical port the cliĆ
ent communicates on.

The network manager, pending its configuration, has a pool" of channels indiĆ
vidually assigned to client connections. The client uses its assigned channel to
communicate its upload and receive its download. When the client ends its sesĆ
sion, the channel is returned to the pool for reuse.

6980/6985 Network Manager Programmer’s Guide 2-3

Logical Channels

Records from the network manager specific to a port (such as Activate Requests)
always use the logical channel which equates to the logical port ID. After the
physical connection on a port is established, data to or from a client is sequential
on a logical channel, and the location of the logical channel should not concern
the host programmer.

Compact Flash

The 6980 Network Manager stores Windows CE, Web Server, FTP Server, 6980
protocols, and handĆheld computer applications on the compact flash within. The
compact flash can be viewed using FTP (either command line or through a
browser) and has a cfata" folder.

Removing or editing files on the compact flash can cause the network manager to
fail. Under some extreme circumstances, the network manager may not be
recoverable. In these extreme cases, the CompactFlash Card must be reimaged.

The compact flash has the following folder structure:

SECTION 2Getting Started

Folder Name Description

\cfata\Websrv Contains all the Web Server pages and the location of the

configuration file for the network manager (6980CE.INI).

\cfata\6980 Location of the 6980 application that provides host and

client communication protocols.

\cfata\6980\data Location for all locally stored client boot applications and

download request data files.

\cfata\UpdFiles Overrides any Kernel resident files. At cold boot, any file in

this directory is copied to the \Windows" folder and the
system is warmĆbooted. Only KernelĆlevel files reside in
this directory.

\cfata\AppFiles Location to store any new applications that may run in the

\Windows" folder (known as the object store" in Windows
CE) once the network manager is started.

Some of the important files which reside on the network manager:

File Location\Name

\cfata\boot.ini A file containing a list of applications to start when

cfata\Websrv\6980ce.ini Configuration file for the network manager

cfata\Websrv\6980ini.def Default configuration file for the network manager

Description

the network manager is started.

(normally modified using Web Pages (see the

6980/6985 Network

details).

(this file returns the network manager to its factory
default).

Manager User's Guide for

2-4 6980/6985 Network Manager Programmer’s Guide

SECTION 2 Getting Started

Device Channel Option

Each record from the network manager is preceded by a device ID, a logical
channel identifier, and a record type field.

There are eight hostĆtoĆnetwork manager record types. Some are request records
which require a response from the host computer. Each record from the host
computer is preceded by a record type field. There are six hostĆtoĆnetwork manĆ
ager record types.

"

NOTE: IP-based communications require a 6-byte header prefixed to each record. See Section 5 for

EM611 IP Header information.

The first data the host will receive on the new device channel is an identification
record. That record contains a userĆdefined ID and configuration information
about the remote network manager. Device channels require the host to index
state variables and file variables by device and handĆheld computer channel
number.

All records from the 6980 Network Manager are preceded with a device number
and channel number.

The partial record layouts illustrate the differences in the logical channel opĆ
tions:

EM311 for 4980 Series Communications Controller:
Position 1 Device channel disabled (optional)
Position 2 HandĆheld computer channel
Position 3 Record type
Position 4+ TypeĆdependent

EM311 for 6980/6985 Network Manager:
Device channel enabled:
Position 1 Device channel
Position 2 HandĆheld computer channel
Position 3 Record type
Position 4+ TypeĆdependent

6980/6985 Network Manager Programmer’s Guide 2-5

SECTION 2Getting Started

2-6 6980/6985 Network Manager Programmer’s Guide

Section 3

Host-to-Network Manager Records

""""""""""""""""""""

The file transfer protocol between the network manager and host is implemented
with six hostĆtoĆnetwork manager record types.

This section explains the function of each hostĆtoĆnetwork manager record type.

EM311 Protocol Interface

Each record sent from your host must have a record type field. There may be
eight record types sent from your host to the network manager.

This explains the function of each record type. Actual record layouts appear afĆ
ter the record description starting on page 3Ć2.

Each record from an async host must begin with a oneĆbyte beginningĆofĆrecord
delimiter (a slash /") and a oneĆbyte command code (ASCII) 0" through 7".

The host sends records in response to requests from the network manager, except
for the initialization record. The initialization record is sent to activate an inacĆ
tive network manager.

The host may also send two special commands to the network manager, a quesĆ
tion mark ?" and an asterisk *". A question mark indicates the host is ready to
receive data and serves as an acknowledgement record. The asterisk resets the
network manager, although the network manager will reset itself if the host isĆ
sues an invalid record or fails to respond within the host timeout period.

The record includes an endĆofĆrecord delimiter, by default <CR>, which is configĆ
ured in the initialization record.

Data records from the host (not including special commands) must be of the
same fixedĆlength, and may include endĆofĆline pad bytes. The network manager
uses the initialization record sent from the host to determine record size and endĆ
ofĆline pad lengths. IPĆbased communications have a 6Ćbyte header prefixed to
each record. See Section 5 for EM611 header information.

6980/6985 Network Manager Programmer’s Guide 3-1

SECTION 3Host-to-Network Manager Records

Record Types

This section specifies the record types for the Async host interface. For IPĆbased
interfaces, an EM611 header must prefix all records sent to a 6980 Network
Manager.

Table 3Ć1

Host-to-Network Manager Records

Record ID Type Description

0 Download

Data

1 EndĆofĆdata The host sends endĆofĆdata records in response to a download request from

2 Initialization An initialization record is sent at the beginning of a host/network manager

3 Activate

autoanswer

4 Activate

autodial

5 Deactivate

for one
minute

6 Host

Directive

The host sends download data records in response to a download request.
Information obtained from upload data links download data with a specific
handĆheld computer on a logical channel.

the network manager. This indicates that no more download data exists for
this session. EndĆofĆdata records are also sent in response to a file request to
terminate file processing.

session to set the system mode parameters and default port activation paĆ
rameters.

The host sends an activate record in response to a request record. If the reĆ
cord contains a phone number parameter, an autodial is attempted, else the
port is configured for autoanswer. Nonswitched (direct) connections are conĆ
sidered to be autoanswer.

The host sends an activate record in response to a request record. If the reĆ
cord contains a phone number parameter, an autodial is attempted, else the
port is set to autoanswer. Nonswitched (direct) connections are considered to
be autoanswer. The network manager processes autoanswer and autodial
activate records identically. A handĆheld computer port can be defined as
TTY. The activate record specifies the protocol type (TTY) to use for the next
connection.

Deactivate records can postpone activating a port for one minute. Causes a
delay between phone number dials or implements an activation window for a
port.

The host sends a directive in response to a special or download data request
from the network manager. Six subtypes of host directives are available:

" Types 1ć3 manage user data files.
" Type 4 sends download data to a handĆheld computer.
" Type 5 deactivates a request, and
" Type 6 cancels file processing.

3-2 6980/6985 Network Manager Programmer’s Guide

SECTION 3 Host-to-Network Manager Records

Download Data Record (Type 0)

The host sends a download data record in response to a download request. InĆ
formation obtained from upload data links download data with a specific computĆ
er on a logical channel.

Table 3Ć2

Type 0 — Download Data Record

Position Bytes Description

11 Beginning delimiter: /"

21 Command code: 0"

3 256, 512, 1024, 2048, or 4096

depending on configuration

259 or 1027 2 Optional CRC bytes (if enabled)

261+ or 1028+ Optional pad (up to 3 bytes)

Download data

EXAMPLE: (CR = end of record marker)

/0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxx<CRC><CRC>ppp<CR>

Beginning delimiter = “/”
Command code = Download Data “0”
Download data = “xxx”
Optional CRC bytes = 2
Optional pad = “ppp”
Optional end-of-record delimiter = <CR>

6980/6985 Network Manager Programmer’s Guide 3-3

End-of-Data Record (Type 1)

The host sends an endĆofĆdata record in response to a download request from the
network manager. This indicates that no more download data exists for this sesĆ
sion or file. The host also sends endĆofĆdata records in response to a file request
to terminate file processing.

Table 3Ć3

Type 1 — End-of-Data Record

Position Bytes Description

11 Beginning delimiter: /"

21 Command code: 1"

3 256, 512, 1024, 2048, or 4096

depending on configuration

259+ or 1027+ Optional pad (up to 5 bytes)

EXAMPLE: (CR = end of record marker)

/1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxppppp<CR>

Download data with required pad bytes if
less than 256 or 1024 bytes of data.

SECTION 3Host-to-Network Manager Records

Beginning delimiter = “/”
Command code = End-of-Data “1”
Download data = “xxx”
Optional pad = “ppppp”
Optional end-of-record delimiter = <CR>

3-4 6980/6985 Network Manager Programmer’s Guide

SECTION 3 Host-to-Network Manager Records

Initialization Record (Type 2)

At the beginning of a hostĆtoĆnetwork manager session, an initialization record
sets the system mode parameters and default port activation parameters.

Table 3Ć4

Type 2 — Initialization Record

Position Bytes Description

11Beginning delimiter: /"

21Command code: 2"

3 256 Initialization parameters list. The parameter list terminates with a slash /."

259+ Optional pad (up to 5 bytes)

EXAMPLE: (CR = end of record marker)

/2xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxx/ppppp<CR>

Beginning delimiter = “/”
Command code = Initialization Record “2”
Parameter initialization list = “xxx”
Optional pad = “ppppp”
Optional end-of-record delimiter = <CR>

The host sends the initialization record to the network manager at the beginning
of each communication session. The host can activate file processing in the netĆ
work manager using the system mode parameter (-S) in the initialization record.

EXAMPLE: /2 –S744/

Initialize network manager with the network manager file processing enabled.

The host can change system parameters with an initialization record sent at the
beginning of a session. These parameters are subdivided into system, host, and
port.

A slash /" terminates initialization parameters if the initialization record is
padded without spaces. The initialization record size is 258 bytes, minimum.

A parameter list has this general format: –[type]parm

[type] OneĆbyte field specifying the parameter type.

parm" Parameter value.

6980/6985 Network Manager Programmer’s Guide 3-5

System Mode Parameters

The network manager configuration can be customized using system
parameters. —S[system mode]

The system mode is a 1Ć to 5Ćdigit numeric (base 10) field adjusting the operaĆ
tional mode for the network manager. Mode parameters have a value and are
turned on by adding in the values for each specific mode.

These parameters are supported in the initialization record:

/* defined bits in “S” record mode */
/* system mode parameters */
/* LABEL DECIMAL BINARY */

MODE_OFF 0 /* 0000 0000 0000 0000 */
RMT_ID_ON 64 /* 0000 0000 0100 0000 */
FILES_ON 128 /* 0000 0000 1000 0000 */

System Mode Parameters

Value Meaning Description

8 Boot 4000 Series in a

LAN connected to
network manager.

Enabled when a LAN port is installed and a list of boot files exists on the
network manager's system disk.

SECTION 3Host-to-Network Manager Records

Table 3Ć5

32 2Ćbyte channel

option.

64 Remote ID on. Forward ID from remote controller to host. (Required)

128 Network manager

file processing.

512 Local ID on. Forward ID from remote controller to host. (Required)

All records to host are preceded by a 2Ćbyte channel identifier. (Required)

When added in, the host is prompted with file requests at the beginning of
a hostĆnetwork manager communications session.

3-6 6980/6985 Network Manager Programmer’s Guide

SECTION 3 Host-to-Network Manager Records

Host Parameters

The network manager's host parameters can be customized in the initialization
record.

Table 3Ć6

Host Parameters

Parameter Default Description

-C[parity] 0 1 digit numeric field setting parity and number of data bits. Valid values are:
0" = No parity/8 data bits(-C0)
1" = Odd parity/7 data bits (-C1)
2" = Even parity/7 data bits (-C2)

-D[stopbits] 1 1 digit numeric field setting stop bits. Valid values are:

1" = One stop bit (-D1)
2" = Two stop bits (-D2)
3" = Three stop bits (-D3)

-E[delimiter] 13 1Ć to 2Ćdigit numeric field specifying collating sequence number of character

marking end of all records sent from network manager to host. A delimiter of
0" specifies no endĆofĆrecord delimiter.

-B[block size] 0 Numeric field ranging from 256 to 4906 (multiples of 256 Ċ 256, 512, 1024,

2048, or 4096); specifies the minimum network managerĆtoĆhost record block
size. Does not include the endĆofĆrecord delimiter character. Records shorter
than the block size are padded to the block size and the delimiter character is
appended. Forces network manager to send fixedĆlength blocks to the host.

-G[pad char] 32 1Ć to 3Ćdigit numeric field specifying the characters that pad short blocks

when a minimum block size is specified.

-H[ready char] 63 1Ć to 3Ćdigit field specifying the host ready" directive.

-I[read timeout] 30 2Ć or 3Ćdigit numeric field specifying the maximum seconds the network manĆ

ager waits for a response from host. If no response received within set time,
the network manager will reset and await an initialization record from the
host. Valid values are 10 to 120.

-J[hostĆdelay] 0 1Ć or 2Ćdigit numeric field specifying delay in hundredth of seconds before

network manager sends next message to host after receiving a ready characĆ
ter from host. Valid values are 0 to 50.

-K[charĆgap] 10 1Ć or 2Ćdigit numeric field specifying maximum intercharacter gap time in

whole seconds allowed in a block of data sent from host. Valid values are 9 to

40.

-L[ctsĆgap] 5 1Ć to 3Ćdigit numeric field specifying maximum time in tenths of seconds the

network manager waits for CTS after RTS. Valid values are 0 to 100.

EXAMPLE: /2–E0–I60–K30/

6980/6985 Network Manager Programmer’s Guide 3-7