dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separatorApplication at Runtime dl-breadcrumb-item__separatorData Recording with Tracedl-breadcrumb-item__separatorAccessing All Traces on the Controller
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Accessing All Traces on the Controller dl-permalink__symbolPermalink

If the controller supports the runtime component ‎CmpTraceMgr‎ (Trace Manager), then you can access all traces from a CODESYS project which are running on the controller. In addition to application-related traces that capture the values of IEC variables, these can also be strictly controller-specific traces (for example, for recording device signal values or the CPU load).

For each trace running on the controller that you want to present in your project, you have to insert an individual “DeviceTrace” object in the device tree.

In order to show a trace from the device in this object, the connection to the PLC has to be configured correctly (“Communication Settings”). Then use one of the following menu commands:

  • “Trace  Upload Trace”: Establishes the connection to the PLC and opens the “Online List” dialog for selecting a trace from the controller

  • “Trace  Online List”: Available in online mode only; also opens the “Online List” dialog

Now the trace uploaded from the controller can be started and traced in the editor of the DeviceTrace object. The configuration of the presentation (colors, labels, etc.) is the same as with traces for application variables configured in the project.

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

Closing the DeviceTrace editor terminates the connection to the controller.

Note that the connection to the controller is also terminated when the last open “DeviceTrace” editor is closed. In order for device traces to be displayed again in the project, you have to reload them into the “DeviceTrace” objects.

Currently, closing the editor is also the recommended way to deliberately terminate the connection to the controller. Logging out is not enough for this.

  • Displaying the CPU load with DeviceTrace objects in the CODESYS project (example)