fwConfigurationDB_Hierarchies.ctl File Reference


Indexing constants for deviceListObject variables

The following constants are used to refer to the data in a single row of a deviceListObject variable (a recipeRow).

const int fwConfigurationDB_DLO_DPNAME = 1
const int fwConfigurationDB_DLO_DPTYPE = 2
const int fwConfigurationDB_DLO_NAME = 3
const int fwConfigurationDB_DLO_MODEL = 5
const int fwConfigurationDB_DLO_COMMENT = 6
const int fwConfigurationDB_DLO_ITEMID = 7
const int fwConfigurationDB_DLO_PARENTID = 8
const int fwConfigurationDB_DLO_DPID = 9
const int fwConfigurationDB_DLO_REFDP = 10
const int fwConfigurationDB_DLO_REFID = 11
const int fwConfigurationDB_DLO_REF_STATUS = 12
const int fwConfigurationDB_DLO_PROPIDS = 13
const int fwConfigurationDB_DLO_PROPNAMES = 14
const int fwConfigurationDB_DLO_CITEM_ID = 15
const int fwConfigurationDB_DLO_MAX_IDX = 15

Functions

void fwConfigurationDB_getDBHierarchies (dyn_int &ids, dyn_string &types, dyn_string &descriptions, dyn_string &validFrom, dyn_string &validTo, dyn_string &exceptionInfo)
void fwConfigurationDB_extractHierarchyFromDB (string topDevice, string hierarchyType, dyn_dyn_mixed &deviceListObject, dyn_string &exceptionInfo, string system="")
void _fwConfigurationDB_getReferencesFromDB (dyn_dyn_mixed &deviceListObject, string configurationName, dyn_string &exceptionInfo)
void fwConfigurationDB_resolveDevices (dyn_string deviceList, dyn_string &devHierarchies, dyn_string &devDatapoints, dyn_string &exceptionInfo, bool errorOnNotFound=TRUE)
void fwConfigurationDB_getHierarchyFromPVSS (string rootNode, string hierarchyType, dyn_string &nodeList, dyn_string &exceptionInfo, string system="", string includeRootNode=TRUE)
void _fwConfigurationDB_copyDeviceListObjectEntry (dyn_dyn_mixed srcObject, int src_idx, dyn_dyn_mixed &dstObject, int dst_idx, dyn_string &exceptionInfo)
void _fwConfigurationDB_ensureDeviceListObjectValid (dyn_dyn_mixed &obj)
void fwConfigurationDB_expandToDeviceListObject (string hierarchyType, dyn_string deviceList, dyn_dyn_mixed &deviceListObject, dyn_string &exceptionInfo)
void _fwConfigurationDB_dbCompleteDevicesInHierarchy (dyn_string &deviceList, string hierarchyType, string configurationName, dyn_string &exceptionInfo)
void _fwConfigurationDB_completeDevicesInHierarchy (dyn_string &deviceList, string hierarchyType, string system, dyn_string &exceptionInfo)
void fwConfigurationDB_findDevicesInDB (string topDevice, string hierarchyType, dyn_string deviceList, dyn_dyn_mixed &deviceListObject, dyn_string &missingDevicesList, dyn_string &exceptionInfo, string system="")
void _fwConfigurationDB_verifyDatapoints (string hierarchyType, dyn_dyn_mixed &deviceListObject, dyn_dyn_mixed &missingDevicesListObject, dyn_string &exceptionInfo, bool checkDeviceLocal=FALSE)
void fwConfigurationDB_updateDeviceHierarchyFromDB (string topDevice, string hierarchyType, dyn_string &exceptionInfo, string systemName="")
void _fwConfigurationDB_createDevices (dyn_dyn_mixed deviceListObject, string hierarchyType, dyn_string &exceptionInfo)
void _fwConfigurationDB_configureDevices (dyn_dyn_mixed deviceListObject, string hierarchyType, dyn_string &exceptionInfo, int options=fwConfigurationDB_deviceConfig_ALLDEVPROPS)
void _fwConfigurationDB_getDBRootNodeId (string hierarchyType, int &rootNode, dyn_string &exceptionInfo, string systemName="")
void _fwConfigurationDB_DBFindItems (string hierarchyType, dyn_string deviceList, dyn_int &itemIds, dyn_string &exceptionInfo)
void _fwConfigurationDB_DBAssignItemIds (string hierarchyType, dyn_dyn_mixed &deviceListObject, dyn_string &exceptionInfo, string systemName="")
void _fwConfigurationDB_resolveLogicalIds (dyn_dyn_mixed &deviceListObject, dyn_string &exceptionInfo, string systemName)
void _fwConfigurationDB_saveDeviceHierarchyToDB (string topDevice, string hierarchyType, dyn_string deviceDpNames, dyn_string &exceptionInfo, string systemName, dyn_dyn_mixed &deviceListObject)
void fwConfigurationDB_saveReferences (string configurationName, dyn_dyn_mixed deviceListObject, dyn_string &exceptionInfo)
void fwConfigurationDB_getReferencesHistory (string configName, string hierarchyType, time startTime, time endTime, dyn_string itemNames, dyn_dyn_mixed &references, dyn_string &exceptionInfo)
void _fwConfigurationDB_saveItemsToDB (dyn_dyn_mixed deviceListObject, string hierarchyType, dyn_string &exceptionInfo)
void fwConfigurationDB_getDeviceConfigurations (string hierarchyType, dyn_string &confNames, dyn_string &confDescriptions, dyn_int &confIds, dyn_string &exceptionInfo)
int _fwConfigurationDB_checkCreateDeviceConfiguration (string hierarchyType, string confName, string confDescription, dyn_string &exceptionInfo)
void _fwConfigurationDB_checkSaveDpTypes (dyn_string dpTypes, dyn_int &dpTypeIds, dyn_mixed &dpTypeElements, dyn_mixed &dpTypeElementIds, time date, dyn_string &exceptionInfo)
void _fwConfigurationDB_configureFwDevicesWithDefaults (dyn_string dps, dyn_string dptypes, dyn_string models, dyn_string &exceptionInfo)
void fwConfigurationDB_updateDeviceConfigurationFromDB (string configurationName, string hierarchyType, dyn_string &exceptionInfo, time validOn=0, dyn_string deviceList="", string systemName="", int options=fwConfigurationDB_deviceConfig_ALLDEVPROPS)
void _fwConfigurationDB_configureDevicesFromDB (dyn_string dpes, dyn_int propIds, dyn_string &exceptionInfo, int options=fwConfigurationDB_deviceConfig_ALLDEVPROPS)
void _fwConfigurationDB_getIpropIdsInConfiguration (string configurationName, dyn_string &dpes, dyn_int &ipropIds, dyn_string &exceptionInfo)
void fwConfigurationDB_saveDeviceConfigurationInDB (dyn_string deviceList, string hierarchyType, string configurationName, anytype saveConfigs, dyn_string &exceptionInfo, string systemName="", string confDescription="")
void fwConfigurationDB_reconnectDevices (dyn_string deviceList, string configurationName, string hierarchyType, string targetSystem, dyn_string &exceptionInfo)
int fwConfigurationDB_saveDevicesToDBMinimal (dyn_string &deviceList, dyn_string &exceptionInfo, bool abortWhenDeviceMissing=FALSE)
void fwConfigurationDB_updateDeviceModelsInDB (dyn_string dpList, dyn_string &exceptionInfo, bool updateAliases=TRUE)

