| Driver | Function |
|---|---|
Matrix of the supported platforms for the most important WinCC OA drivers / managers. |
|
Driver specific functions |
Description of functionality like Poll groups or Bidirectional peripheral communication. These functions are available with some drivers and can be configured. |
Applicom is among other things a producer of peripheral cards and software tools. Several protocols can be covered by the WinCC OA Applicom driver via the format transformation of the peripheral address between device-specific format and the internal Applicom format. |
|
BACnet provides a consistent and neutral standard for the data communication in and with systems of the building automation section. The purpose of the standardization is the interoperability. The services are transmitted via the client/server principle. WinCC OA is here the client and the BACnet device the server. |
|
Cerberus is a Fire, Intrusion, and Gas system. In a very easy manner, the WinCC OA Cerberus driver ensures the communication from and to central fire alarm systems and building security components in case of fire, gas or intruder alarms. |
|
The DNP3 driver is a telecontrol driver based on TCP/IP or V24. The telegram transmission occurs according to the IEC norms. |
|
The WinCC OA Dynamic Logic driver communicates with various Dynamic Logic devices via the "FSK Outstation Protocol". The protocol provides a number of functions that vary slightly between the supported device models. The driver has a very tight relationship with the WinCC OA Channel Manager. |
|
Driver based on TCP/IP or V24 whose frame transmission conforms to IEC standards. |
|
Modbus/TCP is an adaptation of the serial Modbus protocol for TCP/IP communication. The Modbus/TCP driver can be used for Modbus/TCP or UNICOS at the same time. |
|
Description of important terms and steps for starting a functional OPC Alarms & Events (server and/or client) communication in WinCC OA. |
|
Gives a description of the most important terms and steps for starting a functioning OPC communication. |
|
For the communication with databases, LTA tools, reporting and other control systems via OPC. |
|
OPC Unified Architecture (in short OPC UA) is the most recent OPC specification from the OPC Foundation and differs significantly from its predecessors (DA, A&E, HDA, Commands, Complex Data). OPC UA forms a new standard, which is completely based on a service-oriented architecture. |
|
Description of the WinCC OA driver WCCOArk512, which is used for coupling an PLC via the 3964R/RK512 protocol. The data exchange between driver and PLC (Programmable Logical Control) is over a serial interface. |
|
Native driver for establishing a connection with Siemens S7 PLCs and WinCC OA. |
|
Description of the WinCC OA simulator. It allows the system to be run without being connected to actual present peripherals. |
|
SINAUT (SIemens Network AUTomation) is a communication protocol for automatic monitoring and controlling of remote process stations on basis of SIMATIC S7 developed by Siemens. The main application areas are telemetric and telecontrol in the sectors water/sewage, oil and gas, district heating, mining and traffic engineering. |
|
SNMP is a protocol for monitoring network devices and their functions. SNMP differentiates between agent (provides information) and manager (queries the information). |
|
Description of the WinCC OA driver WCCOAssi, which is used for coupling SAT telecontrol systems. The data exchange between WinCC OA and SAT is via LAN (Ethernet, IEEE 802.3); the telegram formats used are the SAT-defined SSI formats. |