SIMATIC S7

via TCP/IP and MPI

OPC Client (Data Access)

• Compatibility with the specifications DA 1.0 and 2.05a
• Connection to inproc, local or remote server
• Connection with up to 20 servers at the same time
• Monitoring of the connection to the server and automatic reconnection if the connection is interrupted.
• Address browsing if supported by the server.
• Benefits of the CALL-R functionality for CALL-R servers (simplified parameter assignment)

OPC Server (Data Access)

• Corresponds to Data Access 2.05a specification (reading/writing of online values).
• Is to be started as a manager just like other drivers.
• By means of data point groups, the items (DPEs) made available to other clients by the server can be defined.
• DPEs can be declared as readable (read-only access is permitted; Group OPCRead) or as writable items (Group OPCWrite).
• Clients can browse the WinCC OA OPC Server hierarchically.

OPC Alarms & Events

OPC Alarms & Events (abbreviated to OPC A&E) is, in addition to Data Access, a further standard for performing central alarm management on a cross-vendor basis. OPC A&E is used to ensure the link to other control systems and the display of alarms/events in a hierarchical system.

OPC UA (Unified Architecture)

• The OPC UA client supports the OPC UA standards Data Access and Alarms & Conditions.
• The OPC UA Server supports the OPC UA standards Data Access and Alarms & Conditions.

Modbus TCP

Modbus/TCP is based on the serial Modbus protocol, which was adapted for TCP/IP. The Modbus/TCP driver can be used simultaneously for Modbus/TCP or UNICOS.

Serial: RK512/3964R

Is used for interfacing a PLC via the 3964R/RK512 protocol

Cerberus

Cerberus is a fire, intrusion and gas alarm system. The Cerberus driver guarantees communication to and from the central fire alarm systems and building security facilities in the event a fire, gas or intruder alarm.

SSI

Is used for the interfacing of SAT remote control systems. The data is exchanged via the LAN (Ethernet, IEEE 802.3); the frame formats used are the SSI formats defined by SAT. The SK 1703 telecontrol components with a suitable communication card (KE/ET) are supported.

IEC 60870-5-101, -104

IEC drivers are standardized telecontrol drivers that can contain proprietary frames. IEC stands for International Electrotechnical Commission, the international standardization committee for electrical engineering.

• IEC 60870-5-104 for data exchange via TCP/IP
• IEC 60870-5-101 for serial connection

DNP3

The DNP3 (DistributedNetworkProtocol 3) driver is an open, rugged and modern protocol which exhibits characteristics and strengths similar to the IEC driver. The transfer of any number of frames with different data types takes place between the WinCC OA System (Master) and the remote stations (Slave).

SINAUT

SINAUT (SIemensNetworkAUTomation) is a communication protocol for automated monitoring and control of remote process stations on the basis of SIMATIC S7. Communication takes place via TCP/IP.

SNMP Manager & Agent

SNMP (SimpleNetworkManagement Protocol) is a protocol for monitoring network elements (servers, workstations, routers, switches, hubs, etc.) and their functions.

• SNMP Manager supports SNMP V1, V2, and V3
• SNMP Agent supports SNMP V1 and V2

BACnet over IP – driver

BACnet (BuildingAutomation andControlNetworks) is a standardized protocol for building automation and has been set by the ASHRAE (American Society of Heating, Refrigerating and Air-conditioning Engineers) as a guideline to provide a uniform and cross-company standard for data communication within and between building automation systems.

The BACnet Standard 2004 is supported in accordance with the PIC list (see product documentation)

Dynamic Logic – driver

The Dynamic Logic driver communicates with different Dynamic Logic devices via the "FSK outstation protocol".

Applicom General Interface

Applicom is, among other things, a manufacturer of I/O cards and software tools, with a wide range of applications in automation engineering. The Applicom products are compatible with many common fieldbus systems and communications components.

Further drivers on request or via C++ API