SPECIFICATION FOR DATA LOGGER SYSTEM FOR RAILWAY S&T

Microsoft Word - IRS S 992006 Amendment 4 mod 15th OctISO9001:2008 Document No: IRS:S:99/2014 Version No.-4.0 Date Effective :------
Document Title: Draft Specification for Data Logger System for Railway S & T Installation
Prepared By: SSRE/Signal Checked By : ADE/Signal Issued By: Director/Signal-III Printed: Page 1of 132
SPECIFICATION
FOR
October-2014
ISO9001:2008 Document No: IRS:S:99/2014 Version No.-4.0 Date Effective :------
DOCUMENT CONTROL SHEET
Shri M K Mohanty/SSRE
Shri Alok Katiyar/DIRECTOR RDSO Reviewer Prepare
Shri D N Tiwari/ED Tele.
RDSO
AMENDMENTS
February 2002
September 2004
Amendment 4 (details)
1. 1.2 2 Add To clarify The scope of inspection
of Modem & CMU
2. 3.1 4 Modified New parameters to be logged are
added
3. 3.3 3 Modified Output relay capable to drive 24V
Q-Series Relay
4. 3.4 3 Modified Field gear shall not load >2mA
5. 3.4 4 modified Analog input isolation voltage
mentioned. Means of current
7. 3.8 3 Modified To Print in user friendly mode
8. 3.9 3 Modified Format to include location name&
Channel no.
10. 3.10.1&3.10.
annexure
Subsequent
Clause
renumbered
Track circuit and Signal and their
location given in annexure
given
18. 4.2.6 4 Modified Number of fault alarms to be
stored and displayed are given.
19. 4.2.7 4 Modified Provision of synchronization of
time through GPS clock is added.
20. 4.2.8 4 Modified Isolation voltage and method of
isolation clarified
control office digital clock
22. 4.2.10 3 Modified Storing capacity to increase up to
10 lac
memory covered.
Provision of Back-up of data
through USB devise is added.
24. 4.2.12 1&3 Add & Modified To clarify input variation storing
percentage of analog
25. 4.2.16 4 Modified List of Equipment to be monitored
by data logger expanded.
included.
26. 4.2.17 3 Modified Power Supply as per spn 144
27. 4.2.17 4 Modified Crow bar protection for power
supply included
design
30. 4.2.19 4 Modified Networking methods expanded.
Ethernet Channel or OFC is
included.
DL
Digital & 64 Analog
33. 4.2.22 3 Add Termination of All input Like Wago
etc
35. 4.3.1 2 & 3 Modified Specification of PC for CMU
upgraded to state of art &
Sub clause added
36. 4. 3. 2. 1 4 Modified Configuration of PC used as CMU
upgraded
Methodology for monitoring
increased to 64 data loggers.
39. 4.3.8 3 Modified FEP must have capacity to store 10
lac telegrams
40. 4.3.8 4 Modified FEP should have 6 ports and all
ports shall be configurable.
42. 4.3.10 New Data logger user interface software
features added
redundancy
various network elements
45. 5.3 4 Modified Response time given in terms of
sec is modified as data speed to be
maintained in terms of packets per
sec at each stage
46. 5.5 3 Modified Transmission rate to increase up to
57600 BPS
49. 5.6.1 & 5.6.2 4 Deleted Exception reports given as
annexure
51. 6.3.3 4 Deleted Clause contains testing procedure
which already include in
52. 8.3.1 4 Modified Plant and machinery defined as per
SIQ 0001, Version.-1 or latest( STR
for Electronic Signalling
53. 7.1 3 Add Sub clause number given
54. 7.2 3 Modified IR test as per RDSO/SPN/144/2006
& Sub clause added
RDSO/SPN/144/2006 &
56. 7.4 3 Add Applied high voltage test as per
RDSO/SPN/144/2006 & Sub
clause added
DOs and DON’Ts
information to be supplied by
purchaser is added in annexure.
60. 11.2 3 Modified “Additional” ward added
61. 11.4 (c) 2 Delete Deleted against Cl:4.1.(a) (vi)
62. 11.5 &11.5.1 3 Delete Deleted against Cl:4.2.17
63. 11.6 4 New Requirement of network ports
added in information to be
supplied by purchaser
65. Annexure 4 Deleted Replaced by Annexure-A
TABLE OF CONTENTS
1 Foreword 11
2 Scope 12
3 Terminology 12
8 Functional requirements 23
9 Exception report 23
11 Test equipment 24
12 Type tests 24
13 Acceptance test 24
14 Routine test 25
15 Test procedure 25
16 Visual inspection 25
18 Environmental/climatic tests 26
20 Quality assurance 26
21 Plant & machinery 27
25 Annexure 29-133
C 98-104
D 105-110
E 111-113
F 114-117
G 118-120
H 121-123
I 124-133
GOVERNMENT OF INDIA
MINISTRY OF RAILWAYS
0 FOREWORD
0.1 This specification is issued under the fixed serial number followed by the year of
adoption as standard or in case of revision, year of latest revision.
0.2 This specification requires reference to the following specifications: -
IRS: S23 Electrical signaling and interlocking equipment
RDSO/SPN/144 Safety and reliability requirement of electronic signalling
equipment
electrical items
Wherever, reference to any specification appears in this document, it shall be
taken as a reference to the latest version of that specification unless the year of
issue of the specification is specifically stated.
1 SCOPE
1.1 This specification covers the technical and operational requirements of data
logger equipment, which is installed to monitor the status of the signaling gears
at stations. It also covers minimum configuration of central monitoring unit
(CMU)
1.2 Inspection shall be carried out for data logger equipment consisting of RTU, FEP,
and CMU software. Standard accessories used external to the data logger like PC
for CMU, UPS for CMU and modem etc. shall be checked during inspection for
their functional performance only required for data logger system as per
specification.
2 TERMINOLOGY
2.1 For the purpose of this specification, the terminology given in IRS: S23 and RDSO/
SPN/144 shall apply.
2.2 Input module means an electronic module/ card used to read status of relays
(digital input) and/or level of analog signals.
2.3 Signal Conditioner means an electronic module or card used to convert analog
signals to a suitable level for recording.
2.4 SSI/ Electronic interlocking is a processor based electronic system to control
signaling equipment/ functions at any interlocked station.
2.5 Integrated power supply (IPS) is a composite module delivering various AC and
DC voltage for signaling equipment.
3 GENERAL REQUIREMENTS
3.1 The system shall chronologically monitor and record the status of various field
functions like track circuits, points, signals, operator’s push buttons/switches
(digital Inputs)and level of various analog signals like DC and AC supply voltages,
Axle counter signals, DC track circuit currents, Point machine currents, Signal lamp
currents etc.The details Voltage & current ranges are given in Annexure-B.
3.2 The equipment shall also have the capability of statistical analysis, predict the
faults and generate failure reports. It shall be possible for the user to define fault
logics taking digital/analog inputs into consideration and generate reports for
such faults.
3.3 The equipment shall be capable of generating audio-visual alarm under defined
conditions. In addition, it shall be able to deliver non-vital relay outputs on
receipt of command from CMU. At least 8 non-vital relay outputs shall be
provided. The non-vital relay output shall be in the form of potential free
contacts capable of driving relays Voltage :24VDC Current :200MAmps
relays.These outputs may be used for non-vital functions like radio patching of
control circuits etc.
3.4 For digital inputs, potential free contacts shall be used. Analog signals shall be
scaled to a suitable limit using signal conditioner before converting to digital
signal. Each analog input shall be isolated (at least 2KV isolation voltage) from
the system and one another. While tapping analog input, it shall not load the
analog channel/ field gear by more than 2ma.
DC &AC analog currents shall be measured with suitable sensors which provide
galvanic isolation to the source being monitored.
3.5 The system shall be suitable for working on non-electrified, AC electrified and DC
electrified areas and where passenger/freight trains hauled by single phase
thyristor controlled or three phase induction motor controlled AC locomotives or
chopper controlled EMU stock are operated.
3.6 The system shall be capable of working in conjunction with conventional relay
interlocking, multi-aspect color light signaling installations operated by lever
frames/ slides & Electronic Interlocking systems. It shall have facility to log data
received from Electronic Interlocking through a serial port.
3.7 The system (except commercial PC used for CMU) shall be capable of working in
an ambient temperature range of -10 0 C to +70
0 C and relative humidity up to
95% at ambient temperature of 40 0 C.Special protection against ingress of dust,
moisture etc. shall be provided.
3.8 The data logger shall be capable of being connected to a printer for obtaining a
hard copy of the function recorded. It shall be possible to print the following on
the connected printer by selecting from user friendly menu
(i) on line events as they are generated.
(ii) to print the exception report
(iii)to print the status of user specified inputs for user definable time period
3.9 The data logger shall record various field functions as indicated in para 3.10
below chronologically in the following format with name of the location at top of
every page:
Date, time, channel no., field function, status / value
3.10 The status of various functions shall be recorded in the following way: -
3.10.1 Digital Input:given in the Annexure-B
3.10.2 Analog inputs given in the Annexure-B
3.10.3 Parameters to be monitored for Point machine, DC track circuit, Signal lamp and
their location are given in Annexure-G as guidance.
3.11 The system shall be easily re-configurable to any changes required by user,
whenever modifications are carried out in the yard
3.12 Provision for networking and remote monitoring of several data loggers from the
central place shall be provided.
3.13 Implementation of version control and change of software shall be as per
RDSO/SPN/144
4.1 Data logger system consists of:
(a) Data logger equipment which is provided near the signaling gears to be
monitored has following modules:
(iii) Signal conditioning module
(vi) Modem(s)
(b) Central monitoring unit (if provided) with communication facility to retrieve
data from data logger(s) provided at station(s). The central monitoring unit
shall run the diagnostic software to generate alarm and exception reports.
4.2 Data Logger Equipment:
4.2.1 The equipment shall cater for minimum 512 digital inputs (in the form of
potential free contacts) and 32 analog inputs. The system shall be expandable
up to 4096 digital & 96 analog in puts by expansion/cascading the similar
equipment.
4.2.2 The equipment shall have facility to interface with Remote Terminal Unit(RTU).
RTU shall be able to monitor potential free contacts, analog voltages, analog
Currents (AC&DC), receive data packets from equipment like IPS, EI, DAC,
BMU[Battery Monitoring Unit], SSBPAC-D,FMS [Fuse Monitoring Unit] etc.and
change their protocol if required to common protocol. It shall be possible to
network RTUs and also RTU to datalogger or FEP.Since all the above
functionalities are not required for all applications, the RTUs are categorized as
follows.
Type1: (Used for IBS, LCGate, Autosignal etc.)
i. Shall monitor digital inputs in the form of potential free contacts
with capacities :128/64, Analog voltages(DC/AC):16, Analog
currents(AC/DC):4
ii. Networking: by leasedline modem[2 or 3] or GSM or GPRS or
Wireless or dark fiber(channel capacity and its data rate-
minimum 2 Mbps.)[Purchaser to provide type of networking and
number of connections for networking]
iii. Local PC Connectivity : by isolated RS232 serial port
iv. Printer connectivity: by blue-tooth
v. Keyboard of 3X4
vi. 7 segment display
viii. Memory: NonVolatile-1 lakh events capacity
ix. housing: Shall be of 6U and able to be accommodated in a
location box
x. Secondary backup memory(Removable): Secondary data backup
shall be provided with isolation [of power supply and data] and
hot pluggable by the user. It shall be possible to copy data from
RTU in to secondary data backup device on request by user.
Necessary hardware and software tools shall be available to post
data from the device into data base through CMU software. Its
capacity shall be 10 lakh events
xi. Scanning interval shall be similar to data logger
Type II: (Used for Point Machine, Signal, DC Track circuit)
i. Shall monitor 16 digital inputs, 8 Analog voltages, 6 Analog
Currents
communication (Optional).For wireless Zigbee can be used.
iii. Additional Serial / RS485port for connecting additional RTU for
augmentation of capacity.
v. Scanning interval: digital and analog voltages same as data
logger, currents – one sample per 40 millisec with averaging the
sample values
PC/printer and secondary memory
vii. Housing: Shall be of 2U height and able to be accommodated in a
location box
Type III:(Used for IPS, EI, DAC, SSBPAC-D, BMU, FMS etc. )
i. Shall receive data from EI, IPS, DAC, SSBPAC-D, Battery
Monitoring Unit, Fuse Monitoring Unit or any other solid state
equipment which gives its diagnostics in packet form through
serial interface.
ii. It shall be the joint responsibility of the original equipment
manufacturer of the equipment being monitored, data logger
vendor and RDSO to develop appropriate hard ware and
software to correctly depict the status of the equipment
iii. The packet protocol of the equipment monitored is converted to
common protocol where required
v. Shall have 16 asynchronous isolated serial communication ports
vi. Memory 10 lakh events- non-volatile
vii. Network connectivity: by wireless or isolated asynchronous
serial communication
viii. 24 V DC power taken from data logger supply shall be isolated
ix. Housing: shall be of 6U size
NOTE:
i. All types of RTUs shall work on 24VDC(+20%,-30%). While using
common supply isolation shall be achieved within the equipment
ii. Shall generate packets as per common protocol and shall have their
ownRTC for time stamping.
iii. RTC of RTUs shall synchronize with datalogger.
iv. Each RTU shall have its own ID.
v. Digital and analog inputs being monitored shall be isolated like in
datalogger
network and frequency shall be in free band
vii. The RTU may be provided SPD card/unit to protect against surges.
viii. Typically the distance between Track circuits, Point machine & Signal
lamp to Data logger relay room, it is One kilometer it may vary
subject to field condition and in that condition vendor should
provide necessary arrangement.
Block diagrams of data logger system with all 3 types of RTUs connected at a station and
individual RTUs and Data logger connectivity interfaces are given in Annexure-F
4.2.3 Signal conditioning module shall convert analog signals like 230 VAC, 110 VAC,
110 VDC, 60 VDC, 24 VDC, 12VDC and axle counter RX voltages etc. to suitable
level for recording. Normally all AC voltages shall be at commercial frequency of
50 HZ except for Axle counter which is at 5KHZ. When an analog channel is not
connected, it shall not pick up any noise.Provision shall be made to set a channel
as not connected.
Channel Nominal Voltage DC or AC
(RMS)
7 24 DC 22.5-28
8 12DC 10 - 14
Or as specified by purchaser.
4.2.5 Display shall be provided on the front panel of the data logger to display
current status / faults/ alarms along with time stamp. It shall be possible to
display latest 500 faults/ alarms generated by data logger on the panel. At least
two row display shall be used with at least 16 characters in each row.
4.2.6 The data logger shall have built in Real Time Clock for recording time at which
the status of the particular information has changed. The FEP shall have built in
Real Time Clock for storing particular information, FEP shall have a facility to
communicate with external/ internal GPS module and shall get synchronized
it’s in built RTC with GPS time. FEP shall issue the time synchronization
command to data logger and Central Monitoring Unit to synchronize the entire
network with GPS time periodically. In case FEP GPS module failure, CMU shall
issue the time synchronization command to data loggers and FEP to get
synchronization of the entire network with CMU time periodically.
4.2.7 Opto-coupler for each input shall be provided to electrically isolate (at least
4KV Isolation voltage) each external digital inputs (relay contacts) from the
equipment. Self-diagnostics shall be provided in the system. Any fault in the
system shall generate error message in the system panel and generate alarm in
the CMU.
The system shall generate the following diagnostic signals and displayed on the
CMU in graphical form.
Low/high voltage of data logger supply.
Link failure with sub-units like analog unit, EI, DAC, IPS, BMU, FMS or any other
electronic equipment connected through serial port.
Communication failure between two equipment where modem is provided
Internal memory failure
4.2.8 The hardware structure of the system shall be modular.
4.2.9 Event logging facility for minimum 10 Lac events shall be provided in a Data
logger. Data shall be recorded in Primary/Main memory on first in – first out
basis so that latest data is available in the system. Data logger shall also be
capable of recording 10 Lac events data in to Secondary memory simultaneously
on first in – first out basis in case of failure of Main memory so that there should
be no loss of data from the data logger in case of failure of main memory. There
should be no loss of data from the data logger in case of power supply failure.
It shall be possible to remove the secondary memory device for further data
analysis purpose or copy data from data logger in to USB device on request by
user through some secured access. Necessary hardware and software tools shall
be available to post data from the USB device into data base through CMU
Software. Railways will provide power supply for backup hardware.
4.2.10 Scanning interval for digital inputs shall be less than 20 milliseconds. Change in
status of digital signal shall only be recorded.
4.2.11 Scanning interval for analog signals like DC or AC supply voltage, temperature,
axle counter RX voltage etc. shall be less than 1 second. Variation of more than
5% of the nominal value from the last recorded value, provided it has gone 5%
beyond the nominal value, shall be recorded.
4.2.12 Accuracy of measurement of analog signals shall be better than 1% within
±40% of nominal value.
4.2.13 The equipment shall have facility to receive serial data from external equipment
like Electronic Interlocking, Integrated Power Supply etc. and record it with
time stamp.
4.2.14 The software of the system shall be of approved type and written in a
structured format so that the purchaser can reconfigure it, if required.The
software shall have clear bifurcation between generic software and application
software.
4.2.15 At least 12 serial ports shall be provided for communication with other data
loggers, Central Monitoring Unit (CMU), Remote Monitoring Unit (RTU),
Electronic Interlocking (EI), Integrated Power Supply (IPS), Battery monitoring
Unit (BMU),Solid State Block proving Axle Counter (SSBPAC-D), Fuse
Monitoring Unit (FMS) etc. which generates packets in common protocol
format given in the annexure-A and 2 Ethernet ports to connect to Network of
Data Logger / RTU/ local CMU.
4.2.16 Power Supply: The system shall work on 24V DC (+20%, -30%). Railways will
provide 24VDC input supply. Crowbar or better protection shall be provided.
4.2.17 19” rack mountable and 3/4/6 U high cabinets made of aluminum of minimum
thickness 2mm should be used for housing the PCB cards to achieve modular
and ergonomic design for good maintainability for data logger. The cabinet
should be powder coated. The front and backsides of the cabinets shall have
the facility for locking the equipment.
4.2.18 Data Logger shall be capable of working with different transmission media like
underground telecom cable, microwave (Digital or Analog) & OFC. The
provision of either in-built modem or external modem is acceptable. The data
logger equipment will continuously check the modem status and give the
necessary reset as required to eliminate modem hanging condition. The
modem will be housed within the data logger cabinet. The data logger shall be
compatible to the following media:
(i) Main telecom cable.
(iii) Analog channel of OFC, digital microwave or analog microwave.
(iv) E1 data channel on OFC or digital microwave.
(v) Dark fiber
NOTE: Wireless technology used for networking shall support mesh network
and frequency shall be in free band
Where copper cable is used for networking, protection arrangements like
connecting screen and armour to earth and provision of 1:1 isolation
transformer [both in RE and NON-RE areas] shall be ensured by railways before
connecting the cable to data logger or RTU. As far as possible there shall not be
intermediate termination of communication cable. Where provided, they shall
be of screw-less type of connection. No copper conductor of data logger
network shall be taken through conventional ‘U’ link test panel as they cause
loose connection.
Where railway communication network is not available, networking by GSM,
GPRS can be done as given in Annexure-D
4.2.19 Communication between data logger & RTU shall also be as per
communication protocol mentioned in clause 4.3.9.
4.2.20 Cards and terminals required for up to minimum 1024 digital inputs 32 analog
inputs, signal conditioning modules etc. shall be accommodated in one rack of
19" width.
4.2.21 For termination of external digital and analog inputs, international quality
terminals of screw less type like that of WAGO/ Phoenix etc. makes shall be
used as per RDSO SPN/144. All wires should be neatly bunched in horizontal
and vertical channels.
4.3.1 SOFTWARE CONFIGURATION
4.3.1.1 The database management system i.e. MS SQL server or Inter base shall be
used to cater for basic function of Data loggers at CMU level. Only licensed
software shall be used.
4.3.2.1 HARDWARE CONFIGURATION
4.3.2.2 Central monitoring unit shall be state of art PC ( of reputed brand ) based
system working on commercial supply of 230VAC, 50Hz. The minimum
configuration shall be as specified by RDSO from time to time. Presently
minimum configuration must be as under:
i. Core i7-860 2.8GHz, 8MB cache or latest - 2 GB Memory or as
required for latest OS and application software - 500 GB Hard
Drive - Dual Gigabit Ethernet ports –2 USB Ports for connecting
to FEP or data logger - Keyboard (USB) - Mouse (USB Optical) -
Windows 8 or latest OS - Antivirus software - 22” TFT Monitor-1
No – display adopter to support dual monitors, monitor resolution
of 1280x1024 Make: HP/IBM/DELL
NOTE: One 40 inch monitor to be procured for signal monitoring of each
section consisting of about 32 data loggers
ii. UPS with minimum 6 hours battery backup for central monitoring
unit.
iii. Software tools.
4.3.2.3 Central monitoring unit shall have Graphical User Interface (GUI) based
software and retrieve data from all Networked data loggers (up to 64) at
various stations. It shall store data in standard data base files. The CMU shall
also be capable of analyzing the data & generate reports & audio visual alarms
on defined conditions. It shall be possible to compress the data and take back-
up on DVD.
Methodology for Centralized Monitoring of alarms is given in Annexure-H
To make monitoring of signalling gears more affective from central location
online status of data loggers in a section displayed in a CMU shall be shown in
single screen. In case user selected unusual alarms occur at any of the stations,
the same shall be displayed in graphical form so that the person monitoring
the system takes appropriate action. Status of data logger network i.e. link
breaks, data lag also shall be displayed. A typical screen is given in the
Annexure-H.
4.3.3 Software used for analysis of data, prediction of faults etc. in central monitoring
unit shall be of approved type and written in a structured format so that
purchaser can reconfigure it, if required. A copy of software shall be supplied in
CD.
4.3.4 It shall be possible to display the status of signaling gears at any selected time in
graphic form for any selected station yard on the central monitoring unit.
4.3.5 It shall be possible to retrieve the stored data & simulate train movement and
circuit progression on the central monitoring equipment.
4.3.6 It shall be possible to send commands to various Data loggers to activate audio,
visual alarm or operate an electromagnetic relay.
4.3.7 It shall be possible to share data available in CMU by other PCs through available
local area network where this data can be used for train charting / passenger
information purpose.
4.3.8 Front End Processor (FEP) shall be provided to continuously retrieve data from
station data loggers. FEP must have capacity to store 10 lac telegrams. It should
have 6 ports and all ports shall be configurable.
4.3.9 The communication protocol for transmitting data and command between data
logger and CMU is given in Annexure-A.
4.3.10 Some of the desirable features of data logger user interface software is given in
the Annexure-I
4.3.11 To ensure data availability continuously recommended data loggers network
configuration with redundancy enables data access by field officials as well as
zonal HQ is given in the annexure-D
4.3.12 Recommended specifications of hardware required for data logger network
elementsare given in the Annexure-E
5 FUNCTIONAL REQUIREMENTS:
5.1 The system shall generate audiovisual alarm in ASM’s/ Signal Maintainer’s room
in the case of power supply failure (battery voltage low) or battery charger
defective with acknowledgement facility.
5.2 Each data logger shall have its own identity code which shall be transmitted
along with data packet to central monitoring unit.
5.3 Events recorded at each station shall be continuously transmitted to central
monitoring unit for online monitoring. The following minimum data transfer
speeds are to be fulfilled:
i. Data logger to Data logger/FEP–125packets per sec
ii. FEP to CMU – 1000 Packets per sec
iii.RTU to Data logger–40 packets per sec
iv. Data logger to Local PC – 125 packets per sec
5.4 In case of loss of data, retransmission of data shall take place.
5.5 Data transfer rate shall be 57600 BPS with fallback facility to lower rates.
5.6 EXCEPTION REPORT:
Exception condition shall be stored in the data logger chronologically and
displayed one by one on the front panel through a toggle switch. Details of
exception report are attached in Annexure-C
5.7 Data loggers of all stations shall send status report to the Central monitoring unit
continuously. Status information shall be processed at the central monitoring
unit and audio visual alarm generated for the fault / alarm condition
It shall be possible to send important alarms as SMS to maintenance staff as given
in Annexure-C
ISO9001:2008 Document No: IRS:S:99/2014 Version No.4.0 Date Effective :------
Unless otherwise specified all tests shall be carried out at ambient atmospheric
conditions.
6.2 For inspection of material, relevant clauses of IRS: S 23 and RDSO/SPN/144
shall apply.
ii. Digital multimeters- 3.1/2 digit display with facility of diode &
transistor testing with 1% accuracy
iii. EPROM Programmer and UV eraser
iv. Megger (500V)
6.3 Type Tests
a) Visual inspection as per Clause 7.1
b) Insulation Resistance tests as per Clause 7.2
c) Card-level functional tests on all the cards.
d) System level functional tests.
e) Environmental/climatic tests as per Clause 7.3
f) Applied High Voltage Test as per Clause 7.4
6.3.2 Any other tests shall be carried out as considered necessary by the purchaser.
6.4 Acceptance Tests
a) Visual inspection (Clause 7.1).
b) Insulation Resistance tests (Clause 7.2).
c) System level functional tests.
6.5 Routine tests
6.5.1 The following shall comprise the routine tests and shall be conducted by
manufacturer on every equipment and the test results will be submitted to the
inspection authority before inspection. The application software in proper
format shall also be submitted to the inspection authority in advance.
i. Visual inspection (Clause 7.1)
ii. Insulation Resistance tests (Clause 7.2)
iii. Card level functional test on all the cards.
iv. System level functional test.
7 TEST PROCEDURE
The test procedure shall be based on the system design. The methodologies to
be adopted for various tests shall be decided taking into account the system
design/configuration.
7.1 Visual Inspection
The equipment shall be visually inspected to ensure compliance with the
requirement of Clauses 3 to 5 of this specification. The visual inspection will
broadly include –
Conformal coating.
Legend printing.
Green masking.
Indications and displays.
Proper housing of cards.
7.2 Insulation Resistance Test
7.2.1 Insulation Resistance Test shall be conducted as per RDSO/SPN/144
7.3 Environmental / climatic tests
7.3.1 Environmental / climatic tests shall be conducted as per RDSO/SPN/144
7.4 Applied High Voltage Test
7.4.1 Applied High Voltage Test shall be conducted as per RDSO/SPN/144
8 QUALITY ASSURANCE
8.1 All materials & workmanship shall be of good quality.
8.2 Since the quality of the equipment bears a direct relationship to the
manufacturing process and the environment under which it is manufactured,
the manufacturer shall ensure Quality Assurance Program of adequate
standard.
8.3 Validation and system of monitoring of QA procedure shall form a part of type
approval. The necessary Plant, Machinery and Test instruments as given
below shall be available with the manufacturer.
8.3.1 Plant & Machinery:
As per SIQ 0001, Version.-1 or latest( STR for Electronic Signalling
Equipments).
8.3.2 All test instruments as given in Cl. 6.2.1 shall be available with the
manufacturer.
8.4 Along with the prototype sample for type test, the manufacturer shall submit
the Quality Assurance Manual.
9 PACKING
The equipment and its sub-assemblies shall be packed in thermocole boxes
and the empty spaces shall be filled with suitable filling material. Before
keeping in the thermocole box, the equipment shall be wrapped with bubble
sheet. The equipment shall be finally packed in a wooden case of sufficient
strength so that it can withstand bumps and jerks encountered in a road/ rail
journey.
Following documents should be supplied along with the system:
10.1 Mechanical drawings of each sub-system/ rack.
10.2 Trouble shooting chart.
10.3 Installation and Maintenance Manual.
10.4 Pre-commissioning check list, DOs and DON'Ts of data logger system including
RTU, CMU & FEP in the User’s manual.
11 INFORMATION TO BE SUPPLIED BY THE PURCHASER
11.1 Total number of digital and analog inputs to be monitored calculated as
under.
11.1.1 The tenderer should give number of digital inputs required by calculating the
inputs as given in the Annexure-B
11.1.2 Details of Analog inputs to be monitored as per Annexure-B.
11.1.3 Whether RTU is required for monitoring of the equipment at distant place, no.
of digital and analog inputs required in RTU.
Details of analog inputs to be monitored from RTU should be given in the
format as given below:
Data logger
11.2 Additional exception reports (other than those mentioned in Annexure-C to
be generated.
11.3 List of functions (in addition those mentioned in Annexure-B to be monitored.
11.4 (a) Central monitoring equipment (CMU) required – Yes/ No.
(b)FEP required – Yes/NO
If YES, indicate whether it is to be provided at the same station or at a remote
place like control office etc.
11.5 Whether printer is required with data logger (at the station) : Yes/ No
11.6 Type of network ports .
Annexure-A
A.0.0 Overview This Document completely details out all the communication
methods in wired and wireless media and protocols involved in the data
logger as per RDSO SPN 99/2006. This methods and protocols are totally
independent of the hardware of the data logger. The communication method
and protocols have been designed to bring out the maximum throughput
from the network.
A.0.1 Networking in Wired media A.0.1.1 Topology
Ring Network topology has been adopted in this network. In Ring
configuration the Data loggers are connected serially one to another. If ‘n’
number of Data loggers are in network then the first Data logger is connected
to the second Data logger and second Data logger to third Data logger so on
up to the ‘nth ‘ Data logger. Then the first and ‘nth ‘ Data loggers will be
connected to the Front End Processor ( FEP ) individually to make the network
as closed ring. Each Data logger is connected with other Data loggers in either
direction with 4 wire leased line modems. FEP is also connected through the
modems to the first and last Data loggers. Since this type of configuration
gives individual one to one communication between Data loggers, so event
data can be placed into network immediately and simultaneously by all the
Data loggers.
CMU
Data Logger System Network
Direction A is data flow from Data logger n , n-1,…..1 - FEP.
Direction B is data flow from Data logger 1 , 2 ,……n - FEP.
A.0.1.2 Port
(iv) Parity: none
A.0.2 Message Formats
Two types of message formats have been implemented. One for Commands from
CMU to any Data Logger / FEP and other is for event packets transmission in the
network.
CMU Data Logger /FEP
Broad cast request Accept Broadcast request
Accept reply Reply from all
A.0.2.2 Event Packets.
Data Logger n Data Logger / FEP n-1
Send event packet #1 Receive event packet #1
Receive event packets Send event packets
Confirmation packet Confirmation packet For 3 packets
Data Logger n Data Logger / FEP n-1
Time out (300 milliseconds)
Confirmation packet Confirmation packet
Time out (300 milliseconds)
Receive event packets Send event packets
Confirmation packet Confirmation packet
CMU FEP DL 1 DL 2 ….. DL n
Request to DL 2
Direction I
Send event ‘x’
Direction II
Send event ‘x’
= Retransmission to the next Data Logger in the other direction.
A.0.4 Event Packets Communication:
The event packets created in the DL will be sent immediately in both the
directions. The event packets received from one direction is retransmitted to
the other direction. These event packets maintained in the buffer till it is
acknowledged.
On failure of acknowledgement the event packets are tried again for
transmission after the time out of 3 Seconds. This is repeated and tried for
three times with the same time-out of 3 Seconds. If acknowledgment is not
received even after three trials, record will be revalidated, if validation is OK,
then it will transmits again with timeout of 3seconds and follows above
process again until acknowledgement is received. If validation of the packet is
failed, it will be discarded.
The acknowledgement for the event packets are sent for every three event
packets received or if the time between received packet crosses 300
milliseconds.
On receiving any event packet it is validated for CRC. If validity fails, no action
performed. For valid packets Data Logger will check for any duplication within
the last 100 packets. If it is a duplicate packet then acknowledgement will be
given but it will not be transmitted in the other direction. If it is a new packet
then it will be placed in the buffer, if space is available and acknowledge is
sent back. If space is not available then buffer full command is sent back.
Once the space is available then buffer free command is sent to reinitiate the
packets transmission.
Once buffer full command is received back for packet transmission then the
Data logger will set itself buffer full status and wait for a time lapse of 60
Seconds. On receiving the status of buffer free, the Data Logger will clear the
buffer full status and time lapses counts to initiate the transmission of
packets.
At FEP, the received event packets from both the directions are buffered.
These data will be sent to CMU whenever request received from CMU. Till
then it is stored in buffer.
These processes are illustrated with flow diagrams given below.
A.0.5 Received Event Packet Processing
NO
YES
YES
YES
NO
NO
YES
EXIT
ACK
DIRECTION
BUFFER
FREE=?
SEND BUFFER
FULL COMMAND
100 events in the buffer
CHECK FOR CRC and Shift Checksum
VALIDITY
ENTER
IS IT A
A.0.6 Event Packet Transmission Process
YES
NO
NO
A
CHECK THE NUMBER OF
YES
NO
NO
YES
PCKTS.
B
A.0.7 Acknowledgement Process for Event Packet
YES
NO
NO
YES
SEND ACK.
NOT
ACK
A.0.8 Networking in Wireless media:
Networking with GSM data channels or GPRS on mobile network is
recommended in the sections where OFC/Quad cable is not available. In this
type of communication all data loggers or RTUs will directly interact with
FEP/CMU in Central place.
A.0.8.1 GPRS connectivity from DL/RTU to CMU:
Typical Data loggers network through GPRS is as shown below figure.
Fig : Data logger network connectivity using GPRS modems
In this type of communication, each data logger is connected to a GPRS
modem (with GPRS activated SIM card). At central place CMU software (with
GPRS feature) is connected to internet through a Static IP.
After connection is established between Data loggers and CMU software
GPRS
MODEM
DATA LOGGER 1 DATA LOGGER 2 DATA LOGGER N
GPRS
MODEM
GPRS
MODEM
through standard AT commands, event and command communication will be
as explained in Networking in Wired media. All data loggers can send its data
at time using GPRS, because it is multipoint communication. If
acknowledgement for transmitted event is not received within 10sec data
logger retransmits the same record again, this time period is 3seconds in
wired communication. Due to network delays involved in GPRS
communication retransmission period is increased to 10sec instead of
3seconds.
A.0.8.2 GSM connectivity from DL/RTU to CMU:
Typical Data loggers’ network through GSM is as shown below figure.
Fig : Data logger network connectivity using GSM modems
In this type of communication, a GSM modem is placed at FEP and at each
data logger, they establish connection through standard AT commands. By
using GSM data call they transfer data. Since GSM data call is point to point
STATION - N STATION - 2 STATION - 1 CENTRAL PLACE
CMU
ETHERNET
1 FEP
communication, only one data logger shall able to transfer its data to FEP. FEP
establishes connection with one data logger and receives data over a fixed
time period or upto all available data at data logger is transferred (which one
is earlier). Once communication is established, data transmission and
receiving process is similar to wired communication. After that, disconnects
the connection with that data logger and connects to another data logger.
This process continues in cycle.
A.0.9 Commands Communication:
Commands always originated from the CMU to facilitate control actions on
any one or all the Data Logger/s in the network. Buffer full and Buffer free
commands are the only commands originated by Data Loggers for control of
event packets flow. The commands always work in the Request and Response
style.
A.1 EVENT PACKET:
Block 1
DATA
Event packet consists of 3 blocks as shown above.
1. Block 0.
2. Block 1.
3. Block 2.
1.1.i. BLOCK 0: The size of the BLOCK 0 is 11 bytes. The structure of Block 0
iscommon for any type of event packet and it is having the following fivefields.
START:AAH and 66H are the start of the event packet. Here the Header second byte
is changed to 66 H from 55 h, and acknowledgement header second byte is changed
to 99 H from 33 h. To identify the old units connected to this data logger and also to
provide the backward compatibility [To support data logger common protocol].
ID NO: This is used for the identification of various devices like FEP, Data logger and
RTU etc.
Serial Number: It is the sequence number of packet. With this CMU will identify that
it is receiving all the packets or not. Serial no will start from 0000H, whenever a
packet is created count will be incremented by one, and will roll over to 0000H after
reaching FFFFH.
PACKED TIME:
START 2
Time will be stored in the Packed Form. This is a long word size and time will be
calculated in multiples of 1/64 second. This long word will hold time for one year. The
equation to build packed time from the real time is given below.
Packed time = (Days x 24 x 60 x 60 x 64) + (Hr x 60 x 60 x 64)+(Mt x 60 x 64) + (Sec x
64). Here Days = Number of completed days till present date
Hr = Hours
Mt = Minutes
Sec = Seconds
PACKED YEAR LSB: It will represent the YEAR LSB of the packet in which year it was
created. Here year LSB means in 2012 year 12 will be the LSB and it will be stored as
0C H.
1.1. ii. BLOCK 1: Block 1 size is 9 bytes. The values in the BLOCK 1 will vary depending
upon the type of event packet. BLOCK1 is having the following fields.
0 TYPE IDENTIFIER (1 bytes).
1 DATA (8 bytes).
2 a). TYPE IDENTIFIER (TI):
This is a byte-sized value and it indicates packet type. Each packet will have a
unique type identifier. The Event records are classified into two types.
1. Functional Records (type id’s 00 H to 7F H).
2. Diagnosis Records (type id’s 80 H to FF H).
The following table shows Functional records and its type identifiers.
S.No Details Type id Usage
1 Digital Record 00 H Compulsory
2 Analog Record 01 H Compulsory
3 Time Difference Record 02 H Compulsory
4 Time Write(Update) Record 03 H Compulsory
5 Communication status Record 04 H Optional
6 Health Record (Time packet) 05 H Compulsory
7 Digital Periodical All Inputs Status Record 06 H Compulsory
8 Digital All Inputs Status At Reset Record 07 H Compulsory
9 Reserved 08 H
11 Reserved 0A H
14 Digital Fault Record 0D H Optional
15 Analog Fault Record 0E H Optional
16 Reserved 0F H
20 Reserved 13 H
21 Reserved 14 H
22 Reserved 15 H
23 Reserved 16 H
24 Reserved 17 H
26 Internal Temperature Record 19 H Compulsory
28 Reserved 20 H
29 Reserved 21 H
30 Reserved 22 H
31 Reserved 23 H
33 Reserved 25 H
34 Modem’s Periodical Link Status Record 27 H Compulsory
35 Analog Periodical Chatter inputs Record 28 H Reserved
36 Digital Periodical Chatter inputs Record 29 H Optional
37 Reserved 2A H Reserved
38 Analog Periodical All inputs Status Record 2B H Reserved
39 Reserved 2C H
40 Reserved 2D H
41 Reserved 2E H
42 Reserved 2F H
43 Reserved 30 H
44 Reserved 31 H
45 Reserved 32 H
46 Reserved 33 H
47 Secondary Data Backup Module Status Record 34 H Compulsory
48 Primary Data Backup Module Status Record 35 H Compulsory
48 Reserved 36 H
To
7F H
The following table shows Diagnosis records and its type id’s.
S.No Details Type id Usage
1 Data Logger Reset Record 80 H Compulsory
2 Digital / Analog / Communication Card Health Record 81 H Optional
3 Communication Errors status Record 82 H Compulsory
4 Data Base Status Record 83 H Compulsory
5 Reserved
84 H
FF H
b). DATA:
This field is having 8 bytes, last 3 bytes are reserved and first 5 bytes will vary
depending upon packet.
Byte No Description
6 to 8 Reserved
1.1.ii. BLOCK 2:
BLOCK 2 size is 4 bytes. The structure of Block 2 is common for any typeof event
packet and it is having the following two fields.
FIELD NAME SIZE IN BYTES
CRC 2
END 2
I. CRC: The CRC field is a 16 bit value calculated as per CCITT polynomial
"x 16
+x 12
+x 5 +1". This CRC will be calculated to the block 0 and block 1 of the
event packet fields with an exclusive of start bytes. It should be calculate from
top to bottom.
A.1.2 Event Records Data Bytes Description:
1. Digital Record:
This record will be created to indicate the change in status of the digital input.
Dummy and reserved bytes to be filled with zeros.
Occurrence: This record will be created whenever a digital input changes its state
(From ON to OFF or OFF to ON). Its record ID is 00H.
BLOCK 0
BLOCK 1
Dummy (2 bytes)
Reserved (3 bytes)
Input Number: 1 TO 4096
Status of Input: 00 H Picked UP
FF H Drop.
2. Analog Record:
This record will be created whenever there is variation in the any of analog inputs.
Occurrence: This record will be created whenever the difference of previous
recorded channel value and present scanned channel value of a particular input
crosses the configured tolerance limit..
BLOCK 0
BLOCK 1
BLOCK 2
CHANNEL VALUE : 0 TO 4095 (Value 4095 is equivalent to Maximum possible
Channel value for that input). The nominal voltages and their corresponding
maximum voltages are shown in the below table
Nominal voltage Maximum voltage Maximum value
230V AC 330V AC 4095
110V AC 170V AC 4095
110V DC 170V DC 4095
60V DC 90V DC 4095
24V AC 50V DC 4095
24V DC 50V DC 4095
18V DC 50V DC 4095
12V DC 25 VDC 4095
150mv 150 mv 4095
6V DC 10V DC 4095
CHANNEL NUMBER: 1 TO 96.
The External temperature record will also be created with the same analog
record ID with channel number as 00 H. Channel value of temperature is as
shown.
FF – “+VE” temperature.
Byte 2 & 3: Temperature (2 bytes). It is in terms of 0.5 o C. It is ranging
from 0 to 128 o C.
3. Time Difference Record:
This record was created to notify the difference between the packed time and with
RTC chip time.
Occurrence: This record will be created whenever there is a difference in packed
time and RTC chip time. The data logger compares the chip time with the packed
time periodically and to record the difference if any. As Packed time is maintained
by software, this need to be verified with chip time. The maximum interval is 4
minutes.
1 00 H RTC Time > Packed Time
2 FF H RTC Time < Packed Time
DIFFERNCE TIME VALUE: RTC Time ~ Packed Time
4. Time Write record:
This record will be created whenever time set command was sent from CMU/user
interface.
Occurrence: This record is created whenever time was set from CMU.
BLOCK 0
BLOCK 1
Reserved (3 bytes)
BLOCK 0
BLOCK 1
5. Communication Status Record:
These records were created to log network status for later analysis. the network
communication health status.
Occurrence: These records will be created for every 68 minutes approximately.
BLOCK 0
BLOCK 1
BLOCK 2
PACKET COUNT: This count may be Transmitted packets (or) Received packets (or)
Pending packets (or) Duplication packets (or) Fail packets count for two network
ports.
SERIAL NUMBER: It specifies the type of Packets count.
The MSB of the serial number indicates port number 0 – 15 ports.
The LSB of the serial number indicates packet type as shown below.
LSB Details
2 Pending Packets Count
3 Received Packets Count
4 Duplication Packets Count
6. Health Record:
This record will be created to notify the health of data logger to the CMU.
Occurrence: This record will be created for every one minute if any other record is
not created.
BLOCK 0
BLOCK 1
In these records the status of all the digital inputs will be sent. So as the CMU can
synchronize with the latest input status.
Occurrence: These records are created for every 34 minutes approximately and also
on request of the CMU. The number of records created will depend upon the number
of inputs configured. In each record, status of 32 inputs will be sent. Each inputs
status can be 0 or 1(‘0’ for pickup and ‘1’ for drop). If the number of inputs
configured is 512, 16 records will be created. The configuration should be in the
multiples of 512 inputs. The 1st record will have inputs of 1 to 32, 2nd record will
have 33 to 64 and so on up to the total number of inputs.
BLOCK 0
BLOCK 1
TI = 06 H(1 byte)
Bytes number / bit positions B7 B6 B5 B4 B3 B2 B1 B0
Byte 1 Status of 1-8 inputs 8 7 6 5 4 3 2 1
Serial Number ( 1 byte)
SERIAL NUMBER: 00 H-7F H.
For the first 1 to 32 inputs 00h is given as serial number and continued up to7F h.
8. Digital All Inputs Status at RESET:
These records have been created at the time of Data Logger Reset. This is identical
to the Periodical All Inputs Status except the type identifier.
Occurrence: These records will be created whenever the data logger resets.
BLOCK 0
BLOCK 1
TI = 07 H(1 byte)
Bytes number / bit positions B7 B6 B5 B4 B3 B2 B1 B0
Serial Number ( 1 byte)
9. Configuration Record:
This record will be created to store the all configurations of the Data Logger.
BLOCK 0
BLOCK 1
Occurrence: This record will be
created whenever data
This record will also be sent for
every 34 minutes along with the Periodical all input status packets.
CONFIGURATION BYTES:
Bits B2, B1, B0 will indicate the digital inputs configuration.
Device Id (1 byte)
Byte 4 :
1 00 H Analog channels are Disabled
2 01 H 32 Analog input channels configured
3 02 H 64 Analog input channels configured
4 03 H 96 Analog input channels configured.
Byte 5: Device Id
00 H – Data Logger.
10. Digital Fault record:
This record will be created whenever the digital fault sequence occurs.
B2
B1
B0
No specific data format is defined since the digital fault sequence is dependent on
local PC.
Occurrence: This record is created, whenever the predefined sequence of operations
will occur.
Fault Logic Entry number: The fault logic id entered at local station.
BLOCK 0
BLOCK 1
Dummy(3 bytes)
11. Analog Fault Record:
This record will be created to indicate that the analog channels exceeded
configured safe limits.
Occurrence: This record is created whenever an analog channel crosses the
configured minimum or maximum channel limits.
This record is identical to analog record except type identifier.
BLOCK 0
BLOCK 1
CHANNEL VALUE: Data bytes 1 to 2 will give channel value ranging from 0 to
4095.
‘00’ Fault is due to falling below minimum value.
CHANNEL NUMBER: Data bytes 4 and 5 will give channel
12. Digital Chatter on Record:
This record is created whenever any relay is chattering.
Occurrence: This record will be created whenever digital input changes from
NORMAL state to CHATTERING state.
A digital input is said to be in chattering state, if its status changes by 8 times or
more in 4 seconds. Normal state is the state where the input status does not
change so.
BLOCK 0
BLOCK 1
Input Status: No significance
13. Digital Chatter off Record:
This record is created whenever any relay is normalized from chattering.
Occurrence: This record will be created whenever digital input changes from
CHATTERING state to NORMAL state.
BLOCK 0
BLOCK 1
Input Number: 01 TO 4096
Input Status: 00H- PICKUP
14. Modem Link Status Record:
This record will be created whenever the modem establishes or losses the link
with the other modem.
Occurrence: This record will be created whenever 'Carrier Detect' bit of the
modem changes its state.
Byte 2: 01H- Direction A
02H- Direction B etc.,
FF h- ‘CD’ EXSISTING
A.2.1 Analog Chatter ON Record:
This record is created whenever any Analog input is chattering.
If any analog channel value is varying (out of tolerance) continuously results
creation of more analog packets. To avoid this, the behavior of analog channel
needs to be identified and recorded as ‘Analog chatter record’.
Occurrence: This record will be created whenever Analog input changes from
NORMAL state to CHATTERING state.
BLOCK 0
BLOCK 1
Channel Value: No significance
A.2.2 Analog chatter OFF Record:
This record is created whenever any Analog input is normalized from
chattering.
Occurrence: This record will be created whenever Analog input changes from
CHATTERING state to NORMAL state.
BLOCK 0
BLOCK 1
TI = 0C H(1 byte)
Channel Value (3 bytes)
Channel Number (2 bytes)
Cannel Value: This will give the present channel value.
A.2.3 Modem Reset Record:
Occurrence: This record will created whenever the modem hardware reset
happened.
CD Status (1 byte)
Dummy (2 1 byte)
02H- Direction B etc.,
03 – Reset caused by CMU.
A.2.4 Internal Temperature Record:
Occurrence: Created whenever the internal temperature of the data logger
crosses the 5% tolerance value of the previous temperature.
BLOCK 0
BLOCK 1
Temperature Sign (1 byte)
Temperature value (2 bytes)
FF H – Negative temperature
Temperature Value: it is in terms of 0.5 o C. It is ranging from 0 to 128
o C.
Occurrence: Created when ever link status of communication ports changed
from one status to another status (fail to ok / ok to fail).
BLOCK 0
BLOCK 1
Link Status (1 bytes)
Port Number (1 byte)
FF H – Link Fail.
A.2.6 Modem’s Periodical Link Status Record:
Occurrence: This Record will be created for modem status for the purpose of
hour packet. It will created along with periodical all input status records.
BLOCK 0
BLOCK 1
TI = 27 H (1 byte)
Port Number (2 bytes)
CD Status (1 byte)
02H- Direction B etc.
A.2.7 Analog Periodical Chatter Inputs Record:
Occurrence: This Record will be created to notify the CMU about the Analog
Chatter inputs of Data logger. It will create along with Analog periodical all
input status records.
BLOCK 1
Channel Number(2 bytes)
Channel Value: No significance
A.2.8 Digital Periodical Chatter Inputs Record:
Occurrence: This Record will be created to notify the CMU about the Chatter
inputs of Data logger. It will created along with periodical all input status
records.
Input Number (2 bytes)
Input Status (1 byte)
Input Status: No significance
A.2.9 Analog Periodical all input Status Record:
This record will be created at power-on/Reset. And this will be created at
every 68 minutes.
Occurrence: This record will be created whenever the difference of previous
recorded channel value and present scanned channel value of a particular
input crosses the configured tolerance limit..
BLOCK 0
BLOCK 1
BLOCK 2
CHANNEL VALUE : 0 TO 4095 (Value 4095 is equivalent to Maximum
possible Channel value for that input). The nominal voltages and their
corresponding maximum voltages are shown in the below table
Channel Number: 1 TO 96
A.2.10 Primary Data Backup Module Status Record:
This record will be created to notify the health Data Logger SD Card to CMU.
Occurrence: This record will be created at regular time intervals, or when the
failure occurred with reference to SD-card.
BLOCK 0
BLOCK 1
00 00 00 Back-up module is reset
01 00 00 Back-up module is formatted due to no data
01 00 01 Card formatted due to Boundary validation fail
01 00 02 Card formatted due to Linearity validation fail
02 00 00 Card not found at Power On/Reset
02 01 00 Card not found in running condition
03 00 00 Card failure at Power On/Reset due to erase
failure
03 01 00 Card fail at power on due to card functionality fail
03 02 00 Card fail at running condition due to root
directory sector fail
03 03 00 Card fail at running condition due to more no. of
bad sectors
04 03 00 Retrieving terminated abnormally
05 00 Sector no. Root sector read operation fail
05 01 Sector no. Root sector write operation fail
MSB bits
Card is in healthy condition and no. of bad data
sectors in the card.
A.2.11 Secondary Data Backup Module Status Record:
This record will be created to notify the health Data Logger SD Card to CMU.
Occurrence: This record will be created at regular time intervals, or when the
failure occurred with reference to SD-card.
BLOCK 0
BLOCK 1
HELTH BYTES (3 bytes)
HEALTH BYTES:
1 ST
00 00 00 Back-up module is reset
01 00 00 Back-up module is formatted due to no data
01 00 01 Card formatted due to Boundary validation fail
01 00 02 Card formatted due to Linearity validation fail
02 00 00 Card not found at Power On/Reset
02 01 00 Card not found in running condition
03 00 00 Card failure at Power On/Reset due to erase
failure
03 01 00 Card fail at power on due to card functionality fail
03 02 00 Card fail at running condition due to root
directory sector fail
03 03 00 Card fail at running condition due to more no. of
bad sectors
04 03 00 Retrieving terminated abnormally
05 00 Sector no. Root sector read operation fail
05 01 Sector no. Root sector write operation fail
MSB bits
Card is in healthy condition and no. of bad data
sectors in the card.
09 Card size in MB Card size available.
A.3 Diagnosis Records:
A.3.1 Data Logger Reset record:
Occurrence: This Record will be created whenever the Data Logger is Reset/
Power ON.
FF H – Watch Dog Reset.
BLOCK 0
BLOCK 1
A.3.2 Digital / Analog / Communication Card Health Record:
This record will be created to notify the connectivity status of Data Logger
Cards to CMU during Power ON/Reset/ any abnormal conditions.
BLOCK 0
BLOCK 1
Card Type (1 byte)
Card Number (1 byte)
Reserved (3 bytes)
BLOCK 2
Card Type: This will indicate the type of card as follows.
01H: Digital Card.
02H: Analog Card.
03H: Communication Card.
Card Number: It will indicate the card number range from 00H to FFH.
Version: It will indicate the card number range from 00H to FFH.
Health: 00 - Health OK.
01 - Health Fail
Previous fail type: This will indicate the type of previous link fail type.
00H: Card Reset.
FFH: Card Abort.
BLOCK 0
BLOCK 1
Card Type (1 byte)
Card Number (1 byte)
Fail Type (1 byte)
Fail count (2 bytes)
BLOCK 2
Card Type: This will indicate the type of card as follows.
01H: Digital Card.
02H: Analog Card.
03H: Communication Card.
Card Number: It will indicate the card number range from 00H to FFH.
Fail Count: It is ranging from 0000 H to FFFF H.
Fail Type: The different fail types are shown below.
ERROR TYPE BYTES
Update Time Interval to CMU: For every 68 minutes.
A.3.4 Data Base Status Record:
Occurrence: This Record will be created whenever there is a change in the
data logger data base and also at the power-on/ rest.
BLOCK 0
BLOCK 1
Status (1 bytes)
Checksum (4 byte)
Dummy (2 bytes)
Reserved (3 bytes)
Higher Bit B7 indicates Valid or Fail of Data Base
‘0’- Valid data Base
‘1’- Invalid data Base
Remaining bits B6 to B0 will give data base type
00 H – Analog Data Base.
01 H – Digital Data Base.
02 H – SSI Data Base.
03 H – Fault Module Data Base.
Checksum: Existed data base checksum.
A.4 ACKNOWLEDGEMENT PACKET:
The length of the frame is always fixed to 20 bytes in spite of the number of
event packets received are less than 3 also. In that case the other
acknowledges are filled with zero. The acknowledgement packet structure is
given below
Block 0
AA H
FROM ID NO (LSB)
CRC (LSB)
START: AAH, 99H are the start identifiers.
FROM ID NO : Indicates the data logger ID from which the acknowledgement
is sent.
DATALOGGER ID-1: Signifies the DL-ID in the first event packet received.
DATALOGGER ID-2: Signifies the DL-ID in the second event packet received.
DATALOGGER ID-3: Signifies the DL-ID in the third event packet received.
SERIAL NO: Signifies the serial number of the received event packet.
CRC: Signifies the validation Byte for this acknowledgement packet. This CRC
will be calculated for block0 from top to bottom.
END: BBH, BBH are the end identifiers.
A.5Command Format:
Start AA
Block 0
3.1 BLOCK0:
Start: Every command frame will be started with these two identifiers. The
identifiers are
2 AAH
3 CCH
Length: The LENGTH is represented in two bytes as 16-bit value. It defines
the no. of bytes in between Source ID MSB and CRC LSB. Inclusive of both.
Control Field: The control field will have the following fields.
Field Name No.of Bytes
Type Identifier 1
Source ID 2
Destination ID 2
Port No 1
Seq No 1
Source ID: This byte signifies from where the command is originated.
Destination ID: This byte signifies to where the command has to reach.
Sequence Number: This byte is generated by the CMU. And CMU
anticipates the same byte should be echoed in the acknowledgement
command, otherwise CMU treats acknowledgement as invalid.
Port Number: FEP is having 6 Ports in 6 directions. CMU can send the
command in any direction/s by placing ‘1’ in the relevant bit/s in the field.
Byte structure:
Document Title: Draft Specification for Data Logger System for Railway S

Documents

SPECIFICATION FOR DATA LOGGER SYSTEM FOR RAILWAY S&T