Variables

global string _fwConfigurationDB_fileVersion_fwConfigurationDB_Hierarchies_ctl = "3.4.0"
const int fwConfigurationDB_deviceConfig_VALUE = 1
const int fwConfigurationDB_deviceConfig_ADDRESS = 2
const int fwConfigurationDB_deviceConfig_ALERT = 4
const int fwConfigurationDB_deviceConfig_ARCHIVING = 8
const int fwConfigurationDB_deviceConfig_DPFUNCTION = 16
const int fwConfigurationDB_deviceConfig_CONVERSION = 32
const int fwConfigurationDB_deviceConfig_PVRANGE = 64
const int fwConfigurationDB_deviceConfig_SMOOTHING = 128
const int fwConfigurationDB_deviceConfig_UNITANDFORMAT = 256
const int fwConfigurationDB_deviceConfig_ALLDEVPROPS = 511
const int fwConfigurationDB_deviceConfig_VALUE_ADDR_IN = 512
const int fwConfigurationDB_deviceConfig_VALUE_ADDR_OUT = 1024
const int fwConfigurationDB_deviceConfig_FW_DEFAULTS = 32768

Detailed Description

This package contains hierarchy-related functions of the Configuration Database tool

Author:
Piotr Golonka (IT-CO/BE)
Date:
May 2009

