Application Guide Volume II AG2018-24

Understanding and Effectively Using the

SEL MIRRORED BITS Protocol
Mark Diehl and Andrew Dulmage

INTRODUCTION
The SEL MIRRORED BITS® protocol is a secure and reliable serial protocol that transmits and
receives eight digital status bits between two SEL devices. This protocol is often used between
pairs of relays at each end of a transmission line to implement high-speed pilot line protection
schemes such as permissive overreaching transfer trip (POTT) or directional comparison blocking
(DCB) schemes [1]. It is also used in some substation automation schemes such as main-tie-main
or breaker failure schemes on distribution buses.
The purpose of this application guide is to explain the basic functionality of the MIRRORED BITS
protocol, explore the settings required to configure SEL relays to use the MIRRORED BITS protocol,
and discuss techniques and features that are used for the testing, troubleshooting, and commission-
ing of MIRRORED BITS schemes.

MIRRORED BITS DEFINITION

The MIRRORED BITS protocol copies, or “mirrors,” the status of eight bits between two relays over
a serial link, as shown in Figure 1. For each of the eight bits transmitted, an equation setting
assigns the desired bit in the relay to one of the eight bits that are being sent over that MIRRORED
BITS channel. This is known as the Transmit Mirrored Bit (TMB) equation. Each of the eight TMB
equations in Relay 1 can be programmed to contain any Relay Word bit or SELOGIC® control
equation by using the Transmit Mirrored Bit equation for that individual Mirrored Bit. The status
of this Relay Word bit or equation is mirrored to Relay 2, and is received in the form of the corre-
sponding Receive Mirrored Bit (RMB).
For example, the setting for TMB1 in Relay 1 might contain the breaker status bit (52A), which is
a logical 1 when closed and a logical 0 when open. Whenever the breaker changes states, the 52A
bit and TMB1 bit change as well in Relay 1. This bit is then sent to Relay 2, where it is represented
by RMB1 (the seven other TMBs similarly correspond to matching RMBs). When the channel is
healthy, RMB1 in Relay 2 will always have the same value as TMB1 in Relay 1. This means that if
the breaker at Relay 1 closes, RMB1 at Relay 2 should change from 0 to 1. This bit can then be
used in the logic equations of Relay 2.
At the same time, Relay 2 sends eight of its own TMBs to Relay 1. These messages are sent every
relay processing interval (4–8 times a power system cycle, depending on the relay). Traditional
communications protocols such as Distributed Network Protocol (DNP) or Modbus process too
slowly for protection applications. Because the MIRRORED BITS protocol processes quickly from
end to end, it is an ideal protocol to use for protection schemes, such as sending a transfer trip sig-
nal from one relay to another. For more information on MIRRORED BITS technology, see [1]. See
Figure 1 for a visual representation of how the MIRRORED BITS technology works.

Date Code 20180822 SEL Application Guide 2018-24

 2

0 1
TMB1 TMB1
0 0
TMB2 . . TMB2
Transmit . . . . Transmit
. . . .
. .
0 0
TMB8 TMB8

1 0
RMB1 RMB1
0 0
RMB2 . . RMB2
Receive . . . . Receive
. . . .
. .
0 0
RMB8 RMB8

Figure 1 MIRRORED BITS Protocol Data Exchange

There are two different MIRRORED BITS protocols, MB and MB8. To understand the small differ-
ence between these two protocols, one must first understand the general structure of the data being
exchanged. MB and MB8 communications messages consist of four characters (bytes). Each byte
is made up of a start bit, six data bits, one parity bit, and either one or two stop bits.
When MB was initially developed, traditional DB-9 serial cables directly connected the equip-
ment. This could also take the form of a fiber-optic link through the use of transceivers such as the
SEL-2800 Fiber-Optic Transceiver, SEL-2812 Fiber-Optic Transceiver With IRIG-B, or SEL-2830
Single-Mode Fiber-Optic Transceiver/Modem. Because of this dedicated communications chan-
nel, the total number of bits within a character was not especially important, so MB protocol only
includes one stop bit for a total of nine bits per character.
However, some communications channel equipment count bits and require a 10-bit character, so
the MB8 protocol was developed to meet this requirement by including two stop bits instead of one
for a total of ten bits per character. MB8 protocol should be used instead of MB when interfacing
with serial communications equipment, such as radios, multiplexers, or modems [2] [3]. You can
use MB8 protocol for all MIRRORED BITS applications to avoid confusion, because the traditional
direct serial connections support both MB and MB8.

RELAY MIRRORED BITS SETTINGS

