270 likes | 436 Views
CBTC Standardization Can it be Achieved ? Railway Age Status Report May, 1997 T. J. Sullivan Senior Engineering Manager PB Transit & Rail Systems. Presentation Overview. Background of TCRP/IEEE Standards Process On Board Communications Standards IEEE CBTC standards process and progress
E N D
CBTC Standardization Can it be Achieved ? Railway Age Status Report May, 1997 T. J. SullivanSenior Engineering Manager PB Transit & Rail Systems
Presentation Overview • Background of TCRP/IEEE Standards Process • On Board Communications Standards • IEEE CBTC standards process and progress • What’s Over the Horizon
TCRP 1992 Origins ISTEA
Transit Cooperative Research Program • Funds Innovative Research • Problem Statements • Maximum Benefits /return
TCRP Project G4 Developing Standards for System and Subsystem Interfaces in Electric Rail Passenger Vehicles • Founding Group • Thomas J. McGean, PE • LTK Engineering • IEEE VTS & Linda Sue Boehmer • TSD Tom Sullivan • Initial Brainstorming Meeting • Identified 26 potential areas • Costs and benefits estimated • Eight Working Groups Formed • Open to any interested party - IEEE Standards
Eight Working Groups 1 - Communications 2 - CB Train Control 3 - Health Monitoring 4 - Safety Standards for Software 5 - VOBC / Propulsion / Brake 6 - Auxiliary Power Systems 7 - Vehicle Passenger Information 8 - Environmental Standards for Electrical Equipment
Eight Working Groups • 1 - Communications • 2 - CB Train Control • 3 - Health Monitoring 4 - Safety Standards for Software • 5 - VOBC/Propulsion/Brake • 6 - Auxiliary Power Systems • 7 - Vehicle Passenger Information 8 - Environmental Standards
Communications Network CB Train Control Health Monitoring VOBC/Propulsion/Brake Auxiliary Power Systems Vehicle Passenger Information
Communications Network CB Train Control Health Monitoring VOBC/Propulsion/Brake Auxiliary Power Systems Vehicle Passenger Information RADIO MODEM
WG 1 Communcations ProtocolsChair: Bob Anderson, Harmon Industries • Exhaustive search for candidate systems • Initial list reduced to two viable alternatives • Both were selected as a standard • Both can potentially interoperate • Either will do the job • Most successful working group and potentially could be as significant as WG2
Draft Communications Standards • IEEE P 1473.1 • LONWORKS™ Communications Protocol • NYC Transit new subway cars (200 subway cars/year) • AAR’s ECP Brake Program (1,000,000 box cars?) • 2 million nodes sold worldwide, >1500 OEMs • Cost effective, general purpose real-time network • IEEE P 1473.2 • IEC Train Communications Network • Special purpose real time network for rail systems • ADTranz, Siemens, Ansaldo, UITP, etc. • High performance, more expensive than P 1473.2
IEEE P 1473.1 Node • Two sources for silicon • Motorola and Toshiba • OPEN Protocol • Extensive PC-based Development Tools • Modules available from Echelon and many others • “C” Like Languageenhanced with “when” statement
P1473.1 Programming Example #1 when (doors = (open)) { brakes = ON } ; equivalent function BRAKE SYSTEM B+ DOOR SENSOR
P1473.1 Programming Example #2 when(loadweigh=AW3) { Display (Pelham 123 = (Full))} ; 20 MPH PELHAM 123 PELHAM 148 POSSIBLE CONTROL CENTER GRAPHIC SHOWING HEAVILY LOADED PELHAM 123
LONWORKS and Vehicle CBTC PWM, ANALOGOR SERIAL ONE $5 LONWORKS NEURON I.C. (THREE 8-BIT MICROPROCESSORS) Propulsion / Brake Tractive Effort P-Signal FREQUENCY Tachometers IEEE P1473.1 P W M Train Door Systems P W M EMERGENCY BRAKE ACTIVE TOGGLE SERIAL “UPLOADABLE” APPLICATION PROGRAM ( EEPROM ) WAYSIDE TAG READER SPAREI/O
WG-2 Participants(Chairs: David Rutherford & Tom Sullivan) • Weak Participation • Transit Properties(Except NYC Transit) • Industry “Deal Makers” • Good Participation • Major signal suppliers senior technical experts • AAR, FRA, FTA • Consultants • Some Communications and Radio Suppliers
WG 2Activities and Objectives • Definition • Continuous bi-directional communications • Does not require track circuits • Two Basic Philosophies • Vehicle Centric • Wayside Centric • Interoperability Objectives
How much bandwidth is Needed? • Information updates: 1-4 times/sec (transit) • SELTRAC - “Wayside Centric System” • sub 60 second capability (worst case poll 1/sec) • 1200 bits/sec from wayside to train (70 data bits) • 600 bits/sec from train to wayside (31 data bits) • You can never • be too rich • be too thin • or have too much communications bandwidth
Issues working against Standardization • Corporate Greed and Egos • Tradition • Non-technical concessions required • Many technical details • IEEE Standards require 75% to agree
Issues working for Standardization Corporate Committment to Standards NYCT’s Canarsie Line Separate Radio from Train Control TCRP- G4 The Only Forum to discuss Standards
Summary • Communications is, and will, drive everything • The “PCC” meeting for CBTC has yet to occur • Synergy • NYCT Drives Standardization • TCRP -G4 facilitate this process • Transit Property participation is strongly encouraged in TCRP G4 Program
Over the Horizon • Standardized Communication Networks • TCP/IP, LONWORKS, JAVA Internets --> Intranets --> Infranets • New York will drive CBTC standardization in US • TCRP -G4 & IEEE will facilitate standardization • End users will demand safe, non-stop systems
For More Information • CBTC Web Page • www.tsd.org • Eight TCRP Working Groups • CBTC Projects worldwide • CBTC Internet mailing list • Send a message to: cbtc@tsd.org • Ask to be placed on the list • Enter name, address, and brief biographic info.