Basic concept
The following figure shows the basic concept of TwinCAT Analytics from the data source to the Analytics Dashboard based on TwinCAT 3 HMI. The communication in an Analytics scene is realized by the IoT communication protocol MQTT.
Data sources:
Currently there are three different data sources for TwinCAT Analytics. All these sources can communicate with the specific binary data format of TwinCAT Analytics. This format is necessary to achieve high performance.
- TwinCAT 3 control with TF3500 TwinCAT Analytics Logger
- TwinCAT 2, TwinCAT 3 and external control together with a gateway of the TF6720 TwinCAT IoT Data Agent
- All EK9160 IoT Bus Coupler
Storage:
With TwinCAT Analytics it is possible to analyze live and historical data. The TwinCAT Analytics Storage Provider is the interface between native MQTT Message Broker to different stores. As storage TwinCAT Analytics is supporting an Azure Blob store and a Microsoft SQL database. The configuration of the stores is done automatically by the Storage Provider. Thus, it is not necessary to use classic SQL commandos to implement the communication. The user also does not need to setup a special table structure.
Analysis:
For service technicians and machine commissioning
The TE3520 TwinCAT Analytics Service Tool is the perfect tool for experts who like to analyze TwinCAT Analytics data sources. It is integrated into the Microsoft Visual Studio®. The user is able to make his analytics configuration in a graphical configurator choosing from a wide pool of different algorithms. A parallel interaction with the Scope View is also possible. The user is able to find significant values easily by drag and drop from the configurator into the data stream of our Scope View.
For continues 24/7 machine analysis
The TE3500 TwinCAT Analytics Workbench has the same functionality as the Service Tool. In addition, it is possible to automatically generate a PLC code with associated HMI dashboard based on the realized analytics configuration in the configurator. The PLC code is ready to use, so you can start data analysis immediately as in the configurator. But now for 24 hours 7 days per week if necessary. The automatically generated code can be downloaded into the TF3550 TwinCAT Analytics Runtime. Alternatively, a download of the pure PLC project, when created without HMI dashboard, into the Analytics Runtime Base TF3551 (without HMI Server) is possible. Both runtime products are essentially license bundles and can run on a classic IPC or Embedded PC, but also in a virtual machine.
Products:
We have different single products in the TwinCAT Analytics Workflow. See therefore the following list with all products.
Product number | Product name |
|---|---|
TE3500 | Analytics Workbench |
TE3520 | Analytics Service Tool |
TF3500 | Analytics Logger |
TF3510 | Analytics Library |
TF3520 | Analytics Storage Provider |
TF3550 | Analytics Runtime - including HMI Server and Client Pack |
TF3551 | Analytics Runtime Base - without HMI |
TF3560 | Analytics Controller Pack 4 |
TF3561 | Analytics Controller Pack 8 |
TF3562 | Analytics Controller Pack 16 |
TF3563 | Analytics Controller Pack 32 |
TF3564 | Analytics Controller Pack 64 |
TF3565 | Analytics Controller Pack 128 |
TF6720 | IoT Data Agent |
EK9160 | IoT Coupler |
The TwinCAT Analytics Service Tool can be used as a kind of Scope ++ via an ADS channel. This is automatically the most sensible minimum configuration from the basic concept shown. The Analytics Logger can also be used to decouple data collection and analysis. It can store data locally on the machine computer. The data can be evaluated via the service tool. If you want to organize data storage centrally rather than decentrally, you can use the Analytics Storage Provider via MQTT. The data sources available here are TF3500/TF6720/EK9160. Also possible is just to use the TF3510 Analytics Library in a TwinCAT system.