From f1de5b6c5b43c5195c39e05e9b3259582cce1d8f Mon Sep 17 00:00:00 2001 From: Dmitriy Lyubimov Date: Fri, 21 Jul 2017 14:30:04 -0700 Subject: [PATCH] Release notes. --- Hydra_EVSE/Hydra_EVSE.h | 2 +- Hydra_EVSE/ReleaseNotes.md | 95 ++++++++++++++++++++++++-------------- 2 files changed, 62 insertions(+), 35 deletions(-) diff --git a/Hydra_EVSE/Hydra_EVSE.h b/Hydra_EVSE/Hydra_EVSE.h index 0dc87fb..659cef2 100644 --- a/Hydra_EVSE/Hydra_EVSE.h +++ b/Hydra_EVSE/Hydra_EVSE.h @@ -157,7 +157,7 @@ // delay per event. (UL 2231). This MUST BE bigger than ERROR_DELAY (power on high pilot withdrawal), //#define GFI_CLEAR_MS (15 * 60 * 1000) // debug -#define GFI_CLEAR_MS (60 * 1000) +//#define GFI_CLEAR_MS (60 * 1000) #define GFI_CLEAR_ATTEMPTS 4 diff --git a/Hydra_EVSE/ReleaseNotes.md b/Hydra_EVSE/ReleaseNotes.md index 606f737..2796f4d 100644 --- a/Hydra_EVSE/ReleaseNotes.md +++ b/Hydra_EVSE/ReleaseNotes.md @@ -1,3 +1,64 @@ +Hydra EVSE version 2.4.1 +======================== + +* WARNING: EEPROM format is incompatible with previous releases, this release will +reset all the eeprom settings + +* A lot of redundant code and constants eliminated +** display duplication +** symmetrical code duplication +** timezone library is gone. Funcationality rewritten in more compact way +** prodcution removes serial logging and its related strings completely + +* eprom persitence and validation: +** save/load via one operation as the whole struct +** added eeprom "magic" signature to validation logic + +* exponentially weighed average online symmarizer with irregular sampling to smooth out the current displays + (display only; internal analytic is seeing original raw values) + +* experimental: flearn and apply RTC calibration with a fast convergent model with embedded Bayesian treatment + +* experimental: up to 4 attemtps to restart EVSE charging after a GFI fault separated by 15 minute pause + + + + +Hydra EVSE version 2.4.0 +======================== + +2.4.0 adds manual calibration to the ammeters and the pilot. + +Problem statement: +------------------ + +My Spark EV is not a very good citizen (but my other car is, it underdraws diligently by 0.5A or so!). +When being asked to draw a restricted amperage, my Spark EV yet may overdraw by about 5%. This normally is not a problem +per se, since both residential single plug or commercial dual plug chargers have plenty of power to cover well above +its maximum 3.3 kw chargin rate (~13.5A or so). + +However, I have a 30A line which means total available amperage for an EVSE is no more than 24A, or 12A per plug in +the shared Hydra mode when two cars are plugged at the same time. So Spark finds itself under the limit of 12A, +which it doesn't observe well. +In addition, the ammeter readings vary by about 0.2A so it appears that Spark is overdrawing even more than on the other. Add to that some metering and draw variation, and Spark ends up throws error O (overdraw) from time to time in the shared mode on my line A (but not on B, on which it overdraws too, just slightly less due to ammeter reading variation). + +Hydra processes overdraw error if the draw was exceeded by 1A or more for at least 5 seconds (IIRC). +So in an unlikely event that two lines are overdrawing at the same time and exactly by that extreme amount, it would actually mean the draw may go up to 26A with configured 24A capacity before Hydra would error both out. That's why it +is important to derate Hydra EVSE configuration compared to the breaker amperage. + +So the desired fixes are as follows: + +* adjust ammeter natural variations manually by setting draw current adjustmetns of -0.5A to +0.5A in 0.1A increments; + +* adjust additional amperage derate in allowed pilot amperage per line (between 0% and -10%, in 1% decrements). So, +for example, if the half power in shared mode is 12A, then 9.8A will be actually restricted by the pilot while still allowing it to grow up to 12A half power +1A existing Hydra slack = 13A without throwing an overdraw error. This is +actually done per line, not per actual car, assuming problematically overdawing car would be using the same line consistently. + +Important: +---------- + +When flashing firmware 2.4.0 for the first time over previous versions **without erasing the EEPROM** make sure to check calibration menu settings to show all 0s after the first flash. + Hydra EVSE version 2.3.5 ======================== @@ -44,37 +105,3 @@ do initiate charging sessions even after having been fully charged. * Firmware version is tracked separately from the hardware version. Current hardware release is stil 2.3.1 (as found on the EVSE logic board) and is tested again such. Both versions are shown at the startup. -Hydra EVSE version 2.4.0 -======================== - -2.4.0 adds manual calibration to the ammeters and the pilot. - -Problem statement: ------------------- - -My Spark EV is not a very good citizen (but my other car is, it underdraws diligently by 0.5A or so!). -When being asked to draw a restricted amperage, my Spark EV yet may overdraw by about 5%. This normally is not a problem -per se, since both residential single plug or commercial dual plug chargers have plenty of power to cover well above -its maximum 3.3 kw chargin rate (~13.5A or so). - -However, I have a 30A line which means total available amperage for an EVSE is no more than 24A, or 12A per plug in -the shared Hydra mode when two cars are plugged at the same time. So Spark finds itself under the limit of 12A, -which it doesn't observe well. -In addition, the ammeter readings vary by about 0.2A so it appears that Spark is overdrawing even more than on the other. Add to that some metering and draw variation, and Spark ends up throws error O (overdraw) from time to time in the shared mode on my line A (but not on B, on which it overdraws too, just slightly less due to ammeter reading variation). - -Hydra processes overdraw error if the draw was exceeded by 1A or more for at least 5 seconds (IIRC). -So in an unlikely event that two lines are overdrawing at the same time and exactly by that extreme amount, it would actually mean the draw may go up to 26A with configured 24A capacity before Hydra would error both out. That's why it -is important to derate Hydra EVSE configuration compared to the breaker amperage. - -So the desired fixes are as follows: - -* adjust ammeter natural variations manually by setting draw current adjustmetns of -0.5A to +0.5A in 0.1A increments; - -* adjust additional amperage derate in allowed pilot amperage per line (between 0% and -10%, in 1% decrements). So, -for example, if the half power in shared mode is 12A, then 9.8A will be actually restricted by the pilot while still allowing it to grow up to 12A half power +1A existing Hydra slack = 13A without throwing an overdraw error. This is -actually done per line, not per actual car, assuming problematically overdawing car would be using the same line consistently. - -Important: ----------- - -When flashing firmware 2.4.0 for the first time over previous versions **without erasing the EEPROM** make sure to check calibration menu settings to show all 0s after the first flash.