> 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/opc_alarms-und-events-client.md).

# OPC Alarms and Events Client

#### Background

The OPC Alarms & Events driver interface connection works with all OPC servers which deliver alerts and messages. The ACRON Provider is notified of all alerts and messages in event-controlled mode and saves them cyclically to the ACRON database.

Note

If the "Create alert variables automatically" option is not active, only the messages and malfunctions for which an alert variable exists in ACRON are imported.

#### Syntax of external variable

No external variables can be defined, as only alerts and messages are imported.

## Driver <a href="#treiber" id="treiber"></a>

### 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 <a href="#treiberparameter" id="treiberparameter"></a>

### Server name

Name of the OPC server. If you leave the field empty, after startup the ACRON Provider displays all installed OPC servers so you can enter the name subsequently.

### Type

L- the OPC server is running on the local computer.

R- the OPC server is running on the remote computer.

### Node name

Name of the computer on which the OPC server is running.

## Settings <a href="#einstellungen" id="einstellungen"></a>

### Measure interval

This setting indicates the time interval in which values are polled by the control system/PLC. The minimum value depends on the efficiency of the corresponding interface and the number of external variables being logged.

Recommended entry 1 sec.

As the connection is event-controlled, this value is irrelevant.

### 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 OPC Server, about 10 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/opc_alarms-und-events-client.md?ask=<question>
```

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.