• English
Select Language
HMS
Menu

Solutions

Solutions

  • Machine Builder
  • Factory Owner

Products

Products

  • Talk2M
  • Cosy
  • Flexy

Support

Support

  • Ewon Cosy
  • Ewon Flexy
  • Firmware & Software
  • All Documents
  • Talk2M Status
  • Tips & News

About Us

About Us

  • Security
  • Our Story
  • Events
  • News
  • Careers
  • Partners

Contact

Blog

Blog

  • Case Studies
eWON logo

Firmware Release Notes

Latest firmware version of the Ewon: 14.2s0

You can check a complete list of the fixes and improvements brought to the Ewon firmware in the release note file.

Here under, you will find the firmware release notes - starting from version 14.0s0 - with some explanations for some of the fixes / improvements to help you understand what is their scope / definition.

Version 14.0s0

Major

ADDED [ALL] GUI: Talk2M Connection Status Wizard added
ADDED [FLEXY] TAGS: String tag historization
ADDED [FLEXY] TAGS: String tags Rockwell support (DF1 & ABLogix)
ADDED [FLEXY] TAGS: Units support
ADDED [FLEXY] IOT : Siemens MindSphere data connector
ADDED [FLEXY] GUI : Spanish localisation
ADDED [FLEXY] JAVA: MQTT status in JAVA (ETK 1.4.4)
ADDED [FLEXY] JAVA: String Tags Support (ETK 1.4.4)
anchor ADDED [FLEXY] MISC: Flash Memory Management improved

New data logging mechanism in FW 14.0 for Ewon Flexy.
Prior to version 14.0 the recorded data points were synchronised with the flash memory at every change.
From firmware 14.0 on, the recorded data points are synchronised every 10 seconds with the flash memory.
This changes minimizes the CPU load required for the data recording, and it will also have a positive impact on the Ewon flash memory life cycle, especially if Ewon is recording many datapoints.

ADDED [FLEXY] MISC: Transparent forwarding Target device IP address encoding added
CHANGED [FLEXY] TAGS: String Tag size limited to 1KB per Tag
FIXED [ALL] INTERNET CONNECTION: Ethernet gateway is lost on DHCP reconnection if interface stayed disconnected longer than the DHCP lease time
FIXED [ALL] INTERNET CONNECTION: Watchdog when WAN static IP and NTP client are configured but no cable is plugged.
FIXED [ALL] INTERNET CONNECTION: Possible memory overflow issue during NTP synchronization
FIXED [FLEXY]: MQTT Status in BASIC wasn't updated in case of unexpected disconnections
FIXED [FLEXY205]: BACNET IOServer doesn't work properly on Flexy205. NB: BacnetIP IOServer only works on Flexy LAN Port.
FIXED [ALL] SECURITY: XSS vulnerability in the web server form "rcgi.bin"
FIXED [ALL] T2M: T2M instability may cause “biditr” watchdogs
FIXED [ALL] MISC: Various memory issues could cause “Out of memory” watchdogs (as of 14.0s0PR)
FIXED [FLEXY] JAVA: JVM Memory leak when using IOManager readTag/writeTag methods (as of 14.0s0PR)

