Table Of Contents

XNET Convert (Signal to Frame » LIN) (G Dataflow)

Last Modified: November 2, 2017

Converts between NI-XNET signals and LIN frame data.

connector_pane_image
datatype_icon

session in

The session to read. This session is returned from XNET Create Session. The session mode must be Conversion.

datatype_icon

signal data

An input that returns a one-dimensional array of signal values. Each signal value is scaled, 64-bit floating point. Each array element corresponds to a signal configured for the session. The order of signals in the array corresponds to the order in the session list.

The data provides the value for the next conversion of each signal.

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

session out

An output that is the same as session in, provided for use with subsequent nodes.

datatype_icon

unused payloads

This parameter is empty. No user input is needed.

datatype_icon

frame data

Returns the array of LabVIEW clusters. Each array element corresponds to a frame the session converted.

The elements of each cluster are specific to the LIN protocol.

datatype_icon

identifier

The identifier received within the frame's header. The identifier is a number from 0 to 63.

If the schedule entry (slot) is unconditional or sporadic, this identifies the payload data (LIN frame). If the schedule entry is event triggered, this identifies the schedule entry itself, and the protected ID contained in the first payload byte identifies the payload.

datatype_icon

event slot?

This element is not used. This element is false.

datatype_icon

event ID

This element is not used. This element is 0.

datatype_icon

echo?

A Boolean value that determines whether the frame was an echo of a successful transmit (true), or received from the network (false). For conversion, it is always set to false.

datatype_icon

type

The frame type.The decimal value is in parentheses.

LIN Data (64) The LIN data frame contains payload data. This is currently the only frame type for LIN.

For conversion, this is always set to false.

datatype_icon

timestamp

An element that represents the absolute time when the XNET interface received the frame (end of frame), accurate to microseconds. The timestamp returned by the conversion is always invalid (0).

datatype_icon

payload

The array of data bytes for the LIN data frame. The array size indicates the received frame’s payload length.

According to the LIN protocol, this payload is 0-8 bytes in length.

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: Supported

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


Recently Viewed Topics