FFFIS Juridical Recorder-Downloading Tool

ERTMS/ETCS – Class 1FFFIS Juridical Recorder-Downloading toolREF : SUBSET-027ISSUE : 2.3.0DATE : 2009-04-22Company Technical Approval Management approvalALSTOMANSALDOBOMBARDIERINVENSYSSIEMENSTHALESSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 1/35

1. MODIFICATION HISTORY0.0.1Issue NumberDate1999-07-270.1.01999-09-301.0.01999-10-071.1.02000-02-181.2.02000-02-241.2.12000-03-282.0.02000-03-302.0.12001-10-312.2.210-02-032.2.32003-07-072.2.42005-01-03Section Number Modification / Description AuthorAll Creation Sonia ValeroAllModifications after reviewcommentsJavier CongostoSonia ValeroJavier CongostoAll Final version Sonia ValeroJavier CongostoAll Updating to SRS 2.0.0 Sonia ValeroAllAll4.1.2.4.5, Final fordistributionModifications after reviewwith ECSAG (2000-03-22)Final issue to ECSAGUpdate with Proposal 0.0.4to SUBSET-027 v2.0.1Raised in issue for releaseto the Users Group.No technical changesEliminate all reference toM_VOLTAGE as requestedby the Users Group.Including all CRs includedin the UNISIG data baserelated to the FFFIS JRU-Downloading tool v. 2.2.3up to 03/01/2005 and theproblems detected duringthe CEDEX interoperabilitytests. It also containschanges included in SRS v2.2.2 affecting the juridicalrecorder functionality.U. Dräger (ed)Sonia ValeroU.D. (ed)Sonia ValeroWLHSonia ValeroSonia Valero2.2.5 All Updating to SRS 2.2.6. The Sonia ValeroSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 2/35

2005-04-21 chapter about the physicalinterface has been notupdated.2.2.62005-09-052.2.72005-10-132.2.82005-10-172.2.92005-10-172.2.122009-02-252.3.02009-04-223.2.1.124.1.2.5.24.1.2.5.114.1.2.5.254.1.2.5.264.1.2.6.5.14.1.3.1.1.15.1.2.16.1.2.1Update to include proposalsfrom CEDEX andcomments to version 2.2.5.Update to includecomments fromSuperGroupUpdate after revisionUpdate of referenceddocumentsUpdate in the frame of2.3.0d: update according toCRs 240, 262, 394, 643,703 and 775.Update in the frame of2.3.0d regarding CR240modificationsSonia ValeroSonia ValeroSonia ValeroSonia Valero/HKPhilippe PrieelsJörg LiescheSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 3/35

3. INTRODUCTION3.1 Scope3.1.1.1 This document is the Form Fit Function Interface Specification for the JuridicalRecorder-Downloading tool.3.1.1.2 It contains the interface between the function charged to perform the juridical recorderfunction and the Downloading tool for the ERTMS/ETCS system.3.1.1.3 It defines the format and content of the messages exchanged, the communicationprotocol and the physical interface.3.1.1.4 This document is inside the ERTMS/ETCS project scope. It’s based on the document[1], [2] and [3].3.2 General aspects3.2.1.1 This section is only a general description of the main principles of the juridicalrecording function.3.2.1.2 The purpose of this document is to define the interface, the way this function isimplemented (with an specific Juridical Recording Unit or within the ERTMS/ETCS onboardequipment) is out of the scope and it’s not necessary for interoperability.3.2.1.3 The juridical recording function is performed on-board.3.2.1.4 The juridical recording function is performed through a temporary storage device. Theflow of information goes from the ERTMS/ETCS on-board to the Downloading tool,through the Juridical Recorder device without being altered.3.2.1.5 All the information recorded comes from the ERTMS/ETCS kernel.3.2.1.6 It shall be possible for the ERTMS/ETCS on-board to give access to the juridicalrecorder function to other devices out of the ERTMS equipment, such as the STM.3.2.1.7 The juridical recorder device shall be able to store the complete set of data for at leastthe last 24 hours in service.3.2.1.8 The juridical recorder device shall be able to store a reduce set of data for at least thelast 8 days in service.3.2.1.9 The juridical recorder retention time (time the storage device is able to retain thestored data available after the equipment stops being powered) shall be at least 7days.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 5/35

