CEN/TS 13149-3:2007

SLOVENSKI STANDARD
01-februar-2009
-DYQLSUHYR]6LVWHPL]DþDVRYQRUD]SRUHMDQMHLQQDG]RUFHVWQLKYR]LOGHO
9VHELQDVSRURþLO:25/'),3
Public transport - Road vehicle scheduling and control systems - Part 3: WorldFIP
message content
Öffentlicher Verkehr - Straßenfahrzeuge - Planungs- und Steuerungssysteme - Teil 3:
WORLDFIP
Transports publics - Systèmes d'ordonnancement et de contrôle des véhicules routiers -
Partie 3 : Contenu de messages WorldFIP
Ta slovenski standard je istoveten z: CEN/TS 13149-3:2007
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
43.040.15 $YWRPRELOVNDLQIRUPDWLND Car informatics. On board
9JUDMHQLUDþXQDOQLãNLVLVWHPL computer systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL SPECIFICATION
CEN/TS 13149-3
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
July 2007
ICS 35.240.60; 43.080.20; 45.060.01

English Version
Public transport - Road vehicle scheduling and control systems -
Part 3: WorldFIP message content
Transports publics - Systèmes d'ordonnancement et de Öffentlicher Verkehr - Straßenfahrzeuge Planungs- und
contrôle des véhicules routiers - Partie 3 : Contenu de Steuerungssysteme - Teil 3: WORLDFIP Nachrichteninhalt
messages WorldFIP
This Technical Specification (CEN/TS) was approved by CEN on 5 September 2006 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their
comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available
promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)
until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36  B-1050 Brussels
© 2007 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 13149-3:2007: E
worldwide for CEN national Members.

Contents Page
Foreword.4
Introduction .4
1 Scope.4
2 Normative references.5
3 Terms and definitions .5
4 Vehicle related identifiers and numbers .5
4.1 Vehicle operation identifiers and numbers.6
4.2 Fare terms and related identifiers and numbers .10
5 Requirements.11
5.1 Hardware preferences.11
5.2 Devices in a complex network.11
5.3 Station numbers.12
5.4 Bus arbiter modes .13
5.5 Physical layer.13
5.5.1 Bit rates.13
5.5.2 Bus connector.13
5.5.3 Bus cable.13
5.6 Data modelling.13
5.6.1 General.13
5.6.2 Text structure.14
5.6.3 Plain text.14
5.6.4 XML formatted text .14
5.7 Object dictionary.15
5.7.1 Overview of object dictionary entries.15
5.7.2 Detailed Specification of Process Data Units.15
Annex A (informative) Device profiles.44
A.1 Definitions.44
A.2 Device Profile Model.47
A.2.1 Device General Structure.47
A.2.2 Physical Node Interface.50
A.2.3 Logical Node Interface.51
A.2.4 Function Block Interface.53
A.2.5 Exchange Block Interface .57
A.2.6 General Function Block Type.62
A.3 Overview of Device Profiles.64
A.3.1 Definitions.64
A.3.2 Profiles Positioning.66
A.3.3 Profiles Characteristics.67
Annex B (informative) Example of Simple Network Application .68
B.1 Simple Network Application.68
B.1.1 Introduction.68
B.1.2 List of Stations.68
B.2 Bus Arbitration.68
B.2.1 Start-up and Election Timeouts.68
B.2.2 Bus Arbiter Priority.69
B.2.3 Micro Cycle.70
B.2.4 Macro Cycle.71
B.3 Virtual Device Profiles.71
B.3.1 Mapping of Virtual Device, Physical Device and Process Data Units.71
B.3.2 Process Data Unit Producers and Consumers.75
Annex C (informative) Examples of Device Descriptions .78
C.1 Device Description Example 1 .78
C.2 Device Description Example 2 .80
Bibliography.81

