Software version: 1.13.7 ======================== Date: 24.02.2020 ### Charger Operations - support modifications in ConnectorsController ### Drivers ConnectorsController firmware version: 2.15 - support hardware version 0.95 Software version: 1.13.6 ======================== Date: 07.12.2020 ### ServiceWindow - minor modifications in ServiceWindow GUI Software version: 1.13.5 ======================== Date: 30.11.2020 Minimum version required for installation: 1.5.0 ### Charger Operations - do not send Authorize prior to StopTransaction - fix secure sockets communication to backend (wss) ConnectorsController firmware version: 2.13 - fixed a problem when vehicle pauses within first 5s after start charging Software version: 1.13.4 ======================== Date: 26.10.2020 Minimum version required for installation: 1.5.0 ### Charger Operations - updated translations, added Portuguese-Brazil (pt-BR) language - ChargingProfile fixes ### Power Management - Load Guard functionality supported also via Algodue UPM209 and UEM80-4D MIDs Updated drivers in this release: ConnectorsController firmware version: 2.12 - fixed a problem when vehicle pauses charging immediately after start Software version: 1.13.3 ======================== Date: 24.8.2020 Minimum version required for installation: 1.5.0 ### Charger Operations - Fixed: ConnectionWithCentralSystemRestored was sent to backend as Error, now it's sent as Info. - Fixed: OCPP RemoteStartTransaction: charger accepted empty JSON request. Now it rejects it. - Fixed: OCPP RemoteStartTransaction: when AuthorizeRemoteTx was set to true, Authorization timed out and remote start was rejected. - Fixed: OCPP UnlockConnector didn't stop charging, now it does. This is only applicable to chargers without a permanent charging cable. For chargers with a cable it now returns NotSupported and doesn't stop the charging. - Fixed: websocket ping was not working. - Fixed: problem with charging profiles that resulted in skipping some periods. Updated drivers in this release: ConnectorsController firmware version: 2.11 - fixed a problem with Tesla vehicles Software version: 1.13.2 ======================== Date: 27.5.2020 Minimum version required for installation: 1.5.0 ### Charger Operations - modified language files - Fixed: OCPP GetCompositeSchedule over websockets now returns schedule (in previous versions it returned NotImplemented) Software version: 1.13.1 ======================== Date: 2.4.2020 Minimum version required for installation: 1.5.0 ### Charger Operations - modified language files - ssl client certificate added to charging station Software version: 1.13.0 ======================== Date: 18.3.2020 Minimum version required for installation: 1.5.0 ### Charger Operations - Operations database version changed to 8. Bug fixes: - Fixed: charging station with fixed cable was sending state Preparing, when in Plug&Charge mode and no EV connected. - Fixed: charging station was rejecting sessions if authorisation was set to ChargerWhitelistOnly. - Fixed: in case of power loss the station now sets StopTransaction time correctly. - Fixed: if connection with LoadGuard is lost, then max charging current will be minimum of Max cluster currents and Max charging currents when communication with Load Guard fails. - Fixed: WiFi TKIP encryption is now supported. - Fixed: UploadFailed message was not sent if ftp address was incorrect. - Fixed: if the charging started offline and later on the connection to central system was restored, the station didn't send StopTransaction. - Fixed: charging never finished, if EV and EVSE were pausing during charging. - Fixed: serial number and model lengths in Modbus TCP (station) are now set to 20. New Modbus addresses are now 990 for serial number and 1000 for model. - Fixed: Modbus TCP 'Charger Restart' Command (Register address 1004) now works correctly. - Fixed: charging station didn't obey max building and cluster limit settings. - Fixed: Restore configuration now restores also Powermanagement settings. - Fixed: MaxChargingSessions is now 5000 (if it was 100 before). - Fixed: SystemInformation now returns correct hardware version. - Fixed: Modbus TCP registers of the station can now be read also via WiFi. - Fixed: GSM modem configuration parameter 'Ping server' can now support also server name. - Fixed: max EVSE current can be set higher (during session) than initial max current (discovered at start of session). - Fixed: some station Modbus TCP registers were not erased after charging session ended. This is now corrected. - Fixed: authorisation now does not expire if charger is waiting for S2 (CarReady) signal. New features: - configurable digital inputs are now supported, currently: DecreaseChargingPower, ParkingOccupied. - in case of RFID or App authentication, the station first disconnects power from the vehicle and then unlocks connector. - if ContactorWelding event occurs, RCD will be switched off ### Web interface Bug fixes: - Fixed: updated error message, when custom GUI configuration is not available. New message: "Provided custom configuration does not exist. ..." - Fixed: there was wrong message in dashboard, when charging was paused. - Fixed: some translations are corrected. - Fixed: WebUI now shows number of phases during charging. - Fixed: Power cluster status and Dashboard were showing different targets. - Fixed: export to csv was in some cases not working. - Fixed: Version/model year dropdown is now not empty for Home charger used by single user. - Fixed: charger time is now correctly shown in WebUI. - Fixed: select/deselect clock aligned meter value types in WebUI now works correctly. - Fixed: Custom wakeup logo can now be removed. - Fixed: when LoadGuard is enabled, Powermanagement will be enabled automatically. - Fixed: if date and time is set via Modbus TCP WebUI now shows time correctly. - Fixed: WebUI now contains checkbox to select SSL communication. The station has to be rebooted, if modified. - Fixed: authorisation order can now be modified from WebUI. New features: - when user selects Central System or Charger Whitelist and Central System, but connection to central system is not enabled, a warning is shown in WebUI. - when user selects Local users only authentication, a warning not to forget to insert local users or to upload white list from central system is shown. - when user modifies IP address an additional warning is shown in WebUI. - additional message in WebUI, when user modifies Protocol type for communication to backend - during Restore from WebUI an additional warning that connection to WebUI can be lost if IP of station is different from the one in backup, is shown ### Power Management - Powermanagement settings version changed to 6. Bug fixes: - Fixed: Modbus TCP registers for Power cluster now contain correct values - Fixed: Powermanagement master and slave communication is now supported also over WiFi Features: - INCH Home cluster supports only 2 chargers, INCH Pro cluster can contain Pro and Home cluster nodes - LoadGuard can now be replaced with a counter connected via Modbus-TCP protocol - charging current is now shown in Dashboard ### Drivers New features: - Redesign of ConnectorsController firmware. Bug fixes: - Fixed: short power loss sometimes caused AFE to read wrong measurements. Fixed AFE and Reset driver. - Fixed: touchscreen occassionally reported incorrect coordinates Versions of drivers included in this release: - Afe.dll: 1.23 - Backlight.dll: 0.13 - Buzzer.dll: 0.12 - Gsm.dll: 1.15 - Iec.dll: 1.02 - Light.dll: 0.10 - Logger.dll: 1.01 - Nfc.dll: 2.06 - Plc.dll: 0.12 - Rst.dll: 0.10 - Touch_st1633i.dll: 0.3 ConnectorsController firmware version: 2.06 Software version: 1.12.6 ======================== Date: 4.12.2019 Minimum version required for installation: 1.5.0 IMPORTANT: a physical reset may be required after upgrade! ### Charger Operations Bug fixes: - Fixed: RFID tag bytes were not being swapped (little endian) even though the setting SwapBytes was set to true. - Fixed: DataTransfer TxEnergyLimit was sometimes rejected due to DataTransfer arriving before charger point received transaction id for the session that just started. - Fixed: When charger was in status Finishing it didn't wait for user to unplug the cable before moving on to Available, but moved to Available on its own after a few seconds. - Fixed: "Error during initialization" on LCD screen due to charger not being able to communicate with energy meter. Charger will now try to establish communication every 5 minutes, so LCD could still show that error screen, but it will disappear as soon as communication is established. At this point main software will restart itself and there will be another BootNotification in center. StatusNotification with GeneralError stating "Energy meter setup failure" is still sent whenever charger cannot communicate with energy meter on bootup. - Fixed: OCPP StartTransaction included wrong ReservationId. - Fixed: When charger entered state Faulted or Unavailable, reservations weren't cleared. Changes: - When charger restarted itself due to failure to communicate with senter it changed status to Faulted. This has been changed so that charger remains in whatever status it had before restart. - When charger detects that GSM modem's IP has changed, it sends a StatusNotification with Info "GSM IP changed to...". ### Web interface Bug fix: - Fixed: By turning UseSsl (for charger's OCPP SOAP server) on and off it was possible to set charger server's port permanently to 443. Fixed so that it changes together with UseSsl setting. - Fixed: If power management is turned off there are two errors when saving time and regional settings. ### Drivers Bug fixes: - Fixed GSM driver: baudrate was not saved, after modem reboot default baudrate was used. Updated drivers in this release: - gsm.dll 1.15 Software version: 1.12.5 ======================== Date: 28.10.2019 Minimum version required for installation: 1.5.0 ### Charger Operations Bug fix: - Fixed: StatusNotification messages were being sent out of order on power loss even if ObeyOcppNotificationRules was set to true. ### Drivers Bug fixes: - Fixed in IEC and GSM driver: driver's internal problems sometimes resulted in problems with loading AFE driver which resulted in inability to read AFE registers. - Fixed in ConnectorsController firmware: if charger restarted itself (remote restart, web restart, restart after firmware update) it sometimes didn't boot up properly until physical restart. - Fixed in ConnectorsController firmware: locking/unlocking of connector sometimes didn't work if a car simulator was used and charging was stopped remotely (without turning S2 off). Updated drivers in this release: - gsm.dll 1.13 - iec.dll 1.02 - ConnectorsController firmware 1.11 Software version: 1.12.4 ======================== Date: 2.10.2019 Minimum version required for installation: 1.5.0 ### Charger Operations - StartTransactionRequest.MeterStart now contains 0. MeterValue messages send measurand Energy.Active.Import.Register that contains consumed energy in that session instead of meter value. StopTransactionRequest.MeterStop now contains energy consumed in session (or energy limit for that session, if it was reached). Bug fixes: - Fixed: If energy meter couldn't be initialized, LowVoltage warning was sent as a side effect. Now we don't check voltage anymore if we couldn't initialize energy meter. In addition, we send a GeneralError stating "Energy meter setup failure". - Fixed: if LoadGuard was connected to ethernet port of a router and charger was connected to WiFi of this same router, communication LoadGuard - Charger could not be established. ### Drivers Bug fixes: - Fixed in AFE driver: Operations sometimes failed to register AFE events. Events are now named so that Operations doesn't depend on AFE driver to set up events before it can register them. - Fixed in RFID/NFC driver: driver recognized RFID card twice if user held the card until beep. As a result charger cancelled RFID authentication immediately. Updated drivers in this release: - afe.dll 1.21 - nfc.dll 2.06 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