CCS32Clara - Revision history

Tom91: DEAD

2024-12-20T17:48:59Z

DEAD

← Older revision		Revision as of 17:48, 20 December 2024
Line 1:		Line 1:
	The information on this page has been transferred to [[Fully Open CCS Charge Controller (FOCCCI)]]		The information on this page has been transferred to [[Fully Open CCS Charge Controller (FOCCCI)]]
	~~[[Category:ChaDeMo‏‎]]~~
	~~[[Category:CCS]]~~
	~~[[Category:Rapid Charging]]~~
	__FORCETOC__		__FORCETOC__
			[[Category:DEAD]]

Johu: Moved all content from here to Foccci page

2024-06-25T08:13:10Z

Moved all content from here to Foccci page

Show changes

Johu: moved refs to bottom

2024-06-24T12:37:16Z

moved refs to bottom

← Older revision		Revision as of 12:37, 24 June 2024
Line 401:		Line 401:

	'''<u>Attention:</u>''' with this mapping the error flags are ignored, e.g. voltage or current mismatch.		'''<u>Attention:</u>''' with this mapping the error flags are ignored, e.g. voltage or current mismatch.
	~~<references />~~

	== Making Clara talk to boostech BMS ==		== Making Clara talk to boostech BMS ==
Line 410:		Line 410:

	''As of now this mapping is preliminary and has to be confirmed. will then remove this note''		''As of now this mapping is preliminary and has to be confirmed. will then remove this note''
			<references />
	[[Category:ChaDeMo‏‎]]		[[Category:ChaDeMo‏‎]]
	[[Category:CCS]]		[[Category:CCS]]
	[[Category:Rapid Charging]]		[[Category:Rapid Charging]]
	__FORCETOC__		__FORCETOC__

Johu: /* Using Clara as a charge coordinator */

2024-06-24T12:36:06Z

Using Clara as a charge coordinator

← Older revision		Revision as of 12:36, 24 June 2024
Line 35:		Line 35:
	* CableCurrentLimit		* CableCurrentLimit

	To activate the 1k3 ~~resitor~~ aka activating the AC outlet we map AcObcState. It must be set to 2 for activation.		To activate the 1k3 resistor aka activating the AC outlet we map AcObcState. It must be set to 2 for activation.

	Some chargers want to evaluate the CP (and perhaps PP) signal themselves. This issue can ~~yet only~~ be solved with a change over switch that disconnects Foccci from CP while AC charging.		Some chargers want to evaluate the CP (and perhaps PP) signal themselves. This issue can be solved with a change over switch that disconnects Foccci from CP while AC charging. Alternatively the CP signal can be spoofed and the charge current controlled by CAN to satisfy the limits of the AC outlet (EVSE).

	== Configuring Clara via CAN ==		== Configuring Clara via CAN ==

Johu: added integration information

2024-06-23T20:45:02Z

added integration information

