
Quick Start
(Catalog Number 9220-CC)
About this Document
Use this document to install and use the ControlNetnetwork
compliance tool. This tool verifies a product’s compliance to the
ControlNet network protocol.
This tool was designed for engineers and developers familiar with the
ControlNet network and network troubleshooting. To use the tool
efficiently, you should be familiar with ControlNet protocols.
For additional information on these protocols, see the ControlNet
Network Specification.
We use these conventions in this document:
Convention Shows
pt Courier
9
pt Courier bold
9
9
pt Courier italic
Enter
For this information See page
understanding the tool 2
system requirements 4
installing the compliance tool 5
using the compliance tool 7
troubleshooting 14
Screen displays and prompts
Text you type as shown at the DOS prompt
Text you type specific to your setup at the DOS prompt
Keys that you press
Publication
9220-10.3 — September 1997

ControlNet Network Compliance Tool2
Understanding the Tool
Use this tool to:
• examine and analyze a device for ControlNet network protocol
compliance
• assist in the testing and debugging of ControlNet products
Each test has a script file (*.tst) and an executable file (*.exe).
This tool contains these tests:
Test Typical test time Is used to test the
mr_obj.tst
mr_tst.exe
cm_obj.tst
cm_tst.exe
cnet_obj.tst
cnet_tst.exe
dev_obj.tst
dev_tst.exe
cs_obj.tst
cs_tst.exe
ccm_obj.tst
ccm_tst.exe
kpr_stub.tst
ks_tst.exe
alltests.tst 1.3 hours Core objects
15 minutes MR (message router)
30 minutes CM (connection manager)
20 minutes ControlNet object
15 minutes Device/Identity
20 minutes CS (ControlNet scheduling)
20 minutes Keeper object
1 minute Keeper stubs
ccm_cs.tst 40 minutes Keeper and CS object
Use this computer to run the tests
and create log files (.log) of the tests.
personal computer running
compliance tests (9220-CC)
9220-KTCT
Publication
9220-10.3 — September 1997
ControlNet link
device
under
test (DUT)
phase 1.5
ControlNet
device

ControlNet Network Compliance Tool 3
Use this table to become familiar with some of the tool’s terms.
Term Refers to the
TS
DUT Device Under Test
MAC ID ControlNet network address (0–99)
keeper
core
objects
script file ASCII text file (.tst) used by the test sequencer to control the execution of the tests
KTCT 9920-KTCT test card
tests sequencer—a DOS based program used to sequence the execution of a
series of self-contained .exe test programs.
ControlNet Configuration Manager—used to hold the network attributes for all
devices on a link and responsible for distributing those attributes in a timely fashion
Connection Manager, Message router, ControlNet object and Identity object
Publication
9220-10.3 — September 1997

ControlNet Network Compliance Tool4
System Requirements
You need a personal computer with these specifications.
microprocessor
operating system
486 33 MHz PC AT or higher
MS-DOS 3.3 or higher
memory 8 MB or higher
hard disk space
8 MB
À
VGA or high resolution
video adapter
and monitor
recommended: ATI VGAWonder XL card and color, super VGA
display (800 x 600)
minimum: VGA card and a display capable of 640x480 VGA
disk drive one 3.5” high-density drive
ISA/EISA bus
communication interface
pointing device
À
The
amount of hard disk space determines how much data you can store to disk files.
ControlNet ISA/EISA bus interface, updated to the latest release
(disk #2), (9220-KTCT) for interfacing to the ControlNet network
Microsoft mouse or compatible
Publication
9220-10.3 — September 1997

ControlNet Network Compliance Tool 5
Installing the Compliance Tool
1. Insert the 9220-CC disk #1 into your computer’s 3.5” diskette drive.
2. Create a directory on your hard drive for the tool.
mkdir
tool_directory
3. Copy the contents of the tool disk to the directory you created.
copy
A:*.* c:\
tool_directory
4. Execute file 9220cc.exe.
Enter
Enter
9220cc.exe
Enter
5. Execute the self-extracting data file associated with the device being
tested. For example (for PLC
plc5data.exe
Enter
testing):
6. Edit your config.sys file to set up the path for the qtp.dat and ktct.cfg
files.
A. Open your config.sys file.
edit
config.sys
Enter
B. Add these statements to the file.
set
testpath=C:\
tool_directory
Publication
9220-10.3 — September 1997