Engineer working on the wiring and control units of a Hardware-in-the-Loop test system.

Sometimes the most important engine run happens before the first drop of fuel is burned.

A growing proportion of engine development at Everllence now begins in the virtual world rather than on the test bench. Digital twins help engineers identify faults earlier, get new fuels ready for practical use faster and avoid thousands of metric tons of CO₂ emissions every year.

All it takes is a tap on the touchscreen to initiate the engine start sequence. The display shows the preparation steps as the exhaust system is vented, lubrication oil pressure is built up and condensation is removed from the cylinders. Sensors continuously feed data into the system, while the control software responds to every change. Slowly, the needle begins to move across the screen. The engine speed rises to 100 rpm before reaching its operating speed of 515 rpm. The engine is running.

And yet the room remains surprisingly quiet. There are no vibrations, no deep roar you would expect from a large engine, no smell of fuel or oil. The only sound is a faint hum coming from an electrical cabinet behind the control station. Inside, a digital twin is simulating the 49/60DF engine.

HiL workstation with monitors, control units and a test wall used for engine control development.
At the HiL workstation, the physical and virtual worlds converge. Around 2,500 wires connect the control units to a digital twin that simulates temperatures, pressures, rotational speeds and load conditions in real time.

Where the virtual and real worlds meet

At Everllence's Hardware-in-the-Loop (HiL) laboratory in Augsburg, engineers test engine control systems long before a real engine is started for the first time. Mounted on a test rig are the actual control units of a 49/60DF engine. Through the HiL environment, they are connected to a digital twin that simulates temperatures, pressures, rotational speeds and load conditions in real time. Around 1,200 signal channels ensure that the control units receive exactly the same information they will encounter later on in real-world operation.

“For the software, there's no difference,” explains Dr Jörg Kinzel, Program Manager Digital Twins & Automated Testing at Everllence. “It receives the same signals and responds to the same operating conditions and faults.” That becomes evident when Kinzel simulates a load change. The rotational speed briefly drops and the control system reacts immediately, increasing the fuel injection and stabilizing operation again. Everything unfolds on the screens exactly as it would on a real test bench, except that the engine consists entirely of data.

Portrait of Jörg Kinzel wearing glasses and a light blue shirt.
“For the software, there's no difference. It receives the same signals and responds to the same operating conditions and faults.”

Dr Jörg Kinzel, Program Manager Digital Twins & Automated Testing at Everllence

Even fault scenarios and critical operating conditions can be deliberately created. Some situations, such as a dangerous pressure increase, would involve considerable risks on a real engine. At the HiL station, the test team can safely simulate these events and check whether the software's safety functions respond correctly and trigger a shutdown in time. What was often impossible in the past, or required creative workarounds, can now be simulated with a few clicks.

“In the past, people even put a temperature sensor in a kettle to simulate overheating,” Kinzel recalls. “In rare cases, these scenarios are still demonstrated on a real engine during type approval testing. But confidence in Hardware-in-the-Loop testing has increased significantly over the past few years.”

Less fuel, more insights

The impact of this extends far beyond the laboratory. Every test that no longer has to be conducted on a physical test bench saves fuel, resources and emissions. Engine and component testing alone accounts for roughly 58 percent of the direct emissions generated at the Augsburg site. That is why Everllence continues to shift more and more development and validation work to HiL test systems.

A glance at the figures shows the scale of the potential. In a single year, approximately 28,000 metric tons of CO₂ emissions were avoided through virtual engines running for around 7,000 operating hours. That is roughly equivalent to the annual emissions of 15,500 passenger vehicles. On average, every customer project can save around 900 metric tons of CO₂.

The impact at a glance

57.7
%
of Scope 1 emissions at the Augsburg site are generated by engine and component testing.
28000
tons
CO₂ avoided in one year through virtual engine operation.
900
tons
CO₂ is the average emissions saving per customer project.

Better software faster

The environmental benefits are impressive. In day-to-day development, however, there is another, often even more important advantage: faults can be identified much earlier. In the past, engineers sometimes had to wait days or even weeks for a test bench to become available to test a new software release. Now, results are often ready within minutes. When an issue is identified, engineers can immediately analyze it, correct it and run the test again. As a result, by the time the team gets to work on the real engine, the software is far more mature. “The earlier we find a fault, the faster and less expensive it is to fix,” says Kinzel. “If an issue only becomes apparent on the test bench or even in the field, the time and effort involved increases dramatically.”

Another benefit is how quickly the test wall can be adapted to different engine platforms. “We only need to replace a few components, modify the control units or add a sensor,” Kinzel explains. “It doesn’t really matter to the HiL system itself. We load the appropriate digital twin and continue testing.”

Engineer working on an electronic test setup with measuring equipment and a circuit board in a laboratory environment.
While many functions were once developed in small standalone test setups, the Hardware-in-the-Loop-system now makes it possible to observe how different functions interact.

HiL technology is also changing the way teams work together. Software developers, testers and functional engineers now collaborate far more closely. “In the past, individual functions were often developed in isolation in small desktop test setups,” Kinzel says. “Now many developers prefer the HiL environment because they can directly observe the interaction between different functions.” He adds: “In modern engines, success or failure is often determined not by individual functions, but by how different control and safety systems work together.”

Despite all of this, the physical test bench remains indispensable for software development. The final five to ten percent of its validation still takes place on the real engine. Subsequently, the control system is fine-tuned for its future application and customer-specific requirements. Only there can engineers account for the last remaining differences between simulation and reality, including component tolerances and exact behavior. “No two engines are exactly the same,” Kinzel says. “That's why we use the test bench to reconcile the final differences between the model and reality.” Yet the test bench is about much more than validating software. Beyond the control system, it is where the complete engine and the interaction of all its mechanical components are put to the test under real-world conditions.

Why modern engines require new tools 

The strengths of HiL testing become particularly evident when it comes to developing solutions for future fuels. While diesel engines have been optimized over decades, more climate-friendly energy carriers introduce entirely new challenges. “Modern dual-fuel engines and alternative fuels such as methanol lead to significantly more complex combustion processes,” Kinzel explains. “At the same time, control systems have to operate with much greater precision to reliably ensure safety, efficiency and emissions performance.” Digital twins allow engineering teams to get to grips with these complex relationships earlier on and explore new concepts long before a physical engine is built.

Quote
“The most important task of software is to ensure safe engine operation at all times. To do that, it needs to understand far more today than it did in the past.”  

Dr Jörg Kinzel, Program Manager Digital Twins & Automated Testing at Everllence

The future is already running 

The testing capabilities themselves continue to evolve. Everllence now operates five HiL stations in Augsburg, with six additional systems planned in the medium term. This expansion will not only increase testing capacity; it will also lay the foundations for the next step: automated testing.

Recurring test procedures will increasingly be carried out and documented automatically, even outside regular working hours. At the same time, the team is working to simulate additional environmental conditions, different load types and corresponding scenarios like power grid faults.

Engineer working with a laptop among newly installed HiL test systems and cabling infrastructure.
Everllence continues to expand its HiL infrastructure. Additional test stations will increase capacity and pave the way for automated testing.

For Kinzel, however, the vision goes even further. His long-term goal is a seamless digital development chain that begins with the very first line of software code and ends only when the control system has been fully validated for the customer's engine. The more processes are automated and the earlier faults are identified, the faster new functions, new fuels and new technologies can be brought into real-world operation. 

The real engine may not reach the test bench until weeks later. By then, much of what makes it safe, efficient and reliable will already have been tested on its digital twin, long before the first drop of fuel is burned.