ChargeLink Native
Developed byDEVlink

First Successful Session: 15-Minute Tutorial

This tutorial proves the installation, license, profile catalogue, gRPC service, and a local EVSE/EVCC flow without connecting physical charging equipment. For a complete new-workstation sign-off, continue with First 60 Minutes and Environment and Bench Preflight after this quick tutorial.

1. Confirm the environment


chargelink --version
chargelink profile list --json
chargelink doctor --json

2. Start the gRPC agent

Open PowerShell window 1:


chargelink integration serve `
  --listen 127.0.0.1:50051 `
  --state-root C:\ChargeLinkData\runtime\grpc

Leave this window open. The process should remain running.

3. Check agent health

Open PowerShell window 2:


chargelink integration health `
  --endpoint http://127.0.0.1:50051 `
  --json

chargelink integration capabilities `
  --endpoint http://127.0.0.1:50051 `
  --json

4. Run the gRPC session lifecycle smoke test


chargelink integration session-smoke `
  --endpoint http://127.0.0.1:50051 `
  --protocol iso15118-20 `
  --role evse `
  --json

This creates, starts, stops, and deletes a session through the public Integration API.

5. Validate an EVSE profile without opening network sockets


chargelink evse start `
  --dry-run `
  --protocol iso15118-20 `
  --profile-id iso15118_20_dc `
  --json

Record the returned session ID. Then inspect and stop it:


chargelink evse status --json
chargelink evse list-state --json
chargelink evse stop --json

6. Run the local EVCC loopback smoke


chargelink evcc local-loopback-smoke `
  --protocol iso15118-20 `
  --profile-id iso15118_20_dc `
  --peer-ipv6 '::1' `
  --tcp-port 50118 `
  --max-steps 6 `
  --battery-model constant_power_reference `
  --battery-capacity-kwh 80 `
  --initial-soc-pct 20 `
  --target-soc-pct 80 `
  --requested-power-kw 50 `
  --battery-step-seconds 1 `
  --json

7. Locate evidence


Get-ChildItem C:\ChargeLinkData\artifacts -Recurse | Sort-Object LastWriteTime -Descending | Select-Object -First 30

A successful first run means that the CLI works, the license is readable, the gRPC endpoint responds, and a deterministic protocol flow can generate evidence. It is not proof of physical-layer interoperability.

HomeTop