Wiener PCI VME device
Status:
This documentation applies to version 1.16.66.2 of the Wiener PCI VME.
Contents:
Overview:
Device parameters, Addressing,
Standard crates:
Wiener PCI VME version, setup:
Unique device id: The unique device id as defined in the database, DeviceLocation table.
Base persistent file name: If at least one of 'Persistent History' or 'Persistent control data' is checked the base file name must be specified. The filename should be specified without path and extensions. It is used to generate the persistent files used to store current control data and history data. The data files are stored in the ConSys executable directory. The extension on history files is 'hst' and on control files 'permanent'. See also the description of the initialisation method below.
Store interval (hours): The time between update of the persistent data on disc. Under normal conditions, the persistent data is stored when the control system is closed. To ensure loss of data in case of a crash the persistent data is updated regularly at the specified intervals.
Persistent history: Checked, if histories should be stored to disc.
Persistent control data: Checked, if control values should be stored to disc.
Control value initialisation mode:
None: The control values are not transferred to the G64 crate
during initialisation
From database: The control values is obtained from the
database default values and send to all control values in the G64 crate.
From persistent file: During device initialisation the
device first looks for a file with the name '<Base persistent file name>.loadOnce'.
If this file exist the command values are loaded from the file and the file is
deleted. If the file does not exist, the device looks for a file with the name
' <Base persistent file name>.permanent' and load
the command values from this file. If no file could be found the default values
from the database is used to set the crate control values.
Last Modified 06 May 2020