What connection to use?
When connecting your charger(s) to GreenFlux platform, you will be able to connect to choose between two different environments:
Environment | Purpose | (User Access) to Front-end (EvPortal) | Configurations to connect charger to the back-end |
ACCeptance | Customer should use ACC to perform tests and experiences before deploying in Production | Check section below "GreenFlux Endpoints" | |
PRODuction | PROD should be used to connect chargers that will operate under real life conditions |
There are several options that influence the type of configuration settings that need to be defined in the charge station, in order to ensure a smooth connection/commissioning with GreenFlux platform. The following variables/settings need to be assessed:
- Which type of OCPP protocol version to choose? 1.5 JSON; 1.5 SOAP; 1.6 JSON or 2.0.1. This is part of charge station configurations.
- Which type of connection to choose? Secure vs Insecure. This is part of charge station configurations.
- Which APN and communication plan to use, when applicable? This is defined by the Telecom provider, and then configured in the charge station
- What is the endpoint/URL format accepted by the charger?
- Which type of endpoint/URL to choose? Public vs Private. This is determined by GreenFlux, as defined below.
- Other configuration settings (e.g. websocket ping interval, etc)
- Which endpoint/URL to choose? This is determined by GreenFlux, as defined below.
Note: For configurations and settings related with external vendors (e.g. manufacturers, TelCo), check their documentation or support to get the full details.
To manage security check The Security Manager Role
Which OCPP protocol version to choose?
The protocol is defined/chosen by the customer, according to what the charge station supports. +90% of the chargers connected to our platform use OCPP 1.6 JSON, so for the moment, this GreenFlux recommendation. Other OCPP versions are also supported, as per below:
- 1.6 JSON
- 1.5 JSON
- 2.0.1 (protocol still to be tested)
Note: Chargers have to integrated based on protocol version as well. Our current OCPP integration testing is executed on 1.6 JSON. Only one charger (EVBOX G2) is integrated on 1.5 SOAP. No further integrations using 1.5 SOAP protocol are possible.
Which type of connection to choose?
The protocol is defined/chosen by the customer, according to what the charge station supports. This configuration needs to be set in the charge station. It is GreenFlux recommendation that customers use secure connections. The two options are as follows:
Secure connection (TLS, WSS):
- E2E encryption between charge station and GreenFlux platform
- Charge station needs to support it
Note: Some chargers like Alfen needs to have uploaded a certificate.
Insecure connection (WS):
- Data can be intercepted and corrupted
Which APN to use?
The APN (access point name) only needs to be defined in the charge station when user wants to connect to GreenFlux through a VPN connection. The VPN tunnel is default when using Datacom provided by GreenFlux. When datacom is not provided by GreenFlux, then it depends on whether GreenFlux and the datacom provider from the customer have established a VPN connection (this needs to be contractually agreed with the customer and implemented).
Furthermore, it may also be needed to define the appropriate communication plan for the SIM card. GreenFlux ensures the proper one is used for our SIM cards, check with your TelCo if the correct one is used.
When using GreenFlux provided SIM cards, the APN that needs to be used is shown in the table about the end-points.
Internal (GFX) note: For GreenFlux SIM cards Communication plan for NSS (coverage Europe + UK) is Data SMS LTE - EU+3 + KPN - APN2 - GreenFlux
What is the endpoint/URL format accepted by charger?
Some manufacturers use customized endpoints/URLs, like removing ws or adding port number explicitly in URL endpoint. Every manufacturer should be aware what endpoint format they support, so in case of doubt the CPO operators should check with them. However, please see examples below:
Manufacturer | EndPoint format * |
Alfen | ws://ocpp.greenflux.com, ws://ocpp.greenflux.com:80 |
EvBox | ws://ocpp.greenflux.com/ |
Greenflux controller | ocpp.greenflux.com |
Wallbox | ws://ocpp.greenflux.com:80/, wss://ocpp-public.greenflux.com:443/ |
Keba | ocpp.greenflux.com |
Delta | ws://ocpp.greenflux.com |
- The examples above are mostly to private insecure endpoint. Please check with manufacturer's documentation what the format looks like.
Which type of endpoint/URL to choose?
Choose private endpoint/URL when:
- connectivity through APN - GreenFlux provided SIM cards) or
- connectivity through APN - Using customer's own datacom SIM provider, with VPN tunnel established
Choose public endpoint/URL when:
- connectivity through APN - Using customer's own datacom SIM provider, without VPN tunnel established or
- connectivity through Wifi or LAN cable
Other configuration settings
These configurations need to (must) be made on the charge station (and 1 in EvPortal as well), prior to commissioning!
- Charge station ID (OCPP ID) must be added to the EvPortal (ID must have the exactly the same as configured on charger). If charger is not added to the portal, boot notification will be automatically rejected and connection won't be established)
- The web socket ping interval must be set to a value of 180 (seconds) or less. We recommend setting it to 180 seconds. The OCPP key that you need to configure in the charge station should be called 'WebSocketPingInterval'. If it's not available for your charger please reach out to your manufacturer for the name of the configuration key.
- Heartbeat Interval must be set to a value of 900 or less We recommend setting it to 900 seconds. The OCPP key that you need to configure in the charge stations is called "Heartbeatinterval".
- When setting up the DNS configuration on the charger please refrain from using the IP address of the DNS or that of the socket server as these are not static and likely to change without notice. This will lead to chargers configured this way to loose connection and GreenFlux will not be held responsible for any disconnections caused by this configuration. Instead please use the DNS url endpoint.
- 'MeterValueSampleInterval' configuration key: it is advisable to set it between 300 (5 minutes) and 900 (15 minutes). Please not that putting a very low number may increase the data consumption.
- 'MeterValuesSampledData' configuration key: 'Energy.Active.Import.Register,Current.Import,Current.Offered' OR 'Energy.Active.Import.Register,Current.Import.L1,Current.Import.L2,Current.Import.L3,Current.Offered.L1,Current.Offered.L2,Current.Offered.L3'
Which endpoint/URL to choose? Greenflux Endpoints
Based on the variables you went through above, you should now be able to based on those pick the correct endpoint and APN (if applicable), that you will need to configure then in the charge station.
ONLY for chargers using JSON protocol
Type endpoint | Secure vs insecure | PRODuction Environment endpoint | ACCeptance Environment endpoint | Port | APN* |
Public | Secure | wss://ocpp-public.greenflux.com | wss://ocpp-public-a.greenflux.com | 443 | N/A |
Public | Insecure | ws://ocpp-public.greenflux.com | ws://ocpp-public-a.greenflux.com | 80 | N/A |
Private | Secure | wss://ocpp.greenflux.com | wss://ocpp-a.greenflux.com | 443 | apn2.greenflux.tele2.m2m |
Private | Insecure | ws://ocpp.greenflux.com | ws://ocpp-a.greenflux.com | 80 | apn2.greenflux.tele2.m2m |
ONLY for EV - BOX G2 using 1.5 SOAP protocol Format of URL endpoint is a little bit different, check with your manufacturer what is the format they use. No further integrations of this protocol are possible.
Type endpoint | Secure vs insecure | PRODuction Environment endpoint/URL | ACCeptance Environment endpoint/URL | Port | APN* |
Insecure | Private | 80 | apn2.greenflux.tele2.m2m |
APN is valid for SIM cards provided by GreenFlux. When using your own datacom, the APN should be provided by your TelCo provider.