As with other traditional protocols, such as Modbus and DNP3, configurable port settings must be
considered when using MIRRORED BITS communications between two relays. This section goes
through the various settings for MIRRORED BITS available in SEL equipment and what to consider
while setting them. This application guide uses ACSELERATOR Quickset® SEL-5030 Software to
configure Serial Port 3 of an SEL-351S Protection System Relay for the MIRRORED BITS protocol.

Proto (Protocol)
The first step is to set the protocol selection setting (PROTO) to MB8A for this port. This is shown
in Figure 2. Although previously this guide only referenced MB and MB8 protocols, Figure 2
shows MBA, MBB, MB8A, and MB8B as options for the PROTO setting. These are the same MB
and MB8 as previously described with an A or B appended. Most modern SEL relays support as
many as two MIRRORED BITS channels. The A and B designations allow the device to differentiate
locally between these two different MIRRORED BITS channels. For example, if Relay 1 needs one
MB8 connection to Relay 2 and a second connection to Relay 3, one serial port can be set to
MB8A and the other can be set to MB8B. Both are using the same protocol, but the relay needs to
distinguish which eight bits are going to Relay 2 and which are going to Relay 3. If the port con-
nected to Relay 2 is set to MB8A, then TMB1A–TMB8A are the bits sent to Relay 2, and

SEL Application Guide 2018-24 Date Code 20180822

 3

RMB1A–RMB8A are the bits received from Relay 2. Likewise, if the port connected to Relay 3 is
set to MB8B, TMB1B–TMB8B are the bits transmitted to Relay 3, and RMB1B–RMB8B are the
bits received from Relay 3. It is important to know that the A and B designations are not communi-
cated over the MIRRORED BITS channel, so the serial port on one device can be set as MB8A proto-
col and the serial port on the other device set as MB8B and they can still communicate. The A and
B designations are only important within the individual relay.

Figure 2 Configuring the Serial Port Protocol

The SEL-2505 Remote I/O Module and SEL-2506 Rack-Mounted Remote I/O Module are simple
to use products that incorporate MIRRORED BITS, and they are programmed using control (DIP)
switches. These products only support the SEL MB8 protocol. If one of these products is con-
nected to an SEL device, such as an SEL-451 Protection, Automation, and Bay Control System or
SEL-351 Protection System, then the relay should be set to use MB8 protocol to be compatible
with the SEL-2505 or SEL-2506.

Speed (Baud Rate)

Next, configure the baud rate, as shown in Figure 3. When you select MB8A as the protocol, most
of the communication parameters are fixed at specific values. In this example, the baud rate is
9600. In some applications, a higher baud rate may be used to improve latency. However, carefully
consider the appropriate data speed based on the cabling or connection type. Long copper serial
cables in a substation environment can be prone to induction or other noise that has more of an
impact at higher baud rates.
Table 1 lists the back-to-back, one-way data delay time incurred in SEL MIRRORED BITS commu-
nications devices, measured from the time a TMB is asserted in one device to the time the corre-
sponding RMB is received and processed in the other device. It is important to consider this delay
time when using this protocol for a protection scheme. The SEL-400 Series Relays have a
1/8-cycle processing interval and most other SEL relays have a 1/4 cycle processing interval.

Date Code 20180822 SEL Application Guide 2018-24

 4

Table 1 MIRRORED BITS Delay Times

Typical Data Delay of 1/8-Cycle Typical Data Delay of 1/4-Cycle

Baud Rate Processing Interval Devices Processing Interval Devices
(Maximum) (Maximum)
38400 4.2 ms (4.2 ms) 8.3 ms (8.3 ms)
19200 6.3 ms (6.3 ms) 10.5 ms (12.5 ms)
9600 8.3 ms (10.4 ms) 12.5 ms (12.5 ms)
4800 12.5 ms (18.7 ms) 16.7 ms (20.8 ms)

BITS (Data Bits) PARITY (Parity) and STOP (Stop Bits)

These settings are predetermined based on the PROTO setting and cannot be changed. Note that
the settings for Data Bits and Stop Bits have been automatically set to 6 and 2, respectively, with
odd parity. These are consistent with the MB8 message structure described previously. Alterna-
tively, if MB protocol is selected, the settings for Data Bits and Stop Bits will be fixed at 6 and 1,
respectively.
Figure 3 shows typical serial port settings that appear in SEL-300 and SEL-700 Series Relays. The
SEL-400 Series Relays are slightly different. The SEL-400 Series Relays do not have a setting for
MB8A protocol. To mimic the MB8A protocol, select PROTO = MBA (or MBB) and select
STOPBIT = 2.

Figure 3 Configuring Serial Port Communication Parameters

Enable Hardware Handshaking (RTSCTS)