@@ Line 8: / Line 8: @@
 [https://openinverter.org/forum/viewtopic.php?t=3727 Clara in the OpenInverterForum.]
 == Configuring Clara via CAN ==
@@ Line 252: / Line 282: @@
 |%
 |The PWM ratio of the CP line. This is normally 5% for DC chargers, and between 10% and 90% for analog AC chargers.
-Typical values are explained here: [[IEC 62196 Typ 2|IEC 62196 Typ 2 – Wikipedia]]
+Typical values are explained here: [https://de.wikipedia.org/wiki/IEC_62196_Typ_2 IEC 62196 Typ 2 – Wikipedia]
 |-
 |temp1, 2, 3
@@ Line 323: / Line 353: @@
 |-
 |CANTIMEOUT
-|The message mapped to canwatchdog hasn't been received for over 1s or nothing is mapped to canwatchdog
+|The ChargeCurrent hasn't been updated via CAN for more than 2s
 |-
 |PLCTIMEOUT

Johu: Added boostech BMS CAN mapping

2024-06-21T07:50:23Z

Added boostech BMS CAN mapping

← Older revision		Revision as of 07:50, 21 June 2024
Line 372:		Line 372:
	'''<u>Attention:</u>''' with this mapping the error flags are ignored, e.g. voltage or current mismatch.		'''<u>Attention:</u>''' with this mapping the error flags are ignored, e.g. voltage or current mismatch.
	<references />		<references />

			== Making Clara talk to boostech BMS ==
			[[File:Can mapping boostech.png\|thumb\|Can mapping boostech]]
			The boostech BMS has a fixed CAN mapping. It doesn't expect any feedback from the CCS controller so we just keep the CHAdeMO mapping from above in case the info is needed elsewhere in the car.

			The BMS sends out big endian messages hence why the length fields are negative. It does not send out a charge end voltage so we simply multiply the charge enable flag with the voltage we want. In the example 370V.

			''As of now this mapping is preliminary and has to be confirmed. will then remove this note''
	[[Category:ChaDeMo‏‎]]		[[Category:ChaDeMo‏‎]]
	[[Category:CCS]]		[[Category:CCS]]
	[[Category:Rapid Charging]]		[[Category:Rapid Charging]]
	__FORCETOC__		__FORCETOC__

Uhi22: parameter details for ppvariant

2024-06-14T06:18:38Z

parameter details for ppvariant

← Older revision		Revision as of 06:18, 14 June 2024
Line 89:		Line 89:
	\|9		\|9
	\|0		\|0
	\|Various circuit variations exist for PP resistor measurement. "1" is correct for the latest hardware		\|Various circuit variations exist for PP resistor measurement. "1" is correct for the latest hardware (Foccci 4.2 and above) Technically, ppvariant=1 is the correct setting for Foccci with the PP circuit with 330 ohm pull-up to 5V and a 3k pull-down and a 47k by 47k divider.
	\|-		\|-
	\|WakeupPinFunc		\|WakeupPinFunc

Uhi22: extended parameter descriptions regarding inlet voltage options

2024-06-14T06:15:42Z

extended parameter descriptions regarding inlet voltage options

← Older revision		Revision as of 06:15, 14 June 2024
Line 32:		Line 32:
	\|100		\|100
	\|10		\|10
	\|Division factor from ADC digits to V of external voltage measurement board		\|Division factor from ADC digits to V of external voltage measurement board.
			In other words: The UdcDivider is the configuration parameter which defines the scaling of the physical inlet voltage measurement circuit. That's why it is only relevant if a physical inlet voltage measurement circuit is present, and if the parameter InletVtgSrc is 1, means the Clara will measure the inlet voltage with the analog input. CAN mapping makes no sense for the UdcDivider, because it is a fix value. It is the ratio between the voltage on the inlet and the digital value on the AD converter.
	\|-		\|-
	\|EconomizerDuty		\|EconomizerDuty
Line 46:		Line 47:
	\|2		\|2
	\|0		\|0
	\|0 - Charger output voltage is considered equal to charge port inlet voltage		\|Inlet Voltage Source. There are three option where Clara gets the CCS inlet voltage from:
	1 - Analog input is used for measuring charge port inlet voltage		0 - Charger output voltage (EVSEPresentVoltage) is considered equal to charge port inlet voltage
			1 - Analog input U_IN_HV is used for measuring charge port inlet voltage

	2 - Charge port inlet voltage is provided via CAN - don't forget to map something to InletVoltage		2 - Charge port inlet voltage is provided via CAN - don't forget to map something to InletVoltage


			The InletVoltage is important for precharging, while the contactors are still open. The car (Foccci/Clara) will close the contactors, if the inlet voltage is near to the battery voltage. After closing the contactors, it is the battery voltage (besides some cable losses), and out of interest. The most straight forward solution to measure the inlet voltage is to rely on what the charging station tells us. It reports the voltage on the CCS plug in EVSEPresentVoltage. With configuring InletVtgSrc=0 we tell Clara to use the EVSEPresentVoltage. In this case, neither an analog inlet voltage measuring circuit nor a separate gadget which provides the inlet voltage via CAN is necessary. For most users this will be fine (even OEM cars use this approach).
	\|-		\|-
	\|LockDuty		\|LockDuty

Uhi22: More detailled description if the max values.

2024-05-20T21:24:33Z

More detailled description if the max values.

← Older revision		Revision as of 21:24, 20 May 2024
Line 116:		Line 116:
	\|1000		\|1000
	\|100		\|100
	\|Absolute maximum charge power		\|Absolute maximum charge power. Clara will announce this value in the ChargeParameterDiscoveryRequest message in the element EVMaximumPowerLimit. The charger may or may not respect this limitation.
	\|-		\|-
	\|MaxVoltage		\|MaxVoltage
Line 123:		Line 123:
	\|1000		\|1000
	\|410		\|410
	\|Over voltage threshold. Always set about 10-20V higher then desired battery full voltage		\|Over voltage threshold. Always set about 10-20V higher then desired battery full voltage. Clara will announce this value in the ChargeParameterDiscoveryRequest message to the charger, in the element EVMaximumVoltageLimit. The charger may or may not respect this limitation. Some chargers shut down, if this limit is reached. That's why it is recommended to set it some volts higher than the voltage which is used during normal charging.
	\|-		\|-
	\|MaxCurrent		\|MaxCurrent
Line 130:		Line 130:
	\|500		\|500
	\|125		\|125
	\|Absolute maximum charge current		\|Absolute maximum charge current. Clara will announce this value in the ChargeParameterDiscoveryRequest, in the element EVMaximumCurrentLimit. The charger may or may not respect this limitation.
	\|-		\|-
	\|TargetVoltage		\|TargetVoltage

Johu: /* Parameters */

2024-04-05T18:58:01Z

Parameters

← Older revision		Revision as of 18:58, 5 April 2024
Line 107:		Line 107:
	\|4		\|4
	\|2		\|2
	\|Baud rate of CAN interface 0=125k, 1=250k, 2=500k, 3=800k, 4=1M		\|Baud rate of CAN interface 0=125k, 1=250k, 2=500k, 3=800k, 4=1M - '''when configuring this != 500k you will loose communication to the ESP web interface!'''
	\|-		\|-
	\| colspan="6" \|'''Charge Parameters'''		\| colspan="6" \|'''Charge Parameters'''