Foreword
This document CEN/TS 13149-3:2007 has been prepared by Technical Committee CEN/TC 278 “Road
transport and traffic telematics”, the secretariat of which is held by NEN.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Cyprus, Czech
Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and United Kingdom.
Introduction
This Technical Specification is intended to be developed into part 3 of EN 13149, which gives rules for on-
board data transmission systems.
This part 3 together with part 1 and part 2 of EN 13149 describes a complete solution independent from part 4,
part 5 and part 6.
This document uses terms which are already used in other standards e.g. EN 12896 Road transport and
traffic telematics - Public transport - Reference data model, when applicable.
1 Scope
This Technical Specification specifies the choice and the general application's rules of an onboard data
transmission bus between the different equipment for service operations and monitoring of the fleet. This
applies to equipment installed onboard buses, trolley-buses and tramways only as part of a bus fleet operation.
It excludes tramways when they are operated as part of a train, subway or metro operation. This equipment
includes operation aid systems, automatic passenger information systems, fare collection systems, etc.
The equipment directly related to the safety-related functioning of the vehicle (propulsion management, brake
systems, door opening systems, etc.) are excluded from the scope of the present standard and are dealt with
in other standardisation bodies.
For the described application two bus systems are standardised. Part 1 to part 3 of EN 13149 describe the
WorldFIP bus system and part 4 to part 6 describe the CANopen bus system. There is no ranking between the
two bus systems.
The present Technical Specification covers the link between equipment inside a single vehicle. Although it
could be applied to multiple vehicles, this application is not explicitly covered by this standard.
Part 1 of EN 13149 specifies the WorldFIP-based network. This specification describes the general
architecture in terms of hierarchical layers according to the ISO reference model for Open Systems
Interconnection (OSI) specified in ISO 7498.
Part 2 of EN 13149 specifies in detail the connectors and the connector pin assignment and the cabling.
Part 3 (this Technical Specification) specifies in detail the application profiles for a simple network.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
EN 12896:2006, Road transport and traffic telematics - Public transport - Reference data model
EN 13149-1; Public transport - Road vehicle scheduling and control systems - Part 1: WORLDFIP definition
and application rules for onboard data transmission
EN 13149-2; Public transport - Road vehicle scheduling and control systems - Part 2: WORLDFIP cabling
specifications
3 Terms and definitions
For the purposes of this document, the terms and definitions given in EN 12896:2006 apply.
4 Vehicle related identifiers and numbers
4.1 General
The Vehicle ID is assigned uniquely by the system designer to the vehicle. Usually it refers to the vehicle ID
containing the number given inside of the main computer or the number is coded by a fixed connector at the
main computer (see Figure 1: x).
The Body ID assigned by the system designer refers to the body ID containing the readable identification on
the vehicle body. Usual this text is printed on the vehicle body (see Figure 1: y).
The Radio ID assigned by the system designer refers to the radio ID containing the textual radio address of
the bus. This address is necessary for selective calls to this bus (see Figure 1: z).

Figure 1 — Vehicle related identifiers and numbers

4.2 Vehicle operation identifiers and numbers
The Garage ID assigned by the system designer refers to the garage ID object containing the textual
description of the depot or garage, where a vehicle is going to be parked during the night (see Figure 2).
The Block ID assigned by the system designer indicates the work of a vehicle from the time it leaves a parking
point (depot, garage) after parking until its next return to park at a parking point. Any subsequent departure
from a parking point after parking marks the start of a new block. A block should consist of one or several lines
(see Figure 2). The Block ID refers to the Block ID object containing the textual description of the block.
The Line ID assigned by the system designer refers to the Line ID object containing the textual or numerical
name of the line, which the public knows it by. A line should consist of a single route or a group of routes.

Key
Bz = Block z
Lx = Line x
Gi = Garage i
Figure 2 - Non-closed and closed block
A route is an ordered list of points defining one single path through the road (or rail) network. Stop points,
timing points and points of other types should be used to define this path uniquely. The route number is
related to a line (see Figure 3).
The Stop Point ID assigned by the system designer refers to the Stop Point ID object representing uniquely a
stop point within a transportation network (see Figure 3).
The Destination Number is the reference to the route destination. The number can differ from Stop Point ID
(see Figure 3).
The number of running in route representation is the Running Stop Point Number within a route (see Figure 3).
Key
L Line i
i
D Destination number n
n
R Route number x in Line i
x
SP = Stop Point Identifier y
y
N = running Stop Point Number z in the route
z
Figure 3 - Definition of a line
The Journey Number refers to a journey (between one terminus to another terminus) related to a given time or
time table (see Figure 4).
Key
R = route number
i
J = journey number
i
t = time
1 Departure
2 Terminus
Figure 4 - Definition of a journey
The Route Destination ID identifies a unique route and line. With this identifier the path and the rail track of
this line/route is defined for a vehicle. For example, this is used for the controlling of rail switches in the track
(see Figure 5).
Key
L = Line ID x
x
R = Route number I
i
D = Destination number
j
RD = Route destination ID
n
Figure 5 - Description of the use of Route Destination ID
4.3 Fare terms and related identifiers and numbers
The Route Segment Number indicates a set of consecutive links on a given route and is unique for a fare
zone (see Figure 6).
The fare zone indicates the current Fare Zone Number (see Figure 6).
The Previous Fare Zone Number indicates the number of the last/previous crossed fare zone (see Table 1).
The Previous Route Segment Number is the number of the last/previous crossed route segment (see Table 1).

