Alstom iVPI Integrated Vital Processor Interlocking Control System Maintenance and Troubleshooting Manual

iVPI™

Integrated

Vital Processor

Interlocking Control

System

Maintenance and

Troubleshooting

Copyright © 2008, 2011, 2012, 2013 Alstom Signaling Inc.

Maintenance and Troubleshooting Manual

P2521B, Volume 5

iVPI™

Integrated

Vital Processor

Interlocking Control

System

Maintenance and

Troubleshooting

Copyright © 2008, 2011, 2012, 2013 Alstom Signaling Inc.

Maintenance and Troubleshooting Manual

Alstom Signaling Inc.

P2521B, Volume 5, Rev. E, November 2013, Printed in U.S.A.

LIST OF EFFECTIVE PAGES

P2521B, Volume 5, iVPI Integrated Vital Processor Interlocking Control System

Maintenance and Troubleshooting Manual

ORIGINAL ISSUE DATE:

CURRENT CHANGE AND DATE:

October 2008

Rev E, November 2013

PAGE

Cover

CHANGE OR REVISION LEVEL

Nov/13

Title page

Preface i through vi

1–1 through 1–6

2–1 through 2–4

3–1 through 3–6

4–1 through 4–92

5–1 through 5–10

6–1 through 6–2

A–1 through A–2

Nov/13

Nov/13

Nov/13

Nov/13

Nov/13

Nov/13

Nov/13

Nov/13

Nov/13

Nov/13

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

THIS PAGE INTENTIONALLY LEFT BLANK.

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

PREFACE

NOTICE OF CONFIDENTIAL INFORMATION

Information contained herein is confidential and is the property of Alstom Signaling Inc. Where furnished with a proposal, the recipient shall use it solely to evaluate the proposal. Where furnished to customer, it shall be used solely for the purposes of inspection, installation, or maintenance. Where furnished to a supplier, it shall be used solely in the performance of the contract. The information shall not be used or disclosed by the recipient for any other purposes whatsoever.

VPI

®

, WEE-Z

®

, and Microchron

®

are registered trademarks of Alstom Signaling Inc.

GM4000A™, iVPI™, microWIU™, and VCS™ are trademarks of Alstom Signaling Inc.

All other trademarks referenced herein are trademarks of their respective owners.

FOR QUESTIONS AND INQUIRIES, CONTACT CUSTOMER SERVICE AT

1-800-717-4477

OR

WWW.ALSTOMSIGNALINGSOLUTIONS.COM

ALSTOM SIGNALING INC.

1025 JOHN STREET

WEST HENRIETTA, NY 14586

REVISION LOG

Revision Date Description

1(A)

2(B)

October 2008

March 2011

Original issue

Updated with commercialized components

3(C) March 2012 Updated with BEX boards, cables, & chassis

4(D)

E

January 2013 Updated to add new iVPI detail

November 2013 Corrected diagnostic display error codes

By Checked Approved

MAS

MAS

KW

RH

NI

NI

JF

SG

SG

RH

RH

KW

NI

NI

MS

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

THIS PAGE INTENTIONALLY LEFT BLANK.

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

ABOUT THE MANUAL

This manual provides maintenance and troubleshooting procedures for the Alstom

Integrated Vital Processor Interlocking Control System, (iVPI). This manual is part of a five volume set of manuals summarized in Section 1.

The information in this manual is arranged into sections. The title and a brief description of each section follow:

Section 1 – INTRODUCTION: This section describes the service log, parts, equipment, and maintenance schedule for maintenance and troubleshooting of the iVPI System.

Section 2 – TROUBLESHOOTING: This section provides troubleshooting flowcharts for the iVPI System.

Section 3 – DESIGN, TEST AND VALIDATION TOOLS: This section describes the available design, test, and validation tools for the iVPI System.

Section 4 – SYSTEM DIAGNOSTICS: This section describes the available system diagnostics on the iVPI System.

Section 5 – BOARD REPLACEMENT: This section provides board replacement procedures for each of the boards used in the iVPI System.

Section 6 – VITAL BOARD VERIFICATION: This section provides procedures for verification of iVPI System Vital board functions.

Appendix A – DATA LOG SHEET: This section contains the Software Configuration

Data Log form for recording system data.

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

THIS PAGE INTENTIONALLY LEFT BLANK.

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

MANUAL SPECIAL NOTATIONS

In the Alstom manuals, three methods are used to convey special informational notations. These notations are warnings, cautions, and notes. Both warnings and cautions are readily noticeable by boldface type and a box around the entire informational statement.

Warning

A warning is the most important notation to heed. A warning is used to tell the reader that special attention needs to be paid to the message because if the instructions or advice is not followed when working on the equipment then the result could be either serious harm or death. The sudden, unexpected operation of a switch machine, for example, or the technician contacting the third rail could lead to personal injury or death.

An example of a typical warning notice follows:

WARNING

Disconnect motor energy whenever working on switch layout or switch machine. Unexpected operation of machine could cause injury from open gears, electrical shock, or moving switch points.

Caution

A caution statement is used when an operating or maintenance procedure, practice, condition, or statement, which if not strictly adhered to, could result in damage to or destruction of equipment. A typical caution found in a manual is as follows:

CAUTION

Turn power off before attempting to remove or insert circuit boards into a module. Boards can be damaged if power is not turned off.

Note

A note is normally used to provide minor additional information to the reader to explain the reason for a given step in a test procedure or to just provide a background detail. An example of the use of a note follows:

Note: This step should be done first to validate the correct information is used.

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

THIS PAGE INTENTIONALLY LEFT BLANK.

P2521B, Volume 5, Rev. E, Nov/13 Alstom Signaling Inc.

TABLE OF CONTENTS

Topic Page

SECTION 1 – INTRODUCTION .................................................................................. 1–1

1.1

GENERAL .................................................................................................. 1–1

1.2

MANUAL SET ORGANIZATION ................................................................ 1–1

1.3

SERVICE LOG .......................................................................................... 1–2

1.4

SPARE PARTS .......................................................................................... 1–2

1.5

TEST EQUIPMENT ................................................................................... 1–4

1.6

PREVENTIVE MAINTENANCE ................................................................. 1–5

SECTION 2 – TROUBLESHOOTING ......................................................................... 2–1

2.1

GENERAL .................................................................................................. 2–1

SECTION 3 – DESIGN, TEST AND VALIDATION TOOLS ........................................ 3–1

3.1

GENERAL .................................................................................................. 3–1

3.2

INTRODUCTION ....................................................................................... 3–1

3.3

APPLICATION DEVELOPMENT TOOL .................................................... 3–2

3.3.1

AlsDload .......................................................................................... 3–4

3.4

MAINTENANCE MANAGEMENT SYSTEM .............................................. 3–5

3.5

EMBEDDED DATALOGGER ..................................................................... 3–6

SECTION 4 – SYSTEM DIAGNOSTICS ..................................................................... 4–1

4.1

GENERAL .................................................................................................. 4–1

4.2

TROUBLESHOOTING WITH LEDS AND DIAGNOSTIC DISPLAYS ........ 4–1

4.2.1

4.2.2

Vital Board LEDs ............................................................................. 4–2

Non-Vital Board LEDs ................................................................... 4–10

4.3

TROUBLESHOOTING WITH VT100 EMULATION INTERFACE ............ 4–13

4.3.1

Overview ....................................................................................... 4–13

4.3.2

VT100 Terminal Device ................................................................. 4–13

4.3.3

4.3.4

4.3.4.1

4.3.4.2

4.3.4.3

Maintenance ACcess (MAC) Port Connection .............................. 4–14

MAC Port Functionality ................................................................. 4–26

VSP Main MAC interface ...................................................... 4–26

NVSP Main MAC interface .................................................... 4–43

Communications Processor MAC interface ........................... 4–45

4.4

ERROR NUMBERS ................................................................................. 4–47

4.4.1

VSP Main Processor Error Numbers ............................................. 4–47

4.4.2

4.4.3

NVSP Main Processor Diagnostic Code Numbers ........................ 4–49

Communication Processor Error Numbers .................................... 4–56

4.5

NON-VITAL SYSTEM DIAGNOSTICS ON THE NVSP BOARD ............. 4–59

P2521B, Volume 5, Rev. E, November 2013 i Alstom Signaling Inc.

TABLE OF CONTENTS

Topic Page

4.5.1

4.5.2

4.5.3

4.5.4

4.5.4.1

4.5.4.2

4.5.4.3

4.5.4.4

4.5.4.5

4.5.4.6

4.5.4.7

4.5.4.8

4.5.5

4.5.5.1

4.5.6

4.5.7

4.5.8

Using Menus ................................................................................. 4–59

Menu Structure.............................................................................. 4–60

NVSP Main Menu .......................................................................... 4–62

Emulation Menu ............................................................................ 4–64

Emulation Menu Choice: Port ............................................... 4–66

Emulation Menu Choice: Next or Last ................................... 4–67

Emulation Menu Choice: Optns ............................................ 4–69

Emulation Menu Choice: Msg ............................................... 4–70

Emulation/Message Sub-Menu Choice: Post ........................ 4–71

Emulation/Message Sub-Menu Choice: Disp ........................ 4–72

Emulation/Message Sub-Menu Choice: Spcl ........................ 4–73

Emulation/Message Sub-Menu Choice: Mode ...................... 4–74

Emulation Diagnostics Menu ......................................................... 4–77

DataTrain VIII Counts Screen (Emulation Diagnostics) ......... 4–78

Monitor Menu ................................................................................ 4–79

System Configuration Information ................................................. 4–82

System Diagnostics Menu ............................................................. 4–83

4.6

EMBEDDED DATALOGGER (DL) ........................................................... 4–88

4.6.1

General Information ...................................................................... 4–88

4.6.2

4.6.3

4.6.4

Real-Time Clock ............................................................................ 4–88

Memory Usage .............................................................................. 4–89

Directory Frames ........................................................................... 4–90

4.6.5

4.6.6

4.6.7

4.6.8

4.6.9

Log Frames ................................................................................... 4–90

Logging Capacity .......................................................................... 4–91

Data Protection ............................................................................. 4–92

Log Area Reclamation ................................................................... 4–92

System Overloading ...................................................................... 4–92

SECTION 5 – BOARD REPLACEMENT .................................................................... 5–1

5.1

GENERAL .................................................................................................. 5–1

5.2

SYSTEM BOARDS .................................................................................... 5–1

5.3

BOARD REPLACEMENT PROCEDURES ................................................ 5–1

5.4

VITAL BOARD REPLACEMENT ............................................................... 5–2

5.4.1

VSP Board (P/N 31166-427-XX) ..................................................... 5–3

5.4.2

5.4.3

CRG Board (P/N 31166-459-XX) .................................................... 5–4

DI Board (P/N 31166-429-XX)......................................................... 5–4

5.4.4

5.4.5

GTP Board (P/N 31166-434-XX) ..................................................... 5–5

SBO, LDO, ACO, DBO Boards (P/N 31166-430-XX, -431-

XX, -432-XX, -433-XX) .................................................................... 5–5

P2521B, Volume 5, Rev. E, November 2013 ii Alstom Signaling Inc.

TABLE OF CONTENTS

Topic Page

5.4.6

System ID Board (P/N 31166-472-XX) and Vital Interface

Boards (P/N 31166-473-XX and 31166-485-XX) ............................ 5–6

5.5

NON-VITAL BOARD REPLACEMENT ...................................................... 5–7

5.5.1

NVSP Board (P/N 31166-428-XX) .................................................. 5–8

5.5.2

5.5.3

5.5.4

5.5.5

NVSP Board Battery (P/N 52397-011-00) ....................................... 5–9

NVI Boards (P/N 31166-457-XX) .................................................... 5–9

NVO Boards (P/N 31166-458-XX) ................................................. 5–10

NVSP Interface Boards (P/N 31166-474-XX, 31166-475-XX) ....... 5–10

SECTION 6 – VITAL BOARD VERIFICATION ........................................................... 6–1

6.1

GENERAL .................................................................................................. 6–1

6.2

INTRODUCTION ....................................................................................... 6–1

6.3

VITAL INPUT BOARDS ............................................................................. 6–1

6.4

VITAL OUTPUT BOARDS ......................................................................... 6–2

APPENDIX A – DATA LOG SHEET .......................................................................... A–1

P2521B, Volume 5, Rev. E, November 2013 iii Alstom Signaling Inc.

Figure No.

Figure 1–1.

Figure 2–1.

Figure 3–1.

Figure 4–1.

Figure 4–2.

Figure 4–3.

Figure 4–4.

Figure 4–5.

Figure 4–6.

Figure 4–7.

Figure 4–8.

Figure 4–9.

Figure 4–10.

Figure 4–11.

Figure 4–12.

Figure 4–13.

Figure 4–14.

Figure 4–15.

Figure 4–16.

Figure 4–17.

Figure 4–18.

Figure 4–19.

Figure 4–20.

Figure 4–21.

Figure 4–22.

Figure 4–23.

Figure 4–24.

Figure 4–25.

Figure 4–26.

Figure 4–27.

Figure 4–28.

Figure 4–29.

Figure A–1.

LIST OF FIGURES

Title Page

iVPI Rack and Subrack ................................................................... 1–6

General Diagnostic Flowchart ......................................................... 2–1

iVPI / VPI CAAPE/CAA Typical Arrangement ................................. 3–3

VSP Board Troubleshooting Using Board Indications ..................... 4–2

ACO Board Troubleshooting Using Board Indications .................... 4–3

CRG Board Troubleshooting Using Board Indications .................... 4–4

DBO Board Troubleshooting Using Board Indications .................... 4–5

DI Board Troubleshooting Using Board Indications ......................... 4–6

GTP Board Troubleshooting Using Board Indications ..................... 4–7

LDO Board Troubleshooting Using Board Indications ..................... 4–8

SBO Board Troubleshooting Using Board Indications ..................... 4–9

NVSP Board Troubleshooting Using Board Indications ................ 4–10

NVI Board Troubleshooting Using Board Indications .................... 4–11

NVO Board Troubleshooting Using Board Indications .................. 4–12

Menu Tree ..................................................................................... 4–61

NVSP Main Menu .......................................................................... 4–62

Emulation Menu ............................................................................ 4–64

Emulation Menu – Select the Serial Port ....................................... 4–66

Example Emulation Menu – View a Station's Messages ............... 4–67

Emulation Menu – View Port Setup ............................................... 4–69

Emulation Menu – Message Sub-Menu ........................................ 4–70

Post a Control Message ................................................................ 4–71

Display Messages in Real-Time .................................................... 4–72

Post a Special Message ................................................................ 4–73

Select the Message Display Mode ................................................ 4–74

Display Messages – New Hex Display Option .............................. 4–76

Display Messages – Binary Display Option ................................... 4–76

DataTrain VIII Diagnostics Menu ................................................... 4–77

DataTrain VIII Counts Screen ....................................................... 4–78

Data Monitor Screen ..................................................................... 4–79

NVSP System Configuration Screen ............................................. 4–82

NVSP System Diagnostics Menu .................................................. 4–83

VSP Log Sheet ................................................................................ A–1

P2521B, Volume 5, Rev. E, November 2013 iv Alstom Signaling Inc.

Table No.

Table 3–1.

Table 4–1.

Table 4–2.

Table 4–3.

Table 4–4.

Table 4–5.

Table 4–6.

Table 4–7.

Table 4–8.

Table 4–9.

Table 4–10.

Table 4–11.

Table 4–12.

Table 4–13.

Table 4–14.

Table 4–15.

Table 4–16.

Table 4–17.

Table 4–18.

Table 4–19.

Table 4–20.

Table 4–21.

Table 4–22.

Table 5–1.

Table 5–2.

Table 5–3.

Table 5–4.

Table 5–5.

Table 5–6.

Table 5–7.

Table 5–8.

Table 5–9.

Table 5–10.

Table 5–11.

Table 6–1.

Table 6–2.

LIST OF TABLES

Title Page

Design Validation Tool Part Numbers ............................................. 3–1

DB9 to DB25 Pin Cabling Connections ......................................... 4–15

Direct Connection Procedure ........................................................ 4–15

VSP Main Processor MAC Port Keyboard Commands ................. 4–27

Start-up Diagnostics Troubleshooting ........................................... 4–32

SYS WARNING Diagnostics ......................................................... 4–36

ERROR ALERT Message Troubleshooting ................................... 4–40

NVSP Main Processor MAC Port Keyboard Commands............... 4–44

Communication Processor MAC Port Keyboard Commands ........ 4–45

VSP Main Processor Error Numbers ............................................. 4–47

NVSP Main Processor Diagnostic Code Numbers ........................ 4–49

Communication Processor Error Numbers .................................... 4–56

NVSP Menu Access ...................................................................... 4–59

Main Menu Choices ...................................................................... 4–63

Emulation Menu Choices .............................................................. 4–65

Hexadecimal to Binary Conversion ............................................... 4–68

Message Display Modes ............................................................... 4–75

Monitor Menu Choices .................................................................. 4–80

Data Monitor Status Indicators ...................................................... 4–81

Message Descriptors..................................................................... 4–81

System Diagnostic Menu Choices ................................................. 4–84

Secondary Diagnostics Menu Choices .......................................... 4–86

DataLogger Memory Usage .......................................................... 4–89

VSP Board Replacement Procedure ............................................... 5–3

CRG Board Replacement Procedure .............................................. 5–4

DI Board Replacement Procedure .................................................. 5–4

GTP Board Replacement Procedure ............................................... 5–5

SBO, LDO, ACO, DBO Board Replacement Procedure .................. 5–5

System ID Board and Vital Interface Board Replacement

Procedure ........................................................................................ 5–6

NVSP Board Replacement Procedure ............................................ 5–8

NVSP Board Battery Replacement Procedure ................................ 5–9

NVI Board Replacement Procedure ................................................ 5–9

NVO Board Replacement Procedure ............................................ 5–10

NVSP Interface Board Replacement Procedure ........................... 5–10

Vital Input Board Functionality Test Procedure ............................... 6–1

Vital Output Board Functionality Test Procedure ............................ 6–2

P2521B, Volume 5, Rev. E, November 2013 v Alstom Signaling Inc.

THIS PAGE INTENTIONALLY LEFT BLANK.

P2521B, Volume 5, Rev. E, November 2013 vi Alstom Signaling Inc.

Introduction

SECTION 1 – INTRODUCTION

1.1 GENERAL

This manual contains specific procedures for the maintenance and troubleshooting of the iVPI system.

WARNING

Disruption of iVPI operation poses a potential threat to rail safety. Before shutting down an interlocking for any reason, the railroad dispatcher in charge of the affected route(s) must be notified. Take all steps necessary to ensure the safe passage of traffic is maintained.

1.2 MANUAL SET ORGANIZATION

This manual is part of a five volume set supporting the iVPI system. The set is organized as follows:

• Volume 1, Installation, Operation, and Theory Manual, includes general overview of the field installation and setup of the iVPI system; including capacity guidelines and allowable board combinations, system operation, and theory of operation.

• Volume 2, Subrack Configuration, describes the subrack configuration including cables and power supplies.

• Volume 3, Vital Subsystem, includes the Vital subsystem board drawings and board reference data.

• Volume 4, Non-Vital Subsystem, includes non-vital subsystem board drawings and board reference data.

• Volume 5, Maintenance and Troubleshooting, is this document. It describes system maintenance and troubleshooting, including discussion of diagnostics and references for the applicable software and hardware manuals.

