CAN Clear with NI-DAQ.vi
Purpose
Stop and clear the CAN task and the NI-DAQ task synchronized with CAN Sync Start with NI-DAQ.vi.
Format
Inputs
 | task reference in is the NI-CAN task reference you passed through the CAN Sync Start with NI-DAQ VI. |
 | If you wire the same RTSI terminal that you passed into CAN Sync Start with NI-DAQ.vi, this VI clears the routing in NI-DAQ. If you leave RTSI terminal unwired, the VI retains the routing in NI-DAQ. This VI always clears RTSI routing for NI-CAN. |
| NI-DAQ task ID is the same NI-DAQ task ID you wired into the CAN Sync Start with NI-DAQ VI. |
 | Error in describes error conditions occurring before the VI executes. If an error has already occurred, the VI returns the value of the Error in cluster in Error out.
 | status is True if an error occurred. If status is True, the VI does not perform any operations. |
 | code is the error code number identifying an error. A value of 0 means success. A negative value means error: VI did not execute the intended operation. A positive value means warning: VI executed intended operation, but an informational warning is returned. For a description of the code, wire the error cluster to a LabVIEW error-handling VI, such as the Simple Error Handler. |
 | source identifies the VI where the error occurred. |
|
Outputs
| Error out describes error conditions. If the Error in cluster indicated an error, the Error out cluster contains the same information. Otherwise, Error out describes the error status of this VI.
| status is True if an error occurred. |
| code is the error code number identifying an error. A value of 0 means success. A negative value means error: VI did not execute the intended operation. A positive value means warning: VI executed intended operation, but an informational warning is returned. For a description of the code, wire the error cluster to a LabVIEW error-handling VI, such as the Simple Error Handler. |
| source identifies the VI where the error occurred. |
|
Description
This VI is intended to serve as an example. You can use the VI as is, but the LabVIEW diagram is commented so that you can use the VI as a starting point for more complex synchronization scenarios. Before you customize the LabVIEW diagram, save a copy of the VI for editing.