3.2.1.10 The temporary storage device shall be extractable to allow the recovering andtransport of data after an accident.3.2.1.11 The traction/brake parameters are still under discussion and might be subject of afuture change due to EEIG Brake Model.3.2.1.12 The messages stored in the Juridical Recorder come from different sources whichmight imply non-sequential time stamps (different delays regarding the physicalinterface with the unit transmitting the message).3.3 References[1] UNISIG Subset 026 System Requirements Specification ERTMS/ETCS Class 1,Version 2.3.0[2] UNISIG Subset 058 FFFIS STM Application Layer ,Version 2.1.1[3] UNISIG Subset 108 Interoperability-related consolidation on TSI annex A documents (mainlySUBSET-026 v2.2.2), Version 1.2.03.4 AbbreviationsACKDMIJRUAcknowledgementDriver Machine InterfaceJuridical Recorder Unit© This document has been developed and released by UNISIGSUBSET-0272.3.0FFFIS JR-Downloading tool Page 6/35

4. FUNCTIONAL INTERFACE DEFINITION4.1 Data exchange (Juridical Recorder - Downloading tool)4.1.1 Dialogue definition4.1.1.1 A dialogue is set up between the Downloading tool and the Juridical Recorder. Thisdialogue is charted here below (figure 1):JuridicalRecorderDownloadingtoolDownloadinginitialisationState request (71)State ack (151)Figure 1. Start up communication dialogue4.1.1.2 During the Downloading tool initialisation, it requests the Juridical Recorder state inorder to start the communication with this equipment. If the Juridical Recorder devicedoes not answer to this message with “state ack”, the Downloading tool considers thejuridical recording function as not available.4.1.1.3 When the Downloading tool receives “JRU failure”, it shall display that the JuridicalRecorder is failed.4.1.1.4 The state request message is sent periodically (every second) until the communicationis established. After a minute without establishing the communication, the Downloadingtool will raise a “Communication failure” message. When getting the “State ack”message, it shall display a “Communication established” message.4.1.1.5 A further explanation of these control messages is included in sections 4.1.2 and 4.1.3of this document. The numbers in brackets that appear close to the message namerefer to the NID_MESSAGE in Table 1 and Table 2.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 7/35

4.1.1.6 After the initialisation process the following dialogue shall be carried out(Figure 2):JuridicalRecorderDownloadingtoolData Downloading Request(72)DatarequestDownloadingStart of transmission (153)DATA (0 … N)End of transmission (154)Figure 2. Data Downloading communication dialogue4.1.1.7 Data downloading (Figure 2) shall be carried out through the Downloading toolphysically connected to the Juridical Recorder device. The downloading toolcommunication above provides the management of stored data downloading.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 8/35

4.1.2 JRU Output information (Messages / Variables)4.1.2.1 Messages list4.1.2.2 Each message has a variable in its header that contains a number to have a way todistinguish the messages. The list of all the messages (data and control messages) isshown in Table 1:NID_MESSAGETYPE OFMESSAGEMESSAGEPAGE0 DATA MESSAGE Intentionally removed1 “ GENERAL MESSAGE 362 “ DATA ENTRY COMPLETED 373 “ EMERGENCY BRAKE ORDER 494 “ SERVICE BRAKE ORDER 495 “ EVENTS 506 “ TELEGRAM FROM BALISE 537 “ MESSAGE FROM EUROLOOP 538 “ MESSAGE FROM RADIO INFILL UNIT 539 “ MESSAGE FROM RBC 5410 “ MESSAGE TO RBC 5511 “ DRIVER’S ACTION 5512 “ BALISE GROUP ERROR 5913 “ RADIO ERROR 6214 “ STM INFORMATION 6215 “ DATA FROM EXTERNAL SOURCES 6316 “ START DISPLAYING FIXED TEXTMESSAGE17 “ STOP DISPLAYING FIXED TEXTMESSAGE6364SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 9/35

18 “ START DISPLAYING PLAIN TEXTMESSAGE19 “ STOP DISPLAYING PLAIN TEXTMESSAGE20 “ CURRENT VALUE OF MOSTRESTRICTIVE SPEED PROFILE65656621 “ TARGET SPEED 6722 “ TARGET DISTANCE 6723 “ RELEASE SPEED 6924 “ WARNING 7025 “ SR SPEED/DISTANCE 7126 “ STM SELECTED 7227 “ PERMITTED SPEED 7328-150 “ SPARE151 CONTROLMESSAGESTATE ACK 76152 “ JRU FAILURE 76153 " START OF TRANSMISSION 76154 " END OF TRANSMISSION 76155-255 “ SPARETable 1. Juridical Recorder-Downloading tool messages listSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 10/35

