FINAL DRAFT WAYSIDE EQUIPMENT INTERFACE SPECIFICATIONgrouper.ieee.org/groups/railtransit/wg14/WEI...

FINAL DRAFT WAYSIDE EQUIPMENT INTERFACE SPECIFICATION REVISION 1.2 DRAFT Prepared for Association of American Railroads

Committee F-1 FINAL DRAFT DECEMBER 1996

Wayside Equipment Interface Specification Final Draft, December, 1996

WAYSIDE EQUIPMENT INTERFACE SPECIFICATION TABLE OF CONTENTS

FOREWORD...............................................................................................................................................................V

1.0 INTRODUCTION ..................................................................................................................................................1

1.1 PURPOSE...............................................................................................................................................................1

1.2 SCOPE ....................................................................................................................................................................1

1.3 DEFINITIONS........................................................................................................................................................2

1.4 CONTENTS............................................................................................................................................................3

2.0 APPLICABLE DOCUMENTS..............................................................................................................................4

3.0 REQUIREMENTS .................................................................................................................................................5

3.1 LAYER 1 ...................................................................................................................................................................5 3.1.1 Synchronous RS-422........................................................................................................................................5 3.1.2 Multiplexed Asynchronous RS-232..................................................................................................................6 3.1.3 Echelon ............................................................................................................................................................8

3.2 LAYER 2 ...................................................................................................................................................................9 3.2.1 Synchronous HDLC - LAPB...........................................................................................................................9 3.2.2 Synchronous HDLC - LAPD ...........................................................................................................................9 3.2.3 Asynchronous Framing ...................................................................................................................................9 3.2.4 Echelon ..........................................................................................................................................................11

3.3 LAYERS 3 THROUGH 6 ...........................................................................................................................................12 3.3.1 Acknowledge and Retry..................................................................................................................................15 3.3.2 Addressing......................................................................................................................................................16 3.3.3 Routing...........................................................................................................................................................17 3.3.4 Packet length..................................................................................................................................................17

3.4 LAYER 7 .................................................................................................................................................................17

APPENDIX A. WAYSIDE EQUIPMENT SYSTEM MESSAGES......................................................................A-1

PING REQUEST .......................................................................................................................................................... A-2 PING RESPONSE ......................................................................................................................................................... A-4 LOOPBACK MESSAGE................................................................................................................................................ A-6 TIME REQUEST .......................................................................................................................................................... A-8 TIME RESPONSE ...................................................................................................................................................... A-10 HEALTH MESSAGE REQUEST .................................................................................................................................. A-12 HEALTH MESSAGE RESPONSE ................................................................................................................................ A-14 DEVICE CAPABILITY REQUEST ............................................................................................................................... A-18 DEVICE CAPABILITY RESPONSE.............................................................................................................................. A-19 MANUFACTURE SPECIFIC DATA.............................................................................................................................. A-20 SUBSCRIPTION REQUEST ......................................................................................................................................... A-21

Wayside Equipment Interface Specification Final Draft, December, 1996 page ii

SUBSCRIPTION RESPONSE ....................................................................................................................................... A-22 UNIT STATUS REQUEST ........................................................................................................................................... A-23 UNIT STATUS RESPONSE.......................................................................................................................................... A-24 TRAIN DIRECTORY REQUEST .................................................................................................................................. A-25 TRAIN DIRECTORY RESPONSE ................................................................................................................................ A-26 USER DEFINED STATIC EVENT ................................................................................................................................ A-29 USER DEFINED DYNAMIC EVENT ............................................................................................................................ A-30 TERMINAL EMULATION........................................................................................................................................... A-31 UPLOAD FIRMWARE REQUEST................................................................................................................................ A-32 UPLOAD FIRMWARE RESPONSE .............................................................................................................................. A-34 ERROR/ALARM CONDITION .................................................................................................................................... A-36

APPENDIX B. HOT BOX DETECTOR MESSAGES..........................................................................................B-1

HOT BOX DETECTOR AXLE DATA ............................................................................................................................ B-2 HOT BOX DETECTOR DEFECT ALARM ..................................................................................................................... B-4 HOT BOX SELF-TEST FAILURE ................................................................................................................................. B-6 HOT BOX DETECTOR TRAIN REPORT ....................................................................................................................... B-7

APPENDIX C. AEI READER MESSAGES..........................................................................................................C-1

AEI TAG DATA.......................................................................................................................................................... C-2

APPENDIX C. WHEEL IMPACT LOAD DETECTOR MESSAGES.................................................................D-1

IMPACT DETECTOR DEFECT ALARM ........................................................................................................................ D-2 IMPACT DETECTOR SKEWING ALARM...................................................................................................................... D-5 IMPACT DETECTOR OVERLOAD ALARM................................................................................................................... D-7 IMPACT DETECTOR UNBALANCED ALARM............................................................................................................... D-9 IMPACT DETECTOR CAR WEIGHT INFORMATION .................................................................................................. D-11

APPENDIX E. GRADE CROSSING DEVICE MESSAGES ...............................................................................E-1

CROSS WARNING DEFECT ALARM.............................................................................................................................E-2 CROSS WARNING INFO REPORT.................................................................................................................................E-3

APPENDIX F. WEIGH SCALE MESSAGES....................................................................................................... F-1

WEIGH SCALE DATA ..................................................................................................................................................F-2 WEIGH SCALE INFORMATION REPORT......................................................................................................................F-3

APPENDIX G. CLEARANCE (HIGH/LOW) DETECTOR MESSAGES......................................................... G-1

APPENDIX H. DRAGGING EQUIPMENT DETECTOR MESSAGES............................................................ H-1

APPENDIX I. WHEEL PROFILE MEASUREMENT DEVICE MESSAGES.................................................... I-1

WHEEL PROFILE MEASUREMENT INFO ......................................................................................................................I-2 AUTOMATIC WHEEL INSPECTION SYSTEM .................................................................................................................I-3

APPENDIX J. ACOUSTIC BEARING MESSAGES............................................................................................ J-1

ACOUSTIC DETECTOR AXLE DATA ............................................................................................................................ J-2 ACOUSTIC DETECTOR DEFECT ALARM ..................................................................................................................... J-4 ACOUSTIC SELF-TEST FAILURE ................................................................................................................................. J-6 ACOUSTIC DETECTOR TRAIN REPORT....................................................................................................................... J-7

APPENDIX K. EVENT RECORDER MESSAGES ............................................................................................ K-1

Wayside Equipment Interface Specification Final Draft, December, 1996 page iii

LOG FILE REQUEST................................................................................................................................................... K-2 LOG FILE REPLY ....................................................................................................................................................... K-3

Wayside Equipment Interface Specification Final Draft, December, 1996 page iv

WAYSIDE EQUIPMENT INTERFACE SPECIFICATION

TABLE OF FIGURES FIGURE 3-1. TYPICAL ATCS WAYSIDE ARCHITECTURE ...........................................................................................6 FIGURE 3-2. MULTIPLEXER WAYSIDE ARCHITECTURE .............................................................................................7 FIGURE 3-3. ECHELON WAYSIDE ARCHITECTURE .....................................................................................................9

Wayside Equipment Interface Specification Final Draft, December, 1996 page v

FOREWORD

This specification for the Wayside Equipment Interface (WEI) has been developed through a public open-forum process involving contracted systems engineers, railroad industry professionals, and suppliers. The purpose of this and other AAR specifications is to define the performance and interface requirements for wayside equipment hardware and software. WEI specifications are designed to document the stated requirements of railroad operational and technical professionals concerning wayside equipment hardware and software. These specifications are designed to facilitate compatibility and standardization without limiting the internal design approaches of individual suppliers. Publication of this specification does not commit any railroad to purchase any hardware or software described herein, require any railroad to use this specification for the purchase of hardware or software generally described, nor constitute endorsement of any supplier's product designed or built according to this specification. Decisions to purchase any product developed in accordance with this specification are matters of discretion and judgment on the part of individual railroads and individual suppliers. WEI specifications are recommended and approved by the AAR Committee F-1 and Hazard Defect Detection Engineering Committee.

Wayside Equipment Interface Specification Final Draft, December, 1996 page 1

1.0 INTRODUCTION 1.1 PURPOSE This document defines the protocol and contents of the messages used by wayside equipment to exchange data with other wayside equipment and with railroad networks that include central office equipment, onboard equipment, and network maintenance and diagnostic equipment. This document is intended to complement related AAR specifications, such as the ATCS specifications, to provide standards for railroad communication networks and for PTS interoperability. Equipment suppliers should note that this and related AAR specifications are meant to promote production of high-performance, low maintenance, high-reliability equipment. Suppliers are free to accomplish these objectives and satisfy the requirements of this specification by means of design techniques and technology which they consider to be cost-effective and appropriate. Suppliers and railroads purchasing hardware or software in accordance with this specification are responsible for ensuring that equipment and its application satisfy regulatory and safety requirements. 1.2 SCOPE This specification is designed to: ∃ Specify the pieces of information that must be provided by the wayside

equipment components. ∃ Specify the bit patterns to be used to encode the information to be transmitted. ∃ Specify how the encoded information is to be placed into messages. ∃ Specify the appropriate communications parameters to be used with each

message. ∃ Specify the protocols used for communication between devices The list of devices covered by this specification include: ∃ Hot Box Detector; ∃ AEI Reader; ∃ Wheel Impact Load Detector (WILD); ∃ Grade Crossing Device; ∃ Weigh Scale; ∃ Clearance (high/wide) Detector; ∃ Dragging Equipment Detector; ∃ Wheel Profile Measurement Device; ∃ Acoustic Bearing Detector; and ∃ Event Recorder.


1.3 DEFINITIONS Definitions of the terms associated with the messages and protocol defined in the WEI Specification are listed for reference. AEI - Automatic Equipment Identifier ATCS - Advanced Train Control Systems BCD - Binary Coded Decimal CRC - Cyclic Redundancy Check CTC - Central Train Control HDLC - High-Level Data Link Control MCP - ATCS/PTS Mobile Communications Package MUX - Multiplexer OSI - Open Systems Interconnection PTS - Positive Train Separation WEI - Wayside Equipment Interface WILD - Wheel Impact Load Detector Central Office Equipment - Equipment located in railroad offices that communicate with

wayside equipment. Central equipment includes, but is not limited to train control (CTC) systems, network management systems, remote diagnostic systems, event recording and performance monitoring system.

Onboard Equipment - Equipment on board locomotives that communicate with

wayside equipment. Onboard equipment includes, but is not limited to displays, alarm devices, and ATCS/PTS computers.

Wayside Equipment - Equipment typically found at railroad field sites. Wayside

equipment includes, but is not limited to defect detectors, AEI equipment, weigh-bridges, signaling control equipment (vital and non vital), road crossing equipment, platform indicators, and other station equipment.


1.4 CONTENTS Documents applicable to this specification are identified in Section 2. Section 3 provides descriptions of the WEI protocols. The appendices to this specification contain the following information: Appendix A - Wayside Equipment System Messages Appendix B - Hot Box Detector Appendix C - AEI Reader Appendix D - Wheel Impact Load Detector (WILD) Appendix E - Grade Crossing Device Appendix F - Weigh Scale Appendix G - Clearance (high/wide) Detector Appendix H - Dragging Equipment Detector Appendix I - Wheel Profile Measurement Device Appendix J - Acoustic Bearing Detector Appendix K - Event Recorder


2.0 APPLICABLE DOCUMENTS The following documents of the issue indicated form a part of this specification to the extent that they are referenced herein. In the event of conflict between the documents referenced and the requirements of this specification, the contents of this specification shall take precedence.

