The core element of the Gateway Connect is a standard OCPP proxy, which relays incoming messages from connected charging stations to any freely selectable Charge Point Management System (CPMS - the backend for authorization and billing).
The OCPP proxy does not interrupt or modify the communication flow between your charging stations and the CPMS. It only monitors the message flow between the charge points and the CPMS. All charging stations at the infrastructure are connected to the integrated OCPP-Proxy. For each single charging station connection, the proxy will create a connection to a selected CPMS.
It is also possible to operate the system without having a CPMS connected to charging stations.
State changes at a charge point and other information, which are relevant, are forwarded by the proxy to the Gateway built-in FLEXeCHARGE Load- and Energy Management System (LMS). Based on this information, the LMS allocates charge currents to requesting EVs according to the selected Smart Charging Policies.
Through its proxy architecture, the FLEXeCHARGE Smart Charging Solution is fully compatible with all Charging Stations and the Charge Point Management Systems (CPMS), which use the Open Charge Point Protocol (OCPP).
Additionally, the system can interface charging stations, power meters, and additional local appliances via Modbus or vendor-specific APIs.
The described OCCP-Proxy architecture is displayed in the image below.
CS = Charging station
WS = Web socket
WSS = Web socket secure
SmartCharging OCPP Messages
The proxy sends standard SmartCharging OCPP Messages (SetChargingProfile) to set the maximum charge current per charger.
These are:
TxDefaultProfile (Default)
TxProfile (Transaction related)
OCPP Message Transparency:
The proxy is fully transparent, meaning every OCPP message is sent from either the backend (CPMS) or a charging station (CS) will be forwarded. The proxy neither adds nor removes, or modifies any OCPP message to the message flow between the charger and the backend.
Connection Transparency:
The proxy is fully connection transparent, meaning if the connection to a charging station (CS) breaks, it will also shut down the connection to the Backend (CPMS) for that charger; the same is true for the backend connection if the connection to a backend is lost, it will break all charger connections for that backend.
The FLEXeCHARGE Gatewayx Connect can be deployed in two configurations.
1. Self-Contained network
2. Existing Building Local Area Network.
See the tabs below to ensure you follow the proper instructions.
When configured as a self-contained network, the Gateway is directly connected to the charging stations and other devices within its own network. In this case, the Gateway functions as a DHCP Server (read more on that in CONFIGURATION LINK). Internet access is provided through the Gateway and its inbuild LTE router. You can either use the FLEXeCHARGE SIM, which requires no setup, or use your own SIM card (make sure to have the PIN, SUPER PIN, and PUK and check that a Sim_Lock is not enabled).
When choosing this configuration, the network must not have internet access through another source.
Otherwise, the preconfigured IP will change and complicate setup.
After choosing a setup type, you are ready to continue with the installation of the Gateway Connect.
Gateway Connect Installation_Guide
In case the existing internet connection is supposed to be used, the Gateway and charging stations, as well as the internet access, must be connected to the same network (for example, via multiple switches). In this configuration, the Gateway functions as a DHCP Client and receives its IP address through the network.
After choosing a setup type, you are ready to continue with the installation of the Gateway Connect.
Gateway Connect Installation_Guide