Charge point emulator
Test your own OCPP backend without a charger: the emulator connects to it as one and plays a scenario, checking and timing every answer.
Test a backend in three steps
- Open Test backend in the top bar of the analyzer (hosted edition, Pro or Team plan, email confirmed). The Guided view opens first; All settings beside it has the full form described below.
- Connect: enter the address, the charge point identity and the password if your backend asks for one, then Test connection. The emulator opens a WebSocket offering OCPP 2.1, 2.0.1 and 1.6, notes the version the backend picks, and closes it without sending an OCPP message. A refused password (HTTP 401 or 403), an unknown identity (404), a server that answers no WebSocket and one that agrees on no OCPP version are each named. Backends you used are remembered in this browser, without the password, for the next test.
- Choose a goal: a Quick check (boot, heartbeat and status, in seconds), a Full run (every scenario that needs nothing from you: boot, a charging session, a reconnect, an unknown card and charging offline; tick the box when someone operates the backend during the run to add the remote start and the charging profile), or Robustness (a message that breaks the schema, a slow link, a dropped connection and charging offline). Each run of a goal counts against the runs of the day.
- Results: the scorecard shows each run passed or failed, the step that failed and why, the steps of each run and its OCPP log. When the first run cannot reach the backend, the others are not started. Download the report saves it as a web page to keep or send to the maker of the backend: the backend, the goal, each run, what failed and why, and the answer times.
- Run every day: save the goal with an hour (UTC). The password, if any, is stored sealed and used only for these runs. The account gets an email when a daily run stops passing, when it passes again, and when it could not run (for example after the plan ended). Pro keeps 3 daily runs, Team 20; pause, run or delete them under Daily runs.
Run a scenario
- Under All settings, pick one scenario and its faults yourself.
- Enter the address of your backend as the charger would use it, without the identity (wss://csms.example.com/ocpp), the charge point identity, and the password if your backend asks for basic authentication. The emulator connects to the address followed by / and the identity.
- Pick OCPP 1.6, 2.0.1 or 2.1 and a scenario: Boot and heartbeat; A charging session (a card, a transaction with three meter readings and the stop); Disconnect and reconnect; An unknown card (the backend has to refuse it); A remote start (the emulator waits up to two minutes for your backend to start a transaction, then charges with the card it named); Smart charging (a session that waits for a SetChargingProfile from your backend); or Offline while charging (the connection drops during a transaction and the readings taken offline follow once it is back, marked offline in 2.0.1 and 2.1).
- A scenario that needs your backend to act says what under the form, before the run.
- Each step shows what the emulator sent, whether the answer holds to the schema, whether it says what the scenario expects (Accepted for the boot and the card), and how long it took. A step that must succeed for the rest to make sense stops the run when it fails.
- The emulator acts on what your backend sends it, as a charger would: it charges within a SetChargingProfile (the energy of each reading falls in proportion, and the limit is reported as Current.Offered or Power.Offered), lifts it on ClearChargingProfile, answers GetCompositeSchedule with the limit in force, accepts a remote start or stop of its transaction, reads and changes its configuration (GetConfiguration and ChangeConfiguration, or GetVariables and SetVariables), accepts a Reset without restarting, and sends a Heartbeat or StatusNotification the backend asks for with TriggerMessage. Anything else gets the first reply the schema allows. Every call is listed with the run.
- Download log saves the run in the form the analyzer reads, for the OCPP checks, or to hold beside a capture.
Load test (Team)
- On the Team plan the Emulator page has a load test: it opens many emulated chargers at once against your own backend, to see how it holds up under many connections at the same time. It is for a backend you run.
- First prove you control the backend. Verify I control this backend shows a token and two ways to place it: a DNS TXT record at _v2g-emulator.<host>, or an HTTPS file at https://<host>/.well-known/v2g-emulator-verification. Place either and verify again. The token is tied to your account and that host, so it works for no one else and no other host.
- Once verified, choose how many chargers (up to your plan) and run it. Each charger boots and then sends heartbeats for a while; the report shows how many connected, how many heartbeats were answered, and the spread of answer times (median, p95, highest). A load run keeps only these figures, not every frame.
- A load test counts against your runs a day and the two-at-a-time limit. An administrator can block a host or an account; the proof is checked again at the start, so a record that is no longer in place does not let a run through.
Faults
- Under Faults (optional) the emulator plays faults on purpose, to see how your backend copes: an extra delay before each of its messages (up to 5 s), a delay before it answers a call of your backend (up to 60 s, so you see whether the backend waits or times out cleanly), and after the boot one StatusNotification that breaks the schema, which the backend should answer with a CALLERROR naming a format error.
- Answers the emulator holds back are still sent before the run closes the connection.
Limits and your data
- Run the emulator only against a backend you are allowed to test. The connection comes from our server, and every run is logged with its target.
- Only wss:// addresses are allowed; plain ws:// only when you tick Allow ws:// without TLS. Private, internal, loopback and cloud metadata addresses are refused, in every notation and after every DNS lookup, and redirects are not followed.
- A server that does not agree on the OCPP version as a WebSocket subprotocol is not treated as a backend: the run ends there.
- Pro has 50 runs a day and Team 200, at most 2 at a time; a run lasts at most 5 minutes, sends one message at a time with a pause, and stops if the backend sends more than 500 messages.
- The emulator sends only the messages of the scenario, the answers to your backend, the messages your backend asks for with TriggerMessage, and the broken message when you ask for it; nothing you type is sent as a message. The test card is at most 20 letters and digits.
- Runs are kept for 7 days with card ids masked. The password is used for the connection only and never stored or logged.
- To report a run against a server that is yours and that you did not start, use the contact page; an administrator can block a target or an account.