Reads the state of J1939 communication using an XNET session.


icon

Inputs/Outputs

  • cgenclassrntag.png session in —

    session in is the session to read. This session is selected from the LabVIEW project or returned from the XNET Create Session VI. The session must use a LIN interface.

  • cerrcodeclst.png error in (no error) —

    The error in cluster can accept error information wired from VIs previously called. Use this information to decide if any functionality should be bypassed in the event of errors from other VIs. The pop-up option Explain Error (or Explain Warning) gives more information about the error displayed.

  • igenclassrntag.png session out —

    session out is the same as session in, provided for use with subsequent VIs.

  • icclst.png J1939 comm —

    J1939 comm returns a LabVIEW cluster containing the communication elements. The elements are:

  • ii32.png fault code —

    fault? indicates that a fault occurred, and its code is available as fault code.

  • ibool.png fault? —

    fault? indicates that a fault occurred, and its code is available as fault code.

  • iu32.png PGN —

    PGN specifies the J1939 PGN that occurred the last error. You cannot assign a PGN to every error.

  • iu8.png src addr —

  • iu8.png dest addr —

    dest addr specifies the destination address that occurred the last error. You cannot assign a destination address to every error or warning.

  • ibool.png transmit error —

    transmit error indicates a transmit-related error occurred.

  • ibool.png receive error —

    receive error indicates a receive-related error occurred.

  • ierrcodeclst.png error out —

    The error out cluster passes error or warning information out of a VI to be used by other VIs. The pop-up option Explain Error (or Explain Warning) gives more information about the error displayed.

    • Description

    You can use the XNET Read (State SAE J1939 Comm) VI with any XNET session mode, as long as the session interface is CAN. Because the state reflects the CAN interface, it can apply to multiple sessions.

    Your application can use the XNET Read (State SAE J1939 Comm) VI to check for problems on the J1939 network independently from other aspects of your application. For example, you intentionally may introduce noise into the CAN cables to test how your ECU behaves under these conditions. When you do this, you do not want the error out of NI-XNET VIs to return errors, because this may cause your application to stop. Your application can use the XNET Read (State SAE J1939 Comm) VI to read the J1939 network state quickly as data, so it does not introduce errors into the flow of your LabVIEW VIs.