• ATCS Specification 200, Communications System Architecture, Version 4.0. • ATCS Specification 250, ATCS Message Specification, Version 4.0. • ATCS Specification 500, Field System Architecture, Version 4.0 • ATCS Specification 530, Wayside Interface Unit, Version 4.0 • ANSI/TIA/EIA-422-B-1994, Electrical Characteristics of Balanced Voltage

Digital Interface Circuits, May, 1994 • ANSI/TIA/EIA-232-E-91, Interface Between Data Terminal Equipment and

Data Circuit Terminating Equipment Employing Serial Binary Data Interchange, July, 1991

• ANSI/TIA/EIA-530-A-92, High Speed 25-Position Interface for Data Terminal Equipment and Data Circuit-Terminating Equipment, Including Alternative 26-Position Connector, June, 1992

• ANSI/TIA/EIA-574-90, 9 Position Non-Synchronous Interface Between Data Terminal Equipment and Data Circuit-Terminating Equipment Employing Serial Binary Data Interchange, September, 1990


3.0 REQUIREMENTS The wayside equipment shall be interfaced using the 7-layer OSI model as described in ATCS Specification 200. The following subsections provide an overview of the wayside equipment 7-layer OSI interface.

Commentary: Alternative Layer 1 and 2 options will be described for maximum flexibility. Suppliers and customers can select an appropriate Layer 1 and 2 interface as appropriate, on a site by site basis.

Time-sync capability shall be optional. The specification provides two methods of exchanging time-sync using either dedicated hardware lines, or single character communications. Equipment that requires time-sync can use one or both methods depending on the capability of other equipment at the site. 3.1 Layer 1 A typical characteristic of railroad equipment is that it is deployed in groups - i.e., a specific site will contain multiple systems which very often have to exchange data with each other as well as the central office. The Layer 1 architecture therefore has to be capable of providing a means of connecting devices to allow these devices to communicate to each other via a Αmaster≅ device in a star configuration or in a multipoint-to-multipoint configuration. For communications with other field sites or with central office or onboard equipment, the wayside network requires an interface, or gateway, to other wayside networks or the railroad’s wide area ATCS network. The design of this interface may vary between field networks, consisting of communication devices such as ATCS MCPs, spread spectrum radios, or modems that dial into office network nodes. In addition, this interface may include routing or group manager software for the wayside network. Regardless of the specific design of this interface, the specification will refer to these devices generically as an ATCS gateway. 3.1.1 Synchronous RS-422 Synchronous RS-422 shall be the standard ATCS interface for wayside equipment.. Figure 3-1 illustrates a typical wayside architecture using this interface. Please refer to Appendix O of the ATCS Specification 200 for details.


D1 D2 D3

Wayside Devices

RS422 - SyncRS422 - Sync

ATCS Gateway(MCP)

Figure 3-1. Typical ATCS Wayside Architecture

Commentary: Not suitable for multidropped connections in a multipoint to multipoint architecture. However, the ATCS specifications does allow inter-device communications via the standard MCP routing functions in a star configuration.

3.1.2 Multiplexed Asynchronous RS-232

An inexpensive multiplexer can in many instances provide a satisfactory solution for interconnecting wayside devices in a multipoint-to-multipoint configuration. Figure 3-2 illustrates a typical wayside architecture using a multiplexer.


Wayside Devices

ATCSGateway

D2D1 D3

ATCSNetwork

RS-232-Async RS-232-Async

Multiplexer

Figure 3-2. Multiplexer Wayside Architecture Each device shall provide a five-wire RS-232 data port, optionally extended to 7-wire if hardware time sync is implemented.

An external MUX hardware unit is required if there is more than two units on site to allow multipoint to multipoint communications. A unit that wishes to send must raise RTS, and obtain CTS before proceeding. If no mux is installed, then RTS can be looped back to CTS.

Data shall be exchanged asynchronously half duplex, using 8 bits per character and no parity. Baudrate is site selectable to the fastest common denominator supported. The multiplexer shall have the capability to optionally filter or not filter the data such that a sending device receives a copy of its own transmission.

If implemented, a marking condition on the time-sync lines shall be the quiescent (normal) condition. A space condition shall signal the Αget ready to receive time-mark≅ condition. The space-to-mark transition shall be the time-mark (T-Zero).

The wayside equipment shall be considered as DTE. Both 25-pin and 9-pin male D connectors can be provided, with the following recommended pinouts:


Signal

Function 25-pin

9-pin

TXD Transmit Data From Equipment 2 3 RXD Receive Data To Equipment 3 2 GND Signal Ground 7 5 RTS Request to Send 4 7 CTS Clear to Send 5 8 SCO Time Sync Output 15 SCI Time Sync Input 17

Table 1. Recommended Pinouts

For 25-pin connectors, two special signals (SCO and SCI) have been defined for systems that support hardware sync. In any particular site, one system shall be defined as the timesync master, and the others as slaves. Wiring shall be such that the SCO output of the master is connected to the SCI input of all slaves.

Consistent with RS-232 conventions, the SCO signal levels are defined in terms of MARKING (negative voltage) and SPACING (positive voltage). There are two alternate functions possible:

1. When idle, the SCO output shall be marking. At the time sync mark, the output shall change to spacing, and remain so for as long as activity (train presence) is detected on site. All slave equipment shall use the MARK-to-SPACE transition to reset their internal event timers.

2. The MARK-to-SPACE transition is a wakeup to warn that the SPACE-to-MARK is the time zero sync. The latter configuration assumes a minimum latency of the slave unit to be specified.

3.1.3 Echelon

Echelon Lontalk, twisted pair operating at 1.25Mbits/s, shall be considered for multidrop configurations. Connectors shall be manufacturer-specific. Figure 3-3 illustrates a typical wayside architecture using Echelon.


ATCSGateway

D1 D2 D3

Wayside Devices

Echelon twistedpair

ATCSNetwork

Figure 3-3. Echelon Wayside Architecture 3.2 Layer 2

Layer 2 functionality deals with using the Layer 1 architecture to send packets of data from one device (node) on the network, to another device (node).

3.2.1 Synchronous HDLC - LAPB

Synchronous HDLC - LAPB shall be the standard ATCS requirement. Please refer to ATCS 200 Specification for details. This protocol is only suitable for point-to-point connections.

3.2.2 Synchronous HDLC - LAPD

The alternative ATCS requirement, polled mode, requires one system to be the master, and is only suitable for a star configuration. However, it can be workable if the standard ATCS MCP is configured for LAPD operation on its client ports, and the slave devices are able to tristate their transmit ports while inactive.

3.2.3 Asynchronous Framing

For wayside equipment that does not support Echelon, the recommended Layer 2 protocol is asynchronous framing. Note that it allows existing maintenance and diagnostic commands to operate concurrently, i.e., it is not necessary to use a dedicated port for this protocol.


1. Data shall be sent as binary packets.

2. Each packet shall be framed with a unique start (STX) and end (ETX) character to delimit the packet.

3. A 16-bit CRC16 field (low order byte first) shall be attached to the end of each packet prior to the end-of-text character.

4. Each packet shall have a Layer 2 address as the second byte of each packet set to the Layer 2 destination address of that packet. The value 99 shall be defined as broadcast addresses.

5. No Layer 2 acknowledgments shall be defined.

6. No Layer 2 software flow control shall be defined

7. Data outside the STX/ETX packet framing shall be considered as terminal I/O - i.e., the wayside equipment shall interpret received data as maintenance / diagnostic commands, and shall output appropriate display updates without STX/ETX framing.

A data-escape mechanism shall exist to allow binary data corresponding to data link control characters to be replaced with a two byte sequence. Characters in the range $f0 through $ff shall be escaped by sending a two-byte sequence $f0, $0n instead, where n is the lower nibble of the character being escaped. E.g., $f7 is sent as $f0, $07. This allows characters $f0 through $ff to be used as unique link control characters. The data-escape mechanism shall be applied to all characters which lie between the STX and ETX, i.e., address + packet+CRC. The assignments are defined in Table 2.

Character

Mnemonic Function

$f0 DLE Data Escape $f3 TWARN Time Sync Warning $f4 TSYNC Time Sync (T-ZERO) $f5 STX Start of packet header $f6 ETX End of packet

Table 2. Layer 2 Data Link Control Characters


At any point, a TSYNC character may be sent in the data stream to indicate a ΑTime Zero≅ (T-ZERO) condition. This method should be used by devices which require synchronization with other devices, but cannot implement the hardware time sync method described in Layer 1. In addition, a TWARN message may precede the TSYNC character, indicating that the system should remain quiescent to prepare for a TSYNC event. The minimum time lag between TWARN and TSYNC shall be determined on a per-implementation basis.

Packet reception shall commence on the receipt of a STX character. Characters shall be accumulated until the ETX character is received. Escaped characters shall be normalized to their original values. Received packets for which the Layer 2 address does not match that of the recipient or the broadcast address shall be ignored.

At the end of reception, the CRC field shall be calculated and compared. Upon receiving an invalid CRC, a receiver shall discard the packet.

Data integrity checking may be bypassed by assigning a value of $DE $AD to the CRC value. A value of $DEAD shall always be considered a valid checksum by a receiving entity. This feature is provided for purposes of supporting older equipment, and shall not be used in future designs.

Some Layer 2 addresses have special meanings, and shall not be reassigned by other equipment:

Node Function 1 Central Office and Intergroup Communications 2 Backup communications 3 Time Sync Master / Site Master 99 Broadcast Address

Table 3. Reserved Layer 2 addresses

3.2.4 Echelon

Packets shall be sent as Echelon Foreign Frames (Type $41), using node addressing following the Layer 2 addresses defined above. The format is fixed by Echelon. Refer to Echelon Specifications.

Domain addressing is not used.

Subnet addressing is always set to 1.


3.3 Layers 3 Through 6

These layers are implemented independent of which Layer 1 or 2 are being used. They shall follow the AAR ATCS specification 200 format. The packet format is reproduced here for informational purposes only. Refer to the ATCS specifications as the final authority.

The packet is constructed of a Layer 3 header (L3_HEAD), facility field, and Layer 4 through 7 header (L47_HEAD). Note that the actual size of L3_HEAD addresses is dynamic due to the variance in address lengths.

The L3_HEAD structure is defined in table 4, followed by the L3_HEAD field definitions in table 4-1.

BIT FIELD DEFINITIONS

7 6 5 4 3 2 1 0

Q D PACKET_TYPE PRIORITY RF_ACK_DISABLE

CHANNEL

TX_SEQ_NUM FIL1

RX_SEQ_NUM FIL2

SRCE_LEN DEST_LEN

ADDRESSES [n]

where, 0 < n < 10

FIL3 FACILITY_LENGTH

Table 4. L3_HEAD Structure


Field Name Description

Q Qualifier - normally set to 0

D Delivery Confirmation - set to 1 if Conf. packet required

PACKET_TYPE 0 = Nack; 2 = Info; 3 = Ack

PRIORITY 0 = highest

RF_ACK_DISABLE Set if RF ack disabled

CHANNEL Always 0

TX_SEQ_NUM TX packet sequence number

FIL1 Always 0

RX_SEQ_NUM RX packet sequence number

FIL2 Always 0

SRCE_LEN Source address length

DEST_LEN Destination address length

ADDRESSES[] Destination and source address digits, BCD encoded, packed

FIL3 Always 0

FACILITY_LENGTH Facility field length (normally 0)

Table 4-1. L3_HEAD Field Definitions


The L47_HEAD structure is defined in table 5, followed by the L47_Head field definitions in table 5-1.

BIT FIELD DEFINITIONS

7 6 5 4 3 2 1 0

NUMBER MORE

PART END_TO_END

LENGTH VITAL

LABEL [2]

VERSION

DATA

Table 5. L47_HEAD Structure


NUMBER Message number

