> 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/prozessrohdatenuebernahme.md).
# ACRON process raw data transfer as of version 8.4 SP8
#### Background
With this driver, the recorded data of the external variables (process raw data) of any ACRON system as of version 8.4 SP8 can be used. The ACRON Provider cyclically transfers the accumulated data from the remote ACRON database to its own ACRON database.
The ACRON Provider notes the last time stamp imported for each variable in a definition file and on the next startup resumes the data transfer from that point. If the Provider does not run for a time, no data will be lost.
The definition file is located in the local plant cache path `C:\ProgramData\ACRON\PlantCache\MyPlantName` named `AcronToAcron.def`.
If the file is not present, or if no entry can be found in it for the variable in question, all data as from 01.01.1990 are imported. This is just what happens when you start up the Provider the first time, or when you create a new external variable.
Note
Alerts and service data cannot be imported via this interface.
{% hint style="info" %}
Attention
All data are imported. Existing data with the same time stamp is overwritten.
{% endhint %}
### Syntax of external variable
There are two ways to define the linkage:
* Link via identification
The identification must be specified exactly as in the remote ACRON system. The name can be user-defined, but must not begin with the character '#'. If the identification is changed in the remote system, this must also be done manually in the local system, otherwise no more data will be transferred since the variable can no longer be found.
* Link via ID
The identification can be assigned freely. The name must begin with the character '#' followed by the numeric ID of the variable from the remote ACRON system. The rest of the name can be freely assigned.
Example of a designation: "#123# Outside temperature".
Advantage of this method: If the identification is changed in the remote system, this has no effect on the link to this variable.
#### Import external variables
1. Fill in the first driver parameter TCP/IP Address
2. Run Import from control system in the "External variables" area
3. Select the variables you want to import into ACRON.
## 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
### TCP/IP address of ACRON database server
TCP/IP address of the database server followed by :port number from which the data are to be transferred. The database server must have at least version ACRON 8.4 SP8.
### TCP/IP address of redundant ACRON database server
TCP/IP address of the redundant database server followed by :port number from which the data are to be transferred. The database server must have at least version ACRON 8.4 SP8.
## Settings
### Measure interval
In this interval all accrued data are imported. Recommended entry 1-60 minutes (60,000 - 3,600,000 milliseconds). The provider uses this interval for all variables that deliver new values at least daily. Variables whose last value was 3 days ago are only queried in the interval \* 3. Variables whose last value was 10 days ago are only queried in the interval \* 10. This calculation is limited to 24 days, i.e. interval \* 24.
Example for measuring interval 10 minutes (600,000 milliseconds). After starting the Provider, all variables are queried. Variable 1 returns the last value from 1 hour ago. Variable 2 returns the last value from 3 days and 4 hours ago. The next query is for variable 1 in 10 minutes and for variable 2 in 30 minutes.
### Polling delay after start
Start of data logging in seconds after the ACRON Provider has successfully established process communication.
For this entry it makes no sense to define a delay, so a 0 must be entered here.
### 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/prozessrohdatenuebernahme.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.