BMX EIA 0100 Module Diagnostics

Communication Interruptions

Communication interruptions between the CPU and BMX EIA 0100 module are caused by the following:

Triggering of the processor watchdog if the BMX EIA 0100 is positioned in the rack holding the processor.
Disconnection of the X Bus cable if the BMX EIA 0100 module is positioned in an extension rack.
Removal of the BMX EIA 0100 power supply
Inoperative CPU

For these types of interruptions, the BMX EIA 0100 enters the OFFLINE mode and the CPU stops communication with the BMX EIA 0100.

NOTE: If the problem is on the X Bus, the CPU also indicates a detected error on the X Bus.

For a communication interruption between the BMX EIA 0100 and the AS-Interface bus, before shutting down the BMX EIA 0100 stops communication with the CPU and tries to switch to the OFFLINE Mode (if it has time). Refer to AS-Interface Power Interruptions and Break in the AS-Interface Medium.

AS-Interface Power Interruptions

If the AS-Interface bus power is interrupted, then:

The BMX EIA 0100 switches to the OFFLINE Mode
Communication with all the slaves is interrupted.

The BMX EIA 0100 indicates the error by turning off the front panel green ASI PWR LED and turning on the red FAULT LED.

The CPU indicates that all slaves values are invalid.

In the CPU memory image:

Digital input values are set to 0
For Analog slaves that adhere the AS-Interface Complete Specification standard, the values are 7FFF hex.

Break in the AS-Interface Medium

There are several places where break in the medium can occur:

After the BMX EIA 0100 module, but before the AS-Interface power supply. The behavior is the same as AS-Interface Power Interruptions. The BMX EIA 0100 does not “see” the power supply.
The break is after the BMX EIA 0100 and the AS-Interface power supply. All slaves disappear from the front panel, but the BMX EIA 0100 does not report a power supply interruption because it still “sees” the power supply.
The break is after the module and after one or more of the slaves. The slaves located after the break disappear from the front panel. No power supply error is reported.

Slave Disappearance

When a slave is removed (or quits functioning) from an active AS-Interface bus without changing the LPS (List of Projected Slaves, configured slaves), then from the point of view of the BMX EIA 0100 bus master, the slave disappears because the module is no longer able to exchange data with the slave. The BMX EIA 0100 then:

Deletes the slave (address) from the LDS (List of Detected Slaves) and LAS (List of Active Slaves)
Adds these slaves to the LFS (List of Fault Slaves) and CDI (Configuration Data Image).

The detected configuration error is reported to the CPU using the Config_OK flag.

The CPU, in the case of a slave disappearance, indicates that:

Value read from the slave is invalid
A detected configuration error is reported to the CPU using the Config_OK flag:
- For a Digital input slave, its value is set to 0.
- For an Analog input slave that adheres the AS-Interface Complete Specification standard, its value is set to 7FFF hex.

Incorrect Configuration

There are 3 slave configuration errors that can be detected by the BMX EIA 0100:

A slave is detected but not projected, i.e., not in the configuration downloaded from the processor
A slave is projected but not detected, i.e., an expected slave is not detected
A Slave is projected and detected, but the configured profile is not the same as that of detected profile

A detected configuration error is reported to the CPU using the Config_OK flag and is indicated in the Module Fault tab of the channel diagnostic window.