Hardware handshaking is a method of flow control where the RTS and CTS pins are used to con-
trol the flow of traffic. It is not required for a MIRRORED BITS connection, so leave it set to the
default, N, which means it is disabled.

SEL Application Guide 2018-24 Date Code 20180822

 5

Transmission Mode (TXMODE)

This setting only appears in the SEL-400 Series Relays. If two SEL-400 Series Relays are commu-
nicating with each other, they can use MIRRORED BITS to communicate faster than other SEL hard-
ware platform products. If this is the case, TXMODE can be set to N for normal, which makes the
MIRRORED BITS link work as fast as possible. If an SEL-400 Series Relay must communicate with
another type of SEL product by using MIRRORED BITS, set TXMODE to P for paced mode for
compatibility.
There are some additional MIRRORED BITS settings associated with Serial Port 3, as shown in
Figure 4.

Figure 4 Configuring Serial Port MIRRORED BITS Parameters

MIRRORED BITS Channel Bad Pickup in Parts Per Million (CBADPU)

CBADPU and RBADPU are both threshold settings used to detect problems with the reliability of
the communications link. CBADPU is a setting used to identify a problem where the communica-
tions channel is periodically going into and out of service. The SEL product using MIRRORED BITS
tracks the number of messages missed, then compares this to the number of messages expected to
be received. The CBADPU setting adjusts this ratio of missed messages to total expected messages
with units of parts per million (PPM). The CBAD bit asserts when the result of the PPM ratio cal-
culation is above the value of the CBADPU setting. Adjust the CBADPU setting based on the reli-
ability of the communications channel being used. Table 2 shows examples of possible settings
based on the channel type.

Date Code 20180822 SEL Application Guide 2018-24

 6

Table 2 CBADPU Setting Based on Communications Channel

Expected MIRRORED BITS

Channel Type Typical Bit Error Rate CBAD Setting
Unavailability
Fiber Optic 10–12 0.002 ppm 10
–9
Digital Channel 10 0.2 ppm 100
Analog Channel 10–6 200 ppm 2000

MIRRORED BITS Channel Bad Pickup in Parts Per Million (RBADPU)

RBADPU is a setting used to identify a problem where the communications channel has experi-
enced an extended continuous dropout. The setting RBADPU establishes the number of seconds
the MIRRORED BITS channel is unavailable before the RBAD Relay Word bit asserts. This might be
caused by a serial port hardware failure or a failed communications channel, such as a broken fiber.
Because RBAD and CBAD are indicators for different types of communications failures, SEL rec-
ommends that you use RBAD and CBAD in conjunction to detect a failed or unstable MIRRORED
BITS channel. These Relay Word bits can be used as alarm points via an output or SCADA, or they
can be used in relay logic to safeguard against unwanted operation. In this example, RBADPU and
CBADPU are left at their default settings. MIRRORED BITS Application Example on page 8 expands
on the use of the RBAD and CBAD bits in troubleshooting.

MIRRORED BITS Transmit Identifier (TXID) and MIRRORED BITS Receive Identifier (RXID)
The TXID setting defines the MIRRORED BITS address that is sent with the transmitted message. At
the receiving end, this TXID from the incoming message is checked against the local RXID set-
ting. If these match, the message is accepted, allowing the received MIRRORED BITS to be used in
the logic of the receiving device. TXID and RXID cannot be set to the same number in the relay.
Continuing the example from Figure 3, the TXID and RXID settings are left at their default set-
tings of TXID = 2 and RXID = 1. This means that the device on the other end of the communica-
tions channel must have TXID = 1 and RXID = 2 to communicate with this device. If the channel
does not work during commissioning, TXID and RXID settings at the two ends might be incorrect.
Proper use of the TXID and RXID settings can help when you are using parallel MIRRORED BITS
channels. This is common when the primary and backup relay schemes are both using MIRRORED
BITS over fiber or other communications equipment. In cases like this, it is possible to accidentally
have the primary relay at one end communicating with the backup at the other end because of a
cabling error. However, if set properly, the TXID and RXID addresses prevent successful commu-
nications from being established if any cabling errors exist. For instance, the user might have the
primary relay scheme use addresses 1 and 2 and the backup scheme use addresses 3 and 4. That
way, if one of the relays using 1 and 2 receive a message with an address of 3 or 4 because of a
cabling error, it will not allow the MIRRORED BITS channel to be established, preventing an unin-
tended operation. If both pairs of relays use 1 and 2, a cabling error might not be noticed and com-
munication might be incorrectly established between a primary and backup relay.

MIRRORED BITS Receive Default State (RXDFLT)

The RXDFLT setting is shown in Figure 5. This setting determines the state of the individual
received MIRRORED BITS when communication is interrupted. These bits are referenced from left
to right as RMB8 through RMB1.

