OCPP Forwarding
Julian Ares
Last Update 11 giorni fa
Using InControl's OCPP (Open Charge Point Protocol) forwarding service, your charger can connect to any OCPP-compliant charge management software ("OCPP Primary"). This enables you to take advantage of specialized 3rd party software for payment, vehicle routing, energy management, and more, while providing InCharge with vital remote access to your charging assets.
While in "proxy mode" the InControl system is forwarding all OCPP messages from the charger to the OCPP Primary, and from the OCPP Primary to the charger. InControl is automatically configured in a passive mode to prevent collisions while proxy mode is active. Charger control operations are greyed out and unavailable to you as the user.
There are times where InCharge needs to turn off proxy mode to make InControl the primary. Future releases will switch the connected OCPP backend passive without interrupting the connection to the charger. This allows service visits, over-the-air charger firmware updates, remote reset, OCPP backend instability, and configuration changed to be issued when necessary on the InControl side. We will coordinate with out OCPP backend partners to schedule these outages whenever possible ahead of time, so they are aware of our actions and can plan accordingly.
How it Works
| ICE Split Systems | Note that ICE-480 and ICE-600 system dispensers function as independent chargers. For example, a four-dispenser system will require four charger objects with unique serial numbers and OCPP data streams in the OCPP backend. |
| Load Management | With InControl set as the passive OCPP backend, Load Management and Smart Charging rules will not be active on the chargers with an enabled proxy connection. We would rely on the active OCPP backend for energy management policy enforcement. |
| Notifications | With InControl set as the passive OCPP backend, Notifications set within InControl will not be sent to designated users. |
| OCPP Data Messages | Our V2X chargers and ICE Cube integrated battery storage (BESS) products utilize several custom OCPP data messages. These additional messages provide functionality outside the scope of the OCPP 1.6-J protocol. We provide documentation separately for integration with these units. |
| OCPP Security Addendum | Currently we support OCPP 1.6-J Security Addendum 3 and Security Profiles 1, 2, and 3. |
| OCPP Versions Supported | Currently we support OCPP 1.6-J fully and OCPP 2.0.1 in limited applications. Throughout 2025 we expect to widen support for 2.0.1. |
| Hybrid Roles | Some OCPP backends are providing extensions of feature sets (payment authorization, energy management) and are not concerned with other aspects of the charger maintenance and management. Future releases will relegate passive and active roles at a granular, feature level. |
| Primary / Passive Toggle | Currently, we turn off the proxy connection to perform service on the charger so as to give the onsite service personnel access to InControl diagnostics tools. The planned feature will allow the technician to set the OCPP backend to either primary or passive. |