Software version: 1.8.0

Date: 25.10.2018

Charger Operations

– Charger supports different max current for single phase and 3 phase charging
– Operators are now part of the settings. When pressing factory reset, operators will be also reset to default values.

• Added possibility to temporary increase charger logs. Log level can be changed from web interface. After 24 hours logs level will be automatically decreased to default. This is working only for operations logs and not power management logs.
• After booting up charger now sends OCPP StatusNotification for connector 1 (as well as connector 0 as it did so far).
• OCPP MeterValues can now send additional measurements: Cluster_Power_Active_Total, Cluster_Power_Active_L1, Cluster_Power_Active_L2, Cluster_Power_Active_L3, Cluster_Current_L1, Cluster_Current_L2, Cluster_Current_L3, Building_Power_Active_Total, Building_Power_Active_L1, Building_Power_Active_L2, Building_Power_Active_L3, Building_Current_L1, Building_Current_L2, Building_Current_L3. This can be configured through charger’s web interface as well as through OCPP ChangeConfiguration (MeterValuesAlignedData, MeterValuesSampledData). Please be aware that this are not custom meter types and needs to be specially implemented on central system level. If you will enabled it on charger and central system will not support it, then probably none of the measurement will be stored on central system.
• Meter readings are more up-to-date as driver doesn’t cache values anymore.
• Added reporting of switched phases during electrical installation. If this happens, charger will send OCPP StatusNotification with VendorErrorCode=“LowVoltage” and message “Charger is not correctly connected to electrical installation. L1 and neutral are switched.” after booting up.
• Initial charging (the 30s period of charging when car is first connected) is now being measured from the time the car starts consuming current. This means that first 30 seconds charging current will be limited to 15A.

Bug fixes:

• Fixed: if authorization was required, charger didn’t automatically resume charging after restart.
• Fixed: Advertising on charger’s LCD wasn’t showing.
• Fixed: When factory reset of charger configuration is requested, operator settings (including password) were not preserved.
• Fixed: sometimes full reboot didn’t have time to execute due to Operations shutting down too fast.
• Fixed: reporting to Power Management master was running even when Power Management was disabled.
• Fixed: added missing connector state WakeUpInProgress.
• Fixed: “frozen LCD” fixes are now complete.
• Fixed: car’s charging limits were only measured during first charging after charger booted up.
• Fixed: sometimes when car stopped charging the LCD screen showed that car has only paused charging.

Web interface

• Enabled entering separate limitation for single phase charging
• Custom firmware flavours for some clients have now possibility for managing Charging authorization types .

Bug fixes:

• Fixed: web interface didn’t allow changing screensaver mode between Blinking and Steady. Default charging mode was being changed instead.
• Fixed: if user enters a charger that doesn’t exist into cluster, web user interface becomes useless.

Power Management

• If PM looses communication with a charger, it now excludes all connectors on that charger from calculation.

Bug fixes:

• Fixed: if cluster had only 1 charger, Power Management never asked charger to measure maximum current the car could charge with, which resulted in car charging with 15A or lower.
• Fixed: even if Load Guard was not installed, PowerManagement still performed claculations using Building power limits and limits set for load guard communication failure.

Installer

• Added ServiceWindow type of installation.

Service Window

• The user interface shown when user presses the button in Service Area was moved to its own executable which will run even if something happens and the rest of the charger isn’t running. When you press a button service window will be displayed in 5 second delay.

Software version: 1.7.1

Date: 19.10.2018

Charger Operations

• Demo slide show now has back button enabled.
• Fixed: new firmware download will be rejected if overall installation status indicates that installation is in progress

Installer

• Fixed: installation now doesn’t fail if backup folder doesn’t exist

Software version: 1.7.0

Date: 25.9.2018

Charger Operations

• Operations settings version changed to 4
  – AuthorizationSettings: removed AppStartCode.
  – CentralSystemCommunicationSettings: added FirstSendingTimeout: tells us how long will a message wait in first sending queue before it receives response.
  – EvsesSettings: added two settings for future use: EnforceMaxCurrentLimit, CustomMaxCurrentSinglePhase; added MeterType: IskraModbusRtu
  – GuiSettings: added setting for future use: ShowConnectivityStatus
  – PowerManagementSettings: added ShortStatusSendInterval, removed LocalMaster settings

New features:

• From this version on Operations will reject downgrade of major or minor version of itself. Downgrades of bugfix versions are still allowed, as we don’t change database or settings structure in bugfix versions. If version is X.Y.Z: X = major, Y = minor, Z = bugfix. Downgrades of other parts of the system are still possible (as long as Operations is not included in the package).
• Measuring maximum current in response to MeasureMaxCurrent message from Power Management.
• Operations now reports meter values to PM every 2 seconds if change is > 0.2 in current or power measurement.
• All meter measurements that are passed to PowerManagement are now freshly read. Also the driver version shipped with this edition doesn’t cache meter readings (previously meter reading could be up to 2s old).
• Optimized web server so that less class instances are created.
• Added reporting of consumed memory every 10 minutes.
• We’re now using Evse.EvseCode in place of StartCode.