4.1.2.3 Messages data to be downloaded: general structure4.1.2.3.1 All the messages have the same structure with a common header and a set ofvariables depending on the message sent.4.1.2.3.2 A message shall be composed of:1. A header (fields 1 and 2).2. Set of common variables to all the messages (fields 3-10). These variables mustbe recorded with each event produced: the date and time (UTC), train position, trainspeed, driver ID, ETCS equipment ID, the ETCS level and the active mode of the onboardsystem.3. Complementary variables as needed by application (fields 11-N).FieldNoFIELDSRemarks1 NID_MESSAGE Message identification number2 L_MESSAGE Message length including fields 1 to N3 DATE Current date4 TIME Current time5 TRAIN_POSITION Current train position6 V_TRAIN Current train speed7 NID_DRIVER Driver identifier8 NID_ENGINE On-board ETCS identity9 LEVEL Current level10 MODE Current mode… Variables Data associated to the message. Its lengthdepends on the message content, but it’salways rounded up to a bytes unit.Note : To be coherent the length of the variables defined in other documents is not included in thefollowing description.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 11/35

4.1.2.4 Common Fields Description4.1.2.4.1 NID_MESSAGEDescriptionThis field contains the message identifier.Content Variable Length CommentNID_MESSAGENameDescriptionNID_MESSAGE 8 Defined belowMessage identifierIdentifier of the messageLength of variable Minimum Value Maximum Value Resolution/formula8 bits 0 255 NumbersSpecial/ReservedValues4.1.2.4.2 L_MESSAGEDescriptionThis field contains the message length.Content Variable Length CommentL_MESSAGENameDescriptionL_MESSAGE 11 Defined below.Message lengthL_MESSAGE indicates the length of the message in bytes, including allvariables defined in the message header (L_MESSAGE also).Length of variable Minimum Value Maximum Value Resolution/formula11 bits 0 2047 1 ByteSpecial/ReservedValues4.1.2.4.3 DATEDescription It contains the date the event recorded has occurred.Content Variable Length CommentYEAR 7 Defined below.MONTH 4 Defined below.DAY 5 Defined below.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 12/35

YEARNameOfficial yearDescriptionIt’s used to label data recorded. Only the last two figures of the year are recorded (unitand ten).Length of variable Minimum Value Maximum Value Resolution/formula7 bits 00 99 1 yearSpecial/ReservedValuesMONTH110 0100…111 1110111 1111100…126127not used…not usedyear unknownNameOfficial monthDescriptionIt’s used to label data recorded.Length of variable Minimum Value Maximum Value Resolution/formula4 bits 01 12 1 monthSpecial/ReservedValuesDAY00001101111011110131415not usednot usednot usedmonth unknownNameOfficial dayDescriptionIt’s used to label data recorded.Length of variable Minimum Value Maximum Value Resolution/formula5 bits 01 31 1 daySpecial/ReservedValues0 0000 0 day unknownSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 13/35

4.1.2.4.4 TIMEDescriptionIt contains the time in Universal Time Co-ordinated (UTC) the event recordedhas occurred.Content Variable Length CommentHOURHOUR 5 Defined below.MINUTES 6 Defined below.SECONDS 6 Defined below.TTS 5 Defined below.NameOfficial hourDescriptionIt’s used to label data recorded.Length of variable Minimum Value Maximum Value Resolution/formula5 bits 00 23 1 hourSpecial/ReservedValuesMINUTES1 1000…1 11101 111124…3031not used…not usedhour unknownNameOfficial minutesDescriptionIt’s used to label data recorded.Length of variable Minimum Value Maximum Value Resolution/formula6 bits 00 59 1 minuteSpecial/ReservedValuesSECONDS11 110011 110111 111011 111160616263not usednot usednot usedminutes unknownNameOfficial secondsDescriptionIt’s used to label data recorded.Length of variable Minimum Value Maximum Value Resolution/formula6 bits 00 59 1 secondSpecial/ReservedValues11 110011 110111 111011 111160616263not usednot usednot usedseconds unknownSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 14/35

