# BASEstartm Open DAS
for Allen-Bradley Data Highwaytm
on Tru64tm UNIX
Installation and User's Guide

Previous | Contents | Index

# 2.3 Postinstallation Tasks

Before using the DAS for Allen-Bradley Data Highway you must perform the following postinstallation tasks:

- Edit the configuration files
- Configure ports
- Set up plant-floor equipment

## 2.3.1 Editing the Configuration Files

Configuration scripts, /usr/var/opt/douab311/etc/ods_ab_config.template/etc and /usr/var/opt/douab311/etc/bstr_ab_config.template/etc, are supplied with the DAS for Allen-Bradley Data Highway. The ODS configuration file contains OMNI Directory Services (ODS) registration commands for Allen-Bradley specific classes and attributes. The BASEstar Open configuration file contains definitions for sample Allen-Bradley VMDs and protocol profile(s).

Copy the template files and edit them to include site-specific directory, VMD and protocol profile definitions. When you complete your edits, execute the files to create the ODS and BASEstar Open Device Services definitions.

The following sections provide examples of ODS and BASEstar Open definitions from the configuration files, and indicate which attributes can be modified. For more information about creating VMD and protocol profile definitions, refer to the BASEstar Open for Tru64 UNIX Command Language Interface. For more information about registering ODS definitions, refer to the Compaq OMNI for Tru64 UNIX Guide to Using Omni Directory Services.

### 2.3.1.1 Editing ODS Registrations

ODS registrations allow the DAS software to locate a particular PLC on an Allen-Bradley data highway network. Example 2-1 shows the configuration file commands that create the ODS registrations.

Example 2-1 ODS Registration

    REGISTER DIRECTORY NAME "/LINE=DATA_HIGHWAY" ATTRIBUTES "OC=DH_LINE
    /PORT=tty07/ENQ_RETRIES=10/NAK_RETRIES=3/KE_TIMEOUT=128/SPEED=9600
    /PARITY=none/MODEM=0/TRACE=0/KE_STATION=12/TIMEOUT=3"
    REGISTER DIRECTORY NAME "/LINE=DATA_HIGHWAY_PLUS" ATTRIBUTES "OC=DH_LINE
    /PORT=tty08/ENQ_RETRIES=10/NAK_RETRIES=3/KE_TIMEOUT=128/SPEED=9600
    /PARITY=none/MODEM=0/TRACE=0/KE_STATION=13/TIMEOUT=3"
    REGISTER DIRECTORY NAME "/LINE=DH485" ATTRIBUTES "OC=DH_LINE
    /PORT=tty18/ENQ_RETRIES=10/NAK_RETRIES=3/SPEED=9600
    /PARITY=none/MODEM=0/TRACE=0/TIMEOUT=3"

    REGISTER DIRECTORY NAME "/PATH=PLC_2_15_PATH" ATTRIBUTES "OC=DH_PATH
    /LINE_NAME=(/LINE=DATA_HIGHWAY)/STATION=20/TRACE=0"
    REGISTER DIRECTORY NAME "/PATH=PLC_2_30_PATH" ATTRIBUTES "OC=DH_PATH
    /LINE_NAME=(/LINE=DATA_HIGHWAY)/STATION=21/TRACE=0"
    REGISTER DIRECTORY NAME "/PATH=PLC_3_PATH" ATTRIBUTES "OC=DH_PATH
    /LINE_NAME=(/LINE=DATA_HIGHWAY)/STATION=22/TRACE=0"
    REGISTER DIRECTORY NAME "/PATH=PLC_5_40_PATH" ATTRIBUTES "OC=DH_PATH
    /LINE_NAME=(/LINE=DATA_HIGHWAY_PLUS)/STATION=20/TRACE=0"
    REGISTER DIRECTORY NAME "/PATH=PLC_5_250_PATH" ATTRIBUTES "OC=DH_PATH
    /LINE_NAME=(/LINE=DATA_HIGHWAY_PLUS)/STATION=21/TRACE=0"
    REGISTER DIRECTORY NAME "/PATH=SLC_5_04" ATTRIBUTES "OC=DH_PATH
    /LINE_NAME=(/LINE=DH485)/STATION=1"

You can modify the command for your site configuration. Table 2-3 lists ODS attributes, the class they belong to and valid values for the attributes. Attribute values are not checked until a connection is initiated with the VMD.

Table 2-3 REGISTER Attributes
Class | Attribute | Default | Value(s)
--- | --- | --- | ---
DH_LINE | PORT |  | tty06, tty07, etc. 1
| SPEED |  | 110 - 19200
| PARITY |  | NONE, EVEN
| MODEM | NO | TRUE, ON, YES, 1 or FALSE, OFF, NO, 0
| TIMEOUT | 3 | 2-6 2
| KE_STATION 3 | 0 | 0-377 4
| KE_TIMEOUT | 128 | 0-255 6
| ENQ_RETRIES 7 | 10 | 0-20
| NAK_RETRIES 8 | 3 | 0-20
| TRACE 9 | NO | TRUE, ON, YES, 1 or FALSE, OFF, NO, 0
DH_TELNET | IP_ADDRESS |  | xx.xx.xx.xx 11
| PORT_NUMBER 12 |  |
| TIMEOUT | 3 | 2-6 2
| KE_STATION 3 | 0 | 0-377 4
| KE_TIMEOUT | 128 | 0-255 6
| ENQ_RETRIES 7 | 10 | 0-20
| NAK_RETRIES 8 | 3 | 0-20
| TRACE 9 | NO | TRUE, ON, YES, 1 or FALSE, OFF, NO, 0
DH_PATH | LINE_NAME |  | /LINE=xxx 10
| STATION |  | 0-377 4, 1-31 5
| TRACE 9 | NO | TRUE, ON, YES, 1 or FALSE, OFF, NO, 0

1Do not use /dev/tty07. The DAS prefixes the port name with /dev/ when connecting to the PLC.
2Seconds.
3If a KE Station address is specified, then the DAS will configure the KE/KF/KF-2 for the ENQ retries, NAK retries and KE timeout values specified. If a KE Station Address of 0 is specified, then the DAS does not configure the KE/KF/KF-2 and the KE timeout value is ignored. Do NOT configure the KE station address if connecting to a DH-485 network.
4Octal for PLC-2, PLC-3 or PLC-5 controllers.
5Decimal for SLC controllers. If a SLC controller is connected directly to a data highway plus network, the station is still specified in decimal, not octal.
6The KE timeout value is specified in cycles. Consult the KE/KF/KF-2 documentation to determine how long the time is in seconds.
7The ENQ retries is the number of times a request for a response is sent to the PLC before an error is returned to the user.
8The NAK retries is the number of times a retransmission is attempted when a recoverable error is detected in the message received by the PLC.
9Trace is used to allow troubleshooting of the PLC communications. See Section 2.4 for details.
10Specify a name registered earlier with ODS that specifies the line that the PLC with this station address will be using.
11The TCP/IP address must be in xx.xx.xx.xx notation where xx is a number from 0-255.
12Put a valid port number for a socket connection to the TELNET server.

Previous | Next | Contents | Index