Chargeflux.io

Test CSMS without hardware

If you build or integrate a CSMS / CPMS, waiting on a physical charge point slows every release. An OCPP charge point simulator (virtual charge point) that speaks real OCPP over WebSocket lets you exercise onboarding, transactions, and failure paths before a single EVSE ships to the lab. Broader framing: EV charger testing (protocol vs lab vs certification).

Chargeflux is a browser-hosted OCPP 1.6 simulator (1.6J) and OCPP 2.0.1 simulator aimed at software teams — not a certification harness.

Who this workflow is for

  • CPO engineering teams building or customising a CSMS
  • Integrators connecting a third-party CPMS to new station firmware
  • QA engineers who need repeatable Boot → transaction → MeterValues paths
  • Backend developers who cannot monopolise a shared hardware bench

What you can validate without an EVSE

  1. Connection and identity — WebSocket URL, station identity, subprotocol (ocpp1.6 / OCPP 2.0.1), TLS expectations.
  2. BootNotification acceptance — registration status, interval configuration, and how your CSMS labels unknown vs accepted stations. Sample frames: OCPP 1.6J sample messages.
  3. Session lifecycle — Authorize, StartTransaction / transactionEvent, MeterValues, StopTransaction with realistic connector states.
  4. CSMS → station commands — RemoteStart/Stop, Reset, ChangeAvailability, TriggerMessage, configuration reads/writes where supported.
  5. Operator debugging — message console with correlated request/response pairs you can export for tickets and regression notes.

Recommended first test path (30 minutes)

  1. Open the getting started flow and create a virtual station.
  2. Point the station at a non-production CSMS URL using connect your CSMS.
  3. Confirm BootNotification is accepted and Heartbeat continues on the interval your backend set.
  4. Run one local start and one remote start; watch MeterValues land on the backend.
  5. Force a disconnect / reconnect and confirm your CSMS recovers station state cleanly.

Hardware lab vs OCPP charge point simulator

Use both. They answer different questions (deeper comparison: OCPP charge point simulator):

  • Virtual charge point / OCPP charge point simulator — protocol correctness, CSMS business logic, multi-station scenarios, CI-friendly regression, faster feedback for software-only changes.
  • Physical EVSE — cable/plug behaviour, metering accuracy, power electronics, vendor firmware quirks, field RF/network issues.

Teams that only test on hardware usually ship CSMS bugs late. Teams that only test virtually still need a pilot station before production go-live.

FAQ

Can I test CSMS without any charge point hardware?

Yes for software integration and protocol paths. An OCPP simulator acts as a virtual charge point over WebSocket so your CSMS sees real message shapes.

Is an OCPP simulator the same as OCA certification?

No. Chargeflux validates supported envelopes and payloads for development and QA. Official OCPP certification uses OCA processes and dedicated tools.

Do CPOs and CPMS vendors use the same approach?

Usually yes. Anyone who owns the CSMS side of OCPP benefits from a virtual charge point during build, UAT, and regression — regardless of whether they manufacture hardware.

Ready to try it? Start a virtual station or open the simulator after sign-in.

Last reviewed July 2026 · Chargeflux.io