ChargeLink Native
Developed byDEVlink

Additional Protocol Stacks

ChargeLink Native includes operator-visible surfaces for MCS, NACS/J3400 and ChaoJi/GB/T. Their activation depends on the installed package, license entitlement, hardware and release qualification.

Check entitlement and availability


$CL = "C:\Program Files\ChargeLink Native\chargelink.exe"
& $CL license status --json
& $CL license entitlements --json
& $CL protocol --help
& $CL dc-can catalog --json

MCS


& $CL protocol mcs-live-stack --json

MCS follows a standards-oriented IPv6 HLC path in the implementation. Use the command output to confirm whether the installed release exposes an executable listener, test package or evidence-only surface before wiring a bench.

NACS / SAE J3400


& $CL protocol nacs-j3400-live-stack --json

The stack shares relevant HLC concepts with ISO 15118. Do not assume connector geometry alone determines the selected protocol; select the package profile and transport explicitly.

ChaoJi / GB/T


& $CL protocol chaoji-gbt-live-stack --json
& $CL dc-can catalog --json

ChaoJi/GB/T operation may require a CAN adapter and package-specific profile. Follow the same staged process as CHAdeMO: catalog, virtual execution, adapter loop, signal validation, then controlled power-stage testing.

What “live-stack” output means

The command reports the implementation and activation boundary present in the installed build. Read the returned JSON fields before proceeding. A command that reports a planned, preview, evidence-only or blocked state is not a live interoperability claim.

HomeTop