| Previous | Contents | Index |
The two options for BASEstar Classic DAS for Allen-Bradley INTERCHANGE software have different network interfaces (NI), one to support each option of INTERCHANGE software. The path record associates a device with the correct NI and communication path.
Examples 2-2 and 2-3 show the configuration file commands that create records for Ethernet and PI paths.
| Example 2-2 Path Configuration for EI Network Interface |
|---|
create path DTLNET_PATH/vaxport="05.00.00.04"-
/netname=DTLNET-
/default/io_size=2000/multidrop/log
|
| Example 2-3 Path Configuration for PI MicroVAX |
|---|
create path DTLBPI_PATH/vaxport="NL:"/netname=DTLBPI-
/default/io_size=2000/multidrop/log
|
Since the two options of the DAS for AB INTERCHANGE software are mutually exclusive, the /NETNAME must correspond to the option that has been installed.
For the DAS for AB INTERCHANGE software ethernet option, the /NETNAME parameter must be DTLNET. The VAXPORT parameter of the path definition specifies the network address of the Ethernet interface module connecting the PLC with the TCP/IP network and optionally the DTL server to use when connecting. This address may be either a host name or an IP address specified in dot notation, with the same value that would be passed to the INTERCHANGE software routine DTL_C_CONNECT. Refer to Allen-Bradley documentation for more information.
To specify the DTL server process to use when connecting use the syntax:
/vaxport=xx.xx.xx.xx:yy |
or
/vaxport=host_name:yy |
where yy is the number of the DTL server process (from 1-64) to use when communicating with the Ethernet Interface. A maximum of 40 Ethernet Interfaces can be configured to use the same DTL server process.
For the PI MicroVAX option of the DAS for AB INTERCHANGE software, the /NETNAME parameter must be DTLBPI and the VAXPORT parameter must be NL:. Only one path may be defined when using this option.
Table 2-5 lists the path parameters and indicates the value(s) that are allowed for each.
| Parameter | Value(s) |
|---|---|
| VAXport 1 |
xx.xx.xx.xx, host_name
xx.xx.xx.xx:yy, host_name:yy NL: |
| Netname |
DTLNET
DTLBPI |
| Multidrop | MULTIDROP |
| Timeout 2 | |
| Retries 3 | |
| IO Size 4 |
The line parameters in the path definition are not used by this DAS and are ignored.
Modify the commands for your site configuration, making sure that the
VAX port parameters match your plant-floor configuration. Create
additional paths as needed.
2.3.2.3 Editing Device Records
The device record represents a Allen-Bradley device and references previously defined type and path records. Example 2-4 shows the configuration file commands that create device records.
| Example 2-4 Device Configuration |
|---|
create dev DTL5 /path=DTLNET_PATH/type=DTL_PLC5_TYPE/netaddr="0RM:2,03"-
/timeout=100/vaxport="aa.00.00.bb"-
/write_enable/log
create dev DTL5E /path=DTLNET_PATH/type=DTL_PLC5E_TYPE/netaddr=","-
/timeout=100/vaxport="aa.00.00.bb"/write_enable/log
create dev DTL5250 /path=DTLNET_PATH/type=DTL_PLC5250_TYPE/netaddr=","-
/timeout=100/vaxport="aa.00.00.bb"/write_enable/log
create dev SLC504 /path=DTLNET_PATH/type=DTL_SLC504_TYPE/netaddr="0RM:1,04"-
/timeout=100/vaxport="aa.00.00.bb"/write_enable/log
create dev PI5250 /path=DTLBPI_PATH/type=DTL_PLC5250_TYPE/netaddr=","-
/timeout=100/vaxport="NL:"/write_enable/log
|
The timeout on the device definition controls the time that BASEstar Classic device connection management allows for a device operation to complete. The value for the device timeout should be larger than than the expected time of the longest device operation and also longer than the timeout used by INTERCHANGE software. To control the timeout that INTERCHANGE software uses to timeout requests, use the ILAN$DTL_TIMEOUT parameter. See Section 2.3.5.8 for information on configuring this parameter.
For the DAS for AB INTERCHANGE software, the /NETADDRESS parameter specifies the external communication port and station address of a station outside of the Pyramid integrator chassis respectively. The format of the /NETADDRESS parameter is: port_id,station_id.
Valid port_id values are as follows:
| Port ID | Description |
|---|---|
| 2 or 0RM:2 | Channel 2 of the resource manager in slot 0 |
| 3 or 0RM:3 | Channel 3 of the resource manager in slot 0 |
| nKA:2 | Channel 2 of the KA module with pushwheel n(n=0-4) |
| nKA:3 | Channel 3 of the KA module with pushwheel n(n=0-4) |
| 0RM:2/B:b | Channel 2 of the resource manager through bridge address b (b=1-376(octal)) |
| 0RM:2/B:b/L:l | Channel 2 of the resource manager through bridge address b (b=1-376(octal)) and link l (l=0-65535(decimal)) |
| 0RM:2/L:l/G:g | Channel 2 of the resource manager through link l (l-0-65535(decimal)) and gateway g (g=1-376(octal)) |
| 0RM:2/B:b/L:l/G:g | Channel 2 of the resource manager through bridge address b (b=1-376(octal)) link l (l=0-65535(decimal)) and gateway g (g=1-376(octal)) |
Valid value for the station_id are 1 through 376 (octal) for Data Highway, and 0 through 77 (octal) for Data Highway Plus.
For example, a network address at Data Highway station 7 off of the DH/DH+ port 2 of the resource manager is as follows: /NETADDRESS="0RM:2,07"
For a PLC-5/250 sharing the Pyramid integrator chassis with the Ethernet Interface module, the port_id and station_id are null or empty.
For PLC-5/XXE or SLC-5/05 with a direct connection to the ethernet, the port_id and station_id are also null.
To specify the network address for either of these configurations, use the comma (,) delimiter, as shown: /NETADDRESS=","
Modify the command for your site configuration.
For more information about maintaining type, path, and device definitions, refer to the BASEstar Classic Command Line Interface User's Guide.
| Previous | Next | Contents | Index |