PSI5 Specification v2.0 06-2011 PDF
PSI5 Specification v2.0 06-2011 PDF
PSI5 Specification v2.0 06-2011 PDF
Technical PSI5
Specification Peripheral Sensor Interface V2.0
SesKion
Contents
1 Introduction 3
1.1 Description ....................................................................................................................................... 3
1.2 PSI5 Main Features ......................................................................................................................... 3
1.3 Scope ............................................................................................................................................... 4
1.4 Legal Information ............................................................................................................................. 4
6 Parameter Specification 35
6.1 General Parameters....................................................................................................................... 35
6.1.1 Absolute Maximum Ratings ................................................................................................. 35
6.1.2 System Parameters ............................................................................................................. 35
8 Interoperability Requirements 56
1 Introduction
1.1 Description
The Peripheral Sensor Interface (PSI5) is an interface for automotive sensor applications. PSI5 is an open
standard based on existing sensor interfaces for peripheral airbag sensors, already proven in millions of
airbag systems. The technical characteristics, the low implementation overhead as well as the attractive cost
make the PSI5 also suitable for many other automotive sensor applications.
Development goal of the PSI5 is a flexible, reliable communication standard for automotive sensor
applications that can be used and implemented free of charge.
The PSI5 development and the publication of this technical specification are responsibly managed by the
PSI5 Steering Committee, formed by the companies Autoliv, Bosch, and Continental.
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
This PSI5 technical specification V2.0 is a joint development of the companies Autoliv, Bosch, Continental,
Analog Devices, CS Group, ELMOS, Freescale, Hella, IHR, Infineon, Seskion, ST, TRW and OnSemi.
Main features of the PSI5 are high speed and high reliability data transfer at lowest possible implementation
overhead and cost. PSI5 covers the requirements of the low-end segment of digital automotive interfaces
and offers a universal and flexible solution for multiple sensor applications. It is characterized by
This updated Version 2.0 contains several new features in terms of Physical and Data Link Layer
parameters in order to enlarge the application range of the PSI5 Interface. Due to backward compatibility
established parameters according to Specification V1.3 are still valid; the alternative implementations are
mainly optional and specifically indicated.
Though, general interface parameters are given within this Basic Specification document, application specific
frameworks and conditions are given in the effective substandards airbag, vehicle dynamics control and
powertrain. Recommended operation modes and system configurations are given therein, as well as
forbidden configurations are excluded.
Please be aware, that not every feature can be combined among one other. Hence it is in responsibility of
the system vendor to evaluate what features are necessary to fulfill the system requirements and assure that
the combination of features is compatible.
1.3 Scope
This document describes the interface according to the ISO/OSI reference model and contains the
corresponding parameter specifications. PSI5 standardizes the low level communication between peripheral
sensors and electronic control units.
The specification may be reproduced or copied, subject to acceptance of the contents of this document.
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
No part of this specification may be modified or translated in any form or by any means without prior written
permission of Autoliv, Bosch, and Continental. With their permission Autoliv, Bosch, and Continental assume
no liability for the modifications or translations made by third parties.
In case Autoliv, Bosch, and Continental permit any of the aforementioned modifications or translations
Autoliv, Bosch, and Continental shall be entitled to use such modifications or translations free of charge for
future versions of the PSI5 protocol and make such future versions available to third parties under the same
terms and conditions as for the PSI5 protocol.
Disclaimer
The specification and all enclosed documents are provided to you "AS IS". You assume total responsibility
and risk for your use of them including the risk of any defects or inaccuracies therein.
Autoliv, Bosch, Continental and the other members of the PSI5 Consortium do not make, and expressly
disclaim, any express or implied warranties of any kind whatsoever, including, without limitation, implied
warranties of merchantability of fitness for a particular purpose, warranties or title or non-infringement.
As far as personal injuries are caused due to the specification or any of the enclosed documents and to the
extent the mandatory laws of the law applicable restrict the limitation of liability in such cases or in other
circumstances as for example liability due to wilful intent, fraudulently concealed defects or breach of
cardinal obligations, the mandatory law applicable shall remain unimpaired.
Indemnification
You shall indemnify and hold harmless Autoliv, Bosch, Continental and all members of the PSI5 consortium,
their affiliates and authorized representatives against any claims, suits or proceedings asserted or
commenced by any third party and arising out of, or relating to, you using the specification or enclosed
documents. This obligation shall include indemnification against all damages, losses, costs and expenses
(including attorneys fees) incurred by the consortium, their affiliates and authorized representatives as a
result of any such claims, suits or proceedings, including any costs or expenses incurred in defending
against any such claims, suits, or proceedings.
By making use of the PSI5 protocol you declare your approval with the above standing terms and conditions.
This document is subject to change without notice.
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Figure 1 shows a possible system setup for peripheral sensors connected to an ECU with PSI5.
Peripheral
Electronic Control Unit
Sensors
Two-Wire
Current Interface
C Transceiver Sensor 1
Interface ASIC
Sensor 2
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Sensor 3 Sensor 4
The sensors are connected to the ECU by just two wires, using the same lines for power supply and data
transmission. The transceiver ASIC provides a pre-regulated voltage to the sensors and reads in the
transmitted sensor data. The example above shows a point-to-point connection for sensor 1 and 2 and two
different bus configurations for sensor 3 and 4, and 5 to 7, respectively.
The different PSI5 operation modes define topology and parameters of the communication between ECU
and sensors such as communication mode, number of data bits, error detection, cycle time, number of time
slots per cycle and bit rate.
Communication Mode:
N of Data Bits
Error Detection
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Cycle Time in s
N of Time Slots per cycle
Bit Rate
Example PSI5-P10P-500/3L:
PSI5 synchronous parallel bus operation, 10 data bits with parity bit, 500s sync cycle time with three time
slots and a standard 125 kbps data rate.
Communication Modes
A Asynchronous Mode
P Synchronous Parallel Bus Mode
U Synchronous Universal Bus Mode
D Synchronous Daisy Chain Bus Mode
V Variable Time Triggered Synchronous Operation Mode
Error Detection
P One Parity Bit
CRC Three Bits Cyclic Redundancy Check
Bit Rate
L 125 kbps
H 189 kbps
Cycle time
tttt cycle time in s (e.g. 500)
or minimum allowed cycle time in s for variable time triggered operation (e.g. 228)
ECU
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
S1
Timing VSS
Diagram
0V
S1 S1 S1 S1 S1
ECU Sensor
The synchronous operation modes work according to the TDMA method (Time Division Multiple Access).
The sensor data transmission is synchronized by the ECU using voltage modulation. Synchronization can
optionally be used for point-to-point configurations and is mandatory for bus modes.
TSync
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
In the PSI5 bus topologies, one or more sensors are connected to the ECU in parallel.
ECU
S1 S2 Sn
TSYNC
Timing V2
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Diagram
Threshold
V1
0V
S1 S2 --- Sn S1 t
Each data transmission period is initiated by a voltage synchronization signal from the ECU to the sensors.
Having received the synchronization signal, each sensor starts transmitting its data with the corresponding
time shift in the assigned time slot.
In a parallel bus configuration, an individual identification of the sensors is required. Alternatively the sensors
can be connected in a Daisy Chain configuration to the ECU. In this configuration the sensors have no
fixed address and can be connected to each position on the bus. During startup, each sensor receives an
individual address and then passes the supply voltage to the following sensor subsequently. The addressing
is realized by bidirectional communication from the ECU to the sensor using a specific sync signal pattern.
After having assigned the individual addresses, the sensors start to transmit data in their corresponding time
slots in the same way as specified in the parallel bus topology.
ECU
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
S1 S2 Sn
V2 Tsyn
Vthreshold
V1
Tslo
0V
S1 S2 Sn S1
PSI5-P describes a bus configuration for synchronous data transmission of one or more sensors. Each
sensor is connected to the ECU by a separate pair of wires (star topology).
In order to provide an interchangeability of different sensor and transceiver components, additional interface
parameters for ECU, sensors, and wiring are specified for this bus mode (see chapter 7.3).
PSI5-U describes a bus configuration for synchronous data transmission of one or more sensors. The
sensors are connected to the ECU in different wiring topologies including splices or pass-through
configurations.
RCE RCS
wire
RE RCE 1 RCS ISink
VE
VCE Sensor
RCS
CE CS 1
RCS
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
RCS
wire
ECU 2 RCS ISink
Sensor
RCS
CS 2
RCS
Sen
wire
3 RCS3 ISink
Sensor
RCS
CS 3
RCS
The wiring and sensors are considered as a black box resulting in a limited interchangeability of sensor
and transceiver components. Interface parameters are given for the ECU and the black box only (see
chapter 7.4).
PSI5-D describes a bus configuration for synchronous data transmission of one or more sensors connected
in a daisy chain configuration. The required addressing of the sensors during start up is specified in
chapter 5.2.2.
RCE RCS
wire
RE RCE RCS ISink
VE VCE Sensor
RCS
CE RDS On CS 1
RCS
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
RCS
wire
ECU RCS ISink
Sensor
RCS
RDS On CS 2
RCS
RCS
wire
RCS ISink Sensor
RCS 3
CS
RCS
In a sensor cluster configuration, one physical sensor contains two or more logical channels. Examples
could be a two channel acceleration sensor or a combined temperature and pressure sensor.
The data transmission of the different channels can be realized by splitting up the data word of each data
frame into two or more blocks or by transmitting the data for the different channels in separate data frames
using time multiplex.
ECU
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Sensor
Ch A Ch B
Cluster
S1
Multiple channel
transmission using S1 Ch A Ch B S1 Ch A Ch B S1 Ch A Ch B ... t
one data word
Sensor cluster / multichannel operation modes can be combined with both asynchronous and synchronous
data transmission and with the different bus configurations.
PSI5 uses two wires for both power supply to the sensors and data transmission. The ECU provides a pre-
regulated voltage to the sensor. Data transmission from the sensor to the ECU is done by current modulation
on the power supply lines. Current oscillations are damped by the ECU.
A "low" level (IS,Low) is represented by the normal (quiescent) current consumption of the sensor(s). A "high"
level (IS,High) is generated by an increased current sink of the sensor (IS,Low + IS). The current modulation is
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
TBit
t
Manchester coding is used for data transmission. A logic "0" is represented by a rising slope and a logic "1"
by a falling slope of the current in the middle of TBit.
The data frames are sent periodically from the sensor to the ECU. A minimum gap time TGap larger than one
maximum bit duration TBit is required between two data frames. Each PSI5 data frame consists of p bits
containing
two start bits (S1 and S2),
one parity bit (P) with even parity or alternatively 3 CRC bits (C0, C1, C2), and
a data region (D0 D[k-1]) with k = 10.. 28 bit.
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
frame duration
S1 S2 D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 P
"0 "0 "1 "1 "1" "0" "0" "1" "1" "1" "1" "0" "1"
IS ,High
Manchester Code
Transmission of 0x1E7
(Status "Sensor Ready) IS ,Low
Figure 14 Example of a data frame with 10 data bits (D0-D9), 2 start bits (S1,S2) and one parity bit (P).
The total length of a PSI5 frame is p = k+3 data bits (in case of frames with parity bit) or p = k+5 data bits (in
case of frames with CRC). Data bits are transmitted LSB first. The parity or CRC check bits cover the bits of
the entire data region. The length of the data region can vary between k = 10 28 bits (with 1-bit
granularity).
Error detection is realized by a single bit even parity (for 10 bit data words) or a three bit CRC
(recommended for longer data words). The generator polynomial of the CRC is g(x)=1+x+x3 with a binary
CRC initialization value 111. The transmitter extends the data bits by three zeros (as MSBs). This
augmented data word shall be fed (LSB first) into the shift registers of the CRC check. Start bits are ignored
in this check. When the last zero of the augmentation is pending on the input adder, the shift registers
contain the CRC checksum. These three check bits shall be transmitted in reverse order (MSB first: C2, C1,
C0).
C0 C1 C2
CRC Calculation input
Scheme data T T T
2 3 3
1*1 + 1*X + 0*X + 1*X =X +X+1
CRC MSB
Data MSB
CRC LSB
Data LSB
Messaging Frame control Status Data Region B Data Region A CRC or parity
Start bits 1, 3 bit
optional optional optional (optional) n = 1024 bit
2 bit
0, 2 bit 0, 1, 2, 3, 4 bit 0, 1 or 2 bit m = 012 bit 1bit granularity
1bit granularity
PSI5 data messages are divided into three separate ranges: a data range for the sensor output signal, a
range for status and error messages and a range for initialization data.
For 10 bit sensors, the decimal values 480 to +480 are used for the sensor output signal. The range 512
to 481 is reserved for the block and data IDs and can be used for transmitting initialization data during
startup of the sensor (see chapter 5.1). The range from +481 to +511 is used for status and error messages.
(*1) Usage for ECU internal purpose possible (e.g. No Data, Manchester Error etc.)
(*2) Reserved for future extensions of this specification, usage not recommended.
3.3.2 Scaling of Data Range (for data words longer than 10 bit)
The sensor output signal range scales with the data word length, whereas status and initialization data
words for frames with a payload data region of more than 10 bits still are sent in 10 bit codes of data region 2
and 3. Hence, during Initialization with the Data range method, the 10 bit codes MSB of the payload region
are always used for signaling as defined in Chapter 5.1. The remaining bits of the payload region (either
A[10]A[23] or an optional Data region B) are free to use.
The following fractions of the Payload Data Region are not affected by signaling range definition:
- Remaining bits above 10 of Data Region A (A[10]...A[23])
- Data Region B (optional)
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
The serial message frame stretches over 18 consecutive PSI5 data messages from the transmitter as shown
below. All 18 frames must be successfully transmitted for the serial value to be received. The messaging bit
M1 of sensor frame No. 8 determines the serial format (12bit data field with 8bit ID or 16bit data field with
4bit ID). In synchronous operation the serial frame, or its constituent messaging bits, respectively, is
assigned to the related time slot of the corresponding PSI5 frame.
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Figure 18 Serial Data Frame generated by the two messaging bits of the sensor data frame (messaging
channel)
The generator polynomial of the 6bit checksum is g(x)=1+x+x4+x6 with a binary initialization value 010101.
The CRC value is derived from the serial messaging contents of sensor frame 7 to 18, the bits are read in to
a newly generated message data word starting with the serial Data bit M0 of sensor frame 7 and ending with
the serial data bit M1 of sensor frame 18. The reading order is illustrated in fig. 19.
For CRC generation the transmitter extends the message data by six zeros. This augmented data word is
fed into the shift registers of the CRC check. When the last zero of the augmentation is pending on the input
adder, the shift registers contain the CRC checksum. These six check bits shall be transmitted MSB first [C5,
C4, ... C0]
Sensor Frame
Frame No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Serial Data (bit M1) 1
0 3
C 5
0 7 0 ID9
serial 11
0 13
0(7-4) 0 15
0 170 ID19
serial 21
0 23
0(3-0) 0
Serial Data (bit M0) 0 2 4 6 8 10 12 14 16 18 20 22
While the sensor to ECU communication is realized by current signals, voltage modulation on the supply
lines is used to communicate with the sensors. The PSI5 sync signal is used for the sensor synchronization
in all synchronous operation modes and also as physical layer for bidirectional communication.
ECU to Sensor communication is performed according to either one of the following two procedures.
1 0 1 1 0 0 1
A logical 1 is represented by the presence of a sync signal, a logical 0 by the absence of a sync signal at
the expected time window of the sync signal period. The voltage for a logical 0 must remain below the 0.5V
limit specified as the sync signal t0 start condition.
This Bit Encoding method is only applicable with a fixed sync signal period.
0 0 0 1 1
A logical 0 is represented by the presence of the regular (short) PSI5 sync signal, a logical 1 by a longer
sync signal (see chapter 6.5)
ECU to Sensor data frames are structured as described below. They are applied in different ways for the bit
coding method in use. The Tooth Gap method is limited to usage of data frame formats 1-3, whereas the
Pulse Width method is applicable with all 4 frames. A combined usage of the frame types 1-3 and frame 4
within one implementation is forbidden in order to ensure safe data recognition. Specific regulations must be
given in the corresponding substandards or specific product specifications.
The frames 1-3 are composed by three start bits, a data field containing the sensor address, function code
and data and a three bit CRC. Sensor response may be sent in data range format within the following two or
three sync periods. Three data field lengths are available, short, long and xlong.
1 1 0 1 0 1 1 1
RC RD1 RD2
Figure 22 Data frame ECU to sensor communication e.g. Tooth Gap method applicable to frame
formats 1-3
The start condition for an ECU to sensor communication consists of either at least five consecutive logical
zeros or at least 31 consecutive logical ones. The sensor responds with the standard sensor to ECU current
communication in its corresponding time slot. Sync Bits (logical 1) are introduced at each fourth bit
position in order to ensure a differentiation between data content and start condition and to enable sensor
synchronization when using the tooth gap method. The data frame length is defined by the content of the
Sensor Adress (SAdr) and the function Codes (FC) as shown in fig. 23. The calculation of the three bit
checksum is given in Ch. 3.2.2
Frame 1 Short
Start SAdr FC CRC Resp
0 1 0 S A0 A1 A2 S F0 F1 F2 S C2 C1 C0 RC RD1 S Synchronisation Bit [1]
Frame 3 XLong
Start SAdr FC RAdr Data CRC Resp
0 1 0 S A0 A1 A2 S F0 F1 F2 S X0-X7 + Sync Bits D0-D7 + Sync Bits C2 C1 S C0 RC RD1 RD2
Data frame 4 is composed by nine start bits, a four bit sensor address field, a 20-bit data field containing
application specific data and a six bit CRC. Stuffing Bits (logical 0) are introduced at each sixth bit
position in order to ensure a differentiation between data content and frame start. Transmission of a correct
ECU to Sensor data frame does not have to be acknowledged in general. However, if required by the
application, the sensor may send a response to the ECU by either transmitting a return code and return data
out of the reserved data range area or via the serial channels messaging bits.
0 1 1 1 0
Sensor
Data
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Figure 24 Data frame ECU to Sensor Communication e.g. Pulse width method with frame format 4
(frame formats 1-3 are also applicable)
C Configuration Bit
[1] Mapping of frames 1-3
[0] all other applications
Frame 4 XXLong
Start SAdr Data CRC
S 1 1 1 1 1 1 1 S A0 A1 A2 C D0 D1 S D2 D7 S D8-D19 + Sync Bits S C0 C1 C2 C3 C4 C5
The generator polynomial of the six bit CRC of frame 4 is g(x)=x6 + x4 +x3 +1 with a binary CRC initialization
value 010101. The transmitter extends the data bits by six zeros (as MSBs). This augmented data word
shall be fed (LSB first) into the shift registers of the CRC check. Start bits and sync bits are ignored in this
check. When the last zero of the augmentation is pending on the input adder, the shift registers contain the
CRC checksum. These six check bits shall be transmitted LSB first [C0, C1 .. C5].
In case the function codes as defined in Ch. 5.2 shall be used in combination with frame 4, they are mapped
as shown below.
1 Configuration Bit
[1] Mapping of frames 1-3
Frame 1 mapped into frame 4
Start SAdr Data CRC
S 1 1 S A0 A1 A2 1 F0 F1 S F2 0 0 0 0 0 S 0 0 0 0 S 0 0 S C0 C5
Start
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Specific application layer implementations are defined in the application substandards or in individual
product specifications. In order to enable global interoperability between PSI5 compatible components and
to avoid potential system malfunction due to erroneous recognition of components, some global definitions
about sensor initialization and bidirectional communication are made in this chapter.
Sensor identification data is sent after each power on or reset. Therefore two different transmission
procedures can be applied:
1) Data range initialization
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Identification data is sent during an initialization procedure before any effective sensor data is sent.
2) Serial channel messaging
For immediate access to measurement data, Identification data is transmitted parallel to sensor data
via serial channel bits M0 and M1. The sensor immediately starts with parallel transmission of
measurement and sensor identification data.
Chapter 5.1.1 defines the Data format of the Data range initialization procedure, further details are given in
the corresponding substandards. The serial channel messaging is fully defined on application level, i.e.
within the specific substandard. Chapter 5.1.2 and 5.1.3 define basic regulations of the Application Layer
that need to be followed by both identification procedures.
The initialization data is transmitted within the range of Payload Data Region 1 using ID and data blocks
out of the reserved data range 3 containing each 16 block identifiers and 4-bit data nibbles.
Block ID 1-16 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0
(0x200 0x20F)
1 0 0 0 0 0 0000 - 1111
Data Nibbles A9 A8 A7 A6 A5 A4 A3 A2 A1 A0
0000 1111
(0x210 0x21F) 1 0 0 0 0 1 0000 - 1111
Initialization ID1 D1 ID2 D2 ID3 D3 ... ... Initialization Sequence Example (k=1)
Hex Value 0x200 0x214 0x201 0x211 0x202 0x21B D1 = 0100 (PSI5 Protocol Revision)
Data Content 0100 0001 1011 D2 = 0001 (Example for number
D3 = 1011 of data nibbles = 27 dec)
If the initialization data exceeds 4x16=64 bit, data can be paged. The ID codes are reused for every 64 bit
page of data to be transmitted. Data pages are not numbered. Mapping of the information contained in
different data pages has to be derived from the chronology of the startup sequence. It is not mandatory to
transmit complete data pages.
At the very beginning of the identification phase a meta information header is transmitted minimum once
indicating the PSI5 version and the method used for identification data transmission. Irrespective of the
applied identification procedure the header data field is sent in status data format (10-Bit value out of Data
range 3).
5.1.3 Vendor ID
Further Details of Initialization Data Structure and Contents are given in the respective Substandards.
*)
the here given Vendor IDs are effective for PSI 5 V2.0 and mandatory for all future applications; in
compliance with PSI5 V1.3 former codes are still valid. That is specifically regarding Autoliv (0100 0000),
Bosch (0001 0000), Continental (1000 0000), Siemens VDO (0010 0000).
In the following basic regulations of data contents are given that need to be followed by all PSI5 applications.
Address to be
pro- Set Sensor Address & Close Bus
grammed RC: o.K. RC: Error
SetAdr 0 0 0 Switch (The FC field
RD1: Address RD1: ErrN
contains the sensor address)
A2 A1 A0
RD_L Sensor 0 1 0 Read nibble or byte from sensor (*) RC: o.K. RC: Error
Address RD1: Data_Lo RD1: ErrN
WR_L 001 .. 110 0 1 1 Write nibble or byte to sensor (*) RD2: Data_Hi (**) RD2: 0000
6 Parameter Specification
All voltage and current values are measured at the sensor's connector pins unless otherwise noted. Values
in brackets denote redundant parameters that can be calculated by other specified values and are for
illustration purposes only. All parameters are valid under all operating conditions including temperature
range and life time.
With PSI5 Specification V2.0 additional physical layer definitions are implemented in order to satisfy
extended application requirements. The affected parameters are:
Detailed information is given within the corresponding paragraphs of the following pages. Not every feature
can be combined among one other. Hence it is in responsibility of the system vendor to evaluate which
feature is necessary to fulfill the system requirements and assure that the combination of features is
compatible. A first basic preselection is done with the two recommended parameter assemblies given below
for Common Mode and Low Power Mode operation. They still contain several options for particular
parameters. Therefore additional selections must be made for specific applications as they are given in the
effective substandards, for example.
Common Mode
N Parameter Symbol Min Typ Max Unit
10* 12.5
11* Sensor trigger threshold (for Vt2 = 3.5V) 1.4 2.0 2.6
VTRIG V
12* Sensor trigger threshold (for Vt2 = 2.5V) 1.2 1.5 1.8
1,2*) To be guaranteed by the ECU at the pins of the sensors under all conditions including dynamic load
conditions in Asynchronous Mode and Parallel Bus Mode.
2,4*) For Common Mode: Low supply voltage can conflict with the maximum sink current with respect to full
functionality within the scope of all given PSI5 parameters. For low voltage operation, reduced sink
current of 26mA maximum and, if possible, additional reduction of quiescent current is
recommended
3,4*) To be guaranteed by the ECU at the output pins of the ECU under all conditions including dynamic
load conditions in Universal Bus Mode and Daisy Chain Bus Mode.
5*) Optional increased supply voltage to overcome additional voltage drops in Universal Bus and Daisy
Chain Bus applications.
6*) The reduced sink current in Low Power Mode affects the functionality and robustness of system
implementations within the full range of all given PSI5 parameters. For low power operation simple
configurations and shorter cable lengths (e.g. in point to point configuration) are recommended and a
specific system validation is required.
7,8*) Vt2 = 2.5V is recommended for new applications compliant with PSI5 V2.0; however, in compliance
with former PSI5 versions Vt2 = 3.5V still is valid.
9,10*) RE = 9.5V is recommended for low voltage applications, when no additional voltage source is
implemented in the ECU; however, in compliance with former PSI5 versions RE = 12.5V still is valid.
11,12*) Referenced to VSS, BASE
13,14*) Parameters denote the sum over all sensors.
14*) Extended current range for higher current consumption e.g in bus or sensor cluster configurations.
15, 16*) ILOW is the (initial) quiescent current of the bus. Over lifetime and temperature, the quiescent current
may vary by +/- 4.0 mA but must not exceed the limits for ILOW . Means for an adaptive current
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
threshold may be required in the transceiver in order to cope with varying quiescent currents,
especially when connected in bus systems. Data loss of the whole system as consequence of an
abrupt quiescent current drift after loss of one sensor connection also needs to be considered.
17-20*) A maximum slope rate of 55mA/s has to be provided by the ECU.
18,20*) Dynamic load condition: The ECU must have the capability to provide the current ILIMIT, dynamic for at
least 10s. For Daisy Chain Bus Mode this current has to be provided for at least 10ms when a sensor
is powered on.
21*) In Daisy Chain Bus Mode the quiescent current limitations apply for a single sensor.
To ensure a proper startup of the system, a maximum startup time is specified. During this time, the ECU
must provide a minimum current to load capacitances in sensors and wires. After this time, the sensor must
sink to quiescent current within the specified tolerance band.
During power on the ECU may reduce the output voltage to limit the current. However, this situation must be
avoided in case of the daisy chain bus. Therefore, in a Daisy Chain Bus the sensor architecture must ensure
that the overall bus current stays below ILIMIT, dynamic.
IS
tolerance band
ILOW
steady state
quiescent current
0
tSET t
0
2* Settling time for quiescent current ILOW tSET, Daisy Chain Bus 10.0 ms
(Daisy Chain Bus)
The sensor must perform an internal reset if the supply voltage drops below a certain threshold for a
specified time. By applying such a voltage drop, the ECU is able to initiate a safe reset of all attached
sensors.
Microcuts might be caused by lose wires or connectors. Microcuts within the specified limits shall not lead to
a malfunction or degraded performance of the sensor.
Normal Operation
VTh , max
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
undefined
VTh, min
IS=0
Reset
0
0.5s 5ms t
The voltage VTh is at the pins of the sensors. In case of microcuts (IS=0) to a maximum duration of 0.5s the
sensor must not perform a reset. If the voltage at the pins of the sensor remains above VTH the sensor must
not perform a reset. If the voltage at the pins of the sensor falls below 3V for more than 5ms the sensor has
to perform a reset.
Different definitions may apply for Universal Bus and Daisy Chain Bus.
IS
Data Frame Data Frame
S
IHigh
IThreshold I
ILo
TBit TGap
t
Purpose of the synchronization signal is to provide a time base for all devices connected to the interface.
The synchronization signal is realized by a positive voltage modulation on the power supply lines. For ECU
to sensor communication bits are encoded in present or missing sync pulses, respectively. Or optional by
generating long and short sync pulses. The sync pulses are defined as shown in Figure 32 and in the table
below.
Vt2
Lower Boundary
VTRIG Trigger
Point
Vt0
VCE Base
0 0 1 1
t1 t0 tTRIG t2 t 3 t 4 t 3 t 4
The synchronization signal start time t0 is defined as a crossing of the Vt0 value. In the Sync Start phase
before this point, a rounding in of the voltage starting from VCE, Base to Vt0 is allowed for a maximum of t1.
During the Sync Slope phase, the voltage rises within given slew rates to a value between the minimum
sync signal voltage Vt2 and the maximum interface voltage VCE, max. After maintaining between these limits
until a minimum of t03 (t13), the voltage decreases in the Sync Discharge phase until having reached the
initial VCE, base value until latest t04. (t14)
1* Base supply voltage (low voltage) VCE, BASE Mean voltage value at ECU I/F 4.4 11.0 V
2 Base supply voltage (standard) VCE, BASE Mean voltage value at ECU I/F 5.7 11.0 V
3* Base supply voltage (increased) VCE, BASE Mean voltage value at ECU I/F 6.7 11.0 V
4* Sync Slope Reference Voltage Vt0 Referenced to VCE, BASE (0.5) V
5* Sync signal sustain voltage Vt2 Referenced to VCE, BASE 2.5 V
3.5
In the sensors, the trigger is detected within the trigger window during the rising slope of the
synchronization signal at the trigger point with the trigger voltage VTRIG and the trigger time tTRIG.
Vt2
Sync Slope
VEMC Window
VTRIG max Trigger Window
Trigger Point
VTRIG
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
tEMC tEMC
VTRIG min
VEMC
Vt0
Vss Base
t1 t0 tTRIG tTRIG tTRIG t2
min nom max
In order to take into account voltage differences at different points of the interface lines, an additional safety
margin for the trigger detection is defined by VEMC and tEMC.
12 Margin for voltage variations of VEMC for Vt2 = 2.5V -0.7 +0.7 V
the signal on the interface line
for Vt2 = 3.5V -0.9 +0.9
13* Sensor trigger threshold VTRIG for Vt2 = 2.5V 1.2 1.5 1.8 V
(Sensor to detect trigger) for Vt2 = 3.5V 1.4 2.0 2.6 V
14* Nominal trigger detection tTRIG @ VTRIG , @ Sensor Pins (2.1) (3.5) (4.9) s
time
15 Margin for timing variations of the tEMC Relative to nominal trigger -2.1 +2.1 s
signal on the interface line window time
16 Tolerance of internal trigger ttol detect 3 s
detection delay at sensor
17* Trigger detection time TTRIG TTRIG = tTRIG + ttol detect + tEMC 0 10 s
Reference for sensor timebase
13*) Referenced to VSS, BASE ;
14*) Referenced to a straight sync signal slope with nominal slew rate
17*) Additional fixed internal delays are possible but have to be considered for the data slot time calculation
This section describes how the timing of a sensor configuration has to be calculated considering all
tolerances. Each single implementation has to assure that sensor frames do not overlap or conflict with a
sync pulse. For different applications different timing considerations are of importance and hence, a
transceiver should not rely on concrete time slots but rather be individually configurable for different time
slots. In general, timing calculation is done for independent sensors at each slot. If more than one slot is
used by the same sensor, or two sensors rely on the same timing base, respectively, slot tolerances can be
considered as dependent and the timing can be tightened.
Recommended operation modes and timings are specified within the effective application specific
substandards.
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
TSync
TSlot1
tSlot N, End
t1ES
TGAP
t1LS t1LE
t1NS tnNS
t1EE
Vss Base
t0 t1NE tnNE
TTRIG TTRIG
tnES : Earliest start of frame n; this is the earliest time when the transceiver or any other sensor on the
bus can expect that the frame no. n begins.
tnNS : Nominal start of frame n; this is the nominal time when the sender (sensor) transmits data
according to its own internal clock. It is the nominal time when the transceiver or any other
sensor on the bus can expect that the frame no. n begins.
tnLS : Latest start of frame n, this is the latest time when the transceiver or any other sensor on the
bus can expect that the frame no. n begins.
E.g. Substandard Vehicle Dynamics Control, Operation Mode PSI5-P20CRC-500/2L
tnEE : Earliest end of frame n, this is the earliest time when the transceiver or any other sensor on the
bus can expect that the frame no. n is over.
tnNE : Nominal end of frame n
tnLE : Latest end of frame n, this is the latest time when the transceiver or any other sensor on the bus
can expect that the frame no. n is over.
TGAP: Minimum gap time which must be guaranteed between two frames [5.6us / 8.4us]
TTRIG: TTRIG = tolerance to detect the sync pulse = tTRIG + ttol_detect + tEMC
[min = 0s; nom = 3,5s; max = 10s].
TSync: Duration of sync period
e.g. for 1% transceiver clock tolerance: TSync, min = TSync*0,99; TSync, max = TSync*1,01
tSlot 1 Start : Earliest Start of first sensor data word [44 or 71us ]
TBIT: Nominal time for a single bit [5.3us / 8.0 us]
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
For n=1
t1ES = tSlot 1 Start +TTRIG, min
t1NS * tSlot 1 Start /(1-CT1)
t1LS tSlot 1 Start *(1+CT1)/(1-CT1)+TTRIG, max
t1EE t1ES+M1*TBIT*(1-CT1)
= tSlot 1 Start +M1*TBIT*(1-CT1)
t1LE : t1LS+M1*TBIT*(1+CT1)
= tSlot 1 Start *(1+CT1)/(1-CT1)+TTRIG, max+M1*TBIT*(1+CT1)
for n=2..N
tnES (tn-1LE+TGAP)+TTRIG, min
tnNS *) (tn-1LE+TGAP)/(1-CTn)
tnLS (tn-1LE+TGAP)*(1+CTn)/(1-CTn)+TTRIG, max
tnEE tnES+Mn*TBIT*(1-CTn)
= (tn-1LE+TGAP) +Mn*TBIT*(1-CTn)
tnLE : tnLS+Mn*TBIT*(1+CTn)
= (tn-1LE+TGAP)*(1+CTX)/(1-CTX)+TTRIG, max+Mn*TBIT*(1+CTn)
*) The nominal trigger detection tolerance is neglected for calculation of t1NS since this value
typically is used for sensor programming where detection tolerances do not apply.
Last frame must end before next sync pulse starts according to specific application requirements a final
TGAP has to be considered:
tSlot N, End = tNLE (+ TGAP) < TSync, min + t1
Note:
is used since the final frame timing should be equalized in order to cover the whole sync period
with maximum margins.
Transceiver clock tolerance determines effective sync pulse duration. A clock tolerance of 1% is
assumed. (see also TSYNC)
A discretisation of the calculated timings of nominal 0.5us is proposed
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Please refer to the corresponding substandard for details on timing specification and recommended
operation modes.
PSI5 usually uses twisted pair lines which are modeled as shown in Figure 35. Parameter specification is
done for the different system configurations. All indications are based on standard CAN cable with a
maximum inductance of 0.72H/m.
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
RW/2 L W /2
CW
RW/2 L W /2
Parameter Specification
N Parameter Symbol/Remark Min Typ Max Unit
1,2,8*) Large cable lengths / inductances may require appropriate selection of sensor and ECU capacitance
values and / or additional damping measures.
3*) RE = 9.5V is recommended for low voltage applications, when no additional voltage source is
implemented in the ECU; however, in compliance with former PSI5 versions RE = 12.5V still is valid.
Parameter Specification
N Parameter Symbol/Remark Min Typ Max Unit
8 Overall line resistance incl. wire (each wire) 2 * (RCE + RW /2 + RCS) 2.5
All values specified for a 125kbps data rate and a maximum of three sensors.
1,2*) Damping is required in ECU and sensors to limit oscillations on the bus lines. Please refer to chapter
7.6 for the corresponding equivalent circuits
3*) Wire capacitance not included
4*) RE = 9.5V is recommended for low voltage applications, when no additional voltage source is
implemented in the ECU; however, in compliance with former PSI5 versions RE = 12.5V still is valid.
Parameter Specification
N Parameter Symbol/Remark Min Typ Max Unit
5 Bus capacitance CB 9 72 n
F
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Parameter Specification
N Parameter Symbol/Remark Min Typ Max Unit
5 Bus capacitance CB 9 72 n
F
7.6.1 Reference Networks for Asynchronous Mode and Parallel Bus Mode
All indications in this section are valid for asynchronous mode and parallel bus mode with up to three
sensors and for a data transmission rate of 125kbps.
ECU and Wiring Reference Network for asynchronous mode and parallel bus mode
IE Test Circuit IS
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
Sensor
VE RE1 RE2 Rwire Lwire DUT
VSS
CE CL
1* Supply voltage VE 11 V
Sensor damping behaviour for asynchronous mode and parallel bus mode
Sensor
IS
ECU Reference
Test Circuit 1
ZS (2 f) R eq,S IS,Low
j2 f C eq,S
7.6.2 Reference Networks for Universal Bus Mode and Daisy Chain Bus Mode
All indications in this section are valid for universal bus mode and daisy chain bus mode with up to three
sensors and for a data transmission rate of 125kbps.
ECU reference network for universal bus mode and daisy chain bus mode
CE CL
1* Supply voltage VE 11 V
IOver-
IE, IS [%] shoot
tSettle
100
80
trise 20,80
tUnder-
shoot
20
trise trise t
20 80
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.
7.6.4 Sensor Reference Tests for Asynchronous Mode and Parallel Bus Mode
The sensor has to fulfill the reference tests for every voltage VE between a minimum voltage to meet VSS,min
at the sensor pins and 11V.
N Parameter Symbol/Remark Min Nom Max Unit
A1 Sending current rise/fall time (sensor) trise 20, 80 & tfall 80, 20 (IS) 1 s
Test condition: RE1 = 2.5; CE variable between 13nF and 33nF; CL = 2.2nF; Rwire = 0.1; Lwire = 8.7H
B2 Sending current over- / undershoot @sensor IOvershoot, rise & IUndershoot, fall (IS) 50 %
B3 Time for under- / overshoot @ECU tUndershoot, rise & tOvershoot, fall (IE) 0.52 s
C1 Sending current rise/fall time @ECU trise 20, 80 & tfall 80, 20 (IE) 1.8 s
A sensor internal damping behaviour is required corresponding to the equivalent sensor reference network (see
chapter 6.6.1).
A test condition for the sensor damping will be specified in a future version of the PSI5 test specification
See section 7.6.1 for ECU and wiring reference network.
A,C*) Maximum internal ECU resistance RE1 has to be adjusted to meet the implemented RE,max (9.5/12.5)
B*) The sensor has to fulfill reference Test B for every value of the capacitance CE between 13nF and 33nF.
7.6.5 Sensor Reference Tests for Universal Bus Mode and Daisy Chain Bus Mode
The sensor has to fulfill the reference tests for every voltage VE between a minimum voltage to meet VCE,min
at the output pins of the ECU and 11V.
N Parameter Symbol/Remark Min Nom Max Unit
B2 Sending current over- / undershoot @ ECU IOvershoot, rise & IUndershoot, fall (ICE) 50 %
output pins
B3 Time for under- / overshoot @ ECU tUndershoot, rise & tOvershoot, fall (IE) 0.52 s
C1 Sending current rise/fall time @ECU trise 20, 80 & tfall 80, 20 (IE) 1.8 s
See section 7.6.2 for ECU and wiring reference network.
B*) The sensor has to fulfill reference Test B for every value of the capacitance CE between 13nF and 33nF.
C*) Maximum internal ECU resistance RE1 has to be adjusted to meet the implemented RE,max (9.5/12.5)
Test conditions & reference networks for transciever / ECU will be specified in a future version of the PSI5
test specification.
8 Interoperability Requirements
PSI5 defines all basic characteristics of an electrical sensor interface including the physical layer, data link
layer and - to a certain extend - the application layer. Interoperability between ECU and sensors
(asynchronous / synchronous mode) or bus (parallel / universal bus mode and daisy chain mode) requires
the definition of the following additional, system specific parameters:
- Sensor configurations, operation modes and timings (single sensor, bus configuration or sensor cluster)
- System supply voltage (low, standard or increased)
- Current driving capabilities vs. current load of the sensors (standard or extended)
- Initialization data content i.e. also including determination of the repetition count (k)
Other sensor parameters such as mechanical and dimensional characteristics, signal evaluation path and
functional characteristics or reliability and environmental test conditions are beyond the scope of the PSI5
All rights including industrial property rights and all rights of disposal such as copying and passing to third parties reserved.