B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 ... REVISION DATE DOCUMENT NAME DOCUMENT NUMBER PAGE . B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 iii

REVISION DATE DOCUMENT NAME DOCUMENT NUMBER PAGE

B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 i

This document contains proprietary and confidential information originated or owned by Cubic Transportation Systems, Inc. (CTS). Neither this document nor the information disclosed

herein shall be reproduced or transferred to other documents or used or disclosed to others for manufacturing or any other purposes except as specifically authorized in writing by CTS.

EXTERNAL INTERFACE SPECIFICATION

FOR THE

CUBIC TRANSPORTATION SYSTEMS, INC.

SAE J1708/J1587 IMPLEMENTATION

DRAFT


B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 ii



THIS PAGE INTENTIONALLY BLANK

DRAFT


B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 iii



REVISION STATUS (Template Revision Date 01 Apr 02)

Revision Date Description

A.00 04 Aug 03 Initial release.

B.00 30 Oct 03 Updated Figure 1, Section 3.4.1, Table 13, and Table 14 based on LACMTA meetings 10-8-03.

___________________________________________________ ___________________________________________________

Platform Manager—Approved for release Date Project Engineer Date

Jeff Brumfield Cathy Hall

___________________________________________________

Program Manager—Approved for release Date

Gerry Merten

___________________________________________________ ___________________________________________________

Received by Configuration Management. Date Technical Editor Date

Augie Cammarota

DRAFT


B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 iv




DRAFT


B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 v



TABLE OF CONTENTS

Section No./Title Page

REVISION STATUS .................................................................................................................................................. iii

1. INTRODUCTION .................................................................................................................................................. 1 1.1 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS ............................................................................ 1 1.2 REFERENCES ......................................................................................................................................... 1

2. PHYSICAL INTERFACES ................................................................................................................................... 3

3. APPLICATION MESSAGE OVERVIEW .............................................................................................................. 5 3.1 MID ASSIGNMENTS ................................................................................................................................ 6 3.2 TIME SYNCHRONIZATION ..................................................................................................................... 6 3.3 MESSAGE SEQUENCES ........................................................................................................................ 7 3.4 MESSAGING EXAMPLES ....................................................................................................................... 7

3.4.1 Sign-On (BMS Originated) ........................................................................................................ 9 3.4.2 Sign-On (BRCE Originated) ...................................................................................................... 9 3.4.3 In Service/Trip Change (BMS Originated) .............................................................................. 10 3.4.4 In Service/Trip Change (BRCE Originated) ............................................................................ 11 3.4.5 Driver Logoff (BMS Originated)............................................................................................... 11 3.4.6 Driver Logoff (BRCE Originated) ............................................................................................ 12

4. APPLICATION MESSAGE DETAILS ................................................................................................................ 13 4.1 REQUEST PARAMETER (PID 0) .......................................................................................................... 13 4.2 COMPONENT SPECIFIC REQUEST PARAMETER (PID 128) ............................................................ 13 4.3 TIME POINT ENCOUNTER (PID 205) ................................................................................................... 13 4.4 FAREBOX PROBE IDENTIFICATION (206) .......................................................................................... 14 4.5 CASHBOX INFORMATION (207) .......................................................................................................... 14 4.6 POSITION (PID 239) .............................................................................................................................. 14 4.7 COMPONENT IDENTIFICATION (PID 243) .......................................................................................... 14 4.8 CLOCK (PID 251) ................................................................................................................................... 14 4.9 DATE (PID 252) ...................................................................................................................................... 14 4.10 REQUEST PARAMTER (PID 256) ......................................................................................................... 15 4.11 DRIVER LOGON STATUS (PID 344) .................................................................................................... 15 4.12 FAREBOX PROBE TYPE (PID 347) ...................................................................................................... 15 4.13 FARE COLLECTION UNIT STATUS (PID 378) ..................................................................................... 15 4.14 COMPONENT SPECIFIC REQUEST PARAMETER (PID 384) ............................................................ 16 4.15 PAGE 2 MULTISECTION PARAMETER (PID 448) ............................................................................... 16 4.16 FARE COLLECTION UNIT SERVICE DETAILS (PID 502) ................................................................... 16 4.17 VEHICLE CONTROL HEAD KEYBOARD MESSAGE (PID 505) .......................................................... 16

