EVSE simulator
An EVSE simulator is software that behaves like Electric Vehicle Supply Equipment toward a CSMS: it opens a WebSocket, sends BootNotification and session messages, and accepts remote commands — without a physical connector or power stage. The same idea is an OCPP charge point simulator, a virtual charge point (VCP), or an EV charger simulator. The names track different diagrams; the test job is identical.
The job is the same: let CSMS / CPMS software teams test the backend early, share reproducible session evidence, and catch payload or session bugs before a hardware bench is free.
Launch the EVSE simulator · Getting started · EV charger testing · Test CSMS without hardware
What an EVSE simulator is (and is not)
A good EVSE simulator speaks real framed OCPP over WebSocket so your CSMS sees production-shaped traffic. Chargeflux hosts that runtime in the cloud and gives you a browser UI plus message console — useful when CPO partners or remote QA need a shared environment.
- Not a replacement for electrical commissioning of real EVSE
- Not an official OCPP certification lab by itself
- Not a public driver-facing charger network
EVSE simulator vs charge point vs VCP
Search and RFCs mix these labels. Use this scoreboard when you are picking a tool or writing a test plan:
| Name you hear | What people usually mean | Chargeflux role |
|---|---|---|
| EVSE simulator | Pretend the wallbox / dispenser exists so the backend can talk to it | Yes — station side |
| OCPP charge point simulator / VCP | Pretend the OCPP client exists; same WebSocket, framed CALL/CALLRESULT | Yes — same runtime |
| CSMS simulator | Pretend the central system exists so you can test a real charger | No — we connect to your CSMS |
Core capabilities teams expect
- Configurable station identity and CSMS endpoint
- OCPP 1.6J and/or 2.0.1 message flows — see the OCPP 1.6 simulator and OCPP 2.0.1 simulator
- Connector states that match real session lifecycles
- Visibility into raw OCPP JSON for debugging
- Optional API control for automation (see API)
Hardware lab vs EVSE simulator
Use both. They answer different questions:
| Approach | Best for | Weak at |
|---|---|---|
| EVSE simulator / VCP | Protocol correctness, CSMS business logic, multi-station scenarios, fast software feedback | Metering accuracy, plug/cable physics, vendor power-stage quirks |
| Physical EVSE lab | Electrical commissioning, firmware edge cases, field RF/network behaviour | Parallel QA seats, CI regression, booking latency for every backend change |
| Open-source / CLI only | Air-gapped labs, custom scripts, full control inside your VPC | Shared UI for product/QA, zero-install demos with partners |
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.
Hosted vs open-source EVSE simulators
- Hosted (Chargeflux) — fast setup for demos, partner integration, and teams that want a UI and shared cloud runtime. The OCPP WebSocket to your CSMS opens from the hosted backend, not the browser tab.
- Open-source / CLI — full control inside your VPC, custom scripts, air-gapped labs. More ops ownership.
Many teams use both: CLI in CI, hosted UI for human debugging and customer demos. Start with connect your CSMS when you have a public wss:// endpoint.
Chargeflux as a hosted EVSE simulator
Chargeflux runs the station on cloud infrastructure and gives you a browser UI plus message console. You sign in, create a station, connect to your CSMS, and drive sessions without installing a local stack. For fleets still on 1.6J, the OCPP 1.6 simulator guide covers BootNotification, remote start/stop, MeterValues, and the console. For dual-stack backends, pair it with the OCPP 2.0.1 simulator. Protocol primer: what is OCPP.
Typical first path (about 30 minutes)
- Open getting started and create a virtual station.
- Point it at a non-production CSMS URL (connect your CSMS).
- Confirm BootNotification is accepted and Heartbeat continues.
- Run one local start and one remote start; watch MeterValues land (charging session messages).
- Force a disconnect and confirm recovery — see WebSocket troubleshooting if connect fails.
FAQ
What is an EVSE simulator?
Software that pretends to be an Electric Vehicle Supply Equipment (EVSE) station toward a CSMS: it opens a WebSocket, exchanges framed OCPP messages (BootNotification, sessions, status), and accepts remote commands — without a physical connector or power stage. Teams also call it an OCPP charge point simulator, virtual charge point (VCP), or EV charger simulator.
Is an EVSE simulator the same as a virtual charge point?
For CSMS testing, yes — same job. EVSE simulator is the hardware-role name (the box on the wall). Virtual charge point / OCPP charge point simulator is the protocol-role name (the OCPP client). Chargeflux is the station side so you can test your real CSMS over WebSocket.
Is a virtual charge point the same as a CSMS simulator?
No. An EVSE simulator / virtual charge point pretends to be the station. A CSMS simulator pretends to be the backend. Chargeflux is the station side so you can test your real CSMS over WebSocket.
When should I use an EVSE simulator instead of hardware?
Use a simulator when you need fast feedback on protocol correctness, CSMS business logic, multi-station scenarios, or CI-friendly regression before a lab EVSE is free. Keep physical EVSE for metering accuracy, plug behaviour, vendor firmware quirks, and field network issues.
Is Chargeflux a free EVSE simulator?
Demo Mode works without an account. Connecting a virtual station to your CSMS uses free magic-link sign-in with up to two concurrent hosted stations. It is a development and integration OCPP test tool, not an OCA certification lab.
Which OCPP versions does the EVSE simulator support?
OCPP 1.6J and 2.0.1 today. Use the matching version guides so dual-stack CSMS code gets real coverage. OCPP 2.1 is on the public roadmap without a promised date.
How is a hosted EVSE simulator different from open-source CLI tools?
CLI and open-source simulators give full control inside your VPC and custom scripts. A hosted EVSE simulator adds a shared browser UI, cloud runtime that can reach public CSMS endpoints, charger presets, and a message console product and QA can share. Many teams use both: CLI in CI, hosted UI for demos and human debugging.
Next step: run the EVSE simulator, follow getting started, or check pricing.
Last reviewed September 2026 · Chargeflux.io