Skip to content
Start testing
Sample report

Sample protocol test report

A sample run across OCPP 1.6, OCPP 2.0.1, and OCPI 2.2.1: run header, findings per area, and one session's frame log.

This is a representative report layout, not a customer export: run scope, concrete findings, and the message-level evidence behind each one.

Checks shown
Connectivity, transactions, smart charging, roaming, CDR integrity

Sample findings

Pass, Review or Fail per area, with what the team sees.

  • OCPP 1.6 transaction flow

    Status
    Status: Pass
    What the team sees
    BootNotification, Authorize, StartTransaction, MeterValues, and StopTransaction completed within expected timing windows.

  • OCPP 2.0.1 smart charging

    Status
    Status: Review
    What the team sees
    Charging profile accepted, but one EVSE returned a delayed acknowledgement during a reconnect sequence.

  • OCPI 2.2.1 CDR export

    Status
    Status: Pass
    What the team sees
    Session closure and tariff calculation fields matched the expected reference payload for the sample roaming run.

  • Hub-oriented onboarding path

    Status
    Status: Review
    What the team sees
    Credentials exchange succeeded, but partner metadata handling needs a follow-up before certification rehearsal.

Sample protocol trace

One OCPP 2.0.1 session from the run, every frame valid against the OCA 2.0.1 JSON schemas.

  1. CP → CSMS
    Connect
  2. 08:00:00
    CP → CSMS
    BootNotificationAccepted
  3. 08:01:10
    CP → CSMS
    TransactionEventAccepted

    CALL tx-014

    {
  "eventType": "Started",
  "timestamp": "2026-04-01T08:01:10Z",
  "triggerReason": "Authorized",
  "seqNo": 0,
  "transactionInfo": {
    "transactionId": "tx-014",
    "chargingState": "Charging"
  },
  "idToken": {
    "idToken": "046ABC123XY",
    "type": "ISO14443"
  },
  "evse": {
    "id": 1,
    "connectorId": 1
  }
}

    CALLRESULT tx-014

    {
  "idTokenInfo": {
    "status": "Accepted"
  }
}
  4. 08:16:10
    CP → CSMS
    TransactionEventCALLRESULT