SIST-TS CEN/TS 13149-6:2006

SLOVENSKI STANDARD
SIST-TS CEN/TS 13149-6:2006
01-april-2006
-DYQLSUHYR]±6LVWHPL]DþDVRYQRUD]SRUHMDQMHLQQDG]RUFHVWQLKYR]LO±GHO
9VHELQDVSRURþLO&$1
Public transport - Road vehicle scheduling and control systems - Part 6: CAN message
content
Öffentlicher Verkehr - Planungs- und Steuerungssysteme für Straßenfahrzeuge - Teil 6:
CAN Nachrichteninhalt
Transports publics - Systemes d'ordonnancement et de contrôle des véhicules routiers -
Partie 6: Contenu de messages CAN
Ta slovenski standard je istoveten z: CEN/TS 13149-6:2005
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
SIST-TS CEN/TS 13149-6:2006 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TS CEN/TS 13149-6:2006

---------------------- Page: 2 ----------------------

SIST-TS CEN/TS 13149-6:2006
TECHNICAL SPECIFICATION
CEN/TS 13149-6
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
August 2005
ICS 45.060.01; 35.240.60; 43.080.20

English Version
Public transport - Road vehicle scheduling and control systems -
Part 6: CAN message content
Transports publics - Systèmes d'ordonnancement et de Straßentransport- und Verkehrstelematik - Planungs- und
contrôle des véhicules routiers - Partie 6: Contenu de Steuerungssysteme für Straßenfahrzeuge - Teil 6: CAN
messages CAN Nachrichteninhalt
This Technical Specification (CEN/TS) was approved by CEN on 27 June 2004 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, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, 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
© 2005 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 13149-6:2005: E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
Contents
page
Foreword .4
Introduction.5
1 Scope.6
2 Normative references.6
3 Terms and definitions .7
3.1 Identifiers and numbers .7
4 Abbreviations.12
5 Hardware preferences.14
5.1 General.14
5.2 Physical layer .14
6 Data modelling.14
6.1 General.14
6.2 Large data .14
6.3 Text structure.14
7 Virtual device profiles .15
7.1 General.15
7.2 Main on-board computer.15
7.3 Identification .18
7.4 Passenger information.18
7.5 Ticket canceller.20
7.6 Ticket printer.21
7.7 Ticket/card reader/validator .22
7.8 Acoustic announcer .22
7.9 Acoustic control manager .22
7.10 Train bus gateway .23
7.11 Vehicle gateway .23
7.12 Vehicle driver indicator .24
7.13 Tachograph .25
7.14 Data radio communication controller (DRCC).25
7.15 Voice radio communication controller (VRCC).25
7.16 Dedicated Short Range Communication (DSRC) device .26
7.17 Geographical positioning device .26
7.18 Time fixing device.27
7.19 Driver’s console display .27
7.20 Driver’s console keyboard.27
7.21 Passenger counter.28
7.22 Passenger counting manager.28
7.23 Diagnostics device.29
7.24 Generic I/O device.30
7.25 Power supply .30
7.26 Short range command radio (SRCR) device.30
8 Error handling.31
8.1 General.31
8.2 Principle.31
8.3 Error behaviour.31
8.4 Additional error codes.31
9 Predefinitions.32
2

---------------------- Page: 4 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
9.1 Predefined communication objects.32
9.2 Pre-defined configurations.34
9.3 Pre-defined PDOs .35
9.4 Operator-specific configuration.36
10 Object dictionary overview .37
11 Detailed specification of object entries .38
11.1 Introduction.38
11.2 Complex data type definition.38
11.3 Objects related to the physical device.39
11.4 Object 6001 : Virtual device events.40
h
11.5 Object 6002 : Main onboard computer events .44
h
11.6 Objects provided by main on-board computer .46
11.7 Objects provided by identification device.71
11.8 Objects provided to passenger information device .75

