Please note that the date you requested in the address for this web page is not an actual date upon which a change occurred to this item of legislation. You are being shown the legislation from , which is the first date before then upon which a change was made.

ANNEX I CU.K. Requirements for construction, testing, installation, and inspection

Appendix 8

CALIBRATION PROTOCOL U.K.

5.MANAGEMENT SERVICESU.K.
5.1. StartDiagnosticSession service U.K.
5.1.1 Message description U.K.
CPR_025The service StartDiagnosticSession is used to enable different diagnostic sessions in the server. A diagnostic session enables a specific set of services according to Table 17. A session can enable vehicle manufacturer specific services which are not part of this document. Implementation rules shall conform to the following requirements:U.K.
  • There shall be always exactly one diagnostic session active in the VU,

  • The VU shall always start the StandardDiagnosticSession when powered up. If no other diagnostic session is started, then the StandardDiagnosticSession shall be running as long as the VU is powered,

  • If a diagnostic session which is already running has been requested by the tester, then the VU shall send a positive response message,

  • Whenever the tester requests a new diagnostic session, the VU shall first send a StartDiagnosticSession positive response message before the new session becomes active in the VU. If the VU is not able to start the requested new diagnostic session, then it shall respond with a StartDiagnosticSession negative response message, and the current session shall continue.

CPR_026A diagnostic session shall only be started if communication has been established between the client and the VU.U.K.
CPR_027The timing parameters defined in Table 4 shall be active after a successful StartDiagnosticSession with the diagnosticSession parameter set to ‘StandardDiagnosticSession’ in the request message if another diagnostic session was previously active.U.K.
5.1.2 Message format U.K.
CPR_028The message formats for the StartDiagnosticSession primitives are detailed in the following tables.U.K.
Table 14
StartDiagnosticSession Request Message
Byte #Parameter NameHex ValueMnemonic
#1Format byte — physical addressing80FMT
#2Target address byteEETGT
#3Source address bytettSRC
#4Additional length byte02LEN
#5 StartDiagnosticSession Request Service Id 10 STDS
#6diagnosticSession = [one value from Table 17]xxDS_…
#7Checksum00-FFCS
Table 15
StartDiagnosticSession Positive Response Message
Byte #Parameter NameHex ValueMnemonic
#1Format byte — physical addressing80FMT
#2Target address bytettTGT
#3Source address byteEESRC
#4Additional length byte02LEN
#5 StartDiagnosticSession Positive Response Service Id 50 STDSPR
#6diagnosticSession = [same value as in byte #6 Table 14]xxDS_…
#7Checksum00-FFCS
Table 16
StartDiagnosticSession Negative Response Message
a

– the value inserted in byte #6 of the request message is not supported, i.e. not in Table 17,

b

– the length of the message is wrong,

c

– the criteria for the request StartDiagnosticSession are not met.

Byte #Parameter NameHex ValueMnemonic
#1Format byte — physical addressing80FMT
#2Target address bytettTGT
#3Source address byteEESRC
#4Additional length byte03LEN
#5 Negative Response Service Id 7F NR
#6StartDiagnosticSession Request Service Id10STDS
#7ResponseCode =[subFunctionNotSupporteda12RC_SFNS
incorrectMessageLengthb13RC_IML
conditionsNotCorrectc22RC_CNC
#8Checksum00-FFCS