deviceWISE IoT Gateway 24.03 Release Notes
A number of improvements and fixes were added to the IoT Gateway 24.03 release.
Summary:
The 24.03 release includes improvements made to the Workbench, deviceWISE View, Transaction Server and multiple drivers.
Production Release Date: October 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-21906] -Pasting into value cell in action editor can retain trailing newline
Description: Fix issue where pasting into text field may retain trailing newline characters.
deviceWISE View
- [MAP-21587] -Set default Font Size Flag to 'vh' Instead of 'em'
Description: Default font was updated to 'vh' Instead of 'em'. - [MAP-20677] -VI widget - Naming of detected objects is currently under Defects
Description: Renamed the defects in the properties window of the VI widget. - [MAP-20570] -Default to Today's Date/Time in Write Value Date Input
Description: Added default data time. - [MAP-21763] -Remove IBM Widget (no longer supported)
Description: Removed IBM VI Widget (no longer supported). - [MAP-21750] -deviceWISE View Home Display for a user
Description: Added capability to configure home display for the user. - [MAP-15977] -Editor should be floatable/dockable and larger when undocked
Description: Editor updated to floatable/dockable and larger when undocked.
Transaction Server
- [MAP-21895] -Feature Request-Updating Synonym Table on Oracle Database
Description: Added preliminary ability to use Oracle Synonym tables in transactions via the ENABLE_SYNONYMS=true setting in dwjava\dwconfig.properties.
deviceWISE Runtime
- [MAP-21533] -FFMPEG/RTSP -- Image capture should allow image to memory in addition to file (like it is now)
Description: FFMPEG driver can now write captured image to internal memory buffer instead of writing to disk. - [MAP-21345] -Random number generator action should support FLOAT4 and FLOAT8
Description: Added float4 and float8 support to random number generate action to the Generate Random Number Trigger Action. Unlike other datatypes, there are no min nor max values for the floats, seeing that it is very platform dependent. - [MAP-20480] -Feature request: Action Blocks to stop, start and control the HTTP Server
Description: Action: New Action added: HTTP Server Control to Start/Stop the HTTP Server.
Drivers and Extensions
- [MAP-21530] -AMCREST Camera now previews camera snapshots
Description: Added admin panel to Amcrest driver to preview camera snapshots. - [MAP-21528] -Implement Adaptive settings in UA Client (see description)
Description: During the browse of a node the OPCUA Client will attempt to read values with a maximum number of items set to 1000 (adjustable). If the read fails then the children to that node will not be added. To overcome this the driver will reduce the number of items in a single read by half and try again. The maximum read quantity will continue to half until it is reduced to 1. - [MAP-21443] -Support symbols for S7-300 and S7-400
Description: dwsiemens: Updated driver to provide db support for S7-300/S7-400 PLC types. - [MAP-20954] -Create Combined DA Client + DA Server
Description: Implement the new driver to replace the existing OPCDA Client and OPCDA Server drivers. - [MAP-20849] -ABB Flow X optimize tag reading
Description: Added lazy loading to the driver to optimize loading of the tags. The loading of the tag id's is done on the first load, then variables are loaded using lazy loading. - [MAP-20834] -ABB Flow X Archives
Description: Added an event to return the snapshot name when a new archive is generated. The shanpshot name is then used in the report action to retrieve the snapshot from the FlowX meter. - [MAP-20833] -ABB Flow X Reports
Description: Added an event which is fired when a new report is generated. The event is used to call the Report action to read the new report from the FlowX meter. - [MAP-20739] -IP Variable in Siemens Event Data includes Port No
Description: dwsiemens: Removed port num from ip addr field in Siemens(TCP Send) Event Data. - [MAP-21301] -OPC UA Alarm Events
Description: Added new feature for Alarm Events. - [MAP-21654] -OPC-UA Historical Access
Description: A new action has been created to read the historical data from an OPC UA node. - [MAP-21830] -Misc Updates for FFMPEG/RTSP Camera Driver
Description: FFMPEG various cosmetic improvements. Device can be static or dynamic using a input variable for device name. - [MAP-21967] -Memobus driver is now a Tech Preview driver
Description: Memobus driver is moved to tech preview from Internal.
Issues Fixed on the 24.03 Release
Workbench
- [MAP-21476] -Report popout windows register as editors, give warning on exit if open
Description: Prevent detection of open report windows on Workbench exit issue was fixed. The workbench were warning if a user was trying to close with editors open. Report popout windows register as such and cause this warning. The issue was fixed and the behavior corrected. - [MAP-21561] -Watch window: same variable as two different types only graphs it once
Description: Fixed issue in watch window trending same variable as two different types. - [MAP-21790] -Date and Time Mismatch
Description: Fixed inconsistency in report timestamp values in certain timezones. - [MAP-21766] -Object lock fails in transport list panel when validation of transport times out
Description: Fixed an OPC UA browse error where Client was crashing due to too many results being returned from history read. - [MAP-21832] -deviceWISE Workbench - Column Spacing
Description: Fixed column spacing in trigger action editor panels. It will now pack table to maximize variable column space and maintain any user changes to column size for that edit session.
Transaction Server
- [MAP-21803] -Http transport inserting linefeeds in long authorization strings
Description: Fixed encoded issue with http authentication parameters longer than ~80 characters. - [MAP-21810] -HTTP Transport - Set SSL parameters as optional
Description: Corrected issue in 24.01+ transaction server where https connection does not use default SSL when no key/trust stores defined in transport. - [MAP-21728] -"System Error -4313" on Listeners Page
Description: Fixed error -4313 from transport listing command.
deviceWISE View
- [MAP-21525] -dwView does not properly interpret the Modbus Variable list
Description: Fix to update Modbus Variable list from the variable picker. - [MAP-21454] -View - Gallery - hit and miss prompting update gallery dwView version
Description: Add fix to enable prompting update of gallery version. - [MAP-21237] -INT 8 variables not being correctly displayed
Description: Fix INT 8 variables not being correctly displayed. - [MAP-21511] -X axis Categories not working on Line Chart
Description: Fixed X axis Categories not working on Line Chart and applicable for single dimension array. - [MAP-20450] -Trending Widget: Gap in data when device offline breaking graph
Description: Trending Widget fixed Gap in data when device goes offline. - [MAP-21609] -Lazy enumeration for 'ABB Flow-X' and 'DA Client' device types
Description: Fix Lazy enumeration for 'ABB Flow-X' and 'DA Client' device types. - [MAP-21603] -Table and SQL table are not able to scroll like before
Description: A fix was done to Table and SQL table, restoring their ability to scroll as expected. - [MAP-21454] -View - Gallery - hit and miss prompting update gallery dwView version
Description: Add fix to enable prompting update of gallery version. - [MAP-21847] -DW View should warn if javascript is not enabled
Description: Added warning if javascript is not enabled. - [MAP-21903] -View not showing error description
Description: Correct error message is shown when user tries to use dwView without license. - [MAP-21734] -Float4 and Float8 variable types show different outputs for the same value
Description: Subscribing float4 had a chance of displaying a different value. The product's json output was only based on float8, when a float4 convert to float8, the decimal representation could be different. As a fix, it was added float4 native support to json, so now, it will have the same decimal representation.
Visual Inspection
- [MAP-20900] -Inference trigger on Windows x64 has reliability issue
Description: Issue when reading images on Windows platform fixed. - [MAP-21304] -Multiple widget move allows for widget overlay in the same layer
Description: Fix to multiple widgets being overlaid if they are set to the same layer. They won't overlay anymore, only if brought to different layers. - [MAP-21592] -VI - when training and here is not sufficient memory in the GPU, the UI spins forever and there is no indication
Description: Visual Inspection now has a Timeout to avoid issues with insufficient memory in the GPU. - [MAP-21718] -Date Time mismatch between gallery package and web application help menu
Description: Removed the time stamp from the help, only the version will be displayed. - [MAP-21710] -VI -- should indicate where it is running from. See Description
Description: Fix the installer.sh. When installing dwvi, it saves a file to /tmp/devicewise_vi_install_location.txt that indicates the install location. - [MAP-21627] -Unable to write the output of VI Inference action to a Virtual device variable
Description: Before, the output variable Status, the action would end with an error saying the the Status variable was not serviced and did not have data. That has been fixed. - [MAP-21733] -The dwView rounding up a max value in INT8 causing data integrity issues
Description: Added fix in dwView rounding up a max value in INT8. - [MAP-21270] -Value Card supports only numbers on Float variables
Description: JSON library didn't support floating point exponential form. To fix the issue, the support to floating point exponential form was added.
deviceWISE Runtime
- [MAP-21404] -Node crashes with signal[11(Segmentation fault)] in Siemens driver
Description: dwsiemens: Added indirect_get and listener code cleanup to avoid invalid access on device pointer. - [MAP-21343] -Random number generator action INT4/INT8 never generates a positive number
Description: Random number generator never generates full range of values for INT4 and INT8. Problem only occurs if the difference between min and max is very big. - [MAP-21801] -OPC Client crashes when too many results are returned from history read
Description: The history read action may cause a crash when the results from the OPC UA Server are more than the requested quantity [CHANGE]. - [MAP-21799] -Case Audit log entries in Debug.log does not have user information (name)
Description: username is now added to the audit messages in debug.log. - [MAP-21588] -System Hang Due to Memory Usage
Description: Fixed a subscription memory leak when subscribing to a variable that's not available or not found using HTTP api/dwview. - [MAP-21200] -Node Crashed unexpectedly
Description: Fixed a double free when multiple data-publish timeout at the same time, all of them were trying to delete the same btree at the same time. - [MAP-21805] -PeerLink does not properly enumerate when using latest OPC UA/DA clients on remote node
Description: Peerlink can now handle remote device that uses lazy enumeration(eg OPCUA, AbbFloxX). - [MAP-21816] -ffmpeg directory must be created upon package installation
Description: FFMPEG will now create a ffmpeg directory in the staging browser where image files will be stored. - [MAP-21831] -Segfault crash when trying to load the Azure:SAF module
Description: A fix was applied to avoid crashes. - [MAP-21935] -RTSP FFMPEG Camera driver -- absolute path not working
Description: FFMPEG can now save an image to absolute path when the setting is used in the capture action. - [MAP-21605] -Data Trending does not prune tables if node is not running at midnight
Description: To fix the issue where Data Trending was not pruning tables by midnight if deviceWISE wasn't running at that time, it is checked every hour instead of 12am everyday. - [MAP-21383] -Drop table issue - dwcore off when scheduled drops start
Description: To fix the issue where Data Trending was not pruning tables by midnight if deviceWISE wasn't running at that time, it is checked every hour instead of 12am everyday. - [MAP-21671] -Crash of 24.02.11
Description: Fixed a series of internal issues that caused crashes on the 24.02.11. First an issue with the read/write returning 0; Second a crash due to a limit of device name size (32 characters); Third, bad information being returned to Enhanced Demand Read/Enhanced Demand Write if the user supplied a name of the var that didn't exist.
Drivers and Extensions
- [MAP-21669] -Nachi - Diagnostic Read Error
Description: The Nachi diagnostic read will now have the axis number editable. The deault number is 6 unless otherwise set. To edit it, access the Advanced Properties while defining/modifying the device. - [MAP-21624] -Local CPU 0 Not Showing Up in Devices After Power Cycle
Description: dwrcl: Updated cpu.locate.delay default value to 5000 to fix a local CPU removal issue when the PLC is busy. - [MAP-21611] -CNCNetPDM not recognizing T_DOUBLE as FLOAT8
Description: Correct conversion from CNCNetPDM T_DOUBLE to deviceWISE FLOAT8. - [MAP-21552] -Nachi driver -- fails to read many variables
Description: System version added to device attributes and displayed upon device start. - [MAP-21713] -OPCUA Client Server crash when browse size is reduced after browse error
Description: When an OPC UA Server returns an error during a read request during a browse, the maximum number of variables to read is reduced. This could lead to a crash when the enhanced demand read action was used. Now, when this error occurs the OPC UA server will adjust the number of points to read and then attempt to read again. - [MAP-21707] -OPC UA Client Server - device deadlock when stopping
Description: Fixed a deadlock problem between new OPC UA and demand read action. If the demand read/write happens right after the device going from started stated to stopping state. The device stays "stopping" forever. Restart was the only solution. That tiny windows is now closed by properly dereferencing the use count. - [MAP-21141] -Local Inference not working. The image filespec is not complete
Description: Add capability to read VI images from staging directory of the http server. - [MAP-21759] -OPCDA Client Server crashes dwcore when COM fails in server start
Description: When a COM error occurs while trying to connect to an OPC Server a crash may occur in deviceWise. - [MAP-20215] -Node Crash: When Stopping OPC DA client:: got stuck in Stopping state
Description: This driver has been replaced by the combined OPC DA client server driver. - [MAP-21040] -MQTT - It's not possible to copy MQTT triggers when they fail to validate
Description: Trigger that contains MQTT subscribe event can be exported/saved even with device stopped.
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.12 |
| 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.1 |
| 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.5 |
| 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.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.3 |
| SNMP driver | 1.1.1 |
| Stanley Tools driver | 1.3.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.2.4 |
| 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.