Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Generate User-Defined Trace Event Function

LabVIEW 2013 Desktop Execution Trace Toolkit Help

Edition Date: June 2013

Part Number: 372641C-01

»View Product Info
Download Help (Windows Only)

Owning Palette: Desktop Execution Trace Toolkit Function

Requires: Desktop Execution Trace Toolkit (Windows)

Generates an execution event that the Desktop Execution Trace Toolkit can capture. If you trace an application that includes this function, a User Defined event appears on the table pane when this function executes, and the values you wire to the trace string and trace integer inputs appear in the Details column.

Details  

trace string is a string that appears in the Details column of the table pane in the Desktop Execution Trace Toolkit. You can use trace string to define the event this function captures. trace string cannot exceed 255 characters.
trace integer is an integer that appears in the Details column of the table pane in the Desktop Execution Trace Toolkit. If you use multiple Generate User-Defined Trace Event functions in an application, you can use this input to identify events that occur in specific parts of the application. For example, you can assign a trace integer of 1 to any event that occurs in parts of the application that acquire data, a trace integer of 2 to any event that occurs in parts of the application that write data to files, and so on.

Generate User-Defined Trace Event Details

For example, if you trace an application that writes a string to a file, you can wire the string to the trace string input to display the string in the Details column of the table pane.

Refer to the LabVIEW Desktop Execution Trace Toolkit for Windows Help, accessible from the toolkit by selecting File»Help»Launch Help, for more information about trace sessions, events, and the Desktop Execution Trace Toolkit.


 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit