4985 Network Controller
PROGRAMMER’S
GUIDE
" " " " " " " " " " " " " " " " " " " " " " " " " " " "
PN: 977-028-006
Revision A
May 1996
"
NOTICE This publicationcontains information proprietary to Intermec Technologies Corpo-
ration. It is being supplied to you with the express understanding that the information contained herein is for the benefit of the contracting party only,and
may not be copied, distributed, or displayed to third parties without the express
written consent of Intermec Technologies Corporation, and shall be returned to
Intermec Technologies Corporation upon written request. If a purchase, license, or
nondisclosure agreement has been executed, the terms of that agreement shall
govern this document.
This publication is furnished for information only, and the information in it is
subject to change without notice. Although every effort has been made to provide
complete and accurate information, Intermec Technologies Corporation assumes
no responsibility or liability for any errors or inaccuracies that may appear in this
document.
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.
Wewelcome 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
NORAND and PEN*KEY are registered trademarks of Intermec Technologies
Corporation.
Ó 1991 Intermec Technologies Corporation. All rights reserved.
This publication printed on recycled paper.
Acknowledgments
MS-DOS is a registered trademark 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.
CONTENTS
" " " " " " " " " " " " " " " " " " " " " " " " " " " "
SECTION 1
Introduction 1-1. . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . .
About the Controller 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host Interfaces 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 2
Getting Started 2-1. . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . ..
Network Configurations 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4985 Configuration Switches 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication Session 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Channels 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Help 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Beeping 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connections 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Testing 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modem Indicator 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cleaning 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifications 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unpacking Equipment 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Equipment 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optional Peripherals 2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single Dock 2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multidock 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary Power Unit (APU) 2-15. . . . . . . . . . . . . . . . . . . . . . . . .
Power Supply 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modems 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location 2-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Brackets 2-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4985 Network Controller Programmer’s Guide i
CONTENTS "
Connectors 2-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AC Power 2-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 3
Installation 3-1. . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . .
Start Up Operations 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reset Button 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File System 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 4
File Structures 4-1. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . .
Introduction 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-to-Controller Records 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Commands 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Type ? - Host Ready Command 4-2. . . . . . . . . . . . . . . . . . . . . . .
Type * - Reinitialization Command 4-2. . . . . . . . . . . . . . . . . . . .
Record Layouts 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Type 0 - Download Data Record 4-3. . . . . . . . . . . . . . . . . . . . . .
Type 1 - End-of-Data Record 4-4. . . . . . . . . . . . . . . . . . . . . . . . .
Type 2 - Initialization Record 4-5. . . . . . . . . . . . . . . . . . . . . . . . .
Type 3 - Activate (Auto -Answer) Record 4-6. . . . . . . . . . . . . . . .
Type 4 - Activate (Auto -Dial) Record 4-6. . . . . . . . . . . . . . . . . .
Type 5 - Deactivate for One Minute Record 4-8. . . . . . . . . . . . .
Type 6 - Host Directive Record 4-8. . . . . . . . . . . . . . . . . . . . . . .
Type 7 - Reboot Controller Directive 4-9. . . . . . . . . . . . . . . . . .
Directive Types 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Upload Directive “1” 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Create or Load Directive “2” 4-10. . . . . . . . . . . . . . . . . . . . .
File Delete Directive “3” 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Download Directive “4” 4-12. . . . . . . . . . . . . . . . . . . . . . . . . .
File Processing Abort “6” 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller-to-Host Record Layouts 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Type 0 - Upload Data Record 4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Type 1 - End of Session Status Record 4-14. . . . . . . . . . . . . . . . . . . . .
Type 2 - Data Request Record 4 -16. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Type 3 - Inactive Status Record 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . .
Type 4 - Active Status Record 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii 4985 Network Controller Programmer’s Guide
CONTENTS "
Type 5 - Activate Request Record 4-17. . . . . . . . . . . . . . . . . . . . . . . . .
Type 6 - Special Request Record 4-18. . . . . . . . . . . . . . . . . . . . . . . . . .
Type 7 - Directive Status Record 4-19.. . . . . . . . . . . . . . . . . . . . . . . . .
Initialization Record 4-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Mode Parameters 4-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host Parameters 4-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port Parameters 4-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activation Parameters 4-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 5
Other Features 5-1. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . .
Controller-Based File Processing 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NCDIR.NCC 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-to-Controller File Processing Related Commands 5-5. . . . . . . . . . .
Initialization Record (Type 2) 5-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host Directive Record (Type 6) 5-6. . . . . . . . . . . . . . . . . . . . . . . . . .
Host Directive Subrecords (Types 1-3) 5-6. . . . . . . . . . . . . . . . . . . .
File Upload (Subtype 1) 5-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Create or Load (Subtype 2) 5-6. . . . . . . . . . . . . . . . . . . . . .
File Delete (Subtype 3) 5-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller-to-Host File Processing Related Commands 5-7. . . . . . . . . . .
Controller-to-Host Records with 2-Byte Channel ID 5-7. . . . . . . . . .
Directive Status Record (Type 7) 5-7. . . . . . . . . . . . . . . . . . . . . . . . .
Booting HHCs from Controller 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NETRPL.LST 5-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-to-Controller Session Sample 1 5-8. . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-to-Controller Session Sample 2 5-10. . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 6
Writing the Host Program 6-1. . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .
Starting the Main Routine 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receiving Data 6-4.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download Data 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ending Status Routine 6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handling Time-Fill Records 6-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating LAN Port 6-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing Special Requests 6-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4985 Network Controller Programmer’s Guide iii
CONTENTS "
Processing Directive Status Records 6-8. . . . . . . . . . . . . . . . . . . . . . . . . .
Adapting Older Host Programs 6-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record Types 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NI311 Record Types 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NI311-to-Host 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-to-NI311 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4985 Network Controller 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller-to-Host 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host-to-Controller Records 6-10.. . . . . . . . . . . . . . . . . . . . . . . . .
Special Commands 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Channels 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Record Length 6-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhancements 6-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 7
4000 Series Warm Start System 7-1. . . . . . .. . . . . . . .. . . . . . . .. . . . . . .
Creating File Maintenance Lists 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Version Number 7-4.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Converting HHC Application Programs 7-4. . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX A
Power-Up Self-Tests A-1.. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .
APPENDIX B
Communication Session B-1.. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . .
APPENDIX C
CRC Checking with Asynchronous Inter face C-1. . . . . . .. . . . . . . .. . . . .
APPENDIX D
File Structure Records D-1.. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . .
Host-to-Controller Records D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Commands D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record Layouts D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv 4985 Network Controller Programmer’s Guide
CONTENTS "
Directive Types D-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controller-to-Host Record Layouts D-7. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initialization Record D-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activation Parameters D-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURES
Figure 2-1 Host-to-4985 Using 4980 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-2 4980 Network Communications Controller Connection
to 4985 Controller 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-3 4920 Host Communications Package Connection
to 4985 Controller 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-4 4985 Multidocks with Maximum Configuration 2-3. . . . . . . .
Figure 2-5 Optional Wiring with 2 APUs Connected 2-5. . . . . . . . . . . . . .
Figure 2-6 Default Switch Settings 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-7 Typical Host-to-4985 Setup 2-7. . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-8 1-Byte Identifier 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-9 2-Byte Identifier 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-10 4985 Network Controller 2-12. . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-11 4950 Single Dock 2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-12 4960 Multidock 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-13 Auxiliary Power Unit 2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-14 Power Supply Placement and Connectors 2-16. . . . . . . . . . . .
Figure 2-15 Approximate Dimensions of Auxiliary Power Unit 2-17. . . . .
Figure 2-16 Approximate Dimensions of 4985 Network Controller 2-17. .
Figure 2-17 Approximate Dimensions of Docks 2-18. . . . . . . . . . . . . . . . .
Figure 2-18 Sample Wall Layout with Brackets 2-19. . . . . . . . . . . . . . . . . .
Figure 2-19 Vertical or Wall-MountedBracket 2-19. . . . . . . . . . . . . . . . . .
Figure 2-20 Horizontal or Shelf-Mounted Brackets 2-20. . . . . . . . . . . . . . .
Figure 2-21 Connectors on the Back of a 4985 Network Controller 2-21.
Figure 2-22 Isolated Ground Outlets 2-22. . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-1 Default Switch Settings 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLES
Table 3-1 Bank 1 Dip Switches 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-2 Bank 2 Dip Switches 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-3 Bank 3 Dip Switches 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-1 Type ? -Host Ready Command 4-2. . . . . . . . . . . . . . . . . . . . . . .
Table 4-2 Type * -Reinitialization Command 4-2. . . . . . . . . . . . . . . . . . . .
4985 Network Controller Programmer’s Guide v
CONTENTS "
Table 4-3 Type 0 -Download Data Record 4-3. . . . . . . . . . . . . . . . . . . . . .
Table 4-4 Type 1 -End-of-Data Record 4 -4. . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-5 Type 2 -Initialization Record 4-5. . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-6 Type 3 -Activate (Auto-Answer) Record 4-6. . . . . . . . . . . . . . .
Table 4-7 Type 4 -Activate (Auto-Dial) Record 4-7. . . . . . . . . . . . . . . . . .
Table 4-8 Type 5 -Deactivate for One Minute Record 4-8. . . . . . . . . . . .
Table 4-9 Type 6 -Host Directive Record 4-9. . . . . . . . . . . . . . . . . . . . . . .
Table 4-10 Type 7 -Reboot Controller Directive 4-9. . . . . . . . . . . . . . . . .
Table 4-11 File Upload Directive “1” 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-12 File Create or Load Directive “2” 4-11. . . . . . . . . . . . . . . . . . . .
Table 4-13 File Delete Directive “3” 4-12.. . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-14 File Download Directive “4” 4-12. . . . . . . . . . . . . . . . . . . . . . . .
Table 4-15 File Processing Abort “6” 4-13. . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-16 Type 0 -Upload Data Record 4-14. . . . . . . . . . . . . . . . . . . . . . .
Table 4-17 Type 1 -End of Session Status Record 4-15. . . . . . . . . . . . . . . .
Table 4-18 Type 2 -Data Request Record 4-16. . . . . . . . . . . . . . . . . . . . . . .
Table 4-19 Type 3 -Inactive Status Record 4-16. . . . . . . . . . . . . . . . . . . . . .
Table 4-20 Type 4 -Active Status Record 4-17. . . . . . . . . . . . . . . . . . . . . . .
Table 4-21 Type 5 -Activate Request Record 4-17. . . . . . . . . . . . . . . . . . . .
Table 4-22 Type 6 -Special Request Record 4-18. . . . . . . . . . . . . . . . . . . . .
Table 4-23 Type 7 -Directive Status Record 4-19. . . . . . . . . . . . . . . . . . . .
Table 4-24 System Mode Parameters 4-22. . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-25 Host Parameters 4-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-26 Type 4 -LAN Parameters 4-26. . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-1 NCDIR.NCC Record Layout 5-2. . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-2 NETRPL.LST File 5-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table A-1 Beep Count A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table D-1 Type ? -Host Ready Command D-1.. . . . . . . . . . . . . . . . . . . . .
Table D-2 Type * -Reinitialization Command D-1. . . . . . . . . . . . . . . . . . .
Table D-3 Type 0 -Download Data Record D-1. . . . . . . . . . . . . . . . . . . . .
Table D-4 Type 1 -End-of-Data Record D-2. . . . . . . . . . . . . . . . . . . . . . . . .
Table D-5 Type 2 -Initialization Record D-2. . . . . . . . . . . . . . . . . . . . . . . .
Table D-6 Type 3 -Activate (Auto-Answer) Record D-2. . . . . . . . . . . . . . .
Table D-7 Type 4 -Activate (Auto-Dial) Record D-3. . . . . . . . . . . . . . . . . .
Table D-8 Type 5 -Deactivate for One Minute Record D-3. . . . . . . . . . . .
Table D-9 Type 6 -Host Directive Record D-4. . . . . . . . . . . . . . . . . . . . . .
Table D-10 Type 7 -Reboot Controller Directive D-4. . . . . . . . . . . . . . . . .
Table D-11 File Upload Directive “1” D-4. . . . . . . . . . . . . . . . . . . . . . . . . .
Table D-12 File Create or Load Directive “2” D-5. . . . . . . . . . . . . . . . . . . .
Table D-13 File Delete Directive “3” D-6.. . . . . . . . . . . . . . . . . . . . . . . . . .
vi 4985 Network Controller Programmer’s Guide
CONTENTS "
Table D-14 File Download Directive “4” D-6. . . . . . . . . . . . . . . . . . . . . . . .
Table D-15 File Processing Abort “6” D-6. . . . . . . . . . . . . . . . . . . . . . . . . .
Table D-16 Type 0 -Upload Data Record D-7. . . . . . . . . . . . . . . . . . . . . . .
Table D-17 Type 1 -End of Session Status Record D-7. . . . . . . . . . . . . . .
Table D-18 Type 2 -Data Request Record D-8. . . . . . . . . . . . . . . . . . . . . .
Table D-19 Type 3 -Inactive Status Record D-8. . . . . . . . . . . . . . . . . . . . .
Table D-20 Type 4 -Active Status Record D-8. . . . . . . . . . . . . . . . . . . . . . .
Table D-21 Type 5 -Activate Request Record D-8. . . . . . . . . . . . . . . . . . .
Table D-22 Type 6 -Special Request Record D-9. . . . . . . . . . . . . . . . . . . .
Table D-23 Type 7 -Directive Status Record D-10. . . . . . . . . . . . . . . . . . . .
Table D-24 System Mode Parameters D-11. . . . . . . . . . . . . . . . . . . . . . . . .
Table D-25 Host Parameters D-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table D-26 Type 4 -LAN Parameters D-14. . . . . . . . . . . . . . . . . . . . . . . . . .
GLOSSARY
INDEX
4985 Network Controller Programmer’s Guide vii
CONTENTS "
viii 4985 Network Controller Programmer’s Guide
Section 1
Introduction
" " " " " " " " " " " " " " " " " " " " " " " " " " " "
The 4985 Network Communication Controller provides the communication link between a NORANDâHand-Held Computers (HHCs) and
your host computer. Two serial communication channels service the
network. The host interface channel is an RS-232 interface, while the
Local Area Network (LAN) is an RS-485 interface.
Once powered on, the 4985 Network Communication Controller re quires little or no operator intervention. Y oucan enter changes to the
host interface portion using the dip switches (located at the back of the
controller) or a host program that directs the internal soft changes.
This document aids in the writing of the interface program for your
host computer.
At the initial installation, configure the 4985 Network Controller for the
network it should operate. There are three banks of dip switches for
functional configuration of the controller. Each bank contains eight
switches. The first bank defines the type of communications, the second defines the modem type connected to the network, and the third
bank defines the controller’s unique address in your overall network.
Norand supports NORAND modems. You can enable or disable the
modem configuration by setting on or off the appropriate DIP switch.
The file maintenance system provides an HHC boot mechanism. Y our
host computer downloads a boot file list during the file processing
stage of communication. After completing file processing, all of the
files specified in the list can be downloaded to the HHC on the RS-485
network.
4985 Network Controller Programmer’s Guide 1-1
SECTION 1 " Introduction
About the Controller
This controller requires little or no operator intervention during normal operation. Once the initial configuration is complete, controller
operation becomes transparent to the user.
The power-up sequence verifies proper operation of the Read-Only
Memory (ROM), Random Access Memory (RAM), and partial testing
of the serial communication controller. Upon successful completion of
the power-up self-test, the controller sounds a single beep. Passing the
power-up self-test also implies proper operation of the internal Central
Processing Unit (CPU) and bus interface logic. A double beep indicates the host port is ready to communicate.
Should the controller beep multiple times during power-up,the controller has failed a portion of the startup test sequence. Consult the beep
counts table in Appendix A for descriptions of the error codes.
After successful power up, the controller is ready to communicate with
the device attached to the host interface port. If the host port device is
a modem, the controller may configure the modem and wait for the
remote system to call.
Y oucan access a debug facility for analysis of controller hardware and
configuration.
Host Interfaces
Y oumay need a host communication program and support programs
to talk to the controller. Norand provides two host interfaces: Asynchronous and Secondary ADCCP.
The Secondary ADCCP interface only communicates with the
NORAND 4980 Network Controller or the 4920 PC Communication
Package and can communicate locally or remotely using modems.
The asynchronous interface connects the controller directly to your
host computer. This connection provides a gateway for data to pass
between the HHCs and your host using logical channels and record
types.
This guide primarily covers the asynchronous interface which is
4980-compatible. The primary difference between the 4980 and 4985 is
1-2 4985 Network Controller Programmer’s Guide
SECTION 1 " Introduction
the 4985 Controller has only two ports and lacks a display, keypad, and
disk drive. Since one port is dedicated to the host interface, there is
only one port remaining for communicating with HHCs.
The different record types, sent back and forth between the controller
and the host, help tailor the communications session to meet that specific session’s needs.
4985 Network Controller Programmer’s Guide 1-3
SECTION 1 " Introduction
1-4 4985 Network Controller Programmer’s Guide
Section 2
Getting Started
" " " " " " " " " " " " " " " " " " " " " " " " " " " "
Network Configurations
The host port attaches to a host computer, a PC, or another controller.
This connection must use one of two datalink protocols: ASYNC or Secondary ADCCP.
ADCCP
Synchronous
ASYNC
4980 Controller
Modem
Host Computer
SADCCP
Synchronous
Modem
4960 Multidock
NPCP
4985 Controller
Figure 2-1
Host-to-4985 Using 4980
Figure 2-1 demonstrates the host computer directly connecting to a
4980 Network Controller, wired to a synchronous modem. A telephone
4985 Network Controller Programmer’s Guide 2-1
SECTION 2 " Getting Started
line or lease links the two identical modems. Both modems must be
configured exactly alike for smooth communications. The 4985 Network Controller connects to the modem with the host port.
Figure 2-2 shows the 4980 Network Controller on the left connected to
a host computer. The 4985 Controller on the right is at a remote site,
hooked up with at least one six-pack multidock.
4980 Network
Controller
Modem
-OR-
Direct Connect
Modem
4985 Controller
4980 Network Communications Controller Connection to 4985 Controller
Figure 2-2
Figure 2-3 shows a setup using the 4920 Communications Package for
a PC connection to the 4985 Controller.
Modem
-OR-
Direct Connect
4920 Host Communications Package
(Includes Communication Coprocessor)
Figure 2-3
4920 Host Communications Package Connection to 4985 Controller
2-2 4985 Network Controller Programmer’s Guide
Modem
4985 Controller
SECTION 2 " Getting Started
Figure 2-4 has the most Hand-Held Computers (HHCs) that can communicate through one 4985 Controller. The NORANDâAuxiliary Power Units (APUs) connect in series with the multidocks.
4985 Controller
Multidock Multidock
APU
Multidock Multidock
APU
Multidock Multidock
Multidock MultidockMultidock
Multidock
4985 Multidocks with Maximum Configuration
Figure 2-4
4985 Network Controller Programmer’s Guide 2-3
SECTION 2 " Getting Started
"
NOTE: Add APUs to the network when using more than two multidocks. This ensures
adequate power for the multidocks to recharge the HHCs when placed in these
docks. One APU powers four multidocks. The controller powers two multidocks
directly.
Figure 2-5 differs from Figure 2-4 by connecting the two APUs together instead of chaining the second APU in series to a multidock. The
second APU connects directly to the first APU.
2-4 4985 Network Controller Programmer’s Guide
SECTION 2 " Getting Started
4985 Controller
Multidock Multidock
APU
Multidock Multidock
APU
Multidock Multidock
Multidock MultidockMultidock
Multidock
Optional Wiring with 2 APUs Connected
Figure 2-5
If hooking up the maximum number of multidocks allowed, use the
wiring diagram in Figures 2-4 or 2-5. Take into consideration your
power outlets and physical setup.
4985 Network Controller Programmer’s Guide 2-5
SECTION 2 " Getting Started
4985 Configuration Switches
Three 8-position DIP switches allows a user to customize the 4985 for
their particular system application. Switches “1” through “5” of DIP
bank #2 apply only to ADCCP host applications. DIP bank #3 configures the controllers identification number for a large system. The controller converts this 8-bit ID to an ASCII decimal number in the
49850000 to 49850255 range. This ID goes to the host computer at the
start of the host-to-controller communication session. The default value is “49850000” and “49850255” is reserved.
"
NOTE: Details of the three Data Input (DI) bank switches start on page 3-1.
Figure 2-6 shows switch settings for connecting the 4985 Network Controller to the 4980 Network Controller or the 4920 Communication
Package using Secondary ADCCP and a NM9600 Modem.
O
1 2 3 4 5 6 7 8
N
Bank 1
Default Switch Settings
Figure 2-6
O
1 2 3 4 5 6 7 8
N
Bank 2
Bank 1: Switch 1: Command mode is off
Switch 2: Communications mode uses Secondary
ADCCP
Switch 3-5: Communications uses external clocking to
determine speed
Switch 6: Reserved.
Switch 7-8: Sets controller to handle three channels
active to HHCs concurrently.
"
NOTE: All reserved switches or those not applicable must be in the off position.
Bank 2: Switch 1: Auto-configure the modem
Switch 2-3: Auto-dialing is off
2-6 4985 Network Controller Programmer’s Guide
Switch 4: Auto-answer is off
Switch 5: Controller sends AT&F command to modem
Switch 6: Reserved.
Switch 7-8: Three logical channels enabled.
Communication Session
This describes the host-to-HHC communication session. Session examples illustrate what is happening, physically and logically.
SECTION 2 " Getting Started
before configuring.
Host
4985 Network Controller
ASYNC
Direct-Connected
Figure 2-7
Typical Host-to-4985 Setup
4960 Multidock
The host communicates with the 4985 Controller using the NORAND
asynchronous proprietary protocol. The multidock connects to the
LAN port on the 4985 Controller and the host to the HOST port.
The primary controller use is to facilitate the host-to-HHC communication session. The controller provides the physical connection necessary for communication, and maintains the session on a logical channel. This allows you more options to expand your communications
network.
A logical channel between an HHC and your host always passes
through one or more controllers on a logical channel.
The logical channel ID prefixes all records sent from the controller to
the host. It is a 1-byte field if you have disabled device channels and a
2-byte field if you have enabled device channels.
4985 Network Controller Programmer’s Guide 2-7
SECTION 2 " Getting Started
In this case, logical channels, specified by a single HHC channel ID,
prefix each record sent from the controller.
Logical Channel
Record Type Data
Figure 2-8
1-Byte Identifier
The 4985 Network Controller uses the 2-byte identifier option for compatibility. It consists of four parts.
Device Channel
Logical Channel Record Type Data
Figure 2-9
2-Byte Identifier
A device channel is zero as the 4985 is directly connected, the ASYNC
interface is used, and an HHC channel will be “1”, “4”, or “7.” The device channel identifies which controller the HHC channel belongs to.
After making the physical connection, the communication session for
all HHC types is identical. The HHCs’ protocol is transparent to the
host computer.
The communication session for an HHC consists of:
" Upload phase
" Download phase
" End-of-Session status from the HHC
Typically, the HHC sends its ID in the first upload record. The host
uses this information to tie a set of download data as specific HHC.
EXAMPLE: The host receives upload records from an HHC on a logical channel until the
upload is complete. The host then receives download data requests on the same
logical channel from the HHC. The host, using the HHC’s terminal ID, organizes
the requested download data and sends the download data to the HHC on the
logical channel until finished. At this point, the HHC reports the session status by
sending an end-of-session record to the host.
2-8 4985 Network Controller Programmer’s Guide
Configuration information sent to the controller from the host is sent in
the system initialization record at the start of communication.
The host can fine-tune the system and port configurations to meet the
needs of a particular communications session.
Device Channels
Some things to remember:
" A logical channel number and record type prefix all controller
" HHC data is in a contiguous sequence on a logical channel.
" The host telecommunications program must maintain state vari-
Help
The controller runs several self-diagnostic programs during power-up,
ensuring the equipment is in normal working order. If a problem during power-up, the controller beeps several times and the unit does not
operate.
SECTION 2 " Getting Started
data.
ables and file pointers indexed by the logical channel number.
Beeping
The most common problems are often easiest to detect, and in many
cases, correct. These include loose cable connections, loss of AC power, bad or no telecommunication, and sometimes faulty equipment.
The HHC display sometimes helps to diagnose a problem.
The controller performs a series of power-up self-tests each time it
powers on. A single beep indicates that all power-up tests passed. Two
beeps indicate the host port has reset and is ready to communicate. A
long beep or a short pattern of beeps repeating for longer than 30 seconds indicate a problem with the internal hardware. The unit must go
to a service center for repair. These beeps are diagnostic tools for the
service technician. See Appendix A for a list of beep counts and their
problem areas.
4985 Network Controller Programmer’s Guide 2-9
SECTION 2 " Getting Started
Connections
During the installation and startup testing, the system should have
made all connections to the controller and its peripherals. If problems
do occur, ensure that the system has fully seated connectors. Ensure
that power connections are attached securely to wall outlets.
Testing
Diagnostics can run through a command interpreter on the RS-232
port using an attached ASCII terminal. These tests require a technician to access the highly technical test findings.
Modem Indicator
Modems frequently have LEDs to show events as they happen. If a
LED should light but does not, the modem manual and this information can help determine where the trouble exists. The modem could
be bad, or the connections to either the controller or to the telephone
lines could be defective. The modem indicators, if any, can help isolate
a telecommunication (TCOM) problem.
Cleaning
Periodic cleaning maintain the appearance and reliability of the controller. When cleaning, inspect for damage or wear. Clean the controller
with a soft cloth dampened with a quality glass cleaner. Do not use sol
vent solutions.
Specifications
Communication Protocol Support:
RS-232 Secondary ADCCP (9.6Kbps) or Host Async (38.4Kbps)
RS-485 NPCP (500Kbps)
2-10 4985 Network Controller Programmer’s Guide
Hardware
SECTION 2 " Getting Started
Environmental: Operating temperature: 32° to 122° Fahrenheit
0° to 50° Celsius
Memory: 512K Internal RAM
128K Internal ROM
Microprocessor: 80C186 @ 8 MHz
Physical: Height: 9.5 inches (241 mm)
Width: 13 inches (330 mm)
Depth: 7.5 inches (191 mm)
Weight: 5lbs
Chassis: 0.063 inch-thick (1.6 mm)
#5052H32 aluminum
Power Capacity: 12HHCs maximum
Power Supply: External: +15 Volts @ 3.5 Amps
Serial Interfaces: RS-232 1 port
RS-485 1 port
B
CAUTION: Applying cleaners directly to any part of the controller will damage the
controller. Do not use alcohol, benzene, carbon tetrachloride, or any other
solvents to clean any portion of the controller. Use a soft, lint-free cloth
moistened in a quality glass cleaner to clean the exterior of the controller.
B
CAUTION: Using the controller in an hostile environment that includes temperature
extremes or where moisture can enter the unit will damage the controller.
Operate the controller indoors, sheltered from precipitation.
"
NOTE: Ensure that a properly wired, isolated-ground AC outlet powers the power sup-
ply for the controller. Properly installed isolated ground outlets and wiring produce a relatively ElectroMagnetic Interference (EMI) or noise free environment.
This ensures proper operation of sensitive electronics such as computers and
telecommunications devices.
Unpacking Equipment
Inspect the shipping containers for signs of damage before unpacking
the equipment. If any damage, you must immediately report that fact
to the carrier.
4985 Network Controller Programmer’s Guide 2-11
SECTION 2 " Getting Started
Remove equipment and materials from the shipping containers and
examine all items to become familiar with their physical characteristics. Check for signs of damage before you proceed.
Install mounting brackets in pairs, on 6-inch centers for the controller
and the Auxiliary Power Unit (APU), and on 16-inch centers for the
multidocks.
We do not provide mounting hardware. Use 1/4-inch hardware suitable for your wall or mounting surfaces (such as concrete block,
poured concrete, drywall, plywood, sheet-metal, countertop, shelving,
or a table).
LAN
RS485
HOST/MODEM
RS232
CONFIG SWITCHESRESET
ROUTECOMMANDER
R
4000 SERIES
Front Back
Figure 2-10
4985 Network Controller
General Equipment
The controller interfaces between a group of HHCs and another controller,or a larger computer, such as a PC or mainframe. It is a lowcost controller for remote networks supporting 12 or fewer HHCs.
At each remote site, a controller connects to the HHCs by cables and a
peripheral device, such as multidock or single dock. In turn, the controller connects to other network controller devices, a PC, modems, or
a larger computer (host site) through cables or telephone link.
2-12 4985 Network Controller Programmer’s Guide
INPUT
15
V
3.5
A
SECTION 2 " Getting Started
This provides flexible, software-controlled 2 -way communication of
data, messages, and program changes between a host computer and
many HHCs. The controller acts as a buffer (temporary storage) and
control device to ensure orderly communication and minimal errors.
The controller provides communication power and charging voltage for
up to twelve 4000 Series HHCs. Add an APU to expand the network
beyond the power supply capabilities of the controller. Connect up to
two APUs and ten multidocks in series to one 4985 Network Controller.
Optional Peripherals
Optional peripheral devices allow for flexibility and customization:
Single Dock
Figure 2-11
4950 Single Dock
The 4950 Single Dock accommodates one HHC. Use the single dock
under specific restrictions. Special consideration for system power is
required. See your Norand Systems Engineer for details.
4985 Network Controller Programmer’s Guide 2-13
SECTION 2 " Getting Started
Multidock
Chain the 4960 multidocks together with cables to increase the number of HHCs connected to each controller. Each rack has six docks for
the 4000 Series HHCs.
Figure 2-12
4960 Multidock
2-14 4985 Network Controller Programmer’s Guide
Auxiliary Power Unit (APU)
SECTION 2 " Getting Started
Auxiliary Power Unit
Figure 2-13
Place an APU in the network after the first two multidocks, before the
next group of four multidocks. The APU furnishes charging current to
the next group of multidocks and also strengthens signals on the communication lines to ensure reliable, error-freedata transmission in both
directions. There can be a maximum of two APUs and ten multidocks.
4985 Network Controller Programmer’s Guide 2-15
SECTION 2 " Getting Started
Power Supply
Insert your power cord from standard outlet plugs here.
Power Supply Placement and Connectors
Place the power supply on the attached mounting shelf located at the
back of the controller.
Modems
Limit the modem configuration to support these two modems: NORAND NM2400A and NORAND 9600.
Enter remote auto-dial phone numbers into the NORAND modems.
Use the NORAND 9600 Modem front panel to enter the numbers. Use
an RS-232 terminal to enter the phone numbers into an NM2400A. Refer to the operation documents for your modem before entering phone
numbers into the modem.
2-16 4985 Network Controller Programmer’s Guide
Connect the network controller to
this power supply outlet.
Figure 2-14
Loading...