> 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-flexible_alarme-und-audit-trail.md).

# WinCC flexible - Alerts and audit trail

#### Background

Many WinCC flexible systems are capable of storing their messages and the audit trail in an archive as a CSV file. In this, the files being imported are stored in a configurable path (import path). The Provider cyclically checks whether a new file has been created in this path. If it has, the data from this file are automatically imported into the ACRON database. Following successful import, the file is deleted from the ACRON Provider. Any errors occurring during import are written to a log file ("filename.CS\_"). This log file is in \*.CSV format, and can be imported again by renaming it "filename.CSV".

If you want to create the variables relating to the alerts from the import file automatically, you must set the "Create alert variables automatically" marker in the Provider configuration (settings for alerts). Otherwise the alerts of missing alert variables will NOT be imported.

#### File naming

The files must have the extension ".CSV". If ACRON finds multiple CSV files in the import path, they are imported in alphabetical order of their names. If the alerts of a variable are spread across multiple files, it is important that the alerts coming in later are in the file further down the alphabetical order. Only in this way is ACRON able to combine individual incoming/outgoing event pairs into one malfunction.

#### File syntax

The files must have the following syntax:

**1. Message files:**

`"Time_ms";"MsgProc";"StateAfter";"MsgClass";"MsgNumber";"Var1";"Var2";"Var3";"Var4";"Var5";"Var6";"Var7";"Var8";"TimeString";"MsgText";"PLC"`

40073482429,2593;2;1;64;25;;;;;;;;;"07.01.2013 11:34:42";"25 Fill alert Washtank";"PLC"

40073482655,787;2;3;64;25;;;;;;;;;"07.01.2013 11:35:01";"25 Fill alert Washtank";"PLC"

40073482658,8657;2;1;64;216;;;;;;;;;"07.01.2013 11:35:02";"216 Alert communication PLC HMI failed";"\<internal>"

40073482790,1157;2;2;64;25;;;;;;;;;"07.01.2013 11:35:13";"25 Fill alert Washtank";"PLC"

40073482815,9606;2;3;64;216;;;;;;;;;"07.01.2013 11:35:15";"216 Alert communication PLC HMI failed";"\<internal>"

`"$RT_COUNT$";6;;;;;;;;;;;;;;`

**2. Audit trail files**

`"RecordID";"TimeStamp";"DeltaToUTC";"UserID";"ObjectID";"Description";"Comment";"Checksum"`

0;"07.01.2012 11:34:16";"-2:00";"System";"Application";"Runtime start from operating device LEMAIRER-XP-NB. Projekt: 'PROJECT\_1.Touchpanel URS - 0' Build 927, created with WinCC flexible 2008 SP1 AdvancedWinCC flexible RT 2008 SP1";;WAyRZU

608;"07.01.2013 11:34:16";"-2:00";"System";"Application";"Change to 'Online' operating mode.";;klfSK6

609;"07.01.2013 11:34:16";"-2:00";"System";"User administration";"Import user administration successfully completed.";;2+OTso

610;"07.01.2013 11:35:00";"-2:00";"NOTAdmin";"User administration";"User 'NOTAdmin' with group 'NOTAdmin' logged int.";;X5ZnyT

611;"07.01.2013 11:35:01";"-2:00";"NOTAdmin";"Message: 25";"Acknowledgement of message 25 of the PLC control.";;A+omO6

612;"07.01.2013 11:35:15";"-2:00";"NOTAdmin";"Message: 216";"Acknowledgement of message 216 of the controller \<internal>.";;s2g7Ir

613;"07.01.2013 11:35:17";"-2:00";"NOTAdmin";"button is pressed: start button";"pressed";;0yUX75

614;"07.01.2013 11:35:29";"-2:00";"NOTAdmin";"Variable: DB42 Parameter General.Min\_Druck\_RSP\_df";"Change the value of the variable 'DB42 Parameter General.Min\_Druck\_RSP\_df' from '0' to '10.";;NPtvjf

615;"07.01.2013 11:35:56";"-2:00";"NOTAdmin";"Application";"Application will be terminated.";;CRWlmV

0;"07.01.2013 11:35:56";"-2:00";"System";"Application";"End of the program run of WinCC flexible RT 2008 SP1 on device LEMAIRER-XP-NB.";;F9gLQS

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

### Full path for import files

Full path where the files to be imported are located.

### Winter time starts by variable number

An alert variable can be used to control whether ambiguous time stamps are assigned to Summer or Winter time.

As soon as the variable occurs with the number specified here in the import file, all time stamps in the duplicated hour at the start of Winter time are interpreted as Winter time.

Note

This parameter setting is optional.

### Import variable names before the colon

Value 0 (default):

Only the trailing part of the object ID (after the colon) is used as alarm variable.

Value 1:

The whole part of the object ID is used as alarm variable.

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

### Measure interval

This setting the time interval in which data are transferred.

Recommended entry 60 sec.

### Polling delay after start

How many seconds after startup the ACRON Provider is to start data transfer.

Recommended entry 60 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/wincc-flexible_alarme-und-audit-trail.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.
