Home
Southbound Interfaces
The process connection to the actual machines/sensors.
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 Configuration
Connection

Version Information
Release Notes, Update information, Certifications and Frequently Asked Questions.
Concepts
Your first step into modern and powerful process visualization.
Deployment
Topics, you need to know, before using WinCC OA.
Security
Go beyond the norm in cybersecurity.
Engineering
Powerful tools for easy or complex engineering tasks.
Data Management
Classify, structure and archive your data.
Business Logic / Control
Endless possibilities in data processing for your projects.
Data Visualization
User interfaces, Trends and Reports for every purpose and device.
Southbound Interfaces
The process connection to the actual machines/sensors.
- S7Plus Driver
  The WinCC OA S7Plus driver uses the Siemens communication library IOMS and is meant for the communication with Siemens S7 PLCs.
- S7 Driver
  The WinCC OA S7 driver is a native driver for connection to the periphery with Siemens S7 PLCs.
- 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 Client
  This chapter explains the most important terms and presents the steps involved in starting a functioning OPC communication. The individual points will be dealt with in more detail in the subsequent chapters.
- 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
- 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 Driver
  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.
- 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.
- 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.
- 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.
- PROFIsafe Driver
  As an application profile of PROFINET, PROFIsafe is responsible for the communication between safety devices (F-Device) and safety controllers (F-Host).
- S-Bus Driver
  The WinCC OA S-Bus driver is used for the connection from SAIA PCD control devices to WinCC OA projects.
- SSI Driver
  The WinCC OA SSI driver is used for interfacing SAT remote systems.
- 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.
- RK512 Driver
  The WinCC OA driver RK512 is used for interfacing a programmable logic controller using the 3964R/RK512 protocol.
- 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.
- 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).
- 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.
Northbound Interfaces
Your portal to the cloud or supervising systems.
Web Connectivity / Network Interfaces
Data exchange, APIs and web technologies
User Management
All about authorization, authentication and login-customization.
Availability
How to get your system uptime to the maximum.
Reporting
Create state of the art project reports without limits.
Addons
Useful tools and enhancements for special demands.
Reference Tables
Detailed and extensive content for special project adaptation.
Videos & Tutorials
Explore the capabilities of WinCC OA with our carefully selected collection of video tutorials and guides.
WinCC OA Documentation
Basic information about terms and functions within the documentation.
Disclaimer
A brief clarification of liability exclusions or legal notices.

Connection

This tab allows to define general connection parameters like host and port number. Depending on the configuration you may have to define these parameters for a redundant connection too.

Figure 1. Connection tab

Type

Allows to define the connection type.

Unsecure
TLS
WebSocket
TLS-PSK

MQTT Broker - Host:Port

In this field the connection information of the broker can be specified. For the most protocol types this entry specifies a hostname and a port number. For WebSocket connection type this is a URL as can be seen in the example below.

Unsecure: 127.0.0.1:1883
TLS: secureBroker.com:8883
WebSocket: ws://www.example.com/mqtt

Note: Note that for secure websocket the URL starts with wss.

Username

User name to access the broker, if necessary.

Password

Password to access the broker, if necessary.

Certificate

If connection type TLS is defined, the certificate of the broker that the client shall trust must be entered here. The specified certificate file is retrieved from the directory specified by the config entry certPath.

In case of connection type WebSocket no certificate must be defined. However, the broker's root certificate must be installed on the client computer as trusted certificate. For how to install a certificate into the operating system trust list, see https://learn.microsoft.com/en-us/skype-sdk/sdn/articles/installing-the-trusted-root-certificate.

Important: In some cases, certificates created with other tools than openSSL might lead to connection issues, and therefore it is recommended to use openSSL to create all certificates related to your project. An easy method to generate certificates is using the Panel for SSL Certificates.

PSK Identity

The identity that should be used for the pre-shared key defined within the PSK textfield.

Remember: The option is only used if the connection type TLS-PSK is used.

PSK

The pre-shared key that is used for the connection and stored as encrypted string.

Remember: The option is only used if the connection type TLS-PSK is used.

TLS Version

The TLS version that should be used for the connection.

Remember: The option is only used if the connection type TLS-PSK is used.

Restriction: Due to restrictions of the Qt-Framework the TLS version 1.3 cannot be used for PSK based communication.