SEL Application Guide 2018-24 Date Code 20180822

 7

Figure 5 QuickSet View of RXDFLT Setting

The default setting is XXXXXXXX, which causes the received Mirrored Bit to be set to the last
valid state of the bit that was received. The individual bits can also be forced to a 0 or 1 as neces-
sary by setting RXDFLT appropriately. For instance, setting RXDFLT = XXXX0011 would have
the following results in the case of a communications failure: RMB8 through RBM5 would be set
to the last value received, RMB4 and RMB3 would be forced to 0, and RMB2 and RMB1 would
be forced to 1. This feature can be very helpful depending on how the MIRRORED BITS are used in
a relay protection or automation scheme. In the event that communication over the MIRRORED
BITS link has failed, setting RXDFLT appropriately to force certain RMBs to a particular state can
prevent a protection scheme from overtripping or an automation scheme from operating incor-
rectly.

MIRRORED BITS RMB Pickup Debounce Messages (RMB1PU) and MIRRORED BITS RMB Dropout Debounce
Message (RMB1DO)
Figure 6 shows the MIRRORED BITS pickup and dropout debounce settings RMBnPU and
RMBnDO. These settings adjust the required number of consecutive messages containing the
same state before the device processes the change in data. For instance, the pickup debounce set-
ting RMB1PU = 5 would mean that for RMB1 to go from 0 to 1, the relay requires five consecutive
messages where TMB1 = 1 from the remote end. Likewise, if the dropout debounce setting
RMB1DO = 6, the relay needs to receive six consecutive messages from the remote end in which
TMB1 = 0 for RMB1 to transition from 1 to 0 in the relay.

Figure 6 QuickSet View of Debounce Setting

Use of the pickup and dropout debounce settings can increase security by verifying that the same
message has been received multiple times before updating the RMB values. However, this also
results in a delay being introduced by waiting for these multiple messages to be processed. Con-
sider the impact of the pickup and dropout debounce settings in the receiving device and how
delays introduced by using these settings may affect the overall scheme being used.
Note that these pickup and dropout settings are based on the number of messages received and not
on a specific amount of time. This can result in different time delays depending on which products
are being used. An SEL-351 communicating with another SEL-351 sends and receives MIRRORED
BITS messages four times per power system cycle. Therefore, an RMB_Dropout Debounce Msgs
setting of two messages delays a bit by about 1/2 power system cycle. However, because SEL-400
Series Relays send and receive messages faster, the same pickup and dropout settings introduces
less delay.

MIRRORED BITS Transmit Equations (TMB)

The last settings that need to be configured are the MIRRORED BITS Transmit Equations, as shown
in Figure 7. Note that the protocol chosen by the user dictates which set of TMB equations are
used. For instance, if you choose MBA as the protocol, use the Channel A equations. If you choose
MBB as the protocol, use the Channel B equations.

Date Code 20180822 SEL Application Guide 2018-24

 8

These settings define what values are being sent to the remote device in the form of TMBs, and
may be comprised of singular Relay Word bits or of logic equations containing multiple Relay
Word bits and SELOGIC operations. If a logic equation is used, it evaluates to either a 1 or a 0, and
that is the value that will be sent. Note that the default settings seen in Figure 7 have 0 listed for
TMB1A–TMB8A. This means that by default, each transmit bit remains 0, so the remote end will
receive 0 for RMB1–RMB8 for this connection.

Figure 7 QuickSet View of MIRRORED BITS Transmit Equations

One final setting consideration involves using the RMBs received from the remote device in relay
logic. Use the appropriate RMB element in the logic equation to achieve the desired effect. For
instance, if you want to set Latch 1 whenever RMB1A goes high, simply set SET01 = RMB1A in
your logic setting.

MIRRORED BITS APPLICATION EXAMPLE