P2521B, Volume 5, Rev. E, Nov/13 1–1 Alstom Signaling Inc.

Introduction

1.3 SERVICE LOG

Keep a service log on the iVPI system to record test results and keep track of any service performed. A log should describe any malfunctions, corrective action taken and all preventive maintenance performed. The log can also be used to maintain a spare parts inventory by recording the quantities and type of printed circuit boards and spare parts used as replacements.

1.4 SPARE PARTS

WARNING iVPI contains special safety circuit components which must only be replaced by components specified by the Alstom part number.

These original-design replacement parts are manufactured to the same standards as the original parts; their performance being verified. The use of replacement parts that are not of the same Alstom part number could potentially impair the safe performance of the system.

The railroad or transit system authority and the manufacturer of an aftermarket (i.e., non-Alstom designated) part assume the responsibility that the part will not adversely affect the safe performance of the system. The authority and the manufacturer of the aftermarket part must analyze and certify in writing that use of the part will not result in a failure of the system to comply with safety regulations and safety performance. Completion of such an analysis and certification is considered due diligence and standard practice, will not be reviewed or approved by Alstom, and neither absolves the authority and aftermarket part manufacturer of responsibility nor implies approval by Alstom to use such an aftermarket part. The responsibility of any consequences resulting from using such a part remains with the authority and part manufacturer.

WARNING

Only Alstom VRD relay (P/N 56001-787-05) is to be used with the Alstom iVPI system. Alstom products are designed to function within all-Alstom systems. The introduction of non-Alstom products into an Alstom iVPI system could have unintended and unforeseeable safety consequences

P2521B, Volume 5, Rev. E, Nov/13 1–2 Alstom Signaling Inc.

Introduction

The iVPI system is designed for long life and trouble-free operation. This equipment, however, as with all electronic equipment, may have an occasional component failure.

Order spare boards from Alstom based on projected needs. The recommended spare parts to support one iVPI module are:

• A spare lithium battery (P/N 52397-011-00)

Boards with static-sensitive components should be stored, transported, or shipped in conductive Velostate bags and have printed circuit Contabs attached. Leave the printed circuit Contabs on all boards except for testing and installation.

P2521B, Volume 5, Rev. E, Nov/13 1–3 Alstom Signaling Inc.

Introduction

1.5 TEST EQUIPMENT

Field maintenance of the iVPI system requires little in the way of external test equipment. Built-in circuitry tests critical system functions and generate the appropriate status messages on an externally connected PC. In addition, all the circuit boards include LED indicators visible from the front of the Subrack that reveal the operating status of the board.

Besides these automated test tools, a standard multi-meter (Fluke Model 87 or similar) is helpful for checking the level of operating voltages, current levels, and for continuity checks.

CAUTION

Verify that all power to the iVPI system is removed before removal or installation of any boards. Failure to do so may result in damage to board components.

P2521B, Volume 5, Rev. E, Nov/13 1–4 Alstom Signaling Inc.

Introduction

1.6 PREVENTIVE MAINTENANCE

No periodic adjustments are required to sustain continuous iVPI system operation.

Check the module periodically for damaged hardware or loose connections, broken or corroded wiring, signs of overheating and build-up of dust or foreign material. Make sure that all boards are seated in the module properly.

Check the power supply voltages on the power isolation unit on the back of the system

Subrack. The input voltage to the power isolation unit (measured at TB1-2 positive and

TB1-1 negative) should be 9-16 VDC. The output of the power isolation unit (measured at test points TB8 positive and TB11 negative) should be 9-14 VDC.

Use a PC running VT100 terminal emulation software and a VSP board to interrogate the system for system diagnostics. For example, a failure may cause a "SYS

WARNING" status message to be displayed, which may indicate outputs that fail in a non-fatal fashion such as open lamp filaments.

Check the board LED status indicators for expected signals (refer to "Troubleshooting with LED's" later in this volume).

Before starting any detailed troubleshooting, check for simple problems first such as blown fuses, loose plugs, dirty board contacts, or improper voltages.

In addition, if the system has been serviced or turned off and does not restart, check the following prior to beginning detailed troubleshooting:

• Vital Input and Output boards are in their respective slots.

• Input power to the VSP board is between 9.0 and 15.0 volts (measured at P3-D24 and P3-Z24).

• Energizing the VRD Relay causes voltage between 9.0 to 16.0 volts to be applied to the "VRDFRNT-DI" designated Vital input (if configured).System Terms

The iVPI System is modular in design, implemented in one or more Subracks with a set of plug-in eurocard style printed circuit boards applied in varying quantities to meet the needs of specific applications.

The terminology used to define the Subrack and its components is as follows:

• A Subrack is a Chassis with Motherboard

• A System is one or more Subracks filled with the appropriate boards for the application

• When a System is configured with more than one Subrack populated with boards, the individual populated Subracks are Subsystems

P2521B, Volume 5, Rev. E, Nov/13 1–5 Alstom Signaling Inc.

Introduction

Rack

System

Motherboard

Figure 1–1. iVPI Rack and Subrack

P2521B, Volume 5, Rev. E, Nov/13 1–6 Alstom Signaling Inc.

Troubleshooting

SECTION 2 – TROUBLESHOOTING

2.1 GENERAL

This section provides troubleshooting flowcharts for the iVPI system. To troubleshoot,

refer to Figure 2–1, a three sheet general diagnostic flowchart.

At the entrance rack, verify that the problem is actually iVPI related, not field apparatus related.

Confirm that the iVPI system is operating by checking VSP board LEDs and verifying

VT-100 Emulator can communicate with VSP board.

If the VSP board LEDs indicate that Boolean equation processing is taking place, then look at the LEDs on the other boards.

If the VSP board is not running, look at the VSP board hardware and software.

Check the NVSP board

LEDs to determine if there are non-vital communication problems.

Check the VSP board

LEDs to verify that the

VRD Relay is being driven (checkwords are

OK).

Check the DI, ACO,DBO,

SBO, LDO, CRG, GTP board address LEDs to verify that the VSP is communicating to the

I/O board ports.

Change the VSP board or reinstall Flash.

'A'

VT-100 Emulation can provide key information

to further define the problem.

'B'

Figure 2–1. General Diagnostic Flowchart

P2521B, Volume 5, Rev. E, Nov/13 2–1 Alstom Signaling Inc.

Troubleshooting

'A'

From Sheet 1

NVSP LEDs

Verify a non-vital communication problem by observing the

NVSP board LEDs.

Use board LEDs to verify that the proper port is being addressed.

SUMMARY: If there are communications problems, look at board LEDs first.

Study the CAA reports to verify the ports used and the defined protocol. With the diagnostic Query command, look at the Vital memory location to check if the message is successfully being transferred from the NVSP board to the

VSP board.

For additional troubleshooting, special software (Tracker, MMS) can be used to look at the serial output messages.

Figure 2–1. General Diagnostic Flowchart (Cont.)

P2521B, Volume 5, Rev. E, Nov/13 2–2 Alstom Signaling Inc.

Troubleshooting

'B'

From Sheet 1

VSP LEDs

Verify that the Input and Output boards are being addressed by observing the VSP board LEDs .

If boards are being addressed, use a VT-100

Emulator to check for port specific error messages.

Check the BOOLS for a circuit explanation for the failure. Interrogate memory locations with a

VT-100 Emulator.

If no boards are being addressed, check the cabling and hardware as appropriate.

Use ####Q and current /.lvc file printout to check the BOOLS. Note that the application logic may not let the system actually perform the requested tasks.

For example, the interlocking will not throw switches because the track circuit is occupied (down). Don’t focus on the iVPI itself, focus on the affected system circuits.

Using board reports, verify voltages supplied to the power groups on the output boards.

SUMMARY: Once at the output level, determine if the system is trying to turn on or read the correct port. If not, this indicates further problems. If the VT-100

Emulator shows memory location becoming true, then the port is being forced to turn on.

Be aware that the application logic may prevent an action from occurring by system design.

Figure 2–1. General Diagnostic Flowchart (Cont.)

P2521B, Volume 5, Rev. E, Nov/13 2–3 Alstom Signaling Inc.

Troubleshooting

THIS PAGE INTENTIONALLY LEFT BLANK.

P2521B, Volume 5, Rev. E, Nov/13 2–4 Alstom Signaling Inc.

Design, Test and Validation Tools

SECTION 3 – DESIGN, TEST AND VALIDATION TOOLS

3.1 GENERAL

This section describes the design and validation tools available for the iVPI system.

3.2 INTRODUCTION

The Vital system performs all Vital logic associated with interlocking control (switch control, locking, and signal control). At the user's option, this logic can be written in the form of Boolean equations or drawn as relay circuits in AREMA Drop-Line format,

AREMA Straight Line format or as commercial PLC format that emulate traditional relay logic. No special programming language is used in the application thus allowing the source file(s) to be easily understood by a signal engineer.

After the Boolean equations or relay diagrams have been created by the Signal

Engineer, the Computer Aided Application (CAA) software package is used to compile the equations into machine readable code for installation and verification on the application FLASH EPROM to be installed on the appropriate System's VSP board.

The non-vital system performs similar functions on all non-vital logic associated with interlocking control (switch position requests, signal clear requests, Local Control interface, communications to the OCC, local data logging).

Through the use of AlsDload, the VSP and NVSP applications can be programmed without removing the FLASH EPROM.

Table 3–1. Design Validation Tool Part Numbers

Description

CAAPE

“YYY” in part number = version number

“XX” in part number = customer ID

MMS (min. requirements Windows™ NT4 sp6 / 2000 / XP)

MMS Server/Editor (Windows 7 Professional, 32 bit)

Part Number

31754-YYY-XX

51795-063-00

51795-081-00

P2521B, Volume 5, Rev. E, Nov/13 3–1 Alstom Signaling Inc.

Design, Test and Validation Tools

3.3 APPLICATION DEVELOPMENT TOOL

The Computer-Aided Application Programming Environment (CAAPE) is a comprehensive set of development tools for creating iVPI Vital and non-vital applications. These tools are integrated together within a Windows based development environment for easy access.

The CAAPE package is intended for use by Alstom signal engineers, by railroad and transit signal engineers, and by third party signal engineering consultants. The iVPI

CAAPE toolset is built on the same stable foundation that has become an industryaccepted favorite, and is backward compatible to all previous versions.

The top-level CAAPE program provides access to available tools and manages application data through the use of projects. A project is a collection of files describing one or more applications. Some of these files, such as report and prom files are meant to be directly accessible by the user; others are for internal use and are readable only by CAAPE. Typically, a CAAPE project describes all the applications in a particular iVPI

System.

All the files for a given project are contained in a single directory. A single main project file acts as a directory to the rest of the files in the project and specifies the CAAPE options selected by the user for the project. When the CAAPE opens a project it reads the main file to determine the full list of files and options in the project. Tools to assist in software configuration control are included within the CAAPE package.

The lower-level tools such as compilers and application data verifiers, which are tied to a particular version of iVPI system software, comprise a CAA package. The CAAPE can provide access to the tools in multiple CAA packages (Windows versions only). The user can select which set of compiler and data verifier tools to use for a particular application by selecting a specific compiler version based on which version of Vital system software is used. This allows support of older versions of the VPI product line as well as newer versions in the same development environment.

P2521B, Volume 5, Rev. E, Nov/13 3–2 Alstom Signaling Inc.

Design, Test and Validation Tools

CAAPE

PROJECT

CONFIGURATION

GRAPHICAL

HARDWARE

GRAPHICAL

LOGIC

GRAPHICAL

SIMULATOR iVPI CAA

COMPARE iVPI

SYSTEM SW iVPI CAA

COMPARE iVPI

SYSTEM SW iVPI CAA

COMPARE iVPI

SYSTEM SW

GRAPHICAL

UTILITIES

GRAPHICAL

ADV

Figure 3–1. iVPI / VPI CAAPE/CAA Typical Arrangement

APPLICATION

LOGIC

SOFTWARE

DOWNLOAD

UTILITIES

P2521B, Volume 5, Rev. E, Nov/13 3–3 Alstom Signaling Inc.

Design, Test and Validation Tools

3.3.1 AlsDload

AlsDload is a tool for programming application and system software on VPI, iVPI, GTP and PGK boards.

AlsDload provides the following capabilities:

• Download of application and/or system software from files on the PC to the programmable memory on the board

• Upload of application and/or system software from the programmable memory on the board to files on the PC

• Verification that board configuration data is identical to that in selected files

• Access to board diagnostics

• Basic VT100 terminal emulation

• Reading FSSVT settings configured in the application or a CAAPE-generated file

• Changing FSSVT settings

• Saving FSSVT settings in a file or to a board

P2521B, Volume 5, Rev. E, Nov/13 3–4 Alstom Signaling Inc.

Design, Test and Validation Tools

3.4 MAINTENANCE MANAGEMENT SYSTEM

The Maintenance Management System (MMS) is an Alstom diagnostic tool that can remotely monitor each iVPI Vital and non-vital networked system.

MMS is a graphical diagnostic and maintenance application that uses a graphical track layout to dynamically record and display the iVPI diagnostic status, the status of linked iVPI variables and play back recorded data.

Additional tools are available to manage diagnostics, configuration, event and data logs, schedule maintenance tasks, and view, record and play back iVPI application variable data.

For more information on this Alstom tool, refer to Alstom publication P2509

Maintenance Management System for Alstom Vital Processor Interlocking Systems

(VPI, VPI II, iVPI) or P2528 MMS Client/Server for Alstom Vital Processor Interlocking

Systems (VPI II/iVPI).

P2521B, Volume 5, Rev. E, Nov/13 3–5 Alstom Signaling Inc.

Design, Test and Validation Tools

3.5 EMBEDDED DATALOGGER

A feature provided by the non-vital Subsystem, the embedded data logger permits viewing of time stamped events in log form or in near real-time chart recorder form.

Multiple views are provided.

Key features are:

• View Events Historical, Real-Time

• Filters Unwanted Info

• Saves Data In Nonvolatile Memory

• Timeline and Timestamp Views

• Record time-stamped events to on-board battery-backed memory

• Event capacity is typically several days

• Automatically detect a change to a large number of user-specified application parameters, and record when changes occur in real-time

• On-line help is available to assist the operator

P2521B, Volume 5, Rev. E, Nov/13 3–6 Alstom Signaling Inc.

System Diagnostics

SECTION 4 – SYSTEM DIAGNOSTICS

4.1 GENERAL

WARNING

Pressing either of the reset (RST) pushbuttons (main or com) on the front panel interrupts the operation of the iVPI system. Disruption of iVPI operation poses a potential threat to rail safety. Before shutting down an interlocking for any reason, notify the railroad dispatcher in charge of the affected route(s).

Take all steps necessary to ensure that safe passage of traffic is maintained.

This section discusses the system diagnostics available on the iVPI system, including:

• Troubleshooting with board LEDs

• Vital subsystem diagnostics with VT100 Emulation with the VSP board

• Non-vital system diagnostics with the NVSP board

4.2 TROUBLESHOOTING WITH LEDS AND DIAGNOSTIC DISPLAYS

All iVPI boards contain a HEALTH LED that displays in three possible colors to indicate board health

• Green = Board OK

• Yellow = Board Warning

• Red = Board Error

For all iVPI boards:

• If the HEALTH LED is yellow or red, use System Diagnostics to determine the specific error or warning.

• If no LEDs are lit, verify both the system and the board have power.

• If the LED status never changes, verify communication ports.

Board illustrations along with descriptions of how to use the information on board edges

for troubleshooting are provided in Figure 4–1 through Figure 4–8 for Vital boards and

Figure 4–9 through Figure 4–11 for non-vital boards.

For NVSP, NVI and NVO boards:

• If the board is used in a non-vital-only system (VSP board is not configured in the system) and the HEALTH LED is not lit, verify the NVSP FPGA device U42 firmware 39780-099-01 is revision H or later. If not, contact Alstom Customer

Service to arrange a board upgrade.

P2521B, Volume 5, Rev. E, Nov/13 4–1 Alstom Signaling Inc.

System Diagnostics

4.2.1 Vital Board LEDs

Function

Main Processor Receiving Data

Com Processor Receiving Data

Main Processor Transmitting Data

Com Processor Transmitting Data

Link 1 Active LAN 1 Active

Link 2 Active

LAN 2 Active

Main Processor Running

Com Processor Running

Main Processor Reset

Main USB Port Active

Com Processor Reset

Com USB Port Active

To troubleshoot VSP:

- If it is not green, check if the Main or Com

DIAG 7-Segment Displays are indicating

Warning or Error.

- Use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If there are no error or warning indications, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

These LEDs are lit when their respective functions are detected.

Main Serial Port

Use this toggle switch to select a main processor diagnostic display.

I/O Processor Operating, Right

Use Reset Pushbutton to reset the main processor portion of the VSP.

Main USB Port

Selection Button For Scrolling Through Main Diagnostic Display

Main Processor 7-Segment Display 0= Normal Operation

1=Warning

2= Error

Reset Pushbutton, Main

VRD Processor Operating

I/O Processor Operating, Left

Board Health LED Green (OK)

Yellow (Warning)

Red (Error)

Use System

Diagnostics or MMS to determine specific warning or error.

Com Serial Port

Use this toggle switch to select a communication processor diagnostic display.

Com USB Port

Selection Button For Scrolling Through Com

Diagnostic Display

Com Processor 7-Segment Display 0= Normal Operation

1=Warning

2= Error

Reset Pushbutton, Com

Use Reset Pushbutton to reset the communications processor portion of the VSP.

Figure 4–1. VSP Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–2 Alstom Signaling Inc.

These LEDs are lit when their respective functions are activated.

To troubleshoot ACO:

1) Verify the Health LED is green.

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

System Diagnostics

Function

Output 1 Active

Output 2 Active

Output 3 Active

Output 4 Active

Output 5 Active

Output 6 Active

Output 7 Active

Output 8 Active

Group A Outputs

Group B Outputs

Board is Active, Data is Being Written or Read

Board Health LED

Use System Diagnostics or

MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Figure 4–2. ACO Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–3 Alstom Signaling Inc.

System Diagnostics

Output 1 Active

Output 2 Active

Output 3 Active

Output 4 Active

Output 5 Active

Output 6 Active

Output 7 Active

Output 8 Active

1) Verify the Health LED is green.

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

These LEDs are lit when their respective functions are activated.

Port Number Display

Code Rate Display

Reset Pushbutton, Board

Board Health LED

Use System Diagnostics or

MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Selection Button For Scrolling Through Ports

Serial Port

Reset Pushbutton, USB

USB Port

Figure 4–3. CRG Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–4 Alstom Signaling Inc.

These LEDs are lit when their respective functions are activated.

System Diagnostics

Function

Output 1 Active

Output 2 Active

Output 3 Active

Output 4 Active

Output 5 Active

Output 6 Active

Output 7 Active

Output 8 Active

Group A Outputs

Group B Outputs

To troubleshoot DBO:

1) Verify the Health LED is green.

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

Board is Active, Data is Being Written or Read

Board Health LED

Use System Diagnostics or

MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Figure 4–4. DBO Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–5 Alstom Signaling Inc.

System Diagnostics

To troubleshoot DI:

1) Verify the Health LED is green.

Function

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

Input 1 Active

Input 2 Active

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

Input 3 Active

Input 4 Active

Input 5 Active

Input 6 Active

Input 7 Active

