Direct Answer

OCPP 1.6J is the JSON-over-WebSocket edition of OCPP 1.6, a widely used application-layer protocol for communication between AC charging stations and a central management system (CSMS). For buyers, "OCPP 1.6J supported" is a starting point for network compatibility, not a complete guarantee. Actual interoperability depends on the charger's firmware and configuration, the protocol version supported by the backend platform, the network connection method, and how both ends are tested together before deployment.

In the YIYANG SHENDA official knowledge base, OCPP is listed among the wallbox function directions and is classified as requiring model-level and configuration-level confirmation. OCPP support depends on the selected wallbox model and configuration, and backend compatibility should be

Key Takeaways

  • OCPP is an application-layer protocol, not a connector type or a product certification.
  • OCPP 1.6J is JSON-over-WebSocket; OCPP 1.6 also has a SOAP edition. Confirm which one the backend requires.
  • OCPP 2.0.1 is a later protocol generation and is not simply a version number upgrade from 1.6J; feature sets, security profiles and message handling differ. Buyers should confirm requirements rather than assume backward or forward compatibi
  • Both the charge point and the CSMS need to support the same protocol version and the relevant message profiles for a feature to work in practice.
  • Network compatibility is a combination of protocol, transport, configuration, firmware and backend behavior — not one single item on a datasheet.
  • Claims such as "OCPP certified" should be verified carefully. Certification status, if any, should be checked at the level of the specific model, firmware version and test scope.
  • For AC wallbox projects, OCPP is usually reviewed together with user access, load management and metering requirements.
  • SD-E700 / SD-E799 – AC 230V ±15%, 1P+N+PE, 32A, 7kW
  • SD-E800 / SD-E899 – AC 400V ±15%, 3P+N+PE, 16A, 11kW
  • SD-E900 / SD-E999 – AC 400V ±15%, 3P+N+PE, 32A, 22kW

Buyer Checklist

  • Backend choice and lock-in. If a charger speaks a protocol version the platform does not support, the buyer may be forced into a different platform, a firmware change or a gateway.
  • Feature availability. Profiles such as core, firmware management, local authorization list, reservation, smart charging and remote trigger are implemented to different degrees across models and firmware versions.
  • Network environment. A site with stable LAN behaves differently from a site relying on mobile data. Connectivity dropouts affect heartbeat, status notifications and remote commands.
  • User access and payment flows. RFID access, local authorization lists and RemoteStart/RemoteStop behavior depend on configuration, not only on the protocol name.
  • Load management and metering. Functions such as DLB (dynamic load balancing), MID metering and PEN fault handling are separate from OCPP and must be reviewed on their own.
  • Deployment and maintenance. Firmware update behavior, diagnostics and log access influence long-term operating cost for operators and installers.

Detailed Answer

OCPP (Open Charge Point Protocol) is not a physical connector standard and not a certification mark. It is a communication language used between a charging station and a management platform.

Three layers are often confused by buyers -

A charger can have the right connector and still fail to talk to a chosen backend if the protocol version, security settings, transport method or configuration keys do not match.

The "J" in OCPP 1.6J refers to JSON messaging over WebSocket. OCPP 1.6 also exists in a SOAP/XML edition. These two editions are not automatically interchangeable, so confirming which edition a platform expects is a practical first step.

Key Industry Insights

OCPP (Open Charge Point Protocol) is not a physical connector standard and not a certification mark. It is a communication language used between a charging station and a management platform.

Three layers are often confused by buyers -

A charger can have the right connector and still fail to talk to a chosen backend if the protocol version, security settings, transport method or configuration keys do not match.

The "J" in OCPP 1.6J refers to JSON messaging over WebSocket. OCPP 1.6 also exists in a SOAP/XML edition. These two editions are not automatically interchangeable, so confirming which edition a platform expects is a practical first step.

FAQ

Is OCPP 1.6J the same as OCPP 1.6?

No. OCPP 1.6 exists in a SOAP/XML edition and a JSON-over-WebSocket edition. "1.6J" refers to the JSON edition. Buyers should confirm which edition the target backend expects.

Will an OCPP 1.6J charger work with every backend?

Not automatically. Interoperability also depends on the platform's supported version, message profiles, security settings and the charger's configuration.

Do all wallbox chargers support OCPP?

No. OCPP support depends on the selected wallbox model and configuration. This should be verified per model rather than assumed across a product family.

Does OCPP replace load balancing or metering certification?

No. OCPP, DLB, MID metering and PEN fault protection are separate subjects and should each be reviewed against the project requirement and the applicable market.

What should be tested before a larger order or deployment?

A practical review typically covers protocol version matching, message-level behavior between the charger and the target backend, network stability under the site's actual conditions, firmware update behavior, and the access and authorization flow. A proof or small trial deployment can help confirm these points before a wider rollout.

Is OCPP the same as plug and charge?

No. Plug and charge relates to automated authentication and is associated with ISO 15118. It is a separate topic from OCPP version selection, and requirements should be checked against the target market and platform.