Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a226c642481cf814

Jump to content

Draft:Software-in-the-loop

From Wikipedia, the free encyclopedia

Unlike hardware-in-the-loop (HIL), the software-in-the-loop (SIL) method does not require any special hardware.[1] The original ECU code is written to a file – usually a dynamic link library (DLL) – using an automated coding process. This DLL can be integrated into an environment model in a simulation tool (e.g., MATLAB Simulink). The DLL is then tested in a purely virtual model environment. Unlike the hardware-in-the-loop (HIL) method, no control unit or real-time simulator is required.

SIL simulators do not run in real time; the simulation can be paused at any time for debugging purposes. Hardware-related run-time issues or variable overflows that occur on the real ECU are difficult to detect using SIL simulations.

Other advantages of SIL include the fact that the target hardware does not need to be specified in advance and that costs are significantly lower due to the absence of a simulation environment. The simulation model used here can also be reused in subsequent HIL simulations, allowing the individual test runs to be compared with one another.

References

[edit]
  1. ^ Schäuffele, Jörg; Zurawka, Thomas (2010-01-27). Automotive Software Engineering: Grundlagen, Prozesse, Methoden und Werkzeuge effizient einsetzen (in German). Vieweg+Teubner Verlag. ISBN 978-3-8348-0364-1.

Category:Control engineering