Bug fixes:

• Added help text for PIN screen in Slovenian translation.
• As part of solving “frozen LCD” bug, all OCPP messages regardless of protocol are now being added to a queue before sending. This should also help ensure messages that are being sent are not lost in case of Power Loss.
• As part of solving “frozen LCD” bug, touching LCD now doesn’t require a ThreadPool thread. Also vendor animation doesn’t use ThreadPool anymore. There are however other cases that still involve ThreadPool.
• Fixed incorrect TimeZone setting (CentralEurope instead of Europe/Berlin).
• Some chargers are missing Factory settings, which means if user selects Factory Reset this will break the charger. Operations will now copy current settings to Factory folder if they are missing.
• Fixed: some chargers have Identity=DEFAULT in Factory settings. This will be overwritten with Idenity from currently active settings.
• Fixed: when power management was disabled and no charging profile was active, current was set to 14A of 15A (depending on car characteristics) instead to cable max.
• Updated screen borders to show less white on the edges.
• Fixed session sync with Power Management.
• Fixed popup icon & Sonnen leaf positions.
• Fixed: if center makes charger Unavailable and then sends Available, the charger didn’t become available again.
• Fixed “Charging in power mode” written over some other text on screen.
• Fixed: If a file didn’t exist in Config folder and needed to be upgraded, it got upgraded in Config\Factory and didn’t get copied to Factory.
• Fixed: in websockets communication, if server didn’t respond in time that could prevent reception of future responses.

Power Management

• Power Management settings version changed to 4
• WARNING for customers that were already testing Power Management: All existing power management settings will be replaced with new default settings.
• Local master is now always enabled, so that operations web can change power management settings.
• Finalized departure time prediction algorithm.
• Added hysteresis to prevent switching charging on/off very quickly.

Bug fixes:

• Fixed: PowerManagement always had the same version of settings as Operations.

Installer

• Added installation types TestUI and Generic.

Software version: 1.6.0

Date: 16.8.2018

Charger Operations

• Operations settings version changed to 3
  – AuthorizationSettings: changed Login section (added AppStartCode, AppDownloadUrl replaced AndroidAppUrl, IOSAppUrl, WindowsPhoneAppUrl)
  – CentralSystemCommunicationSettings: added NoCommunicationEthernetResetInterval
  – DalSettings: removed ChargePoint section
  – HardwareSettings: removed entirely
  – NetworkSettings: removed Channel
  – SessionSettings: added DefaultChargingMode
  – WebSettings: removed ZipPassword, added AllowAnonymousAccess

• Operations database version changed to 2
  – Operator table is not used anymore. Data is in Operators.json in Data directory so that it can survive database corruption.

New features:
– Enabled Wifi communication.
– If charger looses communication with RFID reader (and the reader is marked as installed and enabled in configuration), it resets RFID reader.
– Improved GSM interface management: ping server to keep up connection, report connection status, network operator and signal strength.
– Added minute-resolution power data to show in web interface (for last 24hr).
– Only ask user about departure time once (after charging starts).
– Changed font to support non-Latin characters and to make text smaller.
– Special beep when charging starts.
– MeterValues: minimal interval is 5s. Interval “0” means that meter values are not sent (as per OCPP spec).
– Operations now acts like watchdog for Power Management, restarting PM in case it crashes.
– Implemented measuring max car current in response to MeasureMaxCurrent message from PM.

Bug fixes:
– Some chargers were produced without a Serial Number. For these chargers, we now send Charger Identity in OCPP BootNotification where Serial Number would be sent.
– Some screens in Etrel flavour had blue gradient instead of solid black.
– Unknown RFID cards had userIdentificationType=0.
– Avoid sending nulls for not-set fields in BootNotification.
– Charging session data was calculated incorrectly.
– SMS login screen was showing charge point identity instead of friendly EvseCode.
– When there was no response over open websockets connection the resulting exception was classified as protocol error and thus didn’t require charger to reconnect and resend.
– When communication with PM failed, setpoint remained limited to safety levels ever after reconnect.
– Charger didn’t respect max current set by power management and OCPP schedules when in Fast mode.

Some Web changes:
– Enabled changing DefaultChargingMode.
– Showing GSM status.
– Enabled uploading custom translations (culture files) for charger screens.
– Enabled uploading custom intro logo.
– Time, regional settings ad currency can be changed through web interface.
– Added frequency control limits.
– We now list selected languages only.
– Bug fix: updating energy price always added new price.
– Bug fix: departure time on web app was different than on LCD screen

