Ocpp Backend; Connection To An Ocpp Backend - Eaton xChargeIn M Serie Konfigurationshandbuch

Functions
5.3

OCPP backend

The charging station offers the option of being connected to a central man-
agement system via the Open Charge Point Protocol (OCPP). OCPP, as an
open application protocol, makes it possible to connect any central manage-
ment system to the charging station regardless of the manufacturer or sup-
plier. The following OCPP versions are supported:
●
●

Connection to an OCPP backend

When connecting to an OCPP backend, note the following:
●
●
●
●
●
Ports for communication via OCPP
For communication with an OCPP backend, the following ports must be en-
abled in the network:
Custom
(1025 -
Custom
82
OCPP 1.5 via SOAP
OCPP 1.6 via SOAP or JSON
It is recommended that the master charging station on the network be
assigned a static IP address based on the MAC address of the device.
Since the OCPP backend is usually not in the same network, the charg-
ing station must be assigned a "public IP address" which is routed to the
internal IP address (NAT).
The firewall must be configured so that communication between the
charging station and the OCPP backend is possible.
For a connection via VPN, the IP address of the VPN must be specified
in the configuration (web interface) for the downlink.
In the case of a mobile communications connection, it may be necessary
for the required ports to be activated by the cellular service provider.
Port Protocol
TCP
65535)
TCP
123 UDP
Definition
Can be reached externally
(incoming)
Access to external (outgo-
ing)
Incoming and outgoing
xChargeIn M Series
Description
OCPP Charge Point Service: This
service is related to the OCPP
backend.
● The port can be freely selected
or it is specified by the OCPP
backend. However, the port
may only be located in the
range from 1025 to 65535.
● The selected port must be
configured on the charging
station.
Port at which the OCPP backend
can be reached.
Port for the time server of the
charging station.
Configuration manual V1.04
© EATON