4.17.1 Description .............................................................................................................................. 16 4.17.2 Format and Content ................................................................................................................ 16

4.18 DRIVER IDENTIFICATION (PID 507) .................................................................................................... 17 4.18.1 Format and Content ................................................................................................................ 17

4.19 TRANSIT ROUTE IDENTIFICATION (PID 508) .................................................................................... 17

DRAFT


B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 vi



LIST OF FIGURES

No./Title Page

Figure 1. BRCE and BMS Interaction .........................................................................................................................8

LIST OF TABLES

No./Title Page

Table 1. Messages Originated from BRCE ................................................................................................................5 Table 2. Messages which the BRCE Accepts ............................................................................................................6 Table 3. Sign-On (BMS Originated) Dialog .................................................................................................................9 Table 4. Sign-On (BMS Originated) Dialog ...............................................................................................................10 Table 5. In Service/Trip Change (BMS Originated) Dialog .......................................................................................11 Table 6. In Service/Trip Change (BRCE Originated) Dialog .....................................................................................11 Table 7. Driver Logoff (BMS Originated) Dialog .......................................................................................................12 Table 8. Driver Logoff (BRCE Originated) Dialog .....................................................................................................12 Table 9. SAE J1587 Data Types...............................................................................................................................13 Table 10. PID 243 Data Format ................................................................................................................................14 Table 11. PID 378 Alarm Details ..............................................................................................................................15 Table 12. PID 378 Dialog ..........................................................................................................................................16 Table 13. PID 505 Data Format ................................................................................................................................17 Table 14. PID 507 Data Format ................................................................................................................................17

DRAFT


B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 1



1. INTRODUCTION

The purpose of this External Interface Specification (EIS) is to ensure uniformity of the intersystem communications software for Cubic Transportation Systems, Inc., (Cubic) Bus Revenue Collection Equipment (BRCE) using the Society of Automotive Engineers (SAE) J1708/J587 standards. The information is provided to assist design engineers in determining interfaces to and from the system. Customers, third-party contractors, developers, and maintainers will find this document useful in design, development, and diagnostic activities. It is not intended to restate the SAE standards. It is intended to document Cubic‟s implementation of those standards.

The term “Bus Revenue Collection Equipment” is used to generically refer to Cubic revenue collection equipment on a bus. This equipment may be a Cubic Driver Console Unit connected to a farebox and/or contactless smart card device, or the combined Cubic/GFI Enhanced Odyssey farebox. This document is written from the BRCE perspective.

1.1 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

AFCS Automatic Fare Collection System

ASCII American Standard Code for Information Interchange

BRCE Bus Revenue Collection Equipment

BMS Bus Management System

CC Central Computer

Cubic Cubic Transportation Systems, Inc.

EIS External Interface Specification

GFI GFI GenFare

ID Identification

IR Infrared

MID Message Identification

PID Parameter Identification

SAE Society of Automotive Engineers

1.2 REFERENCES

[1] Serial Data Communications Between Microcomputer System in Heavy-Duty Vehicle Applications, SAE J1708, Rev. OCT93.

[2] Joint SAE/TMC Electronic Data Interchange Between Microcomputer Systems in Heavy-Duty Vehicle Applications, SAE J1587, Rev. FEB2002.

DRAFT






DRAFT





2. PHYSICAL INTERFACES

The physical interface is defined by the SAE standard and will not be restated in this document. The actual interconnecting cable is contract specific and will be defined separately.

DRAFT






DRAFT





3. APPLICATION MESSAGE OVERVIEW

For the purposes of this document, it is assumed that the BRCE will be communicating with a Bus Management System (BMS). Table 1 lists the messages which will be sent by the BRCE either in response to a specific request or unsolicited, as indicated in the Frequency/Usage column.

