For everyone responsible for LV124 / LV148 testing

If you work with LV124 / LV148,
you know this problem.

More ECUs. More pins. More test cases. Less time. And a test setup that was never designed to keep up — manually operated, ECU-specific, and rebuilt from scratch every project.

Who this page is for

Whether you run the tests or manage the team —
this is for you.

You are the test engineer

You set up the hardware, write the test sequences, supervise the runs, and deal with the results. You know exactly where the time goes — and how much of it is wasted on setup, supervision, and chasing inconsistent results.

Start with what you already know →

You manage the testing team

You are responsible for validation timelines, resource allocation, and test quality. You may not operate the system yourself — but you feel the pressure when test cycles run long, results are inconsistent, or your team is bottlenecked before a product release.

Skip to outcomes and ROI →

The daily reality

The problems that come with manual LV124 testing.

These are not edge cases. They are what most LV124 and LV148 test teams deal with every day — and why validation cycles take far longer than they should.

 

Every new ECU means starting over
Manual setups are ECU-specific. When a new DUT arrives, the setup gets rebuilt. The time spent on setup is time not spent testing.

 

Someone has to watch it the whole time
Manual test runs require supervision. Tests can only happen during working hours. Nights and weekends are wasted capacity.

 

Results vary between runs and operators
When a test is set up and executed manually, slight differences between runs are unavoidable. Reproducibility becomes a problem — especially when an OEM asks why results differ.

 

Coverage gaps you might not even know about
Typical manual setups cover basic supply line pulses — roughly one third of what LV124 actually requires. Pinwise interruption tests, communication line checks, and climatic interactions are often left out entirely.

 

The norm keeps evolving
New OEM variants, new interface requirements, new norm updates. Manual setups have no way to keep up systematically — every change is another manual adaptation.

The good news!

Every one of these problems is structural — not a limitation of your team. They are the natural result of using tools that were not designed for the full LV124 / LV148 norm at scale. That is exactly what RTStand was built to solve.
What changes

Before and after — in practical terms.

Not in theory. In the actual day-to-day of a test lab running LV124 validation.

Before
New ECU arrives. The team spends days rebuilding the test setup from scratch — hardware wiring, software configuration, norm selection. Before a single test runs, hours are gone.
↓
With RTStand
The generic system stays the same. Define the new ECU’s pins and select the norm. The setup is done in minutes. Previously tested ECUs can be reloaded instantly.
Before
Test runs happen during working hours only. Someone has to be present to monitor, intervene when something goes wrong, and record what happened. Weekends and nights are idle time.
↓
With RTStand
Tests run fully unattended — nights, weekends, no supervision required. The system monitors everything and logs all data automatically. Come in Monday to a completed run and a report.
Before
Results vary between runs. An OEM questions a result from six months ago — and there is no way to reproduce the exact test conditions from the original run.
↓
With RTStand
100% reproducible results. Every run uses the same setup, the same timing, the same execution. Results from run one and run one hundred are directly comparable.
Before
Test coverage is partial. Basic supply line pulses are covered. Pinwise interruption tests, communication line monitoring, and climatic integration are either manual workarounds or skipped entirely.
↓
With RTStand
Full LV124 / LV148 norm coverage — all disturbance classes, all pinwise tests, CAN, LIN, Ethernet, GMSL, climatic chambers. One system covers everything the norm requires.
Before
A new OEM norm variant is released. Someone has to manually update the test profiles, verify the setup against the new requirements, and re-run affected test cases. This takes weeks.
↓
With RTStand
New norms are integrated through software updates — continuously. Your system stays current with OEM requirements without manual rework. Over 45 norms supported and growing.
Before
A sporadic ECU fault appears in the field. The test team cannot identify when or why it occurred — the test data does not have the resolution or the synchronisation to pinpoint it.
↓
With RTStand
100kHz monitoring per pin. Time-synchronized voltage, current, and bus communication data. Sporadic faults are visible and traceable — earlier in development, before they reach the field.
For department managers

What this means in numbers your organisation cares about.

Structured, automated LV124 / LV148 testing is not just a quality improvement — it is a measurable operational advantage. These are real outcomes from WKS customers.

The same team. The same ECUs. The same norms. Just a test infrastructure that lets them work the way they should — systematically, reproducibly, and at full capacity around the clock.

 

The investment logic
RTStand is available to buy or rent. Financing options allow you to start testing immediately and pay over time — which means the system’s savings often outpace the cost from the first project cycle. Several customers have calculated full ROI within their first software release cycle.

75%

reduction in test cycle time through 24/7 automated runs

50%

reduction in overall testing time vs. previous manual setup

100%

norm coverage vs. ~33% with typical manual setups

150k€

saved per product release
Valeo — ADAS & Lidar testing

24/7

unattended operation — nights, weekends, no supervision

5+

RTStand systems deployed at ZF alone across multiple sites
Find your situation

Where are you right now?

Different starting points lead to different solutions. Pick the one that describes your situation most closely.