MORE Set if more parts to this message

PART Part number of message

END_TO_END Set if end-to-end ACK required

LENGTH Number of parts in message

VITAL Set if message vital



LABEL[2] Message data type (High-order Byte First)

VERSION Data structure version (ATCS Spec version)

DATA Application data

Table 5-1. L47_HEAD Field Definitions

Together, the L3_HEAD structure, followed by the L47_HEAD structure, comprise the data packet format.

3.3.1 Acknowledge and Retry

Layer 3 acknowledge and retry is implemented to allow high-integrity data transfer. The Layer 3 header fields are used for this mechanism. The following rules apply:

1. Each device shall maintain, for each of the other devices that it communicates with, a set of send and receive sequence numbers (NS and NR) in the range 0 thru 127. A wayside device shall be identified by a unique 12 digit Layer 3 (network) address prefix.

2. Transmitted packets shall be assigned NS numbers PER DESTINATION, and shall be filled in with the expected NR number FROM that destination.

3. The RF_ACK_DISABLE bit in the transmitted packet is normally left clear, requiring the receiver to acknowledge the packet. However, it is legal to have this bit set, indicating that NO acknowledgment is required.

4. A transmitted packet shall be considered to be acknowledged if a subsequent received packet from the transmit destination carries a NR number one higher than the NS number assigned to the transmitted packet. In other words, a receiver acknowledges a packet by incrementing the NR number that it maintains for that particular source address, and returning a packet to the sender.

5. A receiver shall reject any packet for which the NS number does not match the expected value - i.e., the NR number maintained for that particular source. However, it shall always update its


transmit sequence number for that source with the NR value received, and shall still generate a reply packet. In this way, the remote transmitter shall then update its NS number, and retry the packet with the correct NS number.

6. A receiver shall acknowledge a data packet either by sending a return data packet, or, if no data packet is ready to be sent, by sending a special acknowledge packet. (See ATCS Specification 200.).

7. A transmitter may allow a maximum of one outstanding unacknowledged packet per device it is in communications with.

3.3.2 Addressing

14-digit physical hierarchical wayside addressing shall be used. Each wayside device shall be assigned an address of the format T.RRR.LLL.GGG.SS.DD where

T = Address type (Currently 7, in future shall be 5)

RRR = Railroad number assigned by AAR (0 through 999)

LLL = Region / District . (Railroad specific) (0 through 999)

GGG = Control Group within this region (0 through 999)

SS = Equipment within control group (0 through 99)

DD = Internal software entity within equipment (0 through 99).

Packets that are sent intra-group ( i.e., do not leave the site) can optionally shorten the address fields to 5 digits, eliminating the RRR, LLL, and GGG fields, i.e., T.RRR.LLL.GGG.SS.DD becomes T.SS.DD. Note that this reduces packet overhead by 9 bytes.

Note that the SS field is mapped to the Layer 2 node address, i.e., the Layer 2 address for each wayside device is the same as its SS number.

Note also that the above addressing scheme is PHYSICALLY HIERARCHICAL, and differs from the current ATCS specified 15-digit LOGICALLY HIERARCHICAL wayside addressing. This variation allows algorithmic packet routing by the wayside equipment without the need for special configuration tables. However, the actual addressing scheme to be used is a customer/supplier issue, and should be determined on a per installation basis.


3.3.3 Routing

Packets shall be routed based on the Layer 3 destination address defined in the ATCS packet specification. Depending on the choice of a Layer 1/2 implementation, communications may be point-to-point, point-to-multipoint, or multipoint-to-multipoint.

In the multipoint cases, the Layer 3 routing has to determine a Layer 2 address for each data packet. The following algorithm shall apply:

If the packet is intragroup, i.e., the source and destination shares the same first 10 digits of their address, or are not defined, then the Layer 2 address is the SS field of the destination address. In all other cases the Layer 2 address is defaulted to 1. i.e., the inter-group communications device.

3.3.4 Packet length

Maximum packet length including overhead is determined by the Layer 1 and 2 constraints. It is recommended that packets be limited to standard-length ATCS datagrams to maintain compatibility with Echelon architecture, as Echelon limits packet size to 224 bytes. The ATCS Specification 200 provides a mechanism for splitting large data fields into smaller packets, which is handled at Layer 4.

3.4 Layer 7

Layer 7 comprises a 16-bit label, 8 bit version/specification number, and application data. The version number refers to the ATCS specification version to which the application data corresponds. The labels and data fields are defined below, and shall be incorporated in future versions of the ATCS specification. Word values are 16 bits with the Low-Order byte first (LO-HI). Layer 7 data may be split into two broad categories, one category containing wayside system messages, the other category consisting of device specific data.

ATCS messages are numbered with a 3 part identifier indicating function (P1), type (P2), and exact message (P3) and is written as P1.P2.P3 for convenience. The binary label can be calculated from the formula (512*P1) + (64*P2) + P3 = LABEL, where LABEL is a 16 bit unsigned integer.

Commentary: The Layer 7 message formats in the appendices were compiled from contributions from many sources in the industry, representing the best available data at the time. However, it should be expected that the actual implementations will differ from what is documented here. Therefore, suppliers and railroads are encouraged to publish their Layer 7 message formats through the AAR for incorporation into ATCS Specification 250 on an ongoing basis.

Wayside Equipment Interface Specification Final Draft, December, 1996 page A-1

APPENDIX A

WAYSIDE EQUIPMENT SYSTEM MESSAGES Description:

The messages contained in this appendix describe the interaction between wayside equipment and other wayside, central, and onboard equipment at the wayside system level.

Applicable Peripheral Devices:

Hot Box Detector AEI Reader Wheel Impact Load Detector (WILD) Grade Crossing Device Weigh Scale Clearance (high/wide) Detector Dragging Equipment Detector Wheel Profile Measurement Device Acoustic Bearing Detector Event Recorder

Note: This appendix contains messages defined in ATCS Specification 250 and are listed in this specification for convenience. If any discrepancies exist in these messages between this specification and ATCS Specification 250, ATCS Specification 250 shall govern.


Name: Ping Request Revision Date: 9/28/96 Message Number: 4.1.7 (Proposed) Source: Multiple Devices Label: 2119 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 8-88 Octets Purpose: The Ping Request message is used to determine if a specific application is up and running on an ATCS device. Any ATCS device can initiate the Ping Request message and transmit the message to any other ATCS device in the network to request the operational status of a particular application. The recipient of the Ping Request message transmits the message, in its entirety, back to the originator, after verifying the requested application is operational. If the requested application is not operational, the recipient will not respond to the message originator.

Frame Details

Description Type Bits

MSB....LSB

LSB Value

Range Notes

REVISION_LEVEL BYTE 00000101 1 5 ONLY A.

RQST_APPL_SEQ_NUMBER WORD XXXXXXXX XXXXXXXX

1 1-32767

B.

RQST_APPL_PING_START_TIME BYTE[5] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE SEE NOTE

C.

RQST_APPL_DATA BYTE[0-80]

XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE SEE NOTE

D.

Notes A. REVISION_LEVEL reflects the ATCS specification revision level. See ATCS

Specification 250 object SPEC_REVISION. B. The RQST_APPL_SEQ_NUMBER uniquely identifies the specific application

whose operational status is being requested in the ping request message. The RQST_APPL_SEQ_NUMBER record is a 2-octet manufacturer-assigned field defined below. See ATCS Specification 250 object GENERIC_COUNTER.

Octet Description

1 low-order byte

2 high-order byte


C. The RQST_APPL_PING_START_TIME record consists of 5 octets defined below.

See ATCS Specification 250 object TIME_DATE.

Octet Description Range

1 second 0-59

2 minute 0-59

3 hour 0-24

4 day 1-31

5 month 1-12

D. The RQST_APPL_DATA is an optional manufacturer-defined field whose field

size is manufacturer-specified from a range of 1 to 80 bytes.


Name: Ping Response Revision Date: 9/28/96 Message Number: 4.2.18 (Proposed) Source: Multiple Devices Label: 2194 Destination: Multiple Devices Transmission Rate: Upon Response to Ping Max Message Length: 1 Packet Request Size Parameter: 8-88 Octets Purpose: The Ping Response message is the positive reply to a Ping Request message to determine if a specific application is up and running on an ATCS device. The recipient of the Ping Request message transmits the Ping Request message, in its entirety, back to the originator, after verifying the requested application is operational. If the requested application is not operational, the recipient will not respond to the message originator.

Frame Details


MSB....LSB

LSB Value

Range Notes


PING_RQST_SEQ_NUMBER WORD XXXXXXXX XXXXXXXX

1 1-32767

B.

PING_RQST_PING_START_TIME BYTE[5] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE SEE NOTE

C.

PING_RQST_DATA BYTE[0-80]


SEE NOTE SEE NOTE

D.


Specification 250 object SPEC_REVISION. B. The PING_RQST_SEQ_NUMBER uniquely identifies the specific application

whose operational status is being requested in the Ping Request message. The PING_RQST_SEQ_NUMBER record is a 2-octet manufacturer-assigned field defined below. See ATCS Specification 250 object GENERIC_COUNTER.

Octet Description

1 low-order byte

2 high-order byte


C. The PING_RQST_PING_START_TIME record consists of 5 octets defined below. See ATCS Specification 250 object TIME_DATE.


1 second 0-59

2 minute 0-59

3 hour 0-24

4 day 1-31

5 month 1-12

D. The PING_RQST_DATA is an optional manufacturer-defined field whose field

size is manufacturer-specified from a range of 1 to 80 bytes.


Name: Loopback Message Revision Date: 9/28/96 Message Number: 4.4.1 Source: Multiple Devices Label: 2305 Destination: Multiple Devices Transmission Rate: As Needed Max Message Length: 1 Packet Size Parameter: 87 Octets Note: This message is defined in ATCS Specification 250. Purpose: This message is used to test the communication link between ATCS devices (typically for verifying installation and troubleshooting communication problems). Any ATCS device can initiate the loopback message and transmit the message to any other ATCS device in the network. The loopback message differs from the ATCS health messages to the extent that the loopback message provides a method for testing the communication links, independently of the end applications and the end device's health status. The recipient of the loopback message transmits the message, in its entirety, back to the originator and adds the received signal strength (if available) to the message. Any ATCS device that receives this message destined for its "Loopback receiver" should echo the entire message, as received, back to the "Loopback initiator's" address, adding only the receive signal strength if it is available. End-to-end message roundtrip throughput can be measured by the loopback message initiator by comparing the TIMESTAMP_OUT data against the originator's current time when processing the returned loopback message.

Frame Details


MSB....LSB

LSB Value Range Notes


TIMESTAMP_OUT BYTE[5] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE SEE NOTE B.

LOOPBACK_DATA BYTE[80]


SEE NOTE SEE NOTE C.

RCV_SIGNAL_STRENGTH BYTE XXXXXXXX 1 SEE NOTE D.


Specification 250 object SPEC_REVISION. B. The TIMESTAMP_OUT record consists of 5 octets defined below. See ATCS

Specification 250 object TIME_DATE.



1 second 0-59

2 minute 0-59

3 hour 0-24

4 day 1-31

5 month 1-12

C. LOOPBACK_DATA is a manufacturer-defined 80 character ASCII string. See

ATCS Specification 250 object STATUS_DESCRIPTION. D. RCV_SIGNAL_STRENGTH, if available, is added to the loopback message by

the receiving ATCS device when responding to the originator. See ATCS Specification 250 object SIGNAL_STRENGTH. The range of values is:

Value Description

0 Not used

1 -120 dB or lower

2 -119 dB

increasing values (up to 61) in 1 dB increments

61 -60 dB or higher

255 packet received via hardwired connection


