Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

#NameM/ODescrition
1NameMName of the virtual item. Together with the path it must be unique.
2PathOSpecifies the path of the virtual item. Delimiter between sections of the path is the backslash \.
3DescriptionODescription of the virtual item. It will be displayed in the item tree.
4Data TypeMPossible data types are BOOL, STR, BYTE, CHAR, INT8, UINT8, INT16, UINT16, INT32, UINT32, INT64, UINT64, FLOAT, DOUBLE, DATE, TIME.
5Access RightsO

Allowed operations on the virtual item:

  • RW: read-write (default)
  • R: read-only
  • W: write-only
6PersistentOSpecifies whether the value of the virtual item is persistent (restored from the database after server start up ) or not. Default is F (non-persistent).
7SynchronizeO

If set to "T", the value is synchronized between the main and backup server (if present). Default is F (no synchronization).

This applies only to main/backup configurations of the NETx Server.

8Link Item IDOIf a connection to another item is necessary the item ID of this one has to be placed here (bidirectional link between Virtual item and Linked item).
9Script For OnReceiveOImplement any LUA script here which shall be called at the OnReceived event.
10Script For OnSendOImplement any LUA script here which shall be called at the OnSent event.
11Script For OnSetOImplement any LUA script here which shall be called at the OnSet event.
12CommentOOptional comment of the virtual item definition. The value is only used for documentation purposes.

...