How to Start MC (Message Controller), RT (Remote Terminal) and BM (Bus Monitor) Separately in a LabVIEW VI?

This Knowledge Base article explains how to start MC (Message Controller), RT (Remote Terminal), and BM (Bus Monitor) as separate processes in a LabVIEW VI using the Astronics Ballard driver. These components are essential for MIL-STD-1553 communication and can be controlled independently based on your application needs.

Component Overview:

MC (Message Controller): Acts as the bus controller for MIL-STD-1553 communication.
RT (Remote Terminal): Responds to commands from the bus controller and simulates remote devices.
BM (Bus Monitor): Passively monitors bus traffic and logs messages for analysis.

In this article, we will:

• Describe the roles of MC, RT, and BM.
• Show how their start behavior works in LabVIEW.
• Provide test results and recommendations for configuration.

MC, RT, and BM can be started independently within the VI in the attachment. The Astronics Ballard LabVIEW driver allows these components to run as separate processes based on user configuration.

To test the VI with your MIL-STD-1553 card, you first need to identify the card number and core number using the BTI XML Editor.

BM passively monitors the traffic on the bus, including commands from MC to RT, responses from RT, and data transfers between BC and RT. In this VI, when RT is started, the communication data appears in the Record Out section because RT is actively participating in the communication.