> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/acron-9.3/en/anlagenkonfiguration/prozessanbindung/provider/providerid/treiberauswahl/wincc_online-anbindung-ab-wincc-professional-v12-mit-wincc-7.2.md).
# WinCC - Online interface as from WinCC Professional V12 with WinCC 7.2
#### Background
The measurement data connection and the alert data connection are implemented via the WinCC ODK (Open Developers Kit) interface and linked by a process connection driver. The ACRON Provider is notified of all changes to the requested data in event-controlled mode and saves them cyclically to the ACRON database.
Note
To enable the ACRON Provider to find the WinCC modules, the Windows system variable `PATH` muss contain the path to the WinCC programs (e.g. `C:\SIEMENS\WINCC\BIN`). This is normally configured automatically by WinCC Setup. The variable `PATH` can be changed in the Windows Control Panel under "System". Note that any change to this variable will only take effect after you restart Windows.
WinCC has a list of programs to be started along with the runtime module. The list is accessed by right-clicking on the computer icon in WinCC. The ACRON Provider must be included in this list. Whenever the runtime module is activated the Provider will automatically start too. Likewise, the Provider will shut down when the runtime module is shut down. Multiple Providers in the startup list can also be started, provided the parameters are written
directly after the program names rather than in the Parameters box.
Syntax: Program Plant identification Provider identification (Provider number)
e.g. `C:\ACRON\ACProv.exe PLANTDEMO 1`.
If the value of the tag is equal to ZERO, for import of the service processing pulses ACRON assumes that the unit in question is not running. If the value is any other, ACRON assumes that the unit is running.
#### Syntax of external variable
Name of the WinCC variable when defining the external variable
Note
If you only want to import a single bit from an external variable, place a comma after the variable name and then append the bit number (0-31). To import the values of the 0th bit of the variable `TEST`, enter the external variable as follows: `TEST,0`.
#### Import external variables
1. Set all parameters for the Provider
2. Start the control system
3. Run "Import from control system" in the "External variables" area
Select the variables you want to import into ACRON.
If you only want to address individual bits of a variable, you must list the variable repeatedly, each time with the respective bit number suffix.
## Driver
### Driver file
Display the name of the selected driver and select a driver from the list of installed drivers
### Version
Version of the driver file
### Interface type
Display the driver interface type
### Data transfer type
Description of the data transfer type
## Driver parameters
### Alert recording
0 = None
1 = Yes
2 = WinCC groups
### Data update index
The update cycle specified here applies to all external variables that this driver processes. The update cycle is defined by way of the index of entries in the update cycles list.
| | | |
| ----------------- | -------- | ------- |
| In case of change | Index 0 | |
| 250 | ms | Index 1 |
| 500 | ms | Index 2 |
| 001 | sec | Index 3 |
| 002 | sec | Index 4 |
| 005 | sec | Index 5 |
| ... | ... | ... |
| User cycle 5 | Index 15 | |
The update cycles list can be edited in WinCC.
### User block Tag name, Text, Group, Description
Format parameter specifying how the alert information is transferred from WinCC to ACRON Alert. The format consists of four blocks which must be filled out by WinCC:
* Variable name
* Text
* Group
* Description
The individual blocks are enclosed in square brackets.
WinCC supports two types of data via the ODK interface:
* Default handling
* User blocks
Digit 0: Default handling
Digit 1: User block 1
Digit 2: User block 2
Digit 3: User block 3
Digit 4: User block 4
Digit 5: User block 5
Digit 6: User block 6
Digit 7: User block 7
Digit 8: User block 8
Digit 9: User block 9
Digit A: User block 10
Any character containing no digits or greater than A is adopted as text.
**\[0]\[0:3]\[2]\[0]**
Content of alert block 2: Power failure
Content of alert block 3: Control room
**Result:**
ACRON Alert variable name = WinCC default handling
ACRON Alert text = WinCC default handling plus ":" plus "Control room"
ACRON Alert group = "Power failure"
ACRON Alert description = WinCC default handling
Note
The group and description are only filled out by the provider when setting up the variable. There are then no more automatic changes to these two fields.
### Type
The number of the WinCC message type, separate by a blank, is entered here.
Type: HiHi Hi LoLo Lo ABW1 ABW2 AEND DISK OPR SYS: `1 2 4 3 0 0 0 0 0 0`
**That means:**
Message type 1 becomes ACRON event type HiHi
Message type 2 becomes ACRON event type Hi
Message type 4 becomes ACRON event type LoLo
Message type 3 becomes ACRON event type Lo
Note
No other ACRON event types are supported.
## Settings
### Polling delay after start
Start of data logging in seconds after the ACRON Provider has successfully established process communication. This is useful, for example, if the opposite party takes some time after a restart to initialize all the variables.
Recommended entry: Depending on the startup duration of the runtime module, about 30 seconds
### Always display provider window on top
Provider windows are always displayed on top
### Activate test mode
Display a window with diagnostic messages
On startup the ACRON Provider opens a window with diagnostic messages. The log file is stored under the relevant provider name in the ACRON installation path, in the `Log` directory.
Note
As diagnosis mode heavily influences the performance of the application, and the recorded messages can normally only be evaluated by Technical Support, you should only activate it when prompted to do so by Support.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.videc.de/acron-9.3/en/anlagenkonfiguration/prozessanbindung/provider/providerid/treiberauswahl/wincc_online-anbindung-ab-wincc-professional-v12-mit-wincc-7.2.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.