11.9 Objects provided by ticket canceller .84
11.10 Objects provided by ticket printer.84
11.11 Objects provided by ticket/card reader/validator .84
11.12 Objects provided by acoustic announcer .84
11.13 Objects provided by acoustic control manager .84
11.14 Objects provided by train bus gateway .84
11.15 Objects provided by vehicle gateway.85
11.16 Objects provided by vehicle driver information.96
11.17 Objects provided by tachograph .96
11.18 Objects provided by DRCC.103
11.19 Objects provided by VRCC.103
11.20 Objects provided by DSRC.103
11.21 Objects provided by geographical positioning device .103
11.22 Objects provided by time fixing device.107
11.23 Objects provided by driver’s console display .110
11.24 Objects provided by driver’s console keyboard.110
11.25 Objects provided by passenger counter.111
11.26 Objects provided by passenger counting manager .111
11.27 Objects provided by diagnostics device.114
11.28 Objects provided by generic I/O device .121
11.29 Objects provided by SRCR.124
Bibliography.126

3

---------------------- Page: 5 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
Foreword
This Technical Specification (CEN/TS 13149-6:2005) has been prepared by Technical Committee CEN/TC 278
"Road Transport and Traffic Telematics", the secretariat of which is held by NEN.
Annex A is informative.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to announce this CEN Technical Specification: Austria, Belgium, Cyprus, Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and
United Kingdom.
4

---------------------- Page: 6 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
Introduction
This Technical Specification is part 6 of EN 13149, which gives rules for on-board data transmission systems.
This part 6 together with part 4 and part 5 describes a complete solution independent from part 1, part 2 and part 3.
This document uses terms which are already used in other standards e.g. ENV 12896:1997 “Public
transport - Reference data model”, when applicable.
5

---------------------- Page: 7 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)

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 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.
This 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 4 of this European Standard specifies the CANopen-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 5 of this European Standard specifies in detail the connectors and the connector pin assignment and the
cabling.
Part 6 (this document), which will be published as a Technical Specification specifies in detail the application
profiles for the virtual devices in public transport.
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 13149-4, Public transport - Road vehicle scheduling and control systems - Part 4: General application rules
for CANopen transmission buses.
EN 13149-5, Public transport - Road vehicle scheduling and control systems - Part 5: CANopen cabling
specifications.
EN 50325-4, Industrial communication subsystem based on ISO 11898 (CAN) for controller-device interfaces –
Part 4: CANopen
ENV 12896, Road transport and traffic telematics - Public transport - Reference data model.
ISO 11898-1, Road vehicles - Controller area network (CAN) – Part 1: Data link layer and physical signalling.
ISO 11992-3, Road vehicles - Interchange of digital information on electrical connections between towing and
towed vehicles - Part 3: Application layer for equipment other than braking and running gear.
ISO 16844-7, Road vehicles - Tachograph systems - Part 7: Parameters.
ISO/IEC 646, Information technology - ISO 7-bit coded character set for information interchange.
6

---------------------- Page: 8 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
ISO/IEC 8859-1, Information technology - 8-bit single-byte coded graphic character sets - Part 1: Latin alphabet
No. 1.
ISO/IEC 8859-2, Information technology - 8-bit single-byte coded graphic character sets - Part 2: Latin alphabet
No. 2.
ISO/IEC 8859-15, Information technology - 8-bit single-byte coded graphic character sets - Part 15: Latin
alphabet No. 9.

3 Terms and definitions
For the purposes of this Technical Specification, the terms and definitions given in ENV 12896 apply.
3.1 Identifiers and numbers
3.1.1 Vehicle related identifiers and numbers
The vehicle ID is assigned uniquely by the system designer to the vehicle. Usually it refers to the vehicle ID text
object (611C ) containing the number given inside of the main computer or the number is coded by a fixed
h
connector at the main computer (see Figure 1: x).
The body ID assigned by the system designer refers to the body ID text object (611D ) containing the readable
h
identification on the vehicle body. Usually 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 text object (611E ) containing the textual radio
h
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
3.1.2 Vehicle operation identifiers and numbers
The garage ID assigned by the system designer refers to the garage ID text object (611F ) containing the textual
h
description of the depot or garage, where a vehicle is going to be parked during the night (see Figure 2).
7

---------------------- Page: 9 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
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 text object (6197 ) containing the textual description of the block.
h
The line ID assigned by the system designer refers to the line ID text object (6196 ) containing the textual or
h
numerical name of the line, which is known from the public by. A line should consist of a single route or a group of
routes.

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 text object (6120 ) representing
h
uniquely a stop point within a transportation network (see Figure 3).
The destination number is the reference to the route destination. The number may 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).