Name: Time Request Revision Date: 3/31/93 Message Number: 107.1.2 Source: Multiple Devices Label: 54850 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 9 Octets Note: This message is defined in ATCS Specification 250. Purpose: The Time Request message (also named REQ_TIME_MSG in ATCS Specification 250) is used to query a device for time of day information.

Frame Details


MSB....LSB

LSB Value

Range Notes


NETWORK_ADDRESS BYTE[8] BBBBAAAA DDDDCCCC FFFFEEEE HHHHGGGG JJJJIIII LLLLKKKK NNNNMMMM PPPPOOOO

SEE NOTE

SEE NOTE

B.


Specification 250 object SPEC_REVISION. B. The fields AAAA thru NNNN plus PPPP comprise the 15 BCD digit ATCS

address. Field OOOO contains the number of ATCS address digits. A zero digit is encoded as $A. An unused digit in the 15 digit ATCS address field is encoded as $0. The following table describes the NETWORK_ADDRESS field. See ATCS Specification 250 object NETWORK_ADDRESS.


Field Description

AAAA 2nd BCD digit of ATCS address

BBBB 1st BCD digit of ATCS address

CCCC 4th BCD digit of ATCS address

DDDD 3rd BCD digit of ATCS address

EEEE 6th BCD digit of ATCS address

FFFF 5th BCD digit of ATCS address

GGGG 8th BCD digit of ATCS address

HHHH 7th BCD digit of ATCS address

IIII 10th BCD digit of ATCS address

JJJJ 9th BCD digit of ATCS address

KKKK 12th BCD digit of ATCS address

LLLL 11th BCD digit of ATCS address

MMMM 14th BCD digit of ATCS address

NNNN 13th BCD digit of ATCS address

OOOO number of BCD digits in ATCS address

PPPP 15th BCD digit of ATCS address


Name: Time Response Revision Date: 3/31/93 Message Number: 107.4.2 Source: Multiple Devices Label: 55042 Destination: Multiple Devices Transmission Rate: Upon Response to Time Max Message Length: 1 Packet Request Size Parameter: 8 Octets Note: This message is defined in ATCS Specification 250. Purpose: The Time Response message (also named TIME_MSG in ATCS Specification 250) provides the current time of day and year information in response to the Time Request (107.1.2) message, or on a periodic broadcast basis (every 20 minutes).

Frame Details


MSB....LSB

LSB Value

Range Notes


TIME_MSG BYTE[5] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.

YEAR WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.


Specification 250 object SPEC_REVISION. B. The TIME_MSG record consists of 5 octets defined below. See ATCS



1 second 0-59

2 minute 0-59

3 hour 0-24

4 day 1-31

5 month 1-12

C.. Year contains the 4 digit year in a 2 octet record. See ATCS

Specification 250 object GENERIC_COUNTER.


Name: Health Message Request Revision Date: 3/31/93 Message Number: 4.1.2 Source: Multiple Devices Label: 2114 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 9 Octets Note: This message is defined in ATCS Specification 250. Purpose: The Health Request message (also named QUERY_FOR_HEALTH_REPORT_MSG in ATCS Specification 250) is used to request a nondisruptive evaluation of static and general health information from a device.

Frame Details


MSB....LSB

LSB Value

Range Notes


NETWORK_ADDRESS BYTE[8] BBBBAAAA DDDDCCCC FFFFEEEE HHHHGGGG JJJJIIII LLLLKKKK NNNNMMMM PPPPOOOO

SEE NOTE

SEE NOTE

B.


Specification 250 object SPEC_REVISION. B. The fields AAAA thru NNNN plus PPPP comprise the 15 BCD digit ATCS

address. Field OOOO contains the number of ATCS address digits. A zero digit is encoded as $A. An unused digit in the 15 digit ATCS address field is encoded as $0. The following table describes the NETWORK_ADDRESS field. See ATCS Specification 250 object NETWORK_ADDRESS.


Field Description

AAAA 2nd BCD digit of ATCS address

BBBB 1st BCD digit of ATCS address

CCCC 4th BCD digit of ATCS address

DDDD 3rd BCD digit of ATCS address

EEEE 6th BCD digit of ATCS address

FFFF 5th BCD digit of ATCS address

GGGG 8th BCD digit of ATCS address

HHHH 7th BCD digit of ATCS address

IIII 10th BCD digit of ATCS address

JJJJ 9th BCD digit of ATCS address

KKKK 12th BCD digit of ATCS address

LLLL 11th BCD digit of ATCS address

MMMM 14th BCD digit of ATCS address

NNNN 13th BCD digit of ATCS address

OOOO number of BCD digits in ATCS address

PPPP 15th BCD digit of ATCS address


Name: Health Message Response Revision Date: 3/31/93 Message Number: 4.2.2 Source: Multiple Devices Label: 2178 Destination: Multiple Devices Transmission Rate: Upon Response to Health Max Message Length: 1 Packet Message Request or device start-up. Size Parameter: 123 Octets Note: This message is defined in ATCS Specification 250. Purpose: The Health Message Response message (also named HEALTH_REPORT_MSG in ATCS Specification 250) is used to provide a nondisruptive evaluation of static and general health information from a device in response to a Health Message Request (4.1.2) or device start-up.

Frame Details


MSB....LSB

LSB Value

Range Notes


ATCS_EQUIPMENT_CODE BYTE XXXXXXXX SEE NOTE

SEE NOTE

B.

ATCS_STATUS_CODE WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.

ATCS_DEVICE_HARDWARE_ REVISION_LEVEL

WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

D.

ATCS_DEVICE_SOFTWARE_ REVISION_LEVEL


SEE NOTE

SEE NOTE

E.

TEST_TIME BYTE[5] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

F.

ATCS_MANUFACTURER_CODE WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

G.

ATCS_RAILROAD_NUMBER BYTE[2] BBBBAAAA DDDDCCCC

SEE NOTE

SEE NOTE

H.

MANUFACTURER_EQUIPMENT_CODE

BYTE XXXXXXXX SEE NOTE

SEE NOTE

I.

MANUFACTURER_HARDWARE_ REVISION

BYTE[8] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

J.


Frame Details


MSB....LSB

LSB Value

Range Notes

MANUFACTURER_SOFTWARE_ REVISION

BYTE[8] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

K.

DEVICE_IDENTIFIER BYTE[15] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

L.

MAINTENANCE_REF_PT_TYPE BYTE XXXXXXXX SEE NOTE

SEE NOTE

M.

MAINTENANCE_REF_PT_ VALUE

BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

N.

MANUFACTURER_STATUS_ CODE


SEE NOTE

SEE NOTE

O.

MANUFACTURER_STATUS_ DESCRIPTION

BYTE[67] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

P.


Specification 250 object SPEC_REVISION. B. See ATCS Specification 250 object EQUIPMENT_CODE for list of equipment codes. C. See ATCS Specification 250 object STATUS_CODE for list of status codes. D. Version and amendment numbers of ATCS device hardware calculated as: revision = (64*Version Number + Amendment Number) See ATCS Specification 250 object SPEC_REVISION_LEVEL. E. Version and amendment numbers of ATCS device software calculated as: revision = (64*Version Number + Amendment Number) See ATCS Specification 250 object SPEC_REVISION_LEVEL. F. The TEST_TIME record consists of 5 octets defined below. See ATCS




1 second 0-59

2 minute 0-59

3 hour 0-24

4 day 1-31

5 month 1-12

G. ATCS_MANUFACTURER_CODE assignment provided by the AAR. See ATCS

Specification 250 object MANUFACTURER_NUMBER. H. ATCS_RAILROAD_NUMBER contains the BCD 3-digit AAR-designated railroad ID

with the following format. See ATCS Specification 250 object ROAD_NUMBER.

Field Description

AAAA 1st BCD digit of railroad ID

BBBB Null value ($0)

CCCC 3rd BCD digit of railroad ID

DDDD 2nd BCD digit of railroad ID

I. See ATCS Specification 250 object EQUIPMENT_CODE for list of equipment

codes. J. MANUFACTURER_HARDWARE_REVISION defined by the manufacturer. See ATCS

Specification 250 object REVISION_LEVEL. K. MANUFACTURER_SOFTWARE_REVISION defined by the manufacturer. See ATCS

Specification 250 object REVISION_LEVEL. L. DEVICE_IDENTIFIER is a 15-character ASCII string used by the manufacturer

to further identify the device. See ATCS Specification 250 object DEVICE_IDENTIFIER.

M. MAINTENANCE_REF_PT_TYPE identifies the type of maintenance reference

point being used for the data field, MAINTENANCE_REF_PT_VALUE. See ATCS Specification 250 object REFERENCE_POINT_TYPE. The following table describes the maintenance reference point types supported.

Value Maintenance Reference Point Type

0 None

1 Minutes since last reset

2 Cycles since last reset


N. MAINTENANCE_REF_PT_VALUE contains the value of the maintenance reference point indicated by the MAINTENANCE_REF_PT_TYPE data field. See ATCS Specification 250 object MAINTENANCE_REFERENCE_POINT.

O. See ATCS Specification 250 object STATUS_CODE for list of status codes. P. MANUFACTURER_STATUS_DESCRIPTION is an ASCII string defined by the

manufacturer. See ATCS Specification 250 object SHORT_STATUS_DESCRIPTION.


Name: Device Capability Request Revision Date: 9/28/96 Message Number: 9.1.9 (Proposed) Source: Multiple Devices Label: 4681 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 1 Octet Purpose: The Device Capability Request message is used by an application to determine the types of data that another device can provide.

Frame Details


MSB....LSB

LSB Value

Range Notes



Specification 250 object SPEC_REVISION.


Name: Device Capability Response Revision Date: 9/28/96 Message Number: 9.2.15 (Proposed) Source: Multiple Devices Label: 4751 Destination: Multiple Devices Transmission Rate: Upon Response to Device Max Message Length: 1 Packet Capability Request Size Parameter: 1+2n Octets Purpose: The Device Capability Response message lists the types of data that an ATCS device can provide to other ATCS devices in response to a Device Capability Request message.

Frame Details


MSB....LSB

LSB Value

Range Notes


DATA_TYPES WORD[n] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.


Specification 250 object SPEC_REVISION. B. The DATA_TYPES record contains the labels of the data types the

application can provide to other ATCS devices.


Name: Manufacturer Specific Data Revision Date: 9/28/96 Message Number: 2.4.1 (Proposed) Source: Multiple Devices Label: 1281 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 3+n Octets Purpose: The Manufacturer Specific Data message is used for transmitting private or manufacturer specific messages.

Frame Details


MSB....LSB

LSB Value

Range Notes


ATCS_MANUFACTURER_CODE WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.

SPECIFIC_DATA BYTE[n] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.


Specification 250 object SPEC_REVISION. B. ATCS_MANUFACTURER_CODE assignment provided by the AAR. See ATCS

Specification 250 object MANUFACTURER_NUMBER. C. The SPECIFIC_DATA record contains the manufacturer defined data.


Name: Subscription Request Revision Date: 9/28/96 Message Number: 9.1.10 (Proposed) Source: Multiple Devices Label: 4682 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 7+2n Octets Purpose: The Subscription Request message is used to subscribe to a series of data types from another ATCS device. The data types are obtained by the requester by issuing an earlier "Device Capability Request" message to the recipient of the request message.

Frame Details


MSB....LSB

LSB Value

Range Notes


RESERVED BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

DATA_COUNT WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.

DATA_TYPE_REQUEST WORD[n] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.


Specification 250 object SPEC_REVISION. B. DATA_COUNT contains the number of different data types being requested

for subscription. See ATCS Specification 250 object GENERIC_COUNTER. C. The DATA_TYPE_REQUEST record contains the list of data types being

requested for subscription.