Function Documentation

void fwConfigurationDB_getDBHierarchies ( dyn_int &  ids,
dyn_string &  types,
dyn_string &  descriptions,
dyn_string &  validFrom,
dyn_string &  validTo,
dyn_string &  exceptionInfo 
)

void fwConfigurationDB_extractHierarchyFromDB ( string  topDevice,
string  hierarchyType,
dyn_dyn_mixed &  deviceListObject,
dyn_string &  exceptionInfo,
string  system = "" 
)

void _fwConfigurationDB_getReferencesFromDB ( dyn_dyn_mixed &  deviceListObject,
string  configurationName,
dyn_string &  exceptionInfo 
)

Completes the information for the logical hierarchy

requires fields: fwConfigurationDB_DLO_DPNAME, fwConfigurationDB_DLO_DPTYPE fills-in fields: fwConfigurationDB_DLO_REFDP, fwConfigurationDB_DLO_REFID

skips the fields that has type == "Node"

void fwConfigurationDB_resolveDevices ( dyn_string  deviceList,
dyn_string &  devHierarchies,
dyn_string &  devDatapoints,
dyn_string &  exceptionInfo,
bool  errorOnNotFound = TRUE 
)

Resolves device names

This functions takes the list of device names - devices being in either hierarchy, and tells what are the actual hierarchy to which they belong, and what are the datapoint to which they refer

void fwConfigurationDB_getHierarchyFromPVSS ( string  rootNode,
string  hierarchyType,
dyn_string &  nodeList,
dyn_string &  exceptionInfo,
string  system = "",
string  includeRootNode = TRUE 
)

Gets the list of children items, in specified hierarchy

Parameters:
rootNode the name of the parent device (item)
hierarchyType the Framework hierarchy type:
  • fwDevice_HARDWARE for Hardware hierarchy
  • fwDevice_LOGICAL for Logical hierarchy (other hierarchies are not supported yet).
nodeList the resulting list of child items will be stored in this variable. Note that this is "append" operation, i.e. the contents of the variable are not cleared from previous content!
exceptionInfo standard exception handling variable
system (optional) the name of the system (for distributed systems); when not specified, the local system is assumed
includeRootNode (optional) determined if the rootNode will be included in the list; if TRUE (default) rootNode will be included, if FALSE - it will not.
See also:
Device lists section of the Quick Start.

void _fwConfigurationDB_copyDeviceListObjectEntry ( dyn_dyn_mixed  srcObject,
int  src_idx,
dyn_dyn_mixed &  dstObject,
int  dst_idx,
dyn_string &  exceptionInfo 
)

Copies one entry (line) of device object to another device object. if dst_idx=0 this is "append" operation

void _fwConfigurationDB_ensureDeviceListObjectValid ( dyn_dyn_mixed &  obj  ) 

void fwConfigurationDB_expandToDeviceListObject ( string  hierarchyType,
dyn_string  deviceList,
dyn_dyn_mixed &  deviceListObject,
dyn_string &  exceptionInfo 
)

For devices in the deviceList, the DeviceListObject is created, filled with complete information. Note that the function works for the devices that are already in the system (i.e. the function is used when saving hierarchy to DB)

