ChargeLink Documentation
Docs/Reference

Operator Manual

Daily startup

  1. Inspect the bench and confirm the high-voltage area is safe.
  2. Confirm emergency stop operation.
  3. Confirm isolation monitoring and interlock status.
  4. Start the ChargeLink gRPC agent.
  5. Run the health check.
  6. Start the required EVSE, EVCC, HIL, or XIL workflow.
  7. Confirm profile, protocol, role, interface, and peer identity before enabling energy flow.

chargelink integration health --endpoint http://127.0.0.1:50051 --json
chargelink runtime list --json

Start a session

Use a dry-run first after any configuration change:


chargelink evse start --dry-run --profile-id iso15118_20_dc --json

Then use the approved site command from your bench procedure. Record the generated session ID and artifact directory.

During a run

Monitor state and diagnostics:


chargelink evse status --json
chargelink evse list-state --json
chargelink diagnostics list --json
chargelink runtime list --json

Check these conditions continuously on a physical bench:

- Emergency stop clear.

- Isolation and interlock valid.

- Command age below watchdog threshold.

- Voltage/current within bench limits.

- Requested and measured power have expected signs.

- No unexpected protocol retry loop.

Normal stop


chargelink evse stop --json
chargelink evcc stop --json
chargelink runtime list --json

For VeriStand, stop the session, bring current to zero, open contactors, shut down the operator workflow, and undeploy/disconnect the project.

Emergency response

  1. Use the physical emergency stop.
  2. Confirm output current is zero and contactors are open.
  3. Do not reset a fault until the cause is understood.
  4. Preserve logs and evidence.
  5. Follow the site electrical safety procedure.

End-of-day evidence

Copy or archive:

- ChargeLink artifacts.

- Session and diagnostic JSON.

- VeriStand logs and project version when applicable.

- Charger profile and site configuration.

- Test report and operator notes.

Change control

Repeat the commissioning smoke tests after changing software version, license, profile, certificate set, network interface, CAN adapter, VeriStand project, signal mapping, model, or safety wiring.

© 2026 devLink AB · Contact support ↗

Search across the complete documentation.