Input 8 Active

These LEDs are lit when their respective functions are activated.

Board is Active, Data is Being Written or Read

Board Health LED

Use System Diagnostics or

MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Input 9 Active

Input10 Active

Input 11 Active

Input 12 Active

Input 13 Active

Input 14 Active

Input 15 Active

Input 16 Active

These LEDs are lit when their respective functions are activated.

Figure 4–5. DI Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–6 Alstom Signaling Inc.

System Diagnostics

Function

Track One Transmitting

Track One Receiver Test

Track One Code 5 Transmitting

Use these track monitor and common pushbuttons to select the data to be displayed on the

Track 1 (East) RCV and XMIT

7-Segment Displays.

Ethernet Link Detected

Cab Signal 1 Out

GTP Requires Maintenance Attention

West Stick Circuit Picked

Use this toggle switch to select a track.

Track Two Transmitting

Track Two Receiver Test

Track Two Code 5 Transmitting

Use these track monitor and common pushbuttons to select the data to be displayed on the

Track 2 (West) RCV and XMIT

7-Segment Displays.

Cab Signal 3 Out

To troubleshoot GTP:

Track One Receiving

Track One Trouble Code Generated

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

Track One Receive Code

Track One Code 5 Receiving

Track One Transmit Code

Track One Monitor Test Point

Track One Common Test Point

USB Bus Activity

USB Port

Ethernet Activity Detected

These LEDs are lit when their respective functions are detected.

Cab Signal 2 Out

Serial Port

Extra User Defined LED

East Stick Circuit Picked

Board Health LED

Use System Diagnostics or

MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Enter/Select Toggle Switch

Board is Active, Data is Being Written or Read

Track Two Receiving

Track Two Trouble Code Generated

Track Two Receive Code

Track Two Code 5 Receiving

Track Two Transmit Code

Track Two Monitor Test Point

Track Two Common Test Point

Cab Signal 4 Out

Figure 4–6. GTP Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–7 Alstom Signaling Inc.

These LEDs are lit when their respective functions are activated.

Use this toggle switch to select an output.

Use this pushbutton to clear the data in the

7-Segment Display

Use this pushbutton to reset the board.

System Diagnostics

Function

Output 1 Active

Output 2 Active

Output 3 Active

Output 4 Active

Output 5 Active

Output 6 Active

Output 7 Active

Output 8 Active

Group A Outputs

Group B Outputs

Board is Active, Data is Being Written or Read

Error Detected

Output # Of Data Being Displayed

First Digit of Output Data

Second Digit of Output Data

Board Health LED

Use System Diagnostics or

MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Enter/Select Toggle Switch

Clear Pushbutton

Reset Pushbutton

To troubleshoot LDO:

1) Verify the Health LED is green.

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) Verify the ERROR LED is not illuminated.

- If it is illuminated use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

3) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

Figure 4–7. LDO Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–8 Alstom Signaling Inc.

These LEDs are lit when their respective functions are activated.

System Diagnostics

Function

Output 1 Active

Output 2 Active

Output 3 Active

Output 4 Active

Output 5 Active

Output 6 Active

Output 7 Active

Output 8 Active

Group A Outputs

Group B Outputs

To troubleshoot SBO:

1) Verify the Health LED is green.

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

Board is Active, Data is Being Written or Read

Board Health LED

Use System Diagnostics or

MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Figure 4–8. SBO Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–9 Alstom Signaling Inc.

System Diagnostics

4.2.2 Non-Vital Board LEDs

Function

Main Processor Serial Port Receiving Data

Com Processor Serial Port Receiving Data

Serial Port 1 Invalid Address In Received Message

Serial Port 1 Error In Received Message

Not Used (reserved for future use)

Serial Port 2 Invalid Address In Received Message

Serial Port 2 Error In Received Message

Serial Port 3 Receiving Data

Use this switch to select the front or back RS-232 Port.

Use this toggle switch to select a Serial Port.

NVSP Processor Running

Function

Main Processor Serial Port Transmitting Data

Comm Processor Serial Port Transmitting Data

Serial Port 1 Valid Address Message Received

Serial Port 1 Transmitting Data,

Not Used (reserved for future use)

Serial Port 2 Valid Address Message Received

Serial Port 2 Transmitting Data

Serial Port 3 Transmitting Data

To troubleshoot NVSP:

1) Verify the Health LED is green.

- If it is not green, check if the Main or Com DIAG 7-Segment

Displays are indicating Warning or Error.

- Use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If there are no error or warning indications, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

These LEDs are lit when their respective functions are activated.

MAIN Serial Port

RS-232 Port Selection Switch F (Front RS-232 Port)

B (Back RS-232 Port)

MAIN USB Port

Enter/Select Toggle Switch

NVSP Processor 7-Segment Display 0= Normal Operation

1=Warning

2= Error

Reset Pushbutton, Main

NVSP Processor Reset

Board Health LED Green (OK)

Yellow (Warning)

Red (Error)

Use System Diagnostics or

MMS to determine specific warning or error.

Com Serial Port

Link 1 Active

Link 2 Active

Com Processor Running

NVSP USB Port Active

LAN 1 Active

LAN 2 Active

Com Processor Reset

Com USB Port Active

Com USB Port

Com Processor 7-Segment Display 0= Normal Operation

1=Warning

2= Error

Reset Pushbutton, Com

Figure 4–9. NVSP Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–10 Alstom Signaling Inc.

Input 1 Active

Input 2 Active

Input 3 Active

Input 4 Active

Input 5 Active

Input 6 Active

Input 7 Active

Input 8 Active

System Diagnostics

Input 9 Active

Input10 Active

Input 11 Active

Input 12 Active

Input 13 Active

Input 14 Active

Input 15 Active

Input 16 Active

To troubleshoot NVI:

1) Verify the Health LED is green.

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

These LEDs are lit when their respective functions are activated.

Board is Active, Data is Being Written or Read

Board Health LED

Use System Diagnostics or MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Input 17 Active

Input 18 Active

Input 19 Active

Input 20 Active

Input 21 Active

Input 22 Active

Input 23 Active

Input 24 Active

Input 25 Active

Input 26 Active

Input 27 Active

Input 28 Active

Input 29 Active

Input 30 Active

Input 31 Active

Input 32 Active

These LEDs are lit when their respective functions are activated.

Figure 4–10. NVI Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–11 Alstom Signaling Inc.

Output 1 Active

Output 2 Active

Output 3 Active

Output 4 Active

Output 5 Active

Output 6 Active

Output 7 Active

Output 8 Active

System Diagnostics

Output 9 Active

Output10 Active

Output 11 Active

Output 12 Active

Output 13 Active

Output 14 Active

Output 15 Active

Output 16 Active

To troubleshoot NVO:

1) Verify the Health LED is green.

- If it is not green, use System Diagnostics or MMS to determine and troubleshoot specific warning or error.

2) If the HEALTH LED is green, but an LED is not indicating as expected, troubleshoot the source, board connections, and wiring.

These LEDs are lit when their respective functions are activated.

Board is Active, Data is Being Written or Read

Board Health LED

Use System Diagnostics or MMS to determine specific warning or error.

Green (OK)

Yellow (Warning)

Red (Error)

Output 17 Active

Output 18 Active

Output 19 Active

Output 20 Active

Output 21 Active

Output 22 Active

Output 23 Active

Output 24 Active

Output 25 Active

Output 26 Active

Output 27 Active

Output 28 Active

Output 29 Active

Output 30 Active

Output 31 Active

Output 32 Active

These LEDs are lit when their respective functions are activated.

Figure 4–11. NVO Board Troubleshooting Using Board Indications

P2521B, Volume 5, Rev. E, Nov/13 4–12 Alstom Signaling Inc.

System Diagnostics

4.3

4.3.1

TROUBLESHOOTING WITH VT100 EMULATION INTERFACE

Overview

Both the VSP and the NVSP have two Maintenance ACcess (MAC) ports, one for the

Main (application) processor, and one for the Communications processor. Each MAC port provides access to diagnostic information related to the associated function in its subsystem. All MAC ports are accessible via clearly marked connectors on the boards’

front panel (see Figure 4–1 and Figure 4–9) and are designed to operate using VT100

terminal interface.

4.3.2 VT100 Terminal Device

A VT100 compatible (ANSI standard X3.64-1979) terminal device can be one of the following:

• A physical VT100 compatible terminal unit

• Any device capable of emulating a VT100 terminal via an RS-232 compatible serial port

• A Windows XP 32-bit workstation with an Alstom USB Serial Driver installed (see

Table 4–2 for instructions)

• A Windows XP 32-bit workstation with the AlsDload utility installed

• An MMS workstation connected via a MAC port

Note: If MMS is configured to communicate over an Ethernet connection with the iVPI system, use either of the direct

connection options described in 4.3.3 to utilize the VT100

emulation interface.

The VT100 Emulator is necessary to access the diagnostic functions available via the iVPI MAC ports. These functions are used to report system status and for manual control of an iVPI system.

The required VT100 setup is: 24 lines by 80 columns, 19200 baud (typical – may be configured differently on NVSP by user), 8 data bits, 1 stop bit, no parity, and no flow control.

Alstom recommends using AlsDload software or another VT100 emulation software package that allows capture of the serial data stream. Display modes showing the codeline's traffic can be invoked, and the capture of displayed information to a file allows for further analysis at a future date.

P2521B, Volume 5, Rev. E, Nov/13 4–13 Alstom Signaling Inc.

System Diagnostics

4.3.3 Maintenance ACcess (MAC) Port Connection

Alstom recommends using a battery-operated laptop PC with an appropriate software

package installed (see Section 4.3.2) as a VT100 terminal device in order to avoid

creating multiple paths to ground.

WARNING

To prevent multiple paths to ground, a ground isolation plug (converts 3 prong to 2 prong) is required on the 120 VAC connection of the PC running

VT100 emulation software or the VT100 Emulator.

CAUTION

When a laptop is connected to the system, do not ground the laptop. If another peripheral is plugged into the laptop, such as a printer, isolation is breached.

The following equipment is required for correct operation of the MAC port:

• A VT100 compatible terminal (ANSI standard X3.64-1979) running VT100 emulation

software. See Section 4.3.2 for more information.

• For an RS-232/DB9 direct connection, a standard EIA-232 null modem cable no longer than 25 feet connected between the VT100 terminal or PC running VT100 emulation software and the MAC port on the NVSP Board. See Table 4–1 for cabling details.

• For a USB direct connection, a Type B USB cable

• Proper application documentation for the location of interest

There are two direct connection options available:

• RS-232/DB9 Connection: Use this option if the VT100 Emulator has an RS-

232/DB9 connector; the VT100 Emulator connects to the Maintenance Access

(MAC) serial port on the VSP or NVSP board

• USB Connection: Use this option if the VT100 Emulator only has a USB port; the

VT100 Emulator connects to the USB port on the VSP or NVSP board

Follow the steps in Table 4–2 to directly connect the VT100 Emulator to the iVPI system

via HyperTerminal.

P2521B, Volume 5, Rev. E, Nov/13 4–14 Alstom Signaling Inc.

System Diagnostics

DB9

(VSP or NVSP)

2 (RX)

3 (TX)

5 (GND)

Table 4–1. DB9 to DB25 Pin Cabling Connections

Terminal or

Computer (DB25)

2 (TX)

3 (RX)

7 (GND)

DB9

(VSP or NVSP)

2 (RX)

3 (TX)

5 (GND)

Terminal or

Computer (DB-9)

3 (TX)

2 (RX)

5 (GND)

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

1 Depending on the connection option used, connect the appropriate cable to the

VT100 Emulator and the iVPI system (NVSP board connection pictured below).

See Section 4.3.3 for cable requirements.

EIA-232

NULL

MODEM

CABLE

TYPE B

USB

CABLE

MAC PORT, MAIN

USB PORT, MAIN

MAC PORT, COMMUNICATION (COM)

PC With VT-100

Emulation Software

USB PORT, COMMUNICATION (COM)

NVSP Board

• USB Direct Connection: For the USB direct connection, the Alstom CPU2

CP210x USB to UART Bridge driver is required. This driver is automatically pre-installed when AlsDload is installed. If this driver is not pre-installed, go

to Step 2. If this driver is pre-installed, skip to Step 6.

• RS-232/DB9 Direct Connection: If using this option, skip to Step 9.

P2521B, Volume 5, Rev. E, Nov/13 4–15 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

2 Insert CD-ROM P/N 51795-084-02 into the CD-ROM drive on the VT100

Emulator.

This CD-ROM contains the USB driver. If necessary, contact Alstom Customer

Service at 1-800-717-4477 to request the CD-ROM.

3 After the driver pre-installation process is complete, connect a USB cable between the VT100 Emulator PC and the board. The Found New Hardware

Wizard opens to complete the driver installation.

When prompted to run Windows Update, select the No, not this time option.

Click Next.

P2521B, Volume 5, Rev. E, Nov/13 4–16 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

4 The Install Software window opens.

Select the Install the software automatically option.

Click Next. The installation continues.

5 The Installation Complete window opens.

Click Finish to close the wizard.

P2521B, Volume 5, Rev. E, Nov/13 4–17 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

6 Identify the COM Port number assigned to the new driver.

Right-click on My Computer and select Properties. The System Properties window opens.

Select the Hardware tab.

P2521B, Volume 5, Rev. E, Nov/13 4–18 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

7 On the Hardware tab, click the Device Manager button.

The Device Manager window opens.

P2521B, Volume 5, Rev. E, Nov/13 4–19 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

8 From the Device Manager window, expand the Ports (COM & LPT) node.

Identify the COM port number assigned to the Alstom Transport Alstom

CPU2 CP210x USB to UART Bridge driver. This COM port number will be used to configure the HyperTerminal telnet session.

Note: The COM port assignment for this driver is not fixed. The number may change the next time the VT100 Emulator is connected to the iVPI system.

9 Start HyperTerminal to open a telnet session between the VT100 Emulator and the iVPI system. In Windows XP Pro, select Start | Programs | Accessories |

Communications | HyperTerminal.

If necessary, make any new connection settings as prompted.

P2521B, Volume 5, Rev. E, Nov/13 4–20 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

10 The New Connection window opens with the Connection Description dialog box active.

In the Name field, enter a name for the new connection. Click OK.

11 The Connect window opens.

Click the Modify button.

P2521B, Volume 5, Rev. E, Nov/13 4–21 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step

12 The Properties window opens.

Procedure

On the Connect To tab, select the COM port identified in Step 8 from the

Connect using menu.

Click the Configure button.

P2521B, Volume 5, Rev. E, Nov/13 4–22 Alstom Signaling Inc.

System Diagnostics

Step

Table 4–2. Direct Connection Procedure (Cont.)

Procedure

13 The Port Settings tab opens.

Make the following settings:

1. Bits per Second: 19200

2. Data Bits: 8

3. Parity: None

4. Stop Bits: 1

5. Row Control: None

Click OK to close the Port Settings tab.

P2521B, Volume 5, Rev. E, Nov/13 4–23 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

14 From the Properties window, select the Settings tab.

From the Emulation menu, select VT100.

Click OK until the Properties window closes.

P2521B, Volume 5, Rev. E, Nov/13 4–24 Alstom Signaling Inc.

System Diagnostics

Table 4–2. Direct Connection Procedure (Cont.)

Step Procedure

15 The HyperTerminal window re-opens.

When the VSP> (for VSP board) or NVSP> (for NVSP board) prompt appears, the telnet session is active.

P2521B, Volume 5, Rev. E, Nov/13 4–25 Alstom Signaling Inc.

System Diagnostics

4.3.4 MAC Port Functionality

Each MAC port provides access specific information and diagnostic/maintenance functionality. The specific functionality of each MAC port is provided below.

4.3.4.1

4.3.4.1.1

VSP Main MAC interface

Status indications

After starting VT100 Emulation, one of three top-level status messages appears once per second:

• "SYSTEM OK" is displayed when all iVPI functions are working properly (no errors detected).

• "SYS WARNING" indicates an error that has caused an abnormal or out-oftolerance condition. Continued iVPI operation may still be possible (the VRD Relay remains up). The meaning here is that system safety is unaffected.

• "ERROR ALERT" indicates a "fatal" error. Continued iVPI operation is not possible

(the VRD Relay is down with all outputs disconnected). The meaning here is that a system safety problem may exist.

If no message is shown:

• Verify the correct port is connected

• Verify the correct com port is configured on the emulator

• Verify the correct cable is in use

• Verify the VSP board contains valid software

• Verify the wiring is configured correctly if using a RS 232 Serial cable

• Try a new cable

• If the problem persists, replace the VSP board

Further interrogation is possible to help determine the exact cause of a top-level error message ("SYS WARNING" or "ERROR ALERT") by using a series of interactive keyboard commands.

Note: It may be necessary to enter the "S" command to display system status after connecting the terminal or VT100 emulation.

P2521B, Volume 5, Rev. E, Nov/13 4–26 Alstom Signaling Inc.

System Diagnostics

4.3.4.1.2 Keyboard Command Summaries

In the following command description tables, the information given in single quotes ('x') represents the exact key or keys to press on the VT100 Emulator. The final key to press for any command is 'CR' (Carriage Return) on a VT100 Emulator or Enter on a terminal.

This action is required to initiate each command, although for brevity, it is explicitly shown for only the first command's description below. Note that if any keyboard character is entered during the VSP board's power-up cycle, it may halt.

Note: These commands may be entered using upper-case or lower case letters.

Table 4–3. VSP Main Processor MAC Port Keyboard Commands (Cont.)

Command

'C' = Continue

'D' = Output

Diagnostics

Description

This command instructs the iVPI module to continue through its start-up sequence after an error is encountered during system start-up. However, with some errors, it may not be possible to continue until repairs are made. The 'C' command also causes the system to display one of the three top level status messages

("SYSTEM OK", "SYS WARNING" or "ERROR ALERT") without erasing stored error data. The Continue command is initiated by pressing the 'C' key followed by the 'CR' (Carriage Return) key.

This command displays LDO2 output diagnostics in 8 bits.

MSSPP 'D' displays LDO2 output diagnostics for LDO2 output

PP of the board in slot SS of the module.

'E' = Enable This command negates a previously entered 'I' (inhibit) command.

'G' = Output Current This command displays LDO2 output current in amperes.

MSSPP 'G' displays LDO2 output current in amperes for LDO2 output PP of the board in slot SS of the module.

'I' = Inhibit

'S' = Status

This command inhibits the "SYS WARNING" system status message from being displayed due to any warning condition in the system.

This command removes the system from the "query", "report" and "view errors" modes and returns the system to display system status. Exiting from the current mode is necessary when wishing to display other diagnostic messages.

P2521B, Volume 5, Rev. E, Nov/13 4–27 Alstom Signaling Inc.

System Diagnostics

Table 4–3. VSP Main Processor MAC Port Keyboard Commands (Cont.)

Command Description

'N' = Next

'?' = View

Errors/Warnings

'X' = Erase

This command instructs the system to display the next level of diagnostics, and is used while in the "query", "report" and "view errors" modes described below.

Use this command to display warning or error data after a "SYS

WARNING" or "ERROR ALERT" message has appeared. This command is ignored while the status is "SYSTEM OK". Step through all error/warning messages by using the 'N' (Next) command (see below), and exit "view errors" mode by using the

'S' (Status) command.

Erases all stored error and warning data. If the problem persists, the error data appears again even after erasure.

