Home
OCPP 1.6 Simulator

OCPP 1.6 online charge point simulator

Open HTTP version for ws:// test endpoints

Test your OCPP 1.6J server in a browser without a physical charger. Connect, register, authorize a test tag and run a transaction.

Run your first test

Load the example, then open Connection settings. Replace the local endpoint with your own server address and register CP001 and the DEADBEEF test tag on that server.
Save settings, then click Connect. BootNotification is sent automatically. Wait for an Accepted response and the Connected status.
Click Heartbeat to check the response. Click Authorize and verify idTagInfo.status is Accepted before Start Transaction. Finish with Stop Transaction and check the server log.

Enter the base WebSocket endpoint without the charge point ID. The tool appends /CP001. localhost refers to the computer running this browser. This version uses HTTP for compatibility with ws:// test servers; it does not support custom authorization headers or client certificates.

Use a test environment and synthetic data. Loading an example only fills the form; it does not save settings, connect or send messages.

Watch video tutorial (Chinese) Read the guides

Server Status: Authorized Connected Connecting Disconnected Error In Transaction

Charge Point Availability:

Charge Point Status:

Meter value -> SampledValue:

SampledValue -> Context:

SampledValue -> Measurand:

Message log
Clear log

OCPP testing guides

Connect to your own test server using the base endpoint, for example ws://localhost:8080/steve/websocket/CentralSystemService. Set ChargePoint ID to CP001; do not append it twice. The server must accept the ocpp1.6 WebSocket subprotocol.

After an Accepted BootNotification response, test Heartbeat (empty request payload, server returns currentTime), then Authorize and Start Transaction. StartTransaction includes connectorId, idTag, meterStart and a UTC timestamp; the response supplies transactionId and idTagInfo. Verify the response payloads in both logs before continuing. Click Stop Transaction to finish.

If connection fails, check the browser Network → WS handshake and server log: 404 suggests an endpoint mismatch; 401/403 may indicate authentication or access policy; a 101 upgrade only confirms the WebSocket transport. Check the charge point registration, subprotocol and BootNotification response separately. Browser failures can also result from TLS, Origin restrictions or local-network permissions.

This browser tool is for manual debugging, not protocol certification. A connection or transaction badge alone does not establish full OCPP compliance.

Detailed walkthroughs below are in Chinese; your browser may offer translation.

OCPP 1.6 specification

Video tutorial (Chinese)

Steve OCPP Server