The import function in the Cloud Logging configurator is, together with the export function, built to easily and effortlessly copy triggers from one device to another. Additionally, you can use the import function to prepare triggers in a CSV file and load them all at once into your cloud logger.
This article explains the structure of the CSV file and the syntax of the corresponding settings. Despite the fact that every protocol is structured in it’s own way (i.e. Siemens S7 works with Data Blocks and OPC-UA doesn’t) a uniform file structure is applied for all protocols.
CSV file structure
The structure of the CSV file needs to be correct for the import function to work properly. The headers (first row) of column 1-5 should look like this:
Each column represents a different setting and these are all explained below. You can easily navigate to the desired section by pressing the corresponding header above.
You can name the triggers freely. It is advised to enter a very brief description of the variable (i.e. error state, temperature too high, emergency stop zone B).
Here you enter the address corresponding with the variable you’d like to use as trigger. For example, when using Modbus and the variable is a holding register with address 7, you enter a 7 here. If you’re unsure you can best export an existing trigger first.
A trigger happens if the outcome of <variable><condition><threshold> is true. For example, if variable “Temperature” is “greater than or equal to” “60” degrees celsius.
The available options for the condition are:
|Online (X4 remote)||Offline (CSV file)|
|Not equal to||!=|
|Less than or equal to||<=|
|Greater than or equal to||>=|
The threshold is the last part of the equation that determines if a trigger happens or not. The available options depend on the variable’s data type. For example, if the variable’s data type is boolean, then you can choose either TRUE or FALSE.
In addition to the trigger name, you can add a full description of the trigger here.