'Q' = Query Memory This command is used to display the value of one or more Vital parameters in VSP RAM, updated once per second. Parameter addresses are typically obtained from the Vital application's

.LVC compiled output report file. Use the 'S' command to exit from "query" mode.

The 'Q' command has several formats:

• 'wxyzQ' – causes the system to once per second display the contents of four consecutive bytes of VSP RAM, starting at the address entered immediately before the 'Q'. The starting address entered must be in hexadecimal format. The display shows the starting address, followed by the contents of four bytes of RAM data in the form of eight hexadecimal characters. Thus, if the command 'wxyzQ' is entered, the display shows "wxyz/12345678". The eight characters

(12345678) represent, from left to right, the data in the RAM locations wxyz+3, wxyz+2, wxyz+1 and wxyz, respectively.

Use the 'N' (Next) command to display four new bytes of data, starting at the RAM address wxyz+4. RAM addresses for application parameters are defined in the CAAPE generated application .LVC report file.

P2521B, Volume 5, Rev. E, Nov/13 4–28 Alstom Signaling Inc.

System Diagnostics

Table 4–3. VSP Main Processor MAC Port Keyboard Commands (Cont.)

Command

'Q' = Query Memory

(cont.)

Description

• 'wxyzQnn' – causes the system to place RAM address wxyz at position nn in the list of 16 Vital parameters to be queried, and once per second output the true (1) or false (0) states of the 16 Vital parameters whose addresses are currently in the list. In this command, the address wxyz may be from one to four hexadecimal characters, but an address of 0 (zero) is invalid. The position nn must be entered as two digits ranging from position 01 to 16. Typically, wxyz is the address of a Vital application parameter obtained from the application's LVC compiled output report file. After this command is entered, once per second the system displays the current true/false states of the 16 Vital parameters in the format "110000111xx0011x." The character x appears at positions in the list for which no address has yet been specified by the user. The system retains the list of 16 addresses to query unless it is restarted.

• 'wxyzQ00' – causes the system to remove RAM address wxyz from the list of 16 Vital parameters to be queried, and once per second output the true/false states of the 16 parameters whose addresses are currently in the list. In this command, a pair of zeros follows the letter Q.

• 'Q00' – causes the system to erase the entire list of 16 Vital

RAM parameters to be queried, and once per second output a message in the format "xxxxxxxxxxxxxxxx".

• '0Q00' – causes the system to once per second output the true (1) or false (0) states of the 16 Vital parameters currently in the list of addresses, without modification to the list. In this command, a single zero precedes and a pair of zeros follows the letter Q.

• 'Q' – causes the system to show the addresses (four at a time) currently in the list of 16 Vital parameters to be queried, in the format "aaaa;aaaa;aaaa;aaaa". Four dashes (----) are used to indicate an empty position in the list of 16 addresses.

Note that initially all positions are empty, until the user enters the 'wxyzQnn' command one or more times. Use the 'N'

(Next) command to view the next four addresses in the list.

P2521B, Volume 5, Rev. E, Nov/13 4–29 Alstom Signaling Inc.

System Diagnostics

Table 4–3. VSP Main Processor MAC Port Keyboard Commands (Cont.)

Command

'U' = Disable

'O' = Enable

'R' = Report

'RPT' = Report

'V' = Voltage

'W' = System ID

'T' = Timing

'Z' = Ignore

Command

Description

Use this command to inhibit the "SYS WARNING" message

(such as "OUT NOT ON") which appears when the iVPI diagnostics encounters an output that is turned on but is delivering no output current. This command may be appropriate when a no-current condition is normal.

This command negates a previously-entered 'U' (Disable) command.

This command routes configuration data to the Terminal. It provides system software and application configuration information. Step through all configuration messages by using the 'N' (Next) command, and exit "report" mode by using the 'S'

(Status) command.

This command displays software and application configuration control information for the VSP board.

This command configures the system to display the logic voltage value once per second.

This command displays the application revision ID and the system site ID.

This command displays cycle timing information in the following format: ABC/00ZZYYXX where:

• ABC is a query address

• XX is the point in the 1-second cycle where expression evaluation starts

• YY is the point in the 1-second cycle where expression evaluation ends

• ZZ is the point in the 1-second cycle where the main cycle ends

Any command terminated by a 'Z' is ignored by the system.

P2521B, Volume 5, Rev. E, Nov/13 4–30 Alstom Signaling Inc.

System Diagnostics

Table 4–3. VSP Main Processor MAC Port Keyboard Commands (Cont.)

Command Description

‘FST’ = Field Settable

Timer Display

This command will display the Field-Settable Software Vital

Timer(s). The iVPI module will display timer information in four columns. In the first column it will display the expression number. In the second column it will display the application timer name. In the third column it will display the current timer setting.

In the fourth column it will display the default timer value in parenthesis. The terminal is expected to be able to display a maximum of 24 lines of text and the iVPI module is capable of having up to 32 Field-Settable Software Vital Timers.

If more timers are defined than can be displayed on the screen at once then a message saying ‘MORE’ will appear indicating that there is more information to display. If the user presses the space bar then it will display the next group of timer information.

The command will continue as previously described until the end of the list is reached.

4.3.4.1.3 Vital Diagnostic Messages

Three kinds of system diagnostics or messages are possible when accessing VSP board system diagnostics:

• Start-up Diagnostics

• SYS WARNING

• ERROR ALERT

Table 4–4 through Table 4–7 list errors according to the message displayed by System

Diagnostics and give the corresponding user responses. Possible causes for the error message and preliminary steps to resolve system failure are also provided. A general

system troubleshooting flowchart is provided in Figure 2–1.

When troubleshooting, if board replacement is indicated, refer to the board replacement procedures provided in Table 5–1 through Table 5–9.

Note: Table 4–4 through Table 4–7 include the "module number" in

failure messages. Module #1 is always the system module in a multiple-module system, module #2 is Extender module #1, module #3 is Extender module #2, and module #4 is Extender module #3.

P2521B, Volume 5, Rev. E, Nov/13 4–31 Alstom Signaling Inc.

System Diagnostics

4.3.4.1.3.1 Start-up Diagnostics

Table 4–4. Start-up Diagnostics Troubleshooting (Cont.)

Message

Displayed

Possible

Cause(s)

User Response Corrective Action

" "

(no message displayed)

Faulty test cable or invalid software on VSP

Board. Further testing is not possible.

None

CPU DPRAM

ERR

CPU RAM

ERR

Failed checkerboard test of VSP

DPRAM. System may run if not using defective

RAM areas.

Failed

"Checkerboard" test of system

RAM. System may still run if not using defective

RAM areas.

None

Press "C" key and then "ENTER" key

Inspect test cable wiring.

Verify VSP Board software is valid.

If problem persists, replace

VSP Board.

Verify configuration settings on

VT100 terminal are set correctly for VSP Board.

19200 Baud, 8 databits, 1 stop bit, no parity, no flow control

(19200, 8, 1, N).

Replace VSP board.

Replace VSP Board.

P2521B, Volume 5, Rev. E, Nov/13 4–32 Alstom Signaling Inc.

System Diagnostics

Table 4–4. Start-up Diagnostics Troubleshooting (Cont.)

Message

Displayed

Possible

Cause(s)

User Response

CPU SIG

ERR

VSP LOGIC

VOLTG LOW

VSP LOGIC

VOLTG

HIGH

Failure of System

ID, Revision ID, or Site ID as defined in the

VSP application to match the hardwired signature on the back of the system module.

System does not operate under this condition.

Faulty regulator or voltage level detection circuit on the VSP board.

Low input voltage to the power isolation unit.

Faulty isolation unit.

Faulty regulator or voltage level detection circuit on the VSP board.

High input voltage to the power isolation unit.

Faulty isolation unit.

Press "C" key and then "ENTER" key

None

None

Corrective Action

Verify that the hardwired signature on the back of the system module matches the

System ID, Revision ID, and

Site ID as defined in the VSP application.

Verify input to power isolation unit to be 9-16 VDC.

Verify Output of power isolation unit to be 9-14 VDC.

Verify power wiring.

Replace VSP board.

Replace power isolation unit.

Verify input to power isolation unit to be 9-16 VDC.

Verify Output of power isolation unit to be 9-14 VDC.

Verify power wiring.

Replace VSP board.

Replace power isolation unit.

P2521B, Volume 5, Rev. E, Nov/13 4–33 Alstom Signaling Inc.

System Diagnostics

Table 4–4. Start-up Diagnostics Troubleshooting (Cont.)

Message

Displayed

POLY DIV

ERR

PROM MEM

ERR

OUTPUT

ERR

Possible

Cause(s)

Failure of PD portion of VSP

Board.

VSP system as application

FLASH.

Failed test of one or more outputs on a Vital Output

Board

Defective VSP

Board. System not likely to operate under this condition.

User Response

Press "N" key and then "ENTER" key

Failure Messages

'PD C3, 1 ERR'

'PD C3, 2 ERR'

'PD C1, 1 ERR'

'PD C1, 2 ERR'

'PD C1, 1N ERR'

'PD C1, 2N ERR'

'PD LOAD ERR'

Press "N" key and then "ENTER" key

Failure Messages

'ROUTINE PROM'

'ADS-

NOSHADOW'

'ADS-SHADOW'

Press "?" to find bad output board

Press "N" key and then "ENTER" key

Failure Message

'OUT#x/yy/z' x = Module number y = Slot number z = Port number

Corrective Action

Record failure for VSP Board in module.

Inspect/replace VSP Board.

Record failure for VSP Board in module.

Check Application/System software compatibility per the application.

Replace VSP Board system or application Flash.

Replace VSP Board.

Check for defective VSP

Board.

Verify continuity of iVPI

Motherboard.

Check expansion cables.

Replace Vital Output Board(s) as indicated.

P2521B, Volume 5, Rev. E, Nov/13 4–34 Alstom Signaling Inc.

System Diagnostics

Table 4–4. Start-up Diagnostics Troubleshooting (Cont.)

Message

Displayed

NVSP INTR

ERR

DPRAM

ERR

VRD INTR

ERR

Possible

Cause(s)

Dual-Port

Interface RAM failure on NVSP

Board. System operates under this condition.

VRD Interface

RAM failure on

VSP Board. VSP

Board fault.

System not likely to operate under this condition.

User Response Corrective Action

Press "N" key and then "ENTER" key

Failure Message

'NVSP BD x/yy' x = Module number y = Slot number

Press "C" key and then "ENTER" key

Check continuity of iVPI

System Bus (Motherboard).

Press Reset Switch on VSP

Board to initialize processor to test NVSP Interface RAM.

If test repeatedly fails, replace

NVSP Board.

If test fails with new NVSP

Board, replace VSP Board.

If test continues to fail, check bus connections on module motherboard and expansion cables.

Press Reset Switch on VSP

Board to initialize processor to test VRD Interface RAM.

If test repeatedly fails, replace

VSP Board.

If test continues to fail, check bus connections on module motherboard.

VS INTR

ERR

Dual-Port

Interface RAM failure on Vital

System (VS)

Board (GTP or

CRG). System operates under this condition.

Press "N" key and then "ENTER" key

Failure Message

'VS BD x/yy' x = Module number y = Slot number

Press Reset Switch on VSP

Board to initialize processor to test Interface RAM.

If test repeatedly fails, replace

GTP or CRG Board.

If test continues to fail, check bus connections on module motherboard and expansion cables.

Replace VSP Board.

P2521B, Volume 5, Rev. E, Nov/13 4–35 Alstom Signaling Inc.

System Diagnostics

4.3.4.1.3.2 SYS WARNING Diagnostics

Table 4–5. SYS WARNING Diagnostics (Cont.)

Message

Displayed

BAD IN

DATA

NVSP DIA

ERR

LOSS OF

COMM

OVERCURR

ENT (ON)

Possible

Cause(s)

User Response

One or more of the Vital Input

Ports returned

"Corrupted" circulation data.

Corrupted data is only recognized as faulty after 2 or more consecutive 1second cycles for a particular port.

Failure of VSP to obtain data from a NVSP Board on a 1-second basis.

Indicates NVSP program has failed and has stopped or is undergoing reset condition.

Degrading signal load.

Faulty output wiring.

Press "N" key and then "ENTER" key

Failure Message

'IN#x/yy/z' x = Module number y = Slot number z = Port number

Press "N" key and then "ENTER" key

Failure Message

'NVSP BD x/yy' x = Module number y = Slot number

Press "N" key and the "ENTER" key

Failure Message

OUT#x/yy/z x = module number yy = slot number z = port number

Corrective Action

Determine if input port changes state twice in 2 seconds during normal operation. If it does not change state twice in 2 seconds, then contact bounce could be at fault.

If error appears after clearing all saved error data, replace DI

Board.

Check bus connections on

Motherboard.

Type 'x' to clear and monitor how often it occurs.

Replace NVSP Board if condition continues.

Check mounting of regulator on board.

Replace signal bulb/LED unit.

Inspect output wiring and cables.

Inspect/replace LDO Board.

P2521B, Volume 5, Rev. E, Nov/13 4–36 Alstom Signaling Inc.

System Diagnostics

Table 4–5. SYS WARNING Diagnostics (Cont.)

Message

Displayed

OVERCURR

ENT (OFF)

UNDERCUR

RENT (ON)

EXTERNAL

VOLTAGE

VS DIAG

ERR

Possible

Cause(s)

User Response

Faulty LDO

Board.

Degrading signal load.

Voltage applied externally from the output.

Cable short.

Failure of VSP to obtain data from a Vital System

(VS) Board (CRG or GTP) on a 1second basis.

Indicates VS program has failed and has stopped or is undergoing reset condition.

Press "N" key and the "ENTER" key

Failure Message

OUT#x/yy/zz x = module number yy = slot number zz = port number

Press "N" key and the "ENTER" key

Failure Message

OUT#x/yy/zz x = module number yy = slot number zz = port number

Press "N" key and the "ENTER" key

Failure Message

OUT#x/yy/zz x = module number yy = slot number zz = port number

Press "N" key and the "ENTER" key

Failure Message

VS BD x/yy x = module number yy = slot number

Corrective Action

Inspect/replace LDO Board.

Replace signal bulb/LED unit.

Inspect/replace LDO Board.

Inspect output wiring and cables.

Check bus connections on

Motherboard.

Replace CRG or GTP if condition continues.

P2521B, Volume 5, Rev. E, Nov/13 4–37 Alstom Signaling Inc.

System Diagnostics

Table 4–5. SYS WARNING Diagnostics (Cont.)

Message

Displayed

V TIMER

ERR

OUT NOT

ON

Possible

Cause(s)

Vital Timer expression

(PPVT) returned a result that was not a codeword for Ch. 1 or Ch.

2.

PPVT =

Permanently

Programmed

Vital Timer (time is coded into

PROM)

Output port has been turned on but returned circulation data shows no current flowing through the output port circuit. Possible burned out lamp or other open condition.

User Response Corrective Action

Press "N" key and the "ENTER" key

Failure Message

'PPVT XPR#bbb' bbb = hexadecimal number of PPVT expression'

If error is related to PPVT timeout, use the query RAM to examine parameters of final timer expression.

U / ENTER

Inhibits 'OUT NOT

ON' message.

Press "O" key and then "ENTER" key

Nullifies the U /

ENTER command.

Press "N" key and then "ENTER" key.

Failure Message

'OUT#x/yy/z' x = Module number yy = Port number z = Port number

Check load on this port to determine if it is within proper current range.

If load on port (field equipment) is operational, replace output board.

This may be a valid condition if, for example, there is a relay contact in series with the output wiring.

P2521B, Volume 5, Rev. E, Nov/13 4–38 Alstom Signaling Inc.

System Diagnostics

Table 4–5. SYS WARNING Diagnostics (Cont.)

Message

Displayed

XPR RSLT

ERR

NO VRD

FRONT

Possible

Cause(s)

User Response

Evaluated expression returned a result that was not a codeword in code

Channel 1 or code Channel 2.

Press "N" key and then "ENTER" key

Failure Message

'XPR # xxx/CHy' xxx = The expression

CHy = Channel number of failed expression.

Press "N" key and then "ENTER" key to continue

After all expressions have been displayed,

'END ERR DATA' appears

Press "N" key and then "ENTER" key

VPI system wiring bad.

12V not applied to VRD section of

VSP Board.

Output errors.

System errors.

5V logic low.

Corrective Action

Determine if error data from other failures may have contributed to the expression result failure.

Examine parameter values of the product term that failed to determine whether a parameter value is an incorrect word.

Verify 12V applied to VSP

Board VRD section.

Interrogate VSP for more diagnostics.

P2521B, Volume 5, Rev. E, Nov/13 4–39 Alstom Signaling Inc.

System Diagnostics

4.3.4.1.3.3 ERROR ALERT Diagnostics

Table 4–6. ERROR ALERT Message Troubleshooting (Cont.)

Message

Displayed

POLY DIV

ERR

MAIN CWD

ERR

VRD XFR

ERR

Possible

Cause(s)

User Response Corrective Action

Failure of test performed on

VSP Board once each 1-second main cycle. VSP

Board is bad.

One or more of the 20 main checkwords was delivered to the

VRD with errors.

VRD Relay detected deenergized and checkwords sent to the VRD Board determined to be correct.

Press "N" key and then "ENTER" key

Failure Messages

'PD C3, 1 ERR'

'PD C3, 2 ERR'

'PD C1, 1 ERR'

'PD C1, 2 ERR'

'PD C1, 1N ERR'

'PD C1, 2N ERR'

'PD LOAD ERR'

Press "N" key and then "ENTER" key

Failure Message

'MAIN CWD # xx' xx = Main checkword number in the HEX error

Press "N" key and then "ENTER" key to continue

After all failed main checkwords have been displayed, 'END

ERR DATA' appears

Press "N" key and then "ENTER" key

Record failure for PD portion of

VSP Board in module.

Inspect/replace VSP Board.

Course of action depends on which checkword is in error.

Only 'CHKMEM' points to a specific failure.

If CHKMEM appears, verify on

VSP Board that correct software is installed as configured in the application.

Verify System ID is configured per the application.

Verify that correct application is installed on VSP Board.

If other checkwords are bad, replace VSP Board.

If VRD Relay continuously down, replace VRD Board.

If VRD Relay intermittently down, check iVPI System Bus

(Motherboard).

Verify 12V applied to VRD section of VSP Board.

P2521B, Volume 5, Rev. E, Nov/13 4–40 Alstom Signaling Inc.

System Diagnostics

Table 4–6. ERROR ALERT Message Troubleshooting (Cont.)

Message

Displayed

OUTPUT

ERR

TRE VAL

ERR

Note: This message follows

OUTPUT

ERR

Possible

Cause(s)

User Response Corrective Action

Failure of a

Recheck checkword delivered to the

VRD Board once at the beginning of each 50 ms period. Also may be caused by electromagnetic interference from external lines, relay, etc. Bad

Vital Output

Board.

Erroneous TRE values returned from output ports.

These cause incorrect

Recheck checkwords to go to the VRD. Bad

Vital Output

Board.

Press "N" key and then "ENTER" key

Failure Message

'OUT#x/yy/z' x = Module number yy = Slot number z = Port number

Press "N" key and then "ENTER" key to continue

After all failed main checkwords have been displayed, 'END

ERR DATA' appears

Press "N" key and then "ENTER" key

Failure Message

'TRE VAL # xx/yy' xx = Port group yy = Slot number