Situation A

We are doing LV124 testing manually and it is not scaling

Your team manages the tests with manual or half-automated setups. It works — but barely. As ECU complexity grows, setup time and test cycles are getting longer while pressure to deliver faster increases.

See RTStand →

Replace your setup with full automation
Situation B

We do not have an in-house LV124 test lab yet

You need to validate your ECU against LV124 or LV148 but do not have the infrastructure in place. Either the investment is not yet justified, or you are waiting for a system to be procured.

Use our lab →

Ship your DUT — we run the full norm
Situation C

We are evaluating RTStand before making a purchase decision

You have heard about RTStand or seen it referenced by OEMs or Tier 1 suppliers. Before committing to an investment, you want to see the system running with your own ECU and your own test cases.

Visit our lab →

Assessment day — bring your DUT
Situation D

We are developing a new ECU interface and need a test partner

You are working on a next-generation interface — Automotive Ethernet 1000base-T1, GMSL, or something custom — and need a partner who can test it under LV124 / LV148 conditions before your own infrastructure is ready.

Talk to us →

Proof-of-concept testing in our lab
From engineers who made the switch

What changes when the setup works as a system.

We have been using the RTStand LV124 / LV148 system from WKS Informatik for several years and are very satisfied with its high reliability and the fast, straightforward support. Regular maintenance and calibrations ensure that the system is always ready for use, and the personalized service significantly contributes to our satisfaction

SMR Automotive

The RTStand LV124 / LV148 system from WKS Informatik has not only increased our testing efficiency but also improved the workflow in our laboratory. Collaborating with WKS Informatik allowed us to implement custom adjustments, and we consistently benefit from prompt technical support. This efficiency and support have enabled us to effectively overcome the challenges of our dynamic development processes

Bühler Motor

The concept for automated testing of the LV124 prompted us to purchase a test system. The tests can now actually be performed and analyzed automatically. This saves time and resources. The support is also impeccable, and downtimes are minimized through a fast response time.

Leading automotive lighting supplier

We have reduced the overall testing time to a half compared to the previous manual testing and currently save 150.000 EUR for the LV124 testing of every several new software releases of our product

French automotive supplier

“One crucial advantage of your test system, besides timing and other benefits, is reproducibility! With a fully automated test run, there is no room for slight variations in the test runs anymore.”

Top 5 automotive supplier worldwide

This innovative modular concept, which gives us the opportunity to monitor a high number of pins in parallel, with a high resolution of up to 10us, as required in the LV124, allows us to make a deeper analysis of our products and especially find sporadic errors earlier in the development phase.

Continental™ AG

“..really appreciate the cooperation with you and your company!”

Bavarian car manufacturer

Common questions

Questions we hear most often.

We already have a partially working test setup. Is it worth switching?
That depends on how much your current setup actually covers — and how long it takes to run it. Most teams are surprised to find their manual setup covers only a third of the LV124 norm. RTStand is modular, so it may be possible to integrate some of your specific devices.

 

Our ECUs are very different from project to project. How does RTStand handle that?
RTStand is specifically designed for this. The generic system stays the same across all ECUs — only the DUT-side definition changes. You configure the new ECU’s pins in minutes, and previously tested ECUs can be saved and reloaded instantly for retesting. Several customers with highly diverse ECU portfolios run RTStand across all their product lines.

 

We need to test to specific OEM norms — VW 80000, BMW GS95024, and others. Are these supported?
Yes. RTStand includes a norm library covering over 45 norms including VW 80000, BMW GS95024-2-1, Audi LAH, MBN 10567, ISO 16750, GMW 3172, and many others. New norms are integrated through software updates continuously. See the full norm list.

 

Can we try the system with our own ECU before purchasing?
Yes — this is exactly what our lab assessment day is for. You visit our lab in Ravensburg, bring your DUT, define the test cases you want to run, and observe the system in operation with your own hardware. Most teams make a full day of it. See how the lab visit works.

 

What does the support look like after purchase?
WKS provides onsite or remote startup training, DAkkS-certified calibration, and ongoing maintenance contracts covering software updates and new norm integrations. Technical support is direct — you reach the engineers who built the system, not a call centre. This is consistently cited by customers as one of the most important reasons they stay with WKS long-term.

 

We are also testing 48V systems. Does RTStand cover that?
Yes. RTStand supports 12V, 24V, and 48V power networks — including the LV148 standard which specifically governs 48V automotive systems. The F8-90 variant is designed for ECUs with current consumption up to 90A, which covers high-power 48V applications.

Tell us about your testing challenge.

Whether you are an engineer looking for a better setup or a manager evaluating options — start with a conversation. We will ask the right questions and give you a straight answer about what makes sense for your situation.

Get in touch with us

WKS Informatik GmbH  – Ravensburg, Germany

Imprint – Privacy Policy – Careers

 RTStand – Testing lab – Devices – For Engineers – Company – Knowledge Base – Contact