FlexRay Interface and Database Settings

Use this dialog to set the measurement setup interface-related properties and filtering options and assign a database to a measurement setup.

Interface Settings

  • FlexRay Interface—Use this control to assign an interface name on which the measurement should run. The interface name identifies the physical port within NI-XNET APIs.
  • Run Mode—Use this control to select whether to use the interface in Normal mode (the NI-XNET measurement session occupies the interface) or Subordinate mode (any LabVIEW application that uses the interface is responsible for starting and stopping it).
  • Log Transmitted Frames—Use this control when Run Mode is set to Subordinate to display and log frames transmitted from the same interface. Echoed frames are received only after the frame transmit is complete. If there are bus problems (for example, no listener) such that the frame did not transmit, the frame is not received.
  • Termination—Use Termination to control the selected NI-XNET interface termination. If you select this control, a termination is used.
  • Show Null frames—Select this control to use the received null frames for display.
  • Coldstart—If you select this control, the defined startup frame is transmitted to synchronize the interface to another cold start node in a FlexRay network.
  • Startup Frame—Use this control to set the start frame ID. For details about the cold start sequence and startup frame, refer to the NI-XNET Hardware and Software Help at Start»Programs»National Instruments»NI-XNET»NI-XNET Documentation»NI-XNET Manual.chm.
  • Exclude IDs—If you select this control, the selected IDs in the Filter IDs control are excluded from being displayed, analyzed, and logged.
  • Filter IDs—Use this control to add a list of filter identifiers for a software filter mask. Only the IDs listed here are available for display, analyzing, and logging. Filter mask list examples:
    1–10 Filter out IDs 1–10
    1–10,233,401–402 Filter out ID 1–10, 233, and 401–402

Database Settings

  • Alias Name—For FlexRay, you must assign an alias name or filename to a database, as the database contains all relevant interface properties. Select an alias name from the drop-down list.
  • Alias—NI-XNET uses alias names for database files. Click this button to view, add, or remove existing alias names.
  • Cluster Name—If the database contains several clusters, you must select the cluster name from the drop-down list.

FlexRay Communication Notes

A FlexRay network always must have two cold start nodes, which initialize the FlexRay communication. All other nodes must synchronize with the cold start nodes. There are several ways to use the Bus Monitor with cold start nodes on a FlexRay network:

  • The two cold start nodes have already started the network. If two cold start-capable nodes (ECUs) have already started the network, the Bus Monitor can sync with the running network. In this case, clear the Coldstart flag and do not select a startup frame.
  • The network contains only one cold start node. If the network has only one cold start-capable node (ECU), the Bus Monitor can initiate the cold start procedure and sync all other nodes with the network communication. In this case, set the Coldstart flag within the Bus Monitor to be used and assign a valid startup frame. If no startup frame appears in the drop-down list, use the Database Editor to add a valid cold start frame onto the selected FIBEX file alias cluster. To initiate the cold start by a LabVIEW application, for example, you can monitor the same port with the Bus Monitor by selecting the subordinate mode. In subordinate mode, the Bus Monitor is launched in a passive mode in which only the received data frames are displayed; the main application processes the NI-XNET interface initialization/start/stop. While the main application is started, the Bus Monitor receives the incoming frame data; when the main application is stopped, the Bus Monitor receives no data.
  • The network does not contain a cold start node. If the network has no cold start-capable node (ECU), two NI-XNET device FlexRay ports, for example, must perform the cold start initialization. For example, you can use any NI-XNET example and select to use a cold start frame on port A. On the second port, either use another example that uses a startup frame for cold start, or if using only the Bus Monitor, use the startup frame within the Bus Monitor. Select the Coldstart flag and assign a valid startup frame. If no startup frame appears in the drop-down list, use the Database Editor to add a valid cold start frame onto the selected FIBEX file alias cluster.