Communication behaviour
Process data (PD: publisher/subscriber, PD request/reply) and message data (MD: notification, request-reply, request-reply-confirm).
Testing as a Service
TRDP conformance test to IEC 61375-2-8 – as a service
For subsystem and device manufacturers, OEMs and integrators: the independent, reproducible proof that a device operates in conformance with the standard and interoperably within the train communication network – without building a test system of your own.
- IEC 61375-2-8
- ISO 9001
- ISO 27001
- TCN · TCNOpen
- Vendor-neutral
The situation
Why conformance decides whether a project succeeds
One standard, different interpretations: that is exactly where interoperability problems come from, and they often surface late – during integration, in the interplay with devices from other suppliers. That drives up development effort, delays projects and can put successful completion at risk.
For safety-critical and time-critical systems in particular, “it works” is not enough. What counts is the evidence that a device really does behave in conformance with the standard and interoperably.
Test scope
What we test
Data packets and addressing
PDU structure with header, sequence counter and topology counters (etbTopoCnt, opTrnTopoCnt), ComId and dataset, plus the well-known ports PD 17224 and MD 17225.
Data encoding
Endianness, alignment, data length and data type.
Error handling and redundancy
Response to error conditions, including behaviour on error message.
Safe data transmission (SDTv2)
Testing of the safety layer – safety attributes, error detection and error response.
Interoperability
Interaction with devices tested to the same level, not just within one setup.
Procedure
How the test works
-
Test specification
We derive the test cases directly from IEC 61375-2-8 and adapt them to the project requirements where needed.
-
Integration
A predefined REST API test interface connects the implementation under test (IuT) – matching the project application.
-
Automated execution
The test runs reproducibly on our automated test system, independently of the operating system of the implementation.
-
Test report
The result is solid evidence of conformance, with detailed feedback on every deviation from the expected behaviour.
The difference
Why test with Codewerk?
-
A central, independent body – vendor-neutral evidence that holds up with OEMs, integrators and operators.
-
The test environment is already in place – ready to run, reproducible, derived directly from the standard.
-
Purely software-based – no test system of your own, no additional hardware.
-
Integration and testing from one source – no break between development and proof of conformance.
-
Early instead of expensive – the earlier deviations surface, the lower the follow-up cost.
Audience
Who the test is for
For subsystem and device manufacturers building devices or applications with TRDP who need solid evidence of conformance for integration and acceptance – and for OEMs and integrators who want to de-risk supplied components.
Questions and answers
Frequently asked questions
As a rule, yes. OEMs, integrators or operators require evidence that the device behaves in conformance with the standard inside the TCN.
IEC 61375-2-3 describes the TRDP communication and application profile, IEC 61375-2-8 the conformance test specification. Testing is done against 61375-2-8.
No. The test is independent of the operating system.
As early as possible. Faults found late cause the highest follow-up cost and put schedules at risk.
A detailed test report as traceable evidence of conformance.
A dependable partner
More products and services
Related offerings
SOFTSIBAS PN validation test
Proven conformity with SIBAS PN through tests by PROFINET, PROFISAFE, services and project planning.
Learn more
SOFTSIBAS TRDP Stack
With our software-based solution SOFTSIBAS TRDP Stack, you don’t need additional hardware.
View product
SOFTSIBAS PN Stack
With our software-based solution SOFTSIBAS PN Stack, you don’t need additional hardware.
View productContact
Ready for proof of conformance?
Outline the project briefly – device or application, planned acceptance date. We will come back with the next steps.
Not there yet? Download the TRDP conformance checklist (PDF, 95 KB) – it shows at a glance what solid evidence of conformance covers.