Chargeflux.io

Getting started

This guide walks through your first connection: from opening the simulator to seeing an accepted BootNotification in the message console. You need a compatible public wss:// CSMS endpoint. If you don’t have one yet, open demo mode to explore a sample session first.

1. Open the simulator

From the landing page, select Launch Simulator. Demo Mode works without an account. Connecting to a real CSMS requires free magic-link sign-in. A default charger is already configured: a single AC Type 2 connector rated at 7.4 kW. The default protocol is OCPP 1.6J (ocpp1.6 subprotocol); switch to OCPP 2.0.1 in the UI when you need that path. Background on what you are launching: EVSE simulator (OCPP charge point simulator / virtual charge point). How this fits a full EV charger testing plan: software first, lab EVSE before go-live.

2. Enter your CSMS endpoint

Paste your CSMS WebSocket URL. You can paste either a full URL that already includes the station identity, or a base URL that Chargeflux.io appends the station identity to. The simulator always shows you the final WebSocket URL before the hosted runtime connects, and never silently rewrites it.

Full URL:  wss://csms.example.com/ocpp/CF-DEMO-A7K2
Base URL:  wss://csms.example.com/ocpp   -> appends CF-DEMO-A7K2

3. Confirm the station identity, protocol, and preset

The station identity is the virtual Charge Point identity used in the connection convention, for example CF-DEMO-A7K2. A short random suffix is generated by default; edit it to match a station you have registered in your CSMS. Set the protocol to match what your CSMS expects (1.6J or 2.0.1), then choose an AC or DC preset. Version-specific guides: OCPP 1.6 simulator · OCPP 2.0.1 simulator.

4. Connect

Select Connect. Chargeflux's cloud runtime opens a WebSocket using the subprotocol for the version you selected (ocpp1.6 or the 2.0.1 subprotocol) and immediately sends a BootNotification. On 1.6J see BootNotification; on 2.0.1 see 2.0.1 BootNotification. The simulator UI correlates the response by its unique message ID and shows the registration status:

  • Accepted — the station may operate; the heartbeat interval from the response is applied.
  • Pending — the CSMS is not ready to accept the station yet.
  • Rejected — the CSMS will not register the station.

If the connection fails before boot, see troubleshooting WebSocket connections.

5. Start charging

Once the station is accepted and a connector is Available, select Start Charging. What the station emits depends on protocol:

Select Stop Charging when you want a clean end-of-session frame on either version.

Last reviewed August 2026 · Chargeflux.io