void _fwConfigurationDB_dbCompleteDevicesInHierarchy ( dyn_string &  deviceList,
string  hierarchyType,
string  configurationName,
dyn_string &  exceptionInfo 
)

adds the required (parent) devices to the list, based on the data in the database, puts the hierarchy in order. this function is used by fwConfigurationDB_reconnectDevices

void _fwConfigurationDB_completeDevicesInHierarchy ( dyn_string &  deviceList,
string  hierarchyType,
string  system,
dyn_string &  exceptionInfo 
)

adds the required (parent) devices to the list, puts the hierarchy in order

void fwConfigurationDB_findDevicesInDB ( string  topDevice,
string  hierarchyType,
dyn_string  deviceList,
dyn_dyn_mixed &  deviceListObject,
dyn_string &  missingDevicesList,
dyn_string &  exceptionInfo,
string  system = "" 
)

Finds the devices that exist and devices that do not exist, returns them as deviceListObject variables, ready for further processing.

WARNING! Empty system name here means: don't filter!

void _fwConfigurationDB_verifyDatapoints ( string  hierarchyType,
dyn_dyn_mixed &  deviceListObject,
dyn_dyn_mixed &  missingDevicesListObject,
dyn_string &  exceptionInfo,
bool  checkDeviceLocal = FALSE 
)

check if datapoints exist and verify that existing ones have appropriate types and models. Find and group in the missingDevicesListObject the ones that does not exist, report (with exceptionInfo) if some of them exist with incompatible type

void fwConfigurationDB_updateDeviceHierarchyFromDB ( string  topDevice,
string  hierarchyType,
dyn_string &  exceptionInfo,
string  systemName = "" 
)

Creates missing devices in PVSS, so the structure reflects the one in the DB

note that it should work only for the local system

the systemName parameter is only meaning for logical hierarchy: it indicates which type of logical hierarchy should be loaded: the one that includes system name, or the one that does not (empty systemName). In the latter case, only the leaves that are currently mapped to devices that are present on the current system are loaded, plus all the "branch" nodes that lead to them...

use fwConfigurationDB_updateDeviceConfigurationFromDB instead

void _fwConfigurationDB_createDevices ( dyn_dyn_mixed  deviceListObject,
string  hierarchyType,
dyn_string &  exceptionInfo 
)

void _fwConfigurationDB_configureDevices ( dyn_dyn_mixed  deviceListObject,
string  hierarchyType,
dyn_string &  exceptionInfo,
int  options = fwConfigurationDB_deviceConfig_ALLDEVPROPS 
)

void _fwConfigurationDB_getDBRootNodeId ( string  hierarchyType,
int &  rootNode,
dyn_string &  exceptionInfo,
string  systemName = "" 
)

void _fwConfigurationDB_DBFindItems ( string  hierarchyType,
dyn_string  deviceList,
dyn_int &  itemIds,
dyn_string &  exceptionInfo 
)

This one resolves the DB id's of items and reports error if device was not found...

Parameters:
hierarchyType is dummy as of now!

void _fwConfigurationDB_DBAssignItemIds ( string  hierarchyType,
dyn_dyn_mixed &  deviceListObject,
dyn_string &  exceptionInfo,
string  systemName = "" 
)

This one is used when storing the devices in DB, it assigns new identifiers to the devices that are not present, then adjusts parent pointers, etc. It will also resolve the ID's of DPElements, if they are defined

void _fwConfigurationDB_resolveLogicalIds ( dyn_dyn_mixed &  deviceListObject,
dyn_string &  exceptionInfo,
string  systemName 
)

void _fwConfigurationDB_saveDeviceHierarchyToDB ( string  topDevice,
string  hierarchyType,
dyn_string  deviceDpNames,
dyn_string &  exceptionInfo,
string  systemName,
dyn_dyn_mixed &  deviceListObject 
)

Creates devices in DB

