> 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/sattgraph-5000_odbc-anbindung-fuer-alarme.md).

# SattGraph 5000 ODBC interface for alerts

#### Background

The alerts and messages are imported via ODBC from the ACCESS database by a process connection driver into the ACRON Provider, saved to a binary intermediate file for each day, and imported from there into the ACRON database. Depending on the configuration of the external variables in ACRON, the events are assigned to malfunctions, messages, or for service monitoring.

In this, the "oEventlog" table from the database is cyclically checked and newly added records are imported. The "COMMENT" field in the table is of special significance, because ACRON identifies the alert types from this entry. The following entries are expected:

|            |                                                          |
| ---------- | -------------------------------------------------------- |
| *No entry* | Interpretation as for DISK                               |
| HIHI       | The external upper alert limit has been exceeded.        |
| HI         | The internal upper alert limit has been exceeded.        |
| LO         | The internal lower alert limit has been exceeded.        |
| LOLO       | The external lower alert limit has been exceeded.        |
| DEV        | A nominal value deviation has occurred.                  |
| MODF       | The value has changed too rapidly within the time range. |
| DISK       | A discrete event has occurred, e.g. a service pulse.     |

Entries are not case-sensitive.

#### Syntax of external variable

The name of the SattGraph variable (designation).

The syntax is Objectname$Signalname (e.g. Pump$OnRM).

## 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>

### ODBC name

Name of ODBC event database.

Note

ODBC name as configured by the ODBC administrator.

### Password

Usually no entry.

### Event types

Three event types each for event incoming/outgoing/acknowledged.

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

### Measure interval

In this time interval the ACRON Provider scans the "oEventlog" table for newly added events.

Recommended entry 60 sec.

### 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 0 sec.

### 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/sattgraph-5000_odbc-anbindung-fuer-alarme.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.