deviceWISE IoT Gateway 24.04 Release Notes
A number of improvements and fixes were added to the IoT Gateway 24.04 release.
Summary:
The 24.04 release includes improvements made to the Workbench, deviceWISE View, Transaction Server and multiple drivers.
Production Release Date: December 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-21972] -Open URL from Workbench button
Description: Added new weblink field for generic panels. - [MAP-22071] -Maintain correct order of recent nodes on restart
Description: Corrected ordering of recent nodes on Workbench startup. - [MAP-22055] -Allow Start/Stop via double mouse click with modifiers
Description: Added ability to Start/Stop definitions in major list panels using shift-doubleclick to start and ctrl-doubleclick to stop. - [MAP-22161] -Add QoS and Retain for Sparkplug B -- rename existing QoS to priority
Description: Added new options for SparkplugB configuration. - [MAP-22324] -Allow trend pane to be hidden in watch window
Description: Adjusted watch window to allow trend panel to be hidden/maximized. - [MAP-22312] -Allow organization to be set in portal login panel
Description: Allow user to optionally set organization during IoT Portal login. - [MAP-16315] -Device definition should have a description
Description: Added description field to device editor. - [MAP-14856] -Popout Note Window
Description: Added ability to open a node standalone in a separate Workbench instance.
deviceWISE View
- [MAP-22234] -Duplicating a Widget Should Automatically Select the New Widget
Description: When duplicating a Widget, the new one will be automatically selected. - [MAP-22233] -Widget Canvas Should Support Layering
Description: Added support for Layering on Widget Canvas. - [MAP-22232] -Layers Tab Only Hides Widgets that are in a 'Default' State
Description: Fixed Layers Tab Only Hides Widgets that are in a 'Default' State. - [MAP-22239] -Introduce 'Layers' tab in Widget Settings
Description: Added 'Layers' tab in Widget Setting.
Transaction Server
- [MAP-21073] -Concern on Time Format used in Transport Map between Windows and Linux servers
Description: Removed "Internal Time Format" action property from "Get Date Time" action to avoid confusion. The property originally created for Siemens ERPC which does not have GMT hardware clock. This special property allowed to traverse the Local Time back into GMT. ERPC is no longer supported; thus removing this property. Existing triggers using this property will not be affected, new triggers can no longer select the "Local Time" option, GMT will be the default for new triggers.
deviceWISE Runtime
- [MAP-21817] -Support Escape special reserved characters from variable and device names
Description: Certain characters including [ ] \ . are reserved and restricted, so it fails to create the variable with an invalid name. Now the restriction is removed. This change is slightly different than MAP-21902 mentioned bellow. This change applies to device variables instead of an action. The same resolution was given to MAP-21653. - [MAP-21653] -Action Metadata Json/Http processing not accepting brackets in keywords
Description: Similar to MAP-21092 - Certain characters including [ ] \ . are reserved and restricted, so it fails to create the variable with an invalid name. Now the restriction is removed. - [MAP-21994] -Modem manager has to support Quectel EM05-G
Description: Added Quectel EM05-G as supported modem. Auto enumeration should work now. - [MAP-20906] -Add S&F support to an HTTP client action
Description: Added store and forward to HTTP Client action. The HTTP Client action will have 1 more action property "SAF Profile", just like the remote trigger action.
Drivers and Extensions
- [MAP-22124] -CNCnetPDM - Add variable read when AquisitionMethod=2
Description: CNCNetPDM supports AcquisitionMode 2. - [MAP-22000] -Compression/Decompression Action
Description: New actions to compress and decompress strings have been added. - [MAP-22092] -AWS IoT Core --- Publish Topic should be dynamic, just like MQTT Publish Topic is
Description: Topic can now be a input parameter in the publish action by putting $(Topic) in the publish action's Topic parameters. - [MAP-22152] -Support Keyence KV500 PLC
Description: dwkeyence: Added variable ranges for x500 series plc type
Issues Fixed on the 24.04 Release
Workbench
- [MAP-21936] -Lazy Enumeration devices cached forever -- "reload tree" needs to work
Description: Corrected issue with lazy enum device structures not updated on device restart. - [MAP-22177] -Empty global vars when editing triggers
Description: Global device was accidentally converted to Lazy enum device. The default mode of the global device was changed. The issue that was present after lazy enumeration was fixed by 24.04. - [MAP-22140] -Workbench Rendering tag tree in trigger editor incorrectly
Description: Corrected error in trigger action editor with variable tree nodes missing/repeating for lazy enumeration devices.
deviceWISE View
- [MAP-21987] -While in DWView display editor, the delete (trash can) button erases the entire display
Description: Removed the delete button from the toolbar - [MAP-21795] -Variable table missing for ABB Flow X device
Description: Variable with reserved character should be able to display properly now. - [MAP-22235] -Switching Between Widgets with States is Unstable
Description: Fix the defect switching between widgets with states not refreshing the properties panel. - [MAP-22221] -Arrays of timers issue
Description: Fixed issue in variable picker when browsing variables with array. - [MAP-18265] -States should not copy default values when defined (e.g. Text)
Description: States should not copy default values when defined (e.g. Text).
Visual Inspection
- [MAP-22142] -Double clicking on a widget in editor should open property panel
Description: Add support to open properties panel on double clicking on the widget.
deviceWISE Runtime
- [MAP-21984] -Node crashes while we set "missing properties" as "Ignore" in New JSON action
Description: Fixed a crash when there are consecutive unmapped items in the New JSON Encode action(dwjson). - [MAP-22218] -Network Parameter not populating
Description: The Mobile Carrier database is now updated to the latest from mcc-mnc.com. - [MAP-22251] -Timer event missing options for Pause and Resume
Description: Added options for Pause and Resume to the timer event filter. - [MAP-22240] -Basler fails to build on Linux
Description: The Linux x64 build was not working, it has been fixed. - [MAP-22229] -Pause is not working when pressed a second time
Description: The pause button was not working after it was pressed a second time. The issue was fixed. - [MAP-22217] -License being lost after deviceWISE service restart
Description: Added initial sync to acquire license on startup and avoid the issue from happening. - [MAP-22216] -VI Seg Fault
Description: Fixed issue where VI inference was trying to consume file with size of zero. - [MAP-21942] -AWS connector stuck in reconnecting state
Description: AWS Connector will reset itself after an amount of time in the Reconnecting state. - [MAP-22282] -Global Data is not cleared when deleting a Global Variables device
Description: Global Device will now delete persisted data on delete. - [MAP-22259] -Local DB delete Action
Description: The % character was used as a special one in the older version. A change was put into 24.04.07 ant it will no longer treat % any different from other characters. Now, the workaround (to add a preceding \ to % in the sql) is not needed anymore. - [MAP-22254] -Remove OPC self client connections from the OPC server
Description: Changed the OPC UA device admin tab to prevent the addition of OPC UA client devices that reference the internal OPC UA server. - [MAP-22335] -TSL Expiration
Description: Regression introduced in 24.03 whenthe error string (license panel) was changed for the expired TSL. However, the string is used in another place to calculate the TSL expiration day, and since the message has changed, it not longer returns the expected result. The problem was fixed by making the message global (same reference) so that the comparing will always be correct. It is cherrypicked into 24.04, and it can be back port to 24.03 if requested.
Drivers and Extensions
- [MAP-21902] -'Decode JSON' action does not map outputs with '.' in payload
Description: Certain characters including [ ] \ . are reserved and restricted, so it fails to create the variable with an invalid name. Now the restriction is removed. - [MAP-22136] -Multiple codes are duplicated in messages.nls.* files
Description: Corrected incorrect error messages for some error codes. - [MAP-22166] -OPC UA Client Setup w/ Certificates
Description: The advanced settings for OPC UA devices dedicated to allowing certificate errors to be ignored were not working properly, a fix was conducted and they are now producing the expected result. - [MAP-22097] -SparkplugB does not connect to AWS IoT core MQTT Broker
Description: AWS does not support the QOS setting used by the driver. This setting is now configurable and will default to the one supported by AWS. - [MAP-22271] -Basler capture not working for output type that do not support the quality setting
Description: Changed the capture action to remove the quality unless the output type is JPEG. - [MAP-22270] -Basler variable description shows unsupported enum types
Description: Changed the description for variables when the type is enumerated so that only supported enumerations are included. - [MAP-21907] -OPC UA Client - stops reading; reason unknown; requires restart
Description: Fixed an issue when there is a network issue by disabling the device. Fixed an issue when the device is disabled to prevent it from remaining in the "stopping" state. - [MAP-22220] -OPC UA server using security settings drops connections to UA client requiring a restart
Description: Fixed an issue when the device remains in the "Stopping" state after it has been disabled.
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 | 0.2.13 |
| 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.3.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 | 0.6.1 |
| Melsec | 3.5.6 |
| Mitsubishi driver | 3.3.7 |
| Modbus driver | 2.11.5 |
| Modbus Server driver | 1.1.8 |
| Modem | 1.5.1 |
| MQTT driver | 2.1.3 |
| MTConnect driver | 1.3.3 |
| 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.4 |
| 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.0 |
| Technology Preview | |
|---|---|
| Device Driver | Version |
| Amcrest | 0.5.1 |
| 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 |
| Nachi – (Windows Only - Win32 and Win64) | 0.7.2 |
| 1.0.1 | |
| OPTO22 | 0.0.5 |
| Sandbox | 1.3.0 |
| Serial | 1.3.0 |
| SICK CLV Scanner | 1.1.7 |
| Simulation | 0.5.2 |
| Telit SmartIO | 2.2.1 |
| Trending | 1.3.14 |
| Visual Inspection | 1.0.9 |
| 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.