Command: Export symbolic tracing config

Function: The command exports a trace configuration to a *.traceconfig file.

Call: Trace menu; context menu

Requirement: The origin application includes a symbol configuration which defines the configured trace variables as symbols. Access to the IEC variables where data was sampled is therefore symbolic and allows for the use of the trace configuration for various similar applications.

Using the configuration file

You can transmit this file to any runtime system. At runtime, its CmpTraceMgr runtime component can access it and perform data sampling. The configuration file also includes information about the application context in addition to the configuration data.

. The configuration file defines the following context:

Name of the application
Name of the trace
Name of the task

. The application which is run at runtime has to fulfill the following conditions:

The application has the same name as the origin application.
The trace which is configured in the application has the same name as the trace which is configured in the origin application.
The task in which the data sampling is running has the same name as the task in which the origin application is configured.

Important

The configuration is not loaded automatically; you have to execute a command explicitly.

. You can proceed as follows:

You use library interfaces to programmatically access the Trace Manager via IEC code.
You register the configuration file with the Trace Manager. Then the Trace Manager loads the configuration file when the application is started.

Tip

For more information about the functionality of the Trace Manager, see "Trace Manager Runtime System Component Description".

Example of a configuration file

Example 3. Trace_Trigger.traceconfig configuration file

[key]; [value]
Version; 0x03050000
Name; Application.Trace_Trigger
ApplicationName; Application
ApplicationDataGuid; 00000000-0000-0000-0000-000000000000
IecTaskName; MainTask
Comment;
Trigger.Flags; 5
Trigger.Edge; 2
Trigger.Position; 0
Trigger.UpdatesAfterTrigger; 50
Trigger.Variable.Name; PLC_PRG.B.OUT
Trigger.Variable.AddrFlags; 0x00000101
Trigger.Variable.Class; 0
Trigger.Variable.Size; 1
Trigger.Level;
Condition.Name;
Condition.AddrFlags; 0x00000000
Condition.Class; 0
Condition.Size; 0
EveryNCycles; 1
BufferEntries; 100
Flags; 16
0.Variable; PLC_PRG.S5.OUT
0.Address.AddrFlags; 0x00000101
0.Class; 7
0.Size; 2
0.GraphColor; 4278190335
0.GraphType; 3
0.MinWarningColor; 4278190080
0.MaxWarningColor; 4294901760
0.CriticalLowerLimit; 0
0.CriticalUpperLimit; 0
0.ActivateMinWarning; 0
0.ActivateMaxWarning; 0
0.YAxis; 0
0.Data;
1.Variable; PLC_PRG.B.OUT
1.Address.AddrFlags; 0x00000101
1.Class; 0
1.Size; 1
1.GraphColor; 4278222848
1.GraphType; 1
1.MinWarningColor; 4278190080
1.MaxWarningColor; 4294901760
1.CriticalLowerLimit; 0
1.CriticalUpperLimit; 0
1.ActivateMinWarning; 0
1.ActivateMaxWarning; 0
1.YAxis; 0
1.Data;