dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference, User Interfacedl-breadcrumb-item__separatorMenu Commandsdl-breadcrumb-item__separatorMenu 'Trace'dl-breadcrumb-item__separatorCommand 'Export Symbolic Trace Config'
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command 'Export Symbolic Trace Config'dl-permalink__symbolPermalink

Function: This command exports a trace configuration to a ‎traceconfig‎ file.

Call: Main menu “Trace”, or context menu.

Requirement: The origin application includes a symbol configuration that defines the configured trace variables as symbols. Access to the IEC variables where data was recorded is therefore symbolic. Then you can use the trace configuration for various similar applications.

Using the configuration file

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

The configuration file defines the following context:

  • Application name

  • Trace name

  • Task name

The application that is executed at runtime must fulfill the following conditions:

  • The application has the same name as the origin application.

  • The trace that is configured in the application has the same as the trace that is configured in the origin application

  • The task that is running in the data recording has the same name as the task that is configured in the origin application.

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

The configuration is not loaded automatically. You must execute the command explicitly.

You can proceed as follows:

  • Access the trace manager programmatically via IEC code by using library interfaces.

  • Register the configuration file with the trace manager. Then the trace manager loads the configuration file when the application is started.

For more information about the functionality of the trace manager, refer to "Trace Manager Runtime System Component Description".

Sample configuration file

Configuration file ‎Trace_Trigger.traceconfig‎

[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;