Intro
This article creates an overview of StatusNotifications where the Status = Faulted.
For more information on Status Notifications, see this section: Status Notifications
Faulted StatusNotifications
Name | Mandatory | Description |
ConnectorId | Y | The ID of the connector for which the status is reported. ID '0' (zero) is used if the status is for the Charge Point main controller. |
errorCode | Y | This contains the error code reported by the Charge Point. |
info | N | Additional free format information related to the error. |
status | Y | This contains the current status of the Charge Point. |
vendorId | N | This contains the vendor-specific error code. |
vendorErrorCode | N | This identifies the vendor-specificimplementation. |
timestamp | N | The time for which the status is reported. If absent time of receipt of the message will be assumed. |
Below is a list of standard OCPP 1.6 error codes and indication how often they occur
Error code | Descriptions | Commonality |
ConnectorLockFailure | Failure to lock or unlock connector. | Very Frequently |
EVCommunicationError | Communication failure with the vehicle, might be Mode 3 or other communication protocol problem. This is not a real error in the sense that the Charge Point doesn’t need to go to the faulted state. Instead, it should go to the SuspendedEVSE state. | Low |
GroundFailure | Ground fault circuit interrupter has been activated. | Frequent |
HighTemperature | Temperature inside Charge Point is too high | Low |
InternalError | Error in internal hard- or software component | Low |
LocalListConflict | The authorization information received from the Central System is in conflict with the LocalAuthorizationList | Low |
NoError | No error to report. | Frequent |
OtherError | Other type of error. More information in vendorErrorCode. | Frequent |
OverCurrentFailure | Over current protection device has tripped. | Frequent |
OverVoltage | Voltage has risen above an acceptable level | Frequent |
PowerMeterFailure | Failure to read power meter. | Frequent |
PowerSwitchFailure | Failure to control power switch. | Low |
ReaderFailure | Failure with idTag reader. | Low |
ResetFailure | Unable to perform a reset. | Low |
UnderVoltage | Voltage has dropped below an acceptable level. | Low |
WeakSignal | Wireless communication device reports a weak signal. | Low |
Error Codes and Diagnostics
Under development
This section will require more work in the future
ConnectorLockFailure
Type | Incorrect Driver behaviour |
Description | In most cases, this just means that a Driver has not correctly inserted the cable after starting a session |
Impact | low - no charging session |
Resolution | The issue will resolve itself when the driver disconnects or properly connectors |
Type | Lockmechanism failure |
Description | The locking mechanism does not work. Even after stopping a transaction, the cable can't be removed from the CS |
Impact | high - driver can't leave with cable |
Resolution | - try a remote unlock- try remote reset of CS |