THE CUSTOMER STORY
Verify the real software.
Keep the project moving.
The customer was an automotive Tier 1 working with electric vehicle charging controller software. Its project needed to verify the real EVCC application in a Software-in-the-Loop (SIL) environment and complete software delivery and testing within the project schedule.
The EVCC software ran as a virtual ECU, or vECU. That made the real application software the subject of verification inside the virtual environment. The case concerns software execution in SIL; it does not describe a physical EVCC connected to a hardware test bench.
The challenge: make the integration fit the project.
A SIL environment brings software components and test tools together. For this project, ChargeLink needed to fit into that environment so the team could use it while verifying the EVCC vECU. Integration effort mattered because the project still had software to deliver and tests to complete.
The useful question was practical: how could the team bring ChargeLink into its existing SIL work with an integration approach that was straightforward to use?
The solution: connect ChargeLink through its CLI.
The team integrated ChargeLink through its command-line interface (CLI). This gave the project a way to invoke ChargeLink from its SIL workflow and use it alongside the EVCC software running as a vECU.
The customer reported that the integration was easy. That ease of integration was central to the result: ChargeLink became part of the verification environment in time to support the project’s software delivery and testing.
How the pieces fit together
- EVCC software running as a vECU
- The real electric vehicle charging controller application was the software under test in the virtual environment.
- The customer’s SIL environment
- The environment provided the context for executing and verifying the EVCC vECU.
- ChargeLink through CLI integration
- The command-line interface connected ChargeLink to the project’s SIL workflow for EVCC verification.
This distinction matters: the CLI was the integration mechanism for ChargeLink. It should not be confused with the charging protocol exchanged by the controller.
The outcome: software delivered and tested on time.
The project managed to deliver and test its software on time. According to the customer experience shared with DEVlink, straightforward integration with ChargeLink through the CLI helped the team achieve that outcome.
The result demonstrates a practical use of ChargeLink in an automotive SIL environment: real EVCC software can be the verification target as a vECU, with ChargeLink connected through a command-line integration.
Why this case matters to other teams.
For teams developing EVCC software, tool integration is part of the engineering work. A tool needs to fit the environment where the software is already being executed and verified. In this case, the CLI provided that connection and helped the project stay on schedule.
The relevant starting point for another team is therefore a representative EVCC vECU and its intended SIL workflow. That gives the discussion a concrete focus: how ChargeLink will be invoked, which interfaces the environment needs, and what the team must verify.
This anonymous customer account is based on project information provided by DEVlink. The customer name, vehicle programme, SIL platform, protocol profile and quantitative performance metrics are not disclosed.