Press "N" key and then "ENTER" key to continue

After all failed output ports have been displayed,

'END ERR DATA' appears

Inspect/replace Vital Output

Board in question.

Use suppression on external lines and relay to eliminate noise.

Verify external connections and field equipment.

Verify external connections on field equipment.

Inspect/replace Vital Output

Board in question.

P2521B, Volume 5, Rev. E, Nov/13 4–41 Alstom Signaling Inc.

System Diagnostics

Table 4–6. ERROR ALERT Message Troubleshooting (Cont.)

Message

Displayed

RCHK CWD

ERR

Note: This message follows TRE

VAL ERR

Possible

Cause(s)

User Response Corrective Action

Failure of a

Recheck checkword being delivered to the

VRD. Bad Vital

Output Board.

Note: recheck checkword numbers 01 and

04 are summations of all other checkwords; so if any checkword is in error, 01 and

04 are also in error.

Press "N" key and then "ENTER" key

Failure Message

'RCHK CWD # xx' xx = Checkword number

Press "N" key and then "ENTER" key to continue

After all failed output ports have been displayed,

'END ERR DATA' appears

Verify external connections and field equipment.

Inspect/replace Vital Output

Board in question.

P2521B, Volume 5, Rev. E, Nov/13 4–42 Alstom Signaling Inc.

System Diagnostics

4.3.4.2

4.3.4.2.1

NVSP Main MAC interface

Status indications

After starting VT100 Emulation, one of three top-level status messages appears once per second:

• "SYSTEM OK" is displayed when all non-vital functions are working properly (no errors detected).

• "SYS WARNING" indicates an error that has caused an abnormal or out-oftolerance condition. Continued NVSP operation may still be possible.

• "ERROR ALERT" indicates a "fatal" error. Continued NVSP operation is not possible. However, the rest of the iVPI system may continue operation.

If no message is shown:

• Verify the correct port is connected.

• Verify the correct com port is configured on the emulator.

• Verify the correct cable is in use.

• Verify the NVSP board contains valid software.

• Verify the wiring is configured correctly if using a RS-232 Serial cable.

• Try a new cable.

• If the problem persists, replace the NVSP board.

Further interrogation is possible to help determine the exact cause of a top-level error message ("SYS WARNING" or "ERROR ALERT") by using a series of interactive keyboard commands.

Note: It may be necessary to enter the "S" command to display system status after connecting the terminal or VT100 emulation.

P2521B, Volume 5, Rev. E, Nov/13 4–43 Alstom Signaling Inc.

System Diagnostics

4.3.4.2.2 Keyboard Command Summaries

In the following command description tables, the information given in single quotes ('x') represents the exact key or keys to press on the VT100 Emulator. The final key to press for any command is 'CR' (Carriage Return) on a VT100 Emulator or Enter on a terminal.

This action is required to initiate each command, although for brevity, it is explicitly shown for only the first command's description below. Note that if any keyboard character is entered during the VSP board's power-up cycle, it halts.

Note: These commands may be entered using upper-case or lower case letters.

Table 4–7. NVSP Main Processor MAC Port Keyboard Commands (Cont.)

Command

'E' = Enable

'I' = Inhibit

'S' = Status

? – Display

Diagnostics

'X' = Erase

'RPT' = Report

‘RPH’ = Hardware

Configuration Report

‘LED’ = Health LED test

Description

This command negates a previously entered 'I' (inhibit) command.

This command inhibits the "SYS WARNING" system status message from being displayed due to any warning condition in the system.

This command displays the current system status and negates a previously entered ‘I’ (inhibit) command.

This command lists the code and associated message for each entry recorded in the NVSP runtime diagnostic event database.

Use this command to display warning or error data after a "SYS

WARNING" or "ERROR ALERT" message has appeared.

Erases all stored error and warning data. If the problem persists, the error data appears again even after erasure.

This command displays software and application configuration control information for the NVSP board.

This command displays hardware configuration control information for all boards in the system.

Note: This command is only available on the first NVSP in a Non-Vital only system (i.e. no VSP is present).

This command tests Health LEDs on all the boards in the system by cycling them through Red (ERROR), Yellow

(WARNING) and Green (OK) indications.

Note: This command is only available on the first NVSP in a Non-Vital only system (i.e. no VSP is present).

P2521B, Volume 5, Rev. E, Nov/13 4–44 Alstom Signaling Inc.

System Diagnostics

Table 4–7. NVSP Main Processor MAC Port Keyboard Commands (Cont.)

Command

‘V’ – VT100 Menu

Diagnostics

'W' = System ID

Description

This command activates the NVSP menu-driven diagnostics

mode (see Section 4.5 for details). To return to the command

prompt, enter the Ctrl+F key combination.

This command displays the application revision ID and the system site ID, both expected by the application and detected at runtime. A mismatch between the expected and detected site or revision IDs constitutes a fatal error and causes the NVSP to cease all processing, I/O and communications activity.

4.3.4.3 Communications Processor MAC interface

The MAC interface functionality of Communications Processor on the VSP and NVSP is substantially similar, with the NVSP MAC only supporting a subset of the commands applicable to the Non-Vital subsystem. The table below describes all commands supported by Communications Processor MAC port, denoting which commands are supported by NVSP (VSP supports all commands).

Table 4–8. Communication Processor MAC Port Keyboard Commands (Cont.)

Command

'?' = View All

Errors/Warnings

'C' = View

Communication

Processor

Errors/Warnings

'V' = View Main

Processor

Errors/Warnings

'G m/ss/pp' = Display

Signal Output Current

'H' = Display Command

Summary

Description

Use this command to display all warnings or error codes from both the Main processor and the Communication Processor.

See Table 4–9 and Table 4–10.

Supported

Use this command to display all warning or error codes from the Communication

Processor. See Table 4–10.

Use this command to display all warning or error codes from the Main Processor.

See Table 4–9.

Use this command to display the signal output current from an LDO board specified by module (m), slot (ss) and part (pp).

Use this command to display all available commands.

Supported

Use ‘M’ in place of ‘V’

Not

NVSP

Supported

Supported

P2521B, Volume 5, Rev. E, Nov/13 4–45 Alstom Signaling Inc.

System Diagnostics

Table 4–8. Communication Processor MAC Port Keyboard Commands (Cont.)

Command Description NVSP

'I' = Inhibit All Warnings Use this command to inhibit the warning states indication.

'O' = Enable This command negates a previously entered

'U' (Disable) command.

'RIP' = Display IP Report This command displays the configured IP addresses for each network controller.

'RPT' = Display

Configuration Report

This command displays the Main Processor and Communication Processor configuration reports.

Not

Supported

Not

Supported

Supported

Supported

'RNET' = Display

Network Status

'S' = Display System

Status

'T' = Display Main

Processor Timing Cycle

'TSK' = Display

Communication

Processor Task Usage

'U' = Disable

This command displays network statistics

(such as messages transmitted and messages received) for each network controller.

This command displays the Main Processor and Communication Processor status.

This command displays the Main Processor timing cycle.

This command displays the Communication

Processor task usage in percent.

Supported

Not

Supported

Not

Supported

Supported

'V' = Display Logic

Voltage

Use this command to inhibit the "OUT NOT

ON" warning indication.

Use this command to display the logic voltage.

Not

Supported

Not

Supported

'W' = Display System ID Use this command to display the system

Site/Rev. ID.

'X' = Clear All

Diagnostics

Use this command to clear all Main Processor and Communication Processor diagnostics.

Not

Supported

Supported

'XC' = Clear

Communication

Processor Diagnostics

Use this command to clear the

Communication Processor diagnostics.

Supported

'XNET' = Clear Network

Statistics

'XV' = Clear Main processor Diagnostics

Use this command to reset all network statistics to zero.

Supported

Use this command to clear all main Processor

Diagnostics.

Use ‘XM’ in place of ‘XV’

P2521B, Volume 5, Rev. E, Nov/13 4–46 Alstom Signaling Inc.

System Diagnostics

4.4

4.4.1

ERROR NUMBERS

VSP Main Processor Error Numbers

Table 4–9 and Table 4–10 list errors according to the error number. The error number is

the second field of the display error code. All VSP Main Processor error numbers are

cross-references to the corresponding diagnostic table (Table 4–4 through Table 4–7).

Table 4–9. VSP Main Processor Error Numbers (Cont.)

Error Number (hex)

000E

000F

0010

0011

0015

0016

0017

0001

0002

0003

0004

000B

000C

000D

0018

001E

0032

0033

0034

003D

003E

0047

0048

00C9

00CA

Message Displayed

CPU RAM ERR

LOGIC VOLTG LOW

LOGIC VOLTG HIGH

CPU DPRAM ERR

POLY DIV ERR

PROM MEM ERR

CPU SIG ERR

VRD INTR ERR

NO VRD FRONT

VRD XFER ERR

CSE INTER ERR

CSE DIAG ERR

VSC INTER ERR

VSC DIAG ERR

OUTPUT ERR

OUT NOT ON

Failure Messages

PD C3,1 ERR

PD C3,2 ERR

PD C1,1 ERR

PD C1,2 ERR

PD C1,1N ERR

PD C1,2N ERR

PD LOAD ERR

ROUTINE

ADS NOSHADOW

ADS SHADOW

Bootloader

P2521B, Volume 5, Rev. E, Nov/13 4–47 Alstom Signaling Inc.

System Diagnostics

Error Number (hex)

0161

0162

0163

0164

0165

0166

02BD

0259

02BE

02BF

02C0

02C1

02C2

00CB

00CC

00CD

00CE

00CF

012D

015F

0160

Table 4–9. VSP Main Processor Error Numbers (Cont.)

Message Displayed

LDO2 DIAGNOSTICS

BAD IN DATA

V TIMER ERR

XPR RSLT ERR

FSVT XPR ERR

CRG CWD ERR

MAIN CWD ERR

RCHK CWD ERR

TRE VAL ERR

Failure Messages

OVERCURRENT ON

OVERCURRENT OFF

UNDERCURRENT ON

EXTERNAL VOLTAGE

NO I/O DIAGS

FSVT SW ERR

FSVT TIMEOUT

PPVT TIMEOUT

P2521B, Volume 5, Rev. E, Nov/13 4–48 Alstom Signaling Inc.

System Diagnostics

4.4.2 NVSP Main Processor Diagnostic Code Numbers

The non-vital system diagnostics specific messages displayed when accessing NVSP

board system diagnostics are summarized in Table 4–10.

When troubleshooting, if board replacement is indicated, refer to the board replacement

procedures provided in Table 5–1 through Table 5–11.

Table 4–10. NVSP Main Processor Diagnostic Code Numbers (Cont.)

Diagnostic

Code

(Decimal)

1297

Diagnostic

Code (Hex)

0511

1298

1299

1300

1301

0512

0513

0514

0515

Description

Memory

Shortage error, location<Data2

>

Protocol

Missing

Protocol

Initialization error

Task Allocation error, task

Ring Allocation error

Possible Causes

Failed to allocate port data structures

Protocol

Configuration Data

Missing

Protocol configuration error detected by

Protocol Module

Initialization routine, reported in subsequent diagnostic message

Failed to allocate task (should not happen as the maximum task count is meant to support all defined ports and TWC instances) – system design error

Failed to allocate port ring memory

Corrective Action

Redesign application to reduce memory requirements

See CAAPE documentation for troubleshooting

See Protocol

Module documentation

Contact ALSTOM

Redesign application to reduce memory requirements

P2521B, Volume 5, Rev. E, Nov/13 4–49 Alstom Signaling Inc.

System Diagnostics

Table 4–10. NVSP Main Processor Diagnostic Code Numbers (Cont.)

Diagnostic

Code

(Decimal)

1302

Diagnostic

Code (Hex)

0516

1303

1304

1305

1306

1309

1310

0517

0518

0519

051A

051D

051E

Description

Port Allocation error

CAA Indication

Flag error, Loc

<Data2>

CAA Control

Flag error, Loc

<Data2>

Special Msg

Flag.

Port Flag error,

Loc <Data2>

Protocol error number

MAC Initiated

Software Reset

PROM Task

Failure

Possible Causes

Failed to allocate port ring memory

Unexpected flag value, internal system error

Unexpected flag value, internal system error

Unexpected flag value, internal system error

Protocol configuration error detected by the

Protocol Module

Initialization routine, reported in subsequent diagnostic message

System reset on user request

Prom CRC

Mismatch- likely corruption

Corrective Action

Redesign application to reduce memory requirements

Automatically corrected, contact

ALSTOM if frequent or persistent

Automatically corrected, contact

ALSTOM if frequent or persistent

Automatically corrected, contact

ALSTOM if frequent or persistent

See Protocol

Module documentation

Informational message

Reprogram the

NVSP application via AlsDload

P2521B, Volume 5, Rev. E, Nov/13 4–50 Alstom Signaling Inc.

System Diagnostics

Table 4–10. NVSP Main Processor Diagnostic Code Numbers (Cont.)

Diagnostic

Code

(Decimal)

1311

Diagnostic

Code (Hex)

051F

1314

1315

0522

0523

Description

Reset due to stack crash, count

Application is not running, reset count

<Data2>

Bad Msg Flag,

Msg:<Data2>

Possible Causes

System reset due to Task Stack overrun

System reset due to Application Logic not running

Corrective Action

Automatically corrected, contact

ALSTOM if frequent or persistent

Review Application

Logic for infinite loops

1318

1319

1320

1321

1431

0526

0527

0528

0529

0597

AlsDload

Software Reset

System Start

Up

UNKNOWN

RESET TCB

<Data1>

Active, TOTAL

RESETS

<Data2>

Invalid Serial

Port Interrupt

Index: Port:

Loc:

Data Logger

Reset

Internal system error.

Automatically corrected, contact

ALSTOM if frequent or persistent

System reset for a

Software Update

Informational

Message

System initialized Informational

Message

System reset for an unknown reason

Informational

Message

System detected an invalid serial port interrupt

Informational

Message

Informational

Message

1432

1433

0598

0599

Application

Stopped

Application

Started Up

Data Logger RAM cleared by user request

Application Logic stopped by user request

Application Logic restarted by user request

Informational

Message

Informational

Message

P2521B, Volume 5, Rev. E, Nov/13 4–51 Alstom Signaling Inc.

System Diagnostics

Table 4–10. NVSP Main Processor Diagnostic Code Numbers (Cont.)

Diagnostic

Code

(Decimal)

1530

Diagnostic

Code (Hex)

05FA

1531

1532

1533

1536

1537

1568

1569

1570

1571

05FB

05FC

0F5D

0600

0601

0620

0621

0622

0623

Description

Cleared

Diagnostic

Msgs Loc

MMS Cleared

Diagnostic

Msgs

MMS Requests

RT Clock

MMS set RT

Clock

CP/MMS sent bad diagnostic query datatype.

DT:<Data2>

Lithium button cell battery is low

Invalid CP

Incoming

Header Msg.

Port: <Data1>

Loc: <Data2>

CP Incoming buffer is full

Port:<Data1>

Loc: <Data2>

Msg to CP is

NOT sent

Port:<Data1>

Loc: <Data2>

Msg for CP is

NOT sent, did not fit in buffer.Port:<Dat a1> Loc:

<Data2>

Possible Causes

Diagnostics cleared by MAC user request

Diagnostics cleared by MMS request

MMS Requested

Date/Time

MMS Set

Date/Time

MMS Link Error

BBRAM Battery

Voltage level low

Comm Processor

Interface Error

Comm Processor

Interface

Congestion

Comm Processor

Interface

Congestion

Comm Processor

Interface

Congestion

Corrective Action

Informational

Message

Informational

Message

Informational

Message

Informational

Message

Informational

Message

Replace Battery

per Table 5–8

Automatically corrected, used for support-level troubleshooting

Automatically corrected, used for support-level troubleshooting

Automatically corrected, used for support-level troubleshooting

Automatically corrected, used for support-level troubleshooting

P2521B, Volume 5, Rev. E, Nov/13 4–52 Alstom Signaling Inc.

System Diagnostics

Table 4–10. NVSP Main Processor Diagnostic Code Numbers (Cont.)

Diagnostic

Code

(Decimal)

1572

Diagnostic

Code (Hex)

0624

1600

1601

1602

1632

1633

1634

0640

0641

0642

0660

0661

0662

Description

Unable to lock

CP outgoing buffer

Port:<Data1>

Loc: <Data2>

Invalid CP

MailBox Flag

Loc: :<Data1>

Flag: <Data2>

Fail lock buffer, wait for CP to finish

Loc:<Data1>

Cnt:<Data2>

Fail lock buffer, timeout-CP using

Loc:<Data1>

Cnt:<Data2>

MP tried to lock a buffer it already has locked

Invalid flag when MP tried to lock buffer

Flag:<Data2>

Received bad/unused port number

Possible Causes

Comm Processor

Interface

Congestion

Comm Processor

Interface Error

Comm Processor

Interface Error

Comm Processor

Interface Error

Comm Processor

Interface Error

Comm Processor

Interface Error

Invalid Data Packet provided by CP;

Incoming data packet dropped by excessive network utilization

Corrective Action

Automatically corrected, used for support-level troubleshooting

Automatically corrected, used for support-level troubleshooting

Automatically corrected, used for support-level troubleshooting

Automatically corrected, used for support-level troubleshooting

Automatically corrected, used for support-level troubleshooting

Informational

Message

Informational

Message

P2521B, Volume 5, Rev. E, Nov/13 4–53 Alstom Signaling Inc.

System Diagnostics

Table 4–10. NVSP Main Processor Diagnostic Code Numbers (Cont.)

Diagnostic

Code

(Decimal)

1635

Diagnostic

Code (Hex)

0663

1636

1637

1638

1664

0664

0665

0666

0680

Description

Outgoing

Packet Error

Loc:<Data2>

Incoming

Packet Error

Loc:<Data2>

Outgoing

Packet Header

Error <Data2> bytes dropped

Incoming

Packet Header

Error <Data2> bytes dropped

Possible Causes

Outgoing data packet in DPRAM corrupted

(will be dropped), or is dropped by excessive network utilization

Invalid Data Packet provided by CP;

Incoming data packet dropped due to excessive network utilization

Outgoing data packet in DPRAM corrupted (will be dropped), or is dropped due to excessive network utilization

Invalid Data Packet provided by CP;

Incoming data packet dropped due to excessive network utilization

Hardware Error

Corrective Action

Informational

Message

Informational

Message

Informational

Message

Informational

Message

Replace the board

1696

1697

06A0

06A1

DPRAM

Startup Test

Failure

VSP SiteID

Mismatch

Actual:<Data2>

Bad Rev Id

Switch Setting

Actual:<Data2>

System Site ID

Mismatch

System Site ID

Mismatch

Correct the misconfiguration

Correct the misconfiguration

P2521B, Volume 5, Rev. E, Nov/13 4–54 Alstom Signaling Inc.

System Diagnostics

Table 4–10. NVSP Main Processor Diagnostic Code Numbers (Cont.)

Diagnostic

Code

(Decimal)

Diagnostic

Code (Hex)

Description

1729-1808 06C1-0710 NVI Board

Failed

Mod:<Data1>

Slot:<Data1>

Group:<Data2>

1809-1888 0711-0760 NVO Board

Failed

Mod:<Data1>

Slot:<Data1>

Group:<Data2>

1889-1908 0761-0774 Expecting

<board type> board in

Slot:<slot number>

1909-1928 0775-0788 Wrong Board

