> 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/ifix-von-ge-ab-version-3_5.md).

# iFIX from GE as from version 3.5

#### Background

The measurement data connection and the alert data connection are implemented via the FIX EDA ("Easy Database Access") interface and linked by a process connection driver. The ACRON Provider cyclically polls the required data via the driver and saves them to the ACRON database.

#### Import external variables

Import predefined variables:

1. Set all parameters for the Provider
2. Start FIX
3. Run "Import from control system" in the "External variables" area

   Select the variables you want to import into ACRON.

#### Syntax of external variable

The following syntax muss be observed for the external variable names:

|                         |                     |
| ----------------------- | ------------------- |
| VARIABLENAME            | e.g. PV1            |
| NODE:VARIABLENAME       | e.g. DEMO:PV1       |
| NODE:VARIABLENAME.FIELD | e.g. DEMO:PV1.F\_CV |
| VARIABLENAME.FIELD      | e.g. PV1.F\_CV      |

The "NODE:" entry is optional. If the entry is missing, ACRON adds the local node name of the current running FIX project during the runtime.

ACRON appends the following field extensions if none were specified:

|       |                                                                                  |
| ----- | -------------------------------------------------------------------------------- |
| A\_CV | for alphanumeric variables                                                       |
| E\_CV | for numeric variables if the iFix version supports 64-bit data types             |
| F\_CV | for numeric variables if the iFix version does not yet support 64-bit data types |

Note

The variable names must always be entered in UPPER CASE.

To enable the Provider to find the FIX libraries, the system variable ACRON m`PATH`ust contain the FIX installation path.

In the case of external variables for the service pulses, the ACRON Provider polls every change from FIX and proceeds as follows: If the value changes from ZERO to a different value, ACRON assumes that the unit has been switched on. If the value changes from not equal to ZERO to ZERO, ACRON assumes that the unit has been switched off. These events are stored in a binary intermediate file in the ACRON alert path, and imported from there by the ACRON Reporter or ACRON Data Transfer for the service module as required.

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

### Record alerts (1/0) and name of iFIX AlarmQueue

Record alerts: 0 = No, 1 = Yes

Name of iFIX AlarmQueue: e.g. AC1

Example: `1 AC1`

`AlarmUserQ.exe` must then be started in the SCU with the following parameter: `ALMUSERQ.EXE /nAC1`

### Record alerts only for the following physical node

Alerts are recorded for the specified node; if you make no entry, alerts of all occurring nodes will be recorded.

### Alert filter

Filter constraint for the alerts to be included with wildcards. Only the variable names matching the filter are created and applied. Entries are not case-sensitive. If the field is left blank, the filter is not used.

### Poll only these nodes when browsing

Node names to poll.

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

### 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: 1 - 5 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: 10 - 30 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/ifix-von-ge-ab-version-3_5.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.