Name: Subscription Response Revision Date: 9/28/96 Message Number: 9.2.16 (Proposed) Source: Multiple Devices Label: 4752 Destination: Multiple Devices Transmission Rate: Upon Response to Subscription Max Message Length: 1 Packet Request message Size Parameter: 7+2n Octets Purpose: The Subscription Response message is used to acknowledge and to status the subscription request to the ATCS device that issued the Subscription Request message.

Frame Details


MSB....LSB

LSB Value

Range Notes



DATA_COUNT WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.

DATA_TYPE_ACQ WORD[n] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.


Specification 250 object SPEC_REVISION. B. DATA_COUNT contains the number of different data types for which a

subscription is granted. See ATCS Specification 250 object GENERIC_COUNTER.

C. The DATA_TYPE_ACQ record contains the list of data types for which a

subscription is granted.


Name: Unit Status Request Revision Date: 9/28/96 Message Number: 4.1.8 (Proposed) Source: Multiple Devices Label: 2120 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 1 Octet Purpose: The Unit Status Request message is used to request the current processing state of the queried application.

Frame Details


MSB....LSB

LSB Value

Range Notes





Name: Unit Status Response Revision Date: 9/28/96 Message Number: 4.2.19 (Proposed) Source: Multiple Devices Label: 2195 Destination: Multiple Devices Transmission Rate: Upon Response to Unit Max Message Length: 1 Packet Status Request message Size Parameter: 2 Octets Purpose: The Unit Status Response message provides the current processing state of the queried application requested by the Unit Status Request message.

Frame Details


MSB....LSB

LSB Value

Range Notes


UNIT_STATUS_RESPONSE BYTE XXXXXXXX 1 SEE NOTE

B.


Specification 250 object SPEC_REVISION. B. The UNIT_STATUS_RESPONSE field has the following values.

Value Description

0 Nothing pending

1 Acquire processing complete - post pending

2 Acquire pending - post complete

3 Both acquire and post processing pending


Name: Train Directory Request Revision Date: 9/28/96 Message Number: 7.1.2 (Proposed) Source: Multiple Devices Label: 3650 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 5 Octets Purpose: The Train Directory Request message is used to request a directory of trains stored by a particular application to determine train sequencing information.

Frame Details


MSB....LSB

LSB Value

Range Notes


NUMBER_OF_ENTRIES WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

B.

ENTRY_INDEX WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

C.


Specification 250 object SPEC_REVISION. B. NUMBER_OF_ENTRIES contains the number of entries requested. The value -1

is a request for all entries. See ATCS Specification 250 object GENERIC_COUNTER.

C. ENTRY_INDEX.... The value 0 is a request for the most recent train. See

ATCS Specification 250 object GENERIC_COUNTER.


Name: Train Directory Response Revision Date: 9/28/96 Message Number: 7.4.7 (Proposed) Source: Multiple Devices Label: 3847 Destination: Multiple Devices Transmission Rate: Upon Response to Train Max Message Length: 1 Packet Directory Request message Size Parameter: ?? Octets Purpose: The Train Directory Response message provides the directory of trains stored by a particular application in response to the Train Directory Request message.

Frame Details


MSB....LSB

LSB Value

Range Notes


NUMBER_OF_ENTRIES WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

B.


ENTRY BYTE[36* NUMBER_OF_ENTRIES]


SEE NOTE

SEE NOTE

C.


Specification 250 object SPEC_REVISION. B. NUMBER_OF_ENTRIES contains the number of entries contained in the

message. See ATCS Specification 250 object GENERIC_COUNTER. C. The ENTRY record consists of the following format. The number of ENTRY

records in the message is contained in the NUMBER_OF_ENTRIES data field.

ENTRY Record Data Field

Description Range

BYTE BCD 2 digit day of arrival date

1-31

BYTE BCD 2 digit month of arrival date

1-12



Description Range

WORD BCD 4 digit year of arrival date

0-9999

BYTE BCD 2 digit seconds of arrival time

0-59

BYTE BCD 2 digit minutes of arrival time

0-59

BYTE BCD 2 digit hours of arrival time

0-24

BYTE BCD 2 digit day of departure date

1-31

BYTE BCD 2 digit month of departure date

1-12

WORD BCD 4 digit year of departure date

0-9999

BYTE BCD 2 digit seconds of

departure time

0-59

BYTE BCD 2 digit minutes of

departure time

0-59

BYTE BCD 2 digit hours of departure time

0-24

WORD Axle Count

WORD Vehicle Count

WORD Platform Count

BYTE[10] Lead engine ID

(ASCII)

BYTE[4] - car_id with trailing

spaces

BYTE[6] - car_number with leading zeros

default is zero-filled

BYTE Direction N,S,E,W (ASCII)

BYTE Maximum Speed LSB = 1 mph

-1 = unknown 0-254 mph

BYTE Minimum Speed LSB = 1 mph




Description Range

BYTE Average Speed LSB = 1 mph


WORD Length in feet 0 = unknown


Name: User Defined Static Event Revision Date: 9/28/96 Message Number: 2.4.2 (Proposed) Source: Multiple Devices Label: 1282 Destination: Multiple Devices Transmission Rate: Upon event occurrence Max Message Length: 1 Packet Size Parameter: 82 Octets Purpose: The User Defined Static Event message is used to report a user-defined non-train related event occurring at a site.

Frame Details


MSB....LSB

LSB Value

Range Notes


STATUS BYTE XXXXXXXX SEE NOTE

SEE NOTE

B.

ASCII_MSG BYTE[80] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.


Specification 250 object SPEC_REVISION. B. C. See ATCS Specification 250 object STATUS_DESCRIPTION.


Name: User Defined Dynamic Event Revision Date: 9/28/96 Message Number: 2.4.3 (Proposed) Source: Multiple Devices Label: 1283 Destination: Multiple Devices Transmission Rate: Upon event occurrence Max Message Length: 1 Packet Size Parameter: 84 Octets Purpose: The User Defined Dynamic Event message is used to report a user-defined train related event occurring at a site.

Frame Details


MSB....LSB

LSB Value

Range Notes


TRAIN_SEQUENCE_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.

STATUS BYTE XXXXXXXX SEE NOTE

SEE NOTE

C.

ASCII_MSG BYTE[80] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

D.


Specification 250 object SPEC_REVISION. B. C. D. See ATCS Specification 250 object STATUS_DESCRIPTION.


Name: Terminal Emulation Revision Date: 9/28/96 Message Number: 15.4.8 (Proposed) Source: Multiple Devices Label: 7944 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: ?? Octets Purpose: The Terminal Emulation message is used to transport interactive raw ASCII data between applications. Commentary: This mode of operation is necessary to support older generations of equipment which rely on ASCII communications for exchanging data. Additional processing may be necessary to support this message, e.g., a MCP.

Frame Details


MSB....LSB

LSB Value

Range Notes


TBD B.

TBD


Specification 250 object SPEC_REVISION. B. This message can consist of a single byte which, when received by the

processor, will override the normal operations and force a pass through mode between the wayside device and its remote entity. The value of this byte can be toggled, forcing the communications back to its original configuration, acting as an escape from the pass through processing.


Name: Upload Firmware Request Revision Date: 9/28/96 Message Number: 3.4.28 (Proposed) Source: Multiple Devices Label: 1820 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: ?? Octets Purpose: The Upload Firmware Request message is used to upgrade firmware on ATCS devices.

Frame Details


MSB....LSB

LSB Value

Range Notes


MAJOR_VERSION_NUMBER BYTE XXXXXXXX SEE NOTE

SEE NOTE

B.

MINOR_VERSION_NUMBER BYTE XXXXXXXX SEE NOTE

SEE NOTE

C.

NUMBER_OF_BANKS BYTE XXXXXXXX SEE NOTE

SEE NOTE

D.

BANK_SIZE WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

E.

BANK_DATA BYTE [NUMBER_OF_BANKS*BANK_ SIZE]


SEE NOTE

SEE NOTE

F.

CRC_16 WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

G.


Specification 250 object SPEC_REVISION. B. C. D. E. F. G.


Name: Upload Firmware Response Revision Date: 9/28/96 Message Number: 3.2.9 (Proposed) Source: Multiple Devices Label: 1673 Destination: Multiple Devices Transmission Rate: Upon Response to Upload Max Message Length: 1 Packet Firmware Request message Size Parameter: ?? Octets Purpose: The Upload Firmware Response message is used to provide status of the Upload Firmware Request.

Frame Details


MSB....LSB

LSB Value

Range Notes


MAJOR_VERSION_NUMBER BYTE XXXXXXXX SEE NOTE

SEE NOTE

B.

MINOR_VERSION_NUMBER BYTE XXXXXXXX SEE NOTE

SEE NOTE

C.

BANK_IN_TROUBLE BYTE XXXXXXXX SEE NOTE

SEE NOTE

D.

BANK_STATUS BYTE XXXXXXXX 1 SEE NOTE

E.


Specification 250 object SPEC_REVISION. B. C. D. E. BANK_STATUS reflects the return status of upload firmware request with the following return codes.

Value Description

0 Successful

1 Checksum Error

2 Invalid Bank Count

3 Invalid Bank Size

4 Write Aborted (non-critical)

5 Write Aborted (critical)


Name: Error/Alarm Condition Revision Date: 10/10/96 Message Number: 4.2.20 (Proposed) Source: Multiple Devices Label: 2196 Destination: Multiple Devices Transmission Rate: As Needed Max Message Length: 1 Packet Size Parameter: 6+n Octets Purpose: This message is used to communicate error/alarm conditions to the system.

Frame Details

Description Type Bits LSB Value Range Notes


EVENT_TIME BYTE[5] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE SEE NOTE B.

CONDITION_DATA BYTE[n] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE SEE NOTE C.


Specification 250 object SPEC_REVISION. B. The EVENT_TIME record consists of 5 octets defined below. See ATCS



1 second 0-59

2 minute 0-59

3 hour 0-24

4 day 1-31

5 month 1-12

C. CONDITION_DATA is manufacturer-defined and contains the error/alarm

data to report.

Wayside Interface Message Specification Final Draft, December, 1996 page B-1

APPENDIX B

HOT BOX DETECTOR MESSAGES Description:

The messages contained in this appendix describe the interaction between hot box detector and other wayside, central, and onboard equipment at the wayside system level.


Hot Box Detector Acoustic Detector AEI Reader


Name: Hot Box Detector Axle Data Revision Date: 9/28/96 Message Number: 9.4.1 (Proposed) Source: Multiple Devices Label: 4865 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 21 Octets Purpose: The Hot Box Detector Axle Data message provides all relevant data associated with each axle, including heat data from four heat channels.

Frame Details


MSB....LSB

LSB Value

Range Notes



SEE NOTE

SEE NOTE

B.

JOURNAL_HEAT_RAIL_1 WORD XXXXXXXX XXXXXXXX

.1 mm 1° F

SEE NOTE

C.


1 mm 1° F

SEE NOTE

C.

HOT_WHEEL_RAIL_1 WORD XXXXXXXX XXXXXXXX

10° F SEE NOTE

D.


10° F SEE NOTE

D.

AXLE_SPACING WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

E.

STATUS WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

F.

CAR_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

G.

CAR_AVERAGE_RAIL_1 WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

H.


SEE NOTE

SEE NOTE

I.


Specification 250 object SPEC_REVISION. B.


C. Journal heats can be displayed in millimeter or degrees F. -1 signifies a missed open wheel gate condition. The wayside detector type must be established such that the remote entity is prepared to process the correct data type.

D. Wheel heats are displayed in degrees F. E. If the most significant bit (MSB) is set to 1, the remaining 15 bits

represent the axle spacing in terms of feet; otherwise, the remaining bits represent eighths of feet.