Type in

Slot:<slot number>, expecting

<board type> board.

1929-1948 0789-079C Unexpected

<board type> board in

Slot:<slot number>.

Possible Causes

NVI board

Diagnostics error

NVO board

Diagnostics error

Board missing in slot

Wrong board type in slot

Unexpected board in slot

Corrective Action

Check wiring, replace NVI board

Check wiring, replace NVO board

Add needed board in specified slot

Replace board with needed board in specified slot

Remove the extraneous board in specified slot

Note: <DATA1> and <DATA2> get filled with application-specific data at runtime.

P2521B, Volume 5, Rev. E, Nov/13 4–55 Alstom Signaling Inc.

System Diagnostics

4.4.3 Communication Processor Error Numbers

Communication Processor errors can be displayed for the VSP and NVSP, see

Table 4–11 for a summary of these errors.

When troubleshooting, if board replacement is indicated, refer to the board replacement

procedures provided in Table 5–1 through Table 5–11.

Table 4–11. Communication Processor Error Numbers (Cont.)

Error

Number

(Hex)

Description Possible Causes Corrective Action

4E21

4E22

Stack initialization error

IP Address error

Network stack error Reset CP; if diagnostic is frequent replace board

Invalid IP address Verify configured IP addresses

4E23 Bring up device error

Bad network controller Replace board

4E24 Create socket error Network stack error Reset CP; replace board

4E25 Blocking error Heavy network traffic Reduce network traffic

4E26 Socket Bind error Network stack error Reset CP; if diagnostic is frequent replace board

4E27 Listen socket error Network stack error Reset CP; if diagnostic is frequent replace board

4E85 Pass data up stack error

4E86 Select error

Network stack error Reset CP; if diagnostic is frequent replace board

Network stack error Reset CP; if diagnostic is frequent replace board

4E87 Accept error Network stack error Reset CP; if diagnostic is frequent replace board

4E88

4E89

7531

Receive error

Send error

Flash CRC mismatch

Network stack error Reset CP; if diagnostic is frequent replace board

Network stack error Reset CP; if diagnostic is frequent replace board

Bad Flash Use AlsDload to re-download

Flash data; if frequent replace board

7532 Memory test error Bad RAM Replace board

P2521B, Volume 5, Rev. E, Nov/13 4–56 Alstom Signaling Inc.

System Diagnostics

Table 4–11. Communication Processor Error Numbers (Cont.)

Error

Number

(Hex)

Description Possible Causes Corrective Action

7534

7535

7536

DPRAM locked by

MP

Invalid MAC command

Unsupported protocol

Main Processor busy Reduce MP load; clear diagnostic; if frequent call customer service

Bad MAC_TCP message

Clear diagnostic; if frequent call customer service

Bad network message Clear diagnostic; if frequent call customer service

Call customer service 7595 Memory allocation error

Out of memory

7596 Illegal RtOs return Operating system error

Call customer service

7597 Failed to create semaphore

7598 Failed to create mutex

7599 Failed to create task

759A Invalid semaphore status

Operating system error

Operating system error

Operating system error

Operating system error

Bad RAM

Call customer service

Call customer service

Call customer service

Call customer service

759B Heap Initialization error

75F9 Duplicate IP address detected

IP address used by another node

MAC address used by another node

Replace board

Verify configured IP addresses

Replace board 75FA Duplicate MAC address detected

75FB

75FC

Unsupported network protocol

Maximum open sockets exceeded

Bad network message Clear diagnostic; if frequent call customer service

Too many open connections

Reduce network connections

75FD Network link is lost Remote node shutdown, disconnected cable

Check network connections.

Verify remote node communication

P2521B, Volume 5, Rev. E, Nov/13 4–57 Alstom Signaling Inc.

System Diagnostics

Table 4–11. Communication Processor Error Numbers (Cont.)

Error

Number

(Hex)

75FE

75FF Network device Rx queue overrun

7600 Network device Tx queue overrun

765D Vital Serial Tx transfer overrun

765E Vital Serial Tx transfer invalid

765F Vital Serial Rx transfer overrun

7660 Vital Serial Rx transfer invalid

7661 Vital Serial Tx timeout

7662 TCP timeout

7663

Description

Network device is down

TCP lost connection

Possible Causes Corrective Action

Remote node shutdown, disconnected cable

Check network connections.

Verify remote node communication

Heavy network traffic Clear diagnostic; if frequent, reduce network traffic

Heavy network traffic Clear diagnostic; if frequent, reduce network traffic

Heavy network traffic Clear diagnostic; if frequent, reduce network traffic

Operating system error

Call customer service

Heavy network traffic Clear diagnostic; if frequent, reduce network traffic

Operating system error

Call customer service

Heavy network traffic Clear diagnostic; if frequent, reduce network traffic

Heavy network traffic Clear diagnostic; if frequent, reduce network traffic

Remote node shutdown, disconnected cable

Check network connections; verify remote node communication

P2521B, Volume 5, Rev. E, Nov/13 4–58 Alstom Signaling Inc.

System Diagnostics

4.5

4.5.1

NON-VITAL SYSTEM DIAGNOSTICS ON THE NVSP BOARD

Using Menus

Diagnostics functions are selected from the NVSP menus. The term "menu" is used to describe a list of choices that can access other lists of choices or diagnostic test topics by selecting one of the options displayed near the bottom of the screen display. A menu may be a portion of a screen display. If a menu is the predominant feature of a screen, that screen is typically named according to the menu displayed (such as Main Menu).

See Table 4–12 for the menu access keys. After a menu option is selected, additional information may be required and the user is prompted to add specific data.

Table 4–12. NVSP Menu Access

Key Sequence

Press the Right or Left Arrow key or the

Space Bar

Press the Enter key

Result

To highlight the menu or option of interest

To access a highlighted menu or option of interest

To access the menu or option Press the first letter of a menu or option

(this letter is usually displayed in uppercase)

Press 'E' (Exit)

Press ''Q' (Quit)

Simultaneously press Ctrl and 'E'

Simultaneously press Ctrl and ‘F’

To exit from most menus

To exit from certain submenus

To return directly to the Main Menu from any submenu

To exit the menu-driven mode and return to the MAC Command Prompt

CAUTION

Certain diagnostic menu options take the system off-line, causing an adverse effect on system operations. Use only the screens listed.

CAUTION

Diagnostic tasks run at a lower priority than those system tasks supporting the primary purpose of the application. Therefore, some displays may at times appear to be incorrect. This usually occurs because the presentation of the data on the terminal screen occurs after the event being presented.

P2521B, Volume 5, Rev. E, Nov/13 4–59 Alstom Signaling Inc.

System Diagnostics

4.5.2 Menu Structure

Figure 4–12 shows the selection path from the Main Menu to the other menus available.

The Main Menu is essentially divided into two functional parts, Emulation and System.

This "menu tree" provides an overview of the non-vital iVPI system diagnostic menus and their options.

Each menu or screen is provided with available options and user selection path. The path lists in order the selection process for the menu or screen being described.

The menus normally used are listed first and then the entire available menu structure is listed.

CAUTION

Certain diagnostic menu options can have an effect on non-vital system operations. Be careful to return to the Main Menu when done accessing the diagnostic information.

Diagnostic tasks run at a lower priority than those system tasks supporting the primary purpose of the application. Therefore, some displays may at times appear to be incorrect. This usually occurs because the presentation of the data on the terminal screen occurs after the event is presented.

P2521B, Volume 5, Rev. E, Nov/13 4–60 Alstom Signaling Inc.

System Diagnostics

P2521B, Volume 5, Rev. E, Nov/13

Figure 4–12. Menu Tree

4–61 Alstom Signaling Inc.

System Diagnostics

4.5.3 NVSP Main Menu

After power is applied and the system is initialized, the NVSP Main Menu, shown in

Figure 4–13, is displayed on the terminal screen connected to the MAC port. If the Main

Menu is not displayed, simultaneously press 'Ctrl' and 'E' to jump from any submenu back to the Main Menu. If any NVSP board resets occurred since the last time the system was turned on, this information appears above the Main Menu. This reset log is cleared once the board is turned off.

Note that if the diagnostic password option has been activated, the password must be entered prior to modifying settings that affect system operation.

When a choice is made in the Main Menu, a submenu may appear. The menus and selections are explained below. The available sub-menus are Emulation, Monitor,

System, Diagnostic, Logger, HHT_Use, Tracker, Password, and W.

Note: The Main Menu choices Tracker and W are intended for use by external software utilities, such as Alstom's Tracker program

(refer to Alstom publication P2307), and are not discussed in this manual. Only menu choices used for normal system analysis are discussed in this manual.

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Main Menu

Emulation Monitor System Diagnostic Logger HHT

Support Emulations Used

_ Use Tracker Password W

Figure 4–13. NVSP Main Menu

P2521B, Volume 5, Rev. E, Nov/13 4–62 Alstom Signaling Inc.

System Diagnostics

Table 4–13 describes the options available in the NVSP Main Menu. Further

explanation of options is provided later.

Table 4–13. Main Menu Choices

Option Description

Emulation Invokes the Emulation Menu used to diagnose problems related to communication protocol emulation operation. Subsequent menus accessible from the Emulation Menu via its Diags menu choice are fully documented in the respective Alstom pamphlet for the specific protocol emulation installed (refer to the Alstom publication P2346 series).

Monitor Starts the operation of the data monitor used to display message traffic on specific serial ports. The Monitor Menu is displayed showing the available data monitor options.

System Displays the system configuration information consisting of:

• The application's NVSP ID string

• System and CAA drawing numbers

• Application compilation time and revision

• System compilation time and revision

• Optional DataLogger compilation time and revision

• Serial ports usage and protocol emulation revision

Diagnostic Provides access to system diagnostics used to locate hardware problems, and evaluate software operation.

Logger Provides access to the Alstom Embedded DataLogger diagnostic menus.

NVSP offers detailed event diagnostic capability. For details on this advanced data logging feature refer to Alstom Publication P2512E.

Password Permits entry of an application password to allow modification of system settings. If a diagnostic password has been specified in the non-vital application, the password must be entered before modifying any setting that affect system operation. Only authorized persons should know the diagnostic password.

Initially, "Password Disabled" appears at the upper left of the Main Menu; however, if no password has been defined in the application, then no message appears and the Password menu choice is disabled. Otherwise, select Password and then enter the correct diagnostic password;

"Password Enabled" is now displayed. The operator may now activate features that affect system operation. If there is no MAC port activity for more than 30 minutes, however, the system automatically disables the diagnostic password forcing authorized personnel to enter it again.

W This menu choice is for the exclusive use of Alstom's Watcher diagnostic utility program that runs on a PC, and is not for actual user operation.

P2521B, Volume 5, Rev. E, Nov/13 4–63 Alstom Signaling Inc.

System Diagnostics

4.5.4 Emulation Menu

The Emulation Menu, shown in Figure 4–14, is displayed by selecting Emulation from

the Main Menu. The Emulation Menu provides access to communication protocol emulations loaded in the NVSP system. Each protocol emulation, such as Alstom's

DataTrain VIII (DT8), is assigned to a specific serial port in the non-vital application.

Selection Path:

• Main Menu

– Emulation

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Next Last Optns Msg Diags Reset TWC Vital _ Diags Exit

Figure 4–14. Emulation Menu

P2521B, Volume 5, Rev. E, Nov/13 4–64 Alstom Signaling Inc.

System Diagnostics

Refer to the Table 4–14 for a brief description of the available options in the Emulation

Menu, after which the menu choices are described in more detail.

Option

Port

Next

Last

Optns

Msg

Diags

Reset

TWC

Exit

Table 4–14. Emulation Menu Choices

Description

Select the serial port of interest (for example, enter the port number from 1 to 5) and view the port's setup. The serial port number must be specified prior to using the Next, Last, Optns, Msg or Diags menu choices.

Display the current contents of control, indication and Special Message buffers for the next station on the selected serial port; if only one station is defined for the codeline port, then the Next and Last options behave identically.

Display the current contents of control, indication and Special Message buffers for the previous station on the selected serial port.

View the serial port setup: baud rate and the data format (data bits, stop bits, parity).

Observe message traffic (controls and indications) between the non-vital application logic and the emulation, and enter and manually post a control or a Special Message to the application logic.

Execute protocol emulation specific diagnostics.

Reset the entire system. Use this choice with care since it causes the

NVSP software to reinitiate its start-up sequence, as if the system were turned off then back on.

Access the Train-to-Wayside Communications (TWC) diagnostics menu (if applicable).

Return to the Main Menu.

P2521B, Volume 5, Rev. E, Nov/13 4–65 Alstom Signaling Inc.

System Diagnostics

4.5.4.1 Emulation Menu Choice: Port

The Port menu choice allows the user to specify the NVSP serial port on which the communication protocol is installed. The serial port number must be specified before using the Next, Last, Optns, Msg or Diags options in the Emulation Menu. Both the port usage and the type of protocol loaded are displayed, an example of which is shown in

Figure 4–15.

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Next Last Optns Msg Diags Reset TWC Vital _ Diags Exit

Port 1 has 1 stations using 51612 - 001 - 23 REV F 36 Aug 31 2001 , 13 : 49 : 56

DATATRAIN ( R ) VIII

Figure 4–15. Emulation Menu – Select the Serial Port

P2521B, Volume 5, Rev. E, Nov/13 4–66 Alstom Signaling Inc.

System Diagnostics

4.5.4.2 Emulation Menu Choice: Next or Last

When the Next or Last menu choice is selected, the current information for a single

station is displayed once. This information is not updated in real time. See Figure 4–16

for a sample screen. The Next or Last menu choices are most useful for a port having multiple stations, otherwise information for station 1 is always displayed when Next or

Last is selected.

The station information consists of:

• Control and indication station addresses and the total number of binary bits in each address

• The length of each message: control, indication and Special

• Each message's starting buffer address in RAM (intended for Alstom technical personnel only)

• The most recently posted control, indication and Special Messages

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Next Last Optns Msg Diags Reset TWC Vital _ Diags Exit

Station # 1

Control address

Message length

Last message posted

( 08 ) = 00000050

= 128 , Located at 0000 : 77 EC

: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Indication address

Message length

( 08 ) = 00000050

= 536 , Located at 0000 : 786 D

Last message posted : 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10

Special message

Message length = 0 , Located at 0000 : 0000

Last message posted :

Figure 4–16. Example Emulation Menu – View a Station's Messages

P2521B, Volume 5, Rev. E, Nov/13 4–67 Alstom Signaling Inc.

System Diagnostics

This example shows that the control address for station 1 is 50 with a length of 8 bits.

The message itself contains 128 bits (parameters) and is located in memory beginning at address 0000:77EC. The message contents are shown as a series of 16 hexadecimal bytes, eight bits each. In this example, all 128 bits in the last received control message are false (0).

The indication address is also 50 and has a length of eight bits. The message itself is

536 bits in length and is located in memory beginning at address 0000:786D. The last indication sent is 00 00 00 00 … 00 00 00 00 10. Refer to Table 4–15 to convert data from hexadecimal to binary. In this example, no Special Message buffer is defined in the application for station 1.

Hex

0

1

2

3

Binary

0000

0001

0010

0011

Table 4–15. Hexadecimal to Binary Conversion

Hex

4

5

6

7

Binary

0100

0101

0110

0111

Hex

8

9

A

B

Binary

1000

1001

1010

1011

Hex

C

D

E

F

Binary

1100

1101

1110

1111

P2521B, Volume 5, Rev. E, Nov/13 4–68 Alstom Signaling Inc.

System Diagnostics

4.5.4.3 Emulation Menu Choice: Optns

The Optns menu choice is used to view the selected communication port's setup.

Figure 4–17 shows an example screen if Optns is selected.

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Next Last Optns Msg Diags Reset TWC Vital _ Diags Exit

Baud rate = 1200 , 8 Data Bits , 1 Stop bits , Even parity

Figure 4–17. Emulation Menu – View Port Setup

P2521B, Volume 5, Rev. E, Nov/13 4–69 Alstom Signaling Inc.

System Diagnostics

4.5.4.4 Emulation Menu Choice: Msg

Message flow between the communication protocol installed on a serial port and the non-vital application logic can be monitored using the Msg menu choice. A new menu is

displayed as shown in Figure 4–18. This menu offers the following selections: Post,

Disp (Display), Spcl (Special), and Mode. These options are discussed in detail on the next few pages.

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Message Interface

Post Disp Spcl Mode Exit

Figure 4–18. Emulation Menu – Message Sub-Menu

P2521B, Volume 5, Rev. E, Nov/13 4–70 Alstom Signaling Inc.

System Diagnostics

4.5.4.5 Emulation/Message Sub-Menu Choice: Post

The Post menu choice allows user-entered keyboard input to replace the control message normally posted by the protocol emulation. This feature is useful to determine if a problem is in the application or the emulation.

To post a control, select the Post option. If more than one station exists, a prompt for the station number appears. In this case, enter the proper station number (the maximum number allowed is displayed). A prompt showing the size of the control message appears, at this point enter the new data as a series of hexadecimal bytes. When the entry is complete, the message is posted to the application logic. At most, 96 bits (12 bytes) may be manually posted. Note that if the protocol loaded on this port receives a valid control message, it is posted by the protocol, thus overwriting the control that was manually posted.

Figure 4–19 shows an example screen if the Post option is selected for a control

message containing 16 bits (2 bytes).

WARNING

Posting control data by using the post option causes changes to the operation of the system.

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Message Interface

Post Disp Spcl Mode Exit

WARNING : OPERATION WILL BE ALTERED . Enter message in HEX ( 2 BYTES ):

New Byte ( 62 H ):

Figure 4–19. Post a Control Message

P2521B, Volume 5, Rev. E, Nov/13 4–71 Alstom Signaling Inc.

System Diagnostics

4.5.4.6 Emulation/Message Sub-Menu Choice: Disp

The Disp menu choice displays the data portion of messages posted between the

protocol emulation and the non-vital application logic, updated in real-time. Figure 4–20

shows a typical screen when the display format is set to "Original"; various data display formats are offered via the Mode menu choice discussed later.

The terms "control" and "indication" refer to inbound (received) and outbound (sent) messages, respectively. A Special Message is a bi-directional buffer containing protocol-specific flags used to report or control message flow. Depending upon the application, no Special Message buffer may be defined. The use of flags in the Special

Message buffer varies among the communication protocols supported in iVPI. For specifics, refer to each protocol's manual (Alstom publication series P2346).

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Message Interface

Post Disp Spcl Mode Exit

Last control posted :

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Last indication posted

00

:

Last Special message posted :

Figure 4–20. Display Messages in Real-Time

P2521B, Volume 5, Rev. E, Nov/13 4–72 Alstom Signaling Inc.

System Diagnostics

4.5.4.7 Emulation/Message Sub-Menu Choice: Spcl

The Spcl menu choice allows user-entered keyboard input to be posted to the protocol's

Special Message buffer. To post a Special Message, select the Spcl option. If more than one station exists, a prompt for the station number appears. In this case, enter the proper station number (the maximum number allowed is displayed). A prompt showing the size of the Special Message appears, at this point enter the new data as a series of hexadecimal bytes. When the entry is complete, the message is posted to the application logic. At most, 96 bits (12 bytes) may be manually posted. Note that if the protocol loaded on this port receives messages, this may cause the protocol to write to the Special Message buffer, potentially overwriting the information that was manually posted.