This section explores one example of using MIRRORED BITS. The goal is to send a transfer trip
from a local relay (Relay 1) to a remote relay (Relay 2). This guide focuses on the required relay
logic and assumes that all of the necessary communications and addressing settings have been pre-
viously configured.
First, define the logic that initiates the transfer trip from Relay 1 to Relay 2. You can use any of the
eight available TMBs to send the transfer trip. For this example, the first Mirrored Bit is used. This
example also assumes that both relays are using Channel A. In Relay 1, the relay setting TMB1A
defines the transmit equation for the first of the eight TMBs. When this logic equation asserts, the
status is mirrored to Relay 2 as RMB1A. Note that if Relay 1 were using its Channel B, setting
TMB1B would be used instead. However, if Relay 2 was still using its Channel A, this value would
still be mirrored into the RMB1A bit. As previously mentioned, the A and B designations are not
part of the data exchange between relays, so a relay using MB8A as its protocol can communicate
to a remote device that is using either MB8A or MB8B.
In SEL relays, there is usually a TR equation that contains logic appropriate for trip conditions. If
this equation evaluates to a 1, this signifies a trip condition and the TRIP Relay Word bit asserts.
This toggles the appropriate output contact that is wired to the breaker trip coil to initiate a trip of
the breaker. To incorporate a transfer trip from Relay 1 to Relay 2, set TMB1A = TRIP in Relay 1,
as shown in Figure 8. If you want a different condition to initiate a transfer trip (such as pressing a

SEL Application Guide 2018-24 Date Code 20180822

 9

pushbutton, only manual trips, etc.), customize the logic accordingly. For example, if a digital
input on the relay (e.g., IN102) is connected to a lockout relay that indicates breaker failure, you
could set TMB1A = IN102 to send a transfer trip to remote breaker based on that condition. For
another example, if an independent power producer wants to send a transfer trip to a utility breaker
when its own breaker opens, they could set TMB1A = NOT 52A.

Figure 8 MIRRORED BITS Transmit Equation in Relay 1

Next, configure Relay 2 to trip upon receiving the transfer trip bit. As explained previously, when
equation TMB1A asserts in Relay 1, it mirrors this value to Relay 2 as the Relay Word bit
RMB1A. Therefore, Relay 2 must be programmed to trip based on its normal protective functions,
as well as to trip upon receiving RMB1A. There are several ways this can be achieved, but the
most direct is to use the TR equation discussed previously. At the end of the existing TR equation
in Relay 2, add “+ RMB1A” (for SEL-300 Series Relays) or “OR RMB1A” (for SEL-400,
SEL-600, and SEL-700 Series Relays).
Note that some relays include a TRCOMM equation in which to put the RMB1A bit instead of in
the TR equation. This allows you to separate the regular trip conditions from the trip conditions
that come from communications-based protection schemes. Figure 9 shows the revised TR equa-
tion where RMB1A Relay Word bit was ORed with the default trip equation in an SEL-300 Series
Relay. The logic shown in Figure 8 for the trip equation shows various Relay Word bit being ORed
together (+ operator is an OR), and the last term ORed is the RMB1A Relay Word bit being used
for the transfer trip function.

Figure 9 Trip Logic for Relay 2 Modified to Include Transfer Trip

If you want Relay 2 to be able to send a transfer trip to Relay 1, repeat the previous steps to set up
TMB1A in Relay 2 and edit the trip equation in Relay 1 to include RMB1A.
For troubleshooting purposes and event analysis, it is important to add the appropriate Relay Word
bits to the Sequential Events Recorder (SER) report of each relay. For the transfer trip function,
entering the TMB1A and RMB1A Relay Word bits would be appropriate. The revised SER setting
is shown in Figure 10.

Figure 10 Adding Relay Word Bits to the SER Report

Once all settings have been appropriately adjusted, send the new settings to the relays.

Date Code 20180822 SEL Application Guide 2018-24

 10

Additional Notes
➤ A POTT scheme can be implemented similarly to the transfer trip scheme described.
Refer to the specific relay instruction manual for details on how a POTT scheme works
and how to set one up by using MIRRORED BITS.
➢ In Relay 1, set TMB1A = KEY (this is the relay element that asserts when the
POTT scheme forward fault detecting elements assert).
➢ In Relay 2, set the permissive trip setting (PT1) to RMB1A.
➤ Similarly, you can also implement a DCB scheme. Refer to your specific relay instruc-
tion manual for details on how a DCB scheme works.
➢ In Relay 1, set TMB1A to the logic you want to send to the block (for example, set
TMB1A = NSTRT AND NOT STOP OR DSTRT).
➢ In Relay 2, set the block trip received setting (BT) to RMB1A.

COMMISSIONING AND TROUBLESHOOTING MIRRORED BITS LINKS

When installing a MIRRORED BITS link, use the TAR command to look at the status of the ROKA
or ROKB bit, as shown in Figure 11.

=>>TAR ROKA <Enter>

LBOKB CBADB RBADB ROKB LBOKA CBADA RBADA ROKA
0 0 1 0 0 0 0 1
=>>

Figure 11 Checking MIRRORED BITS Status by Using ROKA

