> 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/nivus_import-von-procosdateien.md).
# NIVUS import of Procos files
#### Background
This driver cyclically imports the delta event archives (\*.PLS files) stored by Procos.
The path from which ACRON imports the PLS files is taken from the Registry:
`HKEY_LOCAL_MACHINE/Software/NIVUS GmbH/PLS/PROCOS/Path + DEA`
The entry is made when installing Procos.
The Provider cyclically checks whether a file in this path for which an external variable was created in ACRON has changed. If it has, the data from this file are automatically imported into the ACRON database.
Measured values, service pulses, service counters and digital values can be imported.
When the Provider starts up, all data found are retrospectively imported. The Provider then logs the month back to which data were imported for each variable in the ASCII file `PROCOS.DEF` in the local plant cache path `C:\ProgramData\Acron\PlantCache\MyPlantName`, and then only imports changes to values in the current and previous month. If you want to import earlier variable data subsequently, you must exit the Provider, delete the relevant line from the `PROCOS.DEF` file and then restart the Provider.
#### Syntax of external variable
The name of the external variable must match the first 5 letters of the name of the PLS files being imported (e.g. M0001). Do exactly the same for manual variables!
Optionally, you can set a filter for the identifier and the "reason" for the values. To do this, enter the identifier and the reason separated by '@'.
| | |
| ------------ | ------------------------------------------------------------------------- |
| "M0001" | All values are imported |
| "M0001\@4@L" | Only data entries with the identifier 4 and the reason "L" are processed. |
| "M0001@\*@L" | Only data entries with the reason "L" are processed. |
| "M0001\@4" | Only data entries with the identifier 4 are processed. |
#### Import of existing manual variables
Create all manual variables in ACRON.
The assigned external variable must have the same name as the first 5 characters of the `H*.pls` file.
In the configuration of the external variables, assign all external variables for manual variables to the Provider for Procos.
Copy all the files from the Procos "Lab values" path to the DEA path.
Start the Provider. All manual variables are imported.
Delete the manual variable files from the DEA path as necessary.
## 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
### Priority
You should define a priority here depending on the computer workload. Higher priorities will result in faster data transfer times but higher computer loading.
1 = High
2 = Normal
3 = Low
4 = Very low
## Settings
### 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.
An entry of 300 seconds is usually enough. Shorter times up to 15 seconds are possible.
### 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/nivus_import-von-procosdateien.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.