Code version 2.1

Task:

A separate task is created for the analytics analysis.

StreamHelper:

If one or more data sources are of type MQTT binary stream, the code generation creates an instance of a StreamHelper object to process the incoming binary stream patterns.

DataTypes:

The data types are created for the analysis. They contain STRUCTs for the reset function or result processing and ENUMs to select the various components.

HMI GVL:

To conveniently map module inputs and outputs with the HMI dashboard, selected variables are generated as global variables.

DataSource/M2M Mapping:

The FB DataSource manages the receipt of input values from the various sources. In the OUTPUT declaration you will find all configured inputs. The FB ValueMapping_M2M manages the value mapping between the modules (M2M - Module to Module) from the module INPUTs to the module OUTPUTs.

Network:

All modules are sorted in a specific network to achieve a better overview and structure of the configured analysis.

Modules:

The module FBs contain all inputs and outputs of the configured modules from the workbench configurator. It is also possible to reconfigure the modules during runtime. To do this, simply change the parameter and then start the reconfiguration process with a rising edge at INPUT bReconfigure.

Results:

If analysis results need to be saved or streamed, the FB Results manages this and streams the selected variables to the message broker or saves the data to the Analytics binary file.

Analysis:

The entire analysis routine is defined in the FB Analysis. All configured networks with their modules and error handling are created.

MAIN:

The FB Analysis is called in the program MAIN_Analytics. The program is assigned to the separate task.

It is also possible to reset single modules, whole networks or all defined networks with only one rising flag. First, select the component to be reset. Then a rising edge at INPUT bReset starts the reset process.

All reset calls are defined in the action A_Reset.