STEP 01 / 06
Bring the real software into SIL
The EVCC application runs as a virtual ECU in the customer’s SIL environment. The software under test remains the focus.
DEVlink / ChargeLinkMake every charging
CHARGELINK
Make every charging
conversation clear.
Simulate EVSE and EVCC roles. Investigate protocol behaviour. Connect each session to traces and results your team can use.
Discuss an evaluation ↗Read the documentation ↗THE ENGINEERING STORY / 48 SECONDS
Inside a virtual charging test.
Follow the engineer’s journey from real EVCC software to a repeatable SIL verification workflow.
CHARGELINK / EVCC IN SIL · 01
Start with real EVCC software.
EVCC APPLICATION SOFTWARE
CHARGELINK / EVCC IN SIL · 02
Bring it into the virtual lab.
EVCC application→vECU in customer SIL
CHARGELINK / EVCC IN SIL · 03
Make execution repeatable.
CLI-DRIVEN WORKFLOW
01 Prepare configuration
02 Start scenario
03 Collect session evidence
Workflow illustration · not executable commandsCHARGELINK / EVCC IN SIL · 04
Watch the conversation.
EVCC vECUSoftware under test
Charging communication
ChargeLinkConfigured test role
CHARGELINK / EVCC IN SIL · 05
Interrupt. Observe. Understand.
EVCC vECUSoftware under test
Charging communication
ChargeLinkConfigured test role
Communication interruptedInspect the controller response
CHARGELINK / EVCC IN SIL · 06
Turn evidence into the next test.
Expected responseObserved signal
Illustrative signals · time →
00:00 / 00:48
STEP 02 / 06
Connect ChargeLink to the target
Configure the interfaces between the virtual EVCC and ChargeLink for the intended test setup. Confirm compatibility for the selected environment.
STEP 03 / 06
Define the charging scenario
Select the supported role and protocol configuration for the project. Use the CLI to integrate session setup and execution into the existing workflow.
STEP 04 / 06
Follow the charging communication
Execute the scenario and observe how the EVCC software responds. The moving connection represents communication, not a live protocol trace.
STEP 05 / 06
Explore an interrupted session
In this illustrative test, communication stops. Review the session evidence and the controller response against the project’s expected behaviour.
STEP 06 / 06
Review the evidence. Repeat the test.
Use the results to investigate behaviour and repeat the scenario after software changes. Exact automation and evidence handling depend on the integration.
1 / 6
The real automotive Tier 1 case confirms EVCC-as-vECU verification, CLI integration and on-time software delivery and testing. This walkthrough’s individual scenario stages are illustrative; the customer’s SIL platform was not identified as DEP.
Read the real Tier 1 case ↗CHARGELINK
EVSE / EVCC simulation
+Protocol investigation
+SIL / HIL integration
REAL CUSTOMER APPLICATION / AUTOMOTIVE TIER 1
Real software.
Virtual environment.
On-time delivery.
An automotive Tier 1 verified its real EVCC software as a vECU in SIL. Easy integration with ChargeLink through the CLI helped the project deliver and test its software on time.
Read the customer story ↗ONE CONNECTED WORKFLOW
From setup to diagnosis.
Configure
Select the role, protocol profile and software or hardware environment. Make the system boundary explicit.
Run & observe
Execute a controlled session and follow discovery, transport, security and protocol-state behaviour.
Investigate & reuse
Review traces and diagnostics. Preserve the configuration and evidence for comparison and repeatable testing.
PROTOCOLS & PROFILES
The right profile.
The right evidence.
Protocol names alone do not define support. Check the role, charging mode, release and environment against the documented capability boundaries.
CONNECT THE ENVIRONMENT
Engineering beyond one tool.
Operator workflows
Move from guided setup into detailed investigation within the engineering environment.
Automation & integration
Use documented CLI, gRPC and integration interfaces. Explore the NI VeriStand Native Gateway in the user documentation.
Clear physical authority
The customer’s safety controller, power electronics and bench-specific adapters retain authority for physical actuation.
BEFORE YOU DECIDE
The practical questions.
Who is ChargeLink for?
EVCC, OBC and EVSE development teams, protocol engineers, integration teams and engineers building repeatable charging tests. The starting point is one defined charging problem.
Can I start without connecting a vehicle or charger?
The documentation includes a software-only first-session workflow. Use it to establish a baseline before preparing the actual network, hardware and bench environment. Follow the first-session guide.
Does every listed standard have the same level of support?
No. Support depends on the installed release, role, profile, mode and environment. Read the capability boundaries and version matrix before selecting a configuration.
Can it work with our existing test environment?
ChargeLink exposes documented automation and integration interfaces, including CLI, gRPC and the NI VeriStand gateway. Hardware, adapters, timing and safety responsibilities are confirmed for your specific setup.
How do we get access and pricing?
Request a scoped technical evaluation. The supplied package, licensing, commercial terms and support arrangements are agreed directly with DEVlink.
YOUR NEXT MOVE
Prove it against your use case.
ChargeLink is available through a scoped technical evaluation. Agree the profile, role, environment and evidence before starting.