Table 2 lists the messages originating from an external device to which the BRCE will respond.

Table 1. Messages Originated from BRCE

PID Message Description Frequency/

Usage

Reference

Section

128 Component specific request

Request for information from a specific unit When needed 1

4.2

205 Time Point Encounter

Transfer cut time. Used to report Cut time currently used with BRCE.

On request 4.3

206 Farebox Probe Identification

Broadcast along with Parameter Identification (PID) 347 and PID 378 at the start of probing.

At probing 4.4

207 Cashbox Information

Broadcast when Cashbox Identification (ID) change detected.

At cashbox exchange

4.5

243 Component ID Model and serial numbers of BCRE On request 4.7

251 Clock Time On request 4.8

252 Date Date in quarter days, month, year On request 4.9

344 Driver Logon Status

Confirmation of Driver Login from BMS On request 4.11

347 Farebox Probe Type

Identifies what type of probe is currently being used at the BRCE

At probing 4.12

378 Fare Collection Unit Status

Used to report alarms for the BRCE On event 4.13

448 Page 2 Multisection Parameter

Used to transmit parameters that are longer than what is limited by SAE J1708.

Sign-on and Trip Change

4.15

502 Fare Collection Unit Service Details

Fareset information. Route, run, trip, and direction information ignored. Due to Block range limitations, this information will be provided in PID 508.


4.16

505 Vehicle Control Head Keyboard Message

Reports Operator keypad depressions for up to four specially configured BRCE buttons.

When needed

4.17

507 Driver Identification

Driver Log on/Log Off Information Sign-on and Sign-off

4.18

508 Transit Route Identification

Route, run, and block information Sign-on and Trip Change

4.19

Note: 1 PID 128 will be used to request PID 239 from the BMS.

DRAFT





Table 2. Messages which the BRCE Accepts

PID Message Description Frequency/

Usage

Referenc

e Section

0 Request parameter

Request for information from all units. When needed 1

4.1

128 Component specific request

Request for information from a specific unit

When needed 1

4.2

205 Time Point Encounter

Transfer cut time. Used to update the BRCE transfer Cut Time.

Trip Change 4.3

239 Position Coordinates of the current position. When needed

4.6

256 Request Parameter

Requests page 2 information from all units that support the requested parameter.

When needed 2

4.10

344 Driver Logon Status

Confirmation of Driver Login from BMS During Sign on process

4.11

384 Component-Specific Request Parameter

Requests page 2 information from a specific unit When needed 2

4.14

448 Page 2 Multi-section Parameter

Used to transmit parameters that are longer than what is limited by SAE J1708.


4.15

502 Fare Collection Unit Service Details

Fareset information. Route, run, trip, and direction information ignored. Due to Block range limitations, this information will be provided in PID 508.

On request 4.16

507 Driver Identification

The Driver ID entered at the BMS console to use for BRCE Sign-on.

On request 4.18

508 Transit Route Identification

The Route information entered at the BMS console for BRCE trip definition.

On request 4.19

Note: 1 The BRCE only responds to request PID‟s 205, 206, 207, 243, 251, and 252 from external devices. 2 The BRCE only responds to request PID‟s 502, 507, and 508 from external devices.

3.1 MID ASSIGNMENTS

The Message Identification (MID) for the BRCE will default to 196 as a revenue collection device. The BRCE will respond to the requests as defined in this document regardless of the originating MID.

Messages directed to the BMS will use destination MID 188.

3.2 TIME SYNCHRONIZATION

The BRCE will not set its internal time or date upon receipt of a PID 251 Clock or PID 252 Date message. The BRCE will synchronize time with the Automatic Fare Collection System (AFCS) Central Computer(CC). The BRCE will transmit local time upon receipt of a request for PID 251, and local date upon receipt of a request for PID 252.

DRAFT





3.3 MESSAGE SEQUENCES

