Comm

Reads the time at which the session's interface completed its integration with the network cluster. This represents the time at which communication began.

1378

Inputs/Outputs

datatype_icon

session in

The session to read.

This session is selected from the LabVIEW project or returned from XNET Create Session.
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

Default value: No error

datatype_icon

session out

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

datatype_icon

time communicating

An output that returns the communication time of the interface as a LabVIEW absolute timestamp.

If the interface is not communicating when this read is called, time communicating returns an invalid time (0).
datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Description

You can use this XNET Read node with any XNET session mode. Because the time is associated with the interface, it can apply to multiple sessions.

This XNET Read node returns time as a LabVIEW absolute timestamp data type.

After your application starts the XNET interface hardware, the communication controller begins to integrate with ECUs in the network. The timestamp at which this integration starts is available using XNET Read (State Time Start). Once the XNET interface is fully integrated and communicating on the network (transmitting and receiving frames), this node captures and returns the time. For the CAN protocol, the time difference between Start and Communicating is very small. For the FlexRay protocol, the time difference can be many milliseconds due to factors such as clock synchronization and cycle length.