Jump to content

OCPP 1.6 JSON guide EVC2: Difference between revisions

From Teltonika Energy Wiki
No edit summary
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= INTEGRATING TELTOCHARGE WITH OCPP 1.6 JSON =
= Integrating Teltonika EVC stations with OCPP 1.6 JSON =


This guide explains how to integrate '''TeltoCharge''' with your existing system using the OCPP 1.6 JSON protocol.
This guide explains how to integrate '''Teltonika EVC stations''' with your existing system using the OCPP 1.6 JSON protocol.


== Getting started ==
== Getting started ==
Line 7: Line 7:
Before you begin, you will need the following:
Before you begin, you will need the following:


* TeltoCharge is installed and configured.
* Teltonika EVC station is installed and configured.
* TeltoCharge has access to the internet.
* Teltonika EVC station has access to the internet.
* Knowledge of the OCPP 1.6 JSON protocol.
* Knowledge of the OCPP 1.6 JSON protocol.


Line 25: Line 25:
4. Test the connection by starting a charging session from your OCPP 1.6 JSON server.
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)'''.
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 Teltonika EVC station please communicate with your Sales manager or directly through Teltonika Energy VIP HelpDesk)'''.


== How to connect TeltoCharge to chosen OCPP provider ==
== How to connect Teltonika EVC stations to chosen OCPP provider ==


*'''Connect TeltoCharge to the internet''' - make sure, that the charging station has the internet connection. (all types are acceptable)
*'''Connect Teltonika EVC station to the internet''' - make sure, that the charging station has the internet connection. (all types are acceptable)
[[File:Connectivity for OCPP.png|frameless|990x990px]]


[[File:Internet_Conectivity_(APP).png|alt=|frameless|700x700px]]
*'''Connect Teltonika EVC station to the chosen OCPP server'''
 
*'''Connect TeltoCharge to the chosen OCPP server'''


<u>OCPP provider must give you info about:</u>
<u>OCPP provider must give you info about:</u>
Line 41: Line 40:
When you have that information, insert it as shown in the picture below and press save.
When you have that information, insert it as shown in the picture below and press save.


[[File:OCPPss.png|alt=|frameless|700x700px]]
[[File:OCPP settings2.png|frameless]]
 
== Troubleshooting ==
 
If you encounter any issues during the integration process, refer to the troubleshooting section of your OCPP 1.6 JSON server documentation or contact Teltonika Energy technical support via your Sales manager or Teltonika Energy VIP HelpDesk.


= COMPATIBLE SOFTWARE PROVIDERS FOR OCPP INTEGRATION =
= 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).
This section provides an overview of the software providers that have been tested and proven compatible with Teltonika EVC station using the OCPP 1.6 JSON (Open Charge Point Protocol).


→For detailed TeltoCharge OCPP documentation contact Teltonika Energy Technical Support team via HelpDesk.←
→For detailed Teltonika EVC stations OCPP documentation contact Teltonika Energy Technical Support team via HelpDesk.←


<u>Segments description:</u>
<u>Segments description:</u>
Line 70: Line 65:


== Tested Software Providers ==
== Tested Software Providers ==
The software providers listed here have undergone comprehensive testing with TeltoCharge hardware, ensuring that they meet standards for performance and reliability.
The software providers listed here have undergone comprehensive testing with Teltonika EVC station 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.
*For integration of your OCPP software, please contact Teltonika Energy Technical Support team via HelpDesk.


Line 189: Line 184:
|}
|}