Standard

  • ADDED [FLEXY] OPCUA: Add SYSTEM option "OpcuaIOSrvIgnCertErr" for OPCUA IOServer to ignore some server certificate errors
  • ADDED [FLEXY] OPCUA: Added KPI folder, units, and Tag quality in OPCUA server
  • ADDED [FLEXY] EBD: String Tags Instantaneous values can now be exported in binary format (EBD)
  • CHANGED [FLEXY] GUI: Changing memory configuration triggers automatic reboot of the device
  • CHANGED [FLEXY] GUI: Authentication certificates upload through the GUI are now automatically trusted in OPCUA Server
  • CHANGED [FLEXY] FILES: 2 new parameters have been inserted: "UseCustomUnit" and "Unit" in config.txt (var_lst.txt, var_lst.csv).
  • CHANGED [FLEXY] FILES: histstr.bin, histstr.txt, inst_val_str.bin added to support string tag historisation
  • FIXED [ALL] INTERNET CONNECTION: DNS cache issues when server IP changes frequently
  • FIXED [ALL] INTERNET CONNECTION: PPP connection would not start on demand in some cases
  • FIXED [ALL] INTERNET CONNECTION: DNS server cannot be configured when using Wifi Static IP configuration
  • FIXED [ALL] INTERNET CONNECTION: LAN Gateway cannot be used when using 3G/4G Modem ext cards but no internet connection configured
  • FIXED [FLEXY] OPCUA: "Change Configuration" user right is now needed to access usr/pki/ directory by FTP
  • FIXED [FLEXY] OPCUA: IOServer cannot update string Tag values in batch
  • FIXED [FLEXY] OPCUA: Writing multiple string Tags to Ewon OPCUA Server does not work
  • FIXED [FLEXY] OPCUA: Tag Addresses containing '"' may not be polled
  • FIXED [FLEXY] OPCUA: OPCUA Tags could be lost when added by BASIC script
  • FIXED [FLEXY] OPCUA: IOServer shutdown after the use of the CLEAR button
  • FIXED [FLEXY] OPCUA: IOServer Status tag has been fixed
  • FIXED [FLEXY] OPCUA: Source and server timestamps wrongly set
  • FIXED [FLEXY] OPCUA: OPCUA Server disconnections when one of the IP interfaces (VPN,LAN or WAN) is up/down
  • FIXED [FLEXY] OPCUA: OPCUA Server doesn't start correctly on some WAN-ETH+WIFI configuration
  • FIXED [FLEXY] OPCUA: IOServer was sometimes stuck when using few Tags
  • FIXED [FLEXY] GUI: OPCUA Certificates handling improved
  • FIXED [FLEXY] BASIC: REQUESTHTTPX with EBD does not handle DNS cache properly
  • FIXED [FLEXY] BASIC: SETIO command using tag id or tag index didn't work properly with string values
  • FIXED [FLEXY] BASIC: Function FS "ls" couldn't retrieve file and directory names starting with numbers
  • FIXED [FLEXY] BASIC: WRITEEBD may fail when writing lots of data
  • FIXED [FLEXY] TAGS: Float Tags were sometimes not properly rounded in the Tag View and in the Historical logging
  • FIXED [ALL] MISC: Ethernet switch (Lan/Wan) could be desynchronized between the boot loader and the firmware
  • FIXED [ALL] MISC: USBIP not working when SD Card is inserted
  • FIXED [ALL] MISC: USB commissioning might not be processed at boot when 3G/4G modem extension card is present
  • FIXED [ALL] MISC: Renaming inside user directory or moving files between different Media failed (ex : from /usr to /usr/sdext)
  • FIXED [ALL] MISC: Importing config.bin via ftp crashed the device
  • FIXED [ALL] MISC: TCP Server port conflict causes reboot
  • FIXED [ALL] MISC: EBD process keeps running in the background even if the request is aborted
  • FIXED [FLEXY] MISC: TagSSI for string tags truncated to 50 characters maximum
  • FIXED [FLEXY] MISC: "Not enough memory" Watchdog when exporting Historical Table
  • FIXED [FLEXY] MISC: Some Tags are lost when importing/updating Modbus Tag with bit selector through FTP
  • FIXED [FLEXY205] MISC: Putting a WAN-ext card doesn't reset the Lan/Wan switch config
  • FIXED [FLEXY205] MISC: 1:1 NAT doesn't work on WAN-ETH FLB3101 extension cardFIXED [ALL] T2M: Ewon Modem visible as a USB device in eCatcher after reset level 1
  • FIXED [ALL] INTERNET CONNECTION: "NTLM authentication" Proxy setting  overwritten by the wizard
  • FIXED [ALL] MODEM: Timeout was sometimes too short when sending SMS via cellular modem.
  • FIXED [ALL] MISC: Transparent forwarding of Rockwell/AB devices (TCP port 44818)
  • FIXED [ALL] MISC: Bolt configuration page unreachable (as of 14.0s0PR)
  • FIXED [FLEXY] TAGS: Unreachable Rockwell/AB devices (DF1/ABLOGIX IOServer) reduce massively Ewon performance

Continuity

  • ADDED [FLEXY] MISC: HTTP 404 error now redirects to the configured Homepage (Config page, Custom page or viewON)
  • ADDED [FLEXY] GUI: Option to disable DataManagement export

  • CHANGED [ALL] GUI: Remove "warning level" and "error level" column from Status pages. Remove warning/error bounds for TotalAllocated field.
  • CHANGED [ALL] MISC: The SDConfigEnable parameter update directly (no need to reboot)
  • FIXED [ALL] MISC: Bolt set-up stabilized
  • FIXED [ALL] MISC: "Reboot reason: User Web Request" missing in events log after user reboot through web interface
  • FIXED [ALL] MISC: Upgrade LED pattern was sometimes Green/Orange instead of Red/Off
  • FIXED [FLEXY] MISC: Device format could fail in some conditions
  • FIXED [FLEXY] MISC: High CPU usage when no cable plugged on WAN extension card and internet activated
  • FIXED [FLEXY] MISC: SNMP tagAlUser not initialized
  • FIXED [ALL] T2M: Current operation status was truncated in Talk2M wizard result page (as of 14.0s0PR)
  • FIXED [ALL] GUI: GUI could crash when USB devices list was empty
  • FIXED [ALL] GUI: Scrollbar added in Diagnostic-Status submenu
  • FIXED [ALL] GUI: Internet Browsers autocompletes specific form fields with non-related data
  • FIXED [ALL] GUI: Some translations containing accentuated characters were badly encoded
  • FIXED [ALL] GUI: Main page indicating "Bolt detected" even if no Bolt on the network
  • FIXED [ALL] GUI: Improve XSS filtering on specific forms
  • FIXED [FLEXY] GUI: Setup of PPPOutgoing with other languages than UK
  • FIXED [FLEXY] GUI: VPN "point to point" mode now sets VPNDrvMode to TUN
  • FIXED [FLEXY] GUI: BASIC IDE: Fullscreen mode was propagated to other pages.
  • FIXED [FLEXY] GUI: BASIC IDE: DMSYNC, WRITEEBD and FS functions weren't set in bold when used
  • FIXED [FLEXY] GUI: Data Management Selection set to T2M API by default
  • FIXED [FLEXY] IOT: Alarms are now correctly handled by the Mindsphere data management
  • FIXED [FLEXY] MISC: Format of /usr fails if SDEUM card present
  • FIXED [FLEXY] MISC : Import of Tags/Users lists with some missing columns through FTP results in using the last known column value