The ROK Relay Word bits stay asserted if the relay is receiving valid Mirrored Bit messages, but
drop out as soon as there is a single bad message. This is most often used to check the status of a
MIRRORED BITS link to determine if it is working properly. However, this bit should not necessar-
ily be used for alarming for a bad channel. The RBAD and CBAD functions are a better indication
of overall channel condition. Because of the sensitive nature of the ROK bit deasserting for even a
single bad message, using this as a SCADA alarm may result in many nuisance alarms.
If ROK is not asserted, check the addressing and baud rate settings in both devices. These are fre-
quently the cause of a MIRRORED BITS link not working. According to the discussion in Relay
MIRRORED BITS Settings on page 2, the transmit address on one end should match the receive
address on the other and vice versa. Also, the baud rate settings should be the same in both relays.
If the problem is not fixed by correcting the addressing or baud rate settings, the physical channel
might be the problem. The channel can be fiber, direct serial connection, a multiplexer, or other
media.
One way to confirm the integrity of the communications channel is a loopback test. It is often pos-
sible to loop back the channel so that the message a device sends is directed back to the receiver of
the same device. Normally, the relay rejects a message that does not have the proper addressing. If
the relay sees a message it is sending out, it rejects it and enters an alarm state. However, the
device can be set to look for the message it is transmitting by executing the LOO (Loopback) com-
mand. The LOO A command causes the Channel A MIRRORED BITS link for the device to enter
loopback mode for 5 minutes. You can also specify different time duration by executing the
LOO A n command, where n is the desired duration in minutes. The LOO command has an
optional parameter to add at the end of the command (DATA), which allows the bits that are trans-
mitted to be processed normally as received data, which will then be used like any other data in the
relay. This is done with a command such as LOO A DATA. Be careful when using the DATA
option, because the relay evaluates the received data normally and a trip or other operation could

SEL Application Guide 2018-24 Date Code 20180822

 11

occur. Block the relay operation with test switches or other means if this is a concern. During the
time the device is in loopback mode, the inputs are forced to the default values. The ROK Relay
Word bit deasserts when in this mode. If the sent message is received by the device correctly, the
LBOKA or LBOKB Relay Word asserts, proving the integrity of the communications medium to
the point where the loopback is taking place. This can be checked by executing the TAR LBOKA
command, as shown in Figure 12.

=>>LOOP A <Enter>
Loopback will be enabled on Mirrored Bits channel A for the next 5 minutes.
The RMB values will be forcred to default values while loopback is enabled.
Are you sure (Y/N)? Y <Enter>
=>>TAR LBOKA <Enter>
LBOKB CBADB RBADB ROKB LBOKA CBADA RBADA ROKA
0 0 1 0 1 0 0 0
=>>

Figure 12 Verifying Looped Back Communication

If the communications path is looped back at various locations, you should be able to locate the
problem in the communications path. If this is a direct fiber link, use a jumper to loop back the link
just as it leaves the sending device. This might be used in conjunction with an SEL transceiver,
such as the SEL-2830M Single-Mode Fiber-Optic Transceiver/Modem. If that test is successful,
the transmit and receive circuits and optics are confirmed to work for that device.
The next step is to loop back the fiber at the remote end towards the sending end. This can be done
at a fiber patch panel on a fiber link. If the loopback test is successful, this rules out any issues with
the sending device and fiber link. If this test does not cause the LBOK bit to assert, there may be a
fiber problem such as a broken fiber, bad splice, etc. Assuming the local and remote loopback tests
result in the LBOK asserting, the problem might be with the equipment at the remote end. Similar
tests can be done by looping back communications with the remote end device.
Note that if the communication is serial EIA-232, the loopback is done with a jumper to connect
Pins 2 and 3 of the serial cable. If the communication is being done over a multiplexer, it is often
possible to use the management software to cause a loopback in the serial interface card at either
the local or remote end of the link. Once the testing is complete, the LOOP command times out
and the device returns to normal operation, or the LOO A R command can be executed to cause
the MIRRORED BITS channel for MIRRORED BITS link A to leave loopback mode.
Once the MIRRORED BITS system is running after the initial commissioning, users may be notified
of a problem via an annunciator panel or via SCADA through the use of the RBAD and CBAD
alarm Relay Word bits discussed earlier. The user can determine whether the alarm was generated
by RBAD or CBAD by using TAR RBADA or TAR CBADA to see which Relay Word bit is cur-
rently asserted. This can also be determined by looking at the results of the SER command if these
Relay Word bits have been programmed into the SER.
According to the discussion in Relay MIRRORED BITS Settings on page 2, if RBAD is asserted, there
has been an extended communications outage on that MIRRORED BITS channel for a user-specified
interval. This typically indicates that something in the communications link has failed. Possible
causes may include a serial port hardware failure on the relay, a failed transceiver such as the
SEL-2830, a broken or severed cable or fiber, a radio failure, or an issue with a multiplexer the
channel is traversing through.
Apply standard troubleshooting methods, such as swapping out components or looping back the
channel at various points in the link to isolate the problem. Once the problem has been corrected,
check the ROK or RBAD Relay Word bits to verify that the MIRRORED BITS link is now communi-
cating.