Installer

• Bug fix: after updating CC firmware charger sometimes didn’t restart. This happened when CC firmware update failed. Installer now repeats firmware update up to 3 times.

Power Management

• Master lowers current setpoints in accordance to building max current, LoadGuard measurements and charger status
• Master lowers setpoints when communication with LoadGuard is lost.
• Implemented configuration transfer from active to backup master
• Implemented message MeasureMaxCurrent to let the charger know it should set as high setpoint as possible and measure actual current

Software version: 1.5.3

Date: 28.6.2018

Charger Operations

Bug fixes:

• Fixed: handling of short filenames when writing log file archive
• GetDiagnostics is now more robust - FTP transfer type set to Binary, file archiving is now done before connection is opened
• Fixed: SetChargingProfile - if ValidFrom was later than StartSchedule, schedule was computed from ValidFrom time
• Fixed: if only one identification type was enabled, back button was enabled
• Fixed: on screen for login with mobile app, wrong value was shown for friendly EVSE code
• Fixed: SetChargingMode only changed mode and not departure time

Other changes:

• WebSocketPingInterval: minimal Ping interval changed from 60s to 10s
  Example for setting 10s interval via OCPP ChangeConfiguration: key=“CentralSystem.Client.WebSocketPingInterval”, value = “0:0:10”

Software version: 1.5.2

Date: 25.5.2018

Charger Operations

Bug fixes:

• Fixed: persistent state initialization
• Fixed: GetDiagnostics sometimes returned malformed zip file: (hopefully) fixed it by excluding size and closing zip entry after writing file

Other changes:

• GetDiagnostics: added looking at time of day (zipping only files that fall within range)
• WebSocketPingInterval: minimum is 1 minute (before: 0)

Software version: 1.5.1

Date: 23.5.2018

Charger Operations

Bug fixes:

• Fixed: when using websockets sometimes charger didn’t realize that it doesn’t have connection to backend.
• Fixed: connection status detection on OCPP heartbeats
• Fixed: charger didn’t detect correct identification type for unknown authorisations
• Fixed: charger now hides “enabled” but not installed sections on login possibilities screen
• Fixed: charger didn’t distinguish between PIN and RFID authorizations
• Disabled zip password for GetDiagnostics because we were getting some malformed ZIP files.
• Fixed: if firmware update was started through web app, charger never restarted itself.

Web app

Bug fixes:

• Fixed: web app didn’t show external modem IP

Software version: 1.5.0

Date: 17.5.2018

New settings:

• NetworkSettings.GsmSettings: added DeviceName, BaudRate
• CommunicationCheckerSettings: added NoCommunicationEthernetResetInterval

Charger Operations

Bug fixes:

• Fixed: sometimes when “back” button was not needed a black corner appeared in lower left corner of the screen (this was only visible if the background was not black, such as in Sonnen chargers).
• Fixed: OCPP GetDiagnostics always sent status UploadFailed regardless of actual outcome. Now it sends Uploaded/UploadFailed as appropriate.
• Fixed: if charger was set to plug&charge mode swiping a card stopped current charging.
• Fixed: if charger lost ethernet connection and there was no charging since last restart, it didn’t restart when it should have.

New features:

• Mobile communication (2G, 3G, 4G).
• WiFi communication is supported, but with a known bug: once wifi module looses communication it cannot reconnect (planned to be fixed in 1.7).
• Hard reset now resets all devices except Mobile and WiFi.
• If a screen is missing, a red screen with text “Missing Screen” will be shown instead.
• Operations uptime is written in logs every time version is written.
• Requires that Firmware updates are zipped with a password.
• All settings that can be updated through Web app or OCPP now enforce correct ranges (mix, max).
• Screens and culture files were moved into subfolders of Operations.
• Pairing of PLC modem.
• Version of Touch driver is recorded in logs.
• In case of database corruption, database is recreated.
• DiagnosticsFileUploadFailed event is now sent to backend because it contains information on why it failed (unlike DiagnosticsStatusNotification).
• Database now contains Version table and Operations can upgrade 1.4.0 version of database to this version.

Web app

Bug fixes:

• Fixed: User was able to enter any string as Gateway.
• Fixed; Entering departure time through web interface as stored departure time in UTC time instead of local time
• Fixed: IP v4 addresses in charger configuration should be properly formatted

New features:

• RestartRequired is returned when a configuration setting is changed that requires restart
• Once user changes configuration for the first time, charger state changes from FirstInstallation to InUse.
• Mobile status is shown in app header if installed. In status details, operator can find useful details: connected status, IP address, last known signal strength
• Wi-Fi status is shown in app header if installed. In status details, operator can find useful details: connected status, IP address, last known signal strength
• Web interface languages are available from burger menu (warning web interface languages are still missing)
• Charger can be restarted from web interface - diagnostic screen

