================ in-tech smart charging Charge Control C ======================= ================ Firmware Release Notes ======================= ================================================================================ Release Date: 2021-01-25 Release Maturity: Beta Release Version: 0.9.0 Important notes for this firmware update: - Before performing the firmware update, make sure that the firmware version is at least 0.4.0 and all data in /opt has been backed up. The whole directory will be removed! - During the firmware update, the currently installed /etc/secc/customer.json will be preserved; a pristine, factory default configuration file is contained in the firmware update and will be available as /etc/secc/customer.json.shipped after the firmware update. Changes since ChargeControl-C-0.8.0 (2020-09-22): Kernel - QCA7000 SPI driver counts bad signature events in the ethtool stats - QCA7000 SPI driver tries to avoid delays caused by signature glitches Operating system - Network - The mains powerline interface is now created with an increased route metric. Thus a wired Ethernet connection is prefered in case both connections are configured and operational. - The bridge forward delay between wired Ethernet and connected USB devices was reduced to speedup access to the device after reboot and/or network cable insertion. - Root FS - update to RAUC v1.5 - use full-featured "ip" command instead of stripped busybox's applet Charging Stack - slacd - general rework of SLAC communication (improved reliability) - avoid SLAC errors in case of fast EV reconnects - iec61851d - signalize 100% duty cycle during QCA7000 reset for highlevel charging - log static current limits at start - check actual ventilation state in case EV requests CP state D before closing the contactor - availability of a connector depends now on two MQTT topics (OCPP and customer interface) - publish the actual availability of a connector to a new topic - iso15118d - fix assert regarding JSON handling - improve simple AC mode - meteringd - add support for Phoenix Contact EEM-350-D-MCB meter - suppress connection errors for expected connectivity loss on Klefr meter - recloserd - improve Modbus request handling to avoid collisions - rgbledd - adapt to new availability topics - updated - allow TLS upgrade for downloads via FTP (implicit TLS connectivity) - ventilationd - allow customer to control ventilation relay via MQTT topics - watchdogd - provide more information in case of a watchdog reset (memory usage, daemon or MQTT broker status) - OCPP - support HTTP(S) upload for GetDiagnostics - improve memory, UART and mains PLC info in GetDiagnostics - ChangeAvailability while Charging is now scheduled properly - StatusNotification caused by ChangeAvailability is now handled properly - fix delay before switching contactor in case of broken OCPP connection - improve compatibility of GetConfiguration - fix runtime issue during tar generation for GetDiagnostics (move local0.log into commands) - fix GetDiagnostics for FTP with implicit TLS connectivity - incomplete CSMS request will be replied with a CallError Not fixed: - occasional unexpected green LED blinking - Modbus scan wrongly detects DZG meter instead of ignoring different Modbus device - firmware downgrade from Yocto to Debian image can cause out-of-memory errors - CP state E during charging is reported as EVDisconnected - ChangeConfiguration without change to the actual value results in "RebootRequired" - in rare offline situations there could be a maximum delay of 60 seconds between start of transaction and power delivery Technical Preview The charging stack now supports the combination of "free charging" and OCPP support with some limitations. Only the following OCPP commands are expected to work: - BootNotification - HeartBeat - ChangeAvailability - ChangeConfiguration - ClearCache - ClearChargingProfile - DataTransfer - GetConfiguration - GetDiagnostics - GetLocalListVersion - Reset - SendLocalList - SetChargingProfile - UnlockConnector - UpdateFirmware Please note that technical previews are released to customers with the following disclaimer: - There is no guarantee that these features are well tested or work at all. - Only very limited technical support is given for such features. - There is no guarantee that these features will remain part of later firmwares. - However, such features are considered safe enough to not disturb/influence the normal/guaranteed functionality of the charging stack.