# BASEstartm Classic DAS
for OMNItm Software
Installation and User's Guide

Previous | Contents | Index

# Chapter 3
Using the DAS

This chapter provides information about the supported functions for OMNI devices, and how to access these functions.

# 3.1 Accessing OMNI Functions

The DAS for OMNI software functions are accessed through the BASEstar Classic, using the following interfaces:

- Commands
- Menu system
- Callable services

To use the BASEstar Classic services, enter the following command at the DCL prompt ($):

    $  BSTAR DCM

For information about BASEstar Classic commands, see the BASEstar Classic Command Line Interface User's Guide.

To use the BASEstar Classic menu system, enter the following command:

    $  BSTAR/MENU

For information about the BASEstar Classic menu system, see the BASEstar Classic Command Line Interface User's Guide. For information about the BASEstar Classic callable services, refer to the BASEstar Classic Application Programming Interface Reference Guide.

# 3.2 Supported Functions

This section describes the functions that are supported by the DAS for OMNI software devices.

The DAS for OMNI software supports the following BASEstar Classic functions using MMS compliant devices:

- Read and Write Named and Unnamed Variables
- Receive Unsolicited Variables (Information Reports, Read and Write Indications)
- Receive Unsolicited Status (Status Indication)
- Receive Unsolicited Aborts and Concludes (Abort/Conclude Indication)
- Read Device Status and Identity
- Download and Upload Domains (Programs and Data)
- Start and Stop Programs (Program Invocations)
- Get Device Directory (Get Name List)

The DAS for OMNI software supports the following BASEstar Classic functions using SINEC-AP/H1 compliant devices:

- Read and Write Named and Unnamed Variables
- Receive Unsolicited Variables (Information Reports, Read and Write Indications)
- Receive Unsolicited Status (Status Indication)
- Receive Unsolicited Aborts and Concludes (Abort/Conclude Indication)
- Read Device Status and Identity
- Read, Write and Exchange SINEC-AP and SINEC-H1 Messages

The DAS for OMNI software supports the following BASEstar Classic functions using SINEC-S7 compliant devices:

- Read and Write Unnamed Variables
- Receive Unsolicited Variables (Information Reports, Read and Write Indications)
- Receive Unsolicited Status (Status Indication)
- Receive Unsolicited Aborts (Abort Indication)
- Read Device Status and Identity

## 3.2.1 Connecting To a Device

The MODIFY DEVICE/ENABLE command is used to set a device online. The DAS then attempts to connect to the device. If the connection is successful then the connection will remain active until either the device is disabled or an abort/conclude is generated. Should the initial connection request fail, further connection attempts will be made when the devices is requested to perform a function, ie. read status or if the reconnect interval defined for the device has expired.

NOTE: The DAS will not accept incoming connection requests from the remote VMD.

Example 3-1 shows an example of enabling a device.

The first time a device is enabled all the OMNI software related data structures have to be built up by the DAS, so this could take a few seconds or more if a lot of variables are defined.

Example 3-1 Connecting to an MMS / SINEC-S7 / SINEC-AP / SINEC-H1 Device

    DCM> modify device TEST_PLC /enable
    DCM>

## 3.2.2 Disconnecting a Device

The MODIFY DEVICE/DISABLE command is used to set a device offline, Example 3-2 shows an example of this.

When a device disabled an abort of the connection is sent to the device.

Example 3-2 Disconnecting an MMS / SINEC-S7 / SINEC-AP / SINEC-H1 Device

    DCM> modify device TEST_PLC /disable
    DCM>

Previous | Next | Contents | Index