Stationary KAVACH Units Overview
118 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the maximum number of Stationary KAVACH units allowed in one E1/Ethernet ring?

  • 10 (correct)
  • 15
  • 5
  • 20

    • What is the value associated with the Stationary KAVACH information message sent to the NMS?

  • 0x13
  • 0x12
  • 0x14
  • 0x11 (correct)

    • Which type of message is sent by the Stationary KAVACH regarding Loco information?

  • TSR Information Message
  • Stationary KAVACH Information Message
  • Emergency Packet Message
  • Loco KAVACH Information Message (correct)

    • What does the TSR Information Message facilitate?

    <p>Receiving information from TSRMS</p> Signup and view all the answers

    What does the acronym NMS stand for in this context?

    <p>Network Management System</p> Signup and view all the answers

    What does the first byte in the Date field represent?

    <p>The official year</p> Signup and view all the answers

    Which range of values indicates an unknown day in the Date field?

    <p>255 only</p> Signup and view all the answers

    What is the width of the Time field in bytes?

    <p>3</p> Signup and view all the answers

    In the Time field, what does a value of 255 signify?

    <p>Unknown minutes</p> Signup and view all the answers

    What type of message does the field designated for 'All TSR Information' contain?

    <p>Multiple types of TSR related messages</p> Signup and view all the answers

    What is the CRC used in the document specified?

    <p>CCITT-32 Bit CRC</p> Signup and view all the answers

    How is the hour represented in the Time field?

    <p>00-23</p> Signup and view all the answers

    Which field has a total byte width of 4?

    <p>CRC field</p> Signup and view all the answers

    What is the width in bytes of the Relay Address field?

    <p>2</p> Signup and view all the answers

    Which value indicates that the Relay Status has been 'Picked Up'?

    <p>0x01</p> Signup and view all the answers

    What is the significance of the CRC field in this protocol?

    <p>To verify data integrity</p> Signup and view all the answers

    What is the maximum value for the Message Sequence number?

    <p>65535</p> Signup and view all the answers

    What format is used for the Date field in the protocol?

    <p>DD/MM/YY</p> Signup and view all the answers

    What are the valid values for the Stationary KAVACH ID?

    <p>1 to 65535</p> Signup and view all the answers

    What does the field 'Event Data' represent?

    <p>Additional data related to the event</p> Signup and view all the answers

    Which byte is used to indicate the Message Type?

    <p>Field 2</p> Signup and view all the answers

    What is the hexadecimal representation of the Start of Frame (SOF)?

    <p>0xAAAA</p> Signup and view all the answers

    How many bytes are allocated for the Time field?

    <p>3</p> Signup and view all the answers

    What is the temperature range for Radio-2 Temperatures?

    <p>-30oC to 70oC</p> Signup and view all the answers

    What voltage range is indicated for Radio-1 PA Supply Voltage?

    <p>11V-13V</p> Signup and view all the answers

    On what change is the Radio-1 Tx PA Current measured?

    <p>On change of current</p> Signup and view all the answers

    What happens to the value received from Radio for Reverse Power for Radio-1 when the power changes?

    <p>Changes by 0.1W</p> Signup and view all the answers

    What is the specified range for Reverse Power for Radio-2?

    <p>0.1W to 1.5W</p> Signup and view all the answers

    What is the value change specification for Radio-1 and Radio-2 Temperatures?

    <p>On change of temperature by 3oC</p> Signup and view all the answers

    What limits are set for Radio-2 Tx PA Current?

    <p>1.5A to 3.2A</p> Signup and view all the answers

    What is the change specification for Radio-2 PA Temperature?

    <p>On change of temperature by 3oC</p> Signup and view all the answers

    What is the hexadecimal value that corresponds to a power value of 1.5W received from Radio-2?

    <p>0x0F</p> Signup and view all the answers

    Which value indicates that both GPS-1 and GPS-2 are active?

    <p>3</p> Signup and view all the answers

    What is the maximum power value represented by the hexadecimal value 0x78?

    <p>12W</p> Signup and view all the answers

    What does the GPS-1 View Status value of 2 represent?

    <p>Data Acquired</p> Signup and view all the answers

    When does the value for GPS-1 Seconds change?

    <p>Upon every hour change</p> Signup and view all the answers

    What is indicated by a value of 0 in the GPS-2 View Status?

    <p>Data Unavailable</p> Signup and view all the answers

    Which packet is related to the delay in establishing communication with Stationary KAVACH?

    <p>Regular Stationary packet</p> Signup and view all the answers

    What is the hexadecimal value that corresponds to a power value of 0.1W?

    <p>0x01</p> Signup and view all the answers

    What is the valid range for the Stationary KAVACH ID?

    <p>1-65535</p> Signup and view all the answers

    What does a value of 0 in the hour field of the Time section indicate?

    <p>Midnight</p> Signup and view all the answers

    Which of the following correctly describes the representation of the Date format in the protocol?

    <p>Day-Month-Year</p> Signup and view all the answers

    In the Time field, what does a value of 254 represent for minutes?

    <p>Not used</p> Signup and view all the answers

    How is the maximum Message Length defined in bytes?

    <p>0-65535</p> Signup and view all the answers

    What is indicated by a System Version of 255?

    <p>Year unknown</p> Signup and view all the answers

    Which field requires validation to be within a specific range according to purchaser's decision?

    <p>Stationary KAVACH ID</p> Signup and view all the answers

    What is the main purpose of the Message Sequence field?

    <p>To sequence messages</p> Signup and view all the answers

    What is the primary function of the KAVACH NMS Network as described in the document?

    <p>To monitor and manage train control systems remotely</p> Signup and view all the answers

    Which communication method is utilized for data exchange between Stationary KAVACH units?

    <p>Ethernet protocol over E1 interface</p> Signup and view all the answers

    What role does the Event Logger module serve in the KAVACH system?

    <p>To log vital events and messages exchanged by the KAVACH units</p> Signup and view all the answers

    What system does the NMS protocol allow modifications without affecting the executive logic of the vital card?

    <p>KAVACH network structure</p> Signup and view all the answers

    How do Stationary KAVACH units connect to form a cohesive network?

    <p>Using E1 interface connections to adjacent KAVACH units</p> Signup and view all the answers

    What type of information is exchanged between Stationary KAVACH units and the Network Management System?

    <p>Signal aspects, track occupancy, and loco position</p> Signup and view all the answers

    What is a key feature of the KAVACH NMS regarding its network monitoring capability?

    <p>It centralizes monitoring for a group of stations</p> Signup and view all the answers

    What is the valid range of values for the official day in the Date field?

    <p>1-31</p> Signup and view all the answers

    What communication method allows the KAVACH units to relay diagnostic messages?

    <p>Predefined packet structures using E1 interface</p> Signup and view all the answers

    What does a value of 2 in the Radio-1 Health field signify?

    <p>Diagnostic Link Fail</p> Signup and view all the answers

    In the Time field, which value indicates that the minute is unknown?

    <p>255</p> Signup and view all the answers

    How many bytes is allocated for the Event Count field?

    <p>1</p> Signup and view all the answers

    What is the hexadecimal representation of a valid time of 07:15:45?

    <p>0x07-0x15-0x2D</p> Signup and view all the answers

    What does the width of the Event Id field measure in bytes?

    <p>2</p> Signup and view all the answers

    Which value represents a Radio Fail in the Radio-2 Health field?

    <p>2</p> Signup and view all the answers

    What is the designated CRC calculation method used in this protocol?

    <p>CRC-32</p> Signup and view all the answers

    What does a System Version value of 1 signify in the protocol?

    <p>It indicates the first version was implemented.</p> Signup and view all the answers

    In the date field, what does a value of 100-254 indicate?

    <p>An unused year.</p> Signup and view all the answers

    What is the width of the Total Event Relays field in bytes?

    <p>2 bytes</p> Signup and view all the answers

    Which range indicates an official month in the Date field?

    <p>01-12</p> Signup and view all the answers

    What does a value of 0 in the Time field signify for minutes?

    <p>Valid official minute</p> Signup and view all the answers

    In the Time field, what byte width is allocated for representing seconds?

    <p>3 bytes</p> Signup and view all the answers

    What is the purpose of the Time field within the packet?

    <p>To provide a timestamp in IST</p> Signup and view all the answers

    Which of the following represents a valid date format as an example?

    <p>25/12/20</p> Signup and view all the answers

    What is the maximum number of faults that can be recorded in the Total Fault Codes field?

    <p>10</p> Signup and view all the answers

    Which value in the Date field represents an unknown month?

    <p>255</p> Signup and view all the answers

    Which hexadecimal value corresponds to the Stationary KAVACH subsystem type in the document?

    <p>0x11</p> Signup and view all the answers

    What does a value of 0x22 signify in the KAVACH subsystem type?

    <p>Onboard KAVACH</p> Signup and view all the answers

    In the representation of the Time field, what does a value of 255 mean for the seconds?

    <p>Seconds unknown</p> Signup and view all the answers

    How many bytes are allocated for the CRC field in the protocol specification?

    <p>4</p> Signup and view all the answers

    What range of values indicates a fault code type of Recovery Code?

    <p>2</p> Signup and view all the answers

    What is the official representation for an unknown day in the Date field?

    <p>255</p> Signup and view all the answers

    What is the width of the Fault Code field in bytes?

    <p>2</p> Signup and view all the answers

    Which component is identified with the NMS System ID from the domain name server?

    <p>Loco KAVACH</p> Signup and view all the answers

    What is the significance of the Message Length field in the KAVACH protocol?

    <p>Specifies the total number of bytes from the Message Type to the CRC.</p> Signup and view all the answers

    How is the System Version field represented in the protocol?

    <p>As a one-byte binary value.</p> Signup and view all the answers

    What identifies the NMS system ID from the onboard KAVACH in the protocol?

    <p>The NMS System ID field</p> Signup and view all the answers

    Which value range is valid for the Message Sequence field in the KAVACH protocol?

    <p>0 to 65535</p> Signup and view all the answers

    What does the field designated for 'Onboard KAVACH ID' consist of?

    <p>3 bytes specific to the onboard unit.</p> Signup and view all the answers

    Which modification was made to the field 'Registered Loco_Count' in the KAVACH health message?

    <p>It was deleted from the message.</p> Signup and view all the answers

    What is the significance of field -42 in the KAVACH system?

    <p>It is related to the override of missing TIN.</p> Signup and view all the answers

    What was added to the Onboard KAVACH Health Packet regarding time measurement?

    <p>Stationary Regular packet received time offset.</p> Signup and view all the answers

    What is the width in bytes of the field that captures GPS-1 Seconds?

    <p>1</p> Signup and view all the answers

    How frequently does the GPS-2 Satellites in View field update?

    <p>Every hour</p> Signup and view all the answers

    Which packets were newly added in CL.4.10 and CL.4.11 regarding RSSI?

    <p>Stationary KAVACH RSSI Message and Loco KAVACH RSSI Message.</p> Signup and view all the answers

    Which field related to RSSI was deleted from the Stationary KAVACH health message?

    <p>Radio-1 RSSI.</p> Signup and view all the answers

    What value corresponds to a situation where no data is recorded in the GPS-2 View field?

    <p>0</p> Signup and view all the answers

    What change was made regarding fields 20 to 29 in the Onboard KAVACH Health Packet?

    <p>They were modified for every one hour in packet.</p> Signup and view all the answers

    What is the maximum CNO Value received from the GPS receiver as specified for GPS-1?

    <p>0-50</p> Signup and view all the answers

    What is the update frequency for the GSM-1 RSSI field?

    <p>Every 30 minutes</p> Signup and view all the answers

    What does the field 39 in the KAVACH health packet now indicate about TLM status?

    <p>TLM failed is represented by the value 0.</p> Signup and view all the answers

    What range of values is given for GPS-1 Seconds?

    <p>0 to 59 seconds</p> Signup and view all the answers

    What was the purpose of adding field -44 in the KAVACH system?

    <p>To record exits due to specific scenarios like train handover.</p> Signup and view all the answers

    Which field is used to capture the maximum CNO Value received from the GPS receiver?

    <p>GPS-1 CNO (Max)</p> Signup and view all the answers

    What value does the field designated for GSM-2 RSSI reflect?

    <p>Value received from GSM module</p> Signup and view all the answers

    What modification was made to Cl.G.4.7 regarding the KAVACH system?

    <p>It was modified to send health packets to NMS.</p> Signup and view all the answers

    Which clause was recently added to include information about KAVACH fault messages?

    <p>Cl.G.4.8</p> Signup and view all the answers

    What does the modification in Cl.G.4.1 specify regarding the field for Station Active Radio?

    <p>It includes values for identifying Ethernet activity.</p> Signup and view all the answers

    What was deleted in Cl.G.4.4 concerning Adjacent KAVACH Information?

    <p>Field 10 &amp; 11.</p> Signup and view all the answers

    Which of the following modifications was specifically described in Cl.G.2.3?

    <p>Deletion of unnecessary connection statements.</p> Signup and view all the answers

    What information does Cl.G.4.2 convey in terms of onboard Active Radio?

    <p>It specifies the activity status of Ethernet connections.</p> Signup and view all the answers

    What is the purpose of adding a new packet under Cl.4.3?

    <p>To carry the TSR Information Message from stationary KAVACH to NMS.</p> Signup and view all the answers

    Which clause was corrected to align the NMS message structure with Stationary KAVACH?

    <p>Cl.G.3</p> Signup and view all the answers

    Which of the following messages is not included in the information log of the NMS?

    <p>Stationary KAVACH Status Update</p> Signup and view all the answers

    What type of message does the KAVACH system utilize to provide train length information?

    <p>Train Length Acknowledgement</p> Signup and view all the answers

    Which message type is described as providing information concerning the stationary KAVACH?

    <p>Stationary KAVACH Field Input Status Message</p> Signup and view all the answers

    In the context of the KAVACH system, which of the following is a primary function of the Heart Beat message?

    <p>To maintain communication link integrity</p> Signup and view all the answers

    What is the function of the Train Handover Request Message in the KAVACH system?

    <p>To initiate a handover between trains</p> Signup and view all the answers

    Which message is specifically concerned with providing field element status in the KAVACH protocol?

    <p>Field Element Status Request Message</p> Signup and view all the answers

    Which of the following is a key category of information included in the KAVACH NMS data logs?

    <p>Train Taken Over Message</p> Signup and view all the answers

    What type of information does the TSL Route Request message provide?

    <p>Details of the current route taken by the train</p> Signup and view all the answers

    Study Notes

    Stationary KAVACH Units

    • Maximum of 10 Stationary KAVACH units can be utilized in one E1/Ethernet ring architecture.

    Network Monitoring System (NMS) Message Structure from Stationary KAVACH

    • Stationary KAVACH transmits information to NMS server through various message types.
    • Stationary KAVACH Information Message (0x11): Transmits all packets related to Station Regular/Access Authority & Additional Emergency Packets.
    • Loco KAVACH Position Information Message (0x12): Transmits all packets related to Loco Regular/Access Request Packets.
    • TSR Information Message (0x13): Transmits information received from the TSRMS (Train Speed Restriction Management System) to the Stationary KAVACH.

    Field Descriptions in TSR Information Message

    • Date: Uses a 3-byte format representing DD/MM/YY and follows specific conventions for year, month, and day representation.
    • Time: Uses a 3-byte format representing HH:MM:SS (IST time) adhering to specific conventions for hour, minutes, and seconds representation.
    • TSR Information Message: Includes various messages related to TSR data communication between the TSRMS and Stationary KAVACH.
    • CRC: Uses a 4-byte CCITT-32 Bit CRC algorithm excluding the SOF (Start of Frame) field.

    Adjacent Kavach Information

    • When a train handover occurs, information is exchanged using:
      • Relay Address: A 2-byte field indicating the relay's unique identification.
      • Relay Status: A 1-byte field representing the relay's state: 0x00 for "Drop Down" and 0x01 for "Picked Up".
      • CRC: Uses a 4-byte CCITT-32 Bit CRC algorithm excluding the SOF field.

    Stationary KAVACH Health Message

    • Transmitted to NMS server to monitor health parameters.
    • Start of Frame (SOF): Uses a 2-byte identifier (0xAAAA).
    • Message Type: Identifies the message as a Stationary KAVACH Health Message (0x17).
    • Message Length: Represents the message's length in bytes.
    • Message Sequence: A 2-byte field for message sequencing (0-65535).
    • Stationary KAVACH ID: A 2-byte unique code assigned to the Stationary KAVACH (1-65535).
    • NMS System ID: Refers to one of the Stationary KAVACH's ID.
    • System Version: Indicates the current system version (1 in this case).
    • Date: Uses a 3-byte format representing DD/MM/YY, following the established conventions.
    • Time: Uses a 3-byte format representing HH:MM:SS (IST time), following the established conventions.
    • Event Count: Records the number of events occurred.
    • Event ID: Identifies the specific event related to the health status.
    • Event Data: Provides detailed information about the event.
    • CRC: Uses a 4-byte CCITT-32 Bit CRC algorithm excluding the SOF field.
    • Radio-2 Temperature: Reports temperature values between -30°C and 70°C (1 byte signed).
    • Radio-1 PA Temperature: Reports temperature values between 20°C and 100°C.
    • Radio-2 PA Temperature: Reports temperature values between 20°C and 100°C.
    • Radio-1 PA Supply Voltage: Reports voltage values between 11V and 13V.
    • Radio-2 PA Supply Voltage: Reports voltage values between 11V and 13V.
    • Radio-1 Tx PA Current: Reports current values between 1.5A and 3.2A.
    • Radio-2 Tx PA Current: Reports current values between 1.5A and 3.2A.
    • Radio-1 Reverse Power: Reports power values received from the radio.
    • Radio-2 Reverse Power: Reports power values received from the radio.
    • Radio-1 Forward Power: Reports power values received from the radio.
    • Radio-2 Forward Power: Reports power values received from the radio.
    • Stationary Regular Packet Received Time Offset: Reports time offsets during communication establishment with Stationary KAVACH (0-2000 ms).
    • Active GPS Number: Indicates which GPS is active for frame number calculation:
      • 0: No Active GPS
      • 1: GPS 1
      • 2: GPS 2
      • 3: Both GPS
    • GPS-1 View Status: Reports status for GPS 1:
      • 0: No Data
      • 1: V
      • 2: A
    • GPS-2 View Status: Reports status for GPS 2:
      • 0: No Data
      • 1: V
      • 2: A
    • GPS-1 Seconds: Reports seconds value (0 to 59) for every hour.

    KAVACH NMS Protocol

    • KAVACH NMS is built on E1 interface, used for centralized monitoring of KAVACH equipped trains and stations
    • KAVACH NMS collects signals, track occupancy, loco absolute position from Stationary KAVACH units within the network
    • Each Stationary KAVACH (SVK) unit connects to adjacent SVK unit and Network Management System (NMS)
    • SVK units communicate with NMS via predefined packets on the E1 network
    • SVK units exchange Stationary-Stationary communication packets with adjacent SVK units and NMS
    • The same network can be used for connection with the TSRMS network
    • Onboard KAVACH and SVK have event logger modules that store vital events, messages exchanged between radio or other units, and diagnostic related messages
    • Changes in NMS protocol may be possible without changes to the executive logic of the vital card

    Packet Structure

    • Packet structure is defined for communication between Stationary KAVACH units and the NMS
    • The Start of Frame (SOF) field of each packet is 0xAAAA, indicating the start of packet transmission
    • The Message Length field specifies the size of the packet, including itself but excluding the SOF field
    • The Message Sequence counter is incremented by one with each packet transmission
    • The NMS System ID identifies the stationary KAVACH unit within the network
    • The System Version field identifies the software version of the stationary KAVACH unit
    • The Date and Time fields record the current date and time in IST format
    • The Total Event Relays field specifies the number of relays for which information is transmitted within the packet
    • The Event Data field contains information about the current state of the relays
    • The CRC field is used to verify the integrity of the packet

    KAVACH NMS Packet Types

    • Two main packet types are defined:
      • Stationary KAVACH to NMS
      • Loco KAVACH to NMS
    • Stationary KAVACH to NMS packets are used for transmission of system health, event logger information, and relay status data to the NMS
    • Loco KAVACH to NMS packets are used for transmission of loco health status, fault codes and recovery codes to the NMS
    • The KAVACH subsystem type field differentiates packets sent from Stationary KAVACH, Onboard KAVACH, and TSRMS
    • The Total Fault Codes field specifies the maximum number of fault codes that are transmitted
    • Specific fault code types are defined for fault codes and recovery codes
    • The Fault Code field contains the specific fault code or recovery code for the system

    Event ID and Event Data

    • Each Event ID corresponds to a specific event or health status
    • The corresponding Event Data field provides a detailed description of the event
    • This data can be used for monitoring the overall health and status of the KAVACH system
    • Event IDs are specific to Onboard KAVACH and Stationary KAVACH

    KAVACH Health Monitoring

    • The Radio-1 and Radio-2 Health fields indicate the status of the radio communication link
    • Radio health status can be "OK", "Diagnostic Link Fail", or "Radio Fail"
    • The Radio-1 Input Supply field monitors the voltage supply of the communication link
    • The voltage is monitored and a change in voltage by 1V triggers transmission of an updated value to the NMS
    • The event logger module records the health and status of the system in a detailed manner
    • This information helps to track and diagnose any potential issues with the KAVACH system within the network

    KAVACH Fault Codes

    • The Fault Code Type field identifies whether the code represents a fault or a recovery event
    • The Fault Code field contains a specific code representing a detected fault or a recovery event
    • Each fault code and recovery code are specific to the KAVACH system and the manufacturer
    • This information is critical for troubleshooting and identifying the root cause of any malfunctions within the KAVACH system

    KAVACH Network Monitoring System Protocol - Amdt-4

    • G 4.2 Loco KAVACH Position Information Message: A new clause has been added to specify the message format for Loco KAVACH's position information.
    • G 4.3 Adjacent Kavach Information: A new clause has been added to define the message format for exchanging information about adjacent KAVACH systems.
    • G 4.4 Field Input Status Message: A new clause has been added to specify the format for messages that report the status of various field inputs.
    • G 4.5 Field Inputs Event Message: A new clause has been added to describe the format for event messages related to changes in field input values.
    • G 4.7 Onboard KAVACH Health Packet to NMS: This clause has been modified to include changes to the data fields and the frequency of updates for key health parameters.
    • G 4.8 KAVACH Fault message to NMS Server: The format of fault messages sent from the KAVACH system to the NMS server has been modified.
    • G 4.9 NMS Acknowledge message to KAVACH Subsystem: The format of acknowledgment messages sent from the NMS server to the KAVACH subsystem has been modified.
    • G 6.1.1.24: Modified to include an additional fault message.
    • G 2.2: Modified to state that the same network can be used for connecting the Train Supervision and Remote Management System (TSRMS) network.
    • G 2.3: Removed the requirement for connecting IB huts to the nearest station in the T network. Updated figure 1 with new connectivity information for the NMS.
    • G 3: The NMS message structure from stationary KAVACH has been corrected.
    • G 4.1: Modified to include an additional field "Station Active Radio" with values: 0xE1 for Ethernet 1 active, 0xE2 for Ethernet 2 active, and any other value for unknown active radio.
    • G 4.2: Modified to include an additional field "onboard Active Radio" with values: 0xE1 for Ethernet 1 active, 0xE2 for Ethernet 2 active, and any other value for unknown active radio.
    • G 4.3: Added a new packet for the TSR information message sent from stationary KAVACH to the NMS.
    • G 4.4: Deleted field 10 and 11 from the adjacent Kavach Information message.
    • G 4.2: Modified the Loco Regular/ Access Request Packet:
      • Current Route ID: The ID of the current route the train is occupying, defining the route where MA is active.
      • Next Route ID: The approaching signal route ID where the train will enter.
    • G 4.4: Added a "Heart Beat message" field in the Adjacent Kavach Information message.
    • G 4.7: Modified the Stationary KAVACH Health Message to NMS server:
      • Deleted fields: Registered Loco_Count, Loco _ID, Abs_Loc_1, Frequency Channel_Number, Radio-1 RSSI, Abs_Loc_2, Frequency Channel_Number, Radio-2 RSSI.
      • Modified fields 30, 31, 32, 33, 34, 35 to update values every hour.
      • Modified field 42 for "Override Missing TIN".
      • Modified field 44 to include exit reasons: 6.Exit due to Train Handover, 7. Exit due to Handover Cancellation
    • G 4.8: Modified the Onboard KAVACH Health Packet to NMS:
      • Deleted fields: Stationary_KAVACH_ID, Abs_Loc_1, Frequency Channel_Number, Radio-1 RSSI, Abs_Loc_2, Frequency Channel_Number, Radio-2 RSSI.
      • Added field 16 for "Stationary Regular packet received time offset" during communication with Stationary KAVACH.
      • Modified fields 20, 21, 22, 23, 24, 25, 26, 27, 28, 29 to update values every hour.
      • Modified field 39 to include "Computed TLM status" with 0 for TLM failed.
    • G 4.10: Added a new packet for Loco KAVACH RSSI message.
    • G 4.11: Added a new packet for Stationary KAVACH RSSI message.
    • Field Input Status Message: This message is sent from the Stationary KAVACH to the NMS and contains information regarding the field input status.
    • Field Input Status Message Packet Format:
      • Start of Frame (SOF): 2 bytes with value 0xBBBB
      • Message Type: 1 byte with value 0x18
      • Message Length: 2 bytes representing the number of bytes from "Message Type" to "CRC" (inclusive).
      • Message Sequence: 2 bytes with a value range of 0 - 65535.
      • Onboard KAVACH ID: 3 bytes representing the ID of the Onboard KAVACH.
      • NMS System ID: 2 bytes representing the NMS system ID.
      • System Version: 1 byte with a value of 1.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Related Documents

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

    Description

    This quiz explores the functioning and message structures of Stationary KAVACH units within an Ethernet ring architecture. It covers various types of messages transmitted to the NMS server and important field descriptions regarding information exchange. Test your knowledge on the Stationary KAVACH system and its role in train operations.

    More Like This

    Use Quizgecko on...
    Browser
    Open
    Browser
    Browser