CCA Network Training

Common Control Architecture

The information contained in this document may contain confidential, proprietary and/or privileged material of either Wabtec Corporation or
one of its subsidiaries. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is prohibited unless authorized in writing. If you have received this document in error,
please contact the sender and delete the material from any system and destroy any copies.
 Scope
➢ There are 4 networks in the Evolution series locomotive;
➢ Serial network for 3rd party panel connections
➢ CAN Bus for Sensors
➢ ArcNet for Locomotive Control
➢ Ethernet for Train Control and intercommunication
➢ The scope of this presentation is to provide technical guidance and troubleshooting for the ARCNet
Network (the green cables that are located on the EVO locomotives).
 NETWORK OVERVEIW

There are two network connections located

within the ARCNet Network, network 0 and
network 1 (they are both located in the same
cable). The two physical networks provide
redundancy in the case where one network
experiences a failure. The other network will
pick up the slack and network communication
will not be interrupted, locomotive operation
will continue as normal.
 NETWORK OVERVEIW
➢ The table on the next slide lists each of the pieces of equipment, along
with its GETS abbreviation and a description of its function.
➢ The ARCNet allows the Smart Displays to perform all of the control
functions that are necessary to manage the generation of 3000+
mechanical horsepower, to convert that power to electrical energy, to
distribute that energy where it is needed, and to use the energy to haul
freight or run internal locomotive support systems.
➢ The Smart Displays use the ARCNet to carry out a wide variety of
functions;
➢ Reading operator input
➢ Controlling the operation of auxiliary equipment (radiator cooling, traction motor cooling,
alternator excitation, battery charging)
➢ Managing diesel engine operation
➢ Controlling the inverters and so the traction motors
➢ Operating contactors and relays to perform other necessary tasks.
 NETWORK OVERVEIW
CONTROL EQUIPMENT CONNECTED WITHIN THE NETWORK
Device Name Location Function
DS2 Smart Display 2 CN2 Control Computer and display
Translates communications between 3rd party equipment and smart
PTP Protocal Translator Panel RLA
displays
DS1 Smart Display 1 CN1 Control Computer and display
The main control computer, Provides input and output channel from
CIO Consolidated I/O Panel CA1
the smart displays to components on the locomotive.
Controls diesel engine speed against loading from propulsion and
ECU Engine Control Unit CA2
auxiliary systems
Traction Alternator
TAC CA2 Controls TA field current (Excitation)
Controller
Converts commands from the CIO and smart displays to power for
TMC Traction Motor Controller CA2
the TMs
Auxiliary Alternator
AAC CA4 Controls AA excitation
Controller
BCC Battery Charge Controller CA4 Voltage controller for battery charging
RFC1 Radiator Fan Controller 1 CA4 Controls the operation of the radiator fan
THE NETWORK LAY OUT
THE NETWORK LAY OUT
 The Network Cable
The network cable is a special constructed cable to reduce noise
susceptibility and emissions. Being a special cable, a unique green
coloring was applied for its outer jacket/insulation to distinguish it from
the rest of the cable/wires. It is important that the specified routing be
followed within the locomotive cabs because of noise susceptibility
and emissions

NOTE: THE NETWORK CABLES ARE NOT TO BE REPAIRED, BUT REPLACED

BY NEW CABLES OF THE SPECIFIED LENGTH. DISCARD ANY OLD
NON-FUNCTIONAL NETWORK CABLE(S). IN FACT THEY ARE NOT PHYSICALLY
REPARIABLE SO DO NOT EVEN TRY.
 The Net work Cable
The wired ARCNet uses a simple alternating algorithm, which places the
updated data on the opposite network, to which it was delivered on
previously. Alternating distributes data onto two physical networks placing
50% delivery dependency on one network.

Outside green insulation

Foil
Braided insulation

Network wires Drain

The internal make-up of the ARCNet Cable

 Network Connector Pins
The Network cable houses two separate networks and a network consists
of 2 wires. It is prudent that each network uses a twisted pair of wires to
reduce noise emissions through coupling. The following table designates the
wire color and the corresponding Pin of the DB9 connector it is set in.

Wire Color Pin Number Network

