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

Previous | Contents | Index

### 2.3.1.2 Editing BASEstar Open Protocol Profile Definitions

The BASEstar Open protocol profile is used to associate a device with the correct DAS. Example 2-2 shows the configuration file commands that create protocol profile definitions.

Example 2-2 BASEstar Open Protocol Profile Configuration

    CREATE PROTOCOL_PROFILE ab_plc2 \
          -APPLPROFID 51 \
          -MAXPDUSIZE 1024 \
          -SMA_MODE ENABLED \
          -LOG
    CREATE PROTOCOL_PROFILE ab_plc3 \
          -APPLPROFID 52 \
          -MAXPDUSIZE 1024 \
          -SMA_MODE ENABLED \
          -LOG
    CREATE PROTOCOL_PROFILE ab_plc5 \
          -APPLPROFID 53 \
          -MAXPDUSIZE 1024 \
          -SMA_MODE ENABLED \
          -LOG
    CREATE PROTOCOL_PROFILE ab_slc \
          -APPLPROFID 54 \
          -MAXPDUSIZE 1024 \
          -SMA_MODE ENABLED \
          -LOG

The DAS for Allen-Bradley Data Highway uses a different Application Profile ID for each PLC family that it supports. When defining a VMD, be sure to specify the proper protocol profile for the family of PLC being defined.

The MAXPDUSIZE should be greater than or equal to the largest total packet sent by the PLC. If a packet is segmented into several smaller packets use the total packet size for this number.

SMA_MODE indicates that the DAS supports reading multiple variables with one read command. The DAS does not support writing multiple variables. Variables in a polling set are grouped and read in one function call by BASEstar Open if the SMA_MODE ENABLED flag is set.

### 2.3.1.3 Editing VMD Definitions

The VMD definition represents an Allen-Bradley PLC and references previously defined ODS and protocol profile definitions. Example 2-3 shows the configuration file commands that create VMD definitions.

Example 2-3 VMD Configuration

    CREATE VMD plc_2_15 -MODEL "PLC_2_15" \
                        -VENDOR "AB" \
                        -DVM_ACCESS_POINT "/PATH=PLC_2_15_PATH":ab_plc2 \
                        -DESCRIPTION "PLC 2/15" \
                        -LOG
    CREATE VMD plc_2_30 -MODEL "PLC_2_30" \
                        -VENDOR "AB" \
                        -DVM_ACCESS_POINT "/PATH=PLC_2_30_PATH":ab_plc2 \
                        -DESCRIPTION "PLC 2/30" \
                        -LOG
    CREATE VMD plc_3 -MODEL "PLC_3" \
                        -VENDOR "AB" \
                        -DVM_ACCESS_POINT "/PATH=PLC_3_PATH":ab_plc3 \
                        -DESCRIPTION "PLC 3" \
                        -LOG
    CREATE VMD plc_5_40 -MODEL "PLC_5_40" \
                        -VENDOR "AB" \
                        -DVM_ACCESS_POINT "/PATH=PLC_5_40_PATH":ab_plc5 \
                        -DESCRIPTION "PLC 5/40" \
                        -LOG
    CREATE VMD plc_5_250 -MODEL "PLC_5_250" \
                        -VENDOR "AB" \
                        -DVM_ACCESS_POINT "/PATH=PLC_5_250_PATH":ab_plc5 \
                        -DESCRIPTION "PLC 5/250" \
                        -LOG
    CREATE VMD slc_5_04 -MODEL "SLC_5_04" \
                        -VENDOR "AB" \
                        -DVM_ACCESS_POINT "/PATH=SLC_5_04_PATH":ab_slc \
                        -DESCRIPTION "SLC 5/04" \
                        -LOG

An access point is created using the following syntax: APPLICATION_SIMPLE_NAME:PROTOCOL_PROFILE_NAME . The APPLICATION_SIMPLE_NAME is the definition registered in ODS. The PROTOCOL_PROFILE_NAME is defined using the BASEstar Open CLI as described in Section 2.3.1.2.

An access point tells the BASEstar Open software how to access the VMD. For more information on specifying client and DVM access points, refer to BASEstar Open for OpenVMS Command Language Interface.

Modify the command for your site configuration. Table 2-4 lists the modifiable device attributes.

Table 2-4 VMD CREATE
VMD | Parameter | Value(s)
--- | --- | ---
PLC 2 | MODEL | PLC_2, PLC_2_5, PLC_2_05, PLC_2_15, PLC_2_16, PLC_2_17, PLC_2_20, PLC_2_30
| VENDOR 1 | Allen-Bradley
| REVISION 1 |
| CLIENT_ACCESS_POINT 2 |
| DVM_ACCESS_POINT 2 |
| DESCRIPTION 1 |
PLC 3 | MODEL | PLC_3
| VENDOR 1 | Allen-Bradley
| REVISION 1 |
| CLIENT_ACCESS_POINT 2 |
| DVM_ACCESS_POINT 2 |
| DESCRIPTION 1 | PLC-3
PLC 5 | MODEL | PLC_5_10, PLC_5_11, PLC_5_12, PLC_5_15, PLC_5_16, PLC_5_20, PLC_5_25, PLC_5_26, PLC_5_30, PLC_5_36, PLC_5_40, PLC_5_40L, PLC_5_46, PLC_5_60, PLC_5_60L, PLC_5_66, PLC_5_80, PLC_5_86, PLC_5_250
| VENDOR 1 | Allen-Bradley
| REVISION 1 |
| CLIENT_ACCESS_POINT 2 |
| DVM_ACCESS_POINT 2 |
| DESCRIPTION 1 |
SLC | MODEL | SLC_500, SLC_5_01, SLC_5_02, SLC_5_03, SLC_5_04, SLC_5_05
| VENDOR 1 | Allen-Bradley
| REVISION 1 |
| CLIENT_ACCESS_POINT 2 |
| DVM_ACCESS_POINT 2 |
| DESCRIPTION 1 |

1The value of this field is informational only and is not checked by the DAS.
2See the BASEstar Open for OpenVMS Command Language Interface for information on specifying client and DVM access points.

Previous | Next | Contents | Index