= OCPP IMPLEMENTATION =
Our station can accept various messages and configuration keys. The following is a list of supported standard messages, key names and values
{| class="wikitable"
|+
! colspan="2" |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
|-
! colspan="2" |Local Auth List Management
|-
|GetLocalListVersion
|
|-
|SendLocalList
|
|-
|LocalAuthListMaxLength
|Max 50 entries
|-
! colspan="2" |Smart Charging
|-
|SetChargingProfile
|
|-
|GetCompositeSchedule
|Max GetCompositeSchedule.req duration 24h
|-
|ClearChargingProfile
|
|-
! colspan="2" |Remote Trigger
|-
|TriggerMessage
|
|-
| colspan="2" |Reservation
|-
|ReserveNow
|
|-
|CancelReservation
|
|-
! colspan="2" |Firmware Management
|-
|GetDiagnostics
|
|-
|DiagnosticsStatusNotification
|
|-
|FirmwareStatusNotification
|
|-
|UpdateFirmware
|
|-
! colspan="2" |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
|
|}
=== Support configuration keys ===
{| class="wikitable"
! colspan="4" |Supported Configuration Key Names & Values
|-
! colspan="2" rowspan="2" |Key
! colspan="2" |Values
|-
!Default
!Supported range
|-
! colspan="4" |Core
|-
| colspan="2" |AllowOfflineTxForUnknownId
|0
|0, 1
|-
| colspan="2" |AuthorizeRemoteTxRequests
|1
|0, 1
|-
| colspan="2" |AuthorizationCacheEnabled
|1
|0, 1
|-
| colspan="2" |ClockAlignedDataInterval
|3600
|300-86400
|-
| colspan="2" |ConnectionTimeOut
|120
|1-3600
|-
| colspan="2" |ConnectorPhaseRotation
|Unknown
|Unknown,RST,RTS,SRT, STR,TRS,TSR
|-
| colspan="2" |GetConfigurationMaxKeys
|60
| -
|-
| colspan="2" |HeartbeatInterval
|3600
|60-86400
|-
| colspan="2" |LocalAuthorizeOffline
|0
|0, 1
|-
| colspan="2" |LocalPreAuthorize
|1
|0, 1
|-
| colspan="2" |MeterValuesAlignedData
|""
|Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import
|-
| colspan="2" |MeterValuesSampledData
|Energy.Active.Import.Register
|Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import
|-
| colspan="2" |MeterValueSampleInterval
|3600
|5-84600
|-
| colspan="2" |NumberOfConnectors
|1
| -
|-
| colspan="2" |ResetRetries
|10
|0-10
|-
| colspan="2" |StopTransactionOnEVSideDisconnect
|1
| -
|-
| colspan="2" |StopTransactionOnInvalidId
|0
|0, 1
|-
| colspan="2" |StopTxnAlignedData
|""
|""
|-
| colspan="2" |StopTxnSampledData
|""
|Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import
|-
|TransactionMessageAttempts
| colspan="2" |3
|1-100
|-
|TransactionMessageRetryInterval
| colspan="2" |20
|5-60
|-
|UnlockConnectorOnEVSideDisconnect
| colspan="2" |1
|0, 1
|-
|WebSocketPingInterval
| colspan="2" |10
|1-1200
|-
! colspan="4" |Local Auth List Management
|-
|LocalAuthListEnabled
| colspan="2" |1
|0, 1
|-
|LocalAuthListMaxLength
| colspan="2" |50
| -
|-
|SendLocalListMaxLength
| colspan="2" |10
| -
|-
! colspan="4" |Smart Charging
|-
|ChargeProfileMaxStackLevel
| colspan="2" |5
| -
|-
|ChargingScheduleAllowedChargingRateUnit
| colspan="2" |"Current"
| -
|-
|ChargingScheduleMaxPeriods
| colspan="2" |5
| -
|-
|MaxChargingProfilesInstalled
| colspan="2" |9
| -
|-
! colspan="4" |Firmware Management
|-
|SupportedFileTransferProtocols
| colspan="2" |"HTTP,HTTPS,FTP"
| -
|-
! colspan="4" |Improved Security
|-
|SecurityProfile
| colspan="2" |0
|0-3
|-
|CpoName
| colspan="2" |""
|0-128 symbols
|-
|AdditionalRootCertificateCheck
| colspan="2" |0
|0
|-
|CertificateStoreMaxLength
| colspan="2" |1
|1
|-
|AuthorizationKey
| colspan="2" |""
|32-40 symbols
|}
=== Error list ===
{| class="wikitable"
|+
!Error
!Explanation
!Info
|-
|Voltage Input fail
|Higher or lower voltage than allowed by mains setting + tolerance
|Check MainsVoltage, UpVoltageTolerance, DownVoltageTolerance settings if supply voltage and voltage tolerance is in accordance with the measured input voltage.
|-
|Voltage Output fail
|Higher or lower voltage than allowed by mains setting + tolerance
|Disconnect charging cable from the EV and check if the issue remains. Reboot charger and try to connect EV again.
|-
|Csmod fail
|Current leakage was detected
|Disconnect the cable from the EV and check if the error persists. If the error is cleared, try to start charging. If the error occurs once again, try following steps: Check if charging cable is fully plugged into socket and/or EV; Check if the inside of both the socket and the plug has no foreign materials inside (is clean). Check visually if the cable is not damaged. Check if the boards are not covered in dust and/or other materials.
|-
|Csmod test fail
|Current leakage sensor self- test failed
|Reboot charger and check if the issue remains.
|-
|Control pilot fail
|Control pilot voltage unexpected level
|Try reconnect charging cable from the EV side. There might be control pilot communication problem which can occur with different EV models. Reconnect EV and try again.
|-
|Car diode fail
|When PWM < 100 and state > A, the -12 V CP signal level is not within limits
|Try reconnect charging cable from the EV side. There might be control pilot communication problem which can occur with different EV models. Reconnect EV and try again.
|-
|Output current fail
|Overcurrent detected (current drawn by EV was higher than allowed by charger)
|Try reducing or increasing OCPP Smart Charging current limits. Restart Charging session. If the issue persists try disconnect and reconnect EV.
|-
|Temperature fail
|Temperature higher than fail limit was reached
|Temperature is higher than 85 ℃ wait while charger cools down.
|-
|Proximity pilot fail
|Cable PP voltage not within limits
|Disconnect the cable from the EV and inspect cable and EV socket: Check if charging cable is fully plugged into socket and/or EV; Check if the inside of both the socket and the plug has no foreign materials inside (is clean). Check visually if the cable is not damaged. Check if the boards are not covered in dust and/or other materials.
|-
|VREF fail
|Internal reference voltage not within limits
|Reboot charger and check if the issue remains.
|-
|Cable lock/unlock fail
|Cable lock/unlock function not working properly
|Check if the charging cable is connected correctly from the charger side (socket version) and from the EV side; Try to reconnect charging cable to the EV and EVSE (if it is socket version). Listen if you can hear a clicking sound from the TeltoCharge when you plug the cable to EV. Charger should lock cable plug.
|-
|Minus 12V fail
| -12V internal voltage is not within limits
|Reboot charger and check if the issue remains.
|-
|PEN protection fail
|Protective earthing fail detected
|Disconnect the cable from the EV and check if the error persists. If the error is cleared, try to start charging. If the error occurs once again, try following steps: Check if charging cable is fully plugged into socket and/or EV; Check if the inside of both the socket and the plug has no foreign materials inside (is clean). Check visually if the cable is not damaged. Check if the boards are not covered in dust and/or other materials.
|-
|Incorrect input wiring
|Voltage on phases is negative
|Check if input wiring is connected correctly. Neutral and phase may be mismatched.
|-
|Voltage sensor fail
|Voltage out of sensor range (U> 500 V or U < -500 V)
|Reboot charger and check if the issue remains.
|-
|Current sensor  fail
|Current out of sensor range (I > 60 A or I < -10 A)
|Reboot charger and check if the issue remains.
|-
|Temperature sensor fail
|Temperature out of sensor range (T > 125°C or T < -40°C)
|Reboot charger and check if the issue remains.
|-
|Eeprom memory failed
|EEPROM initialization fault
|Reboot charger and check if the issue remains.
|}
=== Warnings ===
{| class="wikitable"
!Warning
!Explanation
!Info
|-
|Output  current warning
|Current drawn by EV is higher than  allowed by charger (but lower than fail limit)
|Try reducing or increasing OCPP  Smart Charging current limits. Restart Charging session. If the issue  persists try disconnect and reconnect EV.
|-
|Temperature warning
|Temperature  higher than warning limit, current throttling is present
|Charging  station is reaching the set temperature warning value.
|-
|Ventilation  required
|D state detected
|Check if Charging location is  sufficiently ventilated.
|-
|RTC time lost
|Incorrect  EVSE time
|Check  EVSE RTC coin battery (CR1220) voltage.
|-
|Simplified  CP denied
|Simplified CP detected and not  allowed
|Connected EV uses Simplified  charging sequence. Simplified CP charging is disabled in Installer menu.
|-
|D state denied
|D  state detected and not allowed
|EV  requiring ventilation, but charging location is specified as not ventilated  in Installer menu.
|-
|PEN  CTC not calibrated
|PEN CTC is not calibrated
|Reboot charger and check if the  issue remains.
|-
|Sensors not calibrated
|Voltage/current  sensor calibration not present
|Reboot  charger and check if the issue remains.
|-
|Energy  meter comm fail
|Communication error of  DLB/DLM/SOLAR energy meter
|Check RS485 connection with  external meter. Inspect cable. Check if meter is working. Make sure devices  are configured properly.
|-
|NFC init fail
|NFC  initialization error
|Reboot  charger and check if the issue remains.
|-
|Low  battery voltage
|Low internal RTC battery voltage  (CR1220)
|Check EVSE RTC coin battery  (CR1220 voltage.
|-
|Energy meter wrong type
|Wrong  3ph/1ph type set of DLB/DLM/SOLAR energy meter
|Connected  Energy meter and configured Energy meter type in Installer menu are  different.
|-
|Energy  meter unidentified
|DLB/DLM/SOLAR energy meter is not  supported or not identified
|Unknown device detected. Check if  the energy meter is compatible.
|-
|Simple CP detected
|Simple  CP is detected
|Charging  initiated but B state was skipped. Connected EV uses Simplified CP.
|-
|DLB  CT clamps not calibr
|DLB/SOLAR/EXTRA CTC are not  calibrated
|Calibrate CT clamps.
|-
|Midplate is open
|Charger  case is currently open
|Close the  case
|-
|PEN fault  was detected (active)
|Charger was shut down because of PEN fail  (active for 10s after boot)
|Investigate whether PEN really occurred.
|-
|kWh meter faulty wiring
|kWh meter  does not measure the EVSE load correctly
|Change kWh  meter location.
|-
|DLM slave  device communication timed out
|DLM slave device detected communications  timeout
|Check RS485 connection.
|-
|Energy meter kWh comm fail
|Energy  meter kWh communication error
|Check RS485  connection.
|-
|Energy  meter kWh wrong type
|Energy meter kWh wrong type (3ph/1ph)
|Connected kWh meter and configured kWh  meter type in Installer menu are different. Check if kWh meter configuration  is correct.
|-
|Energy meter kWh unidentified
|Energy  meter kWh unidentified
|Meter not  supported.
|-
|DLM slave  device X communication fail
|X – number from 1 to 20. DLM master to  slave X communication error
|Check RS485 connection to specified device.  Check DLM settings on specified device.
|-
|DLM slave device X unidentified
|X – number  from 1 to 20. DLM slave X unidentified from master side
|Specified  device is not an EVC charger. Check Modbus addresses of your RS485 network  and DLM configuration.
|-
|Unauthorized  BLE connection attempt
|Unsuccessful bonding attempt using BLE
|Someone is trying to connect to the charger  using BLE.
|-
|Unauthorized UART connection attempt
|Unauthorized  connection attempt using UART port inside charger
|Someone is  trying to connect to charger’s internal ports.
|-
|Device case  was opened
|Charger case was opened
|Case was opened earlier. It may be already  closed.
|-
|PEN fault was detected: PE Current
|Current was  detected on PE cable before shutdown, fault is currently inactive
|Investigate  whether PEN fault really occurred.
|-
|PEN fault  was detected: Input Voltage
|Input voltage was out of specifications  before shutdown, fault is currently inactive
|Investigate whether PEN fault really  occurred.
|-
|Current leakage was detected
|Current  leakage was detected before shutdown, fault is currently inactive
|Disconnect  the cable from the EV and check if the error persists. If the error is  cleared, try to start charging. If the error occurs once again, try following  steps: Check if charging cable is fully plugged into socket and/or EV; Check  if the inside of both the socket and the plug has no foreign materials inside  (is clean). Check visually if the cable is not damaged. Check if the boards  are not covered in dust and/or other materials.
|}
''If you have more questions about OCPP please visit our FAQ section: https://wiki.teltonika-energy.com/view/FAQ''
''If you have more questions about OCPP please visit our FAQ section: https://wiki.teltonika-energy.com/view/FAQ''




[[Category: EVC2 Advanced Topics]]
[[Category: EVC2 Advanced Topics]]

Latest revision as of 13:01, 13 July 2026

EVC2 Advanced Topics > OCPP 1.6 JSON guide EVC2

Integrating Teltonika EVC stations with OCPP 1.6 JSON

This guide explains how to integrate Teltonika EVC stations with your existing system using the OCPP 1.6 JSON protocol.

Getting started

Before you begin, you will need the following:

  • Teltonika EVC station is installed and configured.
  • Teltonika EVC station 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 Teltonika EVC station please communicate with your Sales manager or directly through Teltonika Energy VIP HelpDesk).