Key
G = Garage i
i
L = Line j
j
Z = Fare zone n
n
RS = Route segment x
x
P = Vehicle position z
z
Figure 6 - Fare terms and related identifiers and numbers
Table 1 - Contents of the objects at the different vehicle positions
Positions P P P P
1 2 3 4
Fare zone Z Z Z Z
1 1 2 2
Route segment RS RS RS RS
1 2 1 2
Previous fare zone - - Z Z
1 1
Previous route segment - RS RS RS
1 2 1
NOTE In this document, a Fare Stage Number is a stop point on a route beyond which an increment in the fare value
occurs.
5 Requirements
5.1 Hardware preferences
There is a WorldFip convention to characterise standard physical device profiles that contain specific
applications and virtual devices, but this is beyond the present scope of this part of the standard. The aim here
is to define the physical layer and data object dictionary to enable the interoperability of physical devices
(Stations) on a vehicle WorldFip LAN. This specification deals essentially with the Transport Process Data
Units (TPDU) which is elsewhere referred to as Exchange Blocks (Annex A). The Applications Process Data
Units (APDU) also referred to in Annex A as Function Blocks, are not hereafter defined even though they
contribute to the Transport Process Data Units.
5.2 Devices in a complex network
The following illustrates the possible devices in a complex network.

Figure 7 - Devices in a complex network

5.3 Station numbers
Station numbers are given in Table 2.
Table 2 — Station numbers
Number Station
00H Test and Maintenance Device
01H Master On-Board Processor
02H Spare
03H Spare
04H Electronic Ticket Machine
05H Drivers Console
06H Badge Reader
07H Tag/Beacon Reader
08H Short Range Communications
09H Radio Control Unit
0AH Data Modem
0BH On-Board Display 1
OCH On-Board Display 2
ODH On-Board Display 3
0EH On-Board Display 4
0FH External Sign (Front)
10H External Sign (Rear)
11H External Sign (Side/Kerb)
12H GPS
13H Ticket Canceller
14H Ticket Canceller
15H Ticket Canceller
16H Ticket Canceller
17H Ticket Printer
18H Ticket Printer
19H Vehicle Identity
1AH Voice Announcer/Public Address Audio Unit
1BH Passenger Counter
1CH Passenger Counter
1DH Passenger Counter
1EH Passenger Counter
1FH Load Measurement
20H NOT AVAILABLE
21H Digital I/O –Vehicles Sensors (Doors etc.)
22H Gateway to Ancient Data Bus
23H Gateway to Manufacturer's Data Bus
24H Bus Lane Enforcement Camera

