Download Print this page

Intermec 200 System Manual

Intermec 200 controllers: user guide

Hide thumbs Also See for 200:

Quick reference manual (117 pages)

,

Getting started manual (2 pages)

Table Of Contents

page of 695

/ 695
Contents
Table of Contents
Bookmarks

Table of Contents

Advertisement

Quick Links

Download this manual See also: Quick Reference Manual

System Manual

P/N 063439-005

Model 200 Controller

Table of Contents

Advertisement

Table of Contents

Need help?

Need help?

Do you have a question about the 200 and is the answer not in the manual?

Questions and answers

Summary of Contents for Intermec 200

Page 1 System Manual P/N 063439-005 Model 200 Controller...
Page 2 Model 200 Controller. Made other minor corrections throughout the entire manual. Combined the information in the JANUS™ Devices Quick Reference Guide with the Model 200 Controller User’s Manual. 04/97 Addendum 065395-001 was added to the manual. This addendum supports version 2.4 of the controller software,...
Page 3 test...
Page 4 Quick Reference Guide Fast Setup...
Page 5 The information contained herein is proprietary and is provided solely for the purpose of allowing customers to operate and/or service Intermec manufactured equipment and is not to be released, reproduced, or used for any other purpose without written permission of Intermec. Information and specifications in this manual are subject to change without notice.
Page 6: Table Of Contents
Step 5 - Set Up the Data Collection Environment 16 Configuring an RF Card for Your Network 18 Configuring a UDP Plus Network 19 Configuring an Intermec Controller for Your Network 21 Verify Your Data Collection Environment 21 Step 6 - Set Up the Host Communications Environment 24...
Page 7 Fast Setup Quick Reference Guide Setting Up 3270 SNA Terminal Emulation 41 Setting Up Peer-to-Peer Links 47 Setting Up a Terminal Session 53 Verify Your Host Connection 65 Step 8 - Start the Controller 66 Where Do You Go From Here? 68 Index...
Page 8: About Fast Setup
This quick reference guide explains how to use Fast Setup to configure the Model 200 Controller. About Fast Setup Use Fast Setup to configure the Model 200 Controller quickly so you can demonstrate the controller. verify your network environment is functioning.
Page 9: Using Online Help
9180 Network Controller, an uninterruptable power supply, or an external modem. Using Online Help The Model 200 Controller includes online help that provides descriptions of the toolbars, dialog boxes, and options. Help also includes step-by-step procedures and some background information.
Page 10 Fast Setup Quick Reference Guide Connecting the Controller to Your Data Collection Network Host 2.4 GHz T2425 JG2050 JG2020 Access Point Ethernet Model 200 Controller CrossBar 900 MHz 9154 9181 9445 J2050 9189 3400 J2010 JR2020 0200-024 3400...
Page 11: Step 1 - Complete The Worksheets
Step 1 - Complete the Worksheets Before you use Fast Setup, complete the relevant worksheets in Appendix E in the Model 200 Controller User’s Manual. You will need to obtain much of this information from your network administrator. After you have completed the worksheets, you will have all the information you need to run Fast Setup and to configure the controller successfully.
Page 12: Power Cord
The standard power cord that comes with the controller is a 110V U.S. cord. If you need another power cord, contact your local Intermec representative. Note: Intermec recommends that you plug the power cord into a surge protector or an uninterruptable power supply.
Page 13: Step 3 - Install The Controller
Fast Setup Quick Reference Guide Step 3 - Install the Controller You must physically connect the Model 200 Controller to your data collection network and to your host environment. Connecting to Your Data Collection Network Connect the controller to your data collection network. For help, see “Installing the Controller”...
Page 14: Turning On The Controller
Turning on the Controller When you turn on the controller for the first time, a dialog box appears that lists the network adapter cards, RF controller cards, and COM ports in your controller. Choose one of the following options: If you want this dialog box to appear every time the controller boots, choose Show at Boot Time.
Page 15: About The Fast Setup Main Menu
Fast Setup Quick Reference Guide About the Fast Setup Main Menu This main menu appears whenever you turn on the Model 200 Controller. In the title bar, [Save] and [Activate] appear when you make changes to the configuration that you need to save and activate. The Fast Setup main menu has three parts.
Page 16: Step 4 - Set The System Parameters
Fast Setup Quick Reference Guide Step 4 - Set the System Parameters When you set these system parameters, you are defining the operating parameters for the Model 200 Controller.
Page 17 Fast Setup Quick Reference Guide Field Description Send to downline This check box determines if the Model devices every... 200 Controller sends its time to all external Intermec controllers..minutes This field specifies how often in minutes the controller sends the time synchronization message.
Page 18 2. Enable or disable time synchronization. A check in the check box indicates that time synchronization is enabled. Enter how often you want the controller to send the time broadcast to all external Intermec controllers and BRUs. 3. In the File Transfer Time box, enter how long you want the controller to wait for a response from a device when it is downloading files to that device, before it times out.
Page 19: Step 5 - Set Up The Data Collection Environment
Model 200 Controller to 9180 Worksheet Model 200 Controller to CrossBar Worksheet You can use Fast Setup to define the parameters for any external Intermec controllers that exist downline from the Model 200 Controller, for RF controller cards that you may have inside the controller, and for the controller to communicate with the TRAKKER®...
Page 20 To get to the Fast Setup for Downline Network dialog box, from the main menu choose Fast Setup and then choose Downline Network. Field Description Configured The external Intermec controllers, RF Connections controller cards, or UDP Plus that you have already configured. Available...
Page 21: Configuring An Rf Card For Your Network
The channel that the RF controller card will use. Multi-Drop and The number of device addresses to be enabled for the RF controller card, UDP Plus, or an external Intermec controller. Point-to-Point The number of device addresses to be (9161 only) enabled on the 9161 controller.
Page 22: Configuring A Udp Plus Network
Configuring a UDP Plus Network 1. In the Available Connections list box, select UDP Plus. 2. Choose Configure to save your changes. The Setup for UDP Plus Terminals dialog box appears. To set up the UDP Plus devices using a DNS server 1.
Page 23 Fast Setup Quick Reference Guide 4. In the Domain field, enter the name of the domain that all of the terminals are in. Note: If you enable the Use DNS check box and you do not enter a domain, the server searches the domains that are listed in the DNS Configuration dialog box.
Page 24: Configuring An Intermec Controller For Your Network
Verify Your Data Collection Environment Once you configure the Fast Setup for Downline Network dialog box, you may want to verify that you have a connection between the Model 200 controller and a device. When sending a transaction to a device (destination), make sure that your device is ready to accept the transaction.
Page 25 Fast Setup Quick Reference Guide Before you verify your data collection environment, make sure you activate your current configuration and start data collection. To get to the Send Transaction dialog box, from the main menu sidebar buttons choose System Maintenance. The System Maintenance dialog box appears.
Page 26 To verify your data collection environment 1. (Optional) In the Source ID field, enter a destination name that you want to use as the source of the transaction. 2. If you want to send the transaction to one device, in the Destination ID field enter the logical name of the device that you are using to verify the connection.
Page 27: Step 6 - Set Up The Host Communications Environment
Step 6 - Set Up the Host Communications Environment To set up the host communications environment, you need to configure any network adapter cards in your Model 200 Controller. The network adapter cards that your controller may contain are: Ethernet...
Page 28: Ethernet Adapter Card
Adapter Cards Worksheet to help you fill in the fields in this dialog box. Note: The default setting for the Ethernet adapter card is 10BaseT. Contact your local Intermec representative if you are using 10Base2 or 10Base5. Note: If your controller contains two cards (two Ethernet cards or one Ethernet and one token ring card) that communicate using TCP/IP, each card must use a different subnet.
Page 29 Fast Setup Quick Reference Guide Field Description Ethernet TCP/IP The Ethernet card that you are card configuring. Use DHCP This check box enables this network adapter card to be administered by a DHCP server. Local host name A meaningful name that identifies the (Optional) controller to the network.
Page 30: Token Ring Adapter Card
If you are configuring the token ring card in the controller for a TCP/IP network, you need to use Advanced Setup. For help, see Chapter 5, “Connecting to an Ethernet/Token Ring Network” in the Model 200 Controller User’s Manual. If you are not using your token ring card in a TCP/IP network, you do not need to set any parameters for a token ring adapter connection.
Page 31: Twinaxial Adapter Card
Fast Setup Quick Reference Guide Twinaxial Adapter Card If you have a twinaxial adapter card in the controller, you can use Fast Setup to establish a twinaxial connection between the controller and your host. Use the information from the Network Adapter Cards Worksheet to help you fill in the Controller address field in this dialog box.
Page 32: Sdlc Adapter Card
Fast Setup assumes that you are using a leased line for your SDLC configuration. To change this parameter, you must use Advanced Setup. For help, see Chapter 7, “Connecting to an SDLC Network” in the Model 200 Controller User’s Manual.
Page 33: Step 7 - Configure The Host Environment Parameters
Fast Setup Quick Reference Guide Step 7 - Configure the Host Environment Parameters You need to define the host environment parameters that tell the Model 200 Controller how to communicate with the host. Perform one of these procedures: Set up VT100/220/320, ANSI, 5250, or 3270 terminal emulation.
Page 34: Setting Up Telnet Terminal Emulation
Note: You may need to load the correct TE software on all of the JANUS devices that you will be using as terminals. This software is available on the Model 200 Controller. Refer to Chapter 8, “Using Terminal Emulation” in the Model 200 Controller User’s Manual.
Page 35 Fast Setup Quick Reference Guide Field Description Host Name This list box contains the names of the defined TCP/IP hosts. Host Name - The list of terminals that are linked to a Linked Terminals selected host. Available The list of all the terminals that are Terminals available to link to a host.
Page 36 To set up Telnet terminal emulation 1. Choose Telnet Terminal Emulation. The Telnet Terminal Emulation Configuration dialog box appears. 2. Make sure you have added all the Telnet hosts that the terminals will access. The Host Name list box contains all the defined host names. To add a host, follow the instructions in “Adding a TCP/IP Host”...
Page 37 Fast Setup Quick Reference Guide Adding a TCP/IP Host To communicate with TCP/IP hosts, the Model 200 Controller must know their IP addresses. You can either use DNS to resolve these IP addresses or you can enter them in manually.
Page 38 To determine the host IP address using DNS 1. From the Telnet Terminal Emulation Configuration dialog box, choose Add. The TCP/IP Host Connection dialog box appears. 2. In the Host name field, enter the abbreviated or long host name. If you enter the abbreviated name, the controller searches the domain names in the DNS Configuration dialog box to determine the long host name.
Page 39: Setting Up 5250 Sna Terminal Emulation
Note: Your JANUS 900 MHz RF devices and your TRAKKER Antares terminals come with the 5250 TE software already loaded. However, this software is also available on the Model 200 Controller. Also, you must configure your terminals to use the SNA protocol.
Page 40 Field Description Host Name This list box contains the names of the defined SNA hosts. Use device This check box determines if the names selected host in the Host Name list box uses the logical name of the devices when establishing terminal sessions. Host Name - The list of terminals that are linked to a Linked Terminals...
Page 41 Fast Setup Quick Reference Guide To set up 5250 terminal emulation 1. Choose 5250 Terminal Emulation. The 5250 Terminal Emulation Configuration dialog box appears. 2. Make sure you have added all the SNA hosts that the terminals will access for terminal emulation. The Host Name list box contains all the defined host names.
Page 42 Adding an IBM SNA Host Field Description Host name A name that identifies this SNA host. You can use this internal name to make the host LU name more meaningful. Adapter card The network adapter card you are using to connect to the host. Network ID Identifies the network ID on which the host resides.
Page 43 Fast Setup Quick Reference Guide To add an IBM SNA host 1. From the 5250 Terminal Emulation Configuration dialog box, choose Add. The Host Connection Configuration dialog box appears. 2. In the Host name field, enter a meaningful name for the host. 3.
Page 44: Setting Up 3270 Sna Terminal Emulation
Note: Your JANUS 900 MHz RF devices and your TRAKKER Antares terminals come with the 3270 TE software already loaded. However, this software is also available on the Model 200 Controller. Also, you must configure your terminals to use the SNA protocol.
Page 45 Fast Setup Quick Reference Guide Field Description Host Name This list box contains the names of the defined SNA hosts. Host Name - The list of terminals and their NAUs Linked Terminal that are linked to a selected host. - NAU Available The list of all terminals that are Terminals...
Page 46 To set up 3270 terminal emulation 1. Choose 3270 Terminal Emulation. The 3270 Terminal Emulation Configuration dialog box appears. 2. Make sure you have added all the SNA hosts that the terminals will access for terminal emulation. The Host Name list box contains all the defined host names.
Page 47 Fast Setup Quick Reference Guide Adding an IBM SNA Host Field Description Host name A name that identifies this SNA host. You can use this internal name to make the host LU name more meaningful. Adapter card The network adapter card you are using to connect to the host.
Page 48 To add an IBM SNA host 1. From the 3270 Terminal Emulation Configuration dialog box, choose Add. The Host Connection Configuration dialog box appears. 2. In the Host name field, enter a meaningful name for the host. 3. In the Adapter card field, click the down arrow on the right side of the field.
Page 49 Fast Setup Quick Reference Guide 1. From the 3270 Terminal Emulation Configuration dialog box, choose NAU Pool. The 3270 NAU Pool dialog box appears. 2. Add all the NAUs to the NAU pool. Note: Once an NAU is in the pool, you cannot use it in an explicit link. a.
Page 50: Setting Up Peer-To-Peer Links
Setting Up Peer-to-Peer Links To run TCP/IP or APPC applications in your data collection network, you must define all the destination names in the Model 200 Controller. The controller puts these names in a peer-to-peer destination list. You must also specify which transactions the controller routes to each application.
Page 51 Fast Setup Quick Reference Guide Field Description Destination name The name of the destination (application). Hot Standby The number of seconds the controller timeout waits for a response from a destination before it places the transactions going to that destination in a Hot Standby file. Transactions held The number of transactions the in volatile...
Page 52 (application) that will accept the transactions in the Transaction box. Note: You need to add the name of each data collection device in a 2.4 GHz RF network that will communicate with the Model 200 Controller. 3. In the Hot Standby timeout field, enter the number of seconds the controller waits for an acknowledgment from the destination before it places the transactions going to that destination in a Hot Standby file.
Page 53 Fast Setup Quick Reference Guide 8. Add any transaction IDs that are not listed in the Available list box. Follow the instructions in the next section, “Adding a Transaction.” 9. (Optional) In the Delivery Responses box, enter the messages you want to send to the transaction source.
Page 54 Field Description Transaction ID The unique name of the transaction. Hot Standby The message that is sent to the source of message the transaction when the controller (Optional) places the transactions for the destination in a Hot Standby file. Delimiter The character that separates the fields in the transaction.
Page 55 Fast Setup Quick Reference Guide To add transaction fields Field Description Field name The unique name for the transaction field. Number The position of the field in the transaction. 1. From the Transaction Parameters dialog box, choose Add. The Transaction Field Parameters dialog box appears. 2.
Page 56: Setting Up A Terminal Session
Setting Up a Terminal Session You can use Fast Setup to establish VT, ANSI, 5250, or 3270 terminal sessions between the controller and your host. Use these sessions to access your host directly from the controller. By accessing your host, you can verify your host connection and you can start remote applications.
Page 57 Fast Setup Quick Reference Guide Configuring a VT/ANSI Terminal Session Field Description Name A meaningful name for this terminal session. Terminal mode The type of terminal mode you want to use for this terminal session. Host Name The name of the TCP/IP host to which the terminal session connects.
Page 58 To configure a VT/ANSI terminal session 1. Choose VT. The Terminal Session Definition dialog box appears. 2. In the Session box, enter a meaningful name for the session. 3. In the Terminal mode field, click the down arrow on the right side of the field.
Page 59 Fast Setup Quick Reference Guide Customizing the VT Terminal Setup When you add a new VT or ANSI terminal session and you choose Custom, the VT Setup dialog box automatically appears. If you have already created a terminal session and you want to edit the fields in this dialog box, from the Terminal Session list box, select the terminal session and then choose Edit.
Page 60 Field Description Cursor keys Determines whether the arrow keys on the terminal control cursor movement or they send their application control functions. Keypad Determines whether the number keys on the terminal send their keycap characters or they send their programming functions. Line wrap This check box determines if text enabled...
Page 61 Fast Setup Quick Reference Guide To customize the terminal setup Note: If you are defining VT100 terminals, the option buttons in the Controls box and the User-Defined Key box are grayed out. 1. In the Terminal Keys box, choose Normal if you want to use the terminal cursor keys to move the cursor.
Page 62 Fast Setup Quick Reference Guide Configuring a 5250 Terminal Session...
Page 63 Fast Setup Quick Reference Guide Field Description Name A meaningful name for this terminal session. Host Name The name of the SNA host to which the terminal session connects. Mode name This name describes the class of service and other session characteristics that you may want for your network.
Page 64 To configure a 5250 terminal session 1. Choose 5250. The Terminal Session Definition dialog box appears. 2. In the Session box, enter a meaningful name for the session. 3. In the Host Name box, click the down arrow on the right side of the field.
Page 65 Fast Setup Quick Reference Guide Configuring a 3270 Terminal Session Field Description Name A meaningful name for this terminal session. Host Name The name of the SNA host to which the terminal session connects. Number of The number of terminal sessions you sessions want to configure to this host.
Page 66 To configure a 3270 terminal session 1. Choose 3270. The Terminal Session Definition dialog box appears. 2. In the Session box, enter a meaningful name for the session. 3. In the Host Name box, click the down arrow on the right side of the field.
Page 67 Fast Setup Quick Reference Guide Starting a Host Session Once you have set up your terminal sessions on the controller, you can start the host session from the controller. To start a host session 1. From the main menu sidebar buttons, choose System Maintenance. The System Maintenance dialog box appears.
Page 68: Verify Your Host Connection
Once you configure the network adapter cards and your host connection, you may want to use the Send Transactions feature to verify that you have a connection between the Model 200 Controller and your host. For help, see “Verifying Your Data Collection Environment” earlier in this quick reference guide.
Page 69: Step 8 - Start The Controller
Before you start the Model 200 Controller, make sure you have performed these tasks: 1. Connected and configured all external Intermec controllers and devices. 2. Connected the Model 200 Controller to the host and the data collection network. 3. Used Fast Setup to configure the data collection environment.
Page 70 3. From the main menu on the controller, choose Start Data Collection. A message box appears confirming that you want to start data collection. 4. Choose Start. 5. Start the applications on the host. 6. Start the applications on the devices. To stop the controller 1.
Page 71: Where Do You Go From Here
Where Do You Go From Here? Now that your controller is installed in your network, you can perform terminal emulation or send transactions from your Intermec data collection devices to your host. If you need to perform Advanced Setup to edit or delete some of the parameters, or if you need to configure screen mapping, see the Model 200 Controller User’s Manual.
Page 72 Index...
Page 73 Fast Setup Quick Reference Guide...
Page 74 UDP Plus network, 19 configuring a VT/ANSI terminal session, 54 configuring an RF card, 18 configuring external Intermec controllers, 21 configuring the host environment parameters, configuring the local network adapter cards, 24 connecting to your data collection network, 10...
Page 75 Multi-Drop and RF field, 18 Network ID field, 18 Point-to-Point field, 18 RF channel field, 18 Serial port field, 18 Fast Setup for Intermec Hardware dialog box, Configure button, 16 Fast Setup toolbar button, 11 Field name field, 52 File Transfer Time box, 14...
Page 76 Model 200 Controller to 9180 and CrossBar Worksheet, 16 Model 200 Controller to 9180 Worksheet, 16 Model 200 Controller to CrossBar Worksheet, 16 Model 200 Controller to RF Card Worksheet, 16 Model 200 Controller to TRAKKER Antares Terminals Worksheet, 16 monitor, 8, 9...
Page 77 Fast Setup Quick Reference Guide online help, using, 6 parameters setting host environment, 30 setting system, 13 Password field, 60 peer-to-peer applications setting up, 30 setting up links, 47 Peer-to-Peer Destination Parameters dialog box, Available list box, 48 Destination name field, 48 Hot standby field, 48 Hot Standby timeout field, 48 Interactive response field, 48...
Page 78 66 Starting IP address field, 20 steps, configuring controller Host Connections, 12 Intermec Hardware, 12 Local Network Adapters, 12 Stop Data Collection sidebar button, 67 stopping data collection, 67 Strip pad field, 14 Subnet mask, 26 System Maintenance sidebar button...
Page 79 Fast Setup Quick Reference Guide Transaction Parameters dialog box, 50 Delimiter field, 51 Hot Standby message field, 51 Transaction ID field, 51 Transactions held in volatile memory field, 48 transactions, adding, 50 turning on the controller, 11 twinaxial adapter card, configuring, 28 Twinaxial Protocol Configuration dialog box, 28 Controller address field, 28 UDP Plus network, 16...
Page 80 User’s Manual Model 200 Controller...
Page 81 The information contained herein is proprietary and is provided solely for the purpose of allowing customers to operate and/or service Intermec manufactured equipment and is not to be released, reproduced, or used for any other purpose without written permission of Intermec. Information and specifications in this manual are subject to change without notice.
Page 82 Before You Begin xvii Warranty Information xvii Safety Summary xvii Warnings and Cautions xviii About This Manual xix Other Intermec Manuals xxii Learning About the Controller Chapter Checklist 1-3 Features 1-4 What’s New for Release 3.1? 1-5 Unpacking the Controller 1-7...
Page 83 Model 200 Controller User’s Manual How the Controller Acknowledges Transactions 1-25 How the Controller Ensures Data Integrity 1-25 Interactivity With Data Collection Devices 1-25 Data Integrity Modes 1-28 Retaining Transactions in Memory 1-29 How the Controller Sets Application Status 1-30...
Page 84 Starting Data Collection 2-24 Stopping Data Collection 2-25 Turning Off the Controller 2-25 Accessing a Command Prompt 2-26 Connecting to the Intermec RF Network Chapter Checklist 3-3 Connecting the Controller to the 900 MHz RF Network 3-4 Configuring RF Controller Cards 3-6...
Page 85 Model 200 Controller User’s Manual Editing a UDP Plus Device 3-33 Saving Your Run-Time Configuration 3-37 Connecting to the 9180 and the Intermec CrossBar Network Chapter Checklist 4-3 Configuring an External Intermec Controller 4-4 Adding a Controller 4-5 About the Controller Parameters 4-6...
Page 86 Configuring the Network Adapter Card for TCP/IP 5-6 Using DNS 5-10 Clearing the IP Address and Subnet Mask 5-12 Using the Routing Daemon 5-12 Configuring Routing Tables 5-14 Configuring the Network Adapter Card for IEEE 802.2 5-16 Saving Your Run-Time Configuration 5-19 Connecting to a Coaxial/Twinaxial Network Chapter Checklist 6-3 Installing the Controller 6-4...
Page 87 Model 200 Controller User’s Manual Using Terminal Emulation Chapter Checklist 8-3 About Terminal Emulation 8-5 JANUS TE Application 8-6 TRAKKER Antares TE Application 8-7 Setting Up Telnet Terminal Emulation 8-7 Configuring the Controller 8-7 Setting Up 5250 SNA Terminal Emulation 8-12...
Page 88 Exiting the TE Configuration Menu 8-36 Starting TE 8-36 Ending TE 8-37 About Running TE 8-37 About the Auto-Login Feature 8-38 Displaying International Characters 8-39 Configuring Your TRAKKER Antares Terminals 8-40 Configuring for Communications 8-40 Downloading the TRAKKER Antares TE Application 8-41 Accessing the TE Configuration Menu 8-43 Exiting the TE Configuration Menu 8-44 About Running TE on Your Terminals 8-45...
Page 89 Model 200 Controller User’s Manual Communicating With TCP/IP Applications 9-16 How the Controller Communicates With Applications 9-18 Understanding Transaction Routing in a TCP/IP Network 9-20 Communicating Through the Direct TCP/IP Socket Interface 9-23 Direct TCP/IP API vs. NetComm API 9-25...
Page 90 Starting a Host Session 10-26 Mapping Terminal Keyboards to the Model 200 Controller Keyboard 10-27 Using Screen Mapping Chapter Checklist 11-3 About Screen Mapping 11-5 About Script Files 11-7 Preparing to Use the Script Builder Tool 11-7 Single Transaction Script Files vs. Multiple Transaction Script Files 11-8...
Page 91 Model 200 Controller User’s Manual Selecting Transactions for the Script 11-34 Selecting Host Screens for the Current Transaction 11-36 Defining Next Screen Sequences for Host Screens 11-37 Selecting Host Screen Fields for the Current Host Screen 11-39 Selecting Regions for the Current Host Screen 11-43...
Page 92 Building Terminal Screens for Data Collection Devices 11-83 Adding a Terminal Screen 11-87 Adding a Terminal Field 11-89 Validating a Terminal Field 11-93 Getting Terminal Field Attributes From a Host Screen 11-95 Getting Terminal Field Attributes From the Script File 11-96 Defining Next Screen Sequence for Terminal Screens 11-97 Copying a Terminal Screen 11-99 Building Menus From Screens 11-100...
Page 93 Model 200 Controller User’s Manual Troubleshooting General Troubleshooting A-3 Using the System Reporting Tools A-5 Viewing the Configuration A-5 Viewing and Clearing the Hot Standby Files A-7 Message Box Error Messages A-9 Error Log Error Messages A-26 Viewing the Error Messages A-26...
Page 94 Using Download Server Commands to Transfer Files B-18 Using the Controller to Configure TRAKKER Antares Terminals B-20 Using Remote Console About Remote Console C-3 Configuring the NetOp Host (Model 200 Controller) C-3 Configuring for TCP/IP or Dial-Up SLIP C-4 Configuring for APPC C-6 Configuring Security C-8...
Page 95 Model 200 Controller User’s Manual Managing System Firmware and Applications D-17 Viewing Upgrade Event Details D-18 Viewing the Event Log D-20 Worksheets Glossary Index...
Page 96 Warranty Information To receive a copy of the standard warranty provision for this product, contact your local Intermec sales organization. In the U.S. call (800) 755- 5505, and in Canada call (800) 688-7043. Otherwise, refer to the Worldwide Sales & Service list that comes with this manual for the address and telephone number of your Intermec sales organization.
Page 97 Model 200 Controller User’s Manual Warnings and Cautions The warnings and cautions in this manual use the following format. Warning A warning alerts you of an operating procedure, practice, condition, or statement that must be strictly observed to avoid death or serious injury to the persons working on the equipment.
Page 98 About This Manual All the information you need to install, configure, maintain, and troubleshoot the Model 200 Controller is in this manual. Information in this manual should be used by the person who will be installing and configuring the controller. Many of the parameters need to be set by the network administrator.
Page 99 Model 200 Controller User’s Manual Double-click Move your mouse pointer to the item and click the left mouse button twice quickly. In many dialog boxes, you can double-click on an item instead of selecting it and choosing a button. Input From a Host or PC Keyboard When you need to press keys on your host or PC, they are emphasized in bold.
Page 100 Commands Command syntax is shown in the text as it should be entered. For example, to see a list of directories on the JANUS device, type this command: If a command line includes both required and optional parameters, optional parameters are enclosed in braces [ ]. Configuration commands use the convention data to indicate variables.
Page 101 Model 200 Controller User’s Manual Other Intermec Manuals You may need additional information when working with the Model 200 Controller in an Intermec data collection network. Please visit our web site at www.intermec.com to access many of our available manuals in PDF format.
Page 102 Other Intermec Manuals (continued) Manual Intermec CrossBar Products 9154 Multi-Drop Line Controller System Manual 9160A Installation Manual 9161A Operator Guide 9161B Programmer/Operator Guide 9161B Installation Manual Before You Begin Intermec Part No. 048517 044170 046070 049574 049572 xxiii...
Page 103 Model 200 Controller User’s Manual xxiv...
Page 104 Learning About the Controller...
Page 105 Model 200 Controller User’s Manual...
Page 106 This chapter helps you learn about the features of the Model 200 Controller and how the controller works with your LAN and Intermec’s data collection network. Chapter Checklist Done? Task Understand the features of your Model 200 Controller. Unpack the controller.
Page 107 Model 200 Controller User’s Manual Features The Model 200 Controller is a network controller that connects Intermec’s wired and wireless products either to your local area network or directly to a host. Your controller has many important features that make it easy to integrate it into your data collection system.
Page 108 TCP/IP applications. Support for double-byte character sets (DBCS) and data streams. Support for remote access to the Model 200 Controller using a third party remote console package. Ability to print to a printer attached to a terminal serial port that is within all terminal emulation clients.
Page 109 Model 200 Controller User’s Manual Connecting the Model 200 Controller to Intermec’s Data Collection Network 900 MHz 9181 J2050 9189 JR2020 3400 Host 2.4 GHz JG2020 Model 200 Ethernet Controller 9154 3400 T2425 JG2050 Access Point CrossBar 9445 J2010 0200-024...
Page 110 Unpacking the Controller 1. Set the controller on a clean, stable, flat surface and remove the accessories, packing material, and the Model 200 Controller from the shipping container. 2. Save the shipping container and packing material in case you need to move or ship your controller.
Page 111 Model 200 Controller User’s Manual Contents of the Model 200 Controller Package e r s ’ n u a M o d e l 2 0 0 C o n t r o l l e r 0200-002...
Page 112 Description The Model 200 Controller contains several components on the front panel and on the rear panel that you should be able to identify. Understanding the Front Panel CONTROLLER Model 200 Component Power switch Power on indicator Floppy disk access indicator...
Page 113 Description Provides AC power for accessories. Sets the voltage of your controller to 110V or 220V. Provides connections for external Intermec controllers, a modem, or other devices that require serial ports to connect to your controller. Prevents your controller from overheating. When situating your controller, do not place it where the fan is obstructed.
Page 114 About the Graphical User Interface When you are ready to turn on the Model 200 Controller, push the yellow power switch. When you power on the controller for the first time, a dialog box appears that lists the network adapter cards in your controller. Choose...
Page 115 Hot Standby files, and defining system parameters. Using Help The Model 200 Controller includes online help that provides descriptions of the controller toolbars, dialog boxes, and options. Help also provides procedural information and limited background information.
Page 116 Choose Contents to look up a topic in the contents. To learn more about using Help From the sidebar buttons, choose Help. Navigating Through Dialog Boxes In the Model 200 Controller, there are various ways that you can move through dialog boxes: To Do This Action Do This Action...
Page 117 Model 200 Controller User’s Manual Understanding the Dialog Box Buttons These are the most common buttons that appear in the dialog boxes when you are configuring the Model 200 Controller. Button Cancel Help Close Edit Delete 1-14 Description Choose OK to save any changes you have made in the dialog box and exit from that dialog box.
Page 118 How the Controller Works The Model 200 Controller is composed of several software components working together to perform routing functions. For more information about these components, see your DCS 300 Technical Reference Manual. Graphical user interface (GUI) controller. You use it to set up your run-time configuration by defining the...
Page 119 Model 200 Controller User’s Manual Network communication processes (NetComms) NetComms are the communication links between remote applications and the controller. TCP/IP NetComms use TCP sockets to send and receive data from the message handler. APPC NetComms use APPC sessions to send and receive data from the message handler.
Page 120 About Transactions Communications from an application through the Model 200 Controller to data collection devices and other applications involve two types of transactions: data transactions and system transactions. Data Transactions The message handler uses the transaction ID to determine the destinations for a transaction;...
Page 121 How the Controller Routes Transactions Transactions have a well-defined structure consisting of a header and data. The header contains a transaction ID, which the Model 200 Controller uses to determine the destination for a transaction. The transaction ID is the primary routing mechanism used by the controller.
Page 122 If the destination is a device, the message handler determines the name of the DevComm that is servicing that device and forwards the transaction to it. The DevComm receives the transaction, translates the logical name into a physical device address, strips the header from the transaction, and transmits the data to the device.
Page 123 Model 200 Controller User’s Manual Routing Transactions From Applications Local Area Network 9181 Base Radio Unit 1-20 Application Network Connection Receive DevComm NetComm Receive Message Handler Model 200 Controller Readers Remote APP3 Network Connection Send NetComm APP3 APP3 200.074...
Page 124 Routing Transactions From Devices This example discusses the steps to move data from the data collection device to the application. The numbers on the following paragraphs correspond to the numbers on the illustration on the next page. Data is entered at the bar code reader and transmitted through the BRU to the controller.
Page 125 Model 200 Controller User’s Manual Routing Transactions From Devices 9181 Base Radio Unit Local Area Network 1-22 Readers Model 200 Controller Message Handler Receive Receive DevComm NetComm Network Connection Standby APP3 APP3 Send NetComm Network Connection 200.070 Remote Application APP3...
Page 126 Note: Steps 5 through 12 occur for each application that receives a transaction sent by the message handler. Steps 9, 10, and 11 are different for TCP/IP and APPC applications. The message handler determines the correct destination for the transaction. It then checks a flag for the destination to see if it is currently an active or an inactive application: If the application is active, the message handler attempts to deliver the...
Page 127 Model 200 Controller User’s Manual Routing Transactions From Data Collection Devices (continued) 9181 Base Radio Unit Local Area Network 1-24 Readers Model 200 Controller Message Handler Receive Receive DevComm NetComm Network Connection Remote Application APP3 Standby APP3 APP3 Send NetComm...
Page 128 Hot Standby file. A success delivery response for external controllers only indicates that the transaction was successfully transmitted to the device that is communicating directly with the controller.
Page 129 Model 200 Controller User’s Manual There are three levels of interactivity which the controller provides to an application when it is communicating with a device in a data collection network: Fully interactive Partially interactive Noninteractive The levels of interactivity refer to an application’s ability to complete a handshake with the device.
Page 130 Learning About the Controller Partially Interactive System In a partially interactive system, the data collection device is interactive with the controller instead of the application. To guarantee data integrity, the controller sends its acknowledgment to the device only after it has written a transaction to the Hot Standby file.
Page 131 Model 200 Controller User’s Manual Data Integrity Modes The Model 200 Controller operates in one of two data integrity modes for external Intermec controllers: Faster and Safer. You define the data integrity mode for each external controller that the Model 200 Controller uses to communicate with devices (such as terminals, readers, and printers).
Page 132 Retaining Transactions in Memory AUX_Q is an auxiliary queue in volatile memory. By default, the Model 200 Controller uses this queue as a temporary holding place for transactions that are waiting to be sent to a destination while the controller is waiting for an ACK from that destination.
Page 133 Model 200 Controller User’s Manual How the Controller Sets Application Status When the Model 200 Controller is initialized or first starts up, all application channels listed in the configuration file are assumed to be nonactive or batch destinations. This means that until otherwise notified, the message handler automatically routes transactions for these applications to Hot Standby files.
Page 134 Active Applications An active application completes a handshake with the Model 200 Controller for each transaction it receives. The message handler ensures that data is secure by requiring an ACK transaction from the application receiving the data. The controller can deliver only one transaction at a time to each application.
Page 135 Model 200 Controller User’s Manual Sending Hot Standby Messages When the controller receives a transaction for a nonactive application, it can send a user-defined response to the device that was the source of the transaction. This optional, user-defined response is known as the Hot Standby message.
Page 136 Active Recovery Mode Before entering a fully active state, the application goes through a recovery period, called Active Recovery mode. The Model 200 Controller takes transactions from the application’s Hot Standby file and sends them in chronological (FIFO) order to the application. The application must acknowledge each transaction just as if it were active.
Page 137 Model 200 Controller User’s Manual...
Page 138 Setting Up the Controller...
Page 139 Understand how to start data collection, stop data collection, and shut down the controller. If you already understand and have performed these tasks, connect the controller to your Intermec data collection network as described in these chapters: Chapter 3, “Connecting to the Intermec RF Network”...
Page 140 Model 200 Controller User’s Manual Plugging In the Power Cord You need to attach the power cord before you can run the Model 200 Controller. However, you may want to plug the power cord into an uninterruptable power supply (UPS). Intermec requires that you use a surge protector in locations that use 115 VAC.
Page 141 Setting Up the Controller Plugging In the Keyboard You may need to use the keyboard to enter information when using the GUI to configure the Model 200 Controller. Equipment Keyboard (standard) To plug in the keyboard 1. Locate the keyboard port on the rear panel of the controller.
Page 142 Model 200 Controller User’s Manual Plugging In the Mouse The mouse makes it easier for you to move around in the GUI when configuring the Model 200 Controller. Note: You must have the mouse plugged into the controller whenever you boot the controller.
Page 143 Connecting the Monitor Equipment Monitor with cable and power cord (not provided) To connect the monitor to the controller 1. Locate the video port on the rear panel of the controller. 2. Insert one end of the monitor’s cable into the video port. 3.
Page 144 Connecting an Uninterruptable Power Supply Intermec strongly recommends that you connect an uninterruptable power supply (UPS) to your Model 200 Controller. In case of a power failure, the UPS provides enough backup power to allow the Model 200 Controller to properly shut down and minimize the loss of data.
Page 145 10. In the System Maintenance list box, choose Install Accessories and then choose Start. The Install Accessories dialog box appears. 11. Choose UPS. 12. In the Available Ports list box, select the serial port on the Model 200 Controller that you used to connect to the UPS. Setting Up the Controller...
Page 146 Model 200 Controller User’s Manual 13. Choose OK to save your changes. You return to the System Maintenance dialog box. 14. Choose Close to return to the main menu. Uninterruptable power supply To AC power 2-10 0200-009...
Page 147 Connecting a Modem You may want to connect your Model 200 Controller to a modem. If you have remote console support enabled on your server, you may want to use a modem to let you access the controller GUI using a PC with a modem.
Page 148 Start. The Install Accessories dialog box appears. 9. Choose Modem. 10. In the Available Ports list box, select the serial port on the Model 200 Controller that you used to connect to the modem. 11. Choose OK to save your changes. You return to the System Maintenance dialog box.
Page 149 Setting Up the Controller Connecting the Model 200 Controller to a Modem phone line To AC power 0200-014 2-13...
Page 150 Intermec controllers. Note: The time broadcast is not necessarily sent to the data collection devices that are connected to the external Intermec controllers. However, when you configure a controller, you can configure it to broadcast the time to its devices.
Page 151 Field Description Send to downline This check box determines if the Model devices every... 200 Controller sends its time to all external Intermec controllers..minutes This field specifies how often in minutes the controller sends the time synchronization message. File Transfer Time...
Page 152 Model 200 Controller User’s Manual To set the system parameters 1. From the main menu sidebar buttons, choose System Parameters. The System Parameters dialog box appears. 2. Enable or disable time synchronization. A check in the check box indicates that time synchronization is enabled. Enter how often (in minutes) you want the controller to send the time broadcast to all external Intermec controllers.
Page 153 Start Data Collection. Restoring Default Configuration This procedure restores the factory default configuration of the Model 200 Controller. If you want to load your backed up system files or run-time configuration, see “Restoring Your System Files and Run-Time Configuration”...
Page 154 6. Press Ctrl-Alt-Del to reboot the controller. Backing Up the Controller Configuration Once you have configured your Intermec hardware, have set up your host communications, and have set up your host environment parameters, you can start data collection on your Model 200 Controller.
Page 155 Backing Up Your User Files You must back up any user files so that you can restore them if your controller loses its configuration. For example, if you are using screen mapping, you may want to back up your script (.SCR) and template (.TPL) files.
Page 156 8. From the File Handling dialog box, choose Close to return to the main menu. Restoring the Controller Configuration If your Model 200 Controller loses its configuration, you can recover the system files and run-time configuration. Restoring Your System Files and Run-Time Configuration 1.
Page 157 Restoring Your User Files You can also use this feature to transfer files, such as validation files or applications, from a floppy disk to the controller. To restore your user files 1. Insert the 3.5-inch disk that contains the backup of your user files into the controller disk drive.
Page 158 Model 200 Controller User’s Manual 5. In the Available Files list box, add all the files that you want to restore to the Selected Files list box. a. Select the file name. b. Choose Select. The file name appears in the Selected Files list box.
Page 159 Deleting User Files 1. From the main menu sidebar buttons, choose File Handling. The File Handling dialog box appears. 2. In the File Handling list box, select Delete User Files and then choose Start. The Delete User Files dialog box appears. 3.
Page 160 Model 200 Controller User’s Manual Using the Controller To use the Model 200 Controller, you need to know how to start and stop data collection and shut down the controller. Caution Always choose Shutdown Controller before rebooting or turning off the controller.
Page 161 Stopping Data Collection You may need to stop data collection on your Model 200 Controller to update its configuration file. When you stop data collection, all data collection activities are stopped, but any external Intermec controllers continue polling and buffering data. Data collection devices using programs that require a response directly from a destination (interactive mode) also stop until the controller is started again.
Page 162 Model 200 Controller User’s Manual Accessing a Command Prompt While maintaining or configuring your controller, you may find your task is easier by accessing a command prompt. To access a command prompt 1. From the main menu sidebar buttons, choose System Maintenance. The System Maintenance dialog box appears.
Page 163 Connecting to the Intermec RF Network...
Page 164 Model 200 Controller User’s Manual...
Page 165 This chapter explains how to connect the Model 200 Controller to the 900 MHz RF network using RF controller cards and BRUs and to the UDP Plus network using access points, JANUS devices, and TRAKKER Antares terminals. Chapter Checklist Done? Task Connect the controller to the 900 MHz RF network.
Page 166 BRU, you need to configure these BRUs using the 9180 controller’s configuration menu. Refer to your 9180 user’s manual. To connect the Model 200 Controller and the BRU, you need to know if you have 2-port or 4-port RF controller cards in the controller. Cables must be ordered separately.
Page 167 Connecting to the Intermec RF Network Example: The Model 200 Controller Connected to the Intermec 900 MHz RF Network Host Model 200 9181 9181 9450 J2050 9189 JR2020 9465 0200-028 3400...
Page 168 Model 200 Controller User’s Manual Configuring RF Controller Cards You need to configure the communications parameters, enable the BRUs, set the Hot Standby timeout, and set any special time parameters for the RF controller cards. Use the worksheets in Appendix E.
Page 169 Connecting to the Intermec RF Network To configure the RF controller card 1. From the main menu, choose the type of communication you are using to connect the controller to the host. 2. Choose Downline Network. Two buttons, Connection Points and Downline Devices, appear.
Page 170 Model 200 Controller User’s Manual Field Description Card number The RF controller card that you want to configure. RFNC address The radio frequency network address of the RF controller card. Devices use this address to communicate with the BRUs attached to this card.
Page 171 Transactions held The number of transactions the in volatile controller keeps in RAM before it writes memory the transactions to a Hot Standby file. Connecting to the Intermec RF Network Value Default 0 to 255 0 to 255 Check, Clear...
Page 172 8. In the Repeat count field, enter the number of repeaters each message is allowed to pass through. Note: Intermec recommends that a message does not pass through more than three repeaters. Using more than three repeaters may cause excessive delays when communicating with the terminals.
Page 173 Connecting to the Intermec RF Network Setting the Time Parameters Use this dialog box to configure the broadcast and append parameters between the BRUs and their devices. Note: When the controller sends a time broadcast, it is not a guaranteed packet.
Page 174 Model 200 Controller User’s Manual Field Description Broadcast This check box determines if the BRUs enabled broadcast a time to all devices communicating with them. Include Seconds This check box adds seconds to the time. Include Date This check box adds the date to the time.
Page 175 This character separates the data from the appended date and time. Julian date This check box determines if the date is in a 3-digit Julian format. Connecting to the Intermec RF Network Value Default 12 hour, 24 hour 12 hour...
Page 176 Model 200 Controller User’s Manual To set the time parameters 1. From the Setup for Controller dialog box, in the Configure box, choose Time Parameters. The Configure Time Parameters dialog box appears. 2. In the Broadcast Parameters box, enable or disable the time broadcast. A check in the Broadcast enabled check box means that time broadcast is enabled.
Page 177 Connecting to the Intermec RF Network Identifying the RF Devices You need to configure the Model 200 Controller for all the devices that use it to communicate with the host. The device list contains the logical names of all 128 devices. The first eight names are enabled and are configured as JANUS 2020s.
Page 178 Model 200 Controller User’s Manual 4. In the Connection field, click the down arrow on the right side of the field. A list of the connection points that you have configured appears. Select the RF controller card for which you want to enable devices.
Page 179 This check box determines if this device data can receive data from the network. Device type This list box contains the current Intermec devices that are supported. Connecting to the Intermec RF Network Value Default 1 to 16 ISA1XXX alphanumeric...
Page 180 4. In the Device type field, click the down arrow on the right side of the field. A list of all the supported Intermec devices appears. Select the type of device you are configuring. 5. In the Auto-insert from device field, click the down arrow on the right side of the field.
Page 181 FTP, with the controller. The illustration on the next page shows an example of a Model 200 Controller connected to a UDP Plus network. You can also use the controller to route any IP traffic from one subnet to the controller.
Page 182 Novell NetWare Client for DOS and Novell LAN Workplace for DOS. Intermec recommends that you use LAN Workplace to provide the TCP/IP protocol stack. Example: The Model 200 Controller Connected to the Intermec 2.4 GHz RF Network Host Model 200...
Page 183 Connecting to the Intermec RF Network Configuring a UDP Plus Network You need to configure the UDP Plus network if you want the Model 200 Controller to communicate with TRAKKER Antares terminals and JANUS devices that are using UDP Plus. Use the worksheets in Appendix E.
Page 184 Model 200 Controller User’s Manual Adding a UDP Plus Network 1. In the Connection Point List dialog box, choose Add. The Add a Downline Connection Point dialog box appears. 2. In the Downline Connections list box, select UDP Plus. 3. Choose Add. The UDP Plus Network Parameters dialog box appears.
Page 185 “not responding.” 6. In the Inactivity timer field, enter the amount of time in minutes the device can be “not responding” before it is set to “disconnected.” Connecting to the Intermec RF Network Value Default...
Page 186 Model 200 Controller User’s Manual 7. In the Local field, enter the number of the port the controller uses to communicate with itself. This port must be different from the network port. 8. In the Network field, enter the number of the port that the UDP Plus network uses for communication.
Page 187 Connecting to the Intermec RF Network Setting Up the UDP Plus Devices The Model 200 Controller must know the IP address for every UDP Plus terminal that it may communicate with. You can either use the controller to generate logical names for each terminal and use a DNS server to resolve the IP addresses or you can enter each terminal’s IP address.
Page 188 Model 200 Controller User’s Manual Field Description Number of The number of IP addresses you want terminals to the controller to generate. enable Use DNS This check box determines if the controller uses a DNS server to translate the logical name to an IP address.
Page 189 Connecting to the Intermec RF Network 4. In the Domain field, enter the name of the domain that all of the terminals are in. Note: If you enable the Use DNS check box and you do not enter a domain, the controller searches the domains that are listed in the DNS Configuration dialog box.
Page 190 Model 200 Controller User’s Manual Setting the Time Parameters Use this dialog box to configure the broadcast and append parameters between the controller and the UDP Plus terminals. Broadcast Parameters These optional parameters allow the controller to broadcast a time at certain intervals to all UDP Plus terminals. These parameters synchronize the terminals with the controller.
Page 191 This check box determines if a timestamp is added to messages from devices. Include Year This check box adds the 4-digit year to the time. Connecting to the Intermec RF Network Value Default Check, Clear Clear 0 to 99 Check, Clear...
Page 192 Model 200 Controller User’s Manual Field Description Include Month This check box adds the 2-digit month to the time. Include Day This check box adds the 2-digit day to the time. Include Seconds This check box adds a 2-digit seconds to the time.
Page 193 Parameters dialog box. Identifying the UDP Plus Devices You need to configure the Model 200 Controller for the logical names and IP addresses of the UDP Plus terminals that use it to communicate with the host. The device list contains the logical names of all 128 terminals. The first eight names are enabled and are configured as TRAKKER 2400s.
Page 194 Model 200 Controller User’s Manual 4. In the Connection field, click the down arrow on the right side of the field. A list of the connection points that you have configured appears. Select UDP Plus. 5. To enable all 128 terminals, choose Enable All.
Page 195 Connecting to the Intermec RF Network 7. Select a terminal whose individual parameters you want to edit and choose Edit Device. For help, see “Editing a UDP Plus Device” in the next section. 8. Choose OK to save your changes and return to the main menu.
Page 196 Model 200 Controller User’s Manual Field Description Logical name The logical name of the terminal. Able to receive This check box determines if this data terminal can receive data from the network. Device type This list box contains all the current Intermec devices supported.
Page 197 Connecting to the Intermec RF Network 4. In the Device type field, click the down arrow on the right side of the field. A list of all the devices that can run in a UDP Plus network appears. Select a device.
Page 198 Model 200 Controller User’s Manual Determining a UDP Plus Device’s IP Address If you are using a DNS server and you want to know the IP address of a terminal, from the Device Parameters dialog box, choose Addressing. The Device Address dialog box appears.
Page 199 Connecting to the Intermec RF Network Editing a UDP Plus Device’s IP Address If you are not using a DNS server and you want to edit the IP address of a terminal, from the Device Parameters dialog box, choose Addressing. The Device Address dialog box appears.
Page 200 Model 200 Controller User’s Manual...
Page 201 Connecting to the 9180 and the Intermec CrossBar Network...
Page 202 Model 200 Controller User’s Manual...
Page 203 Note: In order for the 9181 Base Radio Units (BRUs) to communicate with a 9180 Network Controller that is connected to the Model 200 Controller, you need to configure these BRUs using the 9180 configuration menu. Refer to your 9180 user’s manual.
Page 204 An external Intermec controller is a 9180 Network Controller, 9161 Port Concentrator, or a 9154 Multi-Drop Line Controller that is connected to the Model 200 Controller through a serial port. The following illustration is an example of a controller connected to a 9180 and a CrossBar network.
Page 205 Connecting to the 9180 and the Intermec CrossBar Network To configure the controller to work with an external Intermec controller 1. From the main menu, choose the type of communication you are using to connect the controller to the host.
Page 206 Model 200 Controller communicates with the controllers that are connected to it. Make sure that any communication parameters that you define on the Model 200 Controller are the same as the parameters set on the external Intermec controller.
Page 207 Connecting to the 9180 and the Intermec CrossBar Network Adding a 9154 Controller Field Description Serial port The communications port to which the 9154 controller is connected. Baud rate The baud rate at which the serial port communicates. LRC enabled...
Page 208 Stop bits The number of bits to use for setting communications protocol. Hot Standby The number of seconds the Model 200 Timeout Controller waits for a response from the 9154 controller before it places the 9154 controller in Hot Standby mode.
Page 209 Connecting to the 9180 and the Intermec CrossBar Network 6. In the Hot Standby Timeout box, enter the number of seconds you want the Model 200 Controller to wait for a response from the 9154 controller before it places the 9154 controller in Hot Standby mode.
Page 210 Model 200 Controller User’s Manual Adding a 9161 Controller Field Description Serial port The communications port to which the 9161 controller is connected. Baud rate The baud rate at which the serial port communicates. LRC enabled This check box determines if the...
Page 211 Connecting to the 9180 and the Intermec CrossBar Network Field Description Stop bits The number of bits to use for setting communications protocol. Hot Standby The number of seconds the Model 200 Timeout Controller waits for a response from the 9161 controller before it places the 9161 controller in Hot Standby mode.
Page 212 Model 200 Controller User’s Manual 6. In the Hot Standby Timeout box, enter the number of seconds you want the Model 200 Controller to wait for a response from the 9161 controller before it places the 9161 controller in Hot Standby mode.
Page 213 Connecting to the 9180 and the Intermec CrossBar Network Adding a 9180 Controller Field Description Serial port The communications port to which the 9180 controller is connected. Baud rate The baud rate at which the serial port communicates. LRC enabled...
Page 214 9180 controller. 6. In the Hot Standby Timeout box, enter the number of seconds you want the Model 200 Controller to wait for a response from the 9180 controller before it places the 9180 controller in Hot Standby mode.
Page 215 Model 200 Controller with its external Intermec controllers. If the external Intermec controller does not support one of the parameters, it is grayed out. Broadcast Parameters These optional parameters broadcast a time, with a short string, at certain intervals from the external Intermec controller to all data collection devices connected to it.
Page 216 This feature will not operate when running terminal emulation or using the direct TCP/IP socket interface. Note: Do not enable time append on both the external Intermec controller and the data collection device itself. If it is enabled on both, two timestamps are appended to incoming data.
Page 217 Connecting to the 9180 and the Intermec CrossBar Network Field Description Broadcast This check box determines if the enabled external Intermec controller broadcasts its time to its devices. Include Seconds This check box adds seconds to the (9180 only) time.
Page 218 Model 200 Controller User’s Manual To configure the time parameters 1. From the Setup for Controller dialog box, in the Time Parameters box, choose Configure. The Configure Time Parameters dialog box appears. 2. In the Broadcast Parameters box, enable or disable the time broadcast. A check in the Broadcast enabled check box means that time broadcast is enabled.
Page 219 12. Choose OK to save your changes and return to the Setup for Controller dialog box. Identifying the CrossBar Devices The Model 200 Controller needs to know the addresses of all the devices that use it to communicate with the host. This section explains how to configure the controller for the CrossBar devices.
Page 220 Model 200 Controller User’s Manual 3. Choose Downline Devices. The Device List dialog box appears. 4. In the Connection field, click the down arrow on the right side of the field. A list of the controllers that are configured appears.
Page 221 Connecting to the 9180 and the Intermec CrossBar Network 8. Select a device whose individual parameters you want to edit and choose Edit Device. For help, see “Editing a CrossBar Device” in the next section. 9. Choose OK to save your changes and return to the main menu.
Page 222 Model 200 Controller User’s Manual Field Description Device type This list box contains all the current Intermec devices supported by the Model 200 Controller. Physical address This read-only field displays the physical address of the device. Auto-insert from This field adds a transaction ID to end...
Page 223 Connecting to the 9180 and the Intermec CrossBar Network 4. In the Device type field, click the down arrow on the right side of the field. A list of all the supported Intermec devices appears. Select the type of device you are configuring.
Page 224 Model 200 Controller User’s Manual...
Page 225 Connecting to an Ethernet/ Token Ring Network...
Page 226 Model 200 Controller User’s Manual...
Page 227 This chapter describes how to install the controller in your Ethernet or token ring network and how to configure the network adapter card. Chapter Checklist Done? Task Install the controller in the Ethernet network. Install the controller in the token ring network. Use the GUI to configure each Ethernet and token ring card for TCP/IP.
Page 228 Your Model 200 Controller contains a 10/100 Mbps Ethernet card. The card automatically switches between 10 Mbps and 100 Mbps. The default configuration for the Ethernet card is 10BaseT or 100BaseTX. Before you can configure the Model 200 Controller, you need to install it in your network. Equipment An Ethernet connection where you can connect the controller.
Page 229 Installing the Controller in a Token Ring Network Before you can configure the Model 200 Controller, you need to install it in your network. Equipment A token ring connection where you can connect the controller. A cable to connect the controller to the connection. Your token ring card comes with an RJ-45 to STP cable.
Page 230 Model 200 Controller User’s Manual Configuring the Network Adapter Card for TCP/IP After you install the Model 200 Controller, you need to turn it on and configure its network adapter cards. Ethernet and token ring cards support both TCP/IP and IEEE 802.2 protocols. Use the worksheets in Appendix E.
Page 231 Connecting to an Ethernet/Token Ring Network To configure the network adapter card 1. From the main menu, choose the type of communication you are using to connect the controller to the host. 2. Choose Local Network Adapter. Five buttons for different network adapter card types appear.
Page 232 Model 200 Controller User’s Manual 5. (Token ring only) Choose the ring speed of your token ring network. The default ring speed is 16 Mbps. 6. Choose Advanced. The TCP/IP Protocol Configuration dialog box appears. Field Description TCP/IP card The card that you are configuring.
Page 233 Connecting to an Ethernet/Token Ring Network To configure the TCP/IP protocol 1. In the TCP/IP Protocol Configuration dialog box, click the down arrow on the right side of the TCP/IP card field. A list of Ethernet cards that are installed in your controller appears. Select the card you want to configure.
Page 234 Model 200 Controller User’s Manual Using DNS The controller supports the use of Domain Name System (DNS) servers in your network. DNS lets you configure single or multiple name servers, which will resolve name/IP address conversions of hosts and devices. The controller automatically obtains these IP addresses from the DNS server, along with any changes.
Page 235 Field Description Name Server List of IP addresses of DNS servers (in Addresses search order) that are used to resolve TCP/IP host names. Domain Names List of internet domains (in search order) that are searched when an abbreviated TCP/IP host name is entered.
Page 236 Using the Routing Daemon The routing daemon tells the Model 200 Controller how to route IP packets in an IP network. Generally, the routing daemon is sufficient for standard network configuration, but you may also configure explicit routes. Obtain these routes from your network administrator.
Page 237 Connecting to an Ethernet/Token Ring Network To enable or disable the routing daemon 1. From the TCP/IP Protocol Configuration dialog box, choose Routing. The Routing Table Entries Configuration dialog box appears. 2. To enable the routing daemon, check the check box for Enable routing daemon.
Page 238 Model 200 Controller User’s Manual Configuring Routing Tables There are four types of routes you can configure: default, network, subnet, and host. The default route specifies a route that can be used as a destination for an IP packet if a route for the IP packet is not specified.
Page 239 Connecting to an Ethernet/Token Ring Network To add a routing table entry 1. From the TCP/IP Protocol Configuration dialog box, choose Routing. The Routing Table Entries Configuration dialog box appears. 2. Select a route in the list box and choose Add before or Add after. The Configure Route dialog box appears.
Page 240 Configuring the Network Adapter Card for IEEE 802.2 After you install the Model 200 Controller, you need to turn it on and configure its network adapter cards. Ethernet and token ring support both TCP/IP and IEEE 802.2 protocols. Use the worksheets in Appendix E.
Page 241 Connecting to an Ethernet/Token Ring Network Advanced Protocol Configuration Dialog Box for the Token Ring Card 4. In the Protocols field, click the down arrow on the right side of the field. Select IEEE 802.2. 5. (Token ring only) Choose the ring speed of your token ring network. The default ring speed is 16 Mbps.
Page 242 Model 200 Controller User’s Manual Field Description IEEE 802.2 card The card that you are configuring. Network adapter The locally administered MAC address address in IEEE format (hex) that identifies the (Optional) card. Ethernet driver The Ethernet frame type you are using.
Page 243 Connecting to an Ethernet/Token Ring Network Saving Your Run-Time Configuration When you finish configuring your network adapter card, you should save your changes. To save your run-time configuration From the main menu sidebar buttons, choose Save Configuration. 5-19...
Page 244 Model 200 Controller User’s Manual...
Page 245 Connecting to a Coaxial/Twinaxial Network...
Page 246 Model 200 Controller User’s Manual...
Page 247 This chapter describes how to connect the controller to your host using a coaxial or twinaxial connection and it also explains how to configure the network adapter card. Chapter Checklist Done? Task Install the controller. Use the GUI to configure the coaxial card for the coaxial network.
Page 248 Model 200 Controller User’s Manual Installing the Controller Before you can configure the Model 200 Controller, you need to install it in your network. Equipment A coaxial or twinaxial connection where you can connect the controller. A cable to connect the controller to the connection. You can use a RG-58 coaxial cable, or for a twinaxial connection you can use 15 conductor IBM custom cable.
Page 249 Connecting to a Coaxial/Twinaxial Network Configuring the Coaxial Adapter Card If you have a coaxial network adapter card in the controller, you do not need to enter any configuration parameters. You can choose the type of communication you are using, Local Network Adapter, and then Coaxial. This message box appears: Choose OK to close the dialog box.
Page 250 Model 200 Controller User’s Manual Configuring the Twinaxial Adapter Card After you install the Model 200 Controller, you need to turn it on and configure its network adapter cards. Use the worksheets in Appendix E. Before you configure the network adapter card, obtain the controller address and the maximum I-field size from your network administrator.
Page 251 To configure a twinaxial network adapter card 1. From the main menu, choose the type of communication you are using to connect the controller to the host. 2. Choose Local Network Adapter. Five buttons for different network adapter card types appear. 3.
Page 252 Model 200 Controller User’s Manual...
Page 253 Connecting to an SDLC Network...
Page 254 Model 200 Controller User’s Manual...
Page 255 This chapter describes how to install the controller in your SDLC network and configure the network adapter card. Chapter Checklist Done? Task Install the controller. Use the GUI to configure the SDLC card for the SDLC network. If you already understand and have performed these tasks, connect the controller to another host or set up the host environment as described in these chapters: Chapter 5, “Connecting to an Ethernet/Token Ring Network”...
Page 256 Model 200 Controller User’s Manual Installing the Controller Before you can configure the Model 200 Controller, you need to install it in your network. Equipment An SDLC connection where you connect the controller. An SDLC cable to connect the controller to the connection. You can use a 25 conductor IBM custom cable.
Page 257 Configuring the Network Adapter Card After you install the Model 200 Controller, you need to turn it on and configure its network adapter cards. Use the worksheets in Appendix E. Before you configure the network adapter card, obtain the local station address from your network administrator.
Page 258 Model 200 Controller User’s Manual Configuring Advanced SDLC Parameters Field Description Line type The type of telecommunications link that the controller is using. Switched lines are the dialed type. Non-switched lines are the leased type. Line mode The type of cable you are using to connect the controller to your host.
Page 259 Field Description Max I-field size The maximum frame size that is used in this connection mode. Send XID This check box determines if the response controller sends the XID response immediately without waiting for the host to send the XID request. To configure the advanced SDLC parameters 1.
Page 260 Model 200 Controller User’s Manual Saving Your Run-Time Configuration When you finish configuring your network adapter card, you should save your changes. To save your run-time configuration From the main menu sidebar buttons, choose Save Configuration.
Page 261 NuggetFont NuggetFont & Using Terminal Emulation...
Page 262 Model 200 Controller User’s Manual NuggetFont NuggetFont...
Page 263 Now that you have configured the Model 200 Controller to communicate with your LAN and you have configured it to communicate with your Intermec RF network, you are ready to tie the entire data collection network together using an application, such as terminal emulation.
Page 264 Note: If your JANUS 2.4 GHz RF devices are running TCP/IP, you do not need a Model 200 Controller to run VT or ANSI TE, TN5250, or TN3270. If your JANUS 2.4 GHz RF devices are running UDP Plus, you need to use a Model 200 Controller.
Page 265 About Terminal Emulation Terminal emulation (TE) lets data collection devices communicate through the Model 200 Controller as if they were directly connected to the host. The controller sends data to the device in a screen format that emulates the host session.
Page 266 3270 TN5250 TN3270 Using the Model 200 Controller, you can run VT/ANSI TE on JANUS UDP Plus devices and TRAKKER Antares terminals. The UNIX or other TCP/IP host must support Telnet. You can also run TN5250 or TN3270 on TRAKKER Antares terminals. Your IBM host must support Telnet. When you send data from the device, the controller routes it to the Telnet session on the host.
Page 267 Note: If you are replacing a 9185 controller with a Model 200 Controller, you must download the new JANUS TE application to all your JANUS devices. TRAKKER Antares TE Application TRAKKER Antares terminals can run VT, ANSI, 5250, or 3270 TE. Your devices are preloaded with the TRAKKER Antares TE application.
Page 268 Model 200 Controller User’s Manual Field Description Host Name This list box contains the logical names of the TCP/IP hosts that you have defined. Host Name - The terminal names that are linked to a Linked Terminals specific host. Available...
Page 269 To set up Telnet terminal emulation 1. From the main menu, choose Terminal Emulation. 2. Choose Telnet Terminal Emulation. The Telnet Terminal Emulation Configuration dialog box appears. 3. Make sure that you have added all your TCP/IP hosts. The Host Name list box contains all the existing host names.
Page 270 Model 200 Controller User’s Manual Adding a TCP/IP Host To communicate with TCP/IP hosts, the Model 200 Controller must know their IP addresses. You can either use DNS to resolve these IP addresses or you can enter them in manually.
Page 271 To determine the host IP address using DNS 1. From the Telnet Terminal Emulation Configuration dialog box, choose Add. The TCP/IP Host Connection dialog box appears. 2. In the Host name field, enter the abbreviated or long host name. If you enter the abbreviated name, the controller searches the domain names in the DNS Configuration dialog box to determine the long host name.
Page 272 Note: To set up TN5250 terminal emulation, see “Setting Up Telnet Terminal Emulation” earlier in this chapter. Configuring the Host For 5250 TE, your network administrator needs to define the Model 200 Controller on the host unless you have auto-create controller turned on. Configuring the Controller To run 5250 TE between JANUS devices and TRAKKER Antares terminals and the host, you must identify all the IBM SNA hosts.
Page 273 Field Description Host Name - This list box contains the logical names Mode - Security - of the 5250 SNA hosts that you have Name defined, what mode they are using, if security is set, and if they are using device names.
Page 274 Model 200 Controller User’s Manual To set up 5250 terminal emulation 1. From the main menu, choose Terminal Emulation. 2. Choose 5250 SNA Terminal Emulation. The 5250 Terminal Emulation Configuration dialog box appears. 3. Make sure that you have added all your hosts. The Host Name list box contains all the existing host names.
Page 275 10. Choose Close to close the dialog box and return to the main menu. Adding an IBM SNA Host You must identify any hosts you want the Model 200 Controller to communicate with for the terminal sessions. When you add a host, you set up a link to a specific host and this information is available throughout the system.
Page 276 Model 200 Controller User’s Manual Field Description Host name A unique name for the SNA host. Use this internal name to make the host LU name easier to identify. Adapter card The network adapter card you are using to connect to the host.
Page 277 5. In the Host LU field, enter the LU name that identifies the host. 6. (Ethernet or token ring only) In the Local PU field, enter a unique PU (physical unit) name for the host. The default name is the local SNA node name plus a 2-digit suffix.
Page 278 2. In the Network ID field, enter the network name used to create a unique SNA network. 3. In the Node Name field, enter the name of the Model 200 Controller that other nodes will use to address it. 4. In the Node ID field, enter the last eight characters in the XID that establish a host connection.
Page 279 3. In the list box, select the mode that you want to use. 4. Choose Close to close the dialog box and return to the 5250 Terminal Emulation Configuration dialog box. The mode appears next to the host name under the Mode column. Setting and Removing the User ID and Password Your host may implement security at the session level.
Page 280 Model 200 Controller User’s Manual 3. In the Host user ID field, enter a user ID that allows the controller to access the host. 4. In the Password field, enter a password that goes with the user ID. 5. Choose OK to save your changes and return to the 5250 Terminal Emulation Configuration dialog box.
Page 281 Performing a Double Pass-Through on the IBM AS/400 Host Note: To use this feature with 5250 terminal emulation, your AS/400 must be version 2.3 or higher. When using 5250 terminal emulation, you may want to perform a double pass-through to log into a remote IBM AS/400 host. A double pass-through lets you log into one AS/400 and then access another AS/400 through the first one.
Page 282 Configuring the Host For 3270 TE, your network administrator must set up the host to see the Model 200 Controller as an IBM model 3174 terminal controller. Your network administrator also needs to provide all the NAUs (host field: LOCADDR) that are set up on the host for the devices to use.
Page 283 Field Description Host Name This list box contains the logical names of the 3270 SNA hosts. Host Name - The terminals that are linked to a Linked Terminal specific host. - NAU Available The list of all the terminals that are Terminals available to add to the Host Name - Linked Terminal - NAU list box.
Page 284 Model 200 Controller User’s Manual To set up 3270 terminal emulation 1. From the main menu, choose Terminal Emulation. 2. Choose 3270 SNA Terminal Emulation. The 3270 Terminal Emulation Configuration dialog box appears. 3. Make sure that you have added all your hosts. The Host Name list box contains all the existing host names.
Page 285 8. Choose Close to close the dialog box and return to the main menu. Adding an IBM SNA Host You need to identify any hosts you want the Model 200 Controller to communicate with for your terminal sessions. When you add a host, you set up a link to a specific host and this information is available throughout the system.
Page 286 Model 200 Controller User’s Manual Field Description Host name A unique name that identifies this SNA host. You can use this internal name to make the host LU name more meaningful. Adapter card The network adapter card you are using to connect to the host.
Page 287 To add an IBM 3270 SNA host 1. From the 3270 Terminal Emulation Configuration dialog box, choose Add. The Host Connection Configuration dialog box appears. 2. In the Host name field, enter a meaningful and unique name for the host. 3.
Page 288 Model 200 Controller User’s Manual Filling the NAU Pool 1. From the 3270 Terminal Emulation Configuration dialog box, choose NAU Pool. The 3270 NAU Pool dialog box appears. 2. Add all the NAUs to the NAU pool. a. In the New NAU field, type in the NAU.
Page 289 Editing a Link 1. From the 3270 Terminal Emulation Configuration dialog box in the Host Name - Linked Terminal -NAU list box, select the NAU that you want to change. 2. Choose Edit Link. The Edit NAU Address dialog box appears. 3.
Page 290 Model 200 Controller User’s Manual Configuring Your JANUS Devices With the Model 200 Controller and your JANUS 900 MHz RF devices or your JANUS 2.4 GHz RF devices using UDP Plus, you can run: VT or ANSI terminal emulation (TE) to a TCP/IP host.
Page 291 To run 5250 or 3270 TE, you do not need to load any files on your JANUS device. Your JANUS device was shipped from Intermec with the TE files already loaded. However, if you lose these TE files, or change the JANUS TE application, you may want to download the .CFG file, the .MAP file, and...
Page 292 Model 200 Controller User’s Manual On the controller, these files are in the \USERDATA\TERMAPPS\TE\JANUS900 TNVT900.EXE This executable file runs VT/ANSI TE. You can only use this file if your JANUS 900 MHz RF device uses firmware v3.1 or higher. J95250.EXE This executable file runs 5250 TE. You can only use this file if your JANUS 900 MHz RF device uses firmware v3.1 or higher.
Page 293 Using the Download Server to Download the JANUS TE Application 1. If you want to send the TE files to more than one JANUS device, define a group in the download server. For help, see “Adding a Group in the Download Server”...
Page 294 Model 200 Controller User’s Manual 6. In the Initialization Data box, choose File. 7. In the field, type the path and filename of the .CFG file that contains the configuration information that each JANUS device needs to run TE. 8. Check the Binary file check box.
Page 295 4. Type and press 5. Type filename.cfg and press where filename.CFG is the name of the file that contains the configuration information that each JANUS device needs to run TE. 6. Type filename.exe and press where filename.EXE is the name of the executable file of the JANUS TE application.
Page 296 Model 200 Controller User’s Manual Exiting the TE Configuration Menu 1. From the TE Configuration menu, choose Exit Config and press Save New Configuration screen appears. 2. Choose Yes and press Your terminal saves the configuration options to flash memory and the sign-on screen appears.
Page 297 When you start the TE program on the JANUS device, it attempts to establish communications with a host session by sending a request to the Model 200 Controller terminal session manager. If a terminal session is started, then the terminal session becomes active and the JANUS device can communicate with the host.
Page 298 Model 200 Controller User’s Manual If a terminal session is started and then the connection is broken, the TE program on the JANUS device exits and you must restart it. If the request for a terminal session is rejected, a message is sent back to the JANUS device.
Page 299 This feature maps SBCS code pages for various Latin-based languages to SBCS code page 850, a multilingual code page for Latin-based languages. On the Model 200 Controller, you can find the .MAP files in the \USERDATA\TERMAPPS\TE\INTERNAT directory To use international character sets 1.
Page 300 Model 200 Controller User’s Manual Configuring Your TRAKKER Antares Terminals With the Model 200 Controller, you can run VT or ANSI terminal emulation (TE) between your TRAKKER Antares terminals and a TCP/IP host. You can run 5250 or 3270 terminal emulation between your terminals and an IBM SNA host.
Page 301 Downloading the TRAKKER Antares TE Application The TRAKKER Antares TE application was preloaded when you ordered your terminal. However, this application is also loaded on your Model 200 Controller should you lose your TE files or if you want to change your TE application.
Page 302 Model 200 Controller User’s Manual To use the download server feature 1. If you want to send the TE files to more than one TRAKKER Antares terminal, define a group in the download server. For help, see “Adding a Group in the Download Server” in Appendix B.
Page 303 Configuration menu when the TE welcome screen is displayed on the terminal or after a TE session is established. You cannot enter the TE Configuration menu when the terminal is trying to connect to the Model 200 Controller. You can set a password for the TE Configuration menu to prevent unauthorized users from accessing this menu.
Page 304 Model 200 Controller User’s Manual To access the TE Configuration menu Note: The icons that are shown in this procedure represent the keys on a T2425. The keys on the T248X terminal may look slightly different. 1. Press 2. Press Configuration menu appears.
Page 305 TE session or if you need to reboot the terminal, you will need to login again. On the Model 200 Controller, you can find an example auto-login script file in the \USERDATA\TERMAPPS\TE\ADD_FILE For more help on creating the auto-login script file, see the TRAKKER Antares Terminal Emulation User’s Guide.
Page 306 Model 200 Controller User’s Manual On the Model 200 Controller, you can find the .MAP files in the \USERDATA\TERMAPPS\TE\INTERNAT To use international character sets 1. On the Model 200 Controller, rename the desired code page table .MAP file to DISPTBLS.MAP. Refer to the table below.
Page 307 You can temporarily change the password on the device. The device stores the new encrypted password in a TE.SEC file. However, each time you start the TE application, the device requests the password that is stored on the controller. Therefore, if you want to permanently change the password, you must change it from the controller.
Page 308 Model 200 Controller User’s Manual 3. To set a password on a terminal, select the terminal from the Available Terminals list box and choose Add. Tip: You can press and hold the Shift key and then select multiple terminals. To set the same password on all the terminals at the same time, choose Add All.
Page 309 2. Choose View Runtime Configuration and then choose Start. The View Runtime Configuration Options dialog box appears. 3. Make sure that the Intermec controllers/Devices check box is checked and choose Run View. The Runtime Configuration dialog box appears. 4. Scroll through the file until you see a list of the devices that are enabled.
Page 310 Model 200 Controller User’s Manual...
Page 311 Using Peer-to-Peer Applications...
Page 312 Model 200 Controller User’s Manual...
Page 313 Now that you have configured the Model 200 Controller to communicate with your LAN and you have configured your controller to communicate with your Intermec network, you are ready to tie the entire data collection network together using an application.
Page 314 Model 200 Controller User’s Manual About Peer-to-Peer Applications The Model 200 Controller runs an applications programming interface (API) that makes communicating with remote applications easier. Applications communicate with the controller through network communications processes called NetComms. NetComms are responsible for safely routing data from remote applications across a network to the controller and back.
Page 315 IP address The IP address is the address that is assigned to the Ethernet card or token ring card in the Model 200 Controller. The IP address has the format xxx.xxx.xxx.xxx where xxx is a number from 0 to 255.
Page 316 Setting Up Peer-to-Peer Links on the Controller To run TCP/IP or APPC applications in your data collection network, you must identify all the application names in the Model 200 Controller. The controller puts these names in a peer-to-peer destination list. Every time an application connects to the controller, it informs the controller of its name.
Page 317 To set up peer-to-peer destination list 1. From the main menu, choose Peer-to-Peer and then choose Host Connection. The Peer-to-Peer Destination List dialog box appears. 2. Add, edit, or delete destinations. For help, see “Adding a Destination” in the next section.
Page 318 Model 200 Controller User’s Manual Adding a Destination...
Page 319 Field Description Destination name The meaningful name that identifies the destination (application). Hot Standby The number of seconds the controller timeout waits for a response from this destination before it places transactions going to this destination in a Hot Standby file. Transactions held The number of transactions the in volatile...
Page 320 Model 200 Controller User’s Manual To define your peer-to-peer link 1. From the Peer-to-Peer Destination List dialog box, choose Add. The Peer-to-Peer Destination Parameters dialog box appears. 2. In the Destination name field, enter the name of the destination (application) that will accept the transactions in the Transaction box.
Page 321 International text pass-through allows data streams representing characters encoded in various encoding schemes to pass without conversion between various hosts and devices through the Model 200 Controller. The data streams appear to the server as arbitrary streams of bytes passed between the hosts and devices.
Page 322 Model 200 Controller User’s Manual Before you use this feature, note the following: The controller attaches a transaction header to messages that it receives from hosts and it attaches a transaction ID to route messages to and from devices. The characters for the transaction header and the transaction ID are limited to what you can enter on the controller.
Page 323 Adding a Transaction You need to define all transaction IDs that you want the Model 200 Controller to route to the destinations. Field Description Transaction ID The unique ID of the transaction. Hot Standby The message that is sent to the source of...
Page 324 Model 200 Controller User’s Manual To add a transaction 1. From the Peer-to-Peer Destination Parameters dialog box, choose Add. The Transaction Parameters dialog box appears. 2. In the Transaction ID field, enter the unique ID for the transaction. 3. (Optional) In the Hot Standby message field, enter the message that the controller sends to the source of the transaction when it places the transaction in a Hot Standby file.
Page 325 To add a transaction field 1. From the Transaction Parameters dialog box, choose Add. The Transaction Field Parameters dialog box appears. 2. In the Field name field, enter a name for the transaction field. 3. In the Number field, enter the order or position (for example, 1, 2, or 3) of the field in the transaction.
Page 326 Model 200 Controller User’s Manual Communicating With TCP/IP Applications The Model 200 Controller communicates with remote applications using TCP/IP sockets. TCP provides a method for creating connection-oriented, error-free, full-duplex, byte-stream communications between two processes. IP provides a method for transmitting blocks of data, called IP datagrams, between hosts.
Page 327 The controller supports only requester (client) connections. The remote application initiates both sockets. For help, see the DCS 300 Technical Reference Manual. Using Peer-to-Peer Applications Host 2 APP 2 Socket TCP Port 4401 Address Family: IP Network Address: 192.5.7.10 200.078 9-17...
Page 328 Model 200 Controller User’s Manual How the Controller Communicates With Applications To use the controller NetComms, you must first configure the controller for TCP/IP communications. For help, see “Configuring the TCP/IP Protocol” in Chapters 5 and 6. Applications acknowledge the controller directly by placing data in an ACK transaction and by using the Inter system transaction to control their interactivity with the controller.
Page 329 Controller NetComms Communicating With Applications Remote machine Local machine Using Peer-to-Peer Applications APP1 Network ACK/NAK tcprecvl tcpsendl APP1 APP2 Model 200 Controller Message Handler APP2 Network Network ACK/NAK Receive 200-040 9-19...
Page 330 Model 200 Controller User’s Manual Understanding Transaction Routing in a TCP/IP Network The applications you create to interact with the Model 200 Controller function as remote applications. When your application receives a message from the controller, your application must perform these steps: 1.
Page 331 Using Peer-to-Peer Applications Programming Interface for Applications to the Controller Message Standby Handler File Receive LAN_APP AUX_Q Recv Send NetComm NetComm Model 200 Controller Local Area Network Network Network Connection Connection 200.056 Remote Application LAN_APP 9-21...
Page 332 Model 200 Controller User’s Manual Your applications will use TCP sockets to communicate with the controller across a TCP/IP network. The controller sets up two channels: Receive channel The low priority Receive channel handles unsolicited transactions from end devices and applications, and handles system transactions from applications.
Page 333 The direct TCP/IP socket interface allows non-TCP/IP capable devices, such as JANUS 900 MHz RF devices and TRAKKER Antares terminals, to establish a TCP/IP socket connection to the host through the Model 200 Controller. For more information on using the direct TCP/IP socket interface, see the DCS 300 Technical Reference Manual.
Page 334 Model 200 Controller User’s Manual Direct TCP/IP Socket Interface 9181 Base Radio Unit TCP/IP Network 9-24 Readers (TCP/IP clients) Model 200 Controller Message Handler/ DevComm Network Connection 200A.001 Remote Application...
Page 335 Using Peer-to-Peer Applications Direct TCP/IP API vs. NetComm API By using the direct TCP/IP API, you no longer need to write applications that communicate with the peer-to-peer interface of the controller. You write your client application to communicate with an existing TCP/IP server application.
Page 336 $IPT is a special transaction ID that contains the protocol that allows JANUS devices and TRAKKER Antares terminals to communicate with the Model 200 Controller using the direct TCP/IP socket interface. Every transaction from a device needs $IPT as the transaction ID, which allows the controller DevComm to route the data to the proper queue.
Page 337 Using International Text Pass-Through International text pass-through allows data streams representing characters encoded in various encoding schemes to pass through the Model 200 Controller without conversion between various hosts and devices. The data streams appear to the server as arbitrary streams of bytes passed between the hosts and devices.
Page 338 The controller does not support sort order, date, item, and currency. Communicating With APPC Applications You can use APPC applications to communicate between the Model 200 Controller and any other device on an SNA network. Before you write APPC applications, you should have some familiarity with APPC/LU 6.2 because APPC applications use APPC/LU 6.2 verbs to communicate with...
Page 339 The controller takes care of communications on its side, but you must make sure you build the APPC verbs into your applications to handle communications on the host side. Intermec recommends that you have some familiarity with the APPC/LU 6.2 protocol.
Page 340 Model 200 Controller User’s Manual MC_SEND_ERROR CONFIRM FLUSH ABEND RECEIVE_ALLOCATE IMS Applications Older IMS applications, before version 4.0, do not support the MC_CONFIRMED or MC_SEND_ERROR verbs. Since IMS applications do not support these verbs, applications must send an acknowledge transaction back to partner programs by setting the acknowledge flag in the controller’s...
Page 341 Using Terminal Sessions...
Page 342 Model 200 Controller User’s Manual...
Page 343 Now that you have configured the Model 200 Controller to communicate with your LAN and you have configured your controller to communicate with your Intermec network, you are ready to tie the entire data collection network together using an application.
Page 344 Model 200 Controller User’s Manual About Terminal Sessions You can establish VT, ANSI, 5250, or 3270 terminal sessions between the controller and your host. Use these sessions on the controller to access your host directly from the controller. By accessing your host, you can verify your host connection and you can start remote applications.
Page 345 Configuring the Host for Terminal Sessions For VT, ANSI, 5250 or 3270 terminal sessions, there are relationships between emulation modes and network adapter cards. This section outlines the network administrator tasks for the special relationships between emulation modes and cards. This table lists the emulation modes and the network adapter cards they support.
Page 346 Creating Terminal Sessions This section explains how to define the communications parameters for the VT, ANSI, 3270, and 5250 terminal sessions between the Model 200 Controller and your host. You can use these sessions to access the host from the controller or you can use them for screen mapping sessions.
Page 347 To create a terminal session 1. From the main menu, choose Terminal Session. 2. Choose Host Connection. The Terminal Session List dialog box appears. 3. The Terminal Session list box lists all the sessions that are already defined. From this dialog box you can add new sessions, or you can edit and delete existing sessions.
Page 348 Model 200 Controller User’s Manual Adding a VT/ANSI Terminal Session Use this dialog box to configure VT/ANSI terminal sessions between your Model 200 Controller and your host. You also need to define terminal sessions that you can use for screen mapping sessions. Field...
Page 349 Field Description Number of The number of terminal sessions that sessions you want to run on the controller. Port number The port number that this session uses to communicate with the telnet daemon on the host. To set up a VT/ANSI terminal session. 1.
Page 350 8. Choose Close to close the Terminal Session List dialog box and to return to the main menu. Adding a TCP/IP Host To communicate with TCP/IP hosts, the Model 200 Controller must know their IP addresses. You can either use DNS to resolve these IP addresses or you can enter them in manually.
Page 351 To determine the host’s IP address using DNS 1. From the Terminal Session Definition dialog box, choose Add. The TCP/IP Host Connection dialog box appears. 2. In the Host name field, enter the abbreviated or long host name. If you enter the abbreviated name, the controller searches the domain names in the DNS Configuration dialog box to determine the long host name.
Page 352 Model 200 Controller User’s Manual Customizing the VT Terminal Setup When you add a new VT or ANSI terminal session and you choose Custom, the VT Setup dialog box automatically appears. If you have already created a terminal session and you want to edit the fields in this dialog box, from the Terminal Session list box, select the terminal session and then choose Edit.
Page 353 Field Description Cursor keys Determines whether the arrow keys on the terminal control cursor movement or they send their application control functions. Keypad Determines whether the number keys on the terminal send their keycap characters or they send their programming functions. Line wrap This check box determines if text enabled...
Page 354 Model 200 Controller User’s Manual 3. Enable or disable the text to automatically wrap to the next line when it reaches the right margin. If line wrap is disabled, when the cursor reaches the right margin, the terminal displays each new character in the last column of the line. Each new character overwrites the previous character.
Page 355 Adding a 5250 Terminal Session Use this dialog box to configure 5250 terminal sessions between your Model 200 Controller and your host. You also need to define terminal sessions that you can use for screen mapping sessions. Note: If you set a password and you choose OK and leave this dialog box, the Show check box does not appear if you edit this session.
Page 356 Model 200 Controller User’s Manual Field Description Name A meaningful long session ID that identifies this terminal session. Short session ID The alpha identifier for this terminal session. Host Name The name of the host to which the terminal session connects.
Page 357 To add a terminal session 1. In the Terminal Session List dialog box, choose 5250. The Terminal Session Definition dialog box appears. 2. In the Session box, enter a unique long session ID for the session. 3. In the Session box, enter the Short session ID. The ID defaults to the next available alpha character.
Page 358 Model 200 Controller User’s Manual Adding an IBM SNA Host You need to identify any hosts you want the Model 200 Controller to communicate with for your terminal sessions. When you add a host, you set up a link to a specific host and this information is available throughout the system.
Page 359 Field Description Network ID Identifies the network ID on which the host resides. This ID must match the network ID configured on the host. Host LU The LU name that identifies the host. This parameter must match the control point (CP) name or node name of the host.
Page 360 Model 200 Controller User’s Manual Configuring the Controller SNA Node These parameters identify the Model 200 Controller to the SNA network. Once configured, these parameters apply system-wide for all SNA connection types and you do not need set them again.
Page 361 5. Choose OK to save your changes and return to the Terminal Session Definition dialog box. Adding a 3270 Terminal Session Use this dialog box to configure terminal sessions between your Model 200 Controller and your host. You also need to define terminal sessions that you can use for screen mapping sessions.
Page 362 Model 200 Controller User’s Manual Field Description Name A meaningful long session ID that identifies this terminal session. Short session ID The alpha identifier for this terminal session. Host Name The name of the host to which the terminal session connects.
Page 363 Adding an IBM SNA Host You need to identify any hosts you want the Model 200 Controller to communicate with for your terminal sessions. When you add a host, you set up a link to a specific host and this information is available throughout the system.
Page 364 Model 200 Controller User’s Manual Field Description Host name A name that identifies this SNA host. (Optional) You use this internal name to make the host LU name more meaningful. Adapter card The network adapter card you are using to connect to the host.
Page 365 To add a host 1. In the Terminal Session Definition dialog box in the Host Name box, choose Add. The Host Connection Configuration dialog box appears. 2. (Optional) In the Host name field, enter a meaningful name for the host. 3.
Page 366 Model 200 Controller User’s Manual Starting a Host Session You can start host sessions between the controller and your host. Use the session on the controller to access your host directly from the controller. By accessing your host, you can verify your host connection and you can start remote applications.
Page 367 Mapping Terminal Keyboards to the Model 200 Controller Keyboard Use these diagrams to help you map terminal emulation keys to the Model 200 Controller keyboard. To use the diagrams 1. Locate the keyboard diagram for your application. 2. On the keyboard diagram, locate the function you want to perform and note its position on the key.
Page 368 Model 200 Controller User’s Manual VT/ANSI Terminal Keyboard F15/Help F16/Do Ctrl-[ Delete Remove Return Key Combination Legend Shift Base 10-28 Ctrl-H Find Prev Scrn Select Next Scrn Enter 200A.004...
Page 369 5250 Terminal Keyboard BckTab RqTab CapsLk CapsLk Rshft ShftLk Rshft LShft LShft Reset Reset Key Combination Legend Shift Ctrl Base AltGr Using Terminal Sessions Clear PrtH Help PrtP Help Clear SysReq ImmRst TstReg BckSpc BckSpc RQBS NumLk NumLk NumLk NewLne Enter Home TOPPAG...
Page 370 Model 200 Controller User’s Manual 3270 Terminal Keyboard BckTab NxtWin NxtWin CapsLk CapsLk Rshft CapsLk Rshft LShft LShft Reset Reset PrCncl Key Combination Legend Shift Ctrl Base AltGr Alt+Shift 10-30 Print ScrLk Restrt ScrLk Clear SysReq PrCtrl BckSpc BckSpc Undo...
Page 371 Using Screen Mapping...
Page 372 Model 200 Controller User’s Manual...
Page 373 Now that you have configured the Model 200 Controller to communicate with your LAN and you have configured your controller to communicate with your Intermec network, you are ready to tie the entire data collection network together using an application, such as screen mapping. Before you can run screen mapping, you need to have defined your terminal sessions in Chapter 10, “Using Terminal...
Page 374 Model 200 Controller User’s Manual Chapter Checklist (continued) Done? Task Repeat the preceding two steps until you have defined all host screen fields, regions, and messages for all host screens that receive the data from the current transaction. Repeat the preceding six steps until you have defined all transactions.
Page 375 Screen mapping lets you map transaction fields from a JANUS device or a TRAKKER Antares terminal to different host screen fields in a host application. On the Model 200 Controller, you use the Script Builder Tool to create a script file that the controller uses to map transaction fields from the data collection devices to host screen fields.
Page 376 Model 200 Controller User’s Manual This figure shows data originating from a JR2020 being sent through a BRU to the controller to a host application running in a terminal emulator. Typical Screen Mapping Application 11-6 Host Screen Add Part Number ...Press enter to save...
Page 377 Using script files, the controller maps transaction fields into host screens. Intermec has designed the Script Builder Tool as a GUI tool that lets you easily create, edit, and check script files. The Script Builder Tool also helps you build your terminal application and generate it before you download it to your data collection devices.
Page 378 Model 200 Controller User’s Manual Single Transaction Script Files vs. Multiple Transaction Script Files You can build a script file that contains only one transaction or you can build a script file that contains many transactions, as long as they all branch from one host screen.
Page 379 Using Screen Mapping Multiple Transaction Script vs. Single Transaction Script Example Main host screen Screen 1 Screen 2 Screen 3 Screen 4 First mapping screen Screen 5 Back to Screen 1 Main host screen/First mapping screen Screen 4 Screen 5 Back to Screen 4 11-9...
Page 380 Model 200 Controller User’s Manual Identifying Key Elements for the Script File Before you create your screen mapping application, you need to be able to identify key elements, such as the main host screen, transactions, and host screen fields, for the script file. You also need to decide if your tasks will use single transaction script files or multiple transaction script files.
Page 381 Using Screen Mapping Screen 3 Screen 4 (Main Host Screen) Screen 5 11-11...
Page 382 Model 200 Controller User’s Manual Example 2 - Multiple Transaction Script File This example adds another transaction to Example 1. Besides the work order add transaction, the script file processes a work order quantity inquiry transaction. The result of the query is sent back to the application that is running on the terminal.
Page 383 Screen 4 (Menu Option 915) Screen 6 (Menu Option 910) Using Screen Mapping Screen 5 Screen 7 11-13...
Page 384 Model 200 Controller User’s Manual Understanding How the Script Builder Tool Flows Use this table and the flow chart on the next page to help you understand how to use the Script Builder Tool. Step Button Name New/Open Logon Transaction...
Page 385 Using Screen Mapping Script Builder Tool Flow Chart New Script Logon Sequence Define Main Host Screen Select Transaction Define Fields Define Regions Define Next Screen Normal Logoff Sequence Abnormal Logoff Sequence Save Script 11-15...
Page 386 Model 200 Controller User’s Manual Using the Script Builder Tool To use screen mapping, you need to create a script file. If you want to capture keystrokes on the host screen for a logon, a normal logoff, and an abnormal logoff, you need to start a temporary host session. You also need to start a host session if you want to get host attributes from the host screen.
Page 387 Creating a New Script File Field Description Script name The unique name of the script you are creating or opening. Description A paragraph of text that describes the (Optional) script. Session ID The session ID that you want to use (Optional) when creating this script.
Page 388 Model 200 Controller User’s Manual 5. (Optional) In the Session ID field, click the down arrow on the right side of the field. A list of session IDs appears. Choose a session ID. Note: This temporary host session does not have to be the same host session as the run-time screen mapping session you associate with the script.
Page 389 To save a script 1. From the Script Builder Tools window, choose Script. 2. Choose Save. The script is saved to disk. Copying a Script File 1. Open the script file that you want to copy. For help, see “Opening an Existing Script File”...
Page 390 Model 200 Controller User’s Manual 8. To assign new transactions to the new script, check the Use different transactions check box. The Save As Script With Different Transaction Names dialog box appears. Or, clear this check box if you want to assign new transactions later while you are editing the script.
Page 391 11. Choose OK to save the script to disk and to return to the Script Builder Tools window. Note: If you choose a script name from the Script name drop-down list box in Step 3, a dialog box appears. This dialog box confirms that you want to write over the existing script.
Page 392 Model 200 Controller User’s Manual Setting Options for the Script File Within the Script Builder Tools window, you can set certain script variables for the current script. Field Description Response timeout Sets the number of minutes that the controller waits for a “host busy”...
Page 393 Field Description Error retries These option buttons determine if the controller retries the connection and how many times it retries the connection to the host application when an error occurs. Data response The number of milliseconds of timeout inactivity you want the controller to (VT/ANSI only) wait before it assumes that the host is ready for more data.
Page 394 Model 200 Controller User’s Manual To set options for the entire script 1. From the Script Builder Tools window, choose Script. 2. Choose Options. The Runtime Script Options dialog box appears. 3. In the Response timeout field, enter the number of minutes you want the controller to wait for a host busy condition to clear.
Page 395 11. Choose the level of auditing you want the controller to perform. If you enable auditing, when a non-fatal error occurs, the controller writes the transaction and the explanatory transaction string to the audit file. Choose Off if you do not want the controller to perform any script auditing.
Page 396 Model 200 Controller User’s Manual Creating Host Access Sequences For each script, you need to capture the keystrokes for a logon sequence, a normal logoff sequence and an abnormal logoff sequence. Logon sequences are keystrokes that take the script from the logon screen to the first host screen that receives all transactions for this script, such as the main host screen.
Page 397 Using Screen Mapping Creating a Logon Sequence The logon sequence contains the keystrokes that get you from the login screen to the main host screen. The main host screen is the first host screen where every transaction in the script starts. 11-27...
Page 398 Model 200 Controller User’s Manual To create a logon 1. From the Script Builder Tools window, choose Host Access. 2. Choose Logon. The Logon Sequence dialog box appears. Note: If you do not want to capture the logon keystrokes, you can type them into the Selected Keystrokes field.
Page 399 Using Screen Mapping Creating a Normal Logoff Sequence The normal logoff sequence contains keystrokes that exit you from the host application from the main host screen. 11-29...
Page 400 Model 200 Controller User’s Manual To create a normal logoff 1. From the Script Builder Tools window, choose Host Access. 2. Choose Normal Logoff. The Normal Logoff Sequence dialog box appears. Note: If you do not want to capture the normal logoff keystrokes, you can type them into the Selected Keystrokes field.
Page 401 Using Screen Mapping Creating an Abnormal Logoff Sequence The abnormal logoff sequence contains keystrokes that exit you from the host application from any host screen. Abnormal logoffs usually occur when the controller encounters a critical error. Note: Some host applications may not allow abnormal logoff sequences. 11-31...
Page 402 Model 200 Controller User’s Manual To create an abnormal logoff 1. From the Script Builder Tools window, choose Host Access. 2. Choose Abnormal Logoff. The Abnormal Logoff Sequence dialog box appears. Note: If you do not want to capture the abnormal logoff keystrokes, you can type them into the Selected Keystrokes field.
Page 403 Editing the Captured Keystrokes When you are done entering keystrokes for the host access sequence, choose Stop. The keystrokes that you typed appear in the Captured Keystrokes box. You can edit these keystrokes. Also, if you do not want to capture keystrokes, you can type them into the Selected Keystrokes field and then choose Before or After.
Page 404 Model 200 Controller User’s Manual Selecting Transactions for the Script You need to define all the transactions you want this script to handle. Using the Script Builder, you can map each transaction field to a host screen field. Therefore, you need to choose a current transaction before you can define any host screens, host screen fields, or regions for that transaction.
Page 405 To select the transactions for the script 1. From the Script Builder Tools window, choose Transaction. The Screen Mapping Transaction IDs dialog box appears. 2. Add all transactions that you want to use for this script to the Selected list box. a.
Page 406 Model 200 Controller User’s Manual Selecting Host Screens for the Current Transaction You need to identify the host screens that receive transaction data from the current transaction. The current host screen is the host screen for which you are currently defining fields, regions, messages, and events. When you define the main host screen, it automatically becomes the current host screen.
Page 407 Defining Next Screen Sequences for Host Screens You need to define the sequence of host screens that the current transaction uses for mapping its fields. Choose Yes in the Next Screen? box if your transaction fields map to host screen fields on more than one host screen. After the Script Builder has performed all the screen events for the current host screen, it retrieves the next host screen.
Page 408 Model 200 Controller User’s Manual 7. Check Yes in the Next Screen box if you want to assign the next screen. To select an existing host screen for the next screen, click the down arrow on the right side of the field. A list of host screens appears. Select the host screen that you want to follow the Current screen.
Page 409 Selecting Host Screen Fields for the Current Host Screen You need to identify all the fields on the current host screen that receive transaction data. To select host screen fields 1. From the Script Builder Tools window, choose Screen. 2. Choose Fields. The Host Screen Field List dialog box appears. This list box displays all of the fields that are defined for the current host screen, their location in the host screen, and whether they receive their data from a transaction field or a static string.
Page 410 Model 200 Controller User’s Manual Adding a Host Screen Field Different transactions may contain fields that map to the same host screen field. If you click the down arrow on the right side of the Field label field, you can choose from a list of defined host screen fields. If you choose one of these fields, the Location box is filled with row, column, and length attributes.
Page 411 Field Description Transaction field The number of the transaction field number whose data is mapped to the host screen field. Static string The string that is mapped to the host screen field. Keystroke to exit Determines the keystroke mnemonic field that exits the input field after data is placed in it.
Page 412 Model 200 Controller User’s Manual 5. Determine how the host screen field will receive its data. Choose Transaction field number, if the data for the host screen field is mapped from a transaction field sent by a terminal. Click the down arrow on the right side of the field.
Page 413 To get host screen field attributes from a host screen 1. Start a temporary host session. For help, see “Starting a Host Session” in Chapter 10. 2. In the host window, open the host screen that contains the field that you need to define.
Page 414 Model 200 Controller User’s Manual To select a region 1. From the Script Builder Tools window, choose Screen. 2. Choose Region List. The Host Screen Region List dialog box appears. This list box displays the group the regions are in, the region labels, and their location in the host screen.
Page 415 Determine what event happens when the region is done performing its actions. The default action is to continue processing screen events. You usually use this action when you read data from a host screen field. However, if you are defining a region to catch an error message that appears on the host screen, you should choose to go to a next screen and then select the main host screen.
Page 416 Model 200 Controller User’s Manual Field Description Region label A name for the region that is unique within the current screen. Region group This check box determines if you want (Optional) this region to be part of a group of regions that share the same action in the Actions for Region NOT appearing box.
Page 417 Field Description Continue This option button indicates that the processing screen script file remains on the host screen to events continue processing any other defined screen events. Cancel This option button indicates that the processing screen script file remains on the host screen, events but does not process any other defined screen events.
Page 418 Model 200 Controller User’s Manual 5. If you started a temporary host session for this script, use the Get Region feature to automatically select the location and contents of the region. For help, see “Getting a Region From a Host Screen” later in this chapter.
Page 419 Getting a Region From a Host Screen In 5250 field-formatted host screens, there are two types of fields: protected and unprotected. Protected fields are fields that you cannot write over and are usually text on the host screen. Unprotected fields are usually input fields.
Page 420 Model 200 Controller User’s Manual Capturing Keystrokes Before you can use the capture keystrokes feature, you must start a temporary host session. For help, see “Starting a Host Session” in Chapter To capture keystrokes 1. From the Host Screen Region Definition dialog box, enable the Keystrokes to clear check box.
Page 421 6. If necessary, edit the keystrokes. For help, see “Editing the Captured Keystrokes” earlier in this chapter. 7. Choose OK to return to the Script Builder Tools window. Defining Next Host Screen Sequences for Regions You may want the script file to go to a different host screen when it is finished performing all the actions for the region.
Page 422 Model 200 Controller User’s Manual 7. In the Next Screen box, check the Yes check box and then click the down arrow on the right side of the Name field. A list of host screens appears. Select the host screen that you want to follow the Current screen.
Page 423 Using Screen Mapping Creating Screen and Region Messages There are two types of messages that you can send: screen messages and region messages. Messages are always sent to the source of the transaction. When you choose Screen and then Message List from the Script Builder Tools, the Screen Message List dialog box displays all the messages that are defined for the current host screen.
Page 424 Model 200 Controller User’s Manual 3. Add, edit, or remove messages for the current host screen. For help, see “Adding a Message” later in this chapter. 4. To use a message as a screen message, select the message and check the Send message as current screen event check box.
Page 425 Using Screen Mapping Adding a Message Use messages to carry information from the host application to the application that is running on the terminal. You can only define one message per transaction per script file to be sent back to the terminal. You can define two types of messages: Status message This message appears in the status line of the terminal.
Page 426 Model 200 Controller User’s Manual Field Description Name A unique name for the message. Type The type of message you want to send to the source of the transaction. Text The text of the message. None This option button indicates that nothing from the host screen is included in the message.
Page 427 3. Choose the type of message you are defining. Choose Status message if you are defining a text message in the Text field. This message will appear in the status line at the bottom of the terminal screen that originated the transaction. Choose Transaction if you are defining a transaction in the Text field that will be mapped back to the terminal screen fields that originated the transaction.
Page 428 Model 200 Controller User’s Manual Transaction Message Example You want to know how many parts you have in stock for a part number. Your Part Query terminal screen has two fields: part number (an input field that maps to transaction field number 1) and quantity (an output field that maps to transaction field number 2).
Page 429 Transaction Message Example (continued) Terminal Changing the Order of Screen Events You can change the order of screen events and you can change the order of the regions within a region group. As each host screen appears, certain screen events can occur. These events include mapping terminal (transaction) fields to host screen fields.
Page 430 Model 200 Controller User’s Manual 3. In the Screen Events list box, select the event you want to move. Events occur in order starting from the top. 4. Choose Up or Down to move the event to the appropriate place.
Page 431 Using Screen Mapping Maintaining the Host Screens The Maintain Screen List dialog box lets you add any new host screens that you did not create when you defined the host screen sequences. You can also edit and delete host screens. Note: You cannot delete or remove the main host screen from the Selected Screens list box.
Page 432 Model 200 Controller User’s Manual Field Description Selected Screens This list box contains the host screens that receive transaction data from the current transaction. Available Screens This list box contains all the host screens that are available to use. To maintain the host screens 1.
Page 433 Adding a Host Screen Each host screen definition corresponds to a different host screen. The screen identifier is any string on a host screen that makes the host screen unique. Field Description Screen label A unique name for the screen Description A description for the screen.
Page 434 Model 200 Controller User’s Manual To add a host screen 1. In the Maintain Screen List dialog box, choose Add. The Host Screen Definition dialog box appears. 2. In the Screen label field, enter a unique name for the host screen.
Page 435 (+) sign in the left margin. When you define user blocks, you can insert script comments or commands that the Script Builder cannot generate. For help, see the Model 200 Controller Technical Reference Manual.
Page 436 Model 200 Controller User’s Manual When you open the User Block List dialog box, you may see these symbols to the left of lines in the script: + A plus sign indicates places where you can enter user blocks. < The less than sign precedes existing user blocks.
Page 437 Using Screen Mapping 6. Add, edit, or delete user blocks. For help, see “Adding a User Block” later in this chapter. 7. Choose Close to return to the Script Builder Tools window. 11-67...
Page 438 Model 200 Controller User’s Manual Adding a User Block You can add user blocks after any line in the script that has a plus (+) sign in the left margin. Make sure you use the pound (#) character before any script comment.
Page 439 Viewing the Script This feature provides you with a hierarchical view of the current script. Since the logic flow of the script is driven by transactions, the View Script feature displays the transactions as the top level in the script structure. You can expand the transaction level to see the host screens that receive data from the transaction.
Page 440 4. You may have errors in the user blocks. Edit the user blocks to correct the errors. 5. Repeat Steps 1 through 4 until the Model 200 Controller View Results window lists no more errors. 11-70...
Page 441 Using Screen Mapping The top part of the Model 200 Controller View Results window displays the result of the script checker. You may see some errors and warnings. Your script file should still run with warnings, but you must resolve all errors.
Page 442 Model 200 Controller User’s Manual (Part 1) To verify the logic of a script file 1. Set up your test environment. a. Add a screen mapping session for the script file. Select all the transactions that the script expects. Enable the Visible when data collection started? check box.
Page 443 From the System Diagnostics dialog box, open the Trace Utility and configure a screen mapping trace. d. From the System Reporting dialog box, open the Model 200 Controller Status Monitor window (View Status Monitor command). 2. Test all successful transactions in the script file one at a time.
Page 444 Model 200 Controller User’s Manual Problem The script file is stuck in a host screen and cannot finish processing the transaction data. Nothing happens on the host screen (VT only) (Part 3) To verify the logic of a script file Test all failed transactions in the script file, one at a time.
Page 445 Problem Solution The script file is View the logic that you defined for the region. If you defined stuck in a host a message to send when the region appears, check the Receive screen. Transactions dialog box to see if the message was received. If the message exists, the script has caught the region.
Page 446 Model 200 Controller User’s Manual Setting Up Screen Mapping Sessions When you define a screen mapping session, you define specific transactions to be sent to a specific host terminal session using a specific script file. Screen mapping sessions allow multiple terminal sessions on the controller to simultaneously communicate with multiple terminal emulator sessions running on different hosts.
Page 447 Using Screen Mapping Adding a Screen Mapping Session Visible when data collection started? check box You may want to view the host terminal session when you develop and debug your screen mapping applications. However, you should not use this feature when you actually run your application because it will affect the controller performance.
Page 448 Hot Standby The number of seconds the Model 200 timeout Controller waits for a response from the data collection device before it places the device in Hot Standby mode.
Page 449 A list of script files appears. Choose the script file associated with this screen mapping session. Note: Intermec highly recommends that you use the Script Builder Tool for creating and editing script files. If you choose Create or Edit in this dialog box and then you save your changes, the Script Builder Tool will not recognize the script file.
Page 450 If you use the Script Builder to generate your script files, you usually do not need to map transaction fields. Intermec highly recommends that you use the Script Builder Tool to generate your script files.
Page 451 3. Add, edit, or delete screen mapping fields from the list box. For help, see “Adding a Screen Mapping Field Placement Entry” later in this chapter. 4. Choose Close to close the dialog box and return to the Screen Mapping Session Definition dialog box.
Page 452 Model 200 Controller User’s Manual Adding a Screen Mapping Field Placement Entry 1. From the Screen Mapping Field List dialog box, choose Add. The Screen Mapping Field Placement dialog box appears. 2. In the Transaction field box Name field, click the down arrow on the right side of the field.
Page 453 JANUS 2020. Note: Transactions sent by TRAKKER Antares terminals and JANUS devices and running in the Intermec 2.4 GHz RF network have a maximum length of 1024 characters, including delimiters. Transactions sent by JANUS devices running in the Intermec 900 MHz RF network have a maximum length of 254 characters, including delimiters.
Page 454 When you build a new terminal screen, you may want to open two other windows on the Model 200 Controller screen. Terminal display like on your terminals. It shows the character positions on a terminal screen, it displays the picture field validation characters for input and output fields, and it displays any fixed fields.
Page 455 Using Screen Mapping This section explains how to build screens and menus and how to generate templates using the terminal template tools in the Script Builder Tools window. From the main menu choose Screen Mapping, and then choose Script Builder. 11-85...
Page 456 Model 200 Controller User’s Manual To build a new terminal screen 1. From the Script Builder Tools window, choose Terminal Template. 2. Choose Build Screen. The Build Screen List dialog box appears. 3. Add, edit, or delete terminal screens. For help, see “Adding a Terminal Screen”...
Page 457 Adding a Terminal Screen Field Description Name The unique name for the terminal screen. Size The screen size of the terminal that the screen will be displayed on. Menu title The name you want to appear for the (Optional) screen in the menu on the terminal. Using Screen Mapping Value Default...
Page 458 Description Transaction The transaction ID of the transaction that is created by this screen and that is sent to the Model 200 Controller. Auto send This check box determines if the screen automatically sends the transaction when all of its fields are populated.
Page 459 7. Enable or disable the Auto send and Wait for response check boxes. If you enable the Wait for response check box, the controller waits for 20 seconds before it places the application in Hot Standby mode. The device waits for 60 seconds before it times out and attempts to resend the transaction.
Page 460 Model 200 Controller User’s Manual Field type - fixed field. Fixed fields contain static text and they do not change as the data entered in the input or output field changes. Use these fields as terminal prompts for input or use them as descriptions for output fields.
Page 461 Field Description Field name A unique identifier for the terminal field. The row position that indicates where the field starts on the terminal screen. Column The column position that indicates where the field starts on the terminal screen. Type The type of field. Fixed fields are always the same value.
Page 462 Model 200 Controller User’s Manual Field Description Data type The type of data that you can enter into this field. Attribute The physical attributes of the data type field. Length The maximum length of the field. Trx field number The position of the field in the transaction sent by this screen.
Page 463 6. Enable or disable the Required check box that determines if this field is required. A check in the check box means that this field is required. 7. In the Trx field number field, enter the order or position (for example, 1, 2, or 3) of this field in the transaction that the screen sends.
Page 464 Model 200 Controller User’s Manual Field Description Range Enable or disable checking the field against a numeric range. From The beginning numeric value in the range. The ending numeric value in the range. File The name of the file on the terminal that contains valid values.
Page 465 5. Choose if the data in the input field is included or excluded in the range or file. 6. Choose OK to save your changes and return to the Screen Field Parameters dialog box. Getting Terminal Field Attributes From a Host Screen In 5250 field-formatted host screens, there are two types of fields: protected and unprotected.
Page 466 Model 200 Controller User’s Manual 6. Choose OK to save your changes and return to the Screen Definition dialog box. 7. Repeat Steps 3 through 6 until you have added all the fields from the host window to the terminal screen.
Page 467 Defining Next Screen Sequence for Terminal Screens This feature lets you identify a linked screen to appear on the terminal when a condition is met after you send a screen transaction. When you set up a Next screen, the terminal compares data in the selected Screen field to a value in the Value field.
Page 468 Model 200 Controller User’s Manual Field Description Screen field The field from the current screen whose data is compared to the Value field. The results of the comparison determine whether or not the screen in the Next field appears. Operator...
Page 469 Copying a Terminal Screen 1. From the Script Builder Tools window, choose Terminal Template Tools. 2. Choose Build Screen. The Build Screen List dialog box appears. 3. In the Screen list box, select the screen that you want to copy. 4.
Page 470 Model 200 Controller User’s Manual Building Menus From Screens After you finish creating the screens, group them into logical menus that, when generated, turn into templates that are downloaded to the JANUS devices and TRAKKER Antares terminals. Note: Make sure you add all the screens (including any screens configured as Next screens) to the menu list.
Page 471 Adding a Menu To add a menu 1. From the Menu List dialog box, choose Add. The Menu Items dialog box appears. 2. In the Menu name field, enter a name for the group of screens you are selecting that you will generate into a template. 3.
Page 472 Model 200 Controller User’s Manual Generating Menus Into Templates When you have built the menus from the screens, you need to generate them into terminal templates. Each menu generates into one terminal template. You can use the download server feature to download this terminal template to your data collection devices or you can use the reader program on your devices to request it.
Page 473 Saving and Activating Your Run-Time Configuration When you finish configuring screen mapping, you should save your changes. If you are done configuring the controller, activate your run-time configuration. When the activate is complete, a message box appears if you need to reboot the controller. To save and activate your run-time configuration 1.
Page 474 Status messages always starts with “TERM_MESSAGE,” which is automatically generated. The destination is always fixed to SRC, the source of the transaction, which is assumed to be an Intermec terminal. The SRC can only receive the message if the Wait for response check box is checked in the Terminal Screen and Fields dialog box.
Page 475 CURRENT_SCREEN The Script Builder Tool generates this command and places it as the first line of every set of events for each transaction. The screen label for this command is the main screen, since every set of events for each transaction starts from processing the main screen events. You cannot control where this command appears in the script.
Page 476 Model 200 Controller User’s Manual VT Keyboard Mapping and Script Keystroke Names This table shows how VT keyboard keys map to the Model 200 Controller keyboard and to the script keystroke names. For a diagram of how the VT keyboard maps to the controller keyboard, see Chapter 8, “Using Terminal Emulation.”...
Page 477 VT Keyboard Map (continued) VT Keyboard F15/Help F16/Do 0 (keypad 0) 1 (keypad 1) 2 (keypad 2) 3 (keypad 3) 4 (keypad 4) Prev Scrn Next Scrn Select Remove Ctrl-[ 5 (keypad 5) 6 (keypad 6) 7 (keypad 7) Using Screen Mapping Controller Keyboard Script Name Alt-F10...
Page 478 Model 200 Controller User’s Manual VT Keyboard Map (continued) VT Keyboard 8 (keypad 8) 9 (keypad 9) . (keypad decimal point) Keystrokes A keystroke can be a mnemonic or a string. The table below lists the 3270 and 5250 keystroke mnemonics supported by the controller.
Page 479 4. Choose Primary Cfg. 5. In the Device Address field, enter the address of the JANUS device. This address must match an address that is enabled in the Model 200 Controller. 6. Configure the Channel Select and the Network ID.
Page 480 Downloading the Terminal Template Application You need to download the terminal template application (RDRPGM.EXE) from the Model 200 Controller to each JANUS device that will be using screen mapping. This application allows the JANUS device to run the templates for screen mapping. Depending on the type of communications...
Page 481 To use the download server to download the terminal template application 1. If you want to send the terminal template application to more than one JANUS device, define a group in the download server. For help, see “Adding a Group in the Download Server” in Appendix B. 2.
Page 482 Model 200 Controller User’s Manual 7. In the field, type: \userdata\termapps\tta\janus\rdrpgm.exe 8. Enable the Binary file check box. 9. Choose Overwrite if you want to overwrite any existing file with the same name on the JANUS devices. Do not choose Append.
Page 483 JANUS device, type Downloading the Template You need to download the template that was generated on the Model 200 Controller to each JANUS device that will be using screen mapping. The template is an ASCII file. Each JANUS device needs a template to run before you can enter data and send transactions.
Page 484 Model 200 Controller User’s Manual To use the download server to download the template 1. Follow Steps 1 through 6 in the procedure for using the download server to download the terminal template application in “Downloading the Terminal Template Application” earlier in this chapter.
Page 485 To request the template from the controller 1. Make sure that the host is running the application. 2. Make sure that you have started data collection on the Model 200 Controller. 3. Press to resume the JANUS device.
Page 486 Model 200 Controller User’s Manual Hint You can write a batch file on the JANUS device to make it easier for the user to start the template. For example, you may want the user on shift 1 to start the template by typing his shift number at the JR2020 prompt. The batch file, SHIFT1.BAT may look like:...
Page 487 Running the Application Once you have selected a screen, you can send data from the screen, reset the screen without sending data, and exit the screen. While you are entering data into screens, you may notice these events: Data may appear in an output field that was previously empty. A linked screen may appear if data in a field in the current screen meets some predefined value.
Page 488 Model 200 Controller User’s Manual Configuring Your TRAKKER Antares Terminals With the Model 200 Controller, you can run screen mapping between your remote host and your TRAKKER Antares terminals. Configuring the Terminals for the First Time Before the terminal can communicate with the Model 200 Controller, you need to configure each terminal.
Page 489 Downloading the Template You need to download the template that was generated on the Model 200 Controller to each TRAKKER Antares terminal that will be using screen mapping. The template is an ASCII file. Each terminal needs a template to run before you can enter data and send transactions.
Page 490 Model 200 Controller User’s Manual 6. In the Initialization Data box, choose File. 7. In the field, type: \tpl\ template .tpl where template.tpl is the name of the template that you want to download. 8. Clear the Binary file check box.
Page 491 To request the template from the controller for the first time 1. Make sure that the host is running the application. 2. Make sure that you have started data collection on the Model 200 Controller. 3. Press to resume the terminal.
Page 492 Model 200 Controller User’s Manual Loading a Validation File You may need to download a validation file to your terminal. The validation file performs validation on input fields in terminal screens. This file is an ASCII file that has one entry per line. Since the file is read sequentially, you should try to keep the file small.
Page 493 Note: The validation file cannot have the extensions .irl, .exe, .cmd, or .img. 1. Make sure that you transfer the validation file to the controller. For help, see “Restoring Your User Files” in Chapter 2. 2. Make sure that you have started data collection on the Model 200 Controller. 3. Press to resume the terminal.
Page 494 Model 200 Controller User’s Manual 11-124...
Page 495 Troubleshooting...
Page 496 Model 200 Controller User’s Manual...
Page 497 This appendix explains the troubleshooting tools provided with your Model 200 Controller. It also lists problems and solutions for error messages that may appear in message boxes or in the error log. General Troubleshooting These problems are general system problems that may occur while you are using the Model 200 Controller.
Page 498 Contact your local Intermec representative. Make sure that the configuration for the external controller in the Model 200 Controller GUI matches the configuration in the controller. Make sure that you are using the correct cables to connect your external controller to your network.
Page 499 For help, see “Message Box Error Messages” and “Error Log Error Messages” later in this chapter. Viewing the Configuration The Model 200 Controller produces a configuration file that you can view to verify the parameters that you have defined for the active configuration. To view the configuration 1.
Page 500 Model 200 Controller User’s Manual 3. Enable the configuration items that you want to view. A check in a check box will display the item in the Runtime Configuration dialog box. 4. Choose Run View. The Runtime Configuration dialog box appears.
Page 501 8. Choose Close to return to the main menu. Viewing and Clearing the Hot Standby Files You can view the contents of the Hot Standby files that the Model 200 Controller creates when it places an application or device in Hot Standby mode.
Page 502 Model 200 Controller User’s Manual To view a Hot Standby file 1. From the main menu sidebar buttons, choose System Reporting. The System Reporting dialog box appears. 2. In the System Reporting list box, select View Hot Standby Files and then choose Start.
Page 503 3. Contact your network administrator to help you solve the problem. 4. Contact Intermec Technical Support to help you solve the problem. Note: If the % character appears in an error message in the following table, it identifies a word that is a variable depending on the context of the message box.
Page 504 Model 200 Controller User’s Manual Error Message % edit box field requires 8 hexadecimal numbers. % edit box field requires alphanumeric data type, beginning with an alphabet. % edit box field requires hexadecimal data type. % edit box field requires numeric data type.
Page 505 There is a problem with backing up your system or user files. Check your floppy disk and try again. Or, try using another disk. If the problem persists, contact Intermec Technical Support. A-11...
Page 506 Could not open default configuration file. A-12 Solution You have configured an external Intermec controller and you have not chosen OK to save your configuration. Save or discard your changes. You have not selected a valid directory. Use the root directory list box to open directories and find files.
Page 507 Solution From the main menu sidebar buttons, choose Shutdown Controller and reboot the controller. If the problem persists, contact Intermec Technical Support. See previous solution. From the main menu sidebar buttons, choose Shutdown Controller. Enable the save and activate check box, choose Shutdown, and reboot the controller.
Page 508 Intermec Technical Support. The controller cannot find the trace program. From the main menu sidebar buttons, choose Shutdown Controller and reboot the controller. If the problem persists, contact Intermec Technical Support. The controller cannot find the manual editor for the script file.
Page 509 Error Message Field position values (row, column and length) will cause this field to overlap an existing field. Field position values (row, column or length) are too large for a terminal screen. File name must be between 1 and 8 characters in length Frequencies must be unique for each BRU.
Page 510 Model 200 Controller User’s Manual Error Message Invalid address format for % field. Invalid data in initial value field for a numeric field. Invalid IP address. Invalid picture data for a date field. Invalid picture data for a numeric field.
Page 511 You are trying to restore the system files and runtime configuration using a disk that the controller did not generate. Verify you are using the correct disk and contact Intermec Technical Support. When configuring a group, you need to add at least one terminal from the Available Terminals list box to the Selected Terminals list box before you choose OK.
Page 512 The controller uses a few special 3-letter prefixes. Use another unique, meaningful prefix. See previous solution. Verify the address you entered. Contact your network administrator for another address. Intermec does not recommend that you use the system backup disk in a new controller.
Page 513 Error Message The cursor position is in a protected (read-only) area that is not valid for an input field. Do you want to get the field info anyway? The cursor position is in an unprotected (writeable) area that is not recommended for a screen ID.
Page 514 Model 200 Controller User’s Manual Error Message The initial value specified is longer than the defined field length. The Keystrokes box is checked but no keystrokes were configured. The Local and Network ports must be unique. The logical name entered is already in use.
Page 515 Error Message The Picture length is greater than the length specified for a Range. The Picture value specified doesn’t match the value specified for the Range. The Range value specified is longer than the defined field length. The range values are incompatible. Change the 'from' or 'through' value.
Page 516 Model 200 Controller User’s Manual Error Message The selected transaction field % has already been mapped in this host screen. The Send Message box is checked but no message was configured. The starting address must have the same subnet address as a currently configured ethernet card.
Page 517 Error Message The transaction cannot be deleted, screen mappings exists for this screen mapping session. The transaction field entered is already in use. Please re-enter. The transaction field selected cannot be removed while it is referenced in a field mapping. The transaction ID entered is already in use.
Page 518 See previous solution. Choose Shutdown Controller. Enable the Save and activate check box. Choose Shutdown Controller and then Choose Start Data Collection. If the problem persists, contact Intermec Technical Support. View the error log. Locate the error message in “Understanding the Error Messages“ later in this chapter.
Page 519 Error Message You must check one of the Region Appearing or Region Not Appearing boxes. You must configure an ethernet adapter before configuring the UDP Plus Network. You must create field definitions for this transaction before specifying placement information. You MUST select a next screen. Use the New button if you need to create a screen.
Page 520 Model 200 Controller User’s Manual Error Log Error Messages Error messages are generated by the Model 200 Controller. The controller sends these messages to the status monitor and to the error log. Viewing the Error Messages The controller error messages are divided into the following parts: The first line contains the date and time the message was generated and information about the message, including the source that generated it.
Page 521 50 messages. When the number of error messages reaches this number, the oldest message is deleted. Note: Intermec recommends that you do not make this number too large since these error messages are stored in RAM. For help troubleshooting the error messages, see “Understanding the Error Messages”...
Page 522 System Reporting dialog box appears. 2. In the System Reporting list box, select View Error Messages. The Model 200 Controller View Error Log dialog box appears. 3. Use the horizontal and vertical scroll bars to view your error messages. For help troubleshooting the error messages, see “Understanding the Error Messages”...
Page 523 If you cannot find an error message: 1. Write down the entire message that is in the error log. 2. Contact your network administrator to help you solve the problem. 3. Contact Intermec Technical Support to help you solve the problem. Error Number...
Page 524 Action Retransmit the system transaction to the Receive channel with valid data. See the Model 200 Controller Technical Reference Manual for more information about the format of this transaction. Problem This informational message is generated by the message handler informing you that your device license file is missing or corrupt.
Page 525 Action If the number of devices allowed does not correspond to the number shown on your terminal license, contact your local Intermec representative. Pay attention to the current terminal count to ensure you do not exceed the number of terminals for which you are licensed.
Page 526 A transaction that was routed to an application may have an invalid transaction number. Action Verify data sent to the application has valid transaction numbers in the transaction header. Contact Intermec Technical Support. Problem A system error occurred while reading from an application temporary file.
Page 527 Error Number Error Message MsgHandler. Error closing or deleting a destination's temporary file App id was not found - no response sent to device Error writing transaction to an application temporary file Error writing transaction to an application temporary IPC channel Error getting device handle - logical or physical information...
Page 528 Action Check the specific system error code for more information. If a response transaction is involved, verify whether data was received at the device. Contact Intermec Technical Support. Problem A record was read from an application’s temporary file that had less than 96 bytes or more than 1120 bytes. The transaction was not forwarded to the application, but still exists in the application’s Hot Standby file (.TMP).
Page 529 AUX_Q channel exceeds the user-defined limit, the message handler writes all the transactions into a Hot Standby file. Action Check the specific system error code for more information. This may be an internal problem. Contact Intermec Technical Support. Problem A system error occurred while querying the Receive channel after an acknowledge was received in the ACK channel.
Page 530 Action Check the specific system error code for more information. There may not be enough timer or semaphore handles on your system. If no system error code was given, contact Intermec Technical Support Problem A system error occurred while disabling a timer for an application ACK timeout.
Page 531 Problem The DevComm could not interpret either the physical or logical name given. Action Verify the configuration and the setup of your downline devices. If the problem continues, contact Intermec Technical Support. Problem The DevComm SMA did not understand the transaction it received.
Page 532 Model 200 Controller User’s Manual Error Number Error Message DEV SMA. Transaction received was neither a Request or Response DEV SMA. The device type specified in the transaction is not recognized DEV SMA. Invalid Data for SMA initialization DEV SMA. Device Error DEV SMA.
Page 533 Error Number Error Message DEV SMA. Invalid/Missing data during execution of Request/Response function DEV SMA. "Soft" Protocol response received DEV SMA. "Hard" Protocol response received APPC Error. Allocate Partner Transaction Program Failed APPC Error. Send Data to Partner Transaction Program Failed APPC Error.
Page 534 Action Examine return code and then shut down and reboot the controller. Start data collection. Problem Failed to allocate enough memory for proper program operation. Action Shut down and reboot the controller. Contact Intermec Technical Support. Problem Could not send error indicator to partner transaction program.
Page 535 Error Number Error Message Error building netcom argument list - configuration argument missing/invalid Error spawning receive netcom Error opening DCMSTOPFILE during Initialization Error creating DCMSTOPFILE during DC stop Error writing to DCMSTOPFILE during DC stop Error closing DCMSTOPFILE during DC stop Solution Problem Not all arguments were available for a remote application.
Page 536 Model 200 Controller User’s Manual Error Number Error Message Unable to write to a batch-file-transfer file Unable to close a batch- file-transfer file Error opening batch- file-transfer file Error copying application IPC channel file to batch- file-transfer file LAN. Problem reading ACK from named pipe LAN.
Page 537 Error Number Error Message LAN. Semaphore Open Error LAN. Semaphore Clear Error LAN. Semaphore Set Error LAN. Problem writing ACK to DCM_ACK IPC channel LAN. Could not load LAN application tables. LAN. Could not create semaphore arrays. Solution Problem A LAN NetComm had a problem opening the specified semaphore.
Page 538 Model 200 Controller User’s Manual Error Number Error Message LAN. Could not spawn LAN netcom. An unknown app id was found in a transaction sent to the DCM_Q IPC channel A system error occurred disabling an interrupt timeout Error spawning a thread MH message.
Page 539 Error Number Error Message LAN. Creation of the named pipe failed. LAN. Named pipe failed to connect. LAN. Named pipe write failure LAN. Named pipe read failure LAN. Failed to set the named pipe handle state LAN. Named pipe close failure LAN.
Page 540 Model 200 Controller User’s Manual Error Number Error Message APPC. Invalid transaction size received for batch file transfer EMCOMM ERROR - Screen description could not be found EMCOMM ERROR - Field description could not be found EMCOMM ERROR - Region description...
Page 541 Error Number Error Message EMCOMM WARNING - Data written to the terminal session was truncated EMCOMM ERROR - A bad position was specified - cannot write data EMCOMM ERROR - The terminal session is busy - timed out EMCOMM ERROR - The terminal presentation space is not available...
Page 542 Model 200 Controller User’s Manual Error Number Error Message EMCOMM ERROR - The terminal screen is unformatted EMCOMM WARNING - A string of length 0 was encountered and was not written EMCOMM ERROR - The script has a syntax or logical error...
Page 543 Error Number Error Message EMCOMM ERROR - The screen description is not correct EMCOMM ERROR - The region description is not correct EMCOMM ERROR - The field description is not correct EMCOMM WARNING - The data field from the transaction does not exist EMCOMM ERROR - System error - the...
Page 544 Model 200 Controller User’s Manual Error Number Error Message EMCOMM ERROR - No match found for script key word - syntax error EMCOMM ERROR - Internal processing error EMCOMM ERROR - A IPC channel error occurred EMCOMM WARNING - The transaction sent has been truncated.
Page 545 Problem The given serial port has been closed unexpectedly. Action Shut down and reboot the controller. If the problem persists, contact Intermec Technical Support. Problem The data bits value for the given serial port is invalid. Action Verify the configuration in the GUI.
Page 546 Model 200 Controller User’s Manual Error Number Error Message Serio. OS2, output flush error Serio. Could not write data to serial port 200GUI. No valid configuration file found, start DC terminated 200GUI. Status session could not be started, start DC continued 200GUI.
Page 547 Action Do not manually edit the configuration file; use the GUI. If you are using a file that was created by the GUI, contact Intermec Technical Support. You will be asked to send a copy of your configuration file to Intermec.
Page 548 There may be a problem with the device. Action Determine the source of the problem and correct it. Contact Intermec Technical Support. Tuning parameters may need to be adjusted. Problem More data was received from a device than the DevComm expected.
Page 549 Problem DevComm: The IPC channel being created already exists. There is probably a DevComm running with this name. Action Shut down the controller. If the other DevComm is still running, contact Intermec Technical Support. Troubleshooting A-55...
Page 550 Problem DevComm: Cannot create or open the file specified. The file may be locked. Action Determine the file status: if it is locked, unlock it to correct the problem. If the file is unlocked, contact Intermec Technical Support. Problem DevComm: Access to the specified file has been denied.
Page 551 Error Number Error Message The file does not exist - cannot open Cannot create the file. Cannot flush the file buffer. This feature is not supported for this file Invalid file type Invalid file mode Too many files are open - cannot open another Cannot close file - not open...
Page 552 Model 200 Controller User’s Manual Error Number Error Message UPS hardware battery is low. Controller will shutdown immediately. FileXfer. An error occurred attempting to download a file. FileXfer. Internal error occurred while downloading. FileXfer. Could not initialize the download of a file.
Page 553 Error Number Error Message Internal file transfer error; upload cancelled. FileXfer. Internal file transfer error; download cancelled. Using the System Diagnostics Tools Use these tools and features, which are availabel under the System Diagnostics sidebar button, to help you troubleshoot error conditions: Message Log Formatter (OS2MLOG.DAT) that contains messages that are generated by the controller.
Page 554 Model 200 Controller User’s Manual Using the Message Log Formatter This system diagnostics tool lets you view the OS/2 message log file (OS2MLOG.DAT). Using this tool, you can also change the format of the messages and save the file. Note: If you choose File and then you choose Save As, the Message Log Formatter - Save As dialog box appears.
Page 555 You can change the status of many communication processes and watch the immediate effects of these changes on the Model 200 Controller. To use SNA subsystem management 1. From the main menu sidebar buttons, choose System Diagnostics. The System Diagnostic Tools dialog box appears.
Page 556 Model 200 Controller User’s Manual Using the Trace Utility This system diagnostics tool provides you with ways to configure and run traces on the peer-to-peer network connections, downline device communications, and screen mapping sessions. The Trace Utility combines features from IP trace and SNA trace applications that are provided with the IBM PComm product.
Page 557 5. Add all the trace components to the Configured Traces list box. For help, see “Adding a Network Trace,” “Adding a Screen Mapping Trace,” and “Adding a System Trace” in the next sections. 6. In the Trace Control box, choose Start. A message box appears confirming that you want to start all the traces.
Page 558 Model 200 Controller User’s Manual To save a trace 1. From the Trace Configuration dialog box, choose the File menu command. 2. Choose Backup Trace Files. A message box appears instructing you to insert a blank formatted disk in your disk drive.
Page 559 Adding a Screen Mapping Trace Screen mapping traces are useful when troubleshooting the script files. The screen mapping trace file is called script.SM, where script is the name of the script file that you are tracing. To add a screen mapping trace 1.
Page 560 Model 200 Controller User’s Manual Adding a System Trace System traces are useful in tracing transactions and SNA traffic on the system. While you are running a system trace, you can watch the traces in the Monitor Message Handler Transactions dialog box. For help, see “Understanding the Monitor Message Handler Transactions Dialog Box”...
Page 561 Troubleshooting Understanding the Monitor Message Handler Transactions Dialog Box When you start a system trace or a screen mapping trace, the Monitor Message Handler Transactions dialog box appears. As you send transactions from your devices to the hosts, you can view the traces. MH_IN This box records the information that enters the message handler Receive (input) channel.
Page 562 Model 200 Controller User’s Manual To pause the system trace Choose Pause. To save the system trace Choose Save. The results are stored in the D:\USERDATA\NGTRACE.DAT file. To close the Monitor Message Handler Transactions dialog box 1. Move the Monitor Message Handler Transactions dialog box so that you uncover the Trace Configuration dialog box.
Page 563 Helpful Information...
Page 564 Model 200 Controller User’s Manual...
Page 565 TRAKKER Antares terminals. System Cabling Specifications This table lists the cables you may use to connect your host and your data collection network with your Model 200 Controller. They also list who supplies the cables and any Intermec part numbers. From...
Page 566 Model 200 Controller User’s Manual System Cabling Specifications (continued) From Model 200 External modem Controller Model 200 Controller Model 200 9180 Network Controller Controller Model 200 9154 CrossBar Controller Controller Model 200 9161 Port Controller Concentrator Cable Type Supplied by...
Page 567 Converting Ethernet Addresses to Token Ring MAC Format When configuring the AS/400 host on the Model 200 Controller, the LAN adapter address you specify depends on whether the controller and the host are on the same type of network. If the controller and AS/400 are on different types of networks, you must “byte-flip”...
Page 568 Model 200 Controller User’s Manual As a shortcut, you can use this table to byte-flip addresses. The table shows what each hexadecimal digit, from 0 to F, becomes when you perform Steps 1 to 3 (from the previous figure). Then you must perform Step 4.
Page 569 Using the Controller to Verify Your Network Connections You can use the Model 200 Controller to verify it is correctly connected to the downline devices and to your host. You need to start data collection before you can use the controller to send or receive transactions.
Page 570 Model 200 Controller User’s Manual Field Description Source ID This field can contain the name that you (Optional) want to use as the source of the transaction. Destination ID This field can contain the name of the (Optional) data collection device that you want to use as the destination of the transaction.
Page 571 11. Choose Close to return to the main menu. Receiving Transactions Once you have configured the Model 200 Controller, you may want to test your configuration by sending transactions from a data collection device to an application without starting the application on the host. Or, you may want to send transactions to a data collection device.
Page 572 Model 200 Controller User’s Manual 5. In the Application name field, enter the name of a destination. The destination name (application or device) must be defined in the controller. 6. Choose Add. The Receive Transactions dialog box appears and the controller begins emulating and monitoring incoming transactions for the destination.
Page 573 10. Choose Close to return to the main menu. Using the Controller to Transfer Files You can use the Model 200 Controller to send binary files, such as the reader program, to JANUS devices and TRAKKER Antares terminals. You can also send ASCII files, such as IRL files, templates, and validation files, to one or more devices in any network.
Page 574 Server Commands to Transfer Files” later in this chapter. Limitations when Downloading IRL Programs Problem When you download an IRL program from the Model 200 Controller, it converts the mnemonic representation of ASCII control characters (0-31) into actual characters. Usually, you use these characters to create bar code printer labels or to create data that is based on the IRL program execution.
Page 575 Solution You can avoid this problem by: using PC-IRL to download the IRL program. For help, see the PC-IRL Reference Manual (Intermec Part No. 049212). using the hex number for the control character. The device translates the hex number after it has parsed all the special characters. Use the previous table to translate the control character to its hex number.
Page 576 Model 200 Controller User’s Manual 3. Choose Add Group. The Add/Edit a Terminal Group dialog box appears. 4. In the Group name field, enter a meaningful name for the group of terminals. 5. Add the terminals that you want in this group to the Selected Terminals list box.
Page 577 Copying Information Between Terminals or Groups 1. From the Terminal Download Configuration dialog box, select the terminal or group that you want to configure. 2. Choose Copy. The Terminal/Group Copy dialog box appears. 3. In the Terminal or group field, click the down arrow on the right side of the field.
Page 578 Model 200 Controller User’s Manual Using the Download Server to Transfer Files Note: The 9154 controller does not support binary file transfer. 1. From the Terminal Download Configuration dialog box in the Terminals and Groups list box, select a terminal or group to receive files or data.
Page 579 3. In the Initialization Data box, choose the type of initialization data to download. Binary file To send a binary file to a device, choose File. Enter the path and filename of the file on the controller and choose Binary file. If the file already exists on one of the devices, decide if you want to Append the new file to the existing file, if you want to Overwrite the existing file, or if you want to do nothing but generate an error message.
Page 580 This section explains some special commands that you can run on data collection devices or use with the Send Transaction feature on the Model 200 Controller. Using these download server commands, you can send files to devices or groups that are configured in the download server.
Page 581 You can use one line to send multiple download server commands by stringing the commands together with a comma and no spaces. For example, to send a validation file, WORKORDR.TXT to device addresses pA and pB and run the program, use this command: $NGDNLD,DEV=pA,DEV=pB,F=WORKORDR.TXT,D=// To send the download server command 1.
Page 582 Model 200 Controller User’s Manual Using the Controller to Configure TRAKKER Antares Terminals You can use the Model 200 Controller to configure one or more TRAKKER Antares terminals by sending configuration commands using the download server. Note: You cannot retrieve configuration data from a terminal.
Page 583 To use the download server to configure a terminal 1. From the Terminal Download Configuration dialog box in the Terminals and Groups list box, select a terminal or group to receive files or data. 2. Choose Edit. The Configure Device Initialization Download dialog box appears.
Page 584 Model 200 Controller User’s Manual 5. Repeat Steps 3 and 4 until you have entered all the commands you want to download for this terminal or group. Commands are downloaded in the order they appear in the Files and Data list box. You can then choose Move Up or Move Down to change the order.
Page 585 Using Remote Console...
Page 586 Model 200 Controller User’s Manual...
Page 587 This appendix explains how to use the remote console option on your Model 200 Controller. For help upgrading the controller to remote console, see “Upgrading to Remote Console” in Appendix D. About Remote Console The remote console option lets you access the server remotely using a LAN, a WAN, or a dial-up modem.
Page 588 For help with APPC, see “Configuring for APPC” later in this chapter. Configuring for TCP/IP or Dial-Up SLIP If you are using dial-up SLIP, you must connect a modem to the Model 200 Controller. For help, see “Connecting a Modem” in Chapter 2.
Page 589 Field Description Communication This box lets you specify which Protocol communication protocol you are using for remote connections. TCP/IP The IP address field lets you choose Properties which IP address you are using to accept the connection. If you are using dial-up SLIP, choose 222.222.222.10.
Page 590 Model 200 Controller User’s Manual To configure for SLIP 1. In the TCP/IP Properties box, click the down arrow on the right side of the field. A drop-down list of configured IP addresses appears. Select 222.222.222.10, which is the SLIP server on the controller.
Page 591 Field Description Communication This box lets you specify which Protocol communication protocol you are using for remote connections. APPC Properties The Local node name field specifies the SNA local node name. Start Up Option This check box determines if the controller starts the NetOp host software when it is booted.
Page 592 Model 200 Controller User’s Manual Configuring Security The NetOp host software includes security features to prevent unauthorized access to the Model 200 Controller. You can also use the security options to limit the actions that the remote PC can perform.
Page 593 Field Description Use keyboard This check box determines if the remote and mouse PC user can control the controller keyboard and mouse. If this check box is clear, the remote PC user can only look at the screen on the controller.
Page 594 Model 200 Controller User’s Manual Field Description Remote guest This check box determines if the remote password PC user needs to enter a password after a NetOp connection is made. …password This field contains the password the remote PC user must enter after a NetOp connection is made.
Page 595 6. Enable or disable the Lock controller keyboard and mouse check box. A check in the check box indicates that the keyboard and the mouse of the controller are locked when a connection is made. Intermec recommends that you enable this feature.
Page 596 Model 200 Controller User’s Manual 3. Create a phonebook entry. a. In My Computer folder, double-click the Dial-Up Networking icon. b. In the Dial-up Networking folder, double-click the Make a New Connection icon to create a new Dial-up Networking connection.
Page 597 e. In the SLIP TCP/IP Settings dialog, you must specify “222.222.222.20” as the IP address. Note: You should also uncheck the IP header compression option. 3. Make sure that the modem that is connected to the controller is configured. 4. After the modem connection is made, start the NetOp guest software. 5.
Page 598 Model 200 Controller User’s Manual Tips for using APPC 1. Use Communication Manager Setup to create a configuration file that defines the partner LU, such as the controller, that you want to control. 2. Start Communication Manager before you start the NetOp guest software.
Page 599 Upgrading the Controller and Devices...
Page 600 Model 200 Controller User’s Manual...
Page 601 This appendix provides you with instructions on how to upgrade the Model 200 Controller and how to use the controller to upgrade the TRAKKER Antares terminals. Upgrading Your Licenses When you purchased your Model 200 Controller, you selected a license that let you run a specific number of devices in your network.
Page 602 Upgrading to Screen Mapping You can purchase screen mapping with remote console (Part No. 067190) or without remote console (Part No. 066370). Intermec has designed an automated Script Builder Tool that lets you create custom screens and script files for your JANUS devices or TRAKKER Antares terminals. Remote console lets you manage the controller remotely.
Page 603 Remote control software for Windows™ 95 and NT (Intermec Part No. 590480) Remote control software for OS/2 (Intermec Part No. 590478) Note: This guest software contains special software that works with the Model 200 Controller. You cannot use Danware’s commercially-available software. To install the license 1.
Page 604 Terminals The Firmware Upgrade Utility lets you simultaneously upgrade the firmware on all the TRAKKER Antares terminals that the Model 200 Controller can communicate with. It detects which firmware each terminal is running and performs the correct upgrade procedure for that version.
Page 605 Upgrading the Controller and Devices In the Scheduled Firmware Upgrades box, you can view the state of all the scheduled upgrade events. Column Description The date on which the upgrade event is scheduled to occur. The time at which the upgrade event is scheduled to occur.
Page 606 Model 200 Controller User’s Manual Column Description 3 (cont.) Missed The utility was unable to perform the upgrade. The event may have been scheduled in the past or data collection was not started on the controller at the scheduled time of the upgrade event.
Page 607 Choose one. Or, load the firmware from a disk that was supplied to you by your local Intermec representative or a VAR. For help, see “Loading Firmware and Applications From a Disk” later in this appendix. Or, choose <Don’t Upgrade> if you want to keep the current firmware version on your devices.
Page 608 Model 200 Controller User’s Manual Or, load the application from a disk that was supplied to you by your local Intermec representative or a VAR. For help, see “Loading Firmware and Applications From a Disk” later in this section. Or, choose <Don’t Upgrade> if you want to keep the current application on your devices.
Page 609 8. Remove any groups and devices that you do not want to upgrade. a. In the Selected Groups/Devices list box, select the groups and devices that you do not want to upgrade. b. Choose Remove. 9. In the Device time-out field, enter the number of minutes that the utility waits for the upgrade to complete on each device before it times out.
Page 610 Loading Firmware and Applications From a Disk If you are ready to start scheduling upgrade events and you have received new firmware or an application from Intermec or a VAR, you can load it on your Model 200 Controller. Then you can continue scheduling an upgrade event.
Page 611 Upgrading the Controller and Devices 5. In the Firmware comment field, enter any comments you want to be stored with the firmware or application. These comments appear in the Firmware File Set Details message box. You can enter up to 40 alphanumeric characters, special characters, or spaces.
Page 612 Model 200 Controller User’s Manual Defining a Group You can define groups so that you can more easily manage upgrading your devices. For example, you may want to upgrade the firmware on the dayshift terminals at night and upgrade the nightshift terminals during the day.
Page 613 Upgrading the Controller and Devices 2. Choose Add. The Group Name dialog box appears. 3. In the Group name field, enter a meaningful group name. This name can have up to 16 alphanumeric characters, special characters, or spaces. 4. Choose OK. You return to the Define Groups dialog box. The new group name appears in the Defined Groups list box and in the Groups list box.
Page 614 Model 200 Controller User’s Manual Renaming a Group 1. From the second Add a New Upgrade Event to be Scheduled dialog box, choose Define Groups. The Define Groups dialog box appears. 2. In the Defined Groups list box, select the group that you want to rename.
Page 615 Managing System Firmware and Applications You can view the firmware and applications that are loaded on your Model 200 Controller. From the Firmware Files Set dialog box, you can also: load new firmware or an application from a disk. view details of the firmware or application that is loaded on the controller.
Page 616 Stop Upgrade button If the status of upgrade on a terminal is Upgrading, you can stop the Model 200 Controller thread that is handling/monitoring the upgrade. For example, if your terminal battery is too low, you can stop the upgrade, change the battery, and restart the upgrade of the terminal.
Page 617 Upgrading the Controller and Devices To view details of an upgrade event 1. From the Firmware Upgrade Utility window, select an event to view. 2. Choose Details. The Upgrade Events Details dialog box appears. This dialog box shows the system file (firmware) and application that the event is using, the status of the event, and the scheduled date and time of the event.
Page 618 Model 200 Controller User’s Manual Viewing the Event Log The event log contains the history of all upgrade events. The log is sorted by date and time, with the most recent event listed first. To view the event log 1. From the Firmware Upgrade Utility window, choose View Log. The Upgrade Log dialog box appears.
Page 619 Upgrading the Controller and Devices a. In the File name field, enter a meaningful file name for the event log. b. If you want to save the file to a floppy disk, check the Save to Removable Floppy check box. If you want to save the file to the controller hard drive, clear the Save to Removable Floppy check box.
Page 620 Model 200 Controller User’s Manual...
Page 621 Worksheets...
Page 622 Model 200 Controller User’s Manual...
Page 623 This appendix provides worksheets that you need to complete before using Fast Setup to configure your Model 200 Controller. You may need help from your network administrator to obtain this information. Start Here Question Answer 1. What downline network Ethernet...
Page 624 Model 200 Controller User’s Manual Model 200 Controller to RF Card Worksheet Question How many 9181 BRUs are you going to connect to the Model 200 Controller (1-8)? How many RF controller cards do you need (1-2)? What type of RF controller cards do you need (2-port/4-port)?
Page 625 Worksheets Model 200 Controller to TRAKKER Antares Terminals Worksheet Question Answer How many TRAKKER Antares terminals are going to communicate through the Model 200 Controller (1-128)? Are you going to use a DNS server to track the IP addresses? Yes / No TRAKKER Antares Terminal Logical Name IP Address (xxx.xxx.xxx.xxx)
Page 626 Model 200 Controller User’s Manual Model 200 Controller to JANUS Devices for the 2.4 GHz RF Network Worksheet Question Answer How many JANUS devices for the 2.4 GHz RF network are you going to communicate through the Model 200 Controller (1-128)? The controller treats each JANUS device for the 2.4 GHz RF network as a node.
Page 627 Model 200 Controller to 9180 and CrossBar Worksheet Device Question 9180 Will you be connecting the Model 200 Controller to a 9180 Network Controller? If yes, how many 9180 controllers do you have (1-3)? 9154 Will you be connecting the Model 200 Controller to a 9154...
Page 628 Using the results from the worksheet on page A-7, choose the COM port that you want to connect to each 9180 Network Controller. Note: You obtain COM3 by purchasing an optional serial I/O board (Intermec P/N 589167). 9180 v1.x COM1 COM2 9180 v2.x...
Page 629 Model 200 Controller to CrossBar Worksheet Using the results from the worksheet on page A-7, choose the COM port that you want to connect to each external Intermec controller. Note: You obtain COM3 by purchasing an optional serial I/O board (Intermec P/N 589167). 9154 COM1...
Page 630 Model 200 Controller User’s Manual Network Adapter Cards Worksheet Note: The default setting for the Ethernet card is 10BaseT. Contact your local Intermec representative or VAR if you cannot connect to your Ethernet network because you are using 10Base2 or 10Base5.
Page 631 Telnet Terminal Emulation Worksheet Host Name Use the table below if you are explicitly linking terminals to hosts. Host Name Worksheets Host IP Address (xxx.xxx.xxx.xxx) Terminal Logical Name E-11...
Page 632 Model 200 Controller User’s Manual 5250 Terminal Emulation (Ethernet/Token Ring) Worksheet Host Name Use the table below if you are explicitly linking terminals to hosts. Host Name A user ID and a password may be required for logging into the host...
Page 633 5250 Terminal Emulation (Twinaxial) Worksheet Host Name Use the table below if you are explicitly linking terminals to hosts. Host Name A user ID and a password may be required for logging into the host. User ID Network ID Host LU Terminal Logical Name Password Worksheets...
Page 634 Model 200 Controller User’s Manual 3270 Terminal Emulation (Ethernet/Token Ring) Worksheet Host Name Host Name E-14 Local PU Address NAU Pool (001-254) Node ID...
Page 635 Worksheets 3270 Terminal Emulation (Ethernet/Token Ring) Worksheet (continued) Use the table below if you are explicitly linking terminals to hosts. Host Name Terminal Logical Name E-15...
Page 636 Model 200 Controller User’s Manual 3270 Terminal Emulation (SDLC) Worksheet Host Name Host Name E-16 Network ID Host LU NAU Pool (001-254) Node ID...
Page 637 Worksheets 3270 Terminal Emulation (SDLC) Worksheet (continued) Use the table below if you are explicitly linking terminals to hosts. Host Name Terminal Logical Name E-17...
Page 638 Model 200 Controller User’s Manual Peer-to-Peer Applications Worksheet Question Answer What delimiter character separates your transaction fields? Destination (Application) Name Transaction ID E-18...
Page 639 Worksheets Peer-to-Peer Applications Worksheet (continued) Transaction ID Field Number Field Name E-19...
Page 640 Model 200 Controller User’s Manual VT/ANSI Terminal Sessions Worksheet Host Name Terminal Session Name Mode E-20 Host IP Address (xxx.xxx.xxx.xxx) Number of Sessions Host Name (1-228) (same as above table) Port Number...
Page 641 5250 Terminal Sessions (Ethernet/Token Ring) Worksheet Host Name Number of Sessions Session Name (1-15) *A user ID and a password may be required for logging into the AS/400. User ID Network ID Host LU Host Name (same as above table) AS/400* Password Worksheets...
Page 642 Model 200 Controller User’s Manual 5250 Terminal Sessions (Twinaxial/SDLC) Worksheet Host Name Number of Sessions Session Name (1-15) *A user ID and a password may be required for logging into the AS/400. User ID E-22 Network ID Host LU Host Name...
Page 643 5250 Terminal Sessions (Coaxial) Worksheet Host Name Number of Sessions Session Name (1-15) *A user ID and a password may be required for logging into the AS/400. User ID Host Name (same as above table) AS/400* Password Worksheets S/36 Mode E-23...
Page 644 Model 200 Controller User’s Manual 3270 Terminal Sessions (Ethernet/Token Ring) Worksheet Host Name Number of Session Name Sessions (1-26) E-24 Local PU Address Host Name (same as above table) Node ID NAU Address (1-254)
Page 645 3270 Terminal Sessions (SDLC) Worksheet Host Name Number of Session Name Sessions (1-26) Network ID Host LU Host Name (same as above table) Worksheets Node ID NAU Address (1-254) E-25...
Page 646 Model 200 Controller User’s Manual 3270 Terminal Sessions (Coaxial) Worksheet Number of Session Name Sessions (1-5) E-26 Host Name NAU Address (1-254)
Page 647 Glossary...
Page 648 Model 200 Controller User’s Manual...
Page 649 An application that allows Intermec data collection devices to look like an IBM 3270 or 5250 terminal. access point A bridge that allows RF packets to go from the Intermec RF network to an Ethernet or token ring network. Advanced Setup The GUI that runs on the Model 200 Controller and allows you to configure the controller.
Page 650 BRU (Base Radio Unit) An Intermec 900 MHz RF device that receives messages from the controller and broadcasts them to Intermec 900 MHz RF data collection devices. The BRU also receives messages sent from devices over the radio waves and sends them to the controller.
Page 651 Glossary CrossBar Intermec proprietary data collection network consisting of a 9161 port concentrator or a 9154 controller, data collection devices, printers, and input devices. CSMA/CD (Carrier Sense Multiple Access/Collision Detection) An Ethernet device using CSMA/CD senses whether or not a channel is in use before attempting to transmit information.
Page 652 Model 200 Controller User’s Manual device address A type of address that is used by the host to identify a particular data collection device. This address can also refer to the device’s physical address. direct sequencing A radio frequency spread spectrum technique by which the transmitted signal is spread over a particular frequency range.
Page 653 (aliases) that any device on the network can reach. Hot Standby mode The mode an application is considered to be in by the Model 200 Controller when the controller sends a transaction to an application, and it does not respond within the time set in the Hot Standby timeout.
Page 654 An LU is SNA software that accepts APPC verbs and acts on those verbs. A single LU can provide services for multiple transaction programs. Multiple LUs can be active in a node simultaneously. Intermec uses LU type 6.2 that supports communication between a host application and the...
Page 655 Glossary LRC (Logitudinal Redundancy Check) LRC provides horizontal error checking of data blocks received and transmitted by the controller. LRC performs an exclusive OR of the data bits, excluding the SOM, but including the received or transmitted EOM characters. LSL (Link Support Layer) This layer serves as an intermediary between ODI and the link driver that supplies an interface between the network card and the rest of the operating system.
Page 656 Model 200 Controller User’s Manual network interface card (NIC) An adapter card that is installed in the controller that allows it to connect to a network (for example, Ethernet, Token Ring, Twinaxial). The card contains both the hardware to accommodate the cables and the software to use the network’s protocols.
Page 657 Glossary preferred tree The tree you specify that you first want to connect to in a NetWare 4.X network if you have multiple trees. If this tree has a server with a free connection, the NetWare DOS Requester attaches to it. presentation space The physical space being displayed by the terminal emulator session.
Page 658 Model 200 Controller User’s Manual router A software and hardware connection between two or more subnetworks that permits traffic to be routed from one network to another on the basis of the intended destinations of that traffic. screen event In screen mapping, the operation that is performed on the host screen when data collection starts.
Page 659 Glossary session pooling The controller establishes one 3270 or 5250 terminal session upline to an IBM host. Then, multiple 3270 or 5250 devices downline from the controller can log in to the controller and send data asynchronously to the host. Each device does not need to establish a separate terminal session.
Page 660 A file that contains a menu of screens for data collection devices. The template is downloaded to the devices from the Model 200 Controller or the devices can use the reader program to request the template. terminal emulation (TE) A data collection device that is running terminal emulation looks like the terminal.
Page 661 You can also use UDP when you do not require all the services of TCP. UDP Plus This Intermec-designed protocol is based on UDP. UDP Plus improves the performance of devices in a mobile wireless environment. Intermec uses this protocol to communicate between the controller and TRAKKER Antares terminals.
Page 662 If more than one computer is connected in a line, the upline computers usually handle data processing and the downline computers usually handle data collection and sometimes some data “preprocessing.” VT terminal emulation An application that allows Intermec data collection devices to look like a VT100, VT220, or VT320 terminal. G-16...
Page 663 Model 200 Controller User’s Manual G-18...
Page 664 Index...
Page 665 Model 200 Controller User’s Manual...
Page 666 9154 controller, adding, 4-7 9161 controller adding, 4-10 configuring, 4-18 using internal DIP switches, 4-18 9180 and CrossBar to Model 200 Controller worksheet, E-7 9180 controller, 1-4 adding, 4-13 connecting to, 3-4, 4-3 9180 to Model 200 Controller worksheet, E-8...
Page 667 Model 200 Controller User’s Manual access points (continued) communicating with TRAKKER Antares terminals, 3-19 communicating with UDP Plus terminals, 3-19 definition, G-3 accessing a command prompt, 2-26 accessing the TE Configuration menu, 8-43 on JANUS devices, 8-35 accessories modem, 2-11...
Page 668 adding a user block, 11-68 adding a VT/ANSI terminal session, 10-8 adding an IBM SNA host, 10-18, 10-23 adding an SNA host, 8-15, 8-25 adding upgrade events, D-8 address family, 9-17 Address field, 8-16, 8-26, 10-19, 10-24 Advanced Protocol Configuration dialog box, 5-7, 5-16 Ring speed option buttons, 5-8, 5-17 Advanced SDLC Adapter Protocol...
Page 669 Model 200 Controller User’s Manual Available Files list box, 2-22 Available Groups/Devices list box, D-10 Available list box, 9-9, 11-34, 11-78 Available Ports list box, 2-9, 2-12 Available Screens list box, 11-62 Available Terminals list box, 8-8, 8-13, 8-23, B-14...
Page 670 Captured Keystrokes box, 11-28, 11-30, 11-32, 11-37, 11-51 capturing keystrokes, 11-26, 11-50 Card number field, 3-8 carrier sense multiple access/collision avoidance, See CSMA/CD Change Name button, 11-20 changing the order of screen events, 11-59 changing the security for the TE Configuration menu, 8-48 Channel - Frequency field, 3-9 channel, definition, G-4...
Page 671 11-83 creating a screen message, 11-53 creating an abnormal logoff sequence, 11-31 creating menus, 11-100 creating script files, 11-7 CrossBar and 9180 to Model 200 Controller worksheet, E-7 CrossBar devices configuring, 4-19 editing, 4-21 CrossBar network, 1-4...
Page 672 CrossBar network, 4-4 connecting to UDP Plus network, 3-20 figure, 1-6 Data field, B-8 data integrity, 1-18, 1-25 with controllers, 1-28 data integrity modes, 1-28 Faster mode, 1-28 Safer mode, 1-28 Data or system field, B-8 Data response timeout field, 11-23, 11-25...
Page 673 Model 200 Controller User’s Manual Device List dialog box (continued) Enabled check box, 3-16, 3-32, 4-20 Device Parameters dialog box, 3-17, 3-33, 4-21 Able to receive data check box, 3-17, 3-34, 4-21 Auto-insert from device field, 3-18, 3-34, 4-22 Device type field, 3-17, 3-34, 4-22...
Page 674 TRAKKER Antares terminals, 8-44 explicit links between devices and hosts, 8-7, 8-12, 8-22 editing NAUs, 8-29 Index external Intermec controllers, 1-4, 1-28, 4-4 adding, 4-5 adding a 9154 controller, 4-7 adding a 9161 controller, 4-10 adding a 9180 controller, 4-13...
Page 675 Model 200 Controller User’s Manual Firmware Upgrade Utility (continued) Firmware button, D-6, D-17 loading files from a disk, D-12, D-17 performing the upgrade, D-16 renaming a group, D-16 Scheduled Firmware Upgrades box, D-7 scheduling upgrade events, D-6 Upgrade Now! button, D-16...
Page 676 Host Connection Configuration dialog box, 8-15, 8-26, 10-18, 10-19, 10-24 Adapter card field, 8-16, 8-26, 10-18, 10-24 Address field, 8-16, 8-26, 10-19, 10-24 Host LU field, 8-16, 10-19 Host name field, 8-16, 8-26, 10-18, 10-24 Local PU field, 8-15, 8-16, 8-25, 8-26, 10-19, 10-24 Network ID field, 8-16, 10-19 Node ID field, 8-26, 10-24...
Page 677 Model 200 Controller User’s Manual Hot standby field, 3-18, 3-34, 4-22, 9-9 Hot Standby files, 1-25, 1-26, 1-27, 1-29, 1-33, 9-22 clearing, A-7 using with batch applications, 9-29 viewing, A-7 Hot Standby message, 1-26, 1-32 Hot Standby message field, 9-13...
Page 678 8-38 using the direct TCP/IP socket interface, 9-23 JANUS devices for the 2.4 GHz RF network to Model 200 Controller worksheet, E-6 JANUS TE software, downloading, 8-31, 8-32 Julian date check box, 3-13, 3-30 Julian format, definition, G-8...
Page 679 Model 200 Controller User’s Manual logical unit, See LU logitudinal redundancy check, See LRC Logoff Sequence dialog box Captured Keystrokes box, 11-30 Start button, 11-30 logon sequence, 11-26, 11-27 example, 11-28 Logon Sequence dialog box, 11-28, 11-61 Captured Keystrokes box, 11-28...
Page 680 E-7 Model 200 Controller to 9180 worksheet, E-8 Model 200 Controller to CrossBar worksheet, Model 200 Controller to JANUS Devices for the 2.4 GHz RF Network worksheet, E-6 Model 200 Controller to RF card worksheet, E-4 Model 200 Controller to TRAKKER Antares...
Page 681 Model 200 Controller User’s Manual New/Open Script dialog box, 11-17 Description box, 11-17 Description text box, 11-17 Script name field, 11-17 Session ID field, 11-17, 11-18 Start Session button, 11-18 Next field, 11-98 Next Host Screen dialog box, 11-38, 11-52...
Page 682 port number, 9-17 Port number field, 10-9 port, definition, G-10 Postamble field, 3-13, 4-17 power cord part numbers, 2-4 plugging in, 2-4 using a surge protector, 2-4 using a UPS, 2-4 power indicator, 1-9 power switch, 1-9 Preamble field, 3-13, 4-17 preferred tree, definition, G-11 Prefix option button, 11-94 presentation space, definition, G-11...
Page 683 2-21 Retries field, 3-23 Retry count field, 3-9 Retype to confirm field, C-10 reverse address resolution protocol, See RARP server RF card to Model 200 Controller worksheet, E-4 RF controller cards, 1-4 2-port, 3-4 4-port, 3-4 adding, 3-7 I-20...
Page 684 Runtime Script Options dialog box (continued) Data response timeout field, 11-23 EHLLAPI mnemonic field, 11-23 Error retries option buttons, 11-23 Process batch transactions check box, 11-23 Reset on timeout check box, 11-22 Response timeout field, 11-22 Send to source when batch transaction received check box, 11-23 Safer mode, 1-28 Save and activate changes check box, 2-25...
Page 685 Model 200 Controller User’s Manual Screen Mapping License Upgrade message box, D-4, D-5 Screen Mapping Session Definition dialog box, 11-77 Available list box, 11-78 Host Terminal Session box, 11-78 Hot Standby timeout field, 11-78 Name field, 11-78 Script File box, 11-78...
Page 686 Send XID response immediately check box, 7-7 SEND_MESSAGE command, 11-104 sending a transaction, B-7 sending download server commands, B-19 sequenced packet exchange, See SPX Index serial controllers, See external Intermec controllers Serial port field, 4-7, 4-10, 4-13 serial ports, 1-10 serial, definition, G-12 server, definition, G-12...
Page 687 Model 200 Controller User’s Manual Setup for Controller RF card dialog box (continued) Card number field, 3-8 Channel - Frequency field, 3-9 Hot Standby Timeout box, 3-9 Network ID field, 3-8 Repeat count field, 3-9 Retry count field, 3-9 RFNC address field, 3-8...
Page 688 system files backing up, 2-18 restoring, 2-20 System Maintenance dialog box Backup System Files option, 2-18 Controller Command Prompt option, 2-26 Firmware Upgrade Utility, D-6 Receive Transactions option, B-9 Remote Console Support, C-4 Reset to Factory Defaults option, 2-17 Restore System Files option, 2-20 Send Transaction option, B-7 Start Host Session command, 10-26 System Maintenance sidebar button, 2-9, 2-11...
Page 689 Model 200 Controller User’s Manual Telnet terminal emulation, 1-4 setting up, 8-7 Telnet Terminal Emulation Configuration dialog box, 8-8 Available Terminals list box, 8-8 Host Name - Linked Terminals list box, 8-8 Host Name list box, 8-8 Telnet terminal emulation worksheet, E-11...
Page 690 Terminal Session Definition dialog box (continued) Short session ID field, 10-16, 10-22 Show check box, 10-16 Terminal mode field, 10-8 Terminal Session List dialog box, 10-7 terminal session manager, See TSM terminal sessions adding a host, 10-18, 10-23 configuring communications parameters, 10-6 definition, G-14 setting host parameters, 10-5...
Page 691 Model 200 Controller User’s Manual TRAKKER Antares terminals (continued) using the auto-login feature, 8-45 using the direct TCP/IP socket interface, 9-23 TRAKKER Antares terminals to Model 200 Controller worksheet, E-5 Transaction field, 11-88 Transaction field number option button, 11-41 Transaction Field Parameters dialog box, 9-14...
Page 692 UDP Plus Network Parameters dialog box, 3-22 Hot Standby Timeout box, 3-23 Inactivity timer field, 3-23 Local field, 3-23 Lower limit field, 3-23 Network field, 3-23 Retries field, 3-23 Time Parameters button, 3-28 Transactions held in volatile memory field, 3-23 Upper limit field, 3-23 UDP Plus terminals communicating with access points, 3-19...
Page 693 5250 terminal emulation (twinaxial), E-13 5250 terminal sessions (coaxial), E-23 5250 terminal sessions (Ethernet/token ring), E-21 5250 terminal sessions (twinaxial/SDLC), E-22 Model 200 Controller to 9180, E-8 Model 200 Controller to 9180 and CrossBar, Model 200 Controller to CrossBar, E-9...
Page 694 Model 200 Controller to JANUS devices for the 2.4 GHz RF network, E-6 Model 200 Controller to RF card, E-4 Model 200 Controller to TRAKKER Antares terminals, E-5 network adapter cards, E-10 peer-to-peer applications, E-18 Telnet terminal emulation, E-11 VT/ANSI terminal sessions, E-20...
Page 695 Model 200 Controller User’s Manual I-32...