Drivers
- Supported Platforms of the main Drivers
- Driver Characteristics
  The driver characteristics overview tables.
- Driver Specific Functions
- BACnet Driver
  BACnet (Building Automation and Control Networks) is a normed protocol for building automation and was designed by ASHRAE (American Society of Heating, Refrigerating and Air-Conditioning Engineers) in order to provide a consistent and intraoperative standard for data communication in and with systems of building automation.
- DNP3 Driver
  The WinCC OA DNP3(Distributed Network Protocol 3) driver uses an open, robust and modern protocol, which has similar characteristics and strong points like the IEC Driver. The transmission of any number of telegrams with different data types occurs between the WinCC OA system (master) and the outstation (slave).
- Ethernet/IP Driver
  Ethernet/IP is used to communicate with multiple generations and families of Rockwell Automation / Allen Bradley PLCs. It is an application layer protocol, layered on top of standard TCP/IP networking.
- IEC 60870-5 Driver
  IEC drivers are standardized remote control drivers that can contain proprietary telegrams.
- IEC 61850 Driver
  IEC 61850 defines an architecture for meeting the needs of electrical substation automation.
- Modbus/TCP
- MQTT
  MQTT (Message Queuing Telemetry Transport) is a messaging protocol which works on top of the TCP/IP protocol and is meant for communication in networks with limited bandwidth.
- MQTT Publisher
  The MQTT publisher provides a northbound data interface for MQTT clients to data point values within the WinCC OA project.
- NTCIP Gateway
  NTCIP (National Transportation Communications for ITS Protocol) is a family of open standards for the configuration, control and monitoring of traffic control equipment (e.g. traffic lights, dynamic message signs, vehicle counting).
- OPC Alarms & Events
  OPC Alarms & Events (brief OPC A&E) is in addition to the Data Access another standard in order to implement a central alert management manufacturer spanning. OPC A&E is used to guarantee the coupling with other control systems as well as to display alerts and events in a hierarchical system
- OPC HDA
- OPC HDA Server
  The WinCC OA OPC Historical Data Access (HDA) Server is used for the exchanging of archived process data of the WinCC OA project.
- OPC Unified Architecture (OPC UA)
  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). OPC UA forms a new standard, which is completely based on a service-oriented architecture.
- OPC Driver
  OPC (OLE for Process Control) is the utilization of OLE/COM technology for process-control systems. The specifications needed for this are laid down by the OPC Foundation.
- PROFIsafe Driver
  As an application profile of PROFINET, PROFIsafe is responsible for the communication between safety devices (F-Device) and safety controllers (F-Host).
- RK512 Driver
  The WinCC OA driver RK512 is used for interfacing a programmable logic controller using the 3964R/RK512 protocol.
- S7 Driver
  The WinCC OA S7 driver is a native driver for connection to the periphery with Siemens S7 PLCs.
- S7Plus Driver
  The WinCC OA S7Plus driver uses the Siemens communication library IOMS and is meant for the communication with Siemens S7 PLCs.
- S-Bus Driver
  The WinCC OA S-Bus driver is used for the connection from SAIA PCD control devices to WinCC OA projects.
- Simulator Driver
  The WinCC OA simulator assumes the tasks of a driver without being connected to actual peripherals. This means it simulates the periphery and is able to generate values "spontaneously". It does this by passing data to the Event Manager that this manager would receive from system components during normal operation of a system. The control system functions can be tested after configuration.
- SINAUT Driver
  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.
- SNMP
  SNMP (Simple Network Management Protocol) is a protocol for monitoring network devices (servers, workstations, routers, switches and hubs etc.) and their functions. It allows you to administer your network.
- SSI Driver
  The WinCC OA SSI driver is used for interfacing SAT remote systems.
- TLS Gateway
  The WinCC OA TLS gateway (Technical Delivery Terms for Route Stations) is a standard for using and establishing traffic control systems on roads.

Details of IEC 61850 control model

IEC 61850 control model error codes

The following table lists the available control model error codes.


Error code	Description
0	No Error
1	Unknown
2	Timeout Test Not OK
3	Operator Test Not OK

IEC 61850 control model response codes


Response code	Description
50	Object has been selected
51	Operation has been canceled
100	Command successfully issued (writing ctlVal)

AddCause values

The parameter AddCause provides additional information if any enhanced mode is used. The following table lists the available AddCause values.


AddCause values	Description
0	Unknown
1	Not-supported
2	Blocked-by-switching-hierarchy
3	Select-failed
4	Invalid-position
5	Position-reached
6	Parameter-change-in-execution
7	Step-limit
8	Blocked-by-Mode
9	Blocked-by-process
10	Blocked-by-interlocking
11	Blocked-by-synchro check
12	Command-already-in-execution
13	Blocked-by-health
14	1-of-n-control
15	Abortion-by-cancel
16	Time-limit-over
17	Abortion-by-trip
18	Object-not-selected
19	Object-already-selected
20	No-access-authority
21	Ended-with-overshoot
22	Abortion-due-to-deviation
23	Abortion-by-communication-loss
24	Blocked-by-command
25	None
26	Inconsistent-parameters
27	Locked-by-other-clients

Client error codes

These error codes are written in case of an MMS error at client side, e.g. trying to pass an incorrect parameter to the TMW stack.


WinCC OA error code	TMW error code	Description
100	0	Success
101	1	NULL Server
102	2	Not connected
103	3	No connection
104	4	Flow controlled
105	5	Max services exceeded
106	6	No read data
107	7	Memory
108	8	Encoding
109	9	Bad transaction
110	10	No transactions
111	11	Connection closed
112	12	Timed out
113	13	Connection state
114	14	Application error
115	15	Bad parameters
116	16	Confirmed error
117	17	Reject
118	18	No authentication
119	19	Conclude with services outstanding

Server error codes

These error codes are written in case of an MMS error at client side.


WinCC OA error-code	TMW error code	Description
200	0	object-invalidated
201	1	hardware-fault
202	2	temporarily-unavailable
203	3	object-access-denied
204	4	object-undefined
205	5	invalid-address
206	6	type-unsupported
207	7	type-incosistent
208	8	object-attribute-inconsistent
209	9	object-access-unsupported
210	10	object-non-existent
211	11	object-value-invalid
212	12	unknown