5.4 Bus arbiter modes
The applications can run with different bus arbiter modes that are defined as follows.
Mode Function
Test Out of service network testing or configuration for network
management using a Test and Maintenance Device which
assumes master bus arbiter when attached to the network
Service Normal operation is for the master bus arbiter to provide for
full service functions including clock
Fallback service Sub-master for reduced service functionality if master fails.
5.5 Physical layer
5.5.1 General
The definitions given in EN 13149-1 and EN 13149-2 shall be used in WorldFIP networks for devices
compliant to this application.
5.5.2 Bit rates.
See EN 13149-1.
5.5.3 Bus connector
See EN 13149-2.
5.5.4 Bus cable
See EN 13149-2.
5.6 Data modelling
5.6.1 General
This part explains the terms that are used in the later tables to characterise the individual data units.
INDEX – A four digit hexadecimal number assigned by system management services for addressing and
these can be related to the station address.
TITLE – A short meaningful description.
FUNCTION – A more complete description of the purpose and function. When the data is of a complex and
structured then special values are inserted in the Data Tables.
NAME – A meaningful abbreviation of the title directly related to the index and assigned by the programmer to
simplify coding.
TPDU TYPE – Transport Process Data Unit Types are.
Periodic Aperiodic
Variables Variables
Messages – Acknowledged Messages – Acknowledged
Messages – Unacknowledged Messages – Unacknowledged
DATA TYPE - Transport Process Data Units should use a standardized structure and can be in two forms:
Simple or Structured.
Simple Structured
Boolean Structure of simple types
Integers(two’s complement notation) Structure of structures
Bit Strings(32 Bytes Max) Tables
Byte Strings (126 Bytes Max) Table of Tables
Visible Strings Table of structures
General Time (14 Ch –YYYY/MM/DD/HH/mm/SS) Lists
4 Byte simple precision floating point ASCII text
8 Byte double precision floating point
ASCII text
LENGTH - Micro FIP supports units of 8 Bytes in multiples up to 128 Bytes. FullFIP supports units of any
length up to 256 Bytes.
PRODUCER (P) – Station producing a PDU (See Annex B)
CONSUMER (C) – Station consuming a PDU (See Annex B). Where this is not specifically defined it is
presumed that the bus arbiter and other devices may consume this data.
DYNAMIC REFRESHMENT – Periodicity that an application refreshes the data.
BUS ARBITER MODE – Some data may be produced for either Test mode, Service mode or both. Fallback
mode is partial functioning of the network if the main bus arbiter fails.
APPLICATION RESPONSE – There may be a need to define the response time of an application in a device
to an event being produced by another device i.e. a doors closed event may trigger a process that causes
information displays to update with 1 s.
DATA VALUE – The detailed construction, value and units of measurement defined for each octet in the PDU.
5.6.2 Text structure
Texts can be stored (and transferred) in two different formats: plain text and XML formatted text.
5.6.3 Plain text
This format will be used to store and transfer plain text without any specific control characters. It is usual to
control old style displays or to store the names of stations.
5.6.4 XML formatted text
The standard permit XML formatted text. The content is considered as user defined.
5.7 Object dictionary
NOTE The current dictionary does not comprehensively define the entire list of objects for the foregoing networks,
but merely a simple network as Annex B.
5.7.1 Overview of object dictionary entries
Identifiers are in accordance with the SM-MPS level of the WorldFIP standard EN 61158:
 10xy - Identification variable
 14xy - Presence variable
 3000 to 7FFF – Free allocation
 9002 – List of presence
 9003 – Synchronisation of Bus Arbiter
5.7.2 Detailed Specification of Process Data Units
The following tables define each data PDU in the order of ascending Index:
5.7.2.1 Index – 10xy – Generalised Equipment Identification Variable
Index 10xy
Title Generalised Equipment Identification Variable
Function This object allows the Station xy to identify itself to the
Name Station xy_IDENT
TPDU Type periodic variable
Periodicity 900m-seconds
Data Type Structured text –ASCII
Length(Bytes) <=126 byte
Dynamic refreshment 50 milliseconds
Bus Arbiter Mode Service and test
Application response Non applicable