F. The STATUS field is detector dependent. Bits can be dedicated to

represent auxiliary alarms, hot box or hot wheel alarms on this particular axle, or bearing ID for each side. An 1 represents an active condition for the alarms.

G. H. I.


Name: Hot Box Detector Defect Alarm Revision Date: 9/28/96 Message Number: 9.4.2 (Proposed) Source: Multiple Devices Label: 4866 Destination: Multiple Devices Transmission Rate: Upon Request or Unsolicited Max Message Length: 1 Packet After Train Passage Size Parameter: 29 Octets Purpose: The Hot Box Detector Defect Alarm message provides descriptive information regarding an alarm detected during train passage. The alarm may be real-time or the result of post train processing. Alarms can be related to journals, wheels, dragging equipment, or clearance conditions. Data is available on demand or automatically transmitted after train presence.

Frame Details


MSB....LSB

LSB Value

Range Notes


SEQUENCE_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.

ALARM_TYPE BYTE XXXXXXXX SEE NOTE

SEE NOTE

C.

AXLE_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

D.

SIDE_INDICATOR BYTE XXXXXXXX 1 0=Left 1=Right

HEAT_OF_JOURNAL_1 WORD XXXXXXXX XXXXXXXX

1 mm 1° F

SEE NOTE

E.


1 mm 1° F

SEE NOTE

E.

CAR_ID BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

F.

CAR_NUMBER BYTE[6] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

G.

VEHICLE_TYPE BYTE XXXXXXXX SEE NOTE

SEE NOTE

H.


Frame Details


MSB....LSB

LSB Value

Range Notes

NUMBER_OF_VEHICLES WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

I.

NUMBER_OF_AXLES BYTE XXXXXXXX SEE NOTE

SEE NOTE

J.

AVERAGE_CAR_HEAT_RAIL_1 WORD XXXXXXXX XXXXXXXX

10° F SEE NOTE

K.


10° F SEE NOTE

K.


Specification 250 object SPEC_REVISION. B. SEQUENCE_NUMBER is the car sequence number. Zero is the first car. C. ALARM_TYPE is manufacturer-dependent defined field depicting hot box, hot

wheel, warm journal, DE, and clearance defects. D. Binary value represents the number of the axle containing the defect,

e.g., 64 (hex) - axle 100. E. Journal heats can be displayed in millimeter or degrees F. -1 signifies

a missed open wheel gate condition. The wayside detector type must be established such that the remote entity is prepared to process the correct data type.

F. CAR_ID is left-justified with ASCII spaces used to fill trailing unused

spaces. Default shall be binary zero. G. CAR_NUMBER is right-justified with ASCII zeros to fill unused spaces.

Default shall be binary zero. H. I. J. Number of axles on the car containing the defect. K. Wheel heats are displayed in degrees F.


Name: Hot Box Self-Test Failure Revision Date: 9/28/96 Message Number: 9.2.17 (Proposed) Source: Multiple Devices Label: 4753 Destination: Multiple Devices Transmission Rate: Upon Request, Appended to Max Message Length: 1 Packet the Post Train Report or Provided Unsolicited via Periodic Testing Size Parameter: 25 Octets Purpose: The Hot Box Self-Test Failure message provides detailed information of a system failure as soon as it is detected. A well condition (or no failure) will also be reported within this message. Failures may be fatal or simply classified as a warning.

Frame Details


MSB....LSB

LSB Value

Range Notes


MANUFACTURER_SPECIFIC BYTE[24] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.




Name: Hot Box Detector Train Report Revision Date: 9/28/96 Message Number: 9.4.3 (Proposed) Source: Multiple Devices Label: 4867 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 240 Octets Purpose: The Hot Box Detector Train Report message provides a comprehensive train report containing data related to the site configuration, system parameters, and train passage.

Frame Details


MSB....LSB

LSB Value

Range Notes


RAILROAD_MNEMONIC BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

B.

SOFTWARE_VERSION BYTE[8] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

C.

MILEPOST BYTE[9] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

D.

SITE_NAME BYTE[30] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

ASCII SEE NOTE

E.

TRACK_DESIGNATION_ COMPASS

BYTE XXXXXXXX ASCII N,S,E,W

ARRIVAL_DATE BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

F.


Frame Details


MSB....LSB

LSB Value

Range Notes

ARRIVAL_TIME BYTE[3] XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

G.

DEPARTURE_DATE BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

F.

DEPARTURE_TIME BYTE[3] XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

G.


1 SEE NOTE

H.

TRAIN_OF_DAY BYTE XXXXXXXX 1 SEE NOTE

I.

TRAIN_DIRECTION BYTE XXXXXXXX ASCII SEE NOTE

J.

ENTRY_SPEED WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

H.

EXIT_SPEED WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

H.

NUMBER_OF_AXLES WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

H.

AMBIENT_TEMP BYTE XXXXXXXX 1 SEE NOTE

K.

TRAIN_LENGTH BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

NUMBER_OF_ALARMS BYTE XXXXXXXX 1 SEE NOTE

M.

NUMBER_OF_INTEGRITY_ FAILURES

BYTE XXXXXXXX 1 SEE NOTE

N.

NUMBER_OF_WARNINGS BYTE XXXXXXXX 1 SEE NOTE

O.

NUMBER_OF_HOT_JOURNALS BYTE XXXXXXXX 1 SEE NOTE

P.

NUMBER_OF_HOT_WHEELS BYTE XXXXXXXX 1 SEE NOTE

Q.

NUMBER_OF_DRAGGING_ EQUIPMENT_ALARMS


R.


Frame Details


MSB....LSB

LSB Value

Range Notes

NUMBER_OF_HIGH-LOAD_ ALARMS


S.

NUMBER_OF_WIDE-LOAD_ ALARMS


T.

RAILSIDE_AVG_RL1_ROLLER_ BEARINGS


1 SEE NOTE

U.



1 SEE NOTE

U.

RAILSIDE_AVG_RL1_PLAIN_ BEARINGS


1 SEE NOTE

U.



1 SEE NOTE

U.

HEAT_COMPENSATION_ FACTOR_RL1_ROLLER_ BEARINGS


1 SEE NOTE

V.



1 SEE NOTE

V.

HEAT_COMPENSATION_ FACTOR_RL1_PLAIN_ BEARINGS


1 SEE NOTE

V.



1 SEE NOTE

V.

TOTAL_CARS BYTE XXXXXXXX 1 SEE NOTE

W.

TOTAL_LOCOMOTIVES BYTE XXXXXXXX 1 SEE NOTE

X.

TOTAL_UNIDENTIFIED_ AXLES


1 SEE NOTE

L.

TRANSDUCER_A_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

TRANSDUCER_B_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

TRANSDUCER_C_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

TRANSDUCER_D_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

MISSED_TRANSDUCER_A_ COUNT


1 SEE NOTE

L.


Frame Details


MSB....LSB

LSB Value

Range Notes

MISSED_TRANSDUCER_B_ COUNT


1 SEE NOTE

L.

MISSED_TRANSDUCER_C_ COUNT


1 SEE NOTE

L.

MISSED_TRANSDUCER_D_ COUNT


1 SEE NOTE

L.

INTEGRITY_HEAT_RL1 WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

U.


1 SEE NOTE

U.

SYSTEM_OPERATIONAL_ PARAMETERS

BYTE[1OO] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

Y.


Specification 250 object SPEC_REVISION. B. C. D. E. F. The DATE record consists of 4 octets defined below.


1 LSB year 0-99

2 MSB year 0-99

3 day 1-31

4 month 1-12

G. The TIME record consists of 3 octets defined below.



1 second 0-59

2 minute 0-59

3 hour 0-24

H. Least significant byte followed by the most significant byte. I. J. TRAIN_DIRECTION record depicts compass direction or normal/reverse K. L. Least significant byte followed by the 2nd least significant byte,

followed by the 2nd most significant byte, followed by the most significant byte.

M. N. O. P. Each hot box alarm counts towards the total. Q. Manufacturer-specified parameters control how many consecutive hot wheels

constitute an alarm. R. S. T. U. Least significant byte followed by the most significant byte. Value can

be millimeters or degrees F. V. Binary value expressed as a three digit decimal, e.g., 1.xyz or 0.xyz. W X. Y. Manufacturer-specific.

Wayside Interface Message Specification Final Draft, December, 1996 page C-1

APPENDIX C

AEI READER MESSAGES Description:

The messages contained in this appendix describe the interaction between the AEI reader and other wayside, central, and onboard equipment at the wayside system level.


AEI Reader


Name: AEI Tag Data Revision Date: 9/28/96 Message Number: 9.4.4 (Proposed) Source: Multiple Devices Label: 4868 Destination: Multiple Devices Transmission Rate: .......... Max Message Length: 1 Packet Size Parameter: 63 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


TIMESTAMP BYTE[6] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.


SEE NOTE

SEE NOTE

C.


ASCII SEE NOTE

D.


ASCII SEE NOTE

E.

ANTENNA_LOCATION BYTE XXXXXXXX ASCII N=Near F=Far U=Undetermined

AXLE_COUNT_AT_READING BYTE XXXXXXXX 1 SEE NOTE

F.

AXLE_COUNT_AT_TAG BYTE XXXXXXXX 1 SEE NOTE

G.

SIDE_INDICATOR BYTE XXXXXXXX BINARY 0=left 1=right

NUMBER_OF_READS BYTE XXXXXXXX 1 SEE NOTE

H.

TAG_EGC BYTE XXXXXXXX SEE NOTE

SEE NOTE

I.


Frame Details


MSB....LSB

LSB Value

Range Notes

TAG_TYPE BYTE XXXXXXXX SEE NOTE

SEE NOTE

J.

TAG_PLATFORM BYTE XXXXXXXX SEE NOTE

SEE NOTE

K.

DATA_FORMAT_CODE BYTE XXXXXXXX SEE NOTE

SEE NOTE

L.

FRAME_NUMBER BYTE XXXXXXXX SEE NOTE

SEE NOTE

M.

START_AXLE_AT_READING WORD XXXXXXXX

XXXXXXXX

SEE NOTE

SEE NOTE

N.

START_AXLE_AT_TAG WORD XXXXXXXX

XXXXXXXX

SEE NOTE

SEE NOTE

O.

ORIENTATION BYTE XXXXXXXX SEE NOTE

SEE NOTE

P.

STATUS BYTE XXXXXXXX ASCII SEE NOTE

Q.

PREDICTED_READS BYTE XXXXXXXX SEE NOTE

SEE NOTE

R.

LENGTH_AT_READING WORD XXXXXXXX

XXXXXXXX

SEE NOTE

SEE NOTE

S.

LENGTH_AT_TAG WORD XXXXXXXX

XXXXXXXX

SEE NOTE

SEE NOTE

T.

DIRECTION BYTE XXXXXXXX ASCII SEE NOTE

U.

SPEED WORD XXXXXXXX

XXXXXXXX

SEE NOTE

SEE NOTE

V.

RAW_TAG_DATA BYTE[20] XXXXXXXX

XXXXXXXX

‘‘

‘‘

XXXXXXXX

XXXXXXXX

SEE NOTE

SEE NOTE

W.




B. TIMESTAMP is a 6 octet field whose format is:

Octet Description 1 Defines the lsb: 0 = 1 Τsec; 1 = 20 Τsec 2-6 5-octet field containing the timestamp

Range is: 0 - 305.4 hrs for 1 Τsec; 0 - 6108 hrs for 20 Τsec

C. SEQUENCE_NUMBER is the car sequence number. Zero is the first car. D. CAR_ID is left-justified with ASCII spaces used to fill trailing unused

spaces. Default shall be binary zero. E. CAR_NUMBER is right-justified with ASCII zeros to fill unused spaces.