SAE J1708/J1587 only requires checking of the first transmitted character to ensure that a collision has not occurred before continuing the rest of the transmission. Cubic recommends that for critical operational items such as setting route and fareset information, that the BMS query the BRCE following the request to confirm that the parameters were correctly received. It is the message originator‟s responsibility to verify that the critical data is received and to limit the number of retries in the event of successive communication failures.

Customer implementations of SAE J1708/J1587 can vary due to the unique nature of the Authority‟s numbering schemes. To accommodate these variances, it may be necessary to broadcast multiple messages instead of a single message to perform a specific action. Performing a Trip Change is a typical case. The BRCE requires, at a minimum, fareset, and route information. Fareset defines the business rules that the BRCE will execute. Route information is used for transfer validation. Run and Block information can also be used for tagging route/run and transaction information but are not required for the BRCE to operate. To transmit this information between the BMS and BRCE, two messages:

PID 508 (route/run/block)

PID 502 (fareset)

will be used to fully define a trip.

3.4 MESSAGING EXAMPLES

The BMS has the ability to control the operational state of the BRCE by sending sign-on, sign-off, and trip set information. The BRCE must have the ability to operate through its own data entry facility, regardless of the BMS installation or activity state. Figure 1 shows the expected dialog between the devices during normal BRCE operations. The order of messages shown does not imply the actual transmission sequence. For example, the BMS will not necessarily wait for a response to a previous query before sending the next PID.

DRAFT





Driver enters data

at BRCE and

presses enter key

Fareset # = A'

Driver # = B'

Route # = C'

BRCE

validates data

locally

Fail

Pass

BRCE in revenue

service and

transmits

Fareset and

Transit Route

Fareset # = A

Driver # = B

Route # = C

IVU receives

Driver ID and

transmits Driver ID

to BMS for

validation

Driver # = B

BMS receives

submitted Driver

ID

BMS ValidationPass

IVU transmitts:

Driver Logon Status

Driver ID

Position

Vehicle ID

Date Message

Clock

Transit Route

Fareset (Note 2)

Cut Time(Note 3)

Driver # (from

previous entry)

Fareset # = A

Route # = C

Fail

Driver Login

BRCE receives

data from IVU

BRCE

validates data

locally

Create New

Route/Run Record

with new

information

Pass

Continue

BRCE Operations

Sound BRCE Error

Tone - Notifies

Operator that BMS

login validation

failed.

Fail

Send failed login

status to IVU

IVU displays failed

login status and

reason.

If login display

brought up it

could confuse

operator in the

middle of a

transaction. This

event shouldn't

occur if BMS and

BRCE system

data is

coordinated.

Cubic Transportation SystemsBRCE/BMS Login/Route Change Flowchart

BMSBRCE

Schedule Based

Route/Run Change

IVU transmitts:

Transit Route

Fareset (Note 2)

Cut Time (Note 3)

A

Operator notified of

failed validation.

BRCE remains in

original operational

state with previous

data. Up to operator

to correct problem.

Note: Driver # will

be cleared if failed

login status received

from BMS when in

Out of Service mode.

Driver Presses

Login, Route/Run

Change button