Data Value Comment
Octet Description Value (Hex)
From To Invalid
1 Identification 50 50
2 Length 01 7D 00
3 Start of manufacturer 80 80 00
4 Length of manufacturer field 03 03
5-7 Field for manufacture 00 FF
8 Start of model 81 81
9 Length of model field 06 06
10-15 model field 00 FF
16 Start of revision field 82 82
17 Length of revision field 01 01
18 Revision number 00 FF
19 Start of tag/name field 83 83
20 TagName Length 0E 0E
21-25 Boot software version 00 FF
26-30 Application Software 00 FF
31-35 Config Data version 00 FF
36 Start of field 84 84
37 Length 01 01
38 SM_MPS conformity 10 10
39 Start of field 85 85 Refer to
WorldFIP FDM
40 Length
software
41 SMS conformity
reference
43 Start of field 86 86
manual for
information
44 Length
45 MPS, MMS, DLL
46 Physical conformity
47 Start of Free field 8A 8A
48 Length
49-126 Free for manufacturer
5.7.2.2 Index 14xy – Generalised Presence Variable
Index 14xy
Title Generalised Presence Variable for station xy
Function Identification of a WorldFIP Node to the Bus Arbiter
Name xy_PRES
TPDU Type Periodic Variable
Periodicity 900 milliseconds
Data Type Structured
Length(Bytes) 5
Dynamic refreshment 50 milliseconds
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1 Presence Identifier 80 80 Hexadecimal
2 Presence length 03 03 Hexadecimal
3 Ident Variable length 01 7F Hexadecimal
4 Reserved 00 00 Hexadecimal
5 Station Status  Bits 0-3 Bus Arbiter
Priority
Bit 4 Bus Arbiter not
supported
Bit 5 Bus Arbiter not
Eligible
Bit 6 Bus Arbiter Idle
Bit 7 Bus Arbiter Active.
5.7.2.3 Index 3200_Tester Visualisation
Index 3200
Title Tester visualisation
Function Periodic Variable used by Test & Maintenance Device to access
bus when the device is connected to the network (For diagnostics
or configuration).
Name TST_VISU
TPDU Type Periodic
Periodicity 50 milliseconds
Data Type Structured
Length(Bytes) 2
Dynamic refreshment N/A
Bus Arbiter Mode Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-2 Unspecified 0100 0100
5.7.2.4 Index 3300 – Change Calibration Factor
Index 3300
Title Change Calibration Factor
Function Enables the input or change of the value of the Odometer
Calibration Factor held in the AVL unit. The subsequent odometer
readings are thereby changed from a count to a distance in
metres.
Name CHANGE_CAL
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 2
Dynamic refreshment 100 milliseconds
Bus Arbiter Mode Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
From To Invalid
1-2 Beta Factor 0100 0800 Less Beta = Decimal value
than divided by 512
0100 or
greater
than
5.7.2.5 Index 3400 – Change Time
Index 3400
Title Change Time
Function Enables the input or change of the value of the Date and time
held in the AVL unit (Test & maintenance mode)
Name AVLU_TIME
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 8
Dynamic refreshment 1 second
Bus Arbiter Mode Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1 Year (YY) 00 99 Decimal
2 Month (MM) 1 12 Decimal
3 Day (DD) 1 31 Decimal
4 Hour (HH) 0 23 Decimal
5 Minute (MM) 0 59 Decimal
6 Second (SS) 0 59 Decimal
7 Hundredth second 0 99 Decimal
8 Day number in week 1 7 Decimal
5.7.2.6 Index 3F07 – Master Time
Index 3F07
Title Time
Function Time from master clock (Full Service & Test Modes)
Name TIME
Object PDU Type Periodic Variable
Periodicity 50 milliseconds
Data Type Structured
Length(Bytes) 14
Dynamic refreshment N/A
Bus Arbiter Mode Service & Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-2 Year(YYYY) 1997 2097 Decimal
3 Month 1 12 Decimal
4 Day (DD) 1 31 Decimal
5 Day of week 1 7 Decimal
6 Week of year 1 53 Decimal
7 Day of Year 1 366 Decimal
8 Hour (HH) 0 23 Decimal
9 Minute (MM) 0 59 Decimal
10 Second 0 59 Decimal
11 Hundredth second 0 99 Decimal
12-14 Reserved 0  Decimal
5.7.2.7 Index 400A – Radio ID
Index 400A
Title Radio ID
Function Radio Identity from a radio modem (Full Service & Test Modes)
Name RADIO_ID
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 3
Dynamic refreshment N/A
Bus Arbiter Mode Service & Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value)
From To Invalid
71 000 127 Decimal
2-3 Radio Identity 0000 9999 Decimal

