CCS32Clara: Difference between revisions

From openinverter.org wiki
Jump to navigation Jump to search
(added some spot value descriptions)
(DEAD)
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Disclaimer: This Page is still work in progress!  Any information written here is a draft only and should be handled as such.  Contributions are more than welcome.  If you have questions, please ask them in the discussion section of the page or in the OpenInverter Forum.
The information on this page has been transferred to [[Fully Open CCS Charge Controller (FOCCCI)]]


This page is about the reference software for the [[Fully Open CCS Charge Controller (FOCCCI)|Fully OpenSource CCS Charge Controller (Foccci)]].  CCS32Clara (also referred to as "Clara") is currently under development by the OpenInverter Community.
Here you will find documentation (or reference) on how to setup Clara, News on the development, diagrams, open ToDos, etc.
[https://github.com/uhi22/ccs32clara Clara on GitHub.]
[https://openinverter.org/forum/viewtopic.php?t=3727 Clara in the OpenInverterForum.]
==Parameters==
{| class="wikitable"
|'''Name'''
|'''Unit'''
|'''Min'''
|'''Max'''
|'''Default'''
|'''Description'''
|-
| colspan="6" |'''Hardware Config'''
|-
|udcdivider
|dig/V
|0
|100
|10
|Division factor from ADC digits to V of external voltage measurement board
|-
|economizer
|%
|0
|100
|100
|Contactor economizer duty cycle. Contactors are always turned on with 12V for 1s then drop to this value. Set to 100% if your contactor has a built-in economizer
|-
|inletvtgsrc
|
|0
|2
|0
|0 - Charger output voltage is considered equal to charge port inlet voltage
1 - Analog input is used for measuring charge port inlet voltage
2 - Charge port inlet voltage is provided via CAN - don't forget to map something to inletvtg
|-
|lockpwm
|%
| -100
|100
|30
|H-bridge duty cycle for operating the lock. Use negative value if lock polarity is swapped
|-
|lockopentm
|ms
|0
|10000
|1000
|Timeout for lock operation
|-
|lockclosethr
|dig
|0
|4095
|0
|Lock feedback value for closed
|-
|lockopenthr
|dig
|0
|4095
|0
|Lock feedback value for open - if equal to lockclosethr no feedback is assumed and lock is operated timed
|-
| colspan="6" |'''Communication'''
|-
|nodeid
|
|1
|63
|22
|CANOpen node id for SDO requests
|-
|canspeed
|
|0
|4
|2
|Baud rate of CAN interface 0=125k, 1=250k, 2=500k, 3=800k, 4=1M
|-
| colspan="6" |'''Charge Parameters'''
|-
|maxpower
|kW
|0
|1000
|100
|Absolute maximum charge power
|-
|maxvtg
|V
|0
|1000
|410
|Over voltage threshold. Always set about 10-20V higher then desired battery full voltage
|-
|maxcur
|A
|0
|500
|125
|Absolute maximum charge current
|-
|demovtg
|V
|0
|500
|0
|Voltage for light bulb demo. To use the board without CAN, to get an constant voltage. Is ignored as long democtrl is not STANDALONE. Only values between 150V and 250V are accepted, others are treated as zero.
|-
|demomode
|
|0
|511
|0
|Enables the standalone demo mode if value is set to STANDALONE. In this mode, no CAN is required and the target voltages for precharge and charging loop are taken from demovtg.
|-
|targetvtg
|V
|0
|1000
|0
|Charge target voltage (volatile)
|-
|chargecur
|A
|0
|500
|0
|Instantaneous current setpoint (volatile)
|-
|soc
|%
|0
|100
|0
|Battery SoC for display on charger (volatile)
|-
|batvtg
|V
|0
|1000
|0
|Present battery voltage for precharge state (volatile)
|-
|enable
|
|0
|1
|1
|When 0 charging is stopped/not started (volatile)
|-
| colspan="6" |'''Testing'''
|-
|locktest
|
|
|
|
|Actuates the lock
|-
|wd_disable
|
|
|
|
|Disabled the CAN timeout detection
|-
|logging
|
|
|
|
|Selects which modules log to the serial console
|}
== Spot values ==
{| class="wikitable"
|+
!Name
!Unit
!
!Description
|-
|opmode
|
|
|
|-
|version
|
|
|
|-
|lasterr
|
|
|
|-
|evsevtg
|
|
|
|-
|evsecurr
|
|
|
|-
|inletvtg
|
|
|
|-
|evsemaxcur
|
|
|
|-
|evsemaxvtg
|
|
|
|-
|evsecp
|%
|
|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]]
|-
|temp1, 2, 3
|°C
|
|Temperatures of the temperature sensors. Requires correct calibration values depending on the used NTC types.
|-
|dcsw1dc
|
|
|
|-
|lockfb
|
|
|
|-
|adcProximityPilot
|digit
|
|Analog value of the PP line. This is the raw value of the analog-to-digital-converter in range 0 to 4095.
|-
|resistanceProximityPilot
|ohm
|
|Measured resistance between PP line and ground. Requires correct setting of the parameter ppvariant.
|-
|cableCurrentLimit
|A
|
|Based on the PP resistance. The current limit of the charging cable for AC charging.
|-
|evseCurrentLimit
|A
|
|Based on the CP PWM. The current limit of the charging station for AC charging.
|-
|adcHwVariant
|digit
|
|raw AD value of the hardware variant coding input. Used to detect which variant of Foccci the software runs on.
|-
|adcIpropi
|digit
|
|raw AD value of the current sensor for the charge port lock motor driver.
|-
|lockstt
|
|
|
|-
|stopreason
|
|
|
|-
|checkpoint
|
|
|
|-
|canwatchdog
|
|
|
|-
|cpuloadCPU
|
|
|
|}
==Errors==
The spot value "lasterr" displays the last detected error that lead to a cancellation of charging or to not starting in the first place
{| class="wikitable"
|+
!Error
!Description
|-
|CANTIMEOUT
|The message mapped to canwatchdog hasn't been received for over 1s or nothing is mapped to canwatchdog
|-
|PLCTIMEOUT
|PLC communication with charger timed out
|-
|PRECTIMEOUT
|Precharging the EVSE output to specified voltage timed out or battery voltage is below minimum EVSE output voltage
|-
|LOCKTIMEOUT
|The connector lock didn't reach the desired position in time
|-
|EVSEFAULT
|The EVSE reported an error and stopped
|-
|RELAYWELDED
|A welded charge port relay was detected
|}
==Making Clara talk CHAdeMO on the CAN side==
A pretty straightforward way to integrate CCS charging into your vehicle is to use the existing CHAdeMO (let's call it CDM from here on) CAN messaging. CDM has pretty much all data items we need to initiate a CCS charging session, so rather than defining a new set of messages we might as well adopt it. For example, Orion BMS or Zombieverter VCU natively support CHAdeMO anyway.
[[File:Can mapping chademo.png|thumb|Screenshot of CAN mapping to interface Clara CCS with CHAdeMO]]
Let's go over the items in the screenshot one by one. Note that the IDs are decimal! (256=0x100, 258=0x102, 264=0x108, 265=0x109)
*'''udcdivider''' - Actually, here we just select some dummy item as the important bit is in the Offset field: the version. In this case I signal non-existent CDM version 10. This tells the CDM module in my car that it talks to Clara. It then includes the battery voltage in some unused message bytes - see below.
*'''evsevtg''' - Transmits the charger's present output voltage back to the vehicle.
*'''evsecur''' - Transmits the charger's present output current back to the vehicle.
*'''opmode''' - Observe the weird gain - this is forged to map Clara state "CurrentDemand (13)" to CDM state "ConnectorLocked (4)". In my car's CDM module this is sufficient to initiate the charging progress. You may need to change it so that the ChargeEnable flag together with ConnectorLocked is forged (numerical value 5).
*'''evsemaxvtg''' - Transmits the EVSE's maximum output voltage back to the vehicle.
*'''evsemaxcur''' - Transmits the EVSE's maximum output current back to the vehicle.
*'''batvtg''' - Transmits the present battery voltage to the EVSE.  This is the special item that normally doesn't exist in CDM and that unfortunately will prevent you from using this solution with an OEM car in a safe manner. Of course, you could manually set this to some medium battery voltage like 360V, but if you arrive with a really low battery at, say, 300V this might weld your charge port contactors.  You could also manually enter the battery voltage before each charging session.
*'''targetvtg''' - Transmits the charge end voltage to the EVSE.
*'''chargecur''' - By far the most important data item: the charge current request.
*'''soc''' - In CDM this isn't normally a percentage value but some encoded kWh value.  In my car's CDM module I specify a full battery as "200" (no idea what this actually means in kWh) and thereby can just output the SoC in 0.5% steps.
*'''enable''' - The car's charge enable flag.  When 0 will stop the CCS session.
*'''canwatchdog''' - (missing in screenshot). Map to 0x102 message at some arbitrary bits with gain=0 so it sets canwatchdog=0 whenever it is received. This makes sure charging stops if the CAN bus is disturbed.
As an additional safety measure you could connect CDM pin 4 (charge enable) to Clara's button input (at least once we added an active low mode for it).  It might also be worthwhile to connect pin 7 (connection check) to the PP input for drive away protection when CDM is plugged in but not charging (again, once we have actually implemented this).
Let's list the CHAdeMO pin mapping one by one as well:
*Pin 1 - GND
*Pin 2 (12V, charger start/stop) - 12V (I take it from cigarette lighter)
*Pin 4 (charging enable) - Foccci BUTTON
*Pin 5, 6 - Power pins, triple check correct polarity!
*Pin 7 (Connection check) - Foccci PP
*Pin 8, 9 (CAN) - Foccci CANL, CANH
*Pin 10 (charger start/stop 2) - Foccci SW1_LS
'''<u>Attention:</u>''' with this mapping the error flags are ignored, e.g. voltage or current mismatch.
[[Category:ChaDeMo‏‎]]
[[Category:CCS]]
[[Category:Rapid Charging]]
__FORCETOC__
__FORCETOC__
[[Category:DEAD]]

Latest revision as of 17:48, 20 December 2024

The information on this page has been transferred to Fully Open CCS Charge Controller (FOCCCI)

Retrieved from "https://openinverter.org/wiki/index.php?title=CCS32Clara&oldid=5396"