Table Of Contents

TraceTool Start Trace (G Dataflow)

Last Modified: July 1, 2018

Starts a trace session and logs VI and thread events from all VIs that begin executing after the TraceTool Start Trace node executes. You must ensure that you wire the TraceTool Start Trace node in sequence with all of the VIs that you want to log.

connector_pane_image
datatype_icon

detailed tracing?

Enables logging of analysis and custom events in the trace session. You must set the detailed tracing? input to TRUE to log analysis and custom events. The default is FALSE.

datatype_icon

buffer size

Defines the size of the memory buffer, in bytes, that logs all events from VIs in memory on the RT target. You must create an appropriately-sized memory buffer to capture all event data. You must not exceed the memory buffer size. Otherwise, the log file may become unusable because overflow may occur from multiple event sources and at different speeds.

spd-note-note
Note  

You cannot change the size of the memory buffer on the RT target after you run the TraceTool Start Trace node. You must reboot the RT target to resize the memory buffer.

datatype_icon

thread tracing?

Enables the logging of thread event data from the application running on the RT target. The default is TRUE.

datatype_icon

VI tracing?

Enables the logging of VI event data from the application running on the RT target. The default is TRUE.

datatype_icon

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

datatype_icon

actual buffer size

Actual size of the memory buffer, in bytes, allocated for event logging if the real-time operating system cannot allocate the requested buffer size.

datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Where This Node Can Run:

Desktop OS: Windows

FPGA: Not supported

Web Server: Not supported in VIs that run in a web application


Recently Viewed Topics