5.7.2.8 Index 410A –Line ID
Index 410A
Title Line ID
Function Vehicle sign on data consisting of the logical and commercial Line
number. These are related together because some system
elements cannot deal with ASCII. but the allocation must be
consistent for the whole VCMS network
Name -LINE_ID
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 8
Dynamic refreshment N/A
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-3 Logical route number 001 999 0 Decimal
4-8 Route number 00001 ZZZZZ 0 ASCII
5.7.2.9 Index 420A – Operating Number
Index 420A
Title Operating number
Function Vehicle sign on data consisting of the Operating number that
relates the driver’s duty roster and the vehicle block id
Name OPER_NUMBER
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 3
Dynamic refreshment N/A
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-3 Operating number 001 999 0 Decimal
5.7.2.10 Index 430A – Journey Number
Index 430A
Title Journey Number
Function Vehicle sign on data consisting of the Journey Number.
Name JOURNEY_NUM
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 3
Application Access Read
Dynamic refreshment N/A
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-3 Trip number 001 999 0 Decimal
5.7.2.11 Index 440A – Destination Number
Index 440A
Title Destination number
Function Vehicle sign on data consisting of the destination numbers and
these are unique for a line
Name DEST_NUM
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 2
Dynamic refreshment N/A
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-2 Destination number 01 99 0 Decimal

5.7.2.12 Index 450A – Garage ID
Index 450A
Title Garage ID
Function Vehicle sign on data from the radio modem consisting of the
garage number.
Name GAR_ID
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 2
Application Access Read
Dynamic refreshment N/A
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-2 Garage number 01 127 0 Decimal

5.7.2.13 Index 460A – Fare Stage Number
Index 460A
Title Fare Stage Number
Function Sign on data consisting of a fare stage pertaining to the Line
Fare Stage Number is a stop point on a route beyond which an
increment in the fare value occurs

Name FARE_STAGE
Object PDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 3
Dynamic refreshment N/A
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-3 Fare Stage 001 999 0 Decimal
5.7.2.14 Index 480A - Traffic Light Priority Request
Index 480A
Title Traffic Light Priority Request
Function VCMS originating data for the Traffic Light Priority Request
Name TLP_REQUEST
Object PDU Type Periodic Variable
Periodicity 50mSec
Data Type Structured
Length(Bytes) 2
Dynamic refreshment 50 milliseconds
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-2 Priority level 20 26 ASCII
5.7.2.15 Index 4907 Calibrated Location
Index 4907
Title Location with calibrated odometer counter
Function Beacon identity plus calibrated Odometer value in metres.
Odometer resets to 0000 when Beacon IDchanges.
Name LOCN_DATA
Object PDU Type Periodic variable
Periodicity 50milli-seconds
Data Type Structured
Length(Bytes) 8 Bytes
Dynamic refreshment 50 milliseconds
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
st
1-2 Beacon ID 0000 9F9F <0000 1 Byte field 0-9BCD
nd
>9F9F 2 Byte field 0-Fhex
3rd Byte field 0-9 BCD
4th Byte field 0-FHex
3-4 Odometers 0000 9999 Decimal
5-8 Spare
5.7.2.16 Index 4D07 – Display Odometer Calibration Factor Number
Index 4D07
Title Display Odometer Calibration Factor
Function Displays the odometer Calibration Factor Number held in the
AVL Unit on the Test and Maintenance Device (Test Mode)
Name DIS_ODO_CAL
Object PDU Type Periodic Variable
Periodicity 50mSec
Data Type Structured
Length(Bytes) 4
Dynamic refreshment 100 milliseconds
Bus Arbiter Mode Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
From To Invalid
1-4 Beta Factor 0100 0800 Hexadecimal

