> 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/import_von-historischen_dateien-dbase-csv.md).
# Import of historical files (DBASE, CSV)
#### Background
The ACRON Provider is used for all interfaces for data transfer from the process. This also applies to the file interface. 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".
Measured values, service counters and alerts can be imported.
Note
Service pulses cannot be imported! Here service counters must be formed in the PLC.
If you want to create the alerts from the import file automatically, you must set the "Create alert variables automatically" option in the Provider configuration (settings for alerts). Otherwise the alerts of missing alert variables will NOT be imported.
{% hint style="info" %}
Attention
In general, all data is imported. Existing data with the same time stamp are overwritten.
{% endhint %}
#### Connection for import of historical values
Two formats are supported for data import:
* DBASE format with file extension `*.DBF`
* CSV format with file extension `*.CSV`
In order to differentiate the value files from the historical alert files, the file names must begin with the letter "A" or "B".
The table layout is the same for both formats, and is explained in the following:
| Field name | Field type | Comment |
| ------------ | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **DATETIME** | Char, max. 30 characters | Here the time and date are set as a character string in the following format: YYYY-MM-DD HH:MM:SS Optionally, a - 'U' can be appended at the end of the time stamp to identify it as UTC time (e.g. 01.01.13 12:00:00U). - 'S' can be appended at the end of the time stamp to identify it as Summer time (e.g. 2013-01-01 12:00:00S). |
| **VARIABLE** | Char, max. 64 characters | Here the name of the external variable configured in ACRON is entered. |
| **VALUE** | Char, max. 64 characters | Here the current specified value of the variable is set as a character string. Either a point or a comma is accepted as the decimal separator. Scientific style is also supported. The valid value range is between -10^34 and +10^34. |
*Other optional fields*
| | | |
| ------------ | ------------------------ | --------------------------------------------------------------------------------------------------------- |
| **STATUS** | Numerical, 1 character | 0: Value is invalid 1: Value is valid |
| **MEANTIME** | Char, max. 32 characters | This field is ignored by ACRON, and exists only for historical reasons. |
| **TYPE** | Char, 1 character | Indicates the type of variable. D or no entry: Instantaneous value A: Average value M: Minimum X: Maximum |
A table may contain any number of data records. Each entry successfully transferred is deleted from ACRON. If the complete table is transferred successfully, it is completely deleted. The name of the table must begin with the letter "A" or "B", but the file extension must be " \*.DBF " or " \*.CSV ".
A semicolon is used as the separator between the fields.
2011-03-25 17:23:00;Intake;100.5
2011-03-25 17:23:00;Outlet;223.5
2011-03-25 18:10:00;Intake;110.5
2011-03-25 18:10:00;Outlet;202.5
2011-03-25 18:12:00;Intake;110.5;1;0;X
2011-03-25 18:12:00;Outlet;202.5;1;86400;A
All the lines in the file not beginning with a digit are ignored. Field-enclosing characters such as ยด or " are accepted.
#### Connection for import of historical alerts and messages
To import historical alerts and messages it is possible to transfer the data from any number of DBASE files or CSV files contained in the import path.
Note
If you want to create the alerts from the import file automatically, you must set the "Create alert variables automatically" option in the Provider configuration (settings for alerts). Otherwise the alerts of missing alert variables will NOT be imported.
#### File naming
The files must begin with the letter "H" or "I" and have the extension ".DBF" or "CSV" as appropriate. If ACRON finds multiple DBASE/CSV files in the alert 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.
It is essential that the order of fields be maintained. If you need one or more optional fields for the import, the previous optional fields must also be in the import file. The table layout is the same for both formats, and is explained in the following:
| Field name | Field type | Length | O / M | Meaning |
| ---------------- | ---------- | ------ | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **DATETIME** | Char | 19 | M | Here the time and date are set as a character string in the following format: YYYY-MM-DD HH:MM:SS Optionally, a - 'U' can be appended at the end of the time stamp to identify it as UTC time (e.g. 01.01.13 12:00:00U). - 'S' can be appended at the end of the time stamp to identify it as Summer time (e.g. 2013-01-01 12:00:00S). |
| **VARIABLENAME** | Char | 32 | M | The variable name |
| **EVENT** | Char | 3 | M | The alert event - Permitted: KMT: Alert begins GHT: Alert ends QIT: Active alert has been acknowledged NEW: New value alert RST: System has been restarted (All open alerts are ended, active alerts must be re-signaled.) |
| **EVENTTYPE** | Char | 5 | M | The alert type. Permitted entries depending on alert type group: [Limit value alerts](https://github.com/Dataforum-Software/gitbook/blob/master/acron/9.3/en/designer/glossar/grenzwertalarm.md): HIHI, HI, LO, LOLO [Deviation alerts](https://github.com/Dataforum-Software/gitbook/blob/master/acron/9.3/en/designer/glossar/abweichungsalarm.md): ABW1, ABW2 [Modification alerts](https://github.com/Dataforum-Software/gitbook/blob/master/acron/9.3/en/designer/glossar/aenderungsalarm.md): MODF Binary alerts 1: DISK Binary alerts 2: OPR Binary alerts 3: LGK Binary alerts 4: DDE Binary alerts 5: SYS |
| **OPERATOR** | Char | 18 | K | The name of the logged-in user |
| **PRIORITY** | Num | 3 | K | The priority of the alert (0-999) |
| **STRING** | Char | 58 | K | The alert text |
| **VALUE** | Char | 28 | K | The current value which has led to the alert being triggered. |
| **LIMIT** | Char | 28 | K | The value of the alert limit which was exceeded. |
| | | | O = Optional field / M = Mandatory field | |
#### Syntax of external variable
Name of variable as used in the DBASE or CSV file
## 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
### Full path for import files
Full path where the files to be imported are located.
### 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 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/import_von-historischen_dateien-dbase-csv.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.