> 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/wizcon-von-axeda.md).
# Wizcon from Axeda
#### Background
The measurement data connection and the alert data connection are implemented via the Wizcon Toolkit interface and linked by a process connection driver. The ACRON Provider is notified of all changes to the requested data in event-controlled mode and saves them cyclically to the ACRON database.
Note
If the value of the tag is equal to ZERO, for import of the service processing pulses ACRON assumes that the unit in question is not running. If the value is any other, ACRON assumes that the unit is running. It is not necessary to define an alert in Wizcon.
### Syntax of external variable
For logging of the measurement data and service data, enter the name of the Wizcon variable (gate name) when defining the external variable.
Note
If you only want to import a single bit from an external variable, place a comma after the variable name and then append the bit number (0-31). To import the values of the 0th bit of the variable `TEST`, enter the external variable as follows: `TEST,0`.
If you do not want to create the alert variables automatically, for all variables used for malfunctions or messages you must specify a *gate name.alert definition ID* (e.g. TEMPERATURE.23). You can get the alert definition ID from the file `Wizcon_Gates.csv` (see "Import external variables and alert groups"). In the latest version of the ACRON process connection driver for Wizcon, gate values for the measurement data or service can be imported either locally or from a remote Wizcon station. When importing from a remote station, enter the external variable as *Stationname:Gatename*. Alerts for malfunction and message logging can only be imported locally.
#### Import external variables
1. Set all parameters for the Provider
2. Start the control system
3. Run "Import from control system" in the "External variables" area
Select the variables you want to import into ACRON.
#### Import predefined alert definitions
1. Enter all the parameters for the Provider, optionally in the file `Wizcon.def`
2. Start Wizcon and ACRON Provider
Every time it starts up the ACRON Provider generates the file `Wizcon_Alerts.csv` in the plant path, if it does not yet exist. In the file all the relevant alert definitions are listed. You can then import them in the Designer under "Alert groups".
#### Optional entries in the "Wizcon.def" file in the ACRON plant data path
In this file you enter settings including the filter conditions for alert logging. If you do not create this file. all alerts are logged. Otherwise only the alerts matching the specified filter condition are logged. The following entries must be inserted in the file using an editor (such as Notepad):
`[WIZCON]`
;under FamilyList specify any number of family names
;separated by spaces- no family is specified
;the alerts of all families are logged.
`FamilyList=Family1 Family2`
;The MinSeverity and MaxSeverity entries define the filter range of the weighting
`MinSeverity=0`
`MaxSeverity=50000`
;Under Class you specify, in hexadecimal format, which
;alerts of the classes are to be logged. The number is ;interpreted as a bit field. Each bit corresponds to a ;Class
`Class=ffffffff`
;The MinZone and MaxZone entries define
;the filter range for the priority
`MinZone=0`
`MaxZone=50000`
;Under StationList you enter any desired number of station names
;separated by spaces. If you do not specify a station
;only the alerts of the local station are logged.
`StationList=Station1 Station2`
## 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
### Record alerts
0 = No
1 = Yes
## Settings
### 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 1 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/wizcon-von-axeda.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.