Blue 2 0
White 7 0
Orange 9 1
Black 4 1
TERMINATION CABLES AND RESISTORS

Notice at each end of the bus, a network termination is required

to ensure the signal integrity. These terminator (shorting) cables
are located at the end of the network on the SDIS2 and the
RFC1. This Termination reduces the signal reflection and absorbs
the generated Potential energy. Also each panel incorporates
two terminating resistors, one for each network (Net 0, Net 1)
integrated onto the network modules/cards on the panels. These
terminating resistors give the panels their identification on the
network.
TERMINATION CABLES AND RESISTORS
The terminating (shorting plug) cable, can ONLY be used at a panel. It can not
be connected to a cable.
5 1

9 6

Figure 1 – Terminator Shorting DB9 Plug

Another termination plug that may be used in troubleshooting is the Terminator

Resistor DB9 Plug. This is a DB9 connector that has two 120 Ohm resistors, one
between pins 4 and 9 and the other between pins 2 and 7. This plug is utilized
in place of the Terminator Shorting DB9 Plug. The Terminator Resistor Plug can
be used on both Panels and cables.

Figure 2 – Terminator Resistor DB9 Plug

TERMINATION CABLES AND RESISTORS

CNA CNB CNA CNB

120Ω

120Ω
CNA CNB CNA CNB

SHORT

SHORT
120Ω

120Ω

SHORT
Trouble shooting the ARCNet Network

On board the locomotive, screens are available to aid in

troubleshooting and evaluating the health of the network. To
view the network screens you must be in L3.
Press the Loco monitor Key to get to the set of predefined
screens.
Pressing the network key will bring you to the Screen shown
in figure 3
Trouble shooting the ARCNet Network
Recon Count – This
number is the number
of Reconfigurations
that each network
has had since power
up. Reconfigurations
are caused by nodes
(panels) that are
trying to gain access
to the network.
These nodes/panels
could have either lost
their connection and
are trying to
reestablish a
connection or the
node could be joining
the network for the
first time (i.e. at
power up). All
panels keep track of
number of recons on
the network. The
Recon Count on the
Network Monitor
screen only
represents what the
CIO believes the
number of Recons is.

Figure 3
Trouble shooting the ARCNet Network
Num TX Error –
This is the
number of
Transmission
Errors that the
CIO has had
while
communicating
with any of the
panels on each
network. This
number will
count up
continuously if
one or more
panels were on
the network
and now is no
longer
communicating.
Figure 3
Trouble shooting the ARCNet Network
Num Exc NACK
– This is the
number of
Excessive Non
Acknowledgeme
nts that the CIO
has had from
other panels on
the network. If
the CIO has
tried to
communicate
with a panel,
and the panel is
too busy, then
the CIO will
receive a NACK
from that panel.
If this happens
four consecutive
times, then an
Excessive
NACK will be
counted. Figure 3
Trouble shooting the ARCNet Network
Control Network Map –
This section of the
screen is used to
designate which panels
are “present” on the
Network from the
perspective of the
network hardware. If an
“X” is present on both
Net 0 and Net 1 this
means that the panel is
communicating at the
hardware level. SDIS#2
will show as a “Rpt”
which means repeater as
this panel does not talk
on the network. If the
panel shows blank on
either Net 0 and/or Net 1,
there is a
communications problem
with that panel on the
given network

Figure 3
Trouble shooting the ARCNet Network

To access all
the network
communicatio
ns that are
available
through the
SDIS
Trouble shooting the ARCNet Network

H J
A K
B C D E F G