Default shall be binary zero. F. AXLE_COUNT_AT_READING is the number of axles assigned to the car as read

by the wheel detector. G. AXLE_COUNT_AT_TAG is the number of axles read from the tag. H. NUMBER_OF_READS is the number of times the reader read the tag frame. I. See AAR S-918. J. See AAR S-918. K. See AAR S-918. L. See AAR S-918. M. Zero is the first frame N. START_AXLE_AT_READING is the number of axles from the start of the train

as read by the wheel detector. Zero is the first axle. O. START_AXLE_AT_TAG is the number of axles from the start of the train as

read from the tags. Zero is the first axle. P. 0 = B end is leading; 1 = A end is leading Q. 0 = Good; 1 = Left missing; 2 = Right missing; 3 = Mismatch; 4 = Untagged R. PREDICTED_READS is the number of times the reader should read the tag

frame based on the average car speed. S. LENGTH_AT_READING is the length in feet as determined from the wheel

detector. T. LENGTH_AT_TAG is the length in feet as read from the tag. See AAR S-918. U. N = North; S = South; E = East; W = West; I = Inbound; O = Outbound V. SPEED is the average car speed in eighths of a mile per hour. W. RAW_TAG_DATA is the undecoded tag data as read from the reader.

Wayside Interface Message Specification Final Draft, December, 1996 page D-1

APPENDIX D

WHEEL IMPACT LOAD DETECTOR MESSAGES Description:

The messages contained in this appendix describe the interaction between the wheel impact load detector and other wayside, central, and onboard equipment at the wayside system level.


Wheel Impact Load Detector (WILD)


Name: Impact Detector Defect Alarm Revision Date: 9/28/96 Message Number: 9.4.5 (Proposed) Source: Multiple Devices Label: 4869 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: 42 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


EVENT_TIME BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.


SEE NOTE

C

SPEED BYTE XXXXXXXX SEE NOTE

SEE NOTE

D

DIRECTION BYTE XXXXXXXX ASCII N,S,E,W

SEQUENTIAL_CAR_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

E.

NUMBER_OF_CAR_AXLES WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

F.

CAR_OWNER BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

G.

CAR_AEI_NUMBER BYTE[6] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

H.

CAR_TYPE BYTE XXXXXXXX ASCII SEE NOTE

I.

SEQUENTIAL_AXLE_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

J.

RAIL_SIDE_OF_WHEEL BYTE XXXXXXXX ASCII N,S,E,W


Frame Details


MSB....LSB

LSB Value

Range Notes

SEQUENTIAL_AXLE_NUMBER_ IN_CAR


SEE NOTE

SEE NOTE

K.

SIDE_CODE_OF_WHEEL BYTE XXXXXXXX SEE NOTE

SEE NOTE

L.

AXLE_LOCATION_OF_WHEEL_ ON_CAR


SEE NOTE

SEE NOTE

M.

PEAK_ALARM BYTE XXXXXXXX SEE NOTE

SEE NOTE

N.

DYNAMIC_ALARM BYTE XXXXXXXX SEE NOTE

SEE NOTE

N.

RATIO_ALARM BYTE XXXXXXXX SEE NOTE

SEE NOTE

N.

ECCENTRICITY_ALARM BYTE XXXXXXXX SEE NOTE

SEE NOTE

N.

PEAK_VALUE WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

O.

NOMINAL_VALUE WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

O.

ECCENTRICITY_VALUE WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

O.


Specification 250 object SPEC_REVISION. B. EVENT_TIME expressed in milliseconds since last time sync. C. D. E. F. G. CAR_OWNER is left-justified with ASCII spaces used to fill trailing

unused spaces. Default shall be binary zero. H. CAR_AEI_NUMBER is right-justified with ASCII zeros to fill unused spaces.

Default shall be binary zero. I. J.


K. SEQUENTIAL_AXLE_NUMBER _IN_CAR - start at 1 closest to lead L. SIDE_CODE_OF_WHEEL - L/R facing rear end M. 1-based N. A, B, C, D, E O. expressed in hundreds


Name: Impact Detector Skewing Alarm Revision Date: 9/28/96 Message Number: 9.4.6 (Proposed) Source: Multiple Devices Label: 4870 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: 36 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes



SEE NOTE

SEE NOTE

B.


SEE NOTE

C


SEE NOTE

D



SEE NOTE

SEE NOTE

E.


SEE NOTE

SEE NOTE

F.


ASCII SEE NOTE

G.


ASCII SEE NOTE

H.

CAR_TYPE BYTE XXXXXXXX ASCII L,F,P

SEQUENTIAL_AXLE_NUMBER_ OF_LEAD_AXLE


SEE NOTE

SEE NOTE

E.

SEQUENTIAL_CAR_AXLE_ NUMBER_OF_LEAD_AXLE


SEE NOTE

SEE NOTE

E.

LOCATION_OF_TRUCK_ ON_CAR


SEE NOTE

SEE NOTE

I.


Frame Details


MSB....LSB

LSB Value

Range Notes

HUNTING_TRUCK_ALARM BYTE XXXXXXXX SEE NOTE

SEE NOTE

J.

SKEWING_TRUCK_ALARM BYTE XXXXXXXX SEE NOTE

SEE NOTE

J.

ANGLE_OF_ATTACK BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

K.


Specification 250 object SPEC_REVISION. B. EVENT_TIME expressed in milliseconds since last time sync. C. D. E. start at 1 F. G. CAR_OWNER is left-justified with ASCII spaces used to fill trailing


Default shall be binary zero. I. 1-based J. A,B,C,D,E K. expressed in hundreds


Name: Impact Detector Overload Alarm Revision Date: 9/28/96 Message Number: 9.4.7 (Proposed) Source: Multiple Devices Label: 4871 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: 32 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes



SEE NOTE

SEE NOTE

B.


SEE NOTE

C


SEE NOTE

D



SEE NOTE

SEE NOTE

E.


SEE NOTE

SEE NOTE

F.


ASCII SEE NOTE

G.


ASCII SEE NOTE

H.


SEQUENTIAL_AXLE_NUMBER_ OF_LEAD_AXLE


SEE NOTE

SEE NOTE

E.

SEQUENTIAL_CAR_AXLE_ NUMBER_OF_LEAD_AXLE


SEE NOTE

SEE NOTE

E.

LOCATION_OF_TRUCK_ ON_CAR


SEE NOTE

SEE NOTE

I.


Frame Details


MSB....LSB

LSB Value

Range Notes

OVERLOAD_TRUCK_ALARM BYTE XXXXXXXX SEE NOTE

SEE NOTE

J.

PERCENT_OVERLOAD BYTE XXXXXXXX SEE NOTE

SEE NOTE

K.




Default shall be binary zero. I. 1-based J. A,B,C,D,E K.


Name: Impact Detector Unbalanced Alarm Revision Date: 9/28/96 Message Number: 9.4.8 (Proposed) Source: Multiple Devices Label: 4872 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: 28 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes



SEE NOTE

SEE NOTE

B.


SEE NOTE

C


SEE NOTE

D



SEE NOTE

SEE NOTE

E.


SEE NOTE

SEE NOTE

F.


ASCII SEE NOTE

G.


ASCII SEE NOTE

H.


LEFT/RIGHT_UNBALANCED_ ALARM


SEE NOTE

I.

FRONT/REAR_UNBALANCED_ ALARM


SEE NOTE

J.

LEFT/RIGHT_UNBALANCED_ LEVEL


SEE NOTE

K.


Frame Details


MSB....LSB

LSB Value

Range Notes

FRONT/REAR_UNBALANCED_ LEVEL


SEE NOTE

K.




Default shall be binary zero. I. J. K. expressed in hundreds


Name: Impact Detector Car Weight Information Revision Date: 9/28/96 Message Number: 9.4.9 (Proposed) Source: Multiple Devices Label: 4873 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: 26 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes



SEE NOTE

SEE NOTE

B.


SEE NOTE

C


SEE NOTE

D



SEE NOTE

SEE NOTE

E.


SEE NOTE

SEE NOTE

F.


ASCII SEE NOTE

G.


ASCII SEE NOTE

H.


CAR_WEIGHT WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

I.




B. EVENT_TIME expressed in milliseconds since last time sync. C. D. E. start at 1 F. G. CAR_OWNER is left-justified with ASCII spaces used to fill trailing


Default shall be binary zero. I. expressed in hundreds

Wayside Interface Message Specification Final Draft, December, 1996 page E-1

APPENDIX E

GRADE CROSSING DEVICE MESSAGES Description:

The messages contained in this appendix describe the interaction between the grade crossing device and other wayside, central, and onboard equipment at the wayside system level.


Grade Crossing Device


Name: Cross Warning Defect Alarm Revision Date: 9/28/96 Message Number: 9.2.18 (Proposed) Source: Multiple Devices Label: 4754 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: 6 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


SHORT-WARNING_TIMER_ ACTIVATION_FAILURE


SEE NOTE

B.

WARNING_TIME WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.

DISCRETE_BITS WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

D.


Specification 250 object SPEC_REVISION. B. C. In seconds. D.


Name: Cross Warning Info Report Revision Date: 9/28/96 Message Number: 9.4.10 (Proposed) Source: Multiple Devices Label: 4874 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: 10 Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


EVENT_DATE BYTE[3] XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.

EVENT_TIME BYTE[3] XXXXXXXX XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

C.

ASSOCIATED_DATA WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

D.


Specification 250 object SPEC_REVISION. B. C. D.

Wayside Interface Message Specification Final Draft, December, 1996 page F-1

APPENDIX F

WEIGH SCALE MESSAGES Description:

The messages contained in this appendix describe the interaction between the weigh scale and other wayside, central, and onboard equipment at the wayside system level.


Weigh Scale


Name: Weigh Scale Data Revision Date: 9/28/96 Message Number: 9.4.11 (Proposed) Source: Multiple Devices Label: 4875 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: ?? Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


TBD

TBD




Name: Weigh Scale Information Report Revision Date: 9/28/96 Message Number: 9.4.12 (Proposed) Source: Multiple Devices Label: 4876 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: ?? Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


TBD

TBD



Wayside Interface Message Specification Final Draft, December, 1996 page G-1

APPENDIX G

CLEARANCE (HIGH/LOW) DETECTOR MESSAGES Description:

The messages contained in this appendix describe the interaction between the clearance (high/low) detector and other wayside, central, and onboard equipment at the wayside system level.


Clearance (high/low) detector

Wayside Interface Message Specification Final Draft, December, 1996 page H-1

APPENDIX H

DRAGGING EQUIPMENT DETECTOR MESSAGES Description:

The messages contained in this appendix describe the interaction between the dragging equipment detector and other wayside, central, and onboard equipment at the wayside system level.


Dragging Equipment Detector

Wayside Interface Message Specification Final Draft, December, 1996 page I-1

APPENDIX I

WHEEL PROFILE MEASUREMENT DEVICE MESSAGES Description:

The messages contained in this appendix describe the interaction between the wheel profile measurement device and other wayside, central, and onboard equipment at the wayside system level.


Wheel Profile Measurement Device


Name: Wheel Profile Measurement Info Revision Date: 9/28/96 Message Number: 9.4.13 (Proposed) Source: Multiple Devices Label: 4877 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: ?? Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


TBD

TBD




Name: Automatic Wheel Inspection System Revision Date: 9/28/96 Message Number: 9.2.19 (Proposed) Source: Multiple Devices Label: 4755 Destination: Multiple Devices Transmission Rate: ........ Max Message Length: 1 Packet Size Parameter: ?? Octets Purpose:

Frame Details


MSB....LSB

LSB Value

Range Notes


TBD

TBD



Wayside Interface Message Specification Final Draft, December, 1996 page J-1

