TestPilot · Get started

Test your charger's OCPP in about 15 minutes

TestPilot acts as the charging network (CSMS) your charger connects to. You point the charger at it once, press Run, and TestPilot drives a full charging session by itself and grades every message the charger sends. No software to install.

What you need

  • A charger that speaks OCPP 1.6J, 2.0.1 or 2.1 over WebSocket, with access to its OCPP settings (web page, app or configuration tool).
  • Internet access from the charger to ocpp.testpilot.infinite-service.com on port 80 (ws://) or 443 (wss://).
  • A vehicle or an EV simulator (test load) you can plug into connector 1. The test starts a real charging session, and most chargers only start one when something is plugged in.
  • About 15 minutes.

Step by step

  1. Create your free account

    Open web.testpilot.infinite-service.com and choose Create account. Enter your email, a password and your company name.

  2. Add your charger

    Go to Stations and create a station, for example “Lab A”. In that station, choose Add charger and fill in:

    Charger ID: the OCPP identity the charger will use (its “charge point ID” or “charge box ID”), for example ACME-AC22-0001. Letters, digits, “_”, “.” and “-”; it must match the charger exactly, including upper and lower case.

    OCPP version: the version the charger is set to use.

    Connection: “wss — password” if the charger supports TLS (recommended), otherwise “ws — password”. Use “ws — no password” only if the charger cannot send a password.

    TestPilot then shows the connection URL, the username and the password. Copy them now: the password is shown only once. (If you lose it, use Rotate password to get a new one.)

  3. Enter the settings on the charger

    In the charger's OCPP settings, enter the values from the table below, then save and restart the charger if it asks you to.

    Within a few seconds the charger should show as Connected on the Stations page. If it does not, open the charger's Connection log there: it says why TestPilot refused it (for example “Wrong password” or “Version mismatch”). See Troubleshooting below.

  4. Run the test

    Plug the vehicle or EV simulator into connector 1. Open Console, choose your charger and press Run Core test.

    TestPilot now does everything itself: it asks the charger for its boot and status messages, starts a charging session remotely, reads the meter values, then stops the session. Nobody needs to tap a card or press a button on the charger. It takes 1 to 3 minutes, depending on how often the charger sends meter values.

  5. Read and download the report

    Each check shows Pass or Fail, what OCPP expects, and what your charger actually sent. Open Reports to download the report as an HTML file to share with your team or customer, or to print as PDF.

    Fixed something? Run the test again. Every run gets its own report, so you can show before and after.

Charger settings

The names differ between manufacturers. These are the usual ones.

Central System URL / CSMS URL / backend URL
wss://ocpp.testpilot.infinite-service.com/testpilot/

For “ws” connections the URL starts with ws:// instead. Copy the exact URL TestPilot shows for your charger.

Charge point ID / charge box ID / identity
Your charger ID, e.g. ACME-AC22-0001

Exactly as you entered it in TestPilot.

Username (HTTP Basic authentication)
Your charger ID

Some chargers do not ask for it and send the ID automatically.

Password / authorization key / AuthorizationKey
The password TestPilot showed once

Not needed for “ws — no password”.

OCPP version / protocol
1.6J, 2.0.1 or 2.1

Must match the version you chose in TestPilot.

If the charger asks for one full URL, use the URL TestPilot shows, which ends with your charger ID. If it asks for the server URL and the charger ID in separate fields, enter the URL without the ID at the end.

What the test checks

The Core test (OCPP 1.6) checks one complete charging session, in order:

  1. 1. BootNotification — The charger announces itself with its vendor and model.
  2. 2. StatusNotification — It reports a valid connector status.
  3. 3. Authorize — It asks to authorize the card TestPilot starts the session with.
  4. 4. StartTransaction — It starts the transaction on a real connector (not connector 0).
  5. 5. MeterValues — It sends at least two meter readings during charging, no further apart than its own sample interval.
  6. 6. StopTransaction — It stops with the same transaction ID TestPilot issued.

For OCPP 2.0.1 and 2.1 the Core test checks the same session with TransactionEvent (Started, Updated, Ended). Paid plans add more tests: boot reasons, the device model report, and the OCPP 2.1 tariff, DER and event-stream messages.

Troubleshooting

The charger stays Offline

Check that the charger has internet access and can reach ocpp.testpilot.infinite-service.com on port 443 (wss) or 80 (ws), and that the URL is typed exactly. Then look at the charger's Connection log on the Stations page: if it is empty, the charger never reached TestPilot.

Connection log says “Wrong password” or “Missing credentials”

Re-enter the password, and check that the username is the charger ID. If you no longer have the password, choose Rotate password and enter the new one on the charger.

Connection log says “Username does not match identity”

The username must be exactly the charger ID, with the same upper and lower case.

Connection log says “Version mismatch”

The charger offered a different OCPP version from the one you chose in TestPilot. Change one of them so they match (Change version or connection, on the charger's card).

StartTransaction or TransactionEvent fails with “no … from the charger”

The charger accepted the remote start but did not begin charging. Usually nothing was plugged into connector 1, or the charger needs a local card or button before it charges. Plug in, then run again.

MeterValues fails

The charger sent fewer than two meter readings, or sent them further apart than its own MeterValueSampleInterval (2.0.1: SampledDataCtrlr.TxUpdatedInterval). The report shows the gap it measured.

A step waits and then fails, but the charger did send it later

Each step waits 15 seconds by default. On the Scenarios page you can raise the step timeout (up to 120 seconds) for slow chargers.

What the free plan includes

One station with one charger, on any OCPP version, connections without TLS client certificates (profiles 0 to 2), and the Core test. Reports carry a “Free plan” watermark.

To test more chargers, the other tests, client-certificate (profile 3) connections, or to get reports without a watermark, see the plans on the pricing page.

See plans and prices

Stuck? We will look at it with you

Email us your charger ID and what you see. We can read its connection log and messages and tell you what to change.

Email support