Figure 4–21 shows an example screen if the Spcl option is selected for a Special

Message containing 24 bits (3 bytes).

WARNING

Posting special message data by using the Spcl option causes changes to the operation of the system.

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Message Interface

Post Disp Spcl Mode Exit

WARNING : OPERATION WILL BE ALTERED . Enter message in HEX ( 3 BYTES ):

New Byte ( 0 CH ):

Figure 4–21. Post a Special Message

P2521B, Volume 5, Rev. E, Nov/13 4–73 Alstom Signaling Inc.

System Diagnostics

4.5.4.8 Emulation/Message Sub-Menu Choice: Mode

The Mode menu choice results in the display of several additional menu options that affect the format of message data displayed using the Disp option in the Message

Submenu as shown in Figure 4–22. After the display format has been set to either

Original, New Hex, Binary or Inverse, message contents are automatically displayed and updated in real-time as if the Disp menu choice had been selected.

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Message Interface

Post Disp Spcl Mode

Original New Hex

Exit

Binary Inverse Exit

Figure 4–22. Select the Message Display Mode

P2521B, Volume 5, Rev. E, Nov/13 4–74 Alstom Signaling Inc.

System Diagnostics

Table 4–16 describes the message display mode options in this menu.

Table 4–16. Message Display Modes

Option Description

Original Restores the display format to the default setting. In this format, data for a single station is shown as a series of hexadecimal bytes, wrapping between lines on the display based on the message lengths for controls, indications and Special Messages.

New Hex In this format, message data is shown 24 hexadecimal bytes at a time from left to right on a single line per station for up to four stations, with the

station number shown at the start of each line of data, see Figure 4–23.

Multiple stations' data (up to four) is shown on subsequent lines as needed. If a message (control, indication, or Special) exceeds 192 bits (24 bytes), use the 'V' (increment byte numbers) and 'B' (decrement byte numbers) keys to bring additional data bytes (one at a time) into view. At most, 24 bytes of a message's data may be viewed at a time in this format.

If more than four stations are defined on the port, use the 'G' and Space

Bar keys to view data for additional stations. Press the 'H' key to bring the display back to the first station, first byte setting.

Binary

Inverse

This display format is similar to New Hex except that message data is shown eight bytes at a time in binary (eight bits per byte). The least significant bit of each byte is shown at the left of each byte of data.

For example, the hexadecimal byte 0x01 is shown as 10000000 in Binary format. Use this format to view message data exactly as posted to the non-

vital application logic. Figure 4–24 contains the same data shown in

Figure 4–23 (New Hex format), but in Binary format instead.

This display format is similar to Binary except that the least significant bit of each byte is shown at the right of each byte of data.

For example, the hexadecimal byte 0x01 is shown as 00000001 in Inverse format.

P2521B, Volume 5, Rev. E, Nov/13 4–75 Alstom Signaling Inc.

System Diagnostics

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Message Interface

02

03

Post Disp

Bit

Spcl Mode Exit V _ Left B _ Right G _ Up _ Down Home

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Last control posted

01

:

00 04 00 00 00 00 00 26 00 51 00

00 00 00 00 00

00 00 00 00 00 00

F 2 00 00 00

04 00 00 00 00 00 00 00 00 00 00 00 00

Last indication posted :

01

02

03

1 C 02 4

00

00

A 00 01

04 00 00

Last Special message posted

01 0 A 12 00

:

Figure 4–23. Display Messages – New Hex Display Option

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Port Message Interface

Post Disp

Bit

Spcl Mode Exit V _ Left B _ Right G _ Up _ Down Home

01 02 03 04 05 06 07 08

Last control posted

01

:

00000000 01000000 00000000 00000000 00000000 00000000 00000000 01100100

02

03

04

00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Last indication posted

01

:

00111000 01000000 01010010 00000000 10000000

02

03

04

00000000

00000000

00000000 00000000

01

Last Special message posted

01010000 01001000 00000000

:

Figure 4–24. Display Messages – Binary Display Option

P2521B, Volume 5, Rev. E, Nov/13 4–76 Alstom Signaling Inc.

System Diagnostics

4.5.5 Emulation Diagnostics Menu

Select Diags from the Emulation Menu for protocol-specific diagnostic functions. Refer to Alstom publication P2346E for detailed information on Alstom's DataTrain VIII

protocol. Figure 4–25 shows a typical protocol diagnostics menu, specifically the

DataTrain VIII Diagnostics Menu. Several DataTrain VIII diagnostic screens are available, only the Counts function is discussed in this manual.

Selection Path:

• Main Menu

– Emulation

– Port (serial port selection from 1 to 5)

– Diags

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module

Counts Reset Show Info Local Timers Flags Exit

Figure 4–25. DataTrain VIII Diagnostics Menu

P2521B, Volume 5, Rev. E, Nov/13 4–77 Alstom Signaling Inc.

System Diagnostics

4.5.5.1 DataTrain VIII Counts Screen (Emulation Diagnostics)

Select the DataTrain VIII Counts menu choice to check the status of communications on the selected port. This dynamically updated screen may be out of step with the actual

I/O because of a particular combination of application choices. Figure 4–26 shows a

typical DataTrain VIII messages counts screen.

Selection Path:

• Main Menu

– Emulation

– Port (serial port selection from 1 to 5)

– Diags

– Counts

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Emulation Control Module addr ain bin cin din ein aout bout cout dout eout ack c

50 0 0 0 0 0 0 0 0 0 55 55 1

Msg Abborts = 1

_ state

Counts Reset Show Info Local Timers Flags Exit

Figure 4–26. DataTrain VIII Counts Screen

While viewing the messages counts, use the Reset option to set the number of messages both sent and received to zero (doing so has no affect on system operation).

In this screen "ain" is the total number of DataTrain VIII Acknowledge messages (type

AA) received, whereas "aout" is the total number of Acknowledge messages sent, and

"bin" is the number of Poll messages (type AB) received.

P2521B, Volume 5, Rev. E, Nov/13 4–78 Alstom Signaling Inc.

System Diagnostics

4.5.6 Monitor Menu

The data monitor screen is viewed by selecting Monitor from the Main Menu. Use the data monitor to observe message traffic on one or more code system ports, as shown in

Figure 4–27.

Selection Path:

• Main Menu

– Monitor

– Port (port selection from 1 to 5)

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Monitor Module

Logging : ON

DC events : OFF

Scroll : ON

Serial messages

Field Changes

ANSI mode : OFF

: OFF Other messages

Ports : 1

Local I /

: REMOTE

: OFF

O Change DC Other Ansi Scroll Port EXIT

> T < AE 50 00 00 00 00 00 00 00

> R < 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

> S < 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

> T < AE 50 00 00 00 00 00 00 00

> R < 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

> S < 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Figure 4–27. Data Monitor Screen

Data monitor operation is a background task. The displayed information may be preempted by other processor operations of a higher priority. As a result, it may not be possible to report all code system port message traffic in monitor mode. Split bytes and

CRC checksums are not shown on this display.

P2521B, Volume 5, Rev. E, Nov/13 4–79 Alstom Signaling Inc.

System Diagnostics

Table 4–17 provides a description of the choices available in the Monitor Menu.

Table 4–17. Monitor Menu Choices

Option Description

Local

I/O

Change Toggle the field changes display. When this option is on, field I/O are displayed in order of their occurrence.

DC

Other

Toggle the input/output status display.

Display DC type events (not used in electronic code applications).

Display communication error messages and other miscellaneous message types.

Ansi

Toggle the Local/Remote serial message flag. When in Local mode, only local messages are displayed.

Scroll

Port

EXIT

Select ANSI mode in which the unit sends control codes to format the screen so that data appears in organized order. These codes cannot be used if a printer or other device is connected to the port.

Start or stop updating the screen so that message traffic can be monitored and displayed in real time.

Select the number of the port (or ports), from 1 to 5, to monitor and display.

Activity on multiple ports may be observed at the same time.

Exit the data monitor. Note that Ctrl + 'E' should not be used to exit from the data monitor screen.

P2521B, Volume 5, Rev. E, Nov/13 4–80 Alstom Signaling Inc.

System Diagnostics

The status of the data monitor fields is displayed at the top of the screen, as shown in

Table 4–18.

Table 4–18. Data Monitor Status Indicators

Field Description

Logging

Scroll

On/off status of the data monitor, this is normally turned on.

On/off status of the display, turn "Scroll" on for real-time display of message traffic.

DC Events On/off status of the DC display, this is normally turned off.

Serial Messages Serial message type (remote or local); this is normally set to remote.

Field Changes Field changes display is turned on or off; this is normally turned off.

Other Messages Other messages display is turned on or off; this must be on for error messages to be displayed.

ANSI Mode ANSI display mode is turned on or off; this is normally turned off.

Ports Reports message traffic for only the code line ports displayed.

When "Scroll" is on, message traffic on the selected port(s) is displayed. A descriptor indicating the type of message received or transmitted precedes each message.

Message descriptions are summarized in Table 4–19.

Table 4–19. Message Descriptors

Message Type Description

>T<

>R<

Transmitted message (for example, an indication).

Received message (for example, a control).

>P<

>S<

>-CFG-<

Received poll message.

Supervisory or status message.

Received system configuration message.

ERROR The received message contained an error.

Communication problems can be monitored in this screen and are displayed in error messages. Specific messages vary between the communication protocols supported by

Alstom. Note that "Other Messages" must be turned on in order for error messages to be displayed by the data monitor.

P2521B, Volume 5, Rev. E, Nov/13 4–81 Alstom Signaling Inc.

System Diagnostics

4.5.7 System Configuration Information

System configuration information is displayed by selecting System from the Main Menu.

This screen shows system configuration information, including the system and CAA drawing numbers, application compilation time, system compilation time, and active serial ports and their usage. No options are available from this screen; press any key to

return to the Main Menu. Figure 4–28 shows a typical system configuration screen.

Selection Path:

• Main Menu

– System

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

Main Menu

Application Software : 33028 - 982 GR 00 H Generated : 08 / 31 / 2001 13 : 51

CSEX ID : LOCATION XYZ

CAA Drawing No . : 31746 - 029 GR 00

System Generated : 51615 - 408 - 12 Rev H 12 Jul 21 2000 , 16 : 14 : 23

51612 - 012 - 016 Rev A 16 CenTraCode II Data Logger Apr 30 2001 at 12 : 44 : 50

Port 1 : 51612 - 001 - 23 REV F 36 Aug 31 , 2001 , 13 : 49 : 56 DATATRAIN ( R ) VIII

Port 2 : Not used

Port 3 : Not used

Port 4 : Not used

Port 5 : Not used

Figure 4–28. NVSP System Configuration Screen

P2521B, Volume 5, Rev. E, Nov/13 4–82 Alstom Signaling Inc.

System Diagnostics

4.5.8 System Diagnostics Menu

The System Diagnostics Menu is displayed by selecting Diagnostic from the Main

Menu. The System Diagnostics Menu provides access to the hardware so that low level testing can be done. The menu also provides access to many board functions such as the non-vital I/O, serial ports, DC interface, memory, and much more. Some options when executed may result in disruption of online operation. These tests are only

intended to be run when the system is offline. Figure 4–29 shows the System

Diagnostics Menu. Table 4–20 summarizes the system diagnostic menu choices.

Selection Path:

• Main Menu

– Diagnostic

ALSTOM SIGNALING

Non-Vital System Processor Maintenance System

System Diagnostics

I / O DC line Ports Clock Memory Variable Show

Ok _ Stack _ Test Exit

_ Port Next Test _ Ports ROM _ Chksum

Figure 4–29. NVSP System Diagnostics Menu

System diagnostic options can be selected from the System Diagnostics Menu and from a Secondary Diagnostics Menu (described later) that is accessed via the Next menu choice in the System Diagnostics Menu. Each menu choice leads to a submenu or requires user input. The choices available in the System Diagnostics Menu are listed next. Most menu choices are intended for use by Alstom technical personnel for system troubleshooting, and are not intended for field maintainer use. Some options that affect system operation can be password-protected.

P2521B, Volume 5, Rev. E, Nov/13 4–83 Alstom Signaling Inc.

System Diagnostics

I/O

Option

DC-line

Ports

Table 4–20. System Diagnostic Menu Choices (Cont.)

Description

This option leads to a submenu. Use the Local menu choice in this submenu to view the current state of all non-vital inputs and outputs in the iVPI system. I/O states are updated in real-time only after the

Disp menu choice has been selected. The state of an input port is either on (1) or off (0), and each is debounced at the rate shown (e.g.

50ms).

The state of each output port depends upon its definition in the application, and is shown as a single hexadecimal digit. Each bit

(four total) of this hexadecimal digit represents the various types of non-vital outputs (NVO) available in a iVPI system, as shown below:

Code NVO State

0001 (1) Steady on

0010 (2) Source

0100 (4) Pulse, width 1

0101 (5) Pulse, width 2

1000 (8) Normal flash, phase A

1001 (9) Fast flash, phase A

1100 (C) Normal flash, phase B

1101 (D) Fast flash, phase B

From the I/O submenu, individual outputs may be turned on and off manually using the Off, Pulse and Flash menu choices. To do so, first halt the non-vital application logic using the CAA menu choice.

Note that this action affects normal system operation.

Use the Rate and Mode menu choices to vary the type of each pulsed or flashed output port, and use the All menu choice to apply the latest output type selected to all displayed output ports. The

Src/Snk (sink and source) menu choice is applicable to CenTraCode

II-s only, and not to NVSP.

Monitor the DC codeline, or toggle a DC relay. This menu choice is primarily intended for use by Alstom technical personnel.

View a code line port's setup and current status, and manually modify its configuration (using the CFG submenu choice). Also allows hardware control lines to be manually toggled. This menu choice is primarily intended for use by Alstom technical personnel.

P2521B, Volume 5, Rev. E, Nov/13 4–84 Alstom Signaling Inc.

System Diagnostics

Table 4–20. System Diagnostic Menu Choices (Cont.)

Option Description

Clock

Memory

Variable

Set the system's battery-backed real-time clock (RTC) date/time registers. The RTC is used primary to time-stamp events stored by

Alstom's optional DataLogger module (refer to Alstom publication

P2326D). The NVSP clock must be initialized when the iVPI system is first put into service or power to the module is left off for more than

48 hours. To set the RTC, use the Clock menu choice followed by the Time (T), Date (D) and then the Initialize (I) submenu choices.

Take care to enter the date and time in the exact format shown.

Select Exit (E) when done.

Display an area of NVSP system memory, 256 bytes at a time, and optionally modify a byte of memory. The RAM starting address must first be entered in Intel-hex segment:offset notation (ssss:oooo). This menu choice is primarily intended for use by Alstom technical personnel.

Examine the contents of a non-vital memory location. The address to be monitored must be entered in Intel-hex segment:offset notation

(ssss:oooo). Typically, this is the address of a non-vital application parameter obtained from the Symbol Table Report in the application's LCS file. Either a 1- or 2-byte (integer) location may be monitored. Press any key to stop monitoring the variable.

Show_Port

Next

Examine the contents of a CPU I/O port. This menu choice is to be used by Alstom technical personnel only.

Advance to the next level of CenTraCode II diagnostics and display

the Secondary Diagnostics Menu described in Table 4–21.

Test_Ports Enable the system's "serial port test". Doing so severely encumbers system operation and is to be used by Alstom technical personnel only.

ROM_Chksum Display the checksum stored in the combined system/application program memory (PROM).

Ok_Stack_Test Test stack space used by the currently running system task. This menu choice is to be used by Alstom technical personnel only.

Exit Return to the Main Menu.

The Secondary Diagnostics Menu is accessed using the Next menu choice in the

System Diagnostics Menu. It offers additional diagnostic features, most of which are intended for use by Alstom technical personnel for system troubleshooting, and is not intended for field maintainer use. The choices in the Secondary Diagnostics Menu are summarized in Table 4–21.

P2521B, Volume 5, Rev. E, Nov/13 4–85 Alstom Signaling Inc.

System Diagnostics

Table 4–21. Secondary Diagnostics Menu Choices

Option Description

Mode

Time

Change the operating mode of one of the system's tasks. This menu choice affects system operation and is to be used by Alstom technical personnel only.

Computes and displays average timing of the non-vital application logic and the tasks running in the system. This is a non-destructive test.

Typically, the calculation is based on 1000 tasking loops and a timing base of 1 and a resolution of 1. This menu choice is primarily intended for use by

Alstom technical personnel.

Remove Remove a task from the system's round-robin task loop. This menu choice affects system operation and is to be used by Alstom technical personnel only.

Insert Insert a task into the system's round-robin task loop. This menu choice affects system operation and is to be used by Alstom technical personnel only.

CAA

Oprtr

Disp

Suspend/resume operation of the non-vital application logic. This menu choice affects system operation and is to be used by Alstom technical personnel only.

Change the operating mode of one of the system's tasks (similar to the

Mode menu choice). This menu choice affects system operation and is to be used by Alstom technical personnel only.

Display information on all currently installed system tasks, such as stack space and usage. This menu choice is primarily intended for use by Alstom technical personnel.

Reset

Exit

Show the total number of system resets since power up, and optionally perform a manual system reset. Use this choice with care since it causes the NVSP software to reinitiate its start-up sequence, as if the system were turned off and back on.

Sys_Err

List all system diagnostic messages logged since power up. Refer to Table

4–10 for all system messages that may be logged by the self-checking

mechanism built into the NVSP System Software. All accumulated messages (up to 128) are automatically shown above the Main Menu, or may be viewed by selecting the Sys_Err menu choice in the Secondary

Diagnostics Menu. In the latter case, messages may be erased from memory by selecting 'R' (Reset).

Return to the System Diagnostics Menu.

P2521B, Volume 5, Rev. E, Nov/13 4–86 Alstom Signaling Inc.

System Diagnostics

Table 4–10 lists all system diagnostic messages that may be displayed at the MAC port

diagnostic menu. Note that all logged messages are lost by the system in the event of power loss.

All accumulated diagnostic messages (up to 128) are automatically shown above the

Main Menu, or may be viewed by selecting the Sys_Err menu choice in the Secondary

Diagnostics Menu. Displayed error messages are of the form:

"mm dd hh:mm:ss – Severity code – message"

P2521B, Volume 5, Rev. E, Nov/13 4–87 Alstom Signaling Inc.

System Diagnostics

4.6

4.6.1

EMBEDDED DATALOGGER (DL)

General Information

An Alstom Signaling NVSP system is composed of several software modules. Each module is dedicated to performing a specific function in the system. Although all modules do not share data with each other, all have links to the operating system software. Alstom's optional Embedded DataLogger module provides the user with realtime on-line event logging with time-stamping and reporting capabilities. Complete detail on DataLogger can be found in Alstom publication P2346D.

When used in an application, the DataLogger (DL) module provides interfaces suitable for accepting data to be logged from other installed modules. It also provides three Non-

Vital Application (NVA) monitoring modules. These modules perform specific functions and pass data to the DL for storage. The first of the three modules is dedicated to monitoring changes in user-composed messages called User Non-Vital Messages

(UNVM) or simply User Messages. The second module is dedicated to monitoring changes occurring at Non-Vital Inputs (NVI) and the third is dedicated to monitoring changes occurring at Non-Vital Outputs (NVO).

4.6.2 Real-Time Clock

All logged data bears a time stamp resolved to one second relative to the system clock.

NVSP boards are equipped with a battery-supported, hardware-based Real-Time Clock