8

---------------------- Page: 10 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)

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).

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)
9

---------------------- Page: 11 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)

Figure 5 — Description of the use of Route Destination ID
3.1.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 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).
10

---------------------- Page: 12 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)

Figure 6 — Fare terms and related identifiers and numbers
Table 1 — Contents of the objects at the different vehicle positions p
x
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

11

---------------------- Page: 13 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
4 Abbreviations
4.1
AAS
Acoustic Announcement System
System that controls the acoustic announcements on a vehicle.
4.2
CAN
Controller Area Network
Data link layer protocol for serial communication as specified in ISO 11898-1.
4.3
CiA
CAN in Automation
International users and manufacturers group promoting CAN.
4.4
COB
Communication Object
Data transportation unit in a CAN network mapped to one or more CAN frames.
4.5
COB-ID
COB Identifier
Identifies a COB uniquely in a network and determines the priory of that COB in the network.
4.6
DRCC
Data Radio Communication Control
Controls data radio transmission between vehicle and central station.
4.7
DSRC
Dedicated Short Range Communication
Controls radio or infrared shot distance communicator.
4.8
GIF
Graphics Interchange Format
The data stream-oriented file format maintained by CompuServe, defines the transmission protocol of bitmap data.
4.9
HMI
Human Machine Interface
Device providing input and/or output capability for human users.
4.10
IAM
IBIS Application Manager
Main on-board computer controlling the IBIS system.
4.11
IBIS
Integrated Board information system
Integrated on-vehicle information system for passengers and drivers.
12

---------------------- Page: 14 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
4.12
JPEG
Joint Photographic Experts Group
The best known standard from JPEG is ISO 10918-1, which is the first of the multi-part set of standards for still
image compression.
4.13
PDO
Process Data Object
Unconfirmed COB containing process data and mapped to one CAN data frame.
4.14
rffu
Reserved for future use
Place holder for future definitions
4.15
RPDO
Receive PDO
PDO received by one node or several nodes depending on the configuration.
4.16
SDO
Service Data Object (SDO)
Confirmed and Optionally segmented COB providing peer-to-peer communication with access to the Object
Dictionary of a device.
4.17
SRCR
Short Range Command Radio
SRCR is a radio short distance command communication link
4.18
TPDO
Transmit PDO
PDO transmitted by one node.
4.19
UTC
Universal Time Coordinated (UTC)
International time base previously known as GMT.
4.20
VRCC
Voice Radio Communication Control
Controls voice radio transmission between vehicle and central station.
4.21
XML
Extensible Markup Language
Formatting language for text (http://www.w3.org/TR/2000/WD-xml-2e-20000814).
13

---------------------- Page: 15 ----------------------

SIST-TS CEN/TS 13149-6:2006
CEN/TS 13149-6:2005 (E)
5 Hardware preferences
5.1 General
This clause defines the hardware preferences for CANopen network implementations.
5.2 Physical layer
The definitions given in EN 13149-4 and EN 13149-5 shall be used in CANopen networks for devices compliant to
this application profile.
5.2.1 Bit rates
See EN 13149-4.
5.2.2 Bus connector
See EN 13149-5 and CiA DR 303-1:2002 “Cabling and connector pin assignment (version 1.1)”.
5.2.3 Bus cable
See EN 13149-5 and CiA DR 303-1:2002 “Cabling and connector pin assignment (version 1.1)”.
6 Data modelling
6.1 General
Application objects should use a standardized structure. Different application objects use the following data
definitions. Most of the data may be transmitted within a single PDO. In case of an object with a length of more than
8 byte, SDO communication is used.
6.2 Large data
The transfer of texts and other data (e.g. bitmaps) longer than 8 byte requires a segmented transfer performed by
SDO. As the transporting of the SDOs is done through a peer-to-peer connection, it is not possible to supply all
devices with the text simultaneously.
The following procedure is determined:
— Texts and other data to be stored may be sent to the equipment at any time using SDO service.
— Each text or data has a system-wide, definite reference number, which is sent within the SDO.
— Devices may also request text and data (by SDO).
— The texts and data may be clearly addressed via the reference number.
— Using a PDO, which contains a reference number the devices (respective indicators) should be requested to
display a text.
6.3 Text structure
...