L
Trouble shooting the ARCNet Network
A. Device – This column lists all of the panels on the ARCNet on the locomotive. The list is arranged in order of physical
arrangement on the locomotive.
B. Source Panel Status – This circular icon indicates the health of the source node (i.e. that panel). A green circle indicates
that both the receiver and transmitter for both N0 and N1 are healthy. A yellow circle with a corresponding number/letter
indicates that the panel communications on N0 and/or N1 are degraded.
C. Destination Panel Status - This circular icon indicates the health of the destination node (i.e. the panel(s) that this panel is
communicating with). A green circle indicates that both the receiver and transmitter for both N0 and N1 are healthy for the
destination panel. A yellow circle with a corresponding number/letter indicates that the destination panel communications
on N0 and/or N1 are degraded.
D. My Recon 0/My Recon 1 – These columns represent the count of reconfigurations that this panel has caused on N0/N1.
E. Exc NAK 0/Exc NAK 1 - This is the number of Excessive Non Acknowledgements that this panel has counted as a result of
communications with other panels on the network. If a source panel has tried to communicate with destination panel, and
the destination panel is too busy, then the source panel will receive a NACK from that panel. If this happens four
consecutive times, then than Excessive NACK will be counted.
F. Out Seq – This is the count of messages that have been received “out of sequence” on both N0 and N1. Messages have
sequence numbers and if message 5 comes after message 6 then and “out of sequence” is counted.
G. Miss Seq – This is the count of messages that have been “missed” on both N0 and N1. Messages have sequence
numbers and if message 4 comes and then message 6, a “missed sequence” is counted.
H. Tx Err 0 / Tx Err 1 – This column represents the number of transmission errors counted by a particular panel. If a source
panel is trying to talk to a destination panel and the panel does not respond, then a transmission error will be counted.
J. Tx TmOut 0 / Tx TmOut 1 – This column represents transmission timeouts. This count usually represents an issue with the
hardware.
K. Reconfig Network 0 / Network 1 - This number is the number of Reconfigurations that each network has had since power
up. Reconfigurations are caused by nodes (panels) that are trying to gain access to the network. These nodes/panels
could have either lost their connection and are trying to reestablish a connection or the node could be joining the network
for the first time (i.e. at power up). All panels keep track of number of recons on the network. The Recon Count on the
Network Monitor screen only represents what CIO believes the number of Recons is.
L. Last Reconfig Caused By Network 0 / Network 1 – This block indicates which panel caused the last reconfiguration on the
network.
Troubleshooting the ARCNet Network
1) What is the allowable reconfiguration rate per second?

The allowed reconfiguration rate is 1 reconfiguration every 15 minutes on a properly setup network. A reconfiguration rate greater than 12
recons/second indicates a serious problem in the network. As panels are deliberately and non-deliberately powered up, that panel will
cause 1 to 4 reconfigurations on each network, this is normal operation. The deliberate power-ups (a breaker was cycled, a panel’s power
plug is disconnected, the panel’s CPU was reset through shorting the reset pin) are expected and are not counted against the allowed
rate.

2) One Network’s Reconfiguration Counter is Increasing at a rate of 1 or more per second.

1.Since the data on the network screen is only CIO’s count of reconfigs, it is wise to confirm the rate of recons with another panel on the
network. To look at the ECU or Aux Panel count of Network Recons, follow the procedure described in Appendix A. Connecting to the
ECU or Aux Panels can also be useful in diagnosing network issues with the SDIS’s not connected.
2.In general, you need to find out whether the network issue resides within a given panel or within one of the network cables. To
determine or eliminate if a panel is the source of the reconfigs, there are two methods. One or both may be required.

• Turning power off to that panel. This eliminates the node from the network, but the network still used the network traces on the card
to complete the bus configuration.
• Bypassing the panel by connecting its network cables together. This will completely bypass the panel.
1. To determine if the failure is within one of the network cables, you will need to use the shorting plugs or terminating plugs
to create a smaller network and then bring cables back into the network.
2. Begin by applying a shorting plug at the CIO panel.

Important Notes:
When disconnecting cables, both networks will be disrupted and comm. loss incidents will log for all panels.
Sometimes the cable lengths will be just right and the system will work unterminated.
Always have at least 3 communicating nodes (remember SDIS2 does not talk) in the network.
X’s on the screen are flashing in and out does not mean that the panel is actually talking. The way that the system sniffs nodes is
inaccurate at this point.
Trouble shooting the ARCNet Network
• If the recon is still counting up, we need to get another version of recons and verify that they are increasing
too. Use ECU or AUX or CIO panels. See Appendix A for ECU/AUX setup.
• If the above steps verify that the network has reconfigurations at a rate of 1 or more per second, it indicates
that there is a hardware issue that needs repair or replacement. To troubleshoot this problem, make two
smaller networks and view recons at SDIS, ECU and PTU. Determine which network still has recons.
• There could be problems with either cables or panels.
• Troubleshoot Bad Panels
Turn off / remove power to panels one at a time and observe recons.
• Troubleshoot Bad Cables
• Connect all the network cables together leaving just 3 panels in the loop.
• Gradually, move the terminator from the last cable to the PT on each cable until recons stop.
• If necessary, take SDIS’s out of the loop and look at ECU’s version of recons.