TTSNameOfficial hundredth of secondDescriptionIt's used to label data recorded. Used only in conjunction with HOUR,MINUTES and SECONDS.Length of variable Minimum Value Maximum Value Resolution/formula5 bits 000 ms 950 ms 050 msSpecial/ReservedValues10100 to 1111011111not usedhundredth of second unknown4.1.2.4.5 TRAIN_POSITIONDescriptionThis field contains the position of the train when the event recorded hasoccurred. This position is calculated with the distance to the last LRBG(Identity of Last Relevant Balise Group).Content Variable Length CommentQ_SCALE Defined in Chapter 7 of [1]NID_LRBG Defined in Chapter 7 of [1]D_LRBG Defined in Chapter 7 of [1]Q_DIRLRBG Defined in Chapter 7 of [1]Q_DLRBG Defined in Chapter 7 of [1]L_DOUBTOVER Defined in Chapter 7 of [1]L_DOUBTUNDER Defined in Chapter 7 of [1]4.1.2.4.6 V_TRAINDescriptionThis field contains the current speed of the train when the event recorded hasoccurred.Content Variable Length CommentV_TRAIN Defined in Chapter 7 of [1]4.1.2.4.7 DRIVER_IDDescriptionThis field contains the driver identifier number.Content Variable Length CommentDRIVER_ID384 bits 48 alphanumeric characters (ISO8859-1, also known as LatinAlphabet #1)SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 15/35

4.1.2.4.8 NID_ENGINEDescription This field contains the onboard ETCS identity.Content Variable Length CommentNID_ENGINE Defined in Chapter 7 of [1]4.1.2.4.9 LEVELDescription This field contains the current level when the event recorded has occurred.Content Variable Length CommentM_LEVEL Defined in Chapter 7 of [1]4.1.2.4.10 MODEDescription This field contains the current mode when the event recorded has occurred.Content Variable Length CommentM_MODE Defined in Chapter 7 of [1]4.1.2.5 Message Description4.1.2.5.1 MESSAGE GENERAL MESSAGEDescriptionThis messages is sent each time any of the header’s variables needs to berecorded (defined in Chapter 3 of [1]).Content Variable Length CommentnullSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 16/35

4.1.2.5.2 MESSAGE DATA ENTRY COMPLETEDDescriptionThis message contains the train and additional data.Content Variable Length CommentV_MAXTRAINMaximum permitted speed for thetrain. Defined in Chapter 7 of [1]NC_TRAIN Train category. Defined in Chapter 7of [1]L_TRAINTrain length. Defined in Chapter 7 of[1]N_SERVICE_SECTIONS 3 Number of sections in order to buildthe service brake model.V_SERVICEDECEL_CAP(k) 10 Speed component of the servicebrake deceleration capacity.A_SERVICEDECEL_CAP(k) 8 Acceleration component of theservice brake deceleration capacity.N_EMERGENCY_SECTIONS 3 Number of sections in order to buildthe emergency brake model.V_EMERGENCYDECEL_CAP(k) 10 Speed component of the emergencybrake deceleration capacity.A_EMERGENCYDECEL_CAP(k) 8 Acceleration component of theemergency brake decelerationcapacity.T_CUT_OFF 12 Time to cut-off traction.T_SERVICE_DELAY 12 Service Brake delay time.T_EMERGENCY_DELAY 12 Emergency Brake delay time.M_LOADINGGAUGE Loading gauge. Defined in Chapter 7of [1]M_AXLELOAD Axle load. Defined in Chapter 7 of [1]N_ITERNumber of iterations. Defined inChapter 7 of [1]M_TRACTION(k) Type of traction. Defined in Chapter 7of [1]M_AIRTIGHTStatus of airtight system. Defined inChapter 7 of [1]M_ADHESION Adhesion factor. Defined in Chapter 7of [1]NID_MNIdentity of Radio Network. Defined inChapter 7 of [1]SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 17/35

NID_CNID_RBCNID_RADIONID_OPERATIONALIdentity of the country or regioncomplementing the RBC identitynumber. Defined in chapter 7 of [1]RBC ETCS identity number. Definedin Chapter 7 of [1]Radio subscriber number. Defined inChapter 7 of [1]Train Running Number. Defined inChapter 7 of [1]N_SERVICE_SECTIONSNameDescriptionService Brake Number of Sections.It contains the number of sections needed to build the Service Brake Model.Length of variable Minimum Value Maximum Value Resolution/formula3 bits 1 7Special/reservedvalueV_SERVICEDECEL_CAPNameDescription0 Spare ValueService Brake Speed Component.It contains the lowest value of the speed to which the related Service BrakeDeceleration Component is applicable.Length of variable Minimum Value Maximum Value Resolution/formula10 bits 0 km/h 600 km/h 1 km/hSpecial/reservedvalue601 - 1023 Spare ValuesSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 18/35

