deviceWISE IoT Gateway 24.01 Release Notes
A number of improvements and fixes were added to the IoT Gateway 24.01 release.
Summary:
The 24.01 release includes improvements made to the Workbench, deviceWISE View, Transaction Server and multiple drivers.
Production Release Date: April 2024
As of Release 24.01 the Technical Support License (TSL) is required to enable updates to new version. The absence of a TSL will prevent the update of installed software. If you do not have a current Technical Support License do not attempt to update your version of deviceWISE.
To ensure you are receiving genuine Telit Cinterion services and updates, all deviceWISE software as of Release 24.01 requires a Technical Support License (TSL) to be installed. The TSL acts as a reminder of the status of your Support subscription. At select periods prior to the expiration of the subscription, a notification on your deviceWISE Workbench will provide a clear visual notification. If you are missing a license or if the license is expired/expiring there will be a visual notice.
New features and enhancements to existing features
Workbench
- [MAP-20743] -Allow Backup Utility to Run as a Service
Description: Backup utility on Windows can now run as a service. - [MAP-21023] -Added ability to change tab layout in admin panel between wrapped and scroll
Description: Administration panel tabs can now be toggled between a stacked view and a scrolling one-line view. - [MAP-21019] -Add go to start/end of table buttons for local db browsing
Description: Added go to start/end for table navigation in local db panel. - [MAP-20882] -Watch Window: Bits from INTEGERS should be supported (Booleans are)
Description: Added ability to watch individual bits in Workbench variable panel when an integer is bit expandable. Requires a 24.01 Gateway and Workbench.
deviceWISE View
- [MAP-20456] -Create Camera Widget
Description: A camera widget was added to View. - [MAP-20579] -Camera Widget - Add support to select camera
Description: Camera widget supports selection of camera. - [MAP-20667] -Trend Widget- Remove the limit for number of samples for absolute and real time trend
Description: It is now up to the user to limit the number of samples and select the time range accordingly as there can be performance issues.
deviceWISE Runtime
- [MAP-20581] -Integrate SRA Client into build
Description: SRA distribution will be part of the build under: DW24.01\24.01.03\Telit\Telit\SecureRemoteAccess - [MAP-19981] -Add signing to all DLL’s and EXE files of thickclient using the Organization’s Certificate
Description: All Workbench and Backup utility installers and runtime binaries are signed. - [MAP-17955] -License Server - Release license when the HTTP Server is stopped (Core)
Description: Warning message will now appear when stopping http server. User must press "Yes" to continue. - [MAP-19980] -Enable Control Flow Guard for all exe and dll
Description: Control Flow Guard is not applicable to java as it does its own memory management.
Transaction Server
- [MAP-20799] -Update Error Messages (SOAP+HTTP) Validate Fails
Description: Updated Error Messages for Http & Webservices Transport.
Drivers and Extensions
- [MAP-20478] -Toyopuc: When receiving error 73 -- retry after a random small delay
Description: dwtoyopuc: Added packet retry on response error:0x73(PLC BUSY) for read and write. - [MAP-20477] -Toyopuc: In addition to allowing consecutive ports, create option to specify a list of ports
Description: dwtoyopuc: Added device definition property to provide custom list of port numbers. - [MAP-20617] -OPCUA Server does not lazy load a device that uses lazy loading
Description: When an OPCUA client connects to the deviceWise OPCUA server and browses a device that is lazy loaded, it will lazy load the device on each browse request from the OPCUA client. - [MAP-19578] -SRA Tunnel Server returns SSL_WRITE error
Description: Improvements were made to increase the stability for satellite connection.
Issues Fixed on the 24.01 Release
Workbench
- [MAP-20629] -Long Variable Names cut off in action panel i/o tables
Description: Display of variable names in action editor will format better for longer names. - [MAP-20626] -Workbench crashes on Apple Mac when dragging action from list
Description: Fixed trigger editor crash on Mac when dragging action to add. - [MAP-20387] -Cellular actions listed under "Hardware Control" in the trigger editor
Description: Group name is changed from Hardware Control to Cellular Modem. - [MAP-20806] -Workbench node disconnect/reconnect functionality inconsistent
Description: Corrected enabling of disconnect/reconnect node context menu options and disconnect detection.
deviceWISE View
- [MAP-20507] -Widget Canvas widget - Doens't honor the background color setting
Description: Added support to change background color for Widget Canvas. - [MAP-20222] -Line Chart Trend widget - Chart doesn't honor foreground color configuration
Description: Line Chart Trend fixed resolution of foreground color. - [MAP-20714] -Trend Widget - Unable to remove Apex Charts > Markers
Description: Trend Widget added capability to remove Apex Charts > Markers. - [MAP-20694] -Data Trending Widget - Legend doesn't appear for a single variable
Description: Added support to show legend for single series. - [MAP-20901] -Different menu options in View on different windows sizes
Description: Missing menu items added to the main tool bar and hidden bar. - [MAP-20880] -Cannot Stop Playing Audio in deviceWISE VIEW
Description: Added stop audio action to stop playing of audio. - [MAP-20450] -Trending Widget: Gap in data when device offline breaking graph
Description: Trending Widget fixed Gap in data when device goes offline.
deviceWISE Runtime
- [MAP-20600] -Campaign sup exhibits error on portal but succeeded on the gateway
Description: Firmware update action tried to change access on a file that is not properly configured. Chmod will now act on the file "install.exe" instead of "install.exe /s"; thus no SUP failure. - [MAP-15059] -Polling stops for all devices while one device times out
Description: Fixed a problem where a device timeout can cause all other devices in the same priority not reading data at the expected interval. - [MAP-19763] -Trigger reporting - Stack trace - OnError
Description: Fixed issue with trigger reporting stack trace successful executions and not just failed ones. - [MAP-19880] -Enable Control Flow Guard for all exe and dll
Description: Control Flow Guard was not applicable to java as it does its own memory management. - [MAP-20317] -Core will not start if too many network interfaces, 64
Description: Fixed a problem where we could not handle 16+ network interfaces on Linux x64 and x86. - [MAP-20755] -Setting Attention Bit On Disabled Devices Does Not Work
Description: Set Attention bit was not working if device is disabled on start for the first time. It now correctly sets the attention bit. - [MAP-21026] - Enterprise Gateway Crashing While in Operation
Description: When the OPCUA Server has a client that subscribes to a node that receives many change notifications at the same instant a crash can occur. - [MAP-20174] - Enterprise Gateway Crashing While in Operation
Description: When the OPCUA Server has a client that subscribes to a node that receives many change notifications at the same instant a crash can occur. - [MAP-20755] -Setting Attention Bit On Disabled Devices Does Not Work
Description: Set Attention bit was not working if device is disabled on start for the first time. It should now correctly set the attention bit.
Licenses
- [MAP-20350] -Valgrind leak on Linux-x64-Generic on tr50_json_parse - Unable to pull licenses when connecting to the tr50 server
Description: Fixed a very small memory leak when tr50 established the connection.
Drivers and Extensions
- [MAP-20353] -Trigger reports are not being generated on certain failures
Description: When trigger is disabled by event failure (ex: Data event fails to read the datapoint), it will no longer increment the failure count. - [MAP-20433] -OPCUA Client subscription to an array element not working
Description: Subscribing to an array element from an OPCUA client was not working, it showed incorrect values. Fixed the issue. - [MAP-20312] -Unable to browse OPC DA URL using OPC ENUM or Manual connection after upgrading DeviceWise version on new OS
Description: The x64 bit version of the OPC DA driver requires the installation of the OPC Core components. - [MAP-20566] -Enterprise Gateway - PeerLINK - Node Connection Not Reading
Description: Node Device Connection was not working in Windows 64 bit system. The size of long is 4 instead of what we expected as in every other platforms, which should be 8. Causing the workbench to wait for a read that will never happen. The issue was fixed. - [MAP-20472] -OPC DA Client memory leak
Description: Fixed issue with memory leak that appears when the driver is set to "read style subscription based" and "all reads sent to server" is true. Under this condition a small increase of memory occurs on every read. - [MAP-20468] -Keyence -- allow for an option to enumerate booleans (liner and word offset)
Description: dwkeyence: Provided dev definition property to enable bit tags to show as linear array instead of words array. - [MAP-20127] -OPC UA client: Node Crashed when Started OPC UA client
Description: The OPCUA client server driver will support adding a device which is an OPCUA client only when it contains a small number of points. There next release will support lazy loading the client device by loading on demand after a browse. - [MAP-19941] -Fanuc CNC driver : Variable are not enumerated after the device restart for FANUC CNC
Description: dwfanuc cnc: Added check on errors for variable enumeration and disable device if enumeration fails. - [MAP-20702] -Azure Event Hub Send Telemetry Timeout issue
Description: Trigger using Send Telemetry to Event Hub will no longer go Disabled when using the Timeout setting in the Advanced Properties. - [MAP-20687] -Codesys issues w Wago/Sonnys
Description: dwcodesys: Fixed issue in enumeration which in turn fixes variable read/write. - [MAP-20598] -AWS IOT Core -- if connection drops -- it wont reconnect on its own
Description: AWS IoT Core will try to automatically connect after deviceWISE restarts and the network connection is unavailable. - [MAP-20790] -AWS triggers disable when trying to reconnect
Description: AWS attempts reconnect after hardware reboot. Triggers stay enabled if store and forward is enabled.
Supported Driver Versions
| Generally Available | |
|---|---|
| Device Driver | Version |
| AcraDyne driver | 1.1.3 |
| Advanced Display Protocol | 1.0.2 |
| Apex Cleco driver | 1.9.4 |
| Atlas Copco driver | 3.9.1 |
| AWS | 0.2.12 |
| Azure | 2.1.12 |
| Beckhoff driver | 2.1.9 |
| Bosch Rexroth driver | 1.8.4 |
| Danlaw | 2.12.3 |
| Estic driver | 1.1.3 |
| FANUC CNC Driver | 1.4.1 |
| Fanuc driver | 2.3.2 |
| Industrial driver | Updated with each release |
| Ingersoll Rand driver | 1.3.4 |
| Kawasaki | 1.2.3 |
| Keyence | 1.0.4 |
| LDAP – do not use with Linux X86 in versions 21.10 and later | 1.1.2 |
| Lua | 1.1.4 |
| IBM Maximo | 1.1.4 |
| IFM IO-Link | 0.6.1 |
| Melsec | 3.5.4 |
| Mitsubishi driver | 3.3.7 |
| Modbus driver | 2.11.2 |
| Modbus Server driver | 1.1.8 |
| Modem | 1.5.1 |
| MQTT driver | 2.1.3 |
| MTConnect driver | 1.3.2 |
| NMEA GPS | 1.0.4 |
| OAuth2 | 2.3.2 |
| Omron driver | 3.8.2 |
| OPC-DA Client driver | 2.8.4 |
| OPC-DA Server driver | 1.3.2 |
| OPC-UA Client driver | 4.1.13 |
| OPC-UA Server | 1.2.6 |
| ROC Plus driver | 2.0.2 |
| Rockwell ControlLogix driver | Updated with each release |
| Schneider Electric | 2.9.0 |
| Siemens S7 driver | 3.0 |
| SNMP driver | 1.1.1 |
| Stanley Tools driver | 1.2.0 |
| Sturtevant Richmont driver | 1.8.4 |
| Sysmon | 1.0.2 |
| TCP Listener | 2.3.12 |
| Toyopuc | 1.0.5 |
| TR50 | 2.6.2 |
| deviceWISE View | 2.1.3 |
| Technology Preview | |
|---|---|
| Device Driver | Version |
| Amcrest | 0.5.0 |
| AWS SiteWise | 1.0.3 |
| BACnet / IP driver | 3.2.12 |
| Barcode Scanner | 1.1.1 |
| CODESYS driver | 0.6.4 |
| CTI (Control Technologies Inc.) driver | 2.1.5 |
| Dell Edge Gateway (Linux 64-bit) | 0.5.0 |
| EDU (not built for Windows 64-bit) | 1.0.1 |
| E-Sensors | 1.0.1 |
| File Watcher - Updated with 23.04 | 1.0.8 |
| Google Cloud Platform (GCP) | 0.3.4 |
| HAAS | 1.0.0 |
| GrovePi driver(Only in Raspbian directory) | 1.0.2 |
| HTTP Server | 0.7.1 |
| J1939 IXXAT device Driver | 1.1.1 |
| JSON | 0.5.3 |
| Melsec | 1.0.1 |
| Keyence | 1.0.3 |
| Nachi – (Windows Only - Win32 and Win64) | 0.7.0 |
| 1.0.1 | |
| OPTO22 | 0.0.5 |
| Sandbox | 1.3.0 |
| Serial | 1.3.0 |
| SICK CLV Scanner | 1.1.7 |
| Simulation | 0.5.1 |
| Telit SmartIO | 2.2.1 |
| Trending | 1.3.11 |
| Visual Inspection | 1.0.0 |
| Virtual | 1.3.0 |
| Xirgo | 1.3.0 |
| Zaxis (only built for Windows products) | 0.5.1 |
Upgrading from previous versions
Backup before upgrading! You should do a Backing up and Restoring a node's configuration of your configuration from the Workbench prior to upgrading to a new version of deviceWISE.
Updating from an earlier release level of an Enterprise Gateway to 24.01
Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 24.01 build level before starting their deviceWISE application.
For Windows Enterprise Gateway products:
Upgrading a Windows Enterprise Gateway product from a version before 19.1.6 to 24.01
We moved to a new installation architecture for Windows Asset Gateway and Enterprise Gateway products with version 19.1.6. These Special Notes apply to a one-time transition from a Windows Gateway version before 19.1.6 to a Windows Gateway version after 19.1.6.
If you are upgrading a Gateway for Windows product to version 19.1.6 or later, you must do the following:
- Perform a node backup of deviceWISE
- Backup all files used in the Staging Browser folders or properties files that were added outside of the original deviceWISE installation. (For example: C:\deviceWISE\Runtime\staging and C:\deviceWISE\Runtime\dwcore)
- Uninstall the (pre-19.1.6) version of the Enterprise Gateway for Windows product
- Install deviceWISE Enterprise Gateway for Windows or deviceWISE Asset Gateway for Windows using the given installers.
- Copy the files backed up from step #2 contained in the Staging Browser folders or properties files to the new installation folder. (For example: C:\Program Files (x86)\deviceWISE\Gateway\staging and C:\Program Files (x86)\deviceWISE\Gateway\dwcore)
- Restart deviceWISE.
- After updating to 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.
- Restore your node.
Upgrading a Windows Enterprise Gateway product from 19.1.6 or later to 24.01
A firmware update from a release for Enterprise Gateway for Windows before version 19.1.6 to 24.01 is not supported. You must do a complete product installation as noted in the previous section.
If you are updating an Enterprise Gateway for Windows 64-bit products from the 19.1.6 release or later, then you can use the firmware update option.
After updating to 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.
After updating the runtime and the package files, you may restore your node from a backup if you did a node backup before installing the new version of runtime and packages.
For AIX, Linux, or WinCPU Enterprise Gateway products:
If you are updating an Enterprise Gateway from a 17.2.3 through 24.01 (inclusive) release, then you can use the firmware update option. A firmware update from a release before 17.2.3 is not supported.
If you are updating an Enterprise Gateway from a 17.1.14 or earlier release to 24.01, you must do a complete product installation. This is required to install the supporting libraries and 3rd party support files. These supporting files are not included in a firmware update for an Enterprise Gateway, however they are included in a complete install.
After updating to 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.
After updating the runtime and the package files, you may restore your node from a backup if you did a node backup before installing the new version of runtime and packages.
A firmware update from 16.1.8 or earlier to 24.01 is not supported for CentOS 7 or systemd installations. A full installation is required.
20.1.9 is the final release for VxWorks-based gateways and got removed from builds beginning with the 20.1.10 release. If you need assistance, please contact us here.
Updating from an earlier release of an Asset Gateway to 24.01
Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 24.01 build level before starting their deviceWISE application.
For Windows Asset Gateway products:
Upgrading a Windows Asset Gateway product from a version before 19.1.6 to 24.01
We moved to a new installation architecture for Windows Asset Gateway and Asset Gateway products with version 19.1.6. These Special Notes apply to a one-time transition from a Windows Gateway version before 19.1.6 to a Windows Gateway version after 19.1.6.
If you are upgrading a Gateway for Windows product to version 19.1.6 or later, you must do the following:
- Perform a node backup of deviceWISE
- Backup all files used in the Staging Browser folders or properties files that were added outside of the original deviceWISE installation. (For example: C:\deviceWISE\Runtime\staging and C:\deviceWISE\Runtime\dwcore)
- Uninstall the (pre-19.1.6) version of the Asset Gateway for Windows product
- Install deviceWISE Enterprise Gateway for Windows or deviceWISE Asset Gateway for Windows using the given installers.
- After updating to 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.
- Copy the files backed up from step #2 contained in the Staging Browser folders or properties files to the new installation folder. (For example: C:\Program Files (x86)\deviceWISE\Gateway\staging and C:\Program Files (x86)\deviceWISE\Gateway\dwcore)
- Restore your node.
Upgrading a Windows Asset Gateway product from 19.1.6 or later to 24.01
A firmware update from a release for Asset Gateway for Windows before version 19.1.6 is not supported. You must do a complete product installation as noted in the previous section.
If you are updating an Asset Gateway for Windows 64-bit products from the 19.1.6 release or later, then you can use the firmware update option.
After updating to 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.
After updating the runtime and the package files, you may restore your node from a backup if you did a node backup before installing the new version of runtime and packages.
For AIX, Linux, or WinCPU Asset Gateway products:
If you are updating an Asset Gateway from a 17.2.3 through 22.02 (inclusive) release, then you can use the firmware update option. A firmware update from a release before 17.2.3 is not supported.
If you are updating an Asset Gateway from a 17.1.14 or earlier release to 24.01, you must do a complete product installation. This is required to install the supporting libraries and 3rd party support files. These supporting files are not included in a firmware update for an Asset Gateway, however they are included in a complete install.
After updating to 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.
A firmware update from 16.1.8 or earlier to 24.01 is not supported for CentOS 7 or systemd installations. A full installation is required.
For more information about upgrading your software, see Updating products.
20.1.9 is the final release for VxWorks-based gateways and got removed from builds beginning with the 20.1.10 release. If you need assistance, please contact us here.