BASEstartm Classic DAS
for OMNItm Software
Installation and User's Guide
Previous Contents Index

2.3 Post Installation Tasks

This section describes the tasks to perform after installing the DAS for OMNI software, including editing the configuration file, setting the BASEstar Classic support block parameter, and setting up shop floor equipment.

2.3.1 Configuring layered products

See the related OMNI/OSAP and DECnet-Plus documentation for configuring the layered products used by the DAS for OMNI software. See Section 2.3.2.4 for information on configuring OSI transport templates.

2.3.2 Editing the Configuration File

A configuration file is supplied with the DAS for OMNI software. The configuration file contains definitions for types, paths, and devices.

The following sections give examples of the type, path, and device records. See the BASEstar Classic Command Line Interface User's Guide for more information about creating type, path, and device definitions.

2.3.2.1 Editing Type Records

The following example shows the type records created by the configuration file. 


 
create type MMS_IS_TYPE/manufacturer=DEC/model="MMS-IS\MMS-IS device"- 
   /protocol=OMNI - 
   /description="MMS-IS ISO 9506 compliant device"/log 
 
create type MMS_DIS_TYPE/manufacturer=DEC/model="MMS-DIS\MMS-DIS device"- 
   /protocol=OMNI - 
   /description="MMS-DIS ISO 9506 compliant device"/log 
 
create type AP_TYPE/manufacturer="Siemens-AG"/model="AP\Siemens AP device"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-AP device"/log 
 
create type H1_S115U_941_TYP/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_115U-941"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S115U_942_TYP/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_115U-942"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S115U_943_TYP/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_115U-943"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S115U_944_TYP/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_115U-944"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S135U_921_TYP/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_135U-921"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S135U_922_TYP/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_135U-922"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S135U_928_TYP/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_135U-928"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S150U_TYPE/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_150U"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type H1_S155U_TYPE/manufacturer="Siemens-AG"- 
   /model="H1\SIMATIC_155U"- 
   /protocol=OMNI - 
   /description="Siemens SINEC-H1 device"/log 
 
create type S7_TYPE/manufacturer="Siemens-AG"- 
   /model="S7\SIMATIC_S7"- 
   /protocol=OMNI - 
   /description="Siemens S7 device"/log

The model is used to define the protocol profile used by the DAS in defining the device to OMNI. The DAS for OMNI software currently supports MMS-IS, MMS-DIS, S7, AP and H1 protocols.

The text before the \ is not modifiable. The text after the \ is used in defining the model to OMNI software. For SINEC-H1 devices, the model field is not modifiable.

2.3.2.2 Editing Path Records

The following example shows the path records included in the configuration file. The commands are commented out in the configuration file so edit the commands and then remove the comment character before executing the configuration file. 


 
create path MMS_IS_LCL_PATH/vaxport="MMS_IS_LOCAL_PLC"/netname=OMNI- 
/multidrop/io_size=512/log 
 
create path MMS_DIS_LCL_PATH/vaxport="MMS_DIS_LOCAL_PLC"/netname=OMNI- 
/multidrop/io_size=512/log 
 
create path AP_LOCAL_PATH/vaxport="S5_AP_LOCAL_PLC"/netname=OMNI- 
/multidrop/io_size=4096/log 
 
create path H1_LOCAL_PATH/vaxport="S5_H1_LOCAL_PLC"/netname=OMNI- 
/multidrop/io_size=4096/log 
 
create path S7_LOCAL_PATH/vaxport="S7_LOCAL_PLC"/netname=OMNI- 
/multidrop/io_size=4096/log

The VAXPORT field contains the local Application Simple Name. This application simple name must be defined in ODS (OMNI Directory Services) to define the network address information for the local VMD. Only one path is required to be defined for each protocol profile. However, multiple paths may be defined if it is desired to define a unique local VMD for each remote VMD. See the discussion in Section 3.3 for more information on defining multiple local paths.

Table 2-3 lists the path parameters and indicates the value(s) that are allowed for each.

Table 2-3 Path Parameters
Parameter Value(s)
VAXport 1 ASN
Netname OMNI
Multidrop 2 MULTIDROP, POINT_TO_POINT
Timeout 3  
Retries 4  
IO Size 5  

1This parameter must be set to the Application Simple Name defined in ODS for the local VMD.
2This parameter is set to "POINT_TO_POINT" if a unique path is defined for each device.
3The parameter is ignored by this DAS. The timeout for an I/O operation is controlled by the OSI transport template parameters.
4The parameter is ignored by this DAS. The DAS does not do retries.
5The parameter is used to set the maximum segment value when defining the device to OMNI software. See the documentation for your device to set this parameter. If not specified, this parameter defaults to 512.

The line parameters in the path definition are not used by this DAS and are ignored.

Previous Next Contents Index