Can BM Monitor BC-RT MIL-STD-1553 Error Injection When BC, RT, and BM Are Configured on the Same Channel of a Ballard MF Card?

Updated Aug 7, 2026

Reported In

Hardware

  • PXI MIL-STD-1553 Interface Module

Driver

  • Astronics Ballard Avionics Driver

Issue Details

A customer is using a Ballard MF card in a LabVIEW environment and has configured BC (Bus Controller), RT (Remote Terminal), and BM (Bus Monitor) on the same channel. The customer would like to perform MIL-STD-1553 error injection on BC-RT communications and monitor the results using BM. If BC, RT, and BM are running on the same channel and the same core, can BM detect and monitor the injected errors? What is the recommended configuration for demonstrating and validating MIL-STD-1553 error injection?

Solution

When BC, RT, and BM are run on the same core, the BM does not operate as an independent hardware Bus Monitor. Instead, it functions as a simulated BM. In this configuration, the BM is not a true listener on the bus and therefore cannot fully monitor or validate BC-RT communications and injected MIL-STD-1553 errors as an independent Bus Monitor would. To properly monitor and validate MIL-STD-1553 error injection in BC-RT communications, the BM must be configured on a separate core and operate as an Independent BM.

For example, when a Sync Error is injected into an active DWD during BC-RT communication running on Core 1, the BM running on the same core does not report the error. However, an Independent BM running on Core 0 successfully detects and reports a Wrong Sync Error.