deviceWISE IoT Gateway 25.01 Release Notes
A number of improvements and fixes were added to the IoT Gateway 25.01 release.
Summary:
The 25.01 release includes improvements made to the Workbench, deviceWISE View, Transaction Server and multiple drivers.
Production Release Date: April 2025
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-22377] -Move Event/Macro/Local/Static to start of variable select box list
Description: Arranged variable list in Trigger editor to show Event/Local/Static/Macro variables first. - [MAP-22450] -Support Octal numeric input in generic entry fields
Description: Allow octal format field in generic panel definitions. - [MAP-22446] -Center trigger editor mousewheel zoom on pointer position
Description: Trigger editor mousewheel zoom will now center zoom on pointer position instead of center of visible canvas. - [MAP-22445] -Allow trigger action editor to be pinned
Description: Added ability to pin action editor in trigger canvas window instead of a floating window. - [MAP-22387] -Allow rearranging nodes in Workbench groups
Description: Allow nodes in group to be ordered in multiple ways: 1. From the group folder nodes can be sorted alphabetically or by IP/scan address. Order with alternate ascending/descending if repeated 2. From the node in the group, can move up/down/top/bottom from menu or via hotkey. - [MAP-22625] -Constant value in transport map payload cannot be edited
Description: Fix issue with editing constant values in transport map schema table inputs. - [MAP-22448] -Trigger Editor Cosmetic/Customization - 1st phase
Description: Updated trigger editor cosmetics, allow for docking of action editor panel to canvas side.
deviceWISE View
- [MAP-22366] -Remove Widget Group from the widget palette
Description: Removed Widget Group from the widget palette. - [MAP-22238] -Introduce Toggle Widget Borders Button
Description: Added Toggle Widget based on layer settings. - [MAP-22547] -Logging tab into Diagnostics tab
Description: Grouped license panels into one sub-panel in the Administration Panel, and the diagnostic panels were grouped into one when extension logging settings are available. - [MAP-21969] -Expose Current Logged In User as Accessible Variable in VIEW
Description: Display the current logged in user in deviceWISE VIEW by exposing this as an accessible variable. - [MAP-21849] -Set Default display by Role
Description: Add capability to set default display by Role. - [MAP-21848] -Should be able to view the home display settings for all users in one panel
Description: View the home display settings for all users in one panel. - [MAP-22378] -No way to save advanced JSON without making editor fullscreen
Description: Add support to save advanced JSON without making editor fullscreen.
Transaction Server
- [MAP-22603] -SOAP Transport Map should allow blank endpoint, default to Transport value when not set
Description: WS_SOAP transport map will allow blank endpoint URL and default to host value for transport when not set.
Visual Inspection
- [MAP-22461] -Add Segmentation to deviceWISE View AI Widget
Description: Added Segmentation to the deviceWISE View AI Widget.
deviceWISE Runtime
- [MAP-21878] -Peerlink node connections, devices do not properly enumerate when using latest OPC UA/DA clients on remote node
Description: Nodelink Device will now work properly with remote device that supports lazy enumeration. - [MAP-22210] -Add optional compression for PeerLink Connections
Description: New device property "Compression" is added to Peerlink and Nodelink devices. Valid values are "Off" and "Auto". Default is set to "Auto". If it's set to Auto, it will apply compression only if the remote side is 25.01+. - [MAP-22208] -IFM implement DI/DO in sensor port
Description: IFM IO-Link supports digital input or digital output functionality when pin 4 on the IFM IO-Link Master is configured as such.
Drivers and Extensions
- [MAP-22380] -AWS IoT Core -- change release version to 1.0.0
Description: Updated AWS IoT Core version to reflect that it is a Generally Available driver. - [MAP-22343] -Add Serial # for the IO-Link Sensor to variable tree
Description: IFM IO-Link now provides the IO-Link sensor serial number as a deviceWISE variable. - [MAP-22309] -Add automation for Compression/Decompression Action
Description: New actions to compress and decompress strings have been added. - [MAP-22567] -OPC UA Server & DA Server -- need to count incoming client requests against licenses
Description: The number of OPC Client connection to the deviceWise server are now limited by the number licenses available. (Similar to [MAP-22101]) - [MAP-21017] -Implement Allen-Bradley DF1 CIP encapsulation
Description: Rockwell driver now supports DF1 messages encapsulated in CIP using the 1756-DHRIO backplane module. - [MAP-22385] -Move all actions/events from dwadvanced to base installation
Description: dwadvanced package contains 2 actions(enhanced demand read/write) and 1 event(ftp activity) are now moved into base installation.
Issues Fixed on the 25.01 Release
Workbench
- [MAP-3086] -XSD: String maxLength attribute not working
Description: Allow default string length to be set in XSD via length facet.
Visual Inspection
- [MAP-22473] -Visual Inspection: Crash on Inference
Description: Fixed Visual Inspection crash when running inference action. - [MAP-22276] -Visual Inspection - Crash when using buffer as inference input
Description: Fixed Visual Inspection crash when using memory buffer for image input and the image is a raw image which is an unsupported type.
deviceWISE View
- [MAP-22379] -Clicking on icon in toolbar does not add widget to display
Description: Fixed error with clicking on a widget icon in the toolbox on a new blank display adds it to the display. - [MAP-22339] -Gauges not working properly
Description: Fixed Scaling of Gauges Widget. - [MAP-22579] -WB Table headers should right align when value cells right aligned
Description: Changed alignment of numeric table column headers to align with cell values. - [MAP-22230] -deviceWISE View installation does not cleanup old app files in staging
Description: Old files will now be removed prior to copying new files. - [MAP-22454] -Value card doesn't show the value of array if the data type is INT8 or UINT8
Description: Fix defect on Value card not showing the value of array if the data type is INT8 or UINT8. - [MAP-22544] -Select Tab within Settings -switch to the edit screen for the selected widget
Description: When selecting the widget from the setting box, deviceWISE View would switch to the edit screen for the selected switch. A fix was made and the current behavior is that the properties window is not always shown. - [MAP-22517] -Select Tab within Settings -the initial widget stays highlighted
Description: Fixed the initial widget stays highlighted when using select tab of widget settings. It is now possible to select the widget in the canvas, then use the select tab of the settings window to select a new widgets, remaining with the selection of the first widget.
Installers
- [MAP-22328] -MAX Installer -- issues w NLS files
Description: devicewise MAX was shipping a wrong NLS file(Chinese) on english installation, thus showing "Message Not found" in various places. It is corrected now with an English NLS file.
deviceWISE Runtime
- [MAP-22337] -Encode JSON Removing Decimal Precision
Description: The input template has a DOUBLE value of 10.000, the JSON efficiently converted 10.000 into 10. When the action executes, assuming the value was a datatype of INT instead of double. The workaround is to change 10.000 into 10.001. A change was also made so that it will preserve the original datatype for this action. - [MAP-22369] -Trigger tag and set command issues
Description: Corrected datatype error when re-editing action/event with lazy enum var in a structure. - [MAP-22487] -License Server remove old clients
Description: Added ability to remove/release license client from the license server admin panel. - [MAP-22493] -String Decompress returns error with missing NLS message when using a String as input
Description: The compress/decompress action error messages show code -1 and had no descriptions. The issue was fixed and NLS messages were added. - [MAP-22479] -API Session Timeout
Description: API Session timeout setting wasn't working after a restart. The module loading order was wrong, hence the timeout is reset to properties file default instead of keeping what's loaded from persistence. The issue is now fixed. - [MAP-22441] -Change Device Disable Load Protection Default
Description: "load protection" is now disabled, meaning that the devices will not be changed to Stopped even when they crash on Starting/Stopping. The protection used to alter customer's application unsolicitedly, which was causing problems. - [MAP-22391] -Add MJPEG support to the core's HTTP Server
Description: Revised the operation of the internal HTTP server to support MJPEG streaming. - [MAP-22449] -Lost connection when using custom ID file
Description: The embedded blank check unintentionally applied to the file name instead of the serial ID itself. The fix removed the check on the file name. - [MAP-22584] -String builder table row insert issue
Description: Fixed a bug in the DW_ANY type. When you assign a variable to DW_ANY, it wasn’t copying the entire array. Now that it's fixed, when the user look at the trigger, the variable mapped to "columns" is actually a string array with 4 element, and when it is converted it into a string it becomes * , , , 0 (that's the values in the variable). The string builder's input logical variable was changed from ANY to STRING with count of 1, so it will always take the value in first element. - [MAP-22581] --5109 Event Variable is Not Serviced
Description: The Meessage "Variable is not serviced" was updated to "Variable is not used". - [MAP-22499] -Missing NLS messages
Description: Missing messages added. - [MAP-22497] -Invalid read on _localdb_delete_select_fe
Description: Selecting null value into a timestamp was causing the crash. It is now fixed by doing a null check before using the variable. - [MAP-22672] -Local DB Insert does not default to Row Count for the number of rows to insert at once if Actual Row Count is blank
Description: Updated "Row Count" to "Maximum Row Count" to clarify that there are two different "count". - [MAP-22635] -License Server does not release license due to TSL issue
Description: A fix was conducted, making the server serve even if the self connected client fails. - [MAP-22618] -Incorrect Insufficient Licenses Error
Description: Client license check for device count was checking for both client licenses and server licenses. It should only require client device count. The issue was fixed with the new version.
Drivers and Extensions
- [MAP-22521] -RTSP/ffmpeg based camera driver -- does not work w Verkada Cameras
Description: The action to capture an image returned incomplete images. A new admin panel was added to display an image and provide a live view. - [MAP-22178] -Investigating CAF23 - Linux GW2 - 2nd Node Crash - 13 Nov 2024
Description: dwsiemens: Cleanup of local variables to avoid crash of stack overflow and fix on i18n (German char conversion) code to avoid the crash. - [MAP-22330] -Trigger failed to write in Rockwell PLC - Variable length is invalid
Description: dwrockwell: Fixed binary type demand read/write issue in which was regression of lazy enumeration. - [MAP-22384] -Kawasaki driver crashes during login
Description: dwkawasaki: Fixed crash issues and connection issue with T controller. - [MAP-22264] -Rockwell driver - Unable to enumerate tags from Micro820 device
Description: dwrockwell: Fixed issue in micro800 tags enumeration. - [MAP-22400] -Register range on RCPU (Local) with Mitsubishi EzSocket Driver
Description: dwmelco: Fixed issue in variable range in enumeration. - [MAP-22673] -OPCUA crash when writing an array range
Description: There was a crash occurring when using a demand write using a range of indexes. The issue was fixed with this new release. - [MAP-22568] -Genicam camera stops taking images after a few hours of operation
Description: The Genicam driver was stopping taking pictures after a few hours of operation when it runs on a slow network, the camera has a high resolution. The logic for creating the stream and waiting for a new frame has been revised, and improved error handling has been implemented. - [MAP-22436] -Add MJPEG support to dwhttp
Description: Added MJPEG support to the dwhttp driver. MJPEG is used by deviceWISE camera drivers to display a live video in a web browser.
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.10 |
| AWS | 1.0 |
| Azure | 2.1.12 |
| Beckhoff driver | 2.1.9 |
| Bosch Rexroth driver | 1.8.4 |
| Danlaw | 2.12.3 |
| Estic driver | 1.2.0 |
| FANUC CNC Driver | 2.0.3 |
| Fanuc driver | 2.3.3 |
| GPS | 1.0.4 |
| Industrial driver | Updated with each release |
| Ingersoll Rand driver | 1.4.0 |
| Kawasaki | 1.4.0 |
| Keyence | 1.0.6 |
| 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 | 1.0.1 |
| Melsec | 3.5.7 |
| Mitsubishi driver | 3.3.7 |
| Modbus driver | 2.11.5 |
| Modbus Server driver | 1.1.8 |
| Modem | 1.5.1 |
| MQTT driver | 2.1.9 |
| MTConnect driver | 1.3.3 |
| NMEA GPS | 1.0.4 |
| OAuth2 | 2.3.2 |
| Omron driver | 3.8.2 |
| OPC-UA Client driver | 3.1.22 |
| ROC Plus driver | 2.0.3 |
| Rockwell ControlLogix driver | Updated with each release |
| Schneider Electric | 2.9.0 |
| Siemens S7 driver | 3.0.5 |
| SNMP driver | 1.1.1 |
| Sparkplug B | Included and Updated as part of MQTT |
| Stanley Tools driver | 1.3.0 |
| Sturtevant Richmont driver | 1.8.4 |
| Sysmon | 1.0.2 |
| TCP Listener | 2.4.0 |
| Toyopuc | 1.0.5 |
| TR50 | 2.6.2 |
| deviceWISE View | 2.3.7 |
| Technology Preview | |
|---|---|
| Device Driver | Version |
| Amcrest | 1.0.1 |
| AWS SiteWise | 1.0.3 |
| BACnet / IP driver | 3.2.12 |
| Barcode Scanner | 1.1.1 |
| CODESYS driver | 1.0.0 |
| CTI (Control Technologies Inc.) driver | 2.1.5 |
| 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) | 1.0.0 |
| HAAS | 1.0.0 |
| GrovePi driver(Only in Raspbian directory) | 1.0.2 |
| HTTP Server | 1.0.1 |
| J1939 IXXAT device Driver | 1.1.1 |
| JSON | 1.0.0 |
| Melsec | 1.0.1 |
| Nachi – (Windows Only - Win32 and Win64) | 1.0.0 |
| 1.0.1 | |
| OPTO22 | 1.0.0 |
| Sandbox | 1.3.0 |
| Serial | 1.3.0 |
| SICK CLV Scanner | 1.1.7 |
| Simulation | 1.0.0 |
| Telit SmartIO | 2.2.1 |
| Trending | 1.3.14 |
| Visual Inspection | 1.0.12 |
| Virtual | 1.3.0 |
| Xirgo | 1.3.0 |
| Zaxis (only built for Windows products) | 1.0 |
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.