dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorApplication at Runtime dl-breadcrumb-item__separatorData Recording with Tracedl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorMenu commands dl-breadcrumb-item__separatorCommand: Upload Trace
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command: Upload Trace dl-permalink__symbolPermalink

Function: The command establishes the connection to the controller if it is not already connected. Then it opens the ⮫ Online List dialog where the traces which are running on the controller are listed. In the dialog, you then click the “Upload” command to load the selected trace to the trace editor.

Call: “Trace” menu; context menu of the trace editor

Requirement: The editor of a “DeviceTrace” object is open. The runtime system uses the ‎CmpTraceMgr‎ components (Trace Manager). At least one application in the runtime system in running. The communication settings for the controller are configured correctly in the CODESYS 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 need 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.

For more information, see: ⮫ “Accessing All Traces on the Controller ”