A_SERVICEDECEL_CAPNameDescriptionService Brake Deceleration Component.It contains the lowest value of the current deceleration to which the relatedService Brake Deceleration Component is applicable.Length of variable Minimum Value Maximum Value Resolution/formula8 bits 0 2,55 0,01 m/s²Special/reservedvalueN_EMERGENCY_SECTIONSNameDescriptionEmergency brake Number of Sections.,It contains the number of sections needed to build the Emergency BrakeModel.Length of variable Minimum Value Maximum Value Resolution/formula3 bits 1 7Special/reservedvalueV_EMERGENCYDECEL_CAPNameDescription0 Spare ValueEmergency Brake Speed Component.It contains the lowest value of the speed to which the related EmergencyBrake Deceleration Component is applicable.Length of variable Minimum Value Maximum Value Resolution/formula10 bits 0 km/h 600 km/h 1 km/hSpecial/reservedvalueA_EMERGENCYDECEL_CAPNameDescription601 - 1023 Spare ValuesEmergency Brake Deceleration Component.It contains the lowest value of the current deceleration to which the relatedEmergency Brake Deceleration Component is applicable.Length of variable Minimum Value Maximum Value Resolution/formula8 bits 0 2,55 0,01 m/s²Special/reservedvalueSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 19/35

4.1.2.5.3 MESSAGE EMERGENCY BRAKE ORDERDescriptionThis message shall record the emergency brake application order.Content Variable Length CommentM_BRAKE_ORDERNameDescriptionM_BRAKE_ORDER 1 Defined belowBrake orderIt contains the order of application or revocation of the brakes.Length of variable Minimum Value Maximum Value Resolution/formula1 bitSpecial/reservedvalue10ApplicationRevocation4.1.2.5.4 MESSAGE SERVICE BRAKE ORDERDescription This message shall record the service brake application order.Content Variable Length CommentM_BRAKE_ORDER 1 Defined in 4.1.2.5.34.1.2.5.5 MESSAGE EVENTSDescriptionThis message shall record important events for train safety, which have beentriggered during the normal train operation.Content Variable Length CommentM_EVENTS 8 Defined belowSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 21/35

M_EVENTSNameDescriptionEvents on boardRecords the events for train safety which take place on board during normaltrain operationalLength of variable Minimum Value Maximum Value Resolution/formula8 bitSpecial/ReservedValues0000 00000000 00010000 00100000 00110000 01000000 01010000 01100000 01110000 10000000 10010000 10100000 10110000 11000000 11010000 1110…Not usedService brake failureStandstill supervision interventionRoll away supervision interventionReverse movement supervision interventionOverride activatedLoop transmission errorOdometer failurePassenger brake applicationVersion incompatibility with RBC/RIUOverride deactivatedTrain enters unsuitable routeNormal adhesion usedReduced adhesion usedVersion incompatibility with baliseFuture use4.1.2.5.6 TELEGRAM FROM BALISEDescriptionContentThis message shall be sent to the Juridical Recorder after receiving atelegram from a balise.The content of this message is the telegram coming from a balise as definedin Chapters 7 and 8 of [1].4.1.2.5.7 MESSAGES FROM EUROLOOPDescriptionContentThis message shall be sent to the Juridical Recorder after receiving amessage from an euroloop unit.The content of this message is any message coming from a euroloop asdefined in Chapters 7 and 8 of [1].SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 22/35

4.1.2.5.8 MESSAGES FROM RADIO INFILL UNITDescriptionContentThis message shall be sent to the Juridical Recorder after receiving amessage from a radio infill unit.The content of this message is any message coming from a radio infill unit asdefined in Chapters 7 and 8 of [1].4.1.2.5.9 MESSAGES FROM RBCDescriptionThis message shall be sent to the Juridical Recorder after receiving amessage from an RBC.Content Variable Length CommentNID_C 10 Defined in Chapter 7 of [1]NID_RBC 14 Defined in Chapter 7 of [1]. ETCSidentity (NID_C + NID_RBC) of theRBC from which the followingmessage has been received.Message, as defined in Chapters 7 and 8 of [1], coming from the referencedRBC.4.1.2.5.10 MESSAGES TO RBCDescriptionThis message shall be sent to the Juridical Recorder after sending amessage to an RBC.Content Variable Length CommentNID_C 10 Defined in Chapter 7 of [1]NID_RBC 14 Defined in Chapter 7 of [1]. ETCSidentity (NID_C + NID_RBC) of theRBC to which the followingmessage has been sent.Message, as defined in Chapters 7 and 8 of [1], sent to the referenced RBC.4.1.2.5.11 DRIVER’S ACTIONSDescriptionThis message shall be sent to the Juridical Recorder whenever the driveracts on the on board system (DMI, information received from the traininterface).Content Variable Length CommentM_DRIVERACTIONS 8 Defined belowSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 23/35