How to connect Teltonika EVC stations to chosen OCPP provider

  • Connect Teltonika EVC station to the internet - make sure, that the charging station has the internet connection. (all types are acceptable)

  • Connect Teltonika EVC station to the chosen OCPP server

OCPP provider must give you info about:

  1. URL address - URL address must end with "/"
  2. 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 Teltonika EVC station using the OCPP 1.6 JSON (Open Charge Point Protocol).

→For detailed Teltonika EVC stations 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 Teltonika EVC station 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

Support configuration keys

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 -
ChargingScheduleAllowedChargingRateUnit "Current" -
ChargingScheduleMaxPeriods 5 -
MaxChargingProfilesInstalled 9 -
Firmware Management
SupportedFileTransferProtocols "HTTP,HTTPS,FTP" -
Improved Security
SecurityProfile 0 0-3
CpoName "" 0-128 symbols
AdditionalRootCertificateCheck 0 0
CertificateStoreMaxLength 1 1
AuthorizationKey "" 32-40 symbols

Error list

Error Explanation Info
Voltage Input fail Higher or lower voltage than allowed by mains setting + tolerance Check MainsVoltage, UpVoltageTolerance, DownVoltageTolerance settings if supply voltage and voltage tolerance is in accordance with the measured input voltage.
Voltage Output fail Higher or lower voltage than allowed by mains setting + tolerance Disconnect charging cable from the EV and check if the issue remains. Reboot charger and try to connect EV again.
Csmod fail Current leakage was detected Disconnect the cable from the EV and check if the error persists. If the error is cleared, try to start charging. If the error occurs once again, try following steps: Check if charging cable is fully plugged into socket and/or EV; Check if the inside of both the socket and the plug has no foreign materials inside (is clean). Check visually if the cable is not damaged. Check if the boards are not covered in dust and/or other materials.
Csmod test fail Current leakage sensor self- test failed Reboot charger and check if the issue remains.
Control pilot fail Control pilot voltage unexpected level Try reconnect charging cable from the EV side. There might be control pilot communication problem which can occur with different EV models. Reconnect EV and try again.
Car diode fail When PWM < 100 and state > A, the -12 V CP signal level is not within limits Try reconnect charging cable from the EV side. There might be control pilot communication problem which can occur with different EV models. Reconnect EV and try again.
Output current fail Overcurrent detected (current drawn by EV was higher than allowed by charger) Try reducing or increasing OCPP Smart Charging current limits. Restart Charging session. If the issue persists try disconnect and reconnect EV.
Temperature fail Temperature higher than fail limit was reached Temperature is higher than 85 ℃ wait while charger cools down.
Proximity pilot fail Cable PP voltage not within limits Disconnect the cable from the EV and inspect cable and EV socket: Check if charging cable is fully plugged into socket and/or EV; Check if the inside of both the socket and the plug has no foreign materials inside (is clean). Check visually if the cable is not damaged. Check if the boards are not covered in dust and/or other materials.
VREF fail Internal reference voltage not within limits Reboot charger and check if the issue remains.
Cable lock/unlock fail Cable lock/unlock function not working properly Check if the charging cable is connected correctly from the charger side (socket version) and from the EV side; Try to reconnect charging cable to the EV and EVSE (if it is socket version). Listen if you can hear a clicking sound from the TeltoCharge when you plug the cable to EV. Charger should lock cable plug.
Minus 12V fail -12V internal voltage is not within limits Reboot charger and check if the issue remains.
PEN protection fail Protective earthing fail detected Disconnect the cable from the EV and check if the error persists. If the error is cleared, try to start charging. If the error occurs once again, try following steps: Check if charging cable is fully plugged into socket and/or EV; Check if the inside of both the socket and the plug has no foreign materials inside (is clean). Check visually if the cable is not damaged. Check if the boards are not covered in dust and/or other materials.
Incorrect input wiring Voltage on phases is negative Check if input wiring is connected correctly. Neutral and phase may be mismatched.
Voltage sensor fail Voltage out of sensor range (U> 500 V or U < -500 V) Reboot charger and check if the issue remains.
Current sensor fail Current out of sensor range (I > 60 A or I < -10 A) Reboot charger and check if the issue remains.
Temperature sensor fail Temperature out of sensor range (T > 125°C or T < -40°C) Reboot charger and check if the issue remains.
Eeprom memory failed EEPROM initialization fault Reboot charger and check if the issue remains.