The function stores the devices in the appropriate hierarchy, without storing their properties. Note that the devices that are already present in the db will not be re-created.

CONVENTIONS: 1) for HARDWARE hierarchy: ) systemName needs to be set. "" is equal to passing getSystemName() ) specifying the name of other (remote) system allows to save its hierarchy! ) topDevice and deviceDpNames needs to contain system name ) if sysname is not specified at all - use the one from systemName ) if sysname is included but differs from systemName: report an error 2) for LOGICAL hierarchy A) when systemName!="" - use specified system name ) topDevice and deviceDpNames need to contain system name ) if sysname not specified - complete it from systemName ) if if differs: report an error B) when systemName=="", we have a hierarchy with common root across all systems (i.e. logical hierarchy without system names) ) topDevice and deviceDpNames must not include system name ) we simply cut it away if it was passed

Parameters:
topDevice - a "hint" information that tells where to start verification of whether device exists, etc. Empty string ("") means the top of hierarchy

void fwConfigurationDB_saveReferences ( string  configurationName,
dyn_dyn_mixed  deviceListObject,
dyn_string &  exceptionInfo 
)

void fwConfigurationDB_getReferencesHistory ( string  configName,
string  hierarchyType,
time  startTime,
time  endTime,
dyn_string  itemNames,
dyn_dyn_mixed &  references,
dyn_string &  exceptionInfo 
)

Returns the history of hierarchies mapping for specipied period of time, and for certain configuration.

Parameters:
configName the name of static configuration
hierarchyType type of hierarchy (eg. fwDevice_LOGICAL)
startTime start of queried period of time
endTime end of queried period of time. Passing 0 as a parameter means: up to now
itemNames list of logical names of devices being queried
references the result will be put in this variable on return; explanation of the output format below
exceptionInfo standard exception handling variable
The data returned by the function has a format of 4-column array: The rows are sorted by logical dpname and start of validity.

Example:
references[1] references[2] references[3] references[4]
SubSys/straw1 dist_1:CAEN/crate01/board00/channel001 5 Jan 2006 6 Jan 2006
SubSys/straw1 dist_1:CAEN/crate01/board00/channel011 6 Jan 2006 10 Jan 2006
SubSys/straw1 dist_1:CAEN/crate01/board10/channel001 10 Jan 2006
SubSys/straw2 dist_1:CAEN/crate01/board01/channel002 5 Jan 2006
SubSys/straw3 dist_1:CAEN/crate01/board01/channel003 5 Jan 2006
In this example, one can see that the SubSys/straw1 aparently had some problems: it was initially mapped to first channel of first board, then on 6th of January 2006, reconnected to eleventh channel of first board, then again, on 10th of January 2006 it was reconnected to first channel of tenth board, and stays as such since then. The other two straws were not touched and stay connected to channel 2 and 3 on first board...

void _fwConfigurationDB_saveItemsToDB ( dyn_dyn_mixed  deviceListObject,
string  hierarchyType,
dyn_string &  exceptionInfo 
)

Store items in DB (LOW LEVEL!)

All ID's for items already need to be there. The things it stores: item id, parent id, name, type, model (or detail of type), comment, dpid Only stores ITEMS-related part; logical mapping, configs, etc are stored elsewhere.

void fwConfigurationDB_getDeviceConfigurations ( string  hierarchyType,
dyn_string &  confNames,
dyn_string &  confDescriptions,
dyn_int &  confIds,
dyn_string &  exceptionInfo 
)

int _fwConfigurationDB_checkCreateDeviceConfiguration ( string  hierarchyType,
string  confName,
string  confDescription,
dyn_string &  exceptionInfo 
)

Returns:
the device configuration id (CONF_ID);

void _fwConfigurationDB_checkSaveDpTypes ( dyn_string  dpTypes,
dyn_int &  dpTypeIds,
dyn_mixed &  dpTypeElements,
dyn_mixed &  dpTypeElementIds,
time  date,
dyn_string &  exceptionInfo 
)

