Skip to main content

Charger testing process

How the test is conducted​

This instruction is intended for remotely performing a compatibility test with the eMabler backend. In the test, an engineer from the organization which controls the charger and an engineer from eMabler will work together to conduct the test remotely.

Testing will take approximately one hour. Usually one round of testing will be enough, but it is also possible that more than one session is needed. If the charger is found to have implemented OCPP in an unusual way, eMabler will adjust their communication to compensate and a new test will be scheduled.

What is needed for the test​

  • A charger to be tested, with a firmware version consistent with production units

  • A network connection for the charger, capable of outbound connections

  • Access to the charger’s configuration (access type will depend on charger)

  • An engineer at the charger to perform parts of the test

  • A laptop or phone to change parameters at the charger (depending on type of charger)

  • An NFC tag which is readable by the charger, with a known ID

  • Either a

    • Type2 EV Simulator and a load or
    • An electric vehicle with a non-full battery

  • About 1 hour of time

Key Information​

A telco connection to eMabler for communicationBasic testing is following either OCPP 1.6 or 2.0.1 JSON standard with Websocket connection. Our testing endpoint is listening in url: wss://ocpp.emabler.net/ocpp/ for OCPP 1.6 and wss://ocpp201.emabler.net/ocpp/ for OCPP 2.0.1 There is no additional password required on this endpoint but the charger need to be created by eMabler before connection is allowed. We only support secure websocket (WSS) connections and also send or support websocket messaging to keep to connection alive. On test scenarios our heart beat interval is 200 seconds.

Basic test case​

Basic connectivity​

  • Connect the charger to eMabler backend by specifying the ChargerID (agreed with eMabler) and configuring the OCPP JSON endpoint on the charger to point to: wss://ocpp.emabler.net/ocpp/ (OCPP 1.6) or wss://ocpp201.emabler.net/ocpp/ (OCPP 2.0.1)

  • eMabler will check that the connection has established correctly. In this section following things are checked from eMabler side:

    • BootNotification comes in and can be handled ok

    • Charger sends StatusNotifications for all its sockets

      • Also StatusNotification is send for socketId 0 (full charger), not mandatory from eMabler perspective

    • eMabler will ask for GetConfiguration when it receives a BootNotification, eMabler will check that it gets configurations back and can interpret them

    • HeartBeat is send on the interval specified on the BootNotification

Basic charging events​

  • Authorization message is send from charger and interpreted correctly by eMabler
  • StartTransaction message is send from charger and interpreted correctly by eMabler
  • StopTransaction message is send from charger and interpreted correctly by eMabler
  • eMabler can calculate correct consumption and time report from the charging transaction messages

Basic CPMS commands​

  • Charger reacts correctly on eMabler Reboot command
  • Charger reacts correctly on ChangeConfiguration command
  • Charger reacts correctly on RemoteStartTransaction command (if charger is configured to do authorization after RemoteStart check that it also works)
  • Charger reacts correctly on RemoteStopTransaction command
  • Charger reacts correctly on UnlockCable command
  • Charger reacts correctly on SetActive and SetInactive commands
  • ClearCache command works
  • SendLocalList command works
  • Charger sends meterValues during transaction

Firmware, diagnostics​

  • Charger sends diagnostics file when send GetDiagnostics command with url (this part varies from manufacturer, ok result is to go thru the manufacturer solution to get diagnostics logs if not directly as in OCPP)

    • Diagnostics status notifications work (not mandatory)

  • Charger can be remotely updated either by UpdateFW command or manufacturer own process.

    • FW Update status notifications work (not mandatory)

Advanced test cases​

These are usually tested by eMabler with chargers on our premises, but can be tested out also together with the Manufacturer remotely. And only tested if charger supports these feature.

Smart Charging​

  • SetChargingProfile message works
  • GetChargingProfile message works
  • GetCompositeSchedule message works

Reservation​

  • Charger reacts correctly on ReserveNow message
  • Charger reacts correctly on CancelReservation message