(RTC).

P2521B, Volume 5, Rev. E, Nov/13 4–88 Alstom Signaling Inc.

System Diagnostics

4.6.3 Memory Usage

Each NVSP system reserves 256Kbytes of battery-backed memory (BBRAM) for data logging. The DL partitions its assigned memory space into three major components: the

Scratch Pad, the Directory, and the Data Log Area, see Table 4–22.

Table 4–22. DataLogger Memory Usage

Memory Location Content

Scratch Pad (234 bytes)

Directory (3840 bytes)

Operating parameters and intermediate variables are stored in this area.

This area contains room for 192 Directory

Frames (20 bytes each).

Data Log Area (258,070 bytes) Log Frames are stored in this area.

Scratch Pad: The DL program reserves 234 bytes of its memory to support housekeeping activities. This secured area, referred to as the Scratch Pad, holds the

DataLogger's operating parameters and intermediate data.

Directory: Another 3,840 bytes of the DataLogger's memory hold Directory Frames. This area is a circular buffer large enough to hold 192 Directory Frames. A record is entered in this area to mark the creation of a new directory, typically each hour. Each record has a fixed length of 20 bytes and is referred to as a Directory Frame.

Data Log Area: The remaining portion of DataLogger's memory is used for recording logged events, called Log Frames. The first 17 bytes of each Log Frame contain overhead information that distinguishes the different types of event data. Log Frames are variable in length due to the various types of data that may be logged.

The Data Log Area is a circular buffer. Events are logged in consecutive memory locations until the end of the area has been reached, at which time the DL restarts at the beginning of the Data Log Area to store subsequent event data. This "wrap around" causes the data stored at the beginning of memory to be overwritten. This overwrite can be inhibited by utilizing the Timed Data Protection mechanism provided by the DL.

P2521B, Volume 5, Rev. E, Nov/13 4–89 Alstom Signaling Inc.

System Diagnostics

4.6.4 Directory Frames

A Directory Frame is stored when any of these events occur:

• System Reset: when the NVSP system is reset or powered up

• Start of Each Hour: when the system clock advances to a new hour

• Clock Setting: when the operator modifies the system date or time through the

DataLogger's password protected clock-setting utility

• End of Memory: when the DL reaches the end of the Data Log Area (end of actual memory), and Timed Data Protection has expired for the oldest directory data

• Erasure of Current Directory: when an erase command is issued for the currently open directory

In all five instances, the creation of a new Directory Frame can be inhibited by the enforcement of Timed Data Protection wherein logs are protected from being overwritten until the data is older than the user-specified duration. A new Directory

Frame is not created until after timed protection expires.

A Directory Frame contains the following information:

• Date and time of creation

• Primary and secondary status indicators

• A log count (number of events)

• A pointer (address) to the first logged event associated with this directory

• A moving pointer to the last event associated with this directory

4.6.5 Log Frames

A Log Frame is composed of event and descriptive data. An event's data is generated by different CTC software modules and passed to the DL for storage. The descriptive portion of a Log Frame has a fixed length used to identify the type and source of the event data.

P2521B, Volume 5, Rev. E, Nov/13 4–90 Alstom Signaling Inc.

System Diagnostics

4.6.6 Logging Capacity

The logging capacity of DataLogger can be roughly expressed in terms of the maximum number of events that can be stored.

In this example, it is assumed that DataLogger is configured to log only changes to User

Message parameters, and that a single parameter changes state in each event. In this case, each stored event (Log Frame) requires 19 bytes of memory: 17 bytes of overhead plus 2 bytes of data for the parameter that changed state. NVSP boards have

258070 bytes of RAM for data logging. Therefore, in this example, 13582 events

(258070/19) are logged before memory becomes full. Be aware that this is approximate, since periodically (typically every hour) DataLogger also automatically stores a snapshot of all parameters.

To estimate capacity in total logging time, estimate how many events typically occur each hour. Using the previous example and assuming an average of 4 events per minute (240 per hour), DataLogger memory becomes full in about 56.6 hours

(13582/240) – approximately 2.3 days. Adjust this calculation based upon the expected frequency of events.

In a given application, it may be determined that typically multiple parameters change at once, and are therefore logged as a single event. In this case, a typical event log contains more than just a single parameter change and is larger than the 19 bytes shown in the example above. Calculate the size (in total number of bytes) of a typical

Log Frame as follows:

• 17 bytes of overhead; plus

• 2 bytes multiplied by the average number of parameters that change state in each event

For example, if a typical event contains three parameter state changes, the size of a typical Log Frame is 23 bytes (17+2*3) resulting in a storage capacity of 11220 events

(258070/23).

P2521B, Volume 5, Rev. E, Nov/13 4–91 Alstom Signaling Inc.

System Diagnostics

4.6.7 Data Protection

The DL stores Log Frames in contiguous memory locations. When the DL runs out of room in the Data Log Area, it seeks to overwrite the logs that belong to the oldest directory. An optional Timed Data Protection mechanism exists to allow users to prevent logs from being overwritten. The user specifies the minimum length a Directory Frame is to be saved after is it created. The specification is made once and applies uniformly to all directories.

4.6.8 Log Area Reclamation

The DL reclaims an entire directory's Data Log Area at a time. Given the same log sources and types, the size of a directory's memory area varies with the number of logs taken. Areas occupied by periods of heavy traffic are larger than those with little or no traffic. When the DL reclaims a Data Log Area, the status indicator in the Directory

Frame that describes the area indicates expired. Data in an expired area cannot be meaningfully interpreted.

Provisions, accessible through the DataLogger's diagnostics, exist to allow a user to erase and recover memory blocks. When an area is erased, the status in its Directory

Frame indicates erased. The erasure of an area is simply a change in status and is not destructive to the previously logged data in that area. However, an erased area loses its timed protection. When the DL runs out of room and encounters an erased area, it sets the area to 'expired' and proceeds to overwrite it with new logs.

The status of unexpired and unerased directories is normally set to valid. An erased area can be recovered only as long as the DL has not run out of memory and has not set the directory's status to 'expired.'

4.6.9 System Overloading

An NVSP system primarily serves as a code system emulator. Its flexibility has allowed it to fill a much wider range of applications. However, it is possible to overload an NVSP system by setting up the DL to record a wide range of frequently-changing parameters in a system configured with fast communication protocols for code system emulation.

Application designers should limit loading to essential requirements and set up the DL to record only needed parameters.

Another example of how a system can be overloaded is to configure the DL to log code line messages (such as serial controls and indications) in Direct mode. Direct mode introduces an overhead that handicaps code line systems that operate with short inter-scan delays (the time interval between messages received by the NVSP system).

P2521B, Volume 5, Rev. E, Nov/13 4–92 Alstom Signaling Inc.

Board Replacement

SECTION 5 – BOARD REPLACEMENT

5.1 GENERAL

This section provides board replacement procedures for each of the boards used in the iVPI system.

5.2 SYSTEM BOARDS

Some board types have configuration data that must remain intact if the board is replaced with a spare.

The VSP and NVSP boards contain system software and application logic that must be reinstalled on replacement boards and verified by procedures outlined later in this

Section. Doing this is essential to restoring proper operation to the iVPI system.

5.3 BOARD REPLACEMENT PROCEDURES

Once a faulty board is identified using the procedures described earlier, follow these steps to replace it and to verify proper operation of the new board. While these tests apply to many types of iVPI repairs, they must not be considered as exhaustive procedures applicable to all possible situations. Use them as guidelines to develop tests that are suited to the requirements of the specific installation.

P2521B, Volume 5, Rev. E, Nov/13 5–1 Alstom Signaling Inc.

Board Replacement

5.4 VITAL BOARD REPLACEMENT

WARNING iVPI contains special safety circuit components which must only be replaced by components specified by the Alstom part number.

These original-design replacement parts are manufactured to the same standards as the original parts; their performance being verified. The use of replacement parts that are not of the same Alstom part number could potentially impair the safe performance of the system.

The railroad or transit system authority and the manufacturer of an aftermarket (i.e., non-Alstom designated) part assume the responsibility that the part will not adversely affect the safe performance of the system. The authority and the manufacturer of the aftermarket part must analyze and certify in writing that use of the part will not result in a failure of the system to comply with safety regulations and safety performance. Completion of such an analysis and certification is considered due diligence and standard practice, will not be reviewed or approved by Alstom, and neither absolves the authority and aftermarket part manufacturer of responsibility nor implies approval by Alstom to use such an aftermarket part. The responsibility of any consequences resulting from using such a part remains with the authority and part manufacturer.

CAUTION

Voltage potentials in the Module could damage printed circuit boards if removed with power applied. Disconnect power from the Module prior to removing boards. Failure to do so could result in damage to the boards.

Boards in the Module contain Electrostatic Discharge (ESD) sensitive components that could be damaged by improper handling. Always ensure boards are transported and stored in static-safe packaging. Before handling any bare board or connecting diagnostic equipment to any board, touch something verified to be grounded and work wearing at least a grounded static-control wrist strap whenever possible. Handle boards only by their edges and do not touch signal traces, leads or output pins on the boards.

P2521B, Volume 5, Rev. E, Nov/13 5–2 Alstom Signaling Inc.

Board Replacement

CAUTION

When replacing boards in a Vital, electronic system, the user should be guided by the instructions and requirements of the operating agency with regard to any testing that must be performed before placing the altered equipment back in service.

5.4.1 VSP Board (P/N 31166-427-XX)

Table 5–1. VSP Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove the failed board.

3 Install software and application on the spare board.

4 Install replacement board, apply system power, and observe the processor messages for errors.

5 If no errors occur, verification of board functionality is complete.

6 Record the system configuration data on the Logic Configuration Log Sheet used during installation especially when using spare software sets. The log

sheet is provided in APPENDIX A – Data Log Sheet.

7 Use a terminal connected to VSP board and record system configuration data as described in P2521B, Volume 1.

8 Verify that the configuration data matches exactly that recorded when the system was last commissioned for service.

CAUTION

If the data does not match, do not place system in service until the reason for the discrepancy is found and accepted. This may require running the Application Data Verifier (ADV) program and comparing current system documentation to that archived when the system was commissioned for service.

9 Return the iVPI system to service. Observe system operation for at least 5 minutes to ensure that all errors have been corrected.

10 Record maintenance performed in the Service Log.

P2521B, Volume 5, Rev. E, Nov/13 5–3 Alstom Signaling Inc.

Board Replacement

5.4.2 CRG Board (P/N 31166-459-XX)

Table 5–2. CRG Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove the failed board.

3 Install replacement board, apply system power and observe VT100 emulation for further errors.

4 If no errors occur, verify board functionality. Exercise the system logic such that each output is energized and then de-energized.

Repeat this for all outputs on the board. Observe the system for proper operation by ensuring that the wayside equipment connected to each output is operating properly and matches the associated output indicator.

5 Return iVPI system to service and record maintenance performed in the Service

Log.

5.4.3 DI Board (P/N 31166-429-XX)

Table 5–3. DI Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove the failed board.

3 Install replacement board, apply system power and observe VT100 emulation for further errors.

4 If no errors occur, verify board functionality. Energize and subsequently deenergize each input and verify the system operates as intended.

5 Return iVPI system to service and record maintenance performed in the Service

Log.

P2521B, Volume 5, Rev. E, Nov/13 5–4 Alstom Signaling Inc.

Board Replacement

5.4.4 GTP Board (P/N 31166-434-XX)

Table 5–4. GTP Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove the failed board.

3 Install software on the spare board.

4 Install replacement board, apply system power and observe VT100 emulation for further errors.

5 If no errors occur, verify board functionality. Exercise the system logic such that each track output is energized and then de-energized.

Observe the system for proper operation.

6 Return iVPI system to service and record maintenance performed in the Service

Log.

5.4.5 SBO, LDO, ACO, DBO Boards

(P/N 31166-430-XX, -431-XX, -432-XX, -433-XX)

Table 5–5. SBO, LDO, ACO, DBO Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove the failed board.

3 Install replacement board, apply system power, and observe VT100 emulation for further errors.

4 If no errors occur, verify board functionality. Exercise the system logic such that each output is energized and then de-energized.

Repeat this for all outputs on the board. Observe the system for proper operation by ensuring that the wayside equipment connected to each output is operating properly and matches the associated output indicator.

5 Return iVPI system to service and record maintenance performed in the Service

Log.

P2521B, Volume 5, Rev. E, Nov/13 5–5 Alstom Signaling Inc.

Board Replacement

5.4.6 System ID Board

(P/N 31166-472-XX) and Vital Interface Boards

(P/N 31166-473-XX and 31166-485-XX)

Table 5–6. System ID Board and Vital Interface Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove the mounting screws securing the board to the appropriate P connector on the VSP or BEX Board

3 Remove the failed board.

4 Install replacement board, reinstalling the mounting screws.

Note: If replacing the System ID board, verify the address configured on the new board matches that of the failed board.

5 Apply system power.

6 Return iVPI system to service and record maintenance performed in the Service

Log.

P2521B, Volume 5, Rev. E, Nov/13 5–6 Alstom Signaling Inc.

Board Replacement

5.5 NON-VITAL BOARD REPLACEMENT

CAUTION

When replacing boards in a Vital electronic system, the user should be guided by the instructions and requirements of the operating agency with regard to any testing that must be performed before placing the altered equipment back in service.

CAUTION

Voltage potentials in the Module could damage printed circuit boards if removed with power applied. Disconnect power from the Module prior to removing boards. Failure to do so could result in damage to the boards.

Boards in the Module contain Electrostatic Discharge (ESD) sensitive components that could be damaged by improper handling. Always ensure boards are transported and stored in static-safe packaging. Before handling any bare board or connecting diagnostic equipment to any board, touch something verified to be grounded and work wearing at least a grounded static-control wrist strap whenever possible. Handle boards only by their edges and do not touch signal traces, leads or output pins on the boards.

P2521B, Volume 5, Rev. E, Nov/13 5–7 Alstom Signaling Inc.

Board Replacement

5.5.1 NVSP Board (P/N 31166-428-XX)

Table 5–7. NVSP Board Replacement Procedure

Step Procedure

1 Remove system power and communications power.

2 Remove failed board.

3 Install software on replacement board.

4 Place board jumpers appropriately, compare jumper locations to those on failed board.

5 Place configuration switches appropriately by comparing the switches to those on the failed board.

6 Install replacement board.

7 Apply system power.

8 Verify board functionality by exercising local and remote control operations, non-vital logic operation and/or non-vital field indications and communication

(all where applicable).

9 Return iVPI system to service and record maintenance performed in the Service

Log.

P2521B, Volume 5, Rev. E, Nov/13 5–8 Alstom Signaling Inc.

Board Replacement

5.5.2 NVSP Board Battery (P/N 52397-011-00)

Table 5–8. NVSP Board Battery Replacement Procedure

Step Procedure

1 Retrieve all Log data prior to replacing battery.

2 Remove system power and communications power.

3 Remove NVSP board.

4 Remove battery from battery holder clip.

5 Install new battery, P/N 52397-011-00, Lithium Coin Cell 2032,3V

6 Reinstall NVSP board.

7 Apply system power.

8 Set Date/Time on NVSP board.

9 Verify board functionality by exercising local and remote control operations, non-vital logic operation and/or non-vital field indications and communication

(all where applicable).

10 Return iVPI system to service and record maintenance performed in the Service

Log.

5.5.3 NVI Boards (P/N 31166-457-XX)

Table 5–9. NVI Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove failed board.

3 Install replacement board.

4 Apply system power.

5 Return iVPI system to service and record maintenance performed in the Service

Log.

P2521B, Volume 5, Rev. E, Nov/13 5–9 Alstom Signaling Inc.

Board Replacement

5.5.4 NVO Boards (P/N 31166-458-XX)

Table 5–10. NVO Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove failed board.

3 Install replacement board.

4 Apply system power.

5 Return iVPI system to service and record maintenance performed in the Service

Log.

5.5.5 NVSP Interface Boards (P/N 31166-474-XX, 31166-475-XX)

Table 5–11. NVSP Interface Board Replacement Procedure

Step Procedure

1 Remove system power.

2 Remove the mounting screws securing the board to the appropriate P connector on the NVSP Board

3 Remove the failed board.

4 Install replacement board, reinstalling the mounting screws

5 Apply system power.

6 Return iVPI system to service and record maintenance performed in the Service

Log.

P2521B, Volume 5, Rev. E, Nov/13 5–10 Alstom Signaling Inc.

Data Log Sheet

SECTION 6 – VITAL BOARD VERIFICATION

6.1 GENERAL

This Section covers verification testing of Vital input and output boards.

6.2 INTRODUCTION

The procedures provided in the Section indicate that the ports should be verified by testing the function controlled by the input or output. The technician must be familiar with the operation of the related portion of the system. The technician identifies a specific input or output device, then "exercises" the board to verify that it is properly interfaced with the iVPI system by noting that the expected response occurs. Specific examples of each possible verification scenario are not provided, as the number of possible combinations is too large to be useful.

6.3 VITAL INPUT BOARDS

Follow Table 6–1 to test each input port.

Table 6–1. Vital Input Board Functionality Test Procedure

Step Procedure

1 Using iVPI Output Report LVC, note the functions assigned to each input. For example: VRDFRNT-DI; input from VRD relay, NWP-DI; input from switch machine.

2 Using Book of Plans, note the required input condition for each of the listed functions.

3 Enable then disable each input, noting the functional response to the input status change.

P2521B, Volume 5, Rev. E, Nov/13 6–1 Alstom Signaling Inc.

Data Log Sheet

6.4 VITAL OUTPUT BOARDS

Follow Table 6–2 to test each output port.

Table 6–2. Vital Output Board Functionality Test Procedure

Step Procedure

1 Using iVPI Output Report LVC, note the functions assigned to each output. For example: NW-DBO; output to switch machine; 2W-LDO; output to signal.

2 Using Book of Plans, note the apparatus connected to each of the listed functions.

3 By initiating the appropriate request, enable then disable each output, noting the response of the apparatus to the output status change.

P2521B, Volume 5, Rev. E, Nov/13 6–2 Alstom Signaling Inc.

Data Log Sheet

APPENDIX A – DATA LOG SHEET

SOFTWARE CONFIGURATION DATA LOG

Name of Person Performing System Query:

Location of System:

System Description ( e.g., SYSTEM 1 or

MAIN SYSTEM or application name ):

IN SERVICE Date:

Current Date:

Following "RPT" Command:

CAA FILE #

INPUT FILE #

RUNDATE/TIME

VRS FILE#

VRS DATE

BOOTLOADER FILE #

BOOTLOADER DATE

BOOTLOADER SIG.

SYSTEM SOFTWARE SIG.

APPLICATION SIG.

FSSVT SIG.

Rev ID

Site ID

Figure A–1. VSP Log Sheet

P2521B, Volume 5, Rev. E, Nov/13 A–1 Alstom Signaling Inc.

Data Log Sheet

THIS PAGE INTENTIONALLY LEFT BLANK.

P2521B, Volume 5, Rev. E, Nov/13 A–2 Alstom Signaling Inc.

FOR QUESTIONS AND INQUIRIES, CONTACT CUSTOMER SERVICE AT

1-800-717-4477

OR

WWW.ALSTOMSIGNALINGSOLUTIONS.COM

ALSTOM SIGNALING INC.

1025 JOHN STREET

WEST HENRIETTA, NY 14586