ABB Zenith 50P-2035 User manual

—
OPERATION AND MAINTENANCE MANUAL
Zenith Modbus Network Card 50P-2035
For MX150/MX250 (MX Version 6.0+ Only)

WARNING
Automatic Transfer Switches are often used in critical applications. Failure of an ATS to operate properly could
cause serious personal injury (including death) and property damage. Therefore, extreme caution must be used
when designing or using programming software that will communicate with the ATS. Improper use of the
Modbus network variables will cause the Automatic Transfer Switch to malfunction. Always conduct a full
test and debug of the programming software prior to installing and using it in the system.
ABB Zenith disclaims any and all liability for use of third-party application software that
will be used to control the Automatic Transfer Switches.
Disclaimer
Table of Contents
Page
Overview ..............................................................................................................................................................................................01
LED Indicator ..........................................................................................................................................................................01
Installation ..........................................................................................................................................................................................02
Installation on the Controller ......................................................................................................................................02
Termination Resistor ..........................................................................................................................................................02
Configuring a Modbus Network Card ....................................................................................................................02
Testing a Modbus Network..............................................................................................................................................03
CDP Programmable Exercisers ....................................................................................................................................03
CDT Exercisers........................................................................................................................................................................ 3
Operation ............................................................................................................................................................................................04
Setting System Time ............................................................................................................................................................04
Operation with In-Phase Monitor ..............................................................................................................................04
Operation Under Battery Backup ..............................................................................................................................04
Appendix A – Read Only Register List......................................................................................................................05-12
Appendix B – Read/Write Register List ................................................................................................................ 13-14
Appendix C – Modbus Network Card ............................................................................................................................ 15
Appendix D – Connections for Configuring and Testing the Modbus Card ...................................... 16
Appendix E – RS485 Multi-Drop Connection .......................................................................................................... 17
Appendix F – Installation of Modbus Card on Controller .............................................................................. 18
Appendix G – Modbus Protocol Illustration ...................................................................................................... 19-21
Appendix H – Configuring Controller for Modbus (MX150/250) .......................................................... 22
Bill of Materials.............................................................................................................................................................................. 23
Components for the Modbus Option (ZNET250M).................................................................................... 23
Components for the Modbus Card Configuration ...................................................................................... 23
Troubleshooting............................................................................................................................................................................ 24

These bits make up the least significant byte of the Status
0 register, while the most significant byte of the Status 0
register contains zeros. Figure 1 shows an example of what
the Master device would see if it read back the entire
Status 0 register. In this example, the Master device would
read back the decimal value of 129 from the Status 0 reg-
ister. When this value is decoded, the Master finds out
that the S1 source is available and the Automatic Transfer
Relay input is active. The Master also has the option of
reading the individual bits, indented under Status 0. This
allows the Master to know the status of each parameter
without doing any decoding. The second column con-
tains the actual addresses for the network variables. These
addresses are used when the Master is reading a Holding
Register (16-bit reg). The third column contains address-
es that are used when the Master is reading a Coil (indi-
vidual bit). The remaining columns show the values and
ranges (only in Appendix B) for the
network variables.
LED Indicator
The Modbus card has a
10-segment LED module
(Refer to Appendix E
for location). These
LED’s display the slave
address of the card as well
as transmit and receive
status. The first LED from
the bottom indicates the
receivestatus, the second
LED indicates the transmit
status. When a Modbus
packet has been success-
fully transmitted or
received, the associated
LED will light for100ms. If
anotherpacket is sent or received before the100ms elaps-
es, the LED on-time will be extended by another 100ms.
LED’s 3-10 display the slave address of the controller as
a binary number with each LED corresponding to a bit.
Figure 2 shows the 10-segment LED module along with
LED’s 3, 5, and 6 being lit. The lit LED’s correspond to
slave address 13.
■ABB Zenith 1 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
The Modbus network card is designed for the MX150
and MX250 controllers, version 6.0 program and above.
If the controller is ordered with the Modbus option, the
Modbus card will reside on the back of the controller
board and it will be part of the controller assembly. The
purpose of this card is to allow the controller to be avail-
able on a Modbus network as a slave device. This allows a
master device, such as a programmable logic controller
(PLC), to obtain information from the controller and
have that information available for control, data acquisi-
tion and monitoring.
Every Modbus network consists of one master device
and at least one slave device. All devices on the network
are daisy-chained using a twisted pair cable (see
Appendix E). Each slave device is assigned a unique
address from 1-247. Factory default for each Modbus
card is Slave Address 1. This address enables the master
to distinguish between the various slaves on the net-
work. It also allows the master device to send a query
command to the addressed slave. When the addressed
slave receives this command it will send back an appro-
priate response to the master. Table 1 shows a list of
Modbus commands which the Modbus network card
supports. Reference Appendix G for a more detailed
description of the Modbus commands.
The Modbus commands allow the master device to read
data from, and write data to, specific memory locations in
the controller. These memory locations, which are listed
in Appendix A and B, make up the Modbus network
variables. These variables allow the reading of controller
status, configuration, etc. The variables which can be
written to (reference Appendix B), include timer values,
Fail/Restore settings, and control variables.
Both lists contain a parameter name column that displays
the name of the memory locations. The non-indented
names in that column are 16-bit registers while the indented
ones are individual bits, which make up the 16-bit registers.
For example, Status 0, a non-indented name, is a 16-bit
register that consists of the following bits:
Overview
Modbus Command Modbus Command Description
01 Read Coil Status
03 Read Holding Register
05 Write Single Coil
06 Write Single Holding Register
15 Write Multiple Coils
16 Write Multiple Holding Registers
Table 1 – Supported Modbus Commands
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
1
Most Si
g
nificant Byte
Normal Source Available
Least Si
g
nificant Byte
Emergency Source Available
Load, No Load, Fast Load Test Status
Load Test Running
Not Used
Alarm
ATS Not in Auto Mode
Automatic Transfer Relay
Figure 1 – Status 0 Register
•S1 Available
• S2 Available
•Load, No Load, Fast
Load Test Status
•Load Test Running
• Alarm
•ATS Not in Auto Mode
•Automatic Transfer Relay
LED 9 - 26
LED 10 - 27
LED 8 - 25
LED 7 - 24
LED 6 - 23
LED 5 - 22
LED 4 - 21
LED 3 - 20
LED 2 - Transmit
LED 1 - Receive
Figure 2 – LED Module