void _fwConfigurationDB_configureFwDevicesWithDefaults ( dyn_string  dps,
dyn_string  dptypes,
dyn_string  models,
dyn_string &  exceptionInfo 
)

void fwConfigurationDB_updateDeviceConfigurationFromDB ( string  configurationName,
string  hierarchyType,
dyn_string &  exceptionInfo,
time  validOn = 0,
dyn_string  deviceList = "",
string  systemName = "",
int  options = fwConfigurationDB_deviceConfig_ALLDEVPROPS 
)

void _fwConfigurationDB_configureDevicesFromDB ( dyn_string  dpes,
dyn_int  propIds,
dyn_string &  exceptionInfo,
int  options = fwConfigurationDB_deviceConfig_ALLDEVPROPS 
)

void _fwConfigurationDB_getIpropIdsInConfiguration ( string  configurationName,
dyn_string &  dpes,
dyn_int &  ipropIds,
dyn_string &  exceptionInfo 
)

void fwConfigurationDB_saveDeviceConfigurationInDB ( dyn_string  deviceList,
string  hierarchyType,
string  configurationName,
anytype  saveConfigs,
dyn_string &  exceptionInfo,
string  systemName = "",
string  confDescription = "" 
)

Saves the device configuration to the database

Parameters:
saveConfigs may either be of bool, or of int type; in the former case, passing FALSE means that only the minimal (hierarchy) information is stored; passing TRUE means all configs of the devices are stored. If the int-typed parameter is used it should contain the sum of options refering to the configs that should be stored: the deviceConfigsIndices constants should be used. To store no configs (i.e. only the minimal hierarchy information), one should pass 0; to store all properties one should pass the fwConfigurationDB_deviceConfig_ALLDEVPROPS constant.

void fwConfigurationDB_reconnectDevices ( dyn_string  deviceList,
string  configurationName,
string  hierarchyType,
string  targetSystem,
dyn_string &  exceptionInfo 
)

int fwConfigurationDB_saveDevicesToDBMinimal ( dyn_string &  deviceList,
dyn_string &  exceptionInfo,
bool  abortWhenDeviceMissing = FALSE 
)

Stores "minimal" information about the devices to DB

This function stores minimal information about devices into the DB, so that recipes for these devices may also be stored.

Parameters:
[in,out] deviceList - list of names of devices; may include a mixture of devices from the HARDWARE and LOGICAL hierarchies; on exit, it will contain the list of devices that were actually stored/verified, namely: the non-existing devices are removed from the list, and devices that are needed to satisfy the hierarchical constraints (parents, grandparents,...) are added to the list
[out] exceptionInfo - standard exception-handling parameter
[in] abortWhenDeviceMissing (optional, default FALSE) - if set to TRUE, the function will abort (and return an error) if some of specified devices does not exist, i.e. it will not store the good ones in the database; otherwise (the default behaviour), the missing devices will be skipped, the good ones will be stored in the database, and the return value of 1 will signify that there were missing devices.
Return values:
0 - everything OK: all devices are in DB now
1 - some devices in the deviceList do not exist, and were skipped; the list of them is in the exceptionInfo; apart from that, everything was OK
-1 - there was an error while storing the devices; details in the exceptionInfo
How to handle the return value and the exceptionInfo, when the abortWhenDeviceMissing parameter is FALSE. This example shows how to make sure that the recipeObject can be saved to DB. The devices that exist - are saved. For all devices that are missing, we post-process the recipeObject to remove the data for non-existing devices, then save the recipeObject to DB
    dyn_dyn_mixed recipeObject;
    // ... get the recipe into the recipeObject somehow...

    dyn_string deviceList=recipeObject[fwConfigurationDB_RO_DP_NAME];

    int rc=fwConfigurationDB_saveDevicesToDBMinimal(deviceList,exceptionInfo,FALSE);
    if (rc!=0) {
      // means something happen
      if (rc==-1) {
        fwExceptionHandling_display(exceptionInfo);
        // abort!
        return FALSE;
      } else if (rc==1) {
        // it is still OK, even though some of the devices were missing:
        // we choose not to display the exception, but only print a message to a log
        DebugN("There were some missing devices - the others were saved OK");
        // post-process the recipeObject, to remove the missing devices...
        // the good ones are returned in the (modified!) deviceList
        for (int i=1;i<=dynlen(recipeObject[fwConfigurationDB_RO_DP_NAME]);i++) {
          string dev=recipeObject[fwConfigurationDB_RO_DP_NAME][i];
          if (!dynContains(deviceList,dev)) {
            // remove the line from all data columns of the recipeObject
            for (int j=1;j<=fwConfigurationDB_RO_MAXIDX;j++) {
              dynRemove(recipeObject[j],i);
             }
             i--;//reset iterator
           }

         }
      }
    }

    // we could save the recipe into the DB now...
    fwConfigurationDB_saveRecipeToDB(recipeObject,"","MyTestRecipe",exceptionInfo);
    if (dynlen(exceptionInfo)){fwExceptionHandling_display(exceptionInfo);return;};