P.S. DO NOT CONNECT RFC1-B AND SDIS-2-A CABLES TOGETHER. THEY ARE SPECIAL.

3) Both Network’s Reconfiguration Counters are Increasing at a rate of 1 or more per second.
• Make sure all the connectors are secure.
• Check panels for compatible panel version.
4) A reconfiguration is happening on both networks every 2 minutes.
• AUX or ECU could be bad because they do not have software in them.
Trouble shooting the ARCNet Network
Trouble shooting the ARCNet Network
Trouble shooting the ARCNet Network
5) X on the Network screen for a panel has disappeared.

a) If one X has disappeared and recons are not counting up, cycle power. If X is still missing, replace the panel
as one of the comm chips might have gone bad.
b) If both the X’s are missing and recons are not counting up – the panel should have an active comm. loss
associated with it.
o Check power cables to the panel – verify that power is getting to the power connector at the panel - if there is no
power to the connector, troubleshoot the power wires per the schematic. If there is power to the panel’s power
connector, attempt the following:
o Try to download software to the panel – If CIO does not have application software, it will log a comm. loss. Verify
panel has application software loaded.
o Check node-id jumpers – Aux panels have external id jumpers if these are defective, then the panel will not boot
up or will boot up wrong.
o Verify voltage at power input pins and then cycle power the system could have gone into la-la land.
o If X’s are still missing even after a power cycle, replace the panel.
c) If recons are counting up, troubleshoot per Question 2.

6) An X on the Network screen for a panel disappears and reappears.

• Check recon rate and troubleshoot per Question 2.

• Check power cables to the panel. Verify voltage at power input pins and then cycle power. If X’s are still missing,
replace the panel.

7) A third Party box is not communicating with the SDIS and I think it is the ARCNET.
• Cycle power to the Protocol Translator Panel (PTP).
• Completely reboot the system using the Battery Switch (BS).
• If the problem persists, troubleshoot the network.
Trouble shooting the ARCNet Network
8) There is a Loss of Communication Incident for a Panel.
• Reboot the system
• Swap node ID’s (not for TMC) – For TMC, swap card slots.
• Check node Id jumpers

9) I unplugged a network Cable then reconnected it, the network is going crazy now.

• Troubleshoot per Question 2.

10) What is the best practice to find the panel causing reconfigurations?

• Troubleshoot per Question 2.

11) One network on the network screen has many missing X’s.

• Please refer to Question 6 and 7.

All panels keep track of number of recons on the network. So, if we need to compare the number of recons or rate of
recons, look at the ECU or CIO or AUX panels. See next slide for ECU/AUX setup.
 ECU & AUX Panel PTU Setup
To get the PTU up on aux/ecu panel application software:
• Connect D9 to D25 serial cable between laptop and panel using Hyperterm connect using
9600,8,N,1,None settings.
• Type rs to refresh the ptu screen and make sure you are talking to the panel

PTU monitor parameters 21-44 are network paramters

at the > type
mmp 21 and this monitor parameter should show on the screen
mmp 21-36
21 M 1 numTtaN0 4699 ::
22 M 1 numTmaN0 4676 ::
23 M 1 numReconN0 7 ::
24 M 1 numMyReconN0 0 ::
25 M 1 numExcNakN0 5 ::
26 M 1 numTtaN1 4696 ::
27 M 1 numTmaN1 4672 à ::
28 M 1 numReconN1 7 ::
29 M 1 numMyReconN1 0 ::
30 M 1 numExcNakN1 6

The physical terminating resistor is actually located on the panel, and jumper
wires inside the connector connect the terminating resistors to the network.