Create a test charge point
Generate the assigned connection details and configure them on the test unit.
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.
Generate the assigned connection details and configure them on the test unit.
Confirm the WebSocket connection and inspect the initial boot and status messages.
Run authorization, transaction, meter, remote command, reset, and error scenarios.
Filter and export the relevant message sequence for debugging or release approval.
The testing terminal shows each OCPP action beside its timestamp and message payload for a selected charge point.
Representative Sock8 product interface
Create the team and the test charge-point identities required for the evaluation.
Allow the required outbound connection and apply the endpoint and security settings to the charger.
List required message sequences, remote operations, negative cases, and firmware variants.
Save the tested version, results, unresolved deviations, and exported message evidence.
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.
The standalone testing tool is cloud-hosted and intended for non-production charger development and validation.
Lifetime access is listed at $199 for up to five users, with the current purchase and refund terms confirmed before checkout.
View platform pricingNo. The tool is a standalone environment for connecting and inspecting test chargers.
The listed testing scope includes OCPP 1.6J and OCPP 2.0.1.
Yes, supported commands can be triggered to inspect the charger response and resulting message sequence.
The product structure includes exportable test history so evidence can be shared with firmware, backend, and support teams.
No. It is intended for development, bench testing, onboarding, and diagnostic workflows rather than production network operations.