F.8 ETB Control Service conformity test
F.8.2 Test control interface for the test of ETB control services
The test of communication services aims to check the following functions:
• Proper detection of (different) train topologies.
• Handling of leading vehicle requests.
• Handling of confirmation and correction.
• Handling of sleep request.
F.8.2.2 Test control telegram
The Test Control Telegram is cyclically sent point-to-point from the tester to the UuT (ECSC emulation) (Figure F.6). Upon reception of a command from the tester, the UuT (ECSC emulation) shall forward this command to its ECSP for execution.
Figure F.6 – Conformance test control telegram TRDP PD telegram parameters:
Message type: ‘Pd’
ComId: 80
Destination: IP address of UuT device executing the test function (unicast)
Dataset: CONFTEST_CTRL
Cycle time: (1,0 ± 0,1) s
Timeout: 5,0 s
If the receiving UuT detects a timeout, the UuT shall reset waiting for the start of a new test run.
The TRDP telegram is defined as shown in Figure F.7.
Figure F.7 – Conformance test control telegram data The payload of the TRDP process data is defined as follows:
CONFTEST_CTRL::= RECORD
{ version VERSION -- telegram version information main version = 1
subversion = 0 reserved01 UINT16 -- reserved (= 0)
IEC
0 7 8 1516 2324 31
version
deviceName
inhibit leadingReq leadingDir reserved reserved
reserved
sleepReq reserved
IEC
tester test control datagram (TRDP-PD) UuT
deviceName LABEL -- function device of tester which sends the telegram
inhibit UINT8 -- inauguration inhibit 0 = no inhibit request 1 = inhibit request leadingReq UINT8 -- leading request
0 = no leading request 1 = leading request leadingDir UINT8 -- leading direction
0 = no leading request
1 = leading request direction 1 2 = leading request direction 2 reserved02 UINT8 -- reserved (= 0)
sleepReq UINT8 -- sleep request
0 = no sleep request 1 = sleep request reserved03 UINT8 -- reserved (= 0) reserved04 UINT16 -- reserved (= 0) }
F.8.2.3 Test status telegram
The Test Control Data Telegram is cyclically sent point-to-point from the UuT to the tester (Figure F.8).
Figure F.8 – Conformance test status telegram TRDP PD telegram parameters:
Message type: ‘Pd’
ComId: 81
Destination: test function of the tester
Dataset: CONFTEST_STATUS
Cycle time: (1,0 ± 0,1) s
Timeout: 5,0 s
The TRDP telegram is defined as shown in Figure F.9.
IEC
tester test status datagram (TRDP-PD) UuT
Figure F.9 – Conformance test status telegram data The payload of the TRDP process data message is defined as follows:
CONFTEST_STATUS::= RECORD
{ version VERSION -- telegram version information main version = 1
subversion = 0 status UINT8 -- status of the UuT
0 = ready
> 1 = error detected (UuT specific) reserved01 UINT8 -- reserved for future use (= 0)
deviceName LABEL -- function device of UuT which sends the telegram
}
F.8.2.4 Confirmation request F.8.2.4.1 General
This message is sent by the tester to request (un-)confirmation and to inform the UuT about corrections rules. This is done by sending a corrected sequence of vehicles. Vehicle gaps are identified by parameter ‘trnVehNo’ set to 0, see Figure F.10.
Figure F.10 – (Un-)confirmation request F.8.2.4.2 Request message
TRDP MD request message parameters:
MsgType: ‘Mr’
Protocol: UDP
ComId: 82
SourceURI (user part): “ComProfTester”
DestinationURI (user part): “ComProfTestAppl”
IEC
tester UuT
confirmation message (TRDP-MD) confirmation reply (TRDP-MD)
IEC
0 7 8 1516 2324 31
version
deviceName
reserved status
DestinationURI (host part): test function of the tester SourceURI (host part): user defined
Dataset: CONFTEST_CONF_REQUEST
ReplyTimeOut: Defined by tester. Default value: 2,5 s The TRDP message is defined as shown in Figure F.11
Figure F.11 – Conformance test confirmation/correction request data The payload of the TRDP request message is defined as follows:
CONFTEST_CONF_REQUEST::= RECORD
{ version VERSION -- telegram version information main version = 1
subversion = 0 command UINT8 -- confirmation order
0 = no command (message to be ignored)
1 = confirmation/correction request
2 = un-confirmation request
reserved01 UINT8 -- reserved (= 0)
deviceName LABEL -- device name of tester which sends the telegram
reserved02 UINT16 -- reserved (= 0) reserved03 UINT8 -- reserved (= 0)
confVehCnt UINT8 -- number of confirmed vehicles in the train (1..63).
if set to 0: no correction confVehList ARRAY [confVehCnt] OF OP_VEHICLE
-- ordered list of
IEC
0 7 8 1516 2324 31
version
deviceName
ARRAY [confVehCnt] OF
VehId
0 trnVehNo
opVehNo
reserved confVehCnt
reserved
0
reserved
vehOrient 0
command
reserved
confirmed vehicles in the train, starting with vehicle at train head, see chapter 5.3.3.2.10.
Parameters ‘isLead’, ‘leadDir’
and ‘ownOpCstNo’ to be set to 0.
}
F.8.2.4.3 Reply message
TRDP MD reply message parameters:
ComId: 83
Dataset: CONFTEST_CONF_REPLY
The TRDP message is defined as shown in Figure F.12.
Figure F.12 – Conformance test confirmation/correction reply data The payload of the TRDP reply message is defined as follows:
CONFTEST_CONF_REPLY::= RECORD
{ version VERSION -- telegram version information main version = 1
subversion = 0
status UINT8 -- status of storing correction info 0 = correctly stored
1 = not stored
reserved01 UINT8 -- reserved (= 0)
deviceName LABEL -- function device of ECSC which sends the telegram
}
F.8.2.5 Operational train directory request
The operational train directory request is sent as a TRDP-MD request expecting a TRDP-MD reply containing a copy of the operational train directory as computed by the UuT (Figure F.13). This request provides a possibility to check the correct computation of the TTDB.
IEC
0 7 8 1516 2324 31
version
deviceName
reserved status
Figure F.13 – Conformance test operational train directory request TRDP MD request message parameters:
Message type: ‘Mr’
Protocol: UDP
ComId: 84
SourceURI (user part): “ComProfTestAppl”
DestinationURI (user part): “ComProfTester”
DestinationURI (host part): test function of the UuT SourceURI (host part): user defined
Dataset: CONFTEST_OPTRAIN_REQUEST
ReplyTimeOut: Defined by tester. Default value: 2,5 s The TRDP message is defined as shown in Figure F.14.
Figure F.14 – Conformance test operational train directory request data The payload of the TRDP request message is defined as follows:
CONFTEST_OPTRAIN_REQUEST::= RECORD
{ version UINT16 -- telegram version information main version = 1
subversion = 0 command UINT8 -- command to UuT
0 = no command (message to be ignored) 3 = respond operational train directory reserved01 UINT8 -- reserved (= 0)
deviceName LABEL -- function device of tester which sends the telegram
}
IEC
0 7 8 1516 2324 31
version
deviceName
command reserved
IEC
tester operational train info response UuT
operational train info request
TRDP MD reply message parameters:
ComId: 85
Dataset: CONFTEST_OPTRAIN_REPLY
The TRDP message is defined as shown in Figure F.15.
Figure F.15 – Conformance test operational train directory reply data The payload of the TRDP reply message is defined as follows:
CONFTEST_OPTRAIN_REPLY::= RECORD
{ version VERSION -- telegram version information main version = 1
subversion = 0 reserved01 UINT16 -- reserved (= 0)
deviceName LABEL -- function device of tester which sends the telegram
opTrnDir OP_TRAIN_DIRECTORY
-- operational train directory as defined in 5.3.3.2.13
}
IEC
0 7 8 1516 2324 31
version
deviceName
ARRAY [opCstCnt] OF
cstUUID
reserved opCstOrient
opCstNo
reserved
ARRAY [opVehCnt] OF
vehId
leadDir trnVehNo
opVehNo
opCstCnt
opTrnTopoCnt reserved
version (opTrainDirectory) etbId opTrnOrient
opVehCnt reserved
isLead
reserved
vehOrient ownOpCstNo
reserved
reserved
trnCstNo