Date Code 20180822 SEL Application Guide 2018-24

 12

If CBAD is asserted, it often indicates an intermittent communications problem. This is often a

result of an unreliable communications link. Examples of these types of links include leased ana-
log phone circuits and microwave radio. These are prone to interruptions because of old infrastruc-
ture, in the case of analog phone circuits, and weather may interfere with microwave links. For an
unreliable link, the channel may have many very short interruptions. It is possible to have cases
where the interruptions are frequent (such that the overall availability is under the CBAD threshold
previously discussed) but short enough that RBAD will not assert based on the RBADPU duration.
In these cases, if you are only using RBAD as a channel alarm, you may not know that the channel
is actually being interrupted many times. For this reason, it is best to use a combination of RBAD
and CBAD to confirm the overall availability of the channel. According to the discussion in Relay
MIRRORED BITS Settings on page 2, the settings for RBADBU and CBADPU are influenced by the
type of channel used and the reliability of that communications link.
If the cause of the alarm is RBAD, the RBAD Relay Word bit deasserts as soon as the MIRRORED
BITS link communication is restored. However, if the alarm is a result of CBAD, the CBAD Relay
Word bit may not immediately deassert when the MIRRORED BITS link communication is restored.
As discussed previously, the CBAD alarm bit asserts when the ratio of bad messages to the total
number of messages is above the CBADPU setting. So, for the CBAD Relay Word bit to deassert,
the MIRRORED BITS channel needs to have reliable communications for long enough that the ratio
of bad messages to the total number of messages is below the CBADPU setting. This could take a
long time to happen, depending on how long the outage is or how intermittent the failures are.
If the communications link has been fixed but the communication has not been running error-free
for a long enough period to clear the CBAD Relay Word bit, you can clear this alarm bit by execut-
ing the COM A C command, as shown in Figure 11. This command resets the calculation of the
ratio of bad messages to total messages, allowing it to start the calculations from a point where the
communications channel is working properly. It is a good practice to reset the communications sta-
tistics once a new MIRRORED BITS link has been commissioned or after a problem has been cor-
rected. This allows the CBAD bit to give a more accurate representation of whether or not there is
still an issue by not taking into account any data from before the communications data was cleared
and starting fresh.

=>>COM A C <Enter>
Clear the channel A communications buffer
Are you sure (Y/N)? Y <Enter>
Clearing Complete
=>>

Figure 13 COM A C Command

The COM A command can provide more detailed information on the status of the MIRRORED BITS
communications channel, which can help when troubleshooting a MIRRORED BITS problem. An
example of this is shown in Figure 14.

SEL Application Guide 2018-24 Date Code 20180822

 13

=>>COM A <Enter>

SEL-751 Date: 12/04/2015 Time: 11:17:16.897

FEEDER RELAY Time Source: Internal

Channel A Summary
From 11/09/2015 07:24:04.116
To 12/04/2015 11:17:16.897
Last failure Relay Disabled
Total failures 1
Device Disabled 1
Data error 0
Re-sync 0
Underrun 0
Overrun 0
Parity error 0
Framing error 0
Bad re-sync 0
Loop back 0
Max duration (sec) 2173992.78
Unavailability 1.000000

Figure 14 COM A Command Response

One version of this command, COM AL, gives details on each of the individual communication
events for that MIRRORED BITS link. This command gives the long report for MIRRORED BITS
Channel A, as shown in Figure 15.

=>COM A L <Enter>

SMALLER Date: 05/16/17 Time: 14:04:26.300

STATION A
FID=SEL-351S-7-Rxxx-Vx-Zxxxxxx-Dxxxxxxxx CID=xxxx
Summary for Mirrored Bits channel A

For 05/16/17 13:57:06.717 to 05/16/17 14:04:26.299

Total failures 12 Last error Data error

Relay Disabled 1
Data error 1 Longest Failure 3.654 sec.
Re-Sync 0
Underrun 10 Unavailability 0.051959
Overrun 0
Parity error 0
Framing error 0 Loop-back 0
Bad Re-Sync 0

