Sock8
See what the charger actually sends

OCPP testing tool for charger integration and debugging

The Sock8 OCPP testing tool gives charger developers, QA teams, and support engineers a cloud endpoint for connecting test units and inspecting message traffic without first configuring a production CSMS.

Use the terminal to follow boot, status, authorization, transaction, metering, heartbeat, and remote-command exchanges. Saved test history helps teams compare firmware behaviour and share reproducible evidence when a flow fails.

Who it is for

Built for teams accountable for live charging.

  • EV charger OEM engineering teams
  • Firmware QA and certification teams
  • CPO charger-onboarding teams
  • Field support and integration engineers
Problems it solves

Replace operational blind spots with one system.

  • No accessible CSMS during bench testing
  • Protocol failures hidden in application logs
  • Difficult handoff between QA and backend teams
  • Inconsistent evidence across firmware releases
How it works

A clear path from connection to daily operation.

01

Create a test charge point

Generate the assigned connection details and configure them on the test unit.

02

Connect

Confirm the WebSocket connection and inspect the initial boot and status messages.

03

Exercise flows

Run authorization, transaction, meter, remote command, reset, and error scenarios.

04

Review evidence

Filter and export the relevant message sequence for debugging or release approval.

Product view

See the operating detail behind the promise.

The testing terminal shows each OCPP action beside its timestamp and message payload for a selected charge point.

Representative Sock8 product interface

Features

Capabilities included in the product scope.

  • Cloud-hosted OCPP endpoint
  • Raw request and response terminal
  • Action and date filters
  • Remote command testing
  • Transaction-flow history
  • Exportable test evidence
Protocols and interfaces

Designed to connect the charging stack.

OCPP 1.6JOCPP 2.0.1WebSocketJSONTLS
Implementation or migration

Move from technical discovery to a controlled launch.

  1. 1

    Account setup

    Create the team and the test charge-point identities required for the evaluation.

  2. 2

    Network configuration

    Allow the required outbound connection and apply the endpoint and security settings to the charger.

  3. 3

    Test plan

    List required message sequences, remote operations, negative cases, and firmware variants.

  4. 4

    Acceptance record

    Save the tested version, results, unresolved deviations, and exported message evidence.

Customer evidence
OCPP 1.6J and 2.0.1 test coverage
Sock8 compatibility programme · Multi-market
The same protocol-level inspection workflow is used to validate charger behaviour before models are approved for production onboarding.

Evidence shown is limited to the named deployment facts currently approved for this site.

Deployment

Choose the operating boundary.

The standalone testing tool is cloud-hosted and intended for non-production charger development and validation.

Pricing information

Scope the commercial model.

Lifetime access is listed at $199 for up to five users, with the current purchase and refund terms confirmed before checkout.

View platform pricing
Buyer FAQs

Questions technical and commercial teams ask.

Do I need a production CSMS account?+

No. The tool is a standalone environment for connecting and inspecting test chargers.

Which OCPP versions can I test?+

The listed testing scope includes OCPP 1.6J and OCPP 2.0.1.

Can the tool send remote commands?+

Yes, supported commands can be triggered to inspect the charger response and resulting message sequence.

Can I export logs?+

The product structure includes exportable test history so evidence can be shared with firmware, backend, and support teams.

Is the tool intended for live networks?+

No. It is intended for development, bench testing, onboarding, and diagnostic workflows rather than production network operations.