M_DRIVERACTIONSNameDescriptionDriver’s actions.This variable contains the driver’s action.Length of variable Minimum Value Maximum Value Resolution/formula8 bitSpecial/ReservedValues0000 00000000 00010000 00100000 00110000 01000000 01010000 01100000 01110000 10000000 10010000 10100000 10110000 11000000 11010000 11100000 11110001 00000001 00010001 00100001 00110001 01000001 01010001 01100001 01110001 10000001 10010001 10100001 10110001 11000001 11010001 11100001 11110010 00000010 00010010 00100010 0011Ack of on sightAck of shuntingAck of tripAck of staff responsibleAck of unfittedAck of reversingAck level 0Ack Level 1Ack level 2Ack level 3Ack level STMShunting selectedNon Leading selectedReversing requestedOverride selectedOverride route suitabilityBrake release acknowledgementExit of shunting selectedExit of Non Leading selectedStart selectedData Entry requestedDriver confirmation of dataConfirm track ahead freeAck of Plain Text MessagesAck of Fixed Text MessagesIntentionally deletedTrain integrity confirmationRequest to show supervision limitsAck of SN/SE modeChange of LanguageRequest to show geographical positionDesk closedDistance in SR changedSpeed in SR changedLevel 0 selectedLevel 1 selectedSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 24/35

0010 01000010 01010010 01100010 01110010 1000…Level 2 selectedLevel 3 selectedLevel STM selectedNormal adhesion selectedReduced adhesion selectedFuture useNote: The registration of these actions is not always mandatory, due to the technical restrictions ofsome trains to access them.4.1.2.5.12 BALISE GROUP ERRORDescriptionThis message contains a balise group related error as identified byM_ERROR.Content Variable Length CommentNID_ERRORBGNameDescriptionNID_C Defined in Chapter 7 of [1]NID_ERRORBGDefined belowM_ERROR Defined in Chapter 7 of [1]Identity number of the balise group to which the error is relatedIt contains the identity number of the balise group to which the error isrelated.NID_ERRORBG is identical to NID_BG (defined in chapter 7 of [1]) except forthe NID_ERRORBG Special Value "16383" which has the meaning"unknown" and covers the case that, due to the error, the balise groupidentity is unknown.Length of variable Minimum Value Maximum Value Resolution/formula14 bits 0 16382 NumbersSpecial/reservedvalue16383 UnknownSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 25/35

4.1.2.5.13 RADIO ERRORDescriptionThis message contains an error related to communication with an RBC asidentified by M_ERROR.Content Variable Length CommentNID_C Defined in Chapter 7 of [1]NID_RBCDefined in Chapter 7 of [1]. ETCSidentity (NID_C + NID_RBC) of theRBC to which the error is relatedM_ERROR Defined in Chapter 7 of [1]4.1.2.5.14 STM INFORMATIONThis message contains the information coming from the STM that must be recorded in theJuridical Recorder. The content of the message is defined in [2].4.1.2.5.15 DATA FROM EXTERNAL SOURCESDescriptionContentThis message has been reserved to record any information coming fromexternal sources. Its content is not under the ERTMS/ETCS equipmentcontrol.The content of this message is Packet Number 44, as defined in Chapter 7 of[1].4.1.2.5.16 START DISPLAYING FIXED TEXT MESSAGESDescriptionThis message contains a fixed text message that is currently being shown tothe driver.Content Variable Length CommentQ_TEXT Defined in Chapter 7 of [1]4.1.2.5.17 STOP DISPLAYING FIXED TEXT MESSAGESDescriptionThis message contains a fixed text message that is not shown to the driverany more.Content Variable Length CommentQ_TEXT Defined in Chapter 7 of [1]SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 26/35