(# Key)

Driver enters

Driver ID:

Driver Card

or

Keypad (requires

advancing to

another field to

signify completion)

Farebox transmits

Driver ID

Driver Waits for

BMS response

Driver # = B

If no BMS

available then

don't wait.

A

Change Route/

Run Data

Driver Presses

Login, Route/Run

Change button

('#' Key)

Driver Login at IVU

Driver enters

Driver ID at IVU

and transmits to

BMS

Continue

BRCE Operations IVU Receives:

Fareset

Transit Route

(Note 1)

Fareset

messages from

IVU will be

ignored if the

BRCE is in coin

bypass

Note 1: Data ignored by IVU unless Run number changed in Transit

Route data

Note 2: If Fareset data is not available in BMS schedule data, the

Fareset message will NOT be sent.

Note 3: If Cut time data is not available in BMS schedule data, the Cut

Time message will not be sent. BRCE will use a default Cut

Time in its place.

Position, Vehicle

ID, Date

Message, and

Clock PIDs

ignored by

BRCE.

Login originate

at BRCE

No

IVU transmitts:

Driver Logon StatusYes

Continue

Figure 1. BRCE and BMS Interaction

DRAFT





3.4.1 Sign-On (BMS Originated)

This sequence would be performed, as an example, to sign-on to begin a route from the depot. The exchange is described in Table 3.

Table 3. Sign-On (BMS Originated) Dialog

PID DESCRIPTION SENDER RECEIVER

344 Transmits BMS logon status BMS BRCE

384 Requests last received logon status BMS BRCE

344 Transmits last received BMS logon status BRCE BMS

507 Sign on command sends Driver Identification BMS BRCE

256/384 Requests last received PID 507 BMS BRCE

507 Transmits last received PID 507 BRCE BMS

508 Transmits Route/Run/Block to BRCE BMS BRCE



502 Transmits fareset information (when available) BMS BRCE

256/384 Requests last received fareset information BMS BRCE

502 Transmits last received fareset information BRCE BMS

205 Transmits cut time (when available) BMS BRCE

0/128 Requests last received cut time BMS BRCE

205 Transmits last received cut time BRCE BMS

The BRCE will start a timer upon the receipt of the first message in the sign-on process above. After a set „delay period‟ (initially set for 1 second), all data collected between the receipt of the first message and the expiration of the timer will be processed. If the BRCE sign-on is successful it will create a new Route/Run record and enter revenue service. If the sign-on is unsuccessful, the BRCE will indicate the error on the driver‟s display.

If the fareset information and cut time information are not sent within the delay period, the BRCE will use the default values for fareset and cut time. The Fareset and default cut-time are parameters configured from the Cubic Central Computer.

3.4.2 Sign-On (BRCE Originated)

This sequence would be performed, as an example, to begin the sign-on process using the BRCE to obtain the Driver ID. The exchange is described in Table 4. DRA

FT





Table 4. Sign-On (BMS Originated) Dialog


507 Driver ID sent once data entered at BRCE BRCE BMS

384 Requests last received PID 507 BRCE BMS

507 Transmits last received PID 507 BMS BRCE

If BMS successfully verifies driver logon




507 Sign on command sends operator identification BMS BRCE












If BMS fails to verify driver logon




BRCE indicates failed login on BRCE operator console. Details of specific failure reason should be available from the on-board BMS system console.

The BRCE will start a timer upon the receipt of the first message after the login is verified. After a set „delay period‟ (initially set for 1 second), all data collected between the receipt of the first message and the expiration of the timer will be processed. If the BRCE sign-on is successful it will create a new Route/Run record and enter revenue service. If the sign-on is unsuccessful, the BRCE will indicate the error on the driver‟s display.

If the fareset information and cut time information are not sent within the delay period, the BRCE will use the default values for fareset and cut time.

3.4.3 In Service/Trip Change (BMS Originated)

This sequence would be performed, as an example, to change from one route to another due to BMS schedule data. The exchange is described in Table 5.

DRAFT





Table 5. In Service/Trip Change (BMS Originated) Dialog











The BRCE will start a timer upon the receipt of the first BMS message. After a set „delay period‟ (initially set for 1 second), all data collected between the receipt of the first message and the expiration of the timer will be processed. If the BRCE trip change is successful it will create a new Route/Run record. If the trip change is unsuccessful, the BRCE will indicate the error on the driver‟s display.

If the fareset information and cut time information are not sent within the delay period, the BRCE will use the default values for fareset and cut time.

3.4.4 In Service/Trip Change (BRCE Originated)

This sequence would be performed, as an example, to change from one route to another due to bus operator data entry at the BRCE console. BRCE will initiate the message sequence once the trip change is successfully completed. The exchange is described in Table 6.

Table 6. In Service/Trip Change (BRCE Originated) Dialog


508 Transmits Route/Run/Block to BRCE BRCE BMS

384 Requests last received PID 508 BRCE BMS


502 Transmits fareset information BRCE BMS

384 Requests last received fareset information BRCE BMS

502 Transmits last received fareset information BMS BRCE

3.4.5 Driver Logoff (BMS Originated)

This sequence would be performed if an operator logoff is commanded by BMS. The exchange is described in Table 7.

DRAFT





Table 7. Driver Logoff (BMS Originated) Dialog


507 BMS sends Driver = 0, Manual Logoff. BRCE logs operator off. BMS BRCE

256/384 Request PID 507 BMS BRCE

507 Transmits last received Driver ID BRCE BMS

3.4.6 Driver Logoff (BRCE Originated)

This sequence would be performed when an operator logoff is initiated via the BRCE console or due to automatic timeout. The exchange is described in Table 8.

Table 8. Driver Logoff (BRCE Originated) Dialog


507 BRCE sends Driver = 0, Manual/Automatic reason code after BRCE completes logoff.

BRCE BMS

384 Request PID 507 from BMS BRCE BMS

507 Transmits last received Driver ID BMS BRCE

In the event of successive communications failures, the BRCE will attempt to deliver this message a maximum of three times.

DRAFT





4. APPLICATION MESSAGE DETAILS

A message consists of a MID character followed by the message contents and a checksum. The MID is a 1-byte identifier for the transmitter. The typical message is a 1-byte Parameter Identification (PID) followed by the data. There is a mode to allow for PIDs greater than 254 by invoking “page 2” mode. A PID of 255 invokes “page 2” mode, and the next byte is interpreted indexed from 256. For example, in “page 2” mode, a zero in the PID field is interpreted as PID 256.

Messages to the BRCE may contain more than one parameter (PID/Data set), provided the maximum message length is not exceeded. If the BRCE cannot process a parameter due to an invalid PID or data, the remainder of the message will be ignored.

The following sections discuss each message handled by the BRCE. The “Format and Content” subsections detail the BRCE interpretation of a message if more information than the SAE J1587 definition is needed. The data types for the messages in this section comply with those described in SAE J1587. A summary of the types used in this document is provided in Table 9 for easy reference.

Table 9. SAE J1587 Data Types

Data Type Description Length (characters)

B/BM Binary Bit-Mapped 1

Uns/SI Unsigned Short Integer 1

Uns/I Unsigned Integer 2

Uns/LI Unsigned Long Integer 4

ALPHA Alphanumeric 1

4.1 REQUEST PARAMETER (PID 0)

This PID requests the current information from all units for a particular PID. It is used in this application to request PIDs 243, 251, and 252 from the BRCE. The BRCE does not respond to any other PID 0 requests. This message is sent by BMS when the information is required, and expected no more frequently than once per minute.

4.2 COMPONENT SPECIFIC REQUEST PARAMETER (PID 128)

This PID will request the current information from a particular unit for a particular PID. It will be used by this application to request PIDs 206, 207, 243, 251, and 252 from the BRCE. The BRCE does not respond to any other PID 128 requests. This message is sent by the BMS when the information is required.

The BRCE will use PID 128 to request PID 239 (Position Data) to log the current bus location.

4.3 TIME POINT ENCOUNTER (PID 205)

This message is used to transmit schedule information about designated time points along a route. The BRCE will interpret this message to be the scheduled arrival time at the end of a route. It will be used by the BRCE to encode a „Cut Time‟ on a ticket on first use. Subsequent uses of this ticket will read the Cut Time from the ticket and add a downloadable transfer duration period to determine whether a transfer time window is still valid. In general, it is expected that this message will be sent at the beginning of a trip. If intermediate time points along the route are inserted into the BMS schedule data, the cut time field should be populated with the same value as transmitted at the beginning of the trip (scheduled arrival time at the end of the route).

If this message is received after a new route/run record is created (See Sections 3.4.1, 3.4.2, and 3.4.3), a new record will not be created but the current cut time will be updated.

DRAFT





4.4 FAREBOX PROBE IDENTIFICATION (206)

This message is sent from the BRCE to identify the Infrared (IR) probe number currently being used to extract information from the BRCE. It will be sent in conjunction with PIDs 347 and 378 at the start of probing. The BRCE will also respond to a PID 128 request for this information.

4.5 CASHBOX INFORMATION (207)

The BRCE will broadcast this message along with the appropriate PID 378 message upon detecting a change in the cashbox identification number. The BRCE will also respond to a PID 128 request for this information.

4.6 POSITION (PID 239)

The BRCE will periodically poll the BMS for the bus‟ current position and log the last set of coordinates received prior to the onset of passenger processing. Polling will cease until such time as a predetermined lull in passenger activity is detected. All new transaction data will be stamped with the current logged coordinates.

4.7 COMPONENT IDENTIFICATION (PID 243)

This message will provide the current component identification for the BRCE. This message is sent by the BRCE to the BMS in response to a PID 0 or PID 128 request. See also Table 10.

Transaction format: pn*ooooooooo*nnnnnn

Table 10. PID 243 Data Format

DATA NAME LENGTH FORMAT DESCRIPTION

p PID 1 Uns/SI PID (243)

n Length 1 Uns/SI Data length (17)

*ooooooooo Farebox model 10 ALPHA Model of the farebox (*950001012)

*nnnnnn Farebox serial number

7 ALPHA Serial number assigned to farebox (e.g. *004532)

This message contains the farebox model number expressed as ASCII numeric characters. The separators are ASCII “*”. Including the MID, PID, length byte, and checksum byte, this message is 21 bytes long.

4.8 CLOCK (PID 251)

This PID reports the current time according to the BRCE. The BRCE time is synchronized to the Automated Fare Collection System Central Computer at time of probing. This message is sent by the BRCE to the BMS in response to a PID 0 or PID 128 request.

4.9 DATE (PID 252)

This message reports the current date according to the BRCE. The BRCE date is synchronized to the Automated Fare Collection System Central Computer at time of probing. This message is sent by the BRCE to the BMS in response to a PID 0 or PID 128 request.

DRAFT





4.10 REQUEST PARAMETER (PID 256)

This message is used to request parameter data transmission of page 2 parameters from other components on the data link. The BRCE will respond to this request for PIDs 502, 507, and 508.

4.11 DRIVER LOGON STATUS (PID 344)

This message is transmitted by the BMS to communicate the results of a requested driver logon. The BRCE will report a failed driver logon on the BRCE terminal. This message is otherwise ignored.

4.12 FAREBOX PROBE TYPE (PID 347)

This message is sent from the BRCE to identify the probe type currently being used to extract information from the BRCE. It will be broadcast in conjunction with PIDs 206 and 378 at the start of probing.

4.13 FARE COLLECTION UNIT STATUS (PID 378)

This message is used to broadcast BRCE events on the data link. It is generated at the time of the event. Each event can be classified as either an emergency or non-emergency condition.

The following events (See Table 11) will trigger this message:

Table 11. PID 378 Alarm Details

EVENT NON-EMERGENCY/EMERGENCY

(BIT 8)

ALARM IDENTIFIER

(BITS 7-1 VALUE)

IR Probe started 0 (Non-emergency) 2

IR Probe completed 0 (Non-emergency) 3

Cashbox removed 0 (Non-emergency) 4

Cashbox removed, unauthorized 1 (Emergency) 4

Cashbox restored 0 (Non-emergency) 5

Cashbox restored, unauthorized 1 (Emergency) 5

Cashbox door timeout 1 (Emergency) 6

Cashbox door opened, authorized 0 (Non-emergency) 7

Cashbox door opened, unauthorized 1 (Emergency) 7

Coin box near full 0 (Non-emergency) 9

Coin box full 1 (Emergency) 10

Currency box near full 0 (Non-emergency) 11

Currency box full 1 (Emergency) 13

Coin mech placed in manual bypass 1 (Emergency) 18

Coin mech reset to normal operation 0 (Non-emergency) 19

Maintenance access (in service) 1 (Emergency) 24

Maintenance assess (out of service) 1 (Emergency) 25

The exchange is described in Table 12.

DRAFT





Table 12. PID 378 Dialog


378 BRCE broadcasts event BRCE BMS

384 Request PID 378 from BMS BRCE BMS


4.14 COMPONENT SPECIFIC REQUEST PARAMETER (PID 384)

This message is used to request page 2 parameter data transmissions from a specified component on the data link. The BRCE will respond to this request for PIDs 502, 507, and 508.

4.15 PAGE 2 MULTISECTION PARAMETER (PID 448)

This PID will only be used to send PID 508 Transit Route Identification, and only when the combination of route, run, and block information (including delimiters) exceeds 16 characters.

Attempts to request PID 448 information from the farebox are not supported.

4.16 FARE COLLECTION UNIT SERVICE DETAILS (PID 502)

This message will be used to transmit the current fareset for the BRCE. The assigned route, assigned run, and assigned block fields of this message will be ignored. The fareset information contained in PID 502 will be used in conjunction with the assigned route, assigned run, and assigned block fields contained in PID 508 to perform a Trip Change.

If the BMS transmits this message after a new Route/Run record is created (See Sections 3.4.1, 3.4.2, and 3.4.3), the delay period will be restarted. Once the delay period expires, the data collected will be processed and a new Route/Run record will be created.

This message can originate at the BRCE or the BMS.

4.17 VEHICLE CONTROL HEAD KEYBOARD MESSAGE (PID 505)

4.17.1 Description

This message reports BRCE keyboard depressions for keys that have been assigned BMS functions. It is up to the other equipment on the data link to interpret and act upon the key indicated.

4.17.2 Format and Content

The data types used in the transaction format below are described in Table 9.

Transaction format (See also Table 13): pnab

DRAFT








n Length 1 Uns/SI Data length = 2

a Scan Code Value 1 Uns/SI Not Used

b Function Key Value 1 Uns/SI Key Depressed:

1: BMS Key 1

2: BMS Key 2

3: BMS Key 3

4: BMS Key 4

Including the MID, PID, length byte, and checksum byte, this message is 6-bytes long.

4.18 DRIVER IDENTIFICATION (PID 507)

This PID will allow the BMS and BRCE to send a sign-on/sign-off command message. This message functions as a command when sent by either device. The BRCE can also send this command when a new driver number is entered at the BRCE console or an automatic sign-off occurs. A Sign-off command is indicated by filling the Driver ID = 0 and including the reason in the „Other Driver Data‟ field. The „Other Driver Data‟ field will only be transmitted with a sign-off command.

4.18.1 Format and Content

The Driver ID and Other Driver Data fields are variable in length and are separated by an ASCII „*‟. The data types used in the transaction format are described below. The field delimiter („*‟) is always required even if the Other Driver Data field is not included.

Transaction format (see also Table 14): pnaaaa*b




n Length 1 Uns/SI Data length = variable

aaaa Driver ID Variable ALPHA Driver ID (0-999999)

b Other Driver Data Variable ALPHA “1”: Manual Sign-off

“2”: Automatic Sign-off

4.19 TRANSIT ROUTE IDENTIFICATION (PID 508)

This PID will allow the BMS to send the BRCE a portion of the Trip Change data. This message functions as a command when received by the BRCE.

Before performing a service state change, a series of validation checks are performed. First, the keyboard state is checked to ensure there is no keyboard activity (pending command). If the keyboard is idle, the BRCE is checked to ensure a user is signed-on, the tables are valid, no security alarms are active, and the fareset and route code are valid. If any validations fail, an error will be displayed on the BRCE.

DRAFT





The assigned route, assigned run, and assigned block fields will be used for Sign-on or Trip Change. Similar fields found in PID 502 will be ignored by the BRCE.

When a Trip Change is initiated and completed at the BRCE console, the BRCE will transmit PIDs 502 and 508. The fareset data will be contained in PID 502, and the assigned route, assigned run, and assigned block will be contained in PID 508.

DRAFT

Documents

B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 ... REVISION DATE DOCUMENT NAME DOCUMENT NUMBER PAGE . B.00 30 Oct 03 EIS for the CTS SAE J1708/J1587 Implementation 5100-62011 iii