Basic Functionality

SAEAUT SNMP OPC Server™ runtime application (Figure bellow) contains SNMP Manager application using SNMP commands GET for reading and SET for writing of variables from / to SNMP agents running on managed devices. When using SET and GET commands the communication is initiated by SNMP manager. SNMP agents on devices can also initiate communication using SNMP command TRAP.

Which variables have to be transferred between SAEAUT SNMP OPC Server™ and devices with running SNMP Agents is defined within address space (namespace) of the SNMP OPC server (address space is configured by configuration application of the SAEAUT SNMP OPC Server™ ) . SNMP OPC server makes these variables available for applications with OPC client interfaces. Address space can be configured as flat or as a tree structure. Tree structure of the address space can match the tree structure of OID for MIB variables. In this case, configuring of big amounts of MIB variables either by their mapping from connected devices or from MIB files can be very fast and easy.

Values transferred to / from devices can be recalculated using JScript engine within SAEAUT SNMP OPC Server™ runtime. (Within SNMP OPC server address space, also variables that have not related mapped variables on managed devices can be defined. Values of these variables can be affected by functionality of JScript itself.)

Variables from address space are available to applications with OPC client first of all through OPC DA interface. Directly within runtime application is implemented also OPC AE server that can generate alarms and events based on values of SNMP variables or variables affected by JScript engine functionality.

Available OPC server interfaces can be enhanced by OPC UA, OPC XML DA and OPC DA automation by wrappers delivered within product SAEAUT SNMP OPC Server™ .

Using SNMP agents running on managed devices, it is possible to transfer a lot of information, but SAEAUT SNMP OPC Server™ can gain leastwise information about availability also from unmanaged devices (without SNMP agent) . It is achieved using ICMP ping protocol. Every unmanaged device communicating with IP protocol can have defined variable within SAEAUT SNMP OPC Server™ address space where information about round trip time can be periodically actualised.

clip0116

Figure: Using of SAEAUT SNMP OPC Server (simple block diagram).