4.1.2.5.18 START DISPLAYING PLAIN TEXT MESSAGESDescriptionThis message contains a plain text message that is currently being shown tothe driver.Content Variable Length CommentL_TEXT Defined in Chapter 7 of [1]X_TEXT(L_TEXT) Defined in Chapter 7 of [1]4.1.2.5.19 STOP DISPLAYING PLAIN TEXT MESSAGESDescriptionThis message contains a plain text message that is not shown to the driverany more.Content Variable Length CommentL_TEXT Defined in Chapter 7 of [1]X_TEXT(L_TEXT) Defined in Chapter 7 of [1]4.1.2.5.20 CURRENT VALUE OF MOST RESTRICTIVE SPEED PROFILEDescriptionThis message contains the current value of the most restrictive speed profilecalculated on-board. It is recorded at every change of the current value of themost restrictive speed profile.Content Variable Length CommentV_MRSPNameDescriptionV_MRSP 7Current value of most restrictive speed profile.Length of variable Minimum Value Maximum Value Resolution/formula7 bits 0 km/h 600 km/h 5 km/hSpecial/reservedvalue121-127 SpareSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 27/35

4.1.2.5.21 TARGET SPEEDDescriptionThis message contains the target speed.Content Variable Length CommentV_TARGETNameDescriptionV_TARGET 7 Defined below.Target speedTarget speed indicated to the driver.Length of variable Minimum Value Maximum Value Resolution/formula7 bits 0 km/h 600 km/h 5 km/hSpecial/reservedvalue121-126127SpareNo target speed is indicated to the driver4.1.2.5.22 TARGET DISTANCEDescriptionThis message contains the target distance.Content Variable Length CommentD_TARGETNameDescriptionQ_SCALE 2 Defined in Chapter 7 of [1].D_TARGET 15 Defined below.Target distanceTarget distance indicated to the driver.Length of variable Minimum Value Maximum Value Resolution/formula15 bits 0 cm 327.660 km 10 cm, 1 m or 10 m dependson Q_SCALE.Special/reservedvalue32767 No target distance is indicated to the driverSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 28/35

4.1.2.5.23 RELEASE SPEEDDescriptionThis message contains the release speed.Content Variable Length CommentV_RELEASENameDescriptionV_RELEASE 7Release speed.Release speed associated to the supervised location.Length of variable Minimum Value Maximum Value Resolution/formula7 bits 0 km/h 600 km/h 5 km/hSpecial/reservedvalue121-127 SpareNote: the resolution of therelease speed on the DMI isactually better (when releasespeed is calculated on-board).Unless the current value is a5km/h step, the recorded valueis a truncation to the nearest5km/h step below the currentvalue.4.1.2.5.24 WARNINGDescriptionContentSpeed supervision warning limit exceeded, recorded when Warning state isentered.It doesn’t contain any variable, only the fact that the speed supervisionwarning limit has been exceeded.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 29/35

4.1.2.5.25 SR SPEED/DISTANCEDescriptionThis message contains the change of the SR Speed or Distance entered bythe driver.Content Variable Length CommentV_SRNameDescriptionQ_SCALE Defined in Chapter 7 of [1].D_SR Defined in Chapter 7 of [1].V_SR 7Staff Responsible speedSpeed allowed to run in Staff Responsible, modified by the driver through theDMI.Length of variable Minimum Value Maximum Value Resolution/formula7 bits 0 600 5 km/hNote: the resolution of the SRspeed entered by the driver isactually better. Unless thecurrent value is a 5km/h step,the recorded value is atruncation to the nearest 5km/hstep below the current value.4.1.2.5.26 STM SELECTEDDescription This message contains the STM selected when the selected level is STM.Content Variable Length CommentNID_STM Defined in Chapter 7 of [1].SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 30/35

4.1.2.5.27 PERMITTED SPEEDDescription This message contains a change on the permitted speedContent Variable Length CommentV_PERMITTED 7V_PERMITTEDNameDescriptionPermitted speedCurrent permitted speedLength of variable Minimum Value Maximum Value Resolution/formula7 bits 0 600 5 km/hSpecial/reservedvalue121-127 SpareNote: the resolution of thepermitted speed on the DMI isactually better. Unless thecurrent value is a 5km/h step,the recorded value is atruncation to the nearest 5km/hstep below the current value.4.1.2.6 Control Messages General Structure4.1.2.6.1 All the messages have the same structure with a common header.4.1.2.6.2 They do not send any variable, because no extra information is needed. The length is8 bits for each message.4.1.2.6.3 Control messages shall not be registered in the juridical recorder device.4.1.2.6.4 A message shall only be composed of a header, which description follows:FieldNoVARIABLESRemarks1 NID_MESSAGE Message identification numberSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 31/35

