OCPP 1.6 JSON guide EVC2
INTEGRATING TELTOCHARGE WITH OCPP 1.6 JSON
This guide explains how to integrate TeltoCharge with your existing system using the OCPP 1.6 JSON protocol.
Getting started
Before you begin, you will need the following:
- TeltoCharge is installed and configured.
- TeltoCharge has access to the internet.
- Knowledge of the OCPP 1.6 JSON protocol.
Steps
1. Configure the charging station to connect to your OCPP 1.6 JSON server. You will need to know the IP address or domain name of your server and the port number for the OCPP 1.6 JSON protocol.
2. Set up a charging station account on your OCPP 1.6 JSON server. You will need to provide the following information:
* Charging station ID: This is a unique identifier for your charging station. * Charging station type: Specify the type of charging station you have. (AC) * Other settings as required by your OCPP 1.6 JSON server.
3. Connect the charging station to your OCPP 1.6 JSON server. The charging station will communicate with your server using the OCPP 1.6 JSON protocol.
4. Test the connection by starting a charging session from your OCPP 1.6 JSON server.
5. Monitor the charging station from your OCPP 1.6 JSON server. You will be able to view the charging status, energy usage, and other important information about the charging station (for configuration keys available at the moment from TeltoCharge please communicate with your Sales manager or directly through Teltonika Energy VIP HelpDesk).
How to connect TeltoCharge to chosen OCPP provider
- Connect TeltoCharge to the internet - make sure, that the charging station has the internet connection. (all types are acceptable)
- Connect TeltoCharge to the chosen OCPP server
OCPP provider must give you info about:
- URL address - URL address must end with "/"
- Charge point ID - Most of the time it's the serial number of the charging station
When you have that information, insert it as shown in the picture below and press save.
COMPATIBLE SOFTWARE PROVIDERS FOR OCPP INTEGRATION
This section provides an overview of the software providers that have been tested and proven compatible with TeltoCharge using the OCPP 1.6 JSON (Open Charge Point Protocol).
→For detailed TeltoCharge OCPP documentation contact Teltonika Energy Technical Support team via HelpDesk.←
Segments description:
- Public Charging Networks - managing large networks of public EV charging stations.
Real-time monitoring, dynamic pricing, user authentication, remote diagnostics, and reporting.
- Commercial and Fleet Charging - supporting commercial fleets and workplace charging solutions.
Fleet management tools, scheduled charging, energy usage reporting, and integration with fleet management systems.
- Residential Charging Solutions - providing home EV charging management for individual users.
User-friendly interfaces, mobile app control, energy usage tracking, and integration with smart home systems.
- Retail and Hospitality Charging - offering EV charging as an amenity at retail locations, hotels, and restaurants.
Customer engagement tools, loyalty programs integration, payment processing, and usage analytics.
Tested Software Providers
The software providers listed here have undergone comprehensive testing with TeltoCharge hardware, ensuring that they meet standards for performance and reliability.
- For integration of your OCPP software, please contact Teltonika Energy Technical Support team via HelpDesk.
List of supported platforms
| Software Vendor | Public Charging Networks | Commercial and Fleet Charging | Residential Charging Solutions | Retail and Hospitality Charging | Official page |
|---|---|---|---|---|---|
| Focus EV | + | + | + | FOCUS EV | |
| Monta | + | + | + | + | MONTA |
| EEVY | + | + | + | + | EEVY |
| Ampeco | + | + | AMPECO | ||
| LastMilesSolutions | + | + | LMS | ||
| GreenFlux | + | + | + | GREENFLUX | |
| SaasCharge | + | + | + | SAASCHARGE | |
| Daloop | + | DALOOP | |||
| Go To-U | + | + | GO TO-U | ||
| Tap Electric | + | + | + | + | TAP ELECTRIC |
| Clenergy EV | + | + | + | + | Clenergy EV |
| Enerlink | + | + | + | + | ENERLINK |
| E-Flux | + | + | + | + | E-FLUX |
| PlugFuse | + | + | + | + | PLUGFUSE |
| eMabler | + | + | + | + | eMABLER |
OCPP IMPLEMENTATION
Our station can accept various messages and configuration keys. The following is a list of supported standard messages, key names and values
| Supported messages | |
|---|---|
| Message | Comment |
| Authorize | |
| BootNotification | |
| ChangeAvailability | |
| ChangeConfiguration | |
| ClearCache | Authorization Cache with max 20 entries |
| DataTransfer | No custom commands |
| GetConfiguration | Max 60 elements per request |
| Heartbeat | |
| MeterValues | In MeterValuesSampledData, MeterValuesAlignedData and StopTxnSampledData only.
Supported measurands: Energy.Active.Import.Register,Current.Import,Current.Offered, Temperature,Voltage,Power.Active.Import. Minimum interval 5s |
| RemoteStartTransaction | |
| RemoteStopTransaction | |
| Reset | |
| StartTransaction | |
| StopTransaction | |
| StatusNotification | |
| UnlockConnector | For socket version charger only |
| Local Auth List Management | |
| GetLocalListVersion | |
| SendLocalList | |
| LocalAuthListMaxLength | Max 50 entries |
| Smart Charging | |
| SetChargingProfile | |
| GetCompositeSchedule | Max GetCompositeSchedule.req duration 24h |
| ClearChargingProfile | |
| Remote Trigger | |
| TriggerMessage | |
| Reservation | |
| ReserveNow | |
| CancelReservation | |
| Firmware Management | |
| GetDiagnostics | |
| DiagnosticsStatusNotification | |
| FirmwareStatusNotification | |
| UpdateFirmware | |
| Improved Security | |
| CertificateSigned | |
| ExtendedTriggerMessage | |
| GetInstalledCertificateIds | Only CentralSystemRootCertificate type is supported |
| GetLog | |
| InstallCertificate | Only CentralSystemRootCertificate type is supported |
| LogStatusNotification | |
| SecurityEventNotification | Only ReconfigurationOfSecurityParameters, SettingSystemTime, SecurityLogWasCleared,
StartupOfTheDevice, ResetOrReboot, FirmwareUpdated notifications are used |
| SignCertificate | |
| Supported Configuration Key Names & Values | |||
|---|---|---|---|
| Key | Values | ||
| Default | Supported range | ||
| Core | |||
| AllowOfflineTxForUnknownId | 0 | 0, 1 | |
| AuthorizeRemoteTxRequests | 1 | 0, 1 | |
| AuthorizationCacheEnabled | 1 | 0, 1 | |
| ClockAlignedDataInterval | 3600 | 300-86400 | |
| ConnectionTimeOut | 120 | 1-3600 | |
| ConnectorPhaseRotation | Unknown | Unknown,RST,RTS,SRT, STR,TRS,TSR | |
| GetConfigurationMaxKeys | 60 | - | |
| HeartbeatInterval | 3600 | 60-86400 | |
| LocalAuthorizeOffline | 0 | 0, 1 | |
| LocalPreAuthorize | 1 | 0, 1 | |
| MeterValuesAlignedData | "" | Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import | |
| MeterValuesSampledData | Energy.Active.Import.Register | Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import | |
| MeterValueSampleInterval | 3600 | 5-84600 | |
| NumberOfConnectors | 1 | - | |
| ResetRetries | 10 | 0-10 | |
| StopTransactionOnEVSideDisconnect | 1 | - | |
| StopTransactionOnInvalidId | 0 | 0, 1 | |
| StopTxnAlignedData | "" | "" | |
| StopTxnSampledData | "" | Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import | |
| TransactionMessageAttempts | 3 | 1-100 | |
| TransactionMessageRetryInterval | 20 | 5-60 | |
| UnlockConnectorOnEVSideDisconnect | 1 | 0, 1 | |
| WebSocketPingInterval | 10 | 1-1200 | |
| Local Auth List Management | |||
| LocalAuthListEnabled | 1 | 0, 1 | |
| LocalAuthListMaxLength | 50 | - | |
| SendLocalListMaxLength | 10 | - | |
| Smart Charging | |||
| ChargeProfileMaxStackLevel | 5 | - | |
| ChargingScheduleAllowedChargingRat eUnit | "Current" | - | |
| ChargingScheduleMaxPeriods | 5 | - | |
| MaxChargingProfilesInstalled | 9 | - | |
| Firmware Management | |||
| SupportedFileTransferProtocols [2] | "HTTP,HTTPS,FTP" | - | |
| Improved Security | |||
| SecurityProfile [5] | 0 | 0-3 | |
| CpoName [5] | "" | 0-128 symbols | |
| AdditionalRootCertificateCheck [5] | 0 | 0 | |
| CertificateStoreMaxLength [5] | 1 | 1 | |
| AuthorizationKey [4] | "" | 32-40 symbols | |
If you have more questions about OCPP please visit our FAQ section: https://wiki.teltonika-energy.com/view/FAQ