FAQ

What is a PR firmware?

PR stands for prerelease.

The release of a firmware version takes place in 2 phases:

  • First, we release a version labeled as PR for prerelease (e.g.: 12.1s1PR).
  • Later, in a time frame of 2 - 3 months, we will release the official version (e.g.: 12.1s1), without the PR suffix.

By doing so, we allow people to take advantage of new features and improvements in an early stage. We are also expressing our belief in the concerned PR firmware version to be an upcoming official release.

It is good to notice that during a PR version:

  • The installation of such PR versions is not advised to be performed on devices which should be deployed or commissioned. We would advise to wait for the official release version.
  • Documentation and other support tools can still be in the process of creation/publishing. They might be available but not fully done.
  • Marketing/sales materials may not be published until the official release. It may also happen that marketing release is provided earlier than the official release, for preannouncement purposes.
What is a pivot firmware?

For Ewon Flexy and Cosy 131, and since firmware version 11.0, it is no longer required to perform an Ewon recovery to upgrade the firmware to another major version.
This major version update can be performed with a simple Ewon firmware update thanks to “Pivot firmware”. This means that the firmware can also be updated from remote.

By "pivot firmware", we define firmware versions that are mandatory to upgrade to before going any higher. In fact, all major versions (v12.0s0, v13.0s0, ...) are pivot firmware.

For example: if the firmware version is currently 11.2s2 and there's a wish to upgrade to v13, a first upgrade to v12 is required. Once the current firmware version is 12, then only can the upgrade to v13 be operated.

However, a firmware recovery is still possible and allows you to jump directly to the latest firmware version. Therefore you do not need to step through all different pivot firmware.
If you have a local access to the Ewon, then it is easier to perform directly an Ewon recovery

What is the difference between a ".edf" and a ".ebu" file?

Both files are used as a firmware update file for an Ewon device.

The ".ebu" file can be used for the following cases:

  • A recovery of your Ewon device with no data lost;
  • A straight update between any firmware versions, especially major versions (e.g.: v11 to v14 in a single step), which also triggers the recovery process with no data lost.

The update via .ebu file - the recovery process - can only be performed locally, either through eBuddy or through the SD card / USB flash drive.

The .edf file can be used in the following cases:

  • An update of an Ewon firmware between minor versions: v14.1s0 to v14.2s0;
  • An update of an Ewon firmware between major versions which involves the firmware to be updated to each pivot firmware version (e.g.: v11.0s0 to 12.0s0, then to 13.0s0, then to 14_0s02, ...)

The update via .edf file can be done either locally or remotely through eBuddy or FTP, and only locally through SD card / USB flash drive.

Expand all

Collapse all

Technical Support

Product name
ORDER CODE:

STEP-BY-STEP GUIDE

  • Preparation
  • Installation
  • Configuration

RESOURCES

  • Downloads and Documentation
  • FAQ
  • Troubleshooting

SERVICES AND TRAINING

  • Technical Services
  • HMS Academy Trainings
Request support

Contact support

Solutions

Factory Owner
Machine Builder

Products

Talk2M
Cosy
Flexy 

 

Support

Ewon Cosy
Ewon Flexy
Firmware & Software
All Documents
Talk2M Status
Tips & News

About us

Security
Our Story
Events
News
Careers
Partners

Blog

Case Studies

 

Contact

Like us Follow us Watch us Join us Newsletter
OUR BRANDS: Anybus Ixxat Ewon Intesis
HMS
Copyright © 2020 HMS Networks.
Menu
  • Cookies
  • Privacy Policy
  • Terms of Use
  • Warranty

We use cookies on this site to enhance your user experience

By clicking any link on this page you are giving your consent for us to set cookies.

I want to find out more Yes, I agree