dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorObjects dl-breadcrumb-item__separatorObject: Device, and Generic Device Editor dl-breadcrumb-item__separatorTab: Licensed Software Metrics
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Tab: Licensed Software Metrics dl-permalink__symbolPermalink

A metric in this environment is the "value" (number) of units relevant to the license calculation. The units are called "tags". Depending on the product, these can be variables, axes, or I/O channels.

The tab of the device editor displays a tree structure containing the metrics which are available for the application. In this way, you can view the current measured values and check whether or not more code is downloaded to a controller than the license allows. The license is issued for each controller and is therefore located on the controller. The license check is also performed there.

The metrics are transferred to the controller during the download. They are refreshed when you click “Build  Generate Code” for the active application.

The following table shows the metric types of the Automation Builder. Add-on products such as CODESYS SoftMotion or CODESYS OPC UA have their own metrics, which are described in the "Licensing" chapter on the help page of the product.

“Read current metrics from device”

Gets and transfers the metrics from the controller and displays them in the “Value on Device” column.

“Metrics”

Metric types per application

“Value in Project”

Number of tags used in the development system. The value is measured during code generation (“Build  Generate Code” command).

For details about the calculation, see the ⮫ type conversion operator section.

Note: If you delete the compile information of the application, then the values will be reset to 0.

“Max. allowed by License”

Allowed maximum values for each application according to the license on the controller

“Value on Device”

Actual measured value, read from the controller

Note: To determine these values, the communication has to be working.

  • Calculation of the values