Warnings

Warning Explanation Info
Output current warning Current drawn by EV is higher than allowed by charger (but lower than fail limit) Try reducing or increasing OCPP Smart Charging current limits. Restart Charging session. If the issue persists try disconnect and reconnect EV.
Temperature warning Temperature higher than warning limit, current throttling is present Charging station is reaching the set temperature warning value.
Ventilation required D state detected Check if Charging location is sufficiently ventilated.
RTC time lost Incorrect EVSE time Check EVSE RTC coin battery (CR1220) voltage.
Simplified CP denied Simplified CP detected and not allowed Connected EV uses Simplified charging sequence. Simplified CP charging is disabled in Installer menu.
D state denied D state detected and not allowed EV requiring ventilation, but charging location is specified as not ventilated in Installer menu.
PEN CTC not calibrated PEN CTC is not calibrated Reboot charger and check if the issue remains.
Sensors not calibrated Voltage/current sensor calibration not present Reboot charger and check if the issue remains.
Energy meter comm fail Communication error of DLB/DLM/SOLAR energy meter Check RS485 connection with external meter. Inspect cable. Check if meter is working. Make sure devices are configured properly.
NFC init fail NFC initialization error Reboot charger and check if the issue remains.
Low battery voltage Low internal RTC battery voltage (CR1220) Check EVSE RTC coin battery (CR1220 voltage.
Energy meter wrong type Wrong 3ph/1ph type set of DLB/DLM/SOLAR energy meter Connected Energy meter and configured Energy meter type in Installer menu are different.
Energy meter unidentified DLB/DLM/SOLAR energy meter is not supported or not identified Unknown device detected. Check if the energy meter is compatible.
Simple CP detected Simple CP is detected Charging initiated but B state was skipped. Connected EV uses Simplified CP.
DLB CT clamps not calibr DLB/SOLAR/EXTRA CTC are not calibrated Calibrate CT clamps.
Midplate is open Charger case is currently open Close the case
PEN fault was detected (active) Charger was shut down because of PEN fail (active for 10s after boot) Investigate whether PEN really occurred.
kWh meter faulty wiring kWh meter does not measure the EVSE load correctly Change kWh meter location.
DLM slave device communication timed out DLM slave device detected communications timeout Check RS485 connection.
Energy meter kWh comm fail Energy meter kWh communication error Check RS485 connection.
Energy meter kWh wrong type Energy meter kWh wrong type (3ph/1ph) Connected kWh meter and configured kWh meter type in Installer menu are different. Check if kWh meter configuration is correct.
Energy meter kWh unidentified Energy meter kWh unidentified Meter not supported.
DLM slave device X communication fail X – number from 1 to 20. DLM master to slave X communication error Check RS485 connection to specified device. Check DLM settings on specified device.
DLM slave device X unidentified X – number from 1 to 20. DLM slave X unidentified from master side Specified device is not an EVC charger. Check Modbus addresses of your RS485 network and DLM configuration.
Unauthorized BLE connection attempt Unsuccessful bonding attempt using BLE Someone is trying to connect to the charger using BLE.
Unauthorized UART connection attempt Unauthorized connection attempt using UART port inside charger Someone is trying to connect to charger’s internal ports.
Device case was opened Charger case was opened Case was opened earlier. It may be already closed.
PEN fault was detected: PE Current Current was detected on PE cable before shutdown, fault is currently inactive Investigate whether PEN fault really occurred.
PEN fault was detected: Input Voltage Input voltage was out of specifications before shutdown, fault is currently inactive Investigate whether PEN fault really occurred.
Current leakage was detected Current leakage was detected before shutdown, fault is currently inactive Disconnect the cable from the EV and check if the error persists. If the error is cleared, try to start charging. If the error occurs once again, try following steps: Check if charging cable is fully plugged into socket and/or EV; Check if the inside of both the socket and the plug has no foreign materials inside (is clean). Check visually if the cable is not damaged. Check if the boards are not covered in dust and/or other materials.

If you have more questions about OCPP please visit our FAQ section: https://wiki.teltonika-energy.com/view/FAQ