Installation
Installation on the Controller
If the Modbus network card is not installed on the
controller, do the following to install it:
1. Open the ATS cabinet. If the ATS has power going
to it, be EXTREMELY cautious not to touch any
energized parts.
2. Remove the two Engine Start wires from the P-Relay(s)
if applicable (not applicable in Utility-Utility applica-
tions). Use electrical tape to tape over the exposed
ends of both wires.
3. Obtain a grounding wrist strap and put the elastic
end of the strap on your wrist. Attach the alligator
clip end to the controller chassis or an equivalent
earth ground.
4. Remove the J5 plug from the controller (located on
bottom of board), this will remove power. If controller
is equipped for external battery, also remove the J4
connector from the side of the controller. When
power is removed from the controller, the ATS will
not transfer.
5. Unscrew the black metal cover from the back of the
controller. Be sure not to lose any screws.
6. Remove the three screws from the metal standoffs
on the controller. Plug the Modbus network card
into socket J3 and fasten it to the controller with
the three screws (previously removed).
7. Screw the black metal cover back on.
8. Reconnect the J5 plug back into the controller.
(If controller is equipped for external battery, also recon-
nect the J4 connector on the side of the controller.)
9. Connect the two Engine Start wires to the P-Relay(s)
if applicable.
10. Once the controller has power, the network option
must be enabled by going into the CFG menu for
the network option (Reference Appendix H).
11. When the network option is enabled, exit the
CFG menu.
Termination Resistor
Located on the bottom of the Modbus card is jumper J6
(See Appendix C), which enables or disables a termination
resistor on the board(Figure 3). Jumper J6 is disabled when
it comes from the factory.
The only time that Jumper J6 should be enabled is when
its corresponding Modbus card is the last device at the end
of the chain.
Enabled
Disabled
(Factory Default)
Figure 3 – Jumper J6
■2 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Configuring a
Modbus Network Card
The Modbus card can be configured in a variety of ways.
The configuration of the card includes configuring the
slave address, RTU or ASCII mode, baud rate, parity, and
stop bits (the default settings are Slave Address 1, RTU mode,
9600 Baud, No Parity and 2 Stop Bits). These slave settings will
be setup by the user and must match the master device
settings for proper communications. The user configures
these settings using the Modbus Configuration applica-
tion (ABB Zenith Part # 50P-1111). This application can
also read the configuration of the card. The following is a
procedure for configuring the Modbus Network card
(See Appendix D for wiring connections).
To change configuration settings:
1. Disconnect the two Engine Start wires from the P-
Relay(s), if applicable. Use electrical tape to tape over
the exposed ends of both wires.
2. Obtain a grounding wrist strap and put the elastic end
of the strap on your wrist. Attach the alligator clip end
to the controller chassis, or an equivalent earth ground.
3. Remove the J5 plug from the controller (located on
bottom of board). This will remove power. (If controller
is equipped for external battery, also remove the J4 con-
nector from the side of the controller.)
4. Unscrew the black metal cover from the back of the
controller.
5. Install the J4 jumper on the back of the Modbus Card
(Refer to Appendix C for location).
6. Connect the RS232/485 converter (ABB Zenith Part #
50W-1208) to the PC that has the Configuration
Application Software Installed.
7. Connect a twisted pair cable between the RS485 connec-
tor of the Modbus Card and the RS485 connector of the
RS232/485 converter. Verify correct polarity (Refer to
Appendix D for connection).
8. Reconnect the J5 plug. This will restore power to the
controller.
9. Start up the Configuration Application on the PC.
10. Click on the “READ” button to read the device's current
configuration.
11. Click on the “MODIFY” button to enable parameter
changing.
12. Make necessary changes to the communication settings.
13. Click on the “WRITE” button to send the new configu-
ration to the Modbus Card.
14. Verify that the configuration was written by clicking the
“READ” button, and verify the settings.
15. Remove the J5 plug from the controller.
16. Remove the J4 jumper from the Modbus Card.
17. Screw the black metal cover back on the controller.
18. Reconnect the J5 plug to the controller. (If controller is
equipped for external battery, also reconnect the J4 con-
nector on the side of the controller.)
19. Reconnect the two Engine Start wires to the P-Relay(s),
if applicable.

■ABB Zenith 3 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Testing a Modbus Network
The Modbus network can be tested using the compo-
nents in the Modbus Configuration package (ABB Zenith
Part # 50P-1124). Reference Appendix D for connections.
1. If testing a network consisting of more than one
card, make sure that all of the cards are daisy
chained as shown in Appendix E. Verify that all
Modbus cards are in the run mode (jumper J4 on
the Modbus card must not be installed).
Termination jumper (J6) is only installed on the
last card on the network daisy chain.
2. Connect the RS232/485 converter (ABB Zenith Part
# 50W-1208) to the PC that contains the
Configuration software (ABB Zenith Part # 50P-1111).
A cable needs to be connected to the RS485 connector
of the Modbus card and the RS485 connector of the
RS232/485 connector. Check to make sure that the
polarity connections are correct. (See Appendix D)
3. Run the Configuration software on the PC.
4. Press the TESTbutton and then verify that the settings
in the Communication Settings section match the settings
of the Modbus network. If necessary, make changes
to the settings and click the NEXT button.
5. The software will now scan the network and display
the serial number of all controllers, which have the
Modbus card attached. The user can select any of
the listed serial numbers and execute a load test on
a controller associated with the selected serial num-
ber, but only one controller can be tested at a time.
CDP Programmable Exercisers
CDP Programmable Exercisers are an option on the
MX150 and MX250. They allow the controller to be pro-
grammed to automatically test the generator and
Automatic Transfer Switch. Up to seven exercisers can
be programmed to run on a daily, 7 day, 14 day, or 28
day basis; or up to 24 exercisers can be programmed to
run on a yearly basis.
Configuration information regarding CDP Programmable
Exercisers is available in the Exerciser Configuration
Register (Holding Register 40063):
Bit 0 of the Exerciser Configuration Register (Coil 81)
indicates whether the controller is configured for CDT
or CDP Programmable Exercisers. A one means the con-
troller is configured for CDP Programmable Exercisers.
Bit 2 of the Exerciser Configuration Register (Coil 82)
indicates whether or not the CDP Programmable
Exercisers can be configured to run under load (trans-
fer the ATS to the generator). A zero indicates that
exercisers can only run No-Load. A one indicates that
exercisers can be programmed to run Load or No-Load.
Holding Registers 40101 through 40110 are provided to
control and report the status of the CDP Exercisers.
These registers contain valid data only if the controller is
configured for CDP Exercisers. If the controller is config-
ured for CDP Exercisers, then Holding Register 40063,
Bit 0 (Coil 81) will be set to 1.
Reading the CDP Exerciser Holding
Registers
The controller may be programmed for multiple exer-
cisers, depending on the status of the Exerciser
Schedule Selection. All data relevant to every exerciser
is read out through Holding Registers 40101 through
40110. These registers will contain data describing one
exerciser at a time. The value of Holding Register
40101, “Exerciser Record Pointer”, determines which
exerciser is presently being displayed in Holding
Registers 40102 through 40109.
To read the contents of a different exerciser, the
Exerciser Record Pointer must be written. For example,
in order to read data about CDP Exerciser #3, the
Exerciser Record Pointer must be set to 3.
The controller will automatically place all exercisers in
chronological order.
CDT Exercisers
CDT Exercisers are a standard feature of the MX150
and MX250 (unless replaced by CDP Programmable
Exercisers). They allow the controller to be pro-
grammed to automatically test the generator and
Automatic Transfer Switch. The exerciser will run at the
same time of day on a daily, 7 day, 14 day, or 28 day
basis. Programming of the CDT Exerciser can be done
only at the HMI on the front panel of the MX150 or
MX250.
Configuration information regarding CDT Exercisers is
available in the Exerciser Configuration Register
(Holding Register 40063):
Bit 0 of the Exerciser Configuration Register (Coil 81)
indicates whether the controller is configured for CDT
or CDP Programmable Exercisers. A zero means the
controller is configured for CDT Exercisers. Conversely,
bit 1 implies the controller is configured for the CDP
Exerciser.
Bit 1 of the Exerciser Configuration Register (Coil 82)
indicates whether or not the CDT is configured for
Load Exercises. A one indicates the CDT will run a
Load Exercise. A zero indicates the CDT will run a No-
Load Exercise.
The upper byte of the Exerciser Configuration Register
(bits 15 through 8) indicates the CDT Exerciser Run
Duration, in minutes.
Installation
(cont’d)

■4 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Operation
Setting System Time
Holding Registers 40094 through 40099 are provided to
control and report the status of the controller’s System
Time. Reading Holding Register 40094 through 40099
will report the current Hour, Minute, Day, Month, Year,
and Day of Week to which controller’s internal clock is
currently set.
Writing the System Time Holding Registers
Holding Registers 40094 through 40098 must be written
using a Write Multiple Holding Register Command
(Function Code 16). This is to ensure that the data con-
tained in these registers is a complete ordered set. Any
attempt to write Holding Registers 40094, 40095, 40096,
40097, or 40098 with a Write Single Holding Register
Command (Function Code 6), or a Write Multiple
Holding Register Command (Function Code 16) that
does not include the entire range of 40094 - 40098, will
result in an Illegal Data Address exception response
from the Modbus Card.
Note: Holding Register 40099, “System Time-Day of
Week” is Read Only. The value of this register is auto-
matically computed and updated by the controller,
based on the calendar date.
Operation with In-Phase Monitor
Special consideration is required if the controller is con-
figured with the In-Phase Monitor. Most Modbus net-
work data and control are unavailable while the In-Phase
Monitor is waiting for phase synchronization. The
Modbus Network Card will return a “Slave Device Busy”
exception code (06h) to all Modbus queries, except for
queries to the System Busy Status Register (Holding
Register 40112) or the System Busy Control Register
(Holding Register 40113).
If the Modbus Network Card returns a Slave Device Busy
exception code, information about the source of the
busy condition may be available in the System Busy
Status Register (Holding Register 40112). If Bit 0 of the
System Busy Status Register (Coil 105) is set to one, the
controller is busy waiting for phase synchronization.
If the controller is busy waiting for phase synchroniza-
tion, the In-Phase Monitor may be bypassed over the
Modbus network by performing the following sequence:
Warning: EXTREME CAUTION must be used when
bypassing the In-Phase Monitor! Transferring between
sources that are not in phase synchronization may cause
unexpected operation, resulting in damage to plant
equipment and personnel.
1. Set Bit 0 of the System Busy Control Register (Coil
113) to one. This is a request by the Modbus user to
bypass the In-Phase Monitor.
2. Once an In-Phase Monitor bypass has been requested,
and the controller has been waiting for phase synchro-
nization for more than one minute, the controller will
request confirmation of the In-Phase Monitor bypass.
This request is indicated by a one in Bit 1 of the System
Busy Status Register (Coil 106).
3. To confirm the request to bypass, set Bit 1 of the
System Busy Control Register (Coil 114) to one.
The controller will bypass the In-Phase Monitor.
Note: The In-Phase Monitor bypass feature is an inter-
locked command-and-confirm mechanism. The Modbus
Card will not allow the Confirm Bypass control bit
(Coil 114) to be set before the controller has set Ready
to Confirm Bypass status bit (Coil 106). If a write request
is received to set Coil 114 before the controller has set
Coil 106, an Illegal Data Value error code will be returned.
Bypass Pending Exerciser
Bit 0 (Coil 121) is the Bypass Pending Exerciser bit.
The MX Platform performs a logic-OR with this bit and
the BPASS EXER key on the HMI. A 1 in Bit 0 bypasses
the pending exerciser; a 0 does nothing.
Cancel Bypass
Bit 1 (Coil 122) is the Cancel Bypass bit. The MX
Platform performs a logic-OR this bit with the CANCL
BPASS key on the HMI. A 1 in Bit 1 cancels the Bypass
Pending Exerciser. A 0 in this bit position does nothing.
The Bypass Pending Exerciser Bit works different,
between a Timer Exerciser and Clock Exerciser,
depending on the state of Exerciser Type (Holding
Register 40063, Bit 0, Coil 81). When Coil 81 = 0 (Timer
Exerciser), if Coil 121 is set to 1, the Timer Exerciser
will be bypassed until the Cancel Bypass Bit (Coil 122)
is set to 1. When Coil 81 = 1 (Clock Exerciser), if Coil
121 is set to 1, only the exerciser that is pending at the
time gets bypassed, and the exerciser only gets bypassed
once. The Controller waits for Coil 121 to reset to a 0
before a subsequent bypass can be performed.
Operation Under Battery Backup
The controller can be powered from an external 12-volt
battery in the event that neither S1 nor S2 are available.
While the controller is on external battery backup,
data will still be available over the Modbus Network
as noted below.
While the controller is running on external battery
backup, data regarding ATS position and limit switch
inputs may be invalid if both S1 and S2 sources are lost.
Therefore, if Bits 6 and 7 of Holding Register 40001,
or Coils 7 and 8, are both zero, the following Modbus
network data may not be reliable:
• Automatic Transfer Relay –
Holding Register 40001, Bit 0 or Coil 1
• SN Limit Switch –
Holding Register 40002, Bit 0 or Coil 9
• SE Limit Switch –
Holding Register 40002, Bit 1 or Coil 10
• SNO Limit Switch –
Holding Register 40002, Bit 2 or Coil 11
• SEO Limit Switch –
Holding Register 40002, Bit 3 or Coil 12
• S1 Position Status –
Holding Register 40004, Bit 9 or Coil 34
• S2 Position Status –
Holding Register 40004, Bit 10 or Coil 35

■ABB Zenith 5 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix A – Read Only Register List
eulaVnoitpircseDlioCtiB.geRgnidloH
40001 MX Status 0
ffO=0,nO=1yaleRrefsnarTcitamotuA10
otuAnitoN=1edoMotuAnitoNSTA21
evitcAmralA=1mralAesopruPlareneG32
3 4 Unused
4 5 Load Test or Fast Load Test Running 1 = Running
5 6 Load, No Load, Fast Load Test Status 1 = Running
elbaliavA=1elbaliavA2S76
elbaliavA=1elbaliavA1S87
40002 MX Status 1
ffO=0,nO=1hctiwStimiLNS90
ffO=0,nO=1hctiwStimiLES0
11
ffO=0,nO=1hctiwStimiLONS112
ffO=0,nO=1hctiwStimiLOES213
4 13 S2 Phase Rotation - Valid only if 3ph and S2 Avail 1 = CW, 0 = CCW
5 14 S1 Phase Rotation - Valid only if 3ph and S1 Avail 1 = CW, 0 = CCW
enO=0,eerhT=12SnosesahPforebmuN516
enO=0,eerhT=11SnosesahPforebmuN617
40003 MX Status 2
0 17 Unused
ffO=0,nO=1evitcA5S811
ffO=0,nO=1evitcA21S912
ffO=0,nO=1evitcA)SL(dehSdaoL023
ffO=0,nO=1evitcA7Q12
4
ffO=0,nO=1evitcA3Q225
6 23 Closed Transfer Relay (CTR) Active 1 = On, 0 = Off
7 24 Transfer Mode Select (TMS) Active 1 = On, 0 = Off
40004 Timer ID 0
1elbaTeeS0tiBremiT520
1elbaTeeS1tiBremiT621
1elbaTeeS2tiBremiT722
3 28 Unused
4 29 Unused
5 30 Unused
6 31 Unused
7 32 Unused
gninnuRremiT=1evitcAremiT338
noitisoP1S=1sutatSnoitisoP1S439
noitisoP2S=1sutatSnoitisoP2S5301
11 36 Unused
12 37 Unused
13 38 Unused
14 39 Unused
15 40 Unused

■6 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix A
(cont’d)
Read Only Register List
eulaVnoitpircseDlioCtiB.geRgnidloH
sdnoceSeulaVnwodtnuoCremiT50004
stloV)B-AesahP(egatloV1S60004
stloV)C-BesahP(egatloV1S70004
stloV)A-CesahP(egatloV1S80004
stloV)B-AesahP(egatloV2S90004
stloV)C-BesahP(egatloV2S01004
stloV)A-CesahP(egatloV2S11004
40012 Unused
01/eulavdelacs=eulaVqerFycneuqerF1S31004
40014 Unused
01/eulavdelacs=eulaVqerFycneuqerF2S51004
40016 Unused
40017 Total Transfers to S1
40018 Unused
40019 Serial Number (MSR)
40020 Serial Number (LSR)
40021 Nominal Full-Scale Voltage
40022 MX Network Configuration 0
0 41 Unused
1 42 Unused
2 43 Unused
3 44 Unused
4 45 Unused
5 46 Closed Transition Configured 1 = Configured
6 47 In-Phase Monitor Configured 1 = Configured
dradnatS=0,yaleD=1epyTSTA847
40023 MX Network Configuration 1
derugifnoC=1noitpOlaunaM/otuA21S940
1 50 S5 Auto/Manual Bypass Option 1 = Configured
2 51 Phase Sequence Check Option 1 = Configured
derugifnoC=1noitpOycneuqerfrevO2S253
derugifnoC=1noitpOegatlovrevO2S354
derugifnoC=1noitpOycn
euqerfrevO1S455
6 55 S1 Underfrequency Option 1 = Configured
derugifnoC=1noitpOegatlovrevO1S657
40024 MX Network Configuration 2
0 57 Phase Imbalance Configured 1 = Configured
1 58 Unused
2 59 Closed Transition Configured 1 = Configured
derugifnoC=1tcennocsiDdaoL-erP063
derugifnoC=1tcennocsiDdaoL-tsoP164
5 62 Open Loop Transfer Option 1 = Configured
6 63 Unused
7 64 Controller T
yp
052/051XM=1e
,
0 = MX200

■ABB Zenith 7 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix A
(cont’d)
Read Only Register List
eulaVnoitpircseDlioCtiB.geRgnidloH
40025 S1 Voltage (Phase A-B), Raw A/D Raw A/D Value - See Note 1
40026 S1 Voltage (Phase B-C), Raw A/D Raw A/D Value - See Note 1
40027 S1 Voltage (Phase C-A), Raw A/D Raw A/D Value - See Note 1
40028 S2 Voltage (Phase A-B), Raw A/D Raw A/D Value - See Note 1
40029 S2 Voltage (Phase B-C), Raw A/D Raw A/D Value - See Note 1
40030 S2 Voltage (Phase C-A), Raw A/D Raw A/D Value - See Note 1
2etoNeeS-eulaVwaRtnuoCdoireP1S13004
2etoNeeS-eulaVwaRtnuoCdoireP2S23004
40049 Total S1 Fails
40050 Total Transfers to S2
40051 Days Powered Up
sruoH)RSM(elbaliavA1SemiT25004
sruoH)RSL(elbaliavA1SemiT35004
sruoH)RSM(elbaliavA2SemiT4
5004
sruoH)RSL(elbaliavA2SemiT55004
40056 Unused
40057 Unused
40058 Unused
40059 Unused
40060 Unused
40061 Unused
40062 Unused
40063 Exerciser Schedule Status
remiT=0,kcolC=1epyTresicrexE180
1 82 Load/No Load Exerciser (Timer Exerciser Only) 1 = Load
2 83 User can set load exercises (Clock Exerciser Only) 1 = Yes
3 84 Unused
4 85 Unused
5 86 Unused
6 87 Unused
7 88 Unused
[15:8] Timer Exerciser Run Duration Minutes
40064 MX Status 3
gnidnePresicrexE=1gnidnePresicrexE980
dessapyBresicrexE=1dessapyBresicrexE091
2 91 Unused
3 92 Unused
4 93 Unused
5 94 Unused
6 95 Unused
7 96 Unused
40065 Unused
40066 Unused
40067 Unused

■8 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix A
(cont’d)
Read Only Register List
eulaVnoitpircseDlioCtiB.geRgnidloH
40068 Timer ID 1
0 97 Unused
1 98 Unused
gninnuR=1gninnuRremiT26A/6A992
gninnuR=1gninnuRremiTT0013
gninnuR=1gninnuRremiTTD1014
gninnuR=1gninnuRremiT3W/3T2015
gninnuR=1gninnuRremiTW3016
gninnuR=1gninnuRremiTWD4017
40069 T or W Timer Countdown Value Seconds
40070 T3/W3 Timer Countdown Value Seconds
40071 A6/A62 Timer Countdown Value Seconds
01/eulaV=reVnoisiveRerawmriFXM27004
40073 Modbus Card Firmware Revision Ver = Value/100
40074 Unused
40075 Unused
40076 Unused
40077 Most Recent Event Pointer
40082 Unused
40083 Unused
40099 System Time – Day of Week
setoNegnaRnoitpircseDlioCtiB.geRgnidloH
40102 Exerciser Record – Hour 0 - 23
40103 Exerciser Record – Minute 0 - 59
40104 Exerciser Record – Month 1 - 12 Not writeable for Daily
sresicrexEylkeeWro
40105 Exerciser Record – Day of Month 1 - 31 Max val. depends on month, year
yliaDrofelbaetirwtoN
sresicrexEylkeeWro
40106 Exerciser Record – Day of Week 1 = Sun., 7 = Sat. Writeable for Weekly Exercisers Onl
y
40107 Exerciser Record – Ex. Duration 0 - 600 minutes
40108 Exerciser Record – Load/No Load 1 = Load, 0 = No Load Writeable ONLY if Factory
sresicrexEdaoLrofderugifnoC
40109 Unused
40110 Exerciser Schedule Selection 0 = Off
)yaD1(yliaD=1
)yaD7(ylkeeW=2
)yaD41(ylkeeW-iB=3
)yaD82(keeW4=4
aD563(radnelaC=5
y
)

■ABB Zenith 9 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix A
(cont’d)
Read Only Register List
eulaVnoitpircseDlioCtiB.geRgnidloH
40111 System Busy Status
ysuBmetsyS=105RoteudysuBmetsyS5010
1 106 Ready to Confirm Bypass R50 1 = Ready to Confirm Bypass
2 107 Unused
3 108 Unused
4 109 Unused
5 110 Unused
6 111 Unused
7 112 Unused
40113 Unused
40114 Unused
40115 Unused
40116 Unused
40117 Unused
40118 Unused
40119 Unused
40120 Unused
2elbaTeeS0tnevErofnosaeR12104
dnoceS0tnevE22104
ruoH0tnevE32104
etuniM0tnevE42104
htnoM0tnevE52104
htnoMfoyaD0tnevE62104
raeY0tnevE72104
2elbaTeeS1tnevErofno
saeR82104
dnoceS1tnevE92104
ruoH1tnevE03104
etuniM1tnevE13104
htnoM1tnevE23104
htnoMfoyaD1tnevE33104
raeY1tnevE43104
2elbaTeeS2tnevErofnosaeR53104
dnoceS2tnevE63104
ruoH2tnevE73104
etuniM2tnevE83104
htnoM2tnevE93104
htnoMfoyaD2tnevE04104
raeY2tnevE14104
2el
baTeeS3tnevErofnosaeR24104
dnoceS3tnevE34104
ruoH3tnevE44104
etuniM3tnevE54104
htnoM3tnevE64104
htnoMfoyaD3tnevE74104
raeY3tnevE84104

■10 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix A
(cont’d)
Read Only Register List
eulaVnoitpircseDlioCtiB.geRgnidloH
2elbaTeeS4tnevErofnosaeR94104
dnoceS4tnevE05104
ruoH4tnevE15104
etuniM4tnevE25104
htnoM4tnevE35104
htnoMfoyaD4tnevE45104
raeY4tnevE55104
2elbaTeeS5tnevErofnosaeR65104
dnoceS5tnevE75104
ruoH5tnevE85104
etuniM5tnevE95104
htnoM5tnevE06104
htnoMfoyaD5tnevE16104
raeY5tnevE26104
2elbaTeeS6tnevErofnosaeR36104
dnoceS6tnevE46104
ruoH6tnevE56104
etuniM6tnevE66104
htnoM6tnevE76104
htnoMfoyaD6tnevE86104
raeY6tnevE96104
2elbaTeeS7tnevErofnosaeR07104
dnoceS7tnevE17104
ruoH7tnevE27104
etuniM7tnevE37104
htnoM7tnevE47104
htnoMfoy
aD7tnevE57104
raeY7tnevE67104
2elbaTeeS8tnevErofnosaeR77104
dnoceS8tnevE87104
ruoH8tnevE97104
etuniM8tnevE08104
htnoM8tnevE18104
htnoMfoyaD8tnevE28104
raeY8tnevE38104
2elbaTeeS9tnevErofnosaeR48104
dnoceS9tnevE58104
ruoH9tnevE68104
etuniM9tnevE78104
htnoM9tnev
E88104
htnoMfoyaD9tnevE98104
raeY9tnevE09104
2elbaTeeS01tnevErofnosaeR19104
dnoceS01tnevE29104
ruoH01tnevE39104
etuniM01tnevE49104
htnoM01tnevE59104
htnoMfoyaD01tnevE69104
raeY01tnevE79104

■ABB Zenith 11 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix A
(cont’d)
Read Only Register List
eulaVnoitpircseDlioCtiB.geRgnidloH
2elbaTeeS11tnevErofnosaeR89104
dnoceS11tnevE99104
ruoH11tnevE00204
etuniM11tnevE10204
htnoM11tnevE20204
htnoMfoyaD11tnevE30204
raeY11tnevE40204
2elbaTeeS21tnevErofnosaeR50204
dnoceS21tnevE60204
ruoH21tnevE70204
etuniM21tnevE80204
htnoM21tnevE90204
htnoMfoyaD21tnevE
01204
raeY21tnevE11204
2elbaTeeS31tnevErofnosaeR21204
dnoceS31tnevE31204
ruoH31tnevE41204
etuniM31tnevE51204
htnoM31tnevE61204
htnoMfoyaD31tnevE71204
raeY31tnevE81204
2elbaTeeS41tnevErofnosaeR91204
dnoceS41tnevE01204
ruoH41tnevE12204
etuniM41tnevE22204
htnoM41tne
vE32204
htnoMfoyaD41tnevE42204
raeY41tnevE52204
2elbaTeeS51tnevErofnosaeR62204
dnoceS51tnevE72204
ruoH51tnevE82204
etuniM51tnevE92204
htnoM51tnevE03204
htnoMfoyaD51tnevE13204
raeY51tnevE23204

■12 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
2. Registers 40031 and 40032 contain unscaled
frequency values. In order to obtain a full-scale
frequency value, use the following formula:
Scales Frequency + (20,000,000 / Period Count)
Notes:
1. Registers 40025 - 40030 contain unscaled voltage
values In order to obtain a full-scale voltage value,
use the following formula:
Voltage = (A/D Raw Value / 192) x
Full Scale Voltage (Register 40021)
eulaVremiT
b111P
W-W3, Unbypassed 110b
W-W3,YE bypassed 101b
T-T3, Unbypassed 011b
Y-T3,YN bypassed 010b
b000U
Reason Code Description
0 S1 Fail
1 S2 Fail
2 S1 Phase Imbalance
3 S2 Phase Imbalance
4 S2 Start
5 S2 Stop
6 Sync Fail
7 Load Shed
8 ATS Inhibit
9 Phase Rotation
10 Remove Test
11 Local Test
12 S1-S2 Volt. Imbalance
13 S1-S2 Freq. Imbalance
14 CT Xfr S1>S2
15 CT Xfr S2>S1
16 Xfr S1>S2
17 Xfr S2>S1
18
19
20 No Xfr
21 OLC
22 STE
23 S1 UV Fail
24 S1 OV Fail
25 S1 UF Fail
26 S1 OF Fail
27 S2 UV Fail
28 S2 OV Fail
29 S2 UF Fail
30 S2 OF Fail
31 S1 Restore
32 S2 to Open
33 Exerciser
34 Remote Test Network
35 Remote Inhibit
36 Local Inhibit
37 S2 Avail
38 S2 Off
Appendix A
(cont’d)
Read Only Register List

■ABB Zenith 13 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix B - Read/Write Register List
setoNegnaRnoitpircseDlioCtiB.geRgnidloH
40033 P Timer Setting 0 - 1000 1/100 of a second
40034 W Timer Setting 0 - 300 seconds
40035 T3/W3 Timer Setting (Mirror of 40038) 0 - 60 seconds
40036 DW Timer Setting 0 - 600 seconds
40037 T Timer Setting 0 - 3600 seconds
40038 T3/W3 Timer Setting (Mirror of 40035) 0 - 60 seconds
40039 DT Timer Setting 0 - 600 seconds
40040 U Timer Setting 0 - 3600 seconds
40041 S1 Undervolt Restore 85 - 100 percent Must be at least 2 > S1 UV Fail
40042 S1 Undervolt Fail 75 - 98 percent Must be at least 2 < S1 UV Restore
40043 S2 Undervolt Restore 85 - 100 percent Must be at least 2 > S2 UV Fail
40044 S2 Undervolt Fail 75 - 98 percent Must be at least 2 < S2 UV Restore
40045 S1 Underfreq Restore 90 - 100 percent Must be at least 2 > S1 UF Fail
40046 S2 Underfreq Restore 90 - 100 percent Must be at least 2 > S2 UF Fail
40047 Net Control 0
0 65 Reset Time S2 Available 1 = Reset
mralAecneliS=1ecneliSmralA661
2 67 Unused
2SotssapyB=1lortnoCEY863
1Sotssa
pyB=1lortnoCNY964
5 70 No Load Test Control 1 = Start Test
6 71 Load Test Control 1 = Start Test
7 72 Fast Load Test Control 1 = Start Test
40048 Net Control 1
0 73 Unused
ffO=0,nO=1lortnoC5S471
ffO=0,nO=1lortnoC21S572
ffO=0,nO=1lortnoCSL673
ffO=0,nO=1lortnoC7Q774
ffO=0,nO=1lortnoC3Q875
ffO=0,nO=1lortnoC2xuA976
ffO=0,nO=1lortnoCSMT087
40078 UMD Timer Setting 0 - 300 seconds
40079 Phase Imbalance Timer Setting 10 - 30 seconds
40080 Phase Imbalance Fail Setting 5 - 20 percent
40081 Phase Imbalance Restore Setting 3 - 18 percent
erotseRVO1S>2tsaeltaebtsuMtnecrep011-501liaFtlovrevO1S48004
40085 S1 Overvolt Restore 103 - 108 percent Must be at least 2 < S1 OV Fail
erotseRVO2S>2tsaeltaebtsuMtnecrep011-501liaFtlovrevO2S68004
40087 S2 Overvolt Restore 103 - 108 percent Must be at least 2 < S2 OV Fail
40088 S1 Underfreq Fail 88 - 98 percent Must be at least 2 < S1 UF Restore
erotseRFO1S>1tsaeltaebtsuMtnecrep501-301liaFqerfrevO1S98004
40090 S1 Overfreq Restore 102 - 104 percent Must be at least 1 < S1 OF Fail
40091 S2 Underfreq Fail 88 - 98 percent Must be at least 2 < S2 UF Restore
erotseRFO2S>1tsaeltaebtsuMtnecrep501-
301liaFqerfrevO2S29004
40093 S2 Overfreq Restore 102 - 104 percent Must be at least 1 < S2 OF Fail

■14 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix B
(cont’d)
Read/Write Register List
setoNegnaRnoitpircseDlioCtiB.geRgnidloH
HR 40094 - 40098 MUST ALL be written with a Write Multiple Holding Register Command
40094 System Time – Hour 0 - 23
40095 System Time – Minute 0 - 59
40096 System Time – Day 1 - 31 Max val. depends on month, year
40097 System Time – Month 1 - 12
40098 System Time – Year 0 - 255, 0 = Year 2000
40100 Daylight Savings Time 1 = ATS follows DST
HR 40101 - 40109 MUST ALL be written with a Write Multiple Holding Register Command
HR's listed as "Not Writeable" under certain conditions must be written as zeros
HR40101-40110 are for CDP Programmable Exercisers Only
40112 System Busy Control
0 113 Command to Bypass In-Phase Monitor 1 =
Bypass In-Phase Monitor
1 114 Confirm Bypass In-Phase Monitor 1 = Confirm
2 115 Unused
3 116 Unused
4 117 Unused
5 118 Unused
6 119 Unused
7 120 Unused
40113 Net Control 2
0 121 Bypass Pending Exerciser 1 = Bypass
1 122 Cancel Exerciser Bypass 1 = Cancel Bypass
2 123 Unused
3 124 Unused
4 125 Unused
6 127 Unused
7 128 Unused

■ABB Zenith 15 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix C – Modbus Network Card
J4
C10
C12
R13
J5
C11
C9
C7
C8
C6
R12
C5
J3
R16
R15
R14
C13
R17
J6
COMMUNICATIONS ADAPTER
R10
LED1
D1
R1
RN1
P1
C1 C3
R5
R9
C2
U2
R3
J1
Y1
J2
U3 R8
D2
R4
U7 U8
C4
U4 R11
U5
S N
U6
REV A
R2
U1
MODBUS
50P-2025
REV X.X
T
OP
5
0P-202
5
MODBU
S
NETW
O
R
K
C
AR
D
CONFIGURATIO
N
JUMPER
(
J4
)
LED ADDR/
S
TATU
S
INDICAT
OR
TOP OF MODBUS CARD BOTTOM OF MODBUS CARD
TERMINATIO
N
JUMPER
(
J6
)

■16 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
A
B
S
EE N
O
TE 6
P
S
-514
0
NETW
O
RK PLU
G
C
O
NNECT
OR
VERIFY P
O
LARIT
Y
C
O
NNECTI
O
N
S
5
0W-120
8
R
S
2
3
2
/
48
5
C
O
NVERTE
R
50P-2035
MODBUS
NETW
O
RK CAR
D
A
SS
EMBL
Y
ADDRE
SS/S
TATU
S
INDICAT
O
R LED
s
(REF. PG.1
,
FIG. 2
)
CONFIGURATION JUMPER
(
J4
)
(
NOTE 2
)
S
EE N
O
TE
1
Appendix D
Connections for Configuring and Testing the Modbus Card
MODBUS NETWORK CARD DEFAULT SETTINGS
SLAVE ADDRESS 1
RTU MODE
8 DATA BITS, 9600 BAUD, NO PARITY, 2 STOP BITS.
NOTES:
1. USETWISTED PAIR CABLE (BELDEN 8471, 16 AWG) (ABB ZENITH
PART # WMW-453).
2. CONFIGURATION JUMPER (J4) MUST BE INSTALLEDTO CHANGE MODBUS
ADDRESS AND MODE. REMOVE FOR NORMAL OPERATION.
3. MODBUS NETWORK CARD ASSEMBLY MUST BE INSTALLED ONTHE CON-
TROLLER. REFERTO APPENDIX F.
4. USE SOFTWARE PROGRAMMING PACKAGE 50P-1111. REFERTO PAGE #
“CONFIGURING A MODBUS NETWORK CARD.”
5. TO TEST THE MODBUS NETWORK, REFER TO PAGE # “TESTING A MODBUS
NETWORK” PROCEDURE.
6. CONNECT TOTHE SERIAL PORT OF THE PC WHICH HAS THE 50P-1111
SOFTWARE PACKAGE.

■ABB Zenith 17 ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix E
MASTER
DEVICE
A
B
MX150/250
WITH
MODBUS
CARD
SLAVE #1
A
B
MX150/250
WITH
MODBUS
CARD
SLAVE #2
A
B
MX150/250
WITH
MODBUS
CARD
SLAVE #3
SEE NOTE 1
A
B
NOTE:
1. TERMINATION JUMPER (J6), LOCATED ON THE MODBUS
CARD, MUST BE CONNECTED ON THE LAST SLAVE IN THE
CHAIN. (REFER TO FIGURE 3 FOR JUMPER POSITIONS)
2. A MAXIMUM OF 247 SLAVES CAN BE ADDRESSED ON
THE MODBUS NETWORK.
3. RECOMMENDED TWISTED PAIR WIRE IS BELDEN 8471,
16 AWG (ABB ZENITH PART # WMW-453).
4. FOLLOW STANDARD RS485 WIRING (INSTALL A REPEATER
IF THE WIRE LENGTH EXCEEDS 4,000 FT. OR FOR EVERY 32
DEVICES ON THE NETWORK).
RS485 Multi-Drop Connection

■18 ABB Zenith ■
MX150/MX250 Series Modbus Network Card (71R-2200)
Appendix F
Installation of Modbus Card on MX Controller
BACK
O
F MX
C
O
NTR
O
LLE
R
R
S
485 NETW
O
R
K
C
O
NNECTI
ON
VERIFY P
O
LARIT
Y
C
O
NNECTI
O
N
S
50P-20
35
M
O
DBU
S
NETW
O
R
K
CARD A
SS
EMBL
Y
REF. APPENDIX E
F
O
R C
O
NNECTI
ON
DETAIL
S