Codabix Web Configuration

A Folder Node can also be referred to as a root node, since it may provide additional Folder or Datapoint Nodes but it itself may may not provide any value.
Set properties are automatically applied to the Child Nodes, except when they define a separate condition.

A Datapoint Node in Codabix is like a variable with additional attributes (properties).
A Datapoint Node must not contain Child Nodes.

Link Nodes have only the properties they have in common.
A Link Node points to another Node that has already been created. This way it is possible to be assemble an individual record from several devices, Folder and Datapoint Nodes.

The Directory Node is a Folder Node that directly points to a physical directory and automatically represents the substructure.

When creating a Folder Node you can decide between the types:

• Folder
• Directory

Type: Folder
The Node is a regular Folder Node with no further special properties.

Type: Directory
The Node is a Folder Node an represents a physical registry in the data system. The Path property of the Node states the registry path (it can contain environmental variables). When browsing Nodes (e.g. via the web configuration) subdirectories are automatically created and aligned in the path property as corresponding Folder Nodes(type directory) and Datapaint Nodes (type file) with the related file path.

Note: On Windows 10 Version 1511 and older (and Windows Server 2012 R2 and older), e.g. on Windows 7, the maximum file path length is limited to 260 characters (MAX_PATH). On Windows 10 Version 1607 and higher (as well as Windows Server 2016 and higher) longer path names can be used. However, for this you will need to enable the setting “Enable Win32 long paths” in the Windows Group Policy, see Enabling Win32 Long Path Support.

Additionally to the previously mentioned properties the Datapoint Node has the following properties:

Note:

• To determine if a captured history value differs from the last history value (for the setting Yes; only on Value Change) only properties Value and Status are considered, but not property Timestamp (CreationTimestamp).
• When the History Options of a node are changed from No to Yes; only on Value Change while Codabix is running, the first captured history value after this change will be written to the database in every case, even when it is not different from the last written history value for that node.
• When the History Options of a node are set to Yes; only on Value Change and Codabix is shut down and later restarted, the first captured history value of the node after the restart will be written into the database in every case, even when it is not different from the last written history value for that node.
• When the History Options of a node are set to Yes; only on Value Change (or no History Interval is specified), the Creation Timestamp of the actual value will be kept when capturing the history value; otherwise, the Creation Timestamp will be set to the current time.
• In a Script, the setting Yes; only on Value Change corresponds to the value codabix.NodeHistoryOptions.Subscription | codabix.NodeHistoryOptions.ValueChange (contains codabix.NodeHistoryOptions.Active), and the setting Yes corresponds to the value codabix.NodeHistoryOptions.Subscription (contains codabix.NodeHistoryOptions.Active)
• History Values are inserted into the database asynchronously in the background by the History Value Dispatcher. This means that when you write a value to a node (where no History Interval is set), even though the write operation finished, the captured history value might not yet be in the database. This is especially true if you set the DB Update Mode to Restricted in the Codabix Settings, because captured history values are then inserted into the database only every 5 seconds.

• Enter name e.g. Press
• Enter display name e.g. Press
• Node type: select “Folder”
• when appropriate set intervals
• create a Node with

• enter name e.g. DirectoryR_MData
• enter display name e.g. machine data
• path: enter directory path e.g. R:\\MachineData
• when appropriate set intervals
• create a Node with

In order for you to be shown folders and files you have to refresh the view, e.g. by clicking “User” and then clicking “Nodes”. Depending on the directory size it is possible that you will not see all files and subdirectories at once.

• enter name e.g. Pressure (bar)
• enter display name e.g. Pressure (bar)
• select value type e.g. Single
• when appropriate enter boundaries, scales, historical data (as e.g. Min Value = 20,5, Scaling Factor = 2,398 …)
• create a Node with

The Node could look like this:

If a Folder Node is selected, automatically all the Nodes lying underneath inherit the selected user group.
The user group is not displayed in the underlying nodes, if you click .
Thus, you have the option to explicitly set the user group to a specific Folder or Datapoint Node, if for example, the Parent Node looses access.

All previously selected Folder and Datapoint Nodes are displayed by hooks. When you select a Folder Node, all nodes below will be automatically selected or deselected.

All device plugins are using the Codabix Device Model. Each device that is provided is registered and managed by the Codabix Device Manager.

S7Device
Connection to Siemens SIMATIC S7.

All Exchange Plugins are using the Codabix Storage Model. Each Exchange Plugin that is provided is registered and managed by the Codabix Device Manager.

Database
Codabix supports connections to databases.

CSV

Codabix contains an API interface.

REST
The REST interface allows access to the Node Codabix via HTTP request formatted as a JSON object.

Scipt Plugins
Script plugins extend Codabix with additional functionalities via JavaScript editor. They are executed in a secure environment.

OPC UA Server Interface
Codabix contains an OPC UA Server for the exchange of data.