TwinCAT Analytics Binary File
TwinCAT Analytics Binary File is a TwinCAT-specific Storage. Therefore no external software is necessary. You can use this type of storage directly after installing the Analytics Storage Provider. This is the same file that the TwinCAT Analytics Logger provides in its “offline” configuration without MQTT Message Broker.
Storage Name:
Assign a descriptive name that describes the purpose of the storage well. It will reappear in various places during configuration in the Manager.
Max Write Length:
The amount of data that is written to the .tay file in one call is specified here.
Storage Comment:
You can enter additional information about the storage here.
File Path:
For the configuration, you must select your preferred folder on the local device on which the Storage Provider is running.
The folder used is displayed in the Connection String window for confirmation.
The folder architecture that is created after the pipeline is started is currently divided into five hierarchical levels:
- System ID (this is a GUID of the system sending the data) - can be replaced by the alias name in the Analytics Logger settings or in local engineering by the Machine Administration Page.
- Recording name - can be set using the configurator.
- Record name - can be set by the configurator and automatically influenced with auto IDs, date, cycle time and other placeholders at runtime.
- Internal ID - cannot be changed.
- Layout GUID - cannot be changed and corresponds to the data storage of the Analytics Logger.
Max Duration:
This value specifies in seconds how much data is written to a .tay file. After time X, the data is written to a new .tay file. Ring buffers that are configured in the Manager only affect complete .tay files of a current recording.