-
Notifications
You must be signed in to change notification settings - Fork 82
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
First draft of new BSP interface. SIL is working,
all other BSP drivers are broken for now. add publish of capabilities for runtime changes add MREC fault types for EvseManager and bsp interface add more specific error codes for connector lock. support A_63_3ph_70_1ph add separate pp_ampacity var add draft for connector lock interface Allow non IEC compliant EVs to pause/resume Start adding error definitions. SIL is still waiting for JS support for errors Add errors for evse_manager allow resume charging after everest restart remove extra stop power on unplug. This may lead to a short pause state if C->A happens without going through B move connector_type into hw_caps Signed-off-by: Cornelius Claussen <[email protected]>
- Loading branch information
1 parent
52a1184
commit b2f68eb
Showing
62 changed files
with
1,810 additions
and
1,229 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
description: >- | ||
Errors for Connector Lock | ||
These following error types give more details about connector lock errors. | ||
You should consider setting a MREC_1_ConnectorLockFailure to indicated a generic lock failure with an MREC error code as well | ||
as one of the more detailed but custom error codes to specify the reason: | ||
All error codes that begin with MREC needs to be implemented to fulfill the Minimum Required Error Codes defined by the ChargeX consortium: | ||
https://inl.gov/content/uploads/2023/07/ChargeX_MREC_Rev5_09.12.23.pdf | ||
errors: | ||
- name: ConnectorLockCapNotCharged | ||
description: The capacitor for connector lock motor failed to charge within expected time | ||
- name: ConnectorLockUnexpectedOpen | ||
description: The connector lock feedback does return open while it should be close | ||
- name: ConnectorLockUnexpectedClose | ||
description: The connector lock feedback does return closed while it should be open | ||
- name: ConnectorLockFailedLock | ||
description: The connector lock failed to lock (feedback still returns open) | ||
- name: ConnectorLockFailedUnlock | ||
description: The connector lock failed to unlock (feedback still returns closed) | ||
- name: MREC1ConnectorLockFailure | ||
description: >- | ||
Failure to lock or unlock connector on the vehicle side as per MREC definition. | ||
How should that be implemented? We can only find out about locking on the EVSE side, | ||
so we will use this error to report EVSE side lock failures. It is probably a mistake in the MREC definition. | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
description: >- | ||
Errors for the evse_board_support interface. | ||
All error codes that begin with MREC needs to be implemented to fulfill the Minimum Required Error Codes defined by the ChargeX consortium: | ||
https://inl.gov/content/uploads/2023/07/ChargeX_MREC_Rev5_09.12.23.pdf | ||
errors: | ||
- name: DiodeFault | ||
description: The CP diode in the EV is shorted. | ||
- name: VentilationNotAvailable | ||
description: EV requested state D but no ventilation is available. | ||
- name: BrownOut | ||
description: The hardware/MCU detected a brown out. | ||
- name: EnergyManagement | ||
description: Energy could not be delivered because an (external) energy management failed. | ||
- name: PermanentFault | ||
description: The EVSE is permanently broken and requires repair. | ||
- name: MREC2GroundFailure | ||
description: Ground fault circuit interrupter has been activated. | ||
- name: MREC3HighTemperature | ||
description: High temperature inside the EVSE is derating power delivery. | ||
- name: MREC4OverCurrentFailure | ||
description: Over current protection device has tripped. | ||
- name: MREC5OverVoltage | ||
description: Input voltage to the vehicle has risen above an acceptable level. | ||
- name: MREC6UnderVoltage | ||
description: Input voltage to the vehicle has dropped below an acceptable level. | ||
- name: MREC8EmergencyStop | ||
description: Emergency stop is pressed by the user (required if equipped). | ||
- name: MREC10InvalidVehicleMode | ||
description: The vehicle is in an invalid mode for charging (Reported by IEC stack) | ||
- name: MREC14PilotFault | ||
description: The control pilot voltage is out of range. | ||
- name: MREC15PowerLoss | ||
description: The EVSE is unable to supply any power due to mains failure | ||
- name: MREC17EVSEContactorFault | ||
description: Contactors fail to open or close on EVSE's side. May also include welding related errors. | ||
- name: MREC18CableOverTempDerate | ||
description: Temperature of charging cable or connector assembly is too high, resulting in reduced power operation. | ||
- name: MREC19CableOverTempStop | ||
description: Temperature of charging cable or connector assembly is too high, resulting in a stopped charging session. | ||
- name: MREC20PartialInsertion | ||
description: Cable latch is raised due to incomplete insertion into the vehicle charging port. | ||
- name: MREC23ProximityFault | ||
description: The proximity voltage is out of range. | ||
- name: MREC24ConnectorVoltageHigh | ||
description: The output voltage of EVSE is high before charging starts or after charging ends. | ||
- name: MREC25BrokenLatch | ||
description: The latch on the connector is broken. | ||
- name: MREC26CutCable | ||
description: The output cable has been severed from the EVSE. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
description: >- | ||
Errors for EvseManager | ||
All error codes that begin with MREC needs to be implemented to fulfill the Minimum Required Error Codes defined by the ChargeX consortium: | ||
https://inl.gov/content/uploads/2023/07/ChargeX_MREC_Rev5_09.12.23.pdf | ||
errors: | ||
- name: Internal | ||
description: Internal error of the state machine | ||
- name: MREC4OverCurrentFailure | ||
description: Over current event |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
description: >- | ||
This interface defines an AC Residual Current Monitor (RCD). Actual emergency switch off is done in HW directly, | ||
but this interface allows some control and telemetry. | ||
cmds: | ||
self_test: | ||
description: >- | ||
Executes a self test of the RCD. Once finished, the var self_test_result should be published. Since | ||
the test can take quite long we do not use a synchronous return value here. | ||
reset: | ||
description: >- | ||
Resets the RCD after a trigger. May not be supported by actual hardware. | ||
result: | ||
description: 'True: Reset successfull, False: Reset failed.' | ||
type: boolean | ||
vars: | ||
rcd_current_mA: | ||
description: Residual current in mA. Note that this does not trigger anything, it is merely for reporting. | ||
type: number | ||
fault_ac: | ||
description: Indicates an AC residual current fault (informational only, hardware needs to shut down power on its own) | ||
type: 'null' | ||
fault_dc: | ||
description: Indicates an DC residual current fault (on the AC wires, informational only, hardware needs to shut down power on its own). | ||
type: 'null' | ||
self_test_result: | ||
description: Result of a triggered self test | ||
type: boolean |
Oops, something went wrong.