5.7.2.17 Index 4E07 - Display AVL Software Release
Index 4E07
Title Display AVL Software Release
Function Displays the Software Release held in the AVL Unit on the
Test & Maintenance Device (Test Mode)
Name DIS_RELEASE
Object PDU Type Periodic Variable
Periodicity 50mSec
Data Type Structured
Length(Bytes) 5
Dynamic refreshment 100 milliseconds
Bus Arbiter Mode Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value
From To Invalid
1-5 Software 00.00 ZZZ.ZZ ASCII -Alpha-numeric
release/version
5.7.2.18 Index 4F07 – Uncalibrated Location
Index 4F07
Title Location with uncalibrated odometer counter
Function Current vehicle location consisting of beacon and uncalibrated
odometer value primarily for bus lane enforcement camera.
Odometer resets to 0000 when Beacon ID changes
Name LOCN_COUNT
TPDU Type Periodic Variable
Periodicity 50 milliseconds
Data Type Structured
Length(Bytes) 8 Bytes
Dynamic refreshment 50 milliseconds
Bus Arbiter Mode Service & Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
From To Invalid
st
1-2 Beacon ID 0000 9F9F <00>9F9F 1 Byte Field 0-9 BCD
nd
2 Byte field 0-F Hex 3rd
Byte Field 0-9 BCD 4th
Byte field 0-F Hex
3-4 Odo Count 0000 9999 Decimal
5-8 Spare 00 FF
5.7.2.19 Index 5009 Driver’s Radio Control Unit Keyboard Command
Index 5009
Title Drivers radio control unit keyboard command
Function Control head keyboard command.
Name KEY_PRESS
TPDU Type Periodic Variable
Periodicity 50mSec
Data Type Structured
Length(Bytes) 120
Dynamic refreshment 100 milliseconds
Bus Arbiter Mode Service & Test
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
From To Invalid
1 Classification 00 00 00Hex
=No command
2-120 Spare no command)  No command mode(If
Octet 1=00)
1 Classification 01 01 01Hex= Buscommand
mode
2 Message Sequence 01 FF 00 Incremented each time
Number the console writes a
command. Defaulted to
zero before the first key
is pressed. Used by the
consumer to recognise a
new command as
opposed to a re-read of
an old command within
the refreshment period.
3 Reserved 00
4 Number of Messages 00 FF
5-120 Key Mapping Data 00 FF User application defined
5.7.2.20 Index 510A – Driver’s Radio Control Unit Display Update
Index 510A
Title Driver’s Radio Control Unit Display Update
Function Text, symbol and indicator control and information
Name CON_DISP_UPD
TPDU Type Periodic Variable
Periodicity 50 milliseconds
Data Type Structured
Length(Bytes) 120
Dynamic refreshment 50 milliseconds
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
From To Invalid
1 Classification 00 00 00Hex
=No update
2-120 Spare (no update)  No update mode

1 Classification 01 01 01Hex = Bus update
2 Radio or other Producer 00 FF 00= Radio No status. 01
Device status = Radio ok
02 = Radio registered
03 = Data being sent
04 = Data confirmed sent
FF = radio fail.
Other values are user
defined and may be used
for indications (LED’s)
3 Message Sequence 01 FF 00 Incremented each time
Number the producer device
writes a command.
Defaulted to zero before
the first update is sent.
Used by the console to
recognise a new
command as opposed to
a re-read of an old
command within the
refreshment period.
4 Number of messages 00 FF
5 Character control 00 FF 01=Steady
02=Flashing
>03= User defined
6-120 Display Text or symbols 00 FF User defined
5.7.2.21 Index 5209 – Radio ID
Index 5209
Title Radio ID
Function Consists of radio prefix and radio address.
Name RADIO_ID
TPDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 120
Dynamic refreshment 50 milliseconds
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
From To Invalid
1 Classification 00 FF Hexadecimal 00
=No personality
2-120 Spare (no command)  No personality Mode

1 Classification 00 FF 01 = MPT1327 Radio
address
2 Radio prefix 00 7F Hexadecimal (MPT1327
Radio Address mode).
3-4 Radio Address 00 1FFF Hexadecimal (MPT1327
Radio Address mode).
5-120 Spare
5.7.2.22 Index 5307- Acknowledge Data Transfer
Index 5307
Title Acknowledge Data Transfer
Function Confirmation that internal signs status data has been transferred
by short range communications to the garage work station
terminal
Name TRANSFER_GWS
TPDU Type Aperiodic Variable
Periodicity
Data Type Structured
Length(Bytes) 1
Dynamic refreshment N/A
Bus Arbiter Mode Service
Application response Less than 10 milliseconds

Data Value Comment
Octet Description Value (Hex)
From To Invalid
1 Transfer Result 0 1 0 = Not ack
1 = Ack
5.7.2.23 Index 550B – Information System Master Unit Status
Index 550B
Title Information Systems Master Unit Status
Function Report of the status of information master unit from the vehicle via
th h t i ti t th k t ti
Name SIGNS_STATUS
TPDU Type Periodic Variable
Periodicity 25mSec
Data Type Stru
...