void fwConfigurationDB_updateDeviceModelsInDB ( dyn_string  dpList,
dyn_string &  exceptionInfo,
bool  updateAliases = TRUE 
)

Updates the device models in the database to the current ones

Parameters:
dpList the list of datapoint names, for which the model is to be changed. Note that if the datapoin
exceptionInfo standard framework exception-handling variable
updateAliases (optional, default TRUE), determines if the models for LOGICAL devices which correspond to the specified datapoints should also be updated.
Note:
: Use with care and cautiously, of what the implications could be! To be used from the dedicated device-conversion panels, such as the ones for the fwWiener component.


Variable Documentation

global string _fwConfigurationDB_fileVersion_fwConfigurationDB_Hierarchies_ctl = "3.4.0"

const int fwConfigurationDB_deviceConfig_VALUE = 1

const int fwConfigurationDB_deviceConfig_ADDRESS = 2

const int fwConfigurationDB_deviceConfig_ALERT = 4

const int fwConfigurationDB_deviceConfig_ARCHIVING = 8

const int fwConfigurationDB_deviceConfig_DPFUNCTION = 16

const int fwConfigurationDB_deviceConfig_CONVERSION = 32

const int fwConfigurationDB_deviceConfig_PVRANGE = 64

const int fwConfigurationDB_deviceConfig_SMOOTHING = 128

const int fwConfigurationDB_deviceConfig_UNITANDFORMAT = 256

const int fwConfigurationDB_deviceConfig_ALLDEVPROPS = 511

const int fwConfigurationDB_deviceConfig_VALUE_ADDR_IN = 512

const int fwConfigurationDB_deviceConfig_VALUE_ADDR_OUT = 1024

const int fwConfigurationDB_deviceConfig_FW_DEFAULTS = 32768

const int fwConfigurationDB_DLO_DPNAME = 1

const int fwConfigurationDB_DLO_DPTYPE = 2

const int fwConfigurationDB_DLO_NAME = 3

fwConfigurationDB_DLO_MODEL = 5

contains model name for framework devices, "DATAPOINT" if this is a non-framework data point, "SYSTEM" if this is a top-node of hierarchy

const int fwConfigurationDB_DLO_COMMENT = 6

const int fwConfigurationDB_DLO_ITEMID = 7

const int fwConfigurationDB_DLO_PARENTID = 8

const int fwConfigurationDB_DLO_DPID = 9

const int fwConfigurationDB_DLO_REFDP = 10

const int fwConfigurationDB_DLO_REFID = 11

const int fwConfigurationDB_DLO_REF_STATUS = 12

const int fwConfigurationDB_DLO_PROPIDS = 13

const int fwConfigurationDB_DLO_PROPNAMES = 14

const int fwConfigurationDB_DLO_CITEM_ID = 15

const int fwConfigurationDB_DLO_MAX_IDX = 15


Generated on Thu May 14 12:06:04 2009 for Configuration Database component by  doxygen 1.4.7