4.1.2.6.5 MESSAGE STATE ACK4.1.2.6.5.1 This message answers to a “state request” which is sent by the Downloading tool.4.1.2.6.6 MESSAGE JRU FAILURE4.1.2.6.6.1 This message is sent to the Downloading tool when the juridical recording functionhas failed.4.1.2.6.7 MESSAGE START OF TRANSMISSION4.1.2.6.7.1 It indicates to the Downloading tool that the transmission of the data stored in theJuridical Recorder device will follow the reception of this message.4.1.2.6.8 MESSAGE END OF TRANSMISSION4.1.2.6.8.1 This message indicates to the Downloading tool that the transmission of the datastored has been completed.4.1.3 JRU Input information (Messages / Variables)4.1.3.1 General structure of messages4.1.3.1.1.1 All the messages sent from the downloading tool to the Juridical Recorder, shallhave the same structure than the control message sent from the Juridical Recorderto the downloading tool. These messages are shown in Table 2:NID_MESSAGE TYPE OF MESSAGE MESSAGE0-70 SPARE71 CONTROL MESSAGE STATE REQUEST72 “ DATA DOWNLOADING REQUEST73-255 “ SPARETable 2. Downloading tool-Juridical Recorder messages list4.1.3.2 STATE REQUEST4.1.3.2.1.1 It requests the state of the Juridical Recorder to set up the communication.4.1.3.3 DATA DOWNLOADING REQUESTIt is sent from the Downloading tool to the Juridical Recorder, to allow the downloading of all thedata stored in it. This message does not allow deleting the data.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 32/35

5. COMMUNICATION PROTOCOLS5.1 Juridical Recorder – Downloading tool Communicationprotocol5.1.1 Data Link layer5.1.1.1 The Data Link layer will ensure the information is transmitted without any error. Itreceives the messages from the application layer and adds the relevant headers. Thefollowing features will be considered:• It implements byte stuffing.• It builds up the start and the end of the frame.5.1.2 Definition of frames5.1.2.1 Each frame contains an application level message. The frame structure is composedof a starting byte (FLAG), an application level message field and an ending byte(FLAG).FLAG MESSAGE FLAGFLAG is a byte, which value is 7EH.The flow of several messages shall be in the following format:FLAG MESSAGE FLAG FLAG MESSAGE FLAG FLAG MESSAGE FLAGwhere message is either a “control message”4.1.3.1.1.1)or a data message (4.1.2.2 &5.1.3 Definition of fields5.1.3.1 Byte stuffing5.1.3.1.1 Its use is due to the existence of some values that coincide with fix values in fields thathave a special meaning for the link layer.5.1.3.1.2 The stuffing byte will be added to some bytes of the MESSAGE or CONTROL fields.5.1.3.1.3 If a byte value is 7EH, it will be replaced by: 7DH, 5EH5.1.3.1.4 If a byte value is 7DH, it will be replaced by: 7DH, 5DHSUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 33/35

5.1.3.2 Character Format5.1.3.2.1 Each byte of the message is transmitted with one start bit, eight data bits, even parityand one stop bit.SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 34/35

6. PHYSICAL INTERFACE SPECIFICATION6.1 Juridical Recorder – Downloading tool Physical Interface6.1.1 Physical Layer Communication Standard.6.1.1.1 The Physical layer is in charge of the physical message transmission/reception. Theserial interface shall be implemented as an asynchronous communication.6.1.1.2 Only one physical link (without redundancy) will be implemented for the JuridicalRecorder-Downloading tool interface. The Physical link will meet the following features:• RS232 compatible with three-wire interface (Full Duplex).• Transmission speed: 19,200 bps6.1.2 Connections.6.1.2.1 The physical connection between Juridical Recorder and Downloading tool will beimplemented through a 9 pin D sub female plug connector (using the RS232standard).Pin 1Pin 2Pin 3Pin 4Pin 5Pin 6Pin 7Pin 8Pin 9spareReceive DataTransmit DataspareSignal Groundsparesparesparespare123456789(Female)SUBSET-0272.3.0© This document has been developed and released by UNISIGFFFIS JR-Downloading tool Page 35/35