Failure Recovery
# Date Time Date Time Duration Cause
1 05/16/17 14:00:28.0074 05/16/17 14:00:30.5281 2.521 Underrun
2 05/16/17 14:00:24.3826 05/16/17 14:00:26.1367 1.754 Underrun
3 05/16/17 14:00:19.1329 05/16/17 14:00:22.0203 2.887 Underrun
4 05/16/17 14:00:18.6455 05/16/17 14:00:18.9913 0.346 Underrun
5 05/16/17 14:00:12.7667 05/16/17 14:00:15.5373 2.771 Underrun
6 05/16/17 14:00:07.7128 05/16/17 14:00:09.9002 2.187 Underrun
7 05/16/17 14:00:01.6048 05/16/17 14:00:04.8880 3.283 Underrun
8 05/16/17 13:59:55.2761 05/16/17 13:59:58.9300 3.654 Underrun
9 05/16/17 13:59:55.0677 05/16/17 13:59:55.2302 0.162 Underrun
10 05/16/17 13:59:49.0973 05/16/17 13:59:52.1929 3.096 Data error
11 05/16/17 13:59:48.8890 05/16/17 13:59:49.0681 0.179 Underrun
12 05/16/17 13:59:06.7177 05/16/17 13:59:06.7177 0.000 Relay Disabled

Figure 15 COM A L Command Response

The various types of errors in the communications reports are explained in Table 3.

Date Code 20180822 SEL Application Guide 2018-24

 14

Table 3 Communication Error Descriptions

Error Type Description

Parity error Data failed UART parity check.
Underrun Three MIRRORED BITS messages transmitted without one being received.
Overrun UART data buffer overrun.
Re-sync The MIRRORED BITS device at the other end of the link detected an error.
Data error Received data was not self-consistent, or the address was wrong.
Relay disabled Relay protection functions disabled as during power up or change in settings or settings group.
Loop back Loopback enabled. Error conditions followed by “(L)” occurred while the system was in
loopback.
Framing error The UART did not detect a stop bit in the received MIRRORED BITS data.

In summary, there are many tools available when troubleshooting a MIRRORED BITS connection.
First, check the communications parameters to confirm they are set correctly on both ends. After
verifying communications settings, verify the physical medium of the connection by employing
loopback testing along the path to rule out a break in the communications link or a hardware fail-
ure that prevents the transmission or receiving of data on the end devices.
While testing, there are many helpful Relay Word bits within the relay to help you understand
where the issue may be. The ROK bit gives an instantaneous indication of whether or not the chan-
nel is communicating. However, because of the sensitive nature of this point, it typically should not
be used for a communications alarm. It is better to use a combination of RBAD and CBAD as
alarm points. RBAD indicates a continuous failure over a certain user-set time period, while
CBAD is based on the overall availability of a channel, exposing intermittent issues that may not
cause a continuous failure. These bits are helpful in troubleshooting, but they can also be used in
relay logic to disable the protection scheme if communication is down.

CONCLUSION
MIRRORED BITS communications can be used to provide a fast and reliable means of communica-
tion for protection and automation applications. This guide examined all of the settings associated
with a MIRRORED BITS connection. It also explored different communications channels options
and recommended settings for each type. Finally, this guide explored troubleshooting techniques
for MIRRORED BITS connections and showed some of the reports that relays can provide to help
determine what may be wrong with a particular channel.

REFERENCES
[1] J. Candelaria and H. Khatri, “Using an SEL-321 and an SEL-311 Series Relay to Set Up
POTT and DCB Schemes,” SEL Application Guide (AG2017-22), 2017. Available:
selinc.com.
[2] K. Behrendt and K. Fodero, “Implementing MIRRORED BITS Technology Over Various Com-
munications Media,” SEL Application Guide (AG2001-12), 2001. Available: selinc.com.
[3] T. Bartman and A. Hargrave, “Using MIRRORED BITS® and SEL-3031 Serial Radio Commu-
nications for Protection Schemes,” SEL Application Guide (AG2016-17), 2016. Available:
selinc.com.

SEL Application Guide 2018-24 Date Code 20180822

 15

TECHNICAL SUPPORT
We appreciate your interest in SEL products and services. If you have questions or comments,
please contact us at:
Schweitzer Engineering Laboratories, Inc.
2350 NE Hopkins Court
Pullman, WA 99163-5603 U.S.A.
Tel: +1.509.338.3838
Fax: +1.509.332.7990
Internet: selinc.com/support
Email: info@selinc.com

Date Code 20180822 SEL Application Guide 2018-24

 16

© 2018 by Schweitzer Engineering Laboratories, Inc. All rights reserved.

All brand or product names appearing in this document are the trademark or registered 2350 NE Hopkins Court • Pullman, WA 99163-5603 U.S.A.
trademark of their respective holders. No SEL trademarks may be used without written Tel: +1.509.332.1890 • Fax: +1.509.332.7990
permission. selinc.com • info@selinc.com
SEL products appearing in this document may be covered by U.S. and Foreign patents.

SEL Application Guide 2018-24 Date Code 20180822