APPENDIX J

ACOUSTIC BEARING DETECTOR MESSAGES Description:

The messages contained in this appendix describe the interaction between the acoustic bearing detector and other wayside, central, and onboard equipment at the wayside system level.


Acoustic Bearing Detector Hot Box Detector AEI Reader


Name: Acoustic Detector Axle Data Revision Date: 9/28/96 Message Number: 9.4.14 (Proposed) Source: Multiple Devices Label: 4878 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 21 Octets Purpose: The Acoustic Detector Axle Data message provides all relevant data associated with each axle.

Frame Details


MSB....LSB

LSB Value

Range Notes



SEE NOTE

SEE NOTE

B.


.1 mm 1° F

SEE NOTE

C.


1 mm 1° F

SEE NOTE

C.


10° F SEE NOTE

D.


10° F SEE NOTE

D.

AXLE_SPACING WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

E.

STATUS WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

F.

CAR_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

G.


SEE NOTE

SEE NOTE

H.


SEE NOTE

SEE NOTE

I.




C. Journal heats can be displayed in millimeter or degrees F. -1 signifies a missed open wheel gate condition. The wayside detector type must be established such that the remote entity is prepared to process the correct data type.

D. Wheel heats are displayed in degrees F. E. If the most significant bit (MSB) is set to 1, the remaining 15 bits

represent the axle spacing in terms of feet; otherwise, the remaining bits represent eighths of feet.

F. The STATUS field is detector dependent. Bits can be dedicated to

represent auxiliary alarms, hot box or hot wheel alarms on this particular axle, or bearing ID for each side. An 1 represents an active condition for the alarms.

G. H. I.


Name: Acoustic Detector Defect Alarm Revision Date: 9/28/96 Message Number: 9.4.15 (Proposed) Source: Multiple Devices Label: 4879 Destination: Multiple Devices Transmission Rate: Upon Request or Unsolicited Max Message Length: 1 Packet After Train Passage Size Parameter: 29 Octets Purpose: The Acoustic Detector Defect Alarm message provides descriptive information regarding an alarm detected during train passage. The alarm may be real-time or the result of post train processing. Alarms can be related to journals, wheels, dragging equipment, or clearance conditions. Data is available on demand or automatically transmitted after train presence.

Frame Details


MSB....LSB

LSB Value

Range Notes



SEE NOTE

SEE NOTE

B.

ALARM_TYPE BYTE XXXXXXXX SEE NOTE

SEE NOTE

C.

AXLE_NUMBER WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

D.

SIDE_INDICATOR BYTE XXXXXXXX 1 0=Left 1=Right


1 mm 1° F

SEE NOTE

E.


1 mm 1° F

SEE NOTE

E.


ASCII SEE NOTE

F.


ASCII SEE NOTE

G.

VEHICLE_TYPE BYTE XXXXXXXX SEE NOTE

SEE NOTE

H.


Frame Details


MSB....LSB

LSB Value

Range Notes

NUMBER_OF_VEHICLES WORD XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

I.


SEE NOTE

J.


10° F SEE NOTE

K.


10° F SEE NOTE

K.


Specification 250 object SPEC_REVISION. B. SEQUENCE_NUMBER is the car sequence number. Zero is the first car. C. ALARM_TYPE is manufacturer-dependent defined field depicting hot box, hot

wheel, warm journal, DE, and clearance defects. D. Binary value represents the number of the axle containing the defect,

e.g., 64 (hex) - axle 100. E. Journal heats can be displayed in millimeter or degrees F. -1 signifies

a missed open wheel gate condition. The wayside detector type must be established such that the remote entity is prepared to process the correct data type.

F. CAR_ID is left-justified with ASCII spaces used to fill trailing unused

spaces. Default shall be binary zero. G. CAR_NUMBER is right-justified with ASCII zeros to fill unused spaces.

Default shall be binary zero. H. I. J. Number of axles on the car containing the defect. K. Wheel heats are displayed in degrees F.


Name: Acoustic Self-Test Failure Revision Date: 9/28/96 Message Number: 9.2.20 (Proposed) Source: Multiple Devices Label: 4756 Destination: Multiple Devices Transmission Rate: Upon Request, Appended to Max Message Length: 1 Packet the Post Train Report or Provided Unsolicited via Periodic Testing Size Parameter: 25 Octets Purpose: The Acoustic Self-Test Failure message provides detailed information of a system failure as soon as it is detected. A well condition (or no failure) will also be reported within this message. Failures may be fatal or simply classified as a warning.

Frame Details


MSB....LSB

LSB Value

Range Notes


MANUFACTURER_SPECIFIC BYTE[24] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

B.




Name: Acoustic Detector Train Report Revision Date: 9/28/96 Message Number: 9.4.16 (Proposed) Source: Multiple Devices Label: 4880 Destination: Multiple Devices Transmission Rate: Upon Request Max Message Length: 1 Packet Size Parameter: 240 Octets Purpose: The Acoustic Detector Train Report message provides a comprehensive train report containing data related to the site configuration, system parameters, and train passage.

Frame Details


MSB....LSB

LSB Value

Range Notes


RAILROAD_MNEMONIC BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

B.

SOFTWARE_VERSION BYTE[8] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

C.

MILEPOST BYTE[9] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

ASCII SEE NOTE

D.

SITE_NAME BYTE[30] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

ASCII SEE NOTE

E.

TRACK_DESIGNATION_ COMPASS

BYTE XXXXXXXX ASCII N,S,E,W

ARRIVAL_DATE BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

F.


Frame Details


MSB....LSB

LSB Value

Range Notes

ARRIVAL_TIME BYTE[3] XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

G.

DEPARTURE_DATE BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

F.

DEPARTURE_TIME BYTE[3] XXXXXXXX XXXXXXXX XXXXXXXX

BCD SEE NOTE

G.


1 SEE NOTE

H.

TRAIN_OF_DAY BYTE XXXXXXXX 1 SEE NOTE

I.

TRAIN_DIRECTION BYTE XXXXXXXX ASCII SEE NOTE

J.

ENTRY_SPEED WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

H.

EXIT_SPEED WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

H.

NUMBER_OF_AXLES WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

H.

AMBIENT_TEMP BYTE XXXXXXXX 1 SEE NOTE

K.

TRAIN_LENGTH BYTE[4] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

NUMBER_OF_ALARMS BYTE XXXXXXXX 1 SEE NOTE

M.

NUMBER_OF_INTEGRITY_ FAILURES


N.

NUMBER_OF_WARNINGS BYTE XXXXXXXX 1 SEE NOTE

O.

NUMBER_OF_HOT_JOURNALS BYTE XXXXXXXX 1 SEE NOTE

P.

NUMBER_OF_HOT_WHEELS BYTE XXXXXXXX 1 SEE NOTE

Q.

NUMBER_OF_DRAGGING_ EQUIPMENT_ALARMS


R.


Frame Details


MSB....LSB

LSB Value

Range Notes

NUMBER_OF_HIGH-LOAD_ ALARMS


S.

NUMBER_OF_WIDE-LOAD_ ALARMS


T.



1 SEE NOTE

U.



1 SEE NOTE

U.



1 SEE NOTE

U.



1 SEE NOTE

U.



1 SEE NOTE

V.



1 SEE NOTE

V.



1 SEE NOTE

V.



1 SEE NOTE

V.

TOTAL_CARS BYTE XXXXXXXX 1 SEE NOTE

W.

TOTAL_LOCOMOTIVES BYTE XXXXXXXX 1 SEE NOTE

X.

TOTAL_UNIDENTIFIED_ AXLES


1 SEE NOTE

L.

TRANSDUCER_A_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

TRANSDUCER_B_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

TRANSDUCER_C_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

TRANSDUCER_D_COUNT WORD XXXXXXXX XXXXXXXX

1 SEE NOTE

L.

MISSED_TRANSDUCER_A_ COUNT


1 SEE NOTE

L.


Frame Details


MSB....LSB

LSB Value

Range Notes

MISSED_TRANSDUCER_B_ COUNT


1 SEE NOTE

L.

MISSED_TRANSDUCER_C_ COUNT


1 SEE NOTE

L.

MISSED_TRANSDUCER_D_ COUNT


1 SEE NOTE

L.


1 SEE NOTE

U.


1 SEE NOTE

U.

SYSTEM_OPERATIONAL_ PARAMETERS

BYTE[1OO] XXXXXXXX XXXXXXXX " " XXXXXXXX XXXXXXXX

SEE NOTE

SEE NOTE

Y.


Specification 250 object SPEC_REVISION. B. C. D. E. F. The DATE record consists of 4 octets defined below.


1 LSB year 0-99

2 MSB year 0-99

3 day 1-31

4 month 1-12

G. The TIME record consists of 3 octets defined below.



1 second 0-59

2 minute 0-59

3 hour 0-24

H. Least significant byte followed by the most significant byte. I. J. TRAIN_DIRECTION record depicts compass direction or normal/reverse K. L. Least significant byte followed by the 2nd least significant byte,

followed by the 2nd most significant byte, followed by the most significant byte.

M. N. O. P. Each hot box alarm counts towards the total. Q. Manufacturer-specified parameters control how many consecutive hot wheels

constitute an alarm. R. S. T. U. Least significant byte followed by the most significant byte. Value can

be millimeters or degrees F. V. Binary value expressed as a three digit decimal, e.g., 1.xyz or 0.xyz. W X. Y. Manufacturer-specific.

Wayside Interface Message Specification Final Draft, December, 1996 page K-1

APPENDIX K

EVENT RECORDER MESSAGES Description:

The messages contained in this appendix describe the interaction between the event recorder and other wayside, central, and onboard equipment at the wayside system level.


Event Recorder


Name: Log File Request Revision Date: 10/10/96 Message Number: 3.1.3 (Proposed) Source: Multiple Devices Label: 1603 Destination: Event Recorder Transmission Rate: As Requested Max Message Length: 1 Packet Size Parameter: 5 Octets Purpose: This message is used to issue access commands to the event recorder.

Frame Details



MANUFACTURER_NAME WORD XXXXXXXX XXXXXXXX

ASCII A...Z B.

COMMAND BYTE XXXXXXXX 1 SEE NOTE C.

NUMBER BYTE XXXXXXXX 1 0-20 D.


Specification 250 object SPEC_REVISION. B. The MANUFACTURER_NAME record contains the manufacturer mnemonic. C. The COMMAND record contains the access command issued to the event

recorder.

Value Command

1 get next events

2 get previous events

3 get oldest events

4 get newest events

5 skip forward

6 skip backward

D. The NUMBER record contains the number of recordable events


Name: Log File Reply Revision Date: 10/10/96 Message Number: 3.4.28 (Proposed) Source: Event Recorder Label: 1820 Destination: Multiple Devices Transmission Rate: Upon Response to Log Max Message Length: 1 Packet File Request message Size Parameter: 83 Octets Purpose: This message is the corresponding response to the Log File Request message issued by the event recorder.

Frame Details



MANUFACTURER_NAME WORD XXXXXXXX XXXXXXXX

ASCII A...Z B.

EVENT_TEXT BYTE[80]


ASCII SEE NOTE C.


Specification 250 object SPEC_REVISION. B. The MANUFACTURER_NAME record contains the manufacturer mnemonic. C. The EVENT_TEXT record is an 80 ASCII-character string description of a

recordable event.

FINAL DRAFT WAYSIDE EQUIPMENT INTERFACE SPECIFICATIONgrouper.ieee.org/groups/railtransit/wg14/WEI...

Documents

Transcript of FINAL DRAFT WAYSIDE EQUIPMENT INTERFACE SPECIFICATIONgrouper.ieee.org/groups/railtransit/wg14/WEI...