Software version: 1.12.3 ======================== Date: 5.9.2019 Minimum version required for installation: 1.5.0 ### Charger Operations Bug fix: - Fixed: if LocalPreAuthorize was set to true and RFID card was only saved in cache, charger didn't recognize that card. As result it still sent Authorize request and wouldn't stop charging if there was no communication with center. ### Drivers Bug fix: - Fixed in AFE driver: problems with reading MID meter - Fixed in RFID/NFC driver: driver periodically stopped reading RFID card if user left the card close to antenna for a few minutes. Updated drivers in this release: - afe.dll 1.20 - nfc.dll 2.03 Removed driver micrel.dll (so that this release can work on motherboard version 1.02) Software version: 1.12.2 ======================== Date: 23.8.2019 Minimum version required for installation: 1.5.0 ### Charger Operations Bug fixes: - Fixed: OCPP RemoteStartTransaction was rejected - Fixed: OCPP StopTransaction was sent with Reason=Remote when transaction was started when charger was offline and stopped when changer got online and center rejected previously started transaction. This was changed to Reason=Deauthorized. - Fixed: Operations was not saving meter value immediately before shutdown, but only when value changed by a certain amount. ### Power Management Bug fixes: - Fixed: PowerManagement service set target current that was approximately 1A lower than desired due to rounding-down of measured maximum current for that vehicle. - Fixed: Null total energy consumption for display on web interface. ### ConnectorsController firmware ConnectorsController firmware version: 1.08 Bug fix: - ConnectorsController firmware detected wrong hardware version which could cause problems during installation. Software version: 1.12.1 ======================== Date: 9.8.2019 Minimum version required for installation: 1.5.0 ### Charger Operations Bug fixes: - Fixed: If charger had active TxProfile and charging was paused (target=0A), and then TxProfile was cleared usinga ClearChargingProfile, the charging didn't continue (target didn't get recalculated). - Fixed: In Plug & Charge mode charger sometimes still showed "Connect vehicle" screen even though charging has already started or asked the user if they wanted to stop charging. This happened when both S1 and S2 were present when the cable was plugged in charger. - Fixed: If only one authentication method was available, authentication screen was missing a "Back" button. - Fixed: If charger had a fixed cable and was in Plug & charge mode, it didn't allow to backup data. - Fixed: If touch registered two touches when user confirmed PIN, two authentications were started which could result in screen being stuck in “Authenticating…” even though central system has already denied authorization. - Fixed: If charger had a long uptime it was possible that it started rejecting authentications due to MaxAuthorizeCounter being reached. ### Web interface Bug fixes: - Fixed: Web UI didn't show GSM status correctly. ### Drivers Bug fix: - Fixed in AFE driver: In some chargers after a restart meter value became falsely high. - Fixed in GSM driver: Improved connectivity. Updated drivers in this release: - afe.dll 1.17 - gsm.dll 1.12 Software version: 1.11.4 ======================== Date: 26.6.2019 Minimum version required for installation: 1.5.0 ### Charger Operations Bug fixes: - Fixed: in some cases when GSM connection was lost it took too long to restart GSM modem. Now we restart it as soon as we cannot ping Network.Gsm.PingServerIP (which happens in intervals specified in Network.Gsm.PingInterval) as long as the modem says it's connected. ### Drivers Bug fix: - Fixed: Service button driver sometimes stopped responding to button being pressed. - Fixed: Gsm driver to allow for faster reconnect. Updated drivers in this release: - Gsm.dll: 1.07 - Rst.dll: 0.09 Software version: 1.11.3 ======================== Date: 6.6.2019 Minimum version required for installation: 1.5.0 ### Charger Operations Improvements: - If the charger is reserved and the IdTag sent in the OCPP RemoteStartTransaction message doesn’t match with Reservation Idtag, the charger will reject it. - If the charger is reserved it now notifies backend that reservation has ended only after reservation has expired or the user who reserved the charger has stopped charging (not at the beginning of charging as was the case before). - When OCPP RemoteStartTransaction is accepted by the charger, connector 1 will change status to Preparing. - Even when charger's GridConnection settings say that it's connected to a single phase, the charger now sends voltages on L2 and L3 in OCPP MeterValues. This is useful for chargers that have the single phase setting, but are actually connected on all three phases. - Added support for FTP firmware update. - Charging can now be stopped with RFID card that has the same parentTagId as the card that started charging. When stopping charging using RFID card the charger will send OCPP Authorize to center to obtain parentIdTag. - Mobile communication: Added pinging of address defined in Network.Gsm.PingServerIP and resetting GSM modem if it claims it's connected but that IP cannot be pinged. Bug fix: - Fixed: When charger was reserved, OCPP RemoteStartTransaction message didn't start charging. - Fixed: Sometimes when OCPP ChangeAvailability message was sent with Type=Inoperative, charger's LCD didn't change to Unavailable. - Fixed: When setting CustomMaxCurrent through OCPP ChangeConfiguration the charger returned RebootRequired, when it should have returned Accepted. - Fixed: Charger showed wrong screensaver ("charging paused") when it should be "in fault". - Fixed: Sometimes, when phase and neutral were switched, the charger didn't show an error on LCD like it should. - Fixed: Charger didn't send MID meter serial number in OCPP BootNotification. - Fixed: when charger was reserved, RemoteStartTransaction didn't start charging (charger showed "Authorization timed out"). ### Web interface Bug fix: - Fixed: When saving maximum currents for power management cluster, web UI showed that operation was successfully executed instead of asking for restart. - Fixed: When saving CustomMaxCurrent web UI showed that restart was required even though it's not required for this setting. - Fixed: Cluster power in graph was wrong. - Fixed: if charging was stopped due to overcurrent error, the web UI still showed current that the car was charging with at the time of error. Overcurrent error was not shown. ### Power Management Improvements: - Support 2 phase vehicles in power cluster - Added smoothing of reported currents and power. - Better handling of suspended connectors (where vehicle fully charged). Bug fix: - Fixed: Power Management sometimes crashed after firmware upgrade. - Fixed: Instant PowerManagement sometimes reacted too quickly to changes in the cluster resulting in oscillations. Instant update now runs every 2 seconds. - Fixed: Calculation of sum of currents and power. - Fixed: Power management based on price optimization now working properly. - Fixed: Pattern learning for departure time prediction wasn't working (it kept offering default departure time instead of learned departure time). Software version: 1.10.0, Language update ========================================= Date: 15.4.2019 Package name: 1.10.0_3 Two languages got updated: Croatian and Hungarian. Software version: 1.10.0, Driver update ======================================= Date: 18.3.2019 Package name: 1.10.0_2 ### Drivers Afe.dll was updated to 1.13. This fixes random RegisterEvents failure. Software version: 1.10.0 ======================== Date: 15.3.2019 Minimum version required for installation: 1.5.0 ### Charger Operations - Operations settings version changed to 7 -- AuthorizationSettings: added setting SupportContact. Support contact is displayed on LCD help screens. -- CentralSystemCommunicationSettings: added setting VendorMessages (array). This enables some customization at sending specific DataTransfer messages. Contact Etrel if you require such customization. -- CentralSystemCommunicationSettings: added setting to the Client: AuthorizationKey. This enables security through OCPP JSON protocol. -- DalSettings: added setting MaxPowerSamples. -- EvsesSettings: removed setting EnforceMaxCurrentLimit, added SWOvercurrentProtectionEnabled and Overcurrent (array of settings). You can now define SW overcurrent protection limits. This protection would stop session before fuse would trip. But SW protection is not protecting against short circuits. -- TimeSettings: added setting TimeServers. Defines NTP servers against which charger can synchronize time if not connected to the central system. - OCPP 1.6 SetChargingProfile: if ChargingRateUnit = W, current is now recalculated periodically throughout charging (using actual measured voltage). - Added support for OCPP 1.6 CancelReservation and ReserveNow. - Added SSL support for OCPP 1.6 SOAP: Charger can communicate with center over HTTPS and it can be configured to host its OCPP endpoint over HTTPS. - OCPP 1.6 GetConfiguration now returns values of Etrel-specific keys (if they are specified in request). - Faster boot-up for chargers with WiFi module. - Disabled Gsm modem driver when Gsm modem isn't installed. - Software overcurrent protection: in case that vehicle is consuming significantly more current than charger allows, this will stop charging. Default settings: in case of 120% overload, stop charging after 1000s. In case of 130% overload, stop charging after 100s. In case of 180% overload, stop charging after 10s. By default this is disabled, but can be enabled through web UI. - Faster generation of GeneralStatus for web UI (by caching of WiFi results). - Help screen shows contact information from setting AuthorizationSettings.SupportContact so it doesn't have to be a part of translations anymore. - URL for downloading charging app and/or registering a new user is also configurable through AuthorizationSettings.Login.AppDownloadUrl so it doesn't have to be a part of translations anymore. This link is used on authorization help screens. - Enabled setting a custom NTP server (setting TimeServers). - CLIENT 43 SPECIFIC: Implemented DataTransfer messages TxEnergyLimit, TxEnergyLimitReached and ChargeComplete. - CLIENT 43 SPECIFIC: Events on connector 0 are now sent as DataTransfer if VendorMessages setting contains CLIENT 43. - Meter serial number is now being sent in BootNotification (if available). - Better error message when charger is configured as three-phase, but connected only on one phase. - When firmware is updated using web UI, charger becomes Unavailable until firmware update is complete. (This was already true for firmware updates started via OCPP.) Bug fix: - Fixed: When communicating over GSM, reported connection status after a hard reset was Connection Failed even when GSM was connected. - Fixed: If connectors controler is in the middle of firmware update while operations starts and immediately suspends OS (before update was completed), the update fails and restarts after restart. - Fixed: Charger allowed two firmware updates to be started at the same time from web UI. Charger will now ignore the second firmware update in order to allow the first one to complete. - Fixed: Saving power measurements in database so archive load diagram can be shown. - Fixed: GeneralStatus was showing that not all power cluster slaves were connected even though power cluster status showed all were online. - Fixed: Sometimes IMSI and ICCID fields of BootNotification remained empty even though GSM modem was connected to the network. - Fixed: On SMS authentication screen, the QR code was different from displayed SMS text. - Fixed: Charger's WiFi access point was published among other networks. Now its SSID is hidden. - Fixed: When AFE RegisterEvents failed, operations crashed. Now it will continue working, but charger will be in Faulted state. ### Web interface - If only one web administrator is registered, don't allow deletion, blocking or degrading the role of this user. - Enforce unique usernames for web UI users. - Web session length is now 1 day (after user logs in they will remain logged in for 1 day). - Added software overcurrent protection settings. - Optimized web UI load times through file minimization. - In Power management dashboard: added horizontal lines to denote building power and cluster power. - Showing additional information for charging sessions that were started remotely. - Disable HTTPS hosting if charger doesn't have its hosting certificate (so that administrator can still connect via HTTP and correct the matter). Bug fix: - Fixed: Saving energy price (tariff) information and deleting unsaved tariff. - Fixed: Power management energy consumption graph was empty. - Fixed: Drop down boxes with numbers were cramped (Configuration\Local users and Configuration\Charger configuration\Web interface access). - Fixed: Number of identifications (in User\Local users) never went down, even when identification was deleted. - Fixed: Power Profile was missing Connector profile data. - Fixed: In Reporting\Authorizations the users got deleted if filtered by user. - Fixed: Showing wrong power of chargers in a cluster. - Fixed: It was possible to enter same RFID card for two local users. - Fixed: When enabling WiFi a never-ending "Please wait searching" was displayed. - Fixed: When switching between WiFi networks, a never-ending "Please wait while connecting" was displayed. - Fixed: In reports, Clear filter sometimes didn't work. - Fixed: Some of the icons in the upper right corner disappeared after reloading the page in browser. - Fixed: If GSM modem is enabled, rebooting the charger via web UI sometimes caused charger get stuck with operations not running (most likely it didn't restart at all). - Fixed: Some PowerManagement settings were not obfuscated (if they included more than one version). - Fixed: Some of the filters in reports didn't work. - Fixed: Gsm connection status was always "Connection failed". - Fixed: WiFi could not conect to an open network (without passphrase). - Fixed: Restore Configuration wasn't working. ### Power Management Bug fix: - Fixed: saving power measurements in database. - Fixed: charging was limited to 15A. - Fixed: PM was cyclically pausing charging on the charger. - Fixed: PM was not respecting cluster current limit. ### Service Window Bug fix: - Fixed: rebooting charger from service window took 6 minutes. ### Drivers Versions of drivers included in this release: - Afe.dll: 1.12 - Backlight.dll: 0.13 - Buzzer.dll: 0.12 - Gsm.dll: 1.00 - Iec.dll: 0.26 - Light.dll: 0.10 - Logger.dll: 1.00 - Nfc.dll: 1.04 - Plc.dll: 0.12 - Rst.dll: 0.08 - Touch_st1633i.dll: 0.02 ConnectorsController firmware version: 1.02