Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Location:


<WorkspaceDirectory>\DataFiles\nxaVirtualItems.40.dat


Virtual items are used like any other server item except for one detail; they are not connected to any real datapoint on bus level. They can be used to store data. They may be connected to a any other server item.
The structure of the virtual item definition file is as follows:


'Syntax of the Virtual Item Definition Table:

'ID;Path;Description;Data Type;Access Rights;Persistent;Historical;Synchronized;Link Item ID;Script For OnReceive; Script For OnSend;Script For OnSet
GlobalOff;BuildingA\Floor1\RoomA;Virtual Item for global off;BOOL;RW;;;;;;;;;;
Each line – except comment lines that start with ' – defines a single virtual item.

 

    
1ID This field is naming the virtual item. Together with the path it must be unique.
2Path The string within this field determines the path of the virtual item. Delimiter between sections of the path is the backslash (" ").
3Description Set the description for the virtual item here. It will be displayed in the item tree.
4Data Type Possible data types are BOOL, STRING, FLOAT, DOUBLE, INT8, UINT8, INT16, UINT16, INT32, UINT32, INT64, and UINT64.
5Access Rights Shall the virtual item be writable or is it read only?
6Persistent This parameter specifies whether the value of the virtual item is persistent (restored from the database after server start up ) or not.
7Historical This parameter specifies whether historical values of the virtual item are stored within the database or not.
8Synchronize If this parameter is set to "T", the value is synchronized between the main and backup server (if present). This will work only if synchronize is enabled in the NMESH configuration of the NETx BMS Core Server.
9Link Item ID If a connection to another item is necessary the item ID of this one has to be placed here.
10Script For OnReceive Implement any LUA script here which shall be called at the OnReceived event.
11Script For OnSend Implement any LUA script here which shall be called at the OnSent event.
12Script For OnSet Implement any LUA script here which shall be called at the OnSet event.
13Extended Data 1 Internal use only.
14Extended Data 1 Internal use only.
15Extended Data 1 Internal use only.
  • No labels