Annexure-G - Specification of Kavach Network Monitoring System Protocol Amdt-4 PDF

ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4...

ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 GOVERNMENT OF INDIA (भारत सरकार) MINISTRY OF RAILWAYS (रे ल मंत्रालय) Annexure – G KAVACH Network Monitoring System Protocol Amdt-4 Issued by SIGNAL & TELECOM DIRECTORATE RESEARCH, DESIGNS & STANDARDS ORGANISATION MINISTRY OF RAILWAYS MANAK NAGAR LUCKNOW – 226 011 Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:11:22 +05'30' Page 1 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Revision History Amdt Date of issue Amendment 1 13.06.2023  Figure-1 -KAVACH Network arrangement diagram is modi- fied  Clause 4.1- Station Active Radio - modified and  Loco Regular / Access Request Packet (As per KAVACH Radio Communication Protocol- Shifted in clause G.4.2.  Cl. G-4.2 - Loco KAVACH Position Information Message- New clause added  Cl. G 4.3 Adjacent Kavach Information –New clause added.  Cl. G..4.4 Field Input Status Message- New clause  Cl.G.4.5 Field Inputs Event Message- New clause  Cl. G.4.7 Onboard KAVACH Health Packet to NMS- Modified  Cl. G.4.8 KAVACH Fault message to NMS Server-modified  Cl. G.4.9 NMS Acknowledge message to KAVACH Subsystem- Modified.  Cl. G.6.1.24- modified for additional fault message. 2 06.11.2023  CL.G.2.2-Modified with addition of “The same network may be used for connection TSRMS network”. CL.G.2.3- deleted “The IB huts shall be connected to the nearest Station in T network. Figure-1 for connectivity with NMS modified.  Cl. G.3- The NMS message structure from Stationary KA- VACH corrected.  CL.G.4.1-Modified in field Station Active Radio with addi- tion of “0xE1: if Ethernet 1 is active, 0xE2: if Ethernet 2 is active, Any other data: Active radio un-known”.  CL.G.4.2-Modified in field onboard Active Radio with addi- tion of “0xE1: if Ethernet 1 is active, 0xE2: if Ethernet 2 is active, Any other data: Active radio un-known”.  CL.4.3- TSR Information Message from stationary KAVACH to NMS- New Packet added.  CL4.4 - Adjacent Kavach Information- Field 10 & 11 is de- leted. 3 16.12.2023  CL.G.4.2- Modified in Loco Regular/ Access Request Packet. a) Current Route ID No of MA section count “Current route is the Route ID in which train occupied. Defines the train route in which MA is extended”. b) Next Route ID - Next route is the approaching signal Route ID in which train will enter. List of MA sections starting from train front end occupied section to EOA Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:11:39 +05'30' Page 2 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 section.  CL.G.4.3- Deleted TSR Data Integrity test message. Acknowledge Medssage in Field No. 10. Modified CRC Field Width 324 in Field No. 11.  CL.G.4.4- Deleted Heart Beat message in Field No. 10.  CL.G.4.6 –Field Input event message-Field-17- Registered Loco_Count, 18- Loco _ID, 19- Abs_Loc_1 & 21- Abs_Loc_2.  CL.G.4.8- Onboard KAVACH Health Packet to NMS- Field-16- Stationary_KAVACH_ID, 17-Abs_Loc_1 & 19- Abs_Loc_2. 4 03.06.2024  CL G.3- New packet of “Loco KAVACH RSSI Message & Sta- tionary KAVACH RSSI Message added.  CL4.3- G.4.3- in field -10 “TSR Data Integrity test message “ added TSR Information Message from stationary KA- VACH to NMS.  CL 4.4 – In field -10 “Heart Beat message” added in Adja- cent Kavach Information  CL.4.7- Stationary KAVACH Health Message to NMS Server  field Registered Loco_Count, Loco _ID, Abs_Loc_1, Frequency Channel_Number, Radio-1 RSSI, Abs_Loc_2, Frequency Channel_Number, Radio-2 RSSI deleted  field 30,31,32,33,34,35 modified with for every one hour in packet.  Field -42- Override Missing TIN modified.  Field-44-6. Exit due to Train Handover. 7. Exit due to Handover cancellation  CL.4.8- Onboard KAVACH Health Packet to NMS  field Stationary_KAVACH_ID, Abs_Loc_1, Frequency Channel_Number, Radio-1 RSSI, Abs_Loc_2, Frequency Channel_Number, Radio-2 RSSI deleted.  Field -16- Stationary Regular packet received time off- set- added with (While establishing communication with Stationary KAVACH).  field 20,21,22,23,24,25,26,27, 28, 29 modified with for every one hour in packet.  Field 39-Computed TLM status- 0-TLM failed added.  CL.4.10- Loco KAVACH RSSI Message- new Pack- et added.  CL.4.11- Stationary KAVACH RSSI Message- new Packet added. Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:12:03 +05'30' Page 3 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 G.1 Introduction This document describes the protocol for Centralized Intelligent KAVACH Network Monitoring System (CIKMS) for the purpose of KAVACH System. G.2 Interface details for Stationary KAVACH to NMS & Stationary KAVACH to Stationary KAVACH Communication on E1 Inter- face G.2.1 KAVACH NMS Network shall be built on E1 interface also which is provided by the Indian Railways. This network shall be used for centralized monitoring of KAVACH equipped Trains and Stations within the network. Centralized monitoring of a group of stations is achieved by collecting signal aspects, track occupancy, loco ab- solute position etc., from each of the Stationary KAVACH unit within the network. Stationary KAVACH units shall communicate with NMS unit using the predefined packets, as explained in Packet Structure in the subsequent clauses. G.2.2 Using E1 interface, each Stationary KAVACH (SVK) unit is con- nected to adjacent stationary KAVACH unit/Network Management System to form a network, as shown in Figure 1. Using Ethernet protocol over this network, Stationary KAVACH units will ex- change Stationary-Stationary communication packets with adja- cent Stationary KAVACH units and NMS. The same network may be used for connection TSRMS network. G.2.3 Event logger module of Onboard KAVACH and Stationary KA- VACH shall store all the Vital events, messages exchanged be- tween Radio or other unit and diagnostic related messages of all the other module. The modification in NMS protocol may be pos- sible without change in executive logic of vital card. G.2.4 Number of Stationary KAVACH units in one E1/Ethernet rings shall be limited to 10. Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:12:20 +05'30' Page 4 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Figure 1 Connectivity with NMS G.3 The NMS message structure from Stationary KAVACH: The different types of messages are as defined belowfor logging in NMS Message Type Value Purpose Stationary KAVACH infor- 0x11 Stationary KAVACH will send all mation Message to NMS packet of Station Regular / Ac- server cess Authority & Additional Emergency Packet. Loco KAVACH Position In- 0x12 Stationary KAVACH will send all formation Message packet of Loco Regular / Access Request Packet. TSR Information Message 0x13 The information received from from stationary KAVACH to TSRMS to Stationary KAVACH NMS packet. Adjacent Kavach Information 0x14 The information log in NMS are Command PDI version check Message PDI version check, Heart Beat message, Train Handover Request Message, Train RRI Message, Train Taken Over Message, Train Handover Cancellation message, Train Length Information message, Train Length Acknowledgement, TSL Route Re-quest message, TSL Information message, Field Elements Status Request message & Field element Status Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:12:39 +05'30' Page 5 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 message. Field Input Status Message 0x15 The information received from Stationary KAVACH field input status. Field Inputs Event Message 0x16 The information received from Stationary KAVACH field input event change message. Stationary KAVACH Health 0x17 The health message received Message to NMS Server from Stationary KAVACH. Onboard KAVACH Health 0x18 The health message received Packet to NMS from onboard KAVACH packet. KAVACH Fault message to 0x19 The fault code message received NMS Server from stationary KAVACH. Loco KAVACH RSSI Message 0x20 RSSI samples captured for last one minute on detection of sta- tionary Ragular packet in Loco KAVACH. Stationary KAVACH RSSI 0x21 RSSI samples captured for last Message one minute on detection of sta- tionary Ragular packet in sta- tionary KAVACH. NMS Acknowledge message 0x1F NMS acknowledgement. to KAVACH Subsystem Stationary KAVACH NMS Packet Structure G.3.1 Fields highlighted (marked with Gray color) are of dynamic in size. G.3.2 Loco to Station packet and Station to Loco packets are the RAW packets which are received/transmitted from/to the radio unit except SOF fields (0xA5, 0xC3). SOF fields shall not be included in Loco to Station Packet and Station to Loco packet. G.3.3 Loco to Station Packet SOF and Station to Loco packet SOF fields should be repeated for all the packets. Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:12:57 +05'30' Page 6 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 G.4 NMS Packet Structure for version 4.0 G.4.1 Stationary KAVACH information Message to NMS server Field Field Description Field Comment No Width (Byte) 1 Start of Frame (SOF) 2 0xAAAA 2 Message Type 1 0x11 3 Message Length 2 In Bytes from field “Message Type” to “CRC” (inclusive of both) 4 Message Sequence 2 0-65535 5 Stationary KAVACH ID 2 Unique Code, Valid values from 1 to 65535 (Purchaser Railway to Decide) 6 NMS system ID 2 It is one of the stationary KA- VACH ID 7 System Version 1 0x00-Version 3.2 0x01- Version 4.0 8 Date 3 DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: not used; 255: month un- known 01-31: official day; 0, 32- 254: not used; 255: day un- known Eg: 27/04/18 → 0x1B-0x04- 0x12 9 Time 3 HH:MM:SS (IST time- Configu- rable) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not used, 255: minutes un- known 00-59: official seconds, 60-254: not used, 255: seconds un- known Eg: 06:36:10 → 0x06-0x24-0x0A 10 Station Active Radio 1 0xF1: if Radio 1 is active. 0xF2: if Radio 2 is active. 0xE1: if Ethernet 1 is active. 0xE2: if Ethernet 2 is active. Any other data: Active radio un- Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:13:14 +05'30' Page 7 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Byte) known 11 SOF Tx byte 1 1 0xA5 12 SOF Tx byte 2 1 0xC3 Station Regular / Access Authority / Additional Emergency Packet / etc. (As per KAVACH Radio Communication Protocol) 13 CRC 4 CCITT- 32 Bit CRC (0x04C11DB7) excluding SOF field. G.4.2 Loco KAVACH Position Information Message: For Every cycle (1 cycle = 2s) when locos registered with SKAVACH. Field Field Field Descrip- Width Comment No tion (Bytes) Start of Frame 1 2 0xAAAA (SOF) 2 Message Type 1 0x12 In Bytes from field “Message Type” to 3 Message Length 2 “CRC” (inclusive of both) Message Se- 4 2 0-65535 quence Stationary KA- Unique Code, Valid values from 1 to 5 2 VACH ID 65535 (Purchaser Railway to Decide) 6 NMS system ID 2 It is one of the stationary KAVACH ID 7 System Version 1 1 DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: 8 Date 3 not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 HH:MM:SS (IST time) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not 9 Time 3 used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:13:31 +05'30' Page 8 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Field Descrip- Width Comment No tion (Bytes) Onboard Active 1 0xF1: if Radio 1 is active. Radio 0xF2: if Radio 2 is active. 0xE1: if Ethernet 1 is active. 10 0xE2: if Ethernet 2 is active. Any other data: Active radio un- known 11 SOF Tx byte 1 1 0xA5 12 SOF Tx byte 2 1 0xC3 Loco Regular / Access Request Packet (As per KAVACH Radio Communi- cation Protocol) No of MA section Defines the train route in which MA 13 1 count is extended. List of MA sections starting from 14 Route ID 2 train front end occupied section to EOA section. CCITT- 32 Bit CRC (0x04C11DB7) 15 CRC 4 excluding SOF (0xAAAA) field. G.4.3 TSR Information Message from stationary KAVACH to NMS Field Field Descrip- Field Comment No tion Width (Bytes) Start of Frame 1 2 0xAAAA (SOF) 2 Message Type 1 0x13 In Bytes from field “Message Type” 3 Message Length 2 to “CRC” (inclusive of both) Message Se- 4 2 0-65535 quence Stationary KA- 5 2 VACH ID 6 NMS system ID 2 7 System Version 1 1 Pavan Digitally signed by Pavan Kumar Kumar Date: 2024.07.16 17:13:51 +05'30' Page 9 of 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Descrip- Field Comment No tion Width (Bytes) DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: 8 Date 3 not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 HH:MM:SS (IST time) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not 9 Time 3 used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A All TSR Information message (As per TSRMS-SKAVACH Commu- nication Protocol) (Command PDI version check, Message PDI version check, All TSR 10 Information message, Get TSR Information message, SKAVACH TSR data message, TSR Data Integrity test message) CCITT- 32 Bit CRC (0x04C11DB7) 11 CRC 4 excluding SOF field. G.4.4 Adjacent Kavach Information: When handover of Train is in progress. Field Field Field Description Width Comment No (Bytes) Start of Frame 1 2 0xAAAA (SOF) 2 Message Type 1 0x14 In Bytes from field “Message Type” to 3 Message Length 2 “CRC” (inclusive of both) 4 Message Sequence 2 0-65535 Stationary KAVACH Unique Code, Valid values from 1 to 5 2 ID 65535 (Purchaser Railway to Decide) 6 NMS system ID 2 It is one of the stationary KAVACH ID 7 System Version 1 1 Pavan Digitally signed by Pavan Kumar Page 10 of Kumar Date: 2024.07.16 17:14:07 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Field Description Width Comment No (Bytes) DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: 8 Date 3 not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 HH:MM:SS (IST time) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not 9 Time 3 used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A As per SKAVACH-SKAVACH Communication Protocol) Command PDI version check Message PDI version check, Heart Beat message, Train Handover Re- quest Message,Train RRI Message, Train Taken Over Message, Train 10 Handover Cancellation message Train Length Information message, Train Length Acknowledgement, TSL Route Request message, TSL In- formation message, Field Elements Status Request message & Field element Status message. CCITT- 32 Bit CRC (0x04C11DB7) 11 CRC 4 excluding SOF field. G.4.5 Field Input Status Message: On power on of SKAVACH, On Link fail recovery & periodically defined by Railways (for play back rea- son) Field Field Description Field Comment No Width (Bytes) 1 Start of Frame (SOF) 2 0xAAAA 2 Message Type 1 0x15 3 In Bytes from field “Message Type” Message Length 2 to “CRC” (inclusive of both) 4 Message Sequence 2 0-65535 5 Stationary KAVACH Unique Code, Valid values from 1 to ID 2 65535 (Purchaser Railway to Decide) Pavan Digitally signed by Pavan Kumar Page 11 of Kumar Date: 2024.07.16 17:14:22 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) 6 It is one of the stationary KAVACH NMS system ID 2 ID 7 System Version 1 1 8 DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown Date 3 01-12: official month; 0,13 to 254: not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 9 HH:MM: SS (IST time) 00-23: official hour; 24-254: not used; 255: hour unknown Time 3 00-59: official minutes, 60-254: not used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A 10 The total number of relays (in bytes) for which information is transmitted Total Event Relays in (E) 2 this packet shall be specified. 11 Each bit indicates status of each in- put. („0' – Drop, '1' – Pickup) LSB of first byte indicates status of first input. This data contains status of all Track Identification Numbers (TIN) and Station Inputs. Round Status of all TINs (0 to 255) shall be Relay Status Image off (E/8) framed first while preparing the Bytes packet. All TINs status shall be sent irre- spective of TIN allocation in the Sta- tion. First input of Stationary KAVACH shall start from 256th bit. Relay status image shall be multiple of 8. Unconnected/Unallocated in- puts shall be filled with Zero. Pavan Digitally signed by Pavan Kumar Page 12 of Kumar Date: 2024.07.16 17:14:38 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) Ex: If No. of Stationary KAVACH in- puts is 66, Relay Status image shall be 25 Bytes (32 bytes TIN + 9 bytes Sta- tionary KAVACH inputs). 12 CCITT- 32 Bit CRC (0x04C11DB7) CRC 4 excluding SOF field. G.4.6 Field Inputs Event Message: On change of any relay status. Field Field Description Field Comment No Width (Bytes) 1 Start of Frame 2 0xAAAA (SOF) 2 Message Type 1 0x16 3 Message Length 2 In Bytes from field “Message Type” to “CRC” (inclusive of both) 4 Message Sequence 2 0-65535 5 Stationary KAVACH 2 Unique Code, Valid values from 1 to ID 65535 (Purchaser Railway to Decide) 6 NMS system ID 2 It is one of the stationary KAVACH ID 7 System Version 1 1 8 Date 3 DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 9 Time 3 HH:MM:SS (IST time) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A 10 Relay Event Count 1 Total events detected in same time Pavan Digitally signed by Pavan Kumar Page 13 of Kumar Date: 2024.07.16 17:14:56 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) 11 Relay Address 2 12 Relay Status 1 0x00 – Drop Down 0x01 – Picked Up 13 CRC 4 CCITT- 32 Bit CRC (0x04C11DB7) excluding SOF field. G.4.7 Stationary KAVACH Health Message to NMS Server Field Field Description Field Comment No Width (Bytes) 1 Start of Frame 2 0xAAAA (SOF) 2 Message Type 1 0x17 3 Message Length 2 In Bytes from field “Message Type” to “CRC” (inclusive of both) 4 Message Sequence 2 0-65535 5 Stationary KA- 2 Unique Code, Valid values from 1 to VACH ID 65535 (Purchaser Railway to Decide) 6 NMS system ID 2 It is one of the stationary KAVACH ID 7 System Version 1 1 8 Date 3 DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 9 Time 3 HH:MM:SS (IST time) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A 10 Event Count 1 11 Event Id 2 Stationary KAVACH Health 12 Event Data m 13 CRC 4 CCITT- 32 Bit CRC (0x04C11DB7) ex- cluding SOF field. Pavan Digitally signed by Pavan Kumar Page 14 of Kumar Date: 2024.07.16 17:15:13 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) Event Field 1. System Tempera- 1 System Temperature value (1 byte ture Signed) - On change of temperature by 3oC 2. Active Radio Num- 1 0: not used ber 1: Radio 1 2: Radio 2 3: Both Radio active 3. Radio-1 Health 1 1: OK 2: Diagnostic Link Fail 3: Radio Fail 4. Radio-2 Health 1 1: OK 2: Diagnostic Link Fail 3: Radio Fail 5. Radio-1 Input sup- 1 Value: 10V-30V ply - On change of voltage by 1V 6. Radio-2 Input sup- 1 Value: 10V-30V ply - On change of voltage by 1V 7. Radio-1 Tempera- 1 Value: -30oC to 70oC (1 byte Signed) ture - On change of temperature by 3oC 8. Radio-2 Tempera- 1 Value: -30oC to 70oC (1 byte Signed) ture - On change of temperature by 3oC 9. Radio-1 PA Tem- 1 Value:20oC to 100oC perature - On change of temperature by 3oC 10. Radio-2 PA Tem- 1 Value:20oC to 100oC perature - On change of temperature by 3oC 11. Radio-1 PA Supply 1 Value: 11V-13V Voltage - On change of voltage by 1V 12. Radio-2 PA Supply 1 Value: 11V-13V Voltage - On change of voltage by 1V 13. Radio-1 Tx PA Cur- 1 Value: 1.5A to 3.2A rent - On change of current 14. Radio-2 Tx PA Cur- 1 Value: 1.5A to 3.2A rent - On change of current 15. Radio-1 Reverse 1 Value received from Radio Power Eg: Value received from Radio is 0x01 = 0.1W (Value: 0x01) - on Change of Reverse power by 0.1W 16. Radio-2 Reverse 1 Value received from Radio Power Eg: Value received from Radio is 0x0F = 1.5W (Value: 0x0F) - on Change of Reverse power by 0.1W 17. Radio-1 Forward 1 Value received from Radio Pavan Digitally signed by Pavan Kumar Page 15 of Kumar Date: 2024.07.16 17:15:29 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) Power Eg: Value received from Radio is 0x36 = 5.4W (Value: 0x36) - on Change of Forward power by 0.1W 18. Radio-2 Forward 1 Value received from Radio Power Eg: Value received from Radio is 0x78 = 12W (Value: 0x78) - on Change of Forward power by 0.1W 19. Current Running 1 0: Default key set, Key 1-30: KMS key set - on change of Key Set 20. Remaining Number 1 0: No keys, of Keys 1-30: Remaining KMS key sets - on change of value 21. Session Key 2 Checksum of 16 bytes session key Checksum - for every 2s at the time of Authentica- tion only 22. Allocated time slot 1 1-50 for new loco - for every 2s at the time of Authentica- tion only 23. New Loco Regular 2 0-2000ms packet received - At the time of successful registration time offset only 24. Loco Count 1 Value: 0-50 Noof Locos supervised by Stationary KA- VACH - On change of value 25. Radio-1 Rx Packet 1 Value: 0-50 Count Total Loco regular packets received from Radio-1 in 2s time frame - for every 2s time frame when locos are present 26. Radio-2 Rx Packet 1 Total Loco regular packets received from Count Radio-2 in 2s time frame - for every 2s time frame when locos are present 27. Active GPS Number 1 Gps used for frame number calculation 0 – No Active GPS 1 – GPS 1 2 – GPS 2 3 – Both GPS - on change of GPS 28. GPS-1 View 1 0 – No Data 1–V Pavan Digitally signed by Pavan Kumar Page 16 of Kumar Date: 2024.07.16 17:15:47 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) 2–A - on detection of change of event 29. GPS-2 View 1 0 – No Data 1–V 2–A - on detection of change of event 30. GPS-1 Seconds 1 0 to 59 seconds - on change of value for every one hour. 31. GPS-2 Seconds 1 0 to 59 seconds - on change of value for every one hour. 32. GPS-1 Satellites in 1 Value received from GPS receiver View - On change of value for every one hour. 33. GPS-1 CNO (Max) 1 Maximum CNO Value received from GPS receiver - On change of value for every one hour. 34. GPS-2 Satellites in 1 Value received from GPS receiver View - On change of value for every one hour. 35. GPS-2 CNO (Max) 1 Maximum CNO Value received from GPS receiver - On change of value for every one hour. 36. GSM-1 RSSI 1 Value received from GSM module - for every 30 minutes 37. GSM-2 RSSI 1 Value received from GSM module - for every 30 minutes 38. Missing RFID 2 - on detection of Missing RFID 39. Invalid RFID 2 - on detection of Invalid RFID 40. Conflict Route 2 - on detection of conflicting route RFID RFID 41. Conflicting TIN 2 Conflicting TIN in the route occupied by another train - On detection of event 42. Missing TIN 2 TIN which is cleared due to RFID reader failure - On detection of event or missing of con- secutive 43. Loco Specific SoS 4 B3 to B1: Loco ID B0: SoS Code given below 1: SoS generated due to wrong route Tag 2: SoS due to collision detection 3: SoS due to shunt limits violation 4: SoS due to Invalid position report 5: SoS due to signal set to conflicting route Pavan Digitally signed by Pavan Kumar Page 17 of Kumar Date: 2024.07.16 17:16:05 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) - On detection of event 44. Train exit mode 4 B3 to B1: Loco ID B0: Exit Code given below 1: Loco exit due to unknown direction in SR or SB mode 2: Loco exit due to out of station bound- ary 3: Loco exit due to specific mode (IS or NL mode) 4: Loco exit due to authentication failure 5: Loco exit due to communication timeout 6. Exit due to Train Handover. 7. Exit due to Handover cancellation - On detection of event 45. Station Modules 2 b15-b4: Module ID Health b3-b0: Module Health - On detection of event 46- Reserved 199 200- Firm specific 2 This field Information is specific to KA- 254 events VACH firm 255 Specific value Not to be used G.4.8 Onboard KAVACH Health Packet to NMS Event Onboard KAVACH Field Description ID Health Width (Bytes) 1. Start of Frame 2 0xBBBB (SOF) 2. Message Type 1 0x18 3. Message Length 2 In Bytes from field “Message Type” to “CRC” (inclusive of both) 4. Message Sequence 2 0-65535 5. Onboard KAVACH 3 ID 6. NMS System ID 2 Onboard KAVACH shall identify the NMS system ID from domain name server / Stationary KAVACH shall send the NMS ID during session es- tablishment 7. System Version 1 1 Pavan Digitally signed by Pavan Kumar Page 18 of Kumar Date: 2024.07.16 17:16:19 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 8. Date 3 DD/MM/YY (IST Time- Configura- ble) 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 9. Time 3 HH:MM:SS (IST time-Configurable) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A 10. Event Count 1 11. Event Id 2 Onboard KAVACH Health 12. Event Data m 13. CRC 4 CCITT- 32 Bit CRC (0x04C11DB7) excluding SOF field. Event Loco KAVACH Field Description ID Health Width (Bytes) – m 1. Radio-1 Health 1 1: OK 2: Diagnostic Link Fail 3: Radio Fail 2. Radio-2 Health 1 1: OK 2: Diagnostic Link Fail 3: Radio Fail 3. Radio-1 Input sup- 1 Value: 10V-30V ply - On change of voltage by 1V 4. Radio-2 Input sup- 1 Value: 10V-30V ply - On change of voltage by 1V 5. Radio-1 Tempera- 1 Value: -30oC to 70oC (1 byte Signed) ture - On change of temperature by 3oC 6. Radio-2 Tempera- 1 Value: -30oC to 70oC (1 byte Signed) ture - On change of temperature by 3oC 7. Radio-1 PA Tem- 1 Value:20oC to 100oC perature - On change of temperature by 3oC 8. Radio-2 PA Tem- 1 Value:20oC to 100oC perature - On change of temperature by 3oC 9. Radio-1 PA Supply 1 Value: 11V-13V Voltage - On change of voltage by 1V Pavan Digitally signed by Pavan Kumar Page 19 of Kumar Date: 2024.07.16 17:16:39 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 10. Radio-2 PA Supply 1 Value: 11V-13V Voltage - On change of voltage by 1V 11. Radio-1 Tx PA Cur- 1 Value: 1.5A to 3.2A rent - On change of current 12. Radio-2 Tx PA Cur- 1 Value: 1.5A to 3.2A rent - On change of current 13. Radio-1 Reverse 1 Value received from Radio Power Eg: Value received from Radio is 0x01 = 0.1W (Value: 0x01) 14. Radio-2 Reverse 1 Value received from Radio Power Eg: Value received from Radio is 0x0F = 1.5W (Value: 0x0F) 15. Radio-1 Forward 1 Value received from Radio Power Eg: Value received from Radio is 0x36 = 5.4W (Value: 0x36) 16. Radio-2 Forward 1 Value received from Radio Power Eg: Value received from Radio is 0x78 = 12W (Value: 0x78) 17. Stationary Regular 2 0-2000 ms (While establishing com- packet received munication with Stationary KAVACH) time offset 18. Active GPS Number 1 Gps used for frame number calcula- tion 0 – No Active GPS 1 – GPS 1 2 – GPS 2 3 – Both GPS - on change of GPS 19. GPS-1 View Status 1 0 – No Data 1–V 2–A - on detection of change of event 20. GPS-2 View Status 1 0 – No Data 1–V 2–A - on detection of change of event 21. GPS-1 Seconds 1 0 to 59 seconds - on change of value for every one hour 22. GPS-2 Seconds 1 0 to 59 seconds - on change of value for every one hour 23. GPS-1 Satellites in 1 Value received from GPS receiver View - On change of value for every one hour 24. GPS-1 CNO (Max) 1 Maximum CNO Value received from Pavan Digitally signed by Pavan Kumar Page 20 of Kumar Date: 2024.07.16 17:16:57 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 GPS receiver - On change of value for every one hour 25. GPS-2 Satellites in 1 Value received from GPS receiver View - On change of value for every one hour 26. GPS-2 CNO (Max) 1 Maximum CNO Value received from GPS receiver - On change of value for every one hour 27. GPS-1 link status 2 0-Both GPS link and PPS fail 1- GPS link fail and PPS ok 2- GPS link ok and PPS fail 3- GPS link ok and PPS ok - On change of event for every one hour 28. GPS-2 link status 2 0-Both GPS link and PPS fail 1- GPS link fail and PPS ok 2- GPS link ok and PPS fail 3- GPS link ok and PPS ok - On change of event for every one hour 29. GSM-1 RSSI 1 Value received from GSM module - On change of value for every one hour 30. GSM-2 RSSI 1 Value received from GSM module - On change of value for every one hour 31. Current Running 1 0: Default key set, Key 1-30: KMS key set - on change of Key Set 32. Remaining Number 1 0: No keys, of Keys 1-30: Remaining KMS key sets - on change of value 33. Session Key 2 Checksum of 16 bytes session key Checksum - for every 2s at the time of Authen- tication only 34. DMI-1 link status 2 0-NOT OK 1-OK - On change of event 35. DMI-2 link status 2 0-NOT OK 1-OK - On change of event 36. RFID Reader-1 link 2 0-NOT OK status 1-OK - On change of event 37. RFID Reader-2 link 2 0-NOT OK Pavan Digitally signed by Pavan Kumar Page 21 of Kumar Date: 2024.07.16 17:17:14 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 status 1-OK - On change of event 38. Duplicate Missing 2 RFID Tag Number RFID Tag 39. Missing linked 4 B3-B1: Linked RFID Tag RFID Tag B0: Linking direction 40. Computed TLM 4 B3-B2: Station Id Status B1-B0: TLM Status b11-b0: Computed TLM Value b15-b12: TLM Status TLM Status: 0- TLM Failed 1 – TLM Updated 2 – TLM Timeout 41. Train Configuration 1 0 – No change 1 – Yes 42. Bootup Sequence 1 0 – Brake Test failed Error 1 – MR not available - On detection of event 43. Selected Train for- 1 1 - Light Engine (120kmph) mation 2 - Light Engine Multi (120kmph) 3 - Passenger Train 3 to 7 Coach (120kmph) 4 - Passenger Train 8 to 13 Coach (120kmph) 5 - Passenger Train 14 to 20 Coach (120kmph) 6 - Passenger Train 21 to 27 Coach(120kmph) 7 - Goods 59 BOXN Empty (1000 - 1999 Ton, 75kmph) 8 - Goods 59 BOXN Half Load(2000 -3499 Ton, 75kmph) 9 - Goods 59 BOXN Full Load(3500 -5500 Ton, 60kmph) 10 - Goods 42 BCN Empty (1000 - 1999 Ton, 75kmph) 11 - Goods 42 BCN Half Load(2000 - 3499 Ton, 75kmph) 12 - Goods 42 BCN Full Load(3500 - 5500 Ton, 60kmph) 13 - Light Engine WAP5 (170kmph) 14 - WAP5-8LHB Coaches (170kmph) 15 - Light Engine WAP7 (140kmph) - On detection of event Pavan Digitally signed by Pavan Kumar Page 22 of Kumar Date: 2024.07.16 17:17:28 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 44. Selected Cab 1 0 – No Cab Selected 1 – Cab1 Selected 2 – Cab2 Selected 3 – Both Cabs Selected - On detection of event 45. Brake application 1 0-Not used reason 1-Reverse movement detected 2-Unusual stoppage detected 3-Overspeed 4-Rollback detected 5-MBT selected 6- No LP Acknowledge 7- MA Shortened 8-Headon collision detected 9-Rearend collision detected 10-Loco Specific SoS received 11-Station General SoS received - On detection of event 46. Station General 3 B2-B1: Station Id SoS B0: General SoS status (1 – Re- ceived, 2 – Cancelled) - On detection of event 47. Station Loco Spe- 3 B2-B1: Station Id cific SoS B0: Specific SoS status (1 – Re- ceived, 2 – Cancelled) - On detection of event 48. Collision Detection 4 B3-B1: Loco Id B0: SoS code Values: 1 – Manual SoS received 2 – Manual SoS cancelled 3 – Unusual stopage detected 4 – Unusual stopage end 5 – Head-on collision detected 6 – Head-on collision end 7 – Rear-end collision detected 8 – Rear-end collision end 9 – Train parting detected 10 – Train parting end - On detection of event 49. Loco Self SoS 1 1 – Manual SoS 2 – Manual SoS end 3 – Unusual stopage start 4 – Unusual stopage end - On detection of event 50. KAVACH Connec- 1 1 – KAVACH Isolated tion 2 – KAVACH Connected Pavan Digitally signed by Pavan Kumar Page 23 of Kumar Date: 2024.07.16 17:17:45 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 - On detection of event 51. BIU Isolated 1 1 – BIU Isolated 2 – BIU Connected 52. EB Bypassed 1 1 – EB Connected 2 – EB Bypassed - On detection of event 53. KAVACH Territory 1 1 – KAVACH Entry 2 – KAVACH Exit 3 – ETCS Entry 4 – ETCS Exit - On detection of event 54. Brake Interface Er- 1 IRAB ror CCB E70 55. Onboard KAVACH 2 b15-b4: Module ID Modules Health b3-b0: Module Health Module Health: 0-NOT OK 1-OK - On detection of event 56. Conflict Route 2 -On detection of conflicting route RFID RFID 57. Train configuration 4 This is Train Configuration Check- data checksum sum selected by LP 58- Reserved 199 200- Firm specific events 2 This field Information is specific to 254 KAVACH firm 255 Specific value Not to be used G.4.9 KAVACH Fault message to NMS Server Field Field Description Field Comment No Width (Bytes) 1 Start of Frame (SOF) 2 0xAAAA (E1 Channel/Network Channel) 0xBBBB (GPRS Channel) 2 Message Type 1 0x19 3 Message Length 2 In Bytes from field “Message Type” to “CRC” (inclusive of both) 4 Message Sequence 2 0-65535 Last received KAVACH subsystem message sequence number 5 KAVACH Subsystem 3 ID Pavan Digitally signed by Pavan Kumar Page 24 of Kumar Date: 2024.07.16 17:18:01 +05'30' 38 Manish Kumar Gupta R. N. Singh M. M. Srivastava G. Pavan Kumar SSE/S&T/RDSO ADE/S&T/RDSO Director/Signal-IV ED/Telecom-II  ISO 9001: 2015 Effective from 16.07.2024 RDSO/SPN/196/2020 Version 4.0 Document Title: Annexure-G - Specification of Kavach (The Indian Railway ATP)- Network Monitoring System Protocol Amdt-4 Field Field Description Field Comment No Width (Bytes) 6 NMS System ID 2 Loco KAVACH shall identify the NMS system ID from domain name server / Stationary KAVACH shall send the NMS ID during session establish- ment 7 System Version 1 8 Date 3 DD/MM/YY 00-99: official year; 100-254: not used; 255: year unknown 01-12: official month; 0,13 to 254: not used; 255: month unknown 01-31: official day; 0, 32-254: not used; 255: day unknown Eg: 27/04/18 → 0x1B-0x04-0x12 9 Time 3 HH:MM:SS (IST time) 00-23: official hour; 24-254: not used; 255: hour unknown 00-59: official minutes, 60-254: not used, 255: minutes unknown 00-59: official seconds, 60-254: not used, 255: seconds unknown Eg: 06:36:10 → 0x06-0x24-0x0A 10 KAVACH subsystem 1 0x11 – Stationary KAVACH type 0x22 – Onboard KAVACH 0x33 – TSRMS 11 Total Fault Codes (F) 1 Max number of faults shall be 10 12 Module ID 1 Firm Specific 13 Fault Code Type 1 1: Fault Code 2: Recovery Code 14 Fault Code 2 Firm Specific 15 CRC 4 CCITT- 32 Bit CRC (0x04C11DB7) excluding SOF