Pintsch: Successful Implementation of a Test System for Digital Interlockings
Ensuring cross-vendor interoperability of various subsystems
As part of the Digital Rail Germany Fast-Track Programme, Pintsch is developing a digital interlocking system (DSTW) with standardized interfaces according to NeuPro. The company faces the challenge of ensuring cross-vendor interoperability of the various subsystems. To meet these complex requirements, Pintsch relies on the proven CANoe test and simulation system from Vector.
In the following interview, you will learn about the challenges Pintsch had to overcome in developing and validating new products, why they chose CANoe, and what successes they have achieved so far. Be inspired by these exciting insights into the world of digital control and signalling technology!
Our Customer
PINTSCH is a leading manufacturer of safety-relevant products for railway infrastructure with over 180 years of experience. The company was founded in 1843 by Julius Pintsch and has continued to develop. Today, PINTSCH offers innovative system solutions for level crossings, shunting equipment, axle counting technology, and switch heating systems. The products are characterized by the highest reliability, modularity, and state-of-the-art technology.
The Interviewees
Project Description and Requirements for Testing and Simulation
As part of the Digital Rail Germany Fast-Track Programme, Pintsch has been commissioned to develop a digital interlocking system (DSTW) with standardized interfaces in accordance with NeuPro. Furthermore, Pintsch is responsible as general contractor for one of the seven implementation projects and must ensure cross-manufacturer interoperability of the various subsystems.
Pintsch requires a modular test system for testing the entire DSTW system and to ensure the gradual integration of the DSTW subsystems. This system can be used to perform fully automated test sequences and also to create simulations of virtual communication partners. The test system should cover all test types, from interoperability tests to operational tests and performance tests, and be used both during development and as an acceptance test system.
From Pintsch ’s Perspective, What Are the Biggest Challenges When Testing and Validating New Products?
Pintsch: It's important to us that we achieve a separation of abstraction levels in the architecture of the test environment. The details of communication protocols between the subsystems must be abstracted and must not be relevant at the test case level. It's also important to us that the multitude of configurations for the different constellations of real and simulated participants remain maintainable. For the test environment, this means that easy switching between real and simulated communication participants must be possible.
Another major challenge arises from the multitude of possible array elements and the correspondingly large number of simulators. To avoid difficult-to-maintain, redundant code that a copy-and-paste solution would produce, it is necessary to develop a scalable solution for the simulators, essentially as an array of objects that are individually parameterized but share a common generic behavior model.
Another key challenge for us is ensuring consistent integration into the existing lifecycle management (ELM) system of the development departments. This is important to meet the requirements of the relevant standard regarding traceability and reproducibility of results.
Which Vector Product Portfolio Is Available in This Segment?
Vector: Our CANoe tool simplifies the simulation, analysis, and automated testing of complex systems and networks. Since its market launch in 1996, CANoe has been continuously developed and is now used for the comprehensive validation of a wide variety of communication protocols and bus systems. These include SCI-XX/RaSTA (based on EULYNX and NeuPro ), OPC UA, EtherCAT, CAN, CANopen, Modbus, and MQTT, which are relevant for applications in digital railway signalling. The tool vTESTstudio supports the convenient design of test sequences.
Network communication (Ethernet and CAN) is connected to CANoe via the VN interfaces. Scalable, modular and efficient HIL tests are performed with the VT system. The VIO system is ideal for simple I/O tests. Both systems enable the smooth exchange of analog and digital data. The portfolio also includes the VectorCAST tool for unit tests.
Why Did Pintsch Choose CANoe?
Pintsch: Initially, we consciously decided against developing our own test environment. Our goal was to rely on an established standard solution that offers long-term availability and support and enables us to benefit from future developments of the tool. Furthermore, in the interest of diversity, we wanted to avoid our self-developed products and the test environment using the same protocol stacks. After surveying the market, we found CANoe, a tool that comes with the so-called RaSTA binding, a RaSTA (Rail Safe Transport Application) and BTP (Bahntechnisches Protokoll) stack, and with the EtherCAT option, offering a standardized interface for connecting various devices. Together with the test automation tool vTESTstudio, this meets all of the test environment requirements we mentioned above.
With the help of Vector's Connection Utility, the required connection to the test management tool is also possible. Since we began development at an early stage of market availability of the RaSTA binding, Vector offered us direct developer support as a pilot customer and, above all, the opportunity to influence the further development of the railway-specific features.
What Experiences Have You Had With the Tool? What Has Pintsch Achieved So Far?
Pintsch: We now have simulators for all elements of the command-and-control level in CANoe, allowing an interlocking (ESTW-ZE) to be tested in a simulated environment based on a given project. This also includes operational tests, as we are able to simulate a train journey by stimulating the axle counting systems. We also use CANoe test benches to test real subsystems such as switches, traffic lights, and axle counting systems. In this setup, CANoe assumes the communication role of the interlocking.
As part of the pilot customer partnership, Vector has expanded the fault injection capabilities at the BTP level and also improved the ability to work with arrays of objects. Currently, work is underway to enable fault injection at the RaSTA level as well.
Using the CANoe Execution Adapter and self-developed automation scripts, we were able to set up a consistent tool chain that allows a set of test cases to be executed directly from the Test Management Tool (ETM) in CANoe. Furthermore, with a view to qualifying our test environment, we set up a configuration management system to manage all test environment artifacts within the ELM.
In summary, it can be said that as of today, the test bench concept for system testing is established on the basis of the Vector tool chain and the aim now is to build a test case library on this basis.
How Does Vector Implement the Insights Gained from Collaboration in Product Development?
Vector: Based on the results of our consistently positive collaboration with our pilot customer Pintsch, we have developed an Add-On for CANoe specifically designed to protect control and safety technology elements. This Add-On is now available to all customers. In addition to the basic functionality used by Pintsch for simulating and testing RaSTA participants, it also includes fault injection capabilities at the application and RaSTA levels (EULYNX and NeuPro), as well as support for the OPC UA protocol for the SMI and SDI interfaces. To help new users get started quickly with CANoe, we offer clear example configurations, detailed documentation on the technical capabilities, and a tutorial explaining the first steps in CANoe.
What Activities Does Pintsch Plan for the Future?
Pintsch: First and foremost, we are continuing to work on building a test case library with the aim of achieving complete test coverage based on the system requirements and implementing the tests in the existing test case catalogs.
In addition to the implementation of additional protocols required for testing subsystems, such as OPC UA and AMQP, the further roadmap also includes the qualification of our test environment as a class T2 tool according to DIN EN 50128. We hope to continue the good cooperation with our colleagues at Vector on both of these points.
In the longer term, our goal is to use the Vector test environment as part of a development- accompanying "Continuous Integrate/Build/Test" environment.