Installer

• Added screen showing that installation is in progress.

Software version: 1.4.0

Date: 19.4.2018

First official release for Sonnen.

Software version: 1.3.0s (DEBUG version)

Date: 14.3.2018
This is listed as debug version because it hasn’t been tested before releasing into the wild (to a Sonnen charger).

Warnings

• Database has changed since previous version. Please delete old database before using this software.
• It works fine on my (versionless) image of WinCE. Which other image versions have been tested?

Operations

• Implemented protocol OCPP1.6J over websockets
  To be added

NetworkTools

This exe is used for debugging Ethernet problems. In DEBUG builds only: press upper left corner of LCD screen to bring up NetworkTools form.

Software version: 1.2.0

Date: never released (testing was not done)

Operations

• Added Verbose log level
• New PIN entry screen
• Replaced boot image (from old green Etrel logo to white on black)
• Added logging of touch coordinates (Verbose logs)
• Updated communication with WiFi module
• Added ability to have central system servers with different communication protocols (primary server has one protocol, secondary different one)
• MeterValues: added temperature, fixed units
• OCPP 1.6S:
  • Added missing WS_Addressing headers
  • Added parsing of SOAP Fault
• Obeys AllowOfflineTxForUnknownId: Enabled charging with unknown ID when charge point cannot reach the center if AllowOfflineTxForUnknownId is set to true
• Obeys AuthorizeRemoteTxRequests: When RemoteStartTransaction is received and AuthorizeRemoteTxRequests is set to true, charge point will try to authorize ID before starting charging.
• Fixed RemoteStartTransaction bug: if car was not connected when the command was sent, the charging didn’t start even after connecting the car

Settings/configuration file version: 2
Changes in this version:

• EvseSettings:
  • CustomMaxPowerKW changed to CustomMaxCurrent
• CentralSystemCommunicationSettings:
  • Protocol moved to the Client.Server setting (each server has it’s onw protocol setting)
  • ChargerServer got two new settings that are used to tell central system the address of charger’s OCPP endpoint:
    • ExternalIp (string), use “” or null if charger’s own IP should be used
    • ExternalPort (int), use 0 if Port should be used instead

No change in:

Power Management, Service Starter, Installer, Shutdown

Software version: 1.1.1

Date: 22.1.2018

Operations

Bug fix: fixed charging limits so that true minimum and maximum discovery is only employed when Power Management is enabled.

No change in:

Power Management, Service Starter, Installer, Shutdown

Software version: 1.1.0

Date: 19.1.2018

Operations

• Fixed missing heartbeat response
• Improved BackendId handling
• Improved central system client error handling and added more detailed logs, including OcppFault
• Fixed reported max power on start charging screen (previously it was commonly higher than actual)
• Fixed very long session length when charge point lost power during charging (edit: I think there still might be a bug here)
• Fixed sending or empty OCPP MeterValues messages to center
• Fixed determining car minimum when there is no power consumption at the beginning of charging session
• Fixed pausing/unpausing of charging depending on max current from Power Management (Operations side - CC side still has some issues)
• Added initial charging for 30s before allowing EVSE to pause charging
• We support new OCPP 1.6 messages:
  • UnlockConnector
  • ClearCache
  • TriggerMessage
• Installation / Firmware Update changes:
  • InstallDetails file was split into InstallTargets and OverallInstallStatus (breaking backwards compatibility).
  • Fixed the issue of Operations not sending OCPP FirmwareStatusNotification when download failed, the file didn’t have required structure, installation failed or installation succeeded.
  • Added support for download retries (by default: 3x)
• Fixed Settings WebApi:
  • Settings are now exported as all settings files combined in a ZIP. The filenames include version number, which is important when files are uploaded to a different version of Operations.
  • Now we hide WiFi password before exporting settings
  • On upload settings that describe installed hardware (such as type of connector) will not override existing settings on charge point.
• Added logging of OS image version, board serial, model, hw version from EEPROM

Power Management

Fixed SystemAbout when connecting to LG.

ServiceStarter

Name of installer restart count file has changed (breaking backwards compatibility).

Installer

• InstallDetails file was split into InstallTargets and OverallInstallStatus (breaking backwards compatibility) and removed InstallDetails.InstallerRestarts.
• Name of installer restart count file has changed (breaking backwards compatibility).
• Increased wait time after connector controller firmware installation (from 3s to 6s) to make sure CC is ready to receive HardResetSOM
• Added setting of StartedLocalTime, overall install status (successful / partially successful / failed) and ErrorMessage for each target
• Made install of CC firmware more robust.
• Each SOM reset is done in up to 3 tries.

Written with StackEdit.