VeriStand Signal Mapping

The package delivers the complete channel layout and mapping; nothing has to be created or mapped in VeriStand. This page explains what the shipped files define, so that you can read a session's status and evidence and recognise the channels in VeriStand. The setup is in Set Up the VeriStand Bench; the prerequisites (NI VeriStand 2024 Q4, .NET 10 runtime x64, .NET Framework 4.8) are listed on the NI VeriStand Bench page.

The files that define the mapping

The owner host checks the system definition against both contracts when it starts. Use these files as delivered: Start-SeccSession.ps1 always points the session at them, and a changed file no longer matches manifest\SHA256SUMS.

The system definition

• Target Controller: Windows, localhost, engine rate 500 Hz, data rate 50 Hz, watchdog filtering off; primary control loop on logical processor 10, model on 11, secondary loop on 12.
• Model Targets/Controller/Simulation Models/Models/ChargeLink ISO15118-20 DC EIM FMU: 64-bit, base rate 1000 µs, decimation 1, referenced by the relative path ChargeLink\Models\….
• User Channels under Targets/Controller/User Channels/: 50 plant channels in ChargeLink ISO15118-20 DC EIM Plant and 14 operator channels in ChargeLink Operator.
• Mappings: 44. Each of the 26 model inputs is fed from the plant User Channel of the same name (User Channel → Inport); each of the 18 model outputs feeds the plant User Channel of the same name (Outport → User Channel). The 6 parameters are not mapped and keep the model's start values. Operator channels are never mapped to the model.

ChargeLink reads and writes only User Channels, never model ports. You can open the .nivssdf in VeriStand's System Explorer to inspect it; do not save it from there, because a saved file changes its hash.

Plant channels

Folder Targets/Controller/User Channels/ChargeLink ISO15118-20 DC EIM Plant:

The Runtime.* channels let the owner host recognise a stale or corrupted exchange: every command carries a sequence, epoch and checksums, and every sample reports which command it applied. The checksums detect corruption; they do not authenticate a client. The Safety.* inputs are the simulated plant's safety signals; they are not connected to any physical device.

Plant channels and canonical signals

pc1\config\grpc_signal_mapping.json pairs ten plant channels with ChargeLink canonical signals (all paths under Targets/Controller/User Channels/ChargeLink ISO15118-20 DC EIM Plant/):

The other plant channels (session state, contactor and precharge, safety, fault injection, command and sample identity) are exchanged by the owner host directly and have no canonical signal.

Operator channels

Folder Targets/Controller/User Channels/ChargeLink Operator, defined by pc1\config\operator_channel_contract.json. The owner host writes the status channels while it runs.

In the package's procedure you do not set the command channels yourself: in an automated session the owner host runs the whole sequence, and in a manual session you send the matching commands with Send-OwnerCommand.ps1 (ApplySafeStartup, StartSession, StartExternalEvccLane, … ShutdownWorkflow; see Manual session).

Watching the channels during a session

In a manual session, GetStatus prints the owner's current snapshot, including plant values such as EVSE.PresentCurrent_A and EVSE.ContactorClosed and the safety state (typed_safety_terminal, typed_safety_phase):

cd C:\ChargeLink\0.5.0-rc2\pc1
.\Send-OwnerCommand.ps1 -RunDirectory '<run folder>' -Command GetStatus

After every session, <run>\host-output\patch598_stagec_external_evcc_evidence.json holds the recorded plant samples, safety and timing, and <run>\external_evcc_artifacts\fix010-pc1-secc\traces\live-v2gtp-frames.jsonl the ISO 15118-20 messages they were exchanged with (Reading the result).

Troubleshooting

The canonical signal dictionary

chargelink.exe exposes one transport-neutral signal dictionary through the gRPC SignalService (gRPC Integration API). The ten canonical signals above belong to it. The dictionary has 94 signals in 17 namespaces. Bidirectional signals can be written by a client and read back; output signals are produced by ChargeLink and are read-only. Each sample carries a source identity (epoch, sequence, target_time_ms, applied_command_sequence) so that a consumer can detect stale values.

Units are SI base units: watts, not kilowatts; watt-hours, not kilowatt-hours. The bench's gRPC service runs only while an owner host runs and is reserved for it; do not write signals into a running bench session.