ChargeLink Native
Developed byDEVlink

ChargeLink gRPC Agent

The ChargeLink gRPC agent exposes chargelink.integration.v1 to local applications, the VeriStand Native Gateway, desktop clients and approved remote agents. It is the stable automation boundary between protocol sessions and external tools.

Start locally


$CL = 'C:\Program Files\ChargeLink Native\bin\chargelink.exe'
& $CL --json `
  --runtime-root 'C:\ChargeLinkData\runtime' `
  --artifact-root 'C:\ChargeLinkData\artifacts' `
  integration serve `
  --listen 127.0.0.1:50051 `
  --state-root 'C:\ChargeLinkData\runtime\grpc'

Keep this window open. A local-only listener is recommended for first use.

Verify health and capabilities


& $CL --json integration health --endpoint http://127.0.0.1:50051
& $CL --json integration capabilities --endpoint http://127.0.0.1:50051
& $CL --json integration session-smoke `
  --endpoint http://127.0.0.1:50051 `
  --protocol iso15118-2 `
  --role evse

Verify canonical signals


& $CL --json signals list --endpoint http://127.0.0.1:50051
& $CL --json signals smoke --endpoint http://127.0.0.1:50051

Read selected signals:


& $CL --json signals read `
  --endpoint http://127.0.0.1:50051 `
  --signal Vehicle.SocPct `
  --signal Evse.PresentVoltageV

Write only signals reported as writable:


& $CL --json signals write `
  --endpoint http://127.0.0.1:50051 `
  --signal Vehicle.SocPct=35

Use with the VeriStand Native Gateway

Start the gRPC agent first. Then the VeriStand workflow starts a persistent bridge with:


& $CL veristand operator-bridge --endpoint http://127.0.0.1:50051

The OperatorLauncher normally supervises that bridge. Do not run multiple bridges against the same operator workflow unless the customer configuration explicitly supports it.

Network exposure

For remote access, bind only to an approved interface and apply the product's mutual-authentication and service-identity configuration. Do not expose an unauthenticated development listener to a customer network. Coordinate port 50051, firewall rules, certificates and DNS/IP ownership with the site administrator.

HomeTop