deviceWISE IoT Gateway 22.04 Release Notes

A number of improvements and fixes were added to the IoT Gateway 22.04 release.

Summary:

The 22.04 release includes many new updates like, Mitsubishi Driver optimizations, IFM IO-Link device control, the release of deviceWISE for the Chinese market, of an Asset Gateway for Generic ARM64 and a Simulation device. The 22.04 release also has fixes for issues that caused the product to restart.

Production Release Date: December 2022

New features and enhancements to existing features

Workbench

[MAP-17885] -"Recent" group was added the node list tree
Description: A tabulated list of the recent nodes was created to make the access more efficient, mainly for those who work with many nodes in the Workbench.
[MAP-17926] -Trigger comment block color/font size customization
Description: Users are now able to set font scaling in trigger comments.
[MAP-17833] -Automatically link and position actions by dropping on top of an existing action
Description: To improve UX, the new update features an automatic link and position to actions that are dropped on top of existing actions, making the process of wiring actions easier and more efficient.
[MAP-17872] -Transport Map and Device Definition editors now nonmodal
Description: The behavior of the Transport Map and Device Def editors are now similar to the Trigger editor, less complicated and more intuitive.
[MAP-17903] -Trigger Function Visuals were refactored
Description: The trigger editor had its visuals modified to better use space and offer a better presentation.
[MAP-18053] -Added search to context menu/toolbar
Description: The 22.04 release features the ability to search for all instances of an action type in the trigger and quickly look at the parameters used in each instance.
[MAP-18148] -Trigger Editor User Interface updated
Description: Visual changes were made to the trigger editor, offering new icons and a new layout.
[MAP-17930] -Add deviceWISE release level column to node list panel
Description: A new column for deviceWISE release level was added to the node list panel.
[MAP-18007] Update the Workbench to run on OpenJDK
Description: Update the Workbench to run on OpenJDK.

deviceWISE View

[MAP-15987] -Username and Password fields now follow the theme
Description: Now, just like the node field, the username and password fields coloring change with the theme.
[MAP-18097] -Default priority property now available
Description: New property created and available to control the deviceWISE view Subscription Priority. Prior to this release, all subscribed variables were using 50 ms Priority. The default priority is now 5 seconds (5000ms). The name of the property to overwrite this default priority is named variable.service.default_priority, the possible settings are as follows: 1 for 50 ms, 2 for 200 ms, 3 for 500ms, 4 for 1000ms, 5 for 5000ms, 6 for 15000 ms, 7 for 60 seconds, 8 for 5 minutes, 9 for 10 minutes, 10 for 15 mins. Add this property to the user.platform.properties. For example, for the default priority to be 1000ms, it is needed to set the variable equals to 4. In the next release, each variable will have its own subscription priority.

deviceWISE Runtime

[MAP-18185] -Add IMEI as a hardware ID
Description: Add IMEI as a hardware ID.

[MAP-18078] -Release Asset Gateway for Generic ARM64
Description: Release Asset Gateway for Generic ARM64.

[MAP-17838] -Critical CVE update for openssl
Description: openssl was updated from 1.1.1l to 1.1.1q.

[MAP-17896] -Modem Manager Updates
Description: New properties added to the Modem Manager, allowing for a property file that will not overwrite the pppd options, more efficient navigation and more stable use.
[MAP-17890] -Modem now provides a better feedback about SIM
Description: The driver was optimized to facilitate debugs and day to day use of the SIM card.
[MAP-17960] -Docker now runs as non-root
Description: In the past, Docker ran as root, in this release it now runs as non-root.
[MAP-18093] -User operation event (cloudlink based) was removed
Description: Cloudlink is no longer supported. Therefore this event was removed.

Transaction Server

[MAP-18236] -SOAP Transport Map Issues
Description: An issue with the ability of limiting the range of an arrayed field was found and fixed.
[MAP-17932] -Add Transport Map name into the Mapping Logs
Description: Add Transport Map name for all Transports to the Mapping Logs. This allows for filtering by Transport Map.

Drivers and Extensions

[MAP-18082] -Modem Manager now displays the full firmware version for Telit radios
Description: Modem Manager now displays the full firmware version for Telit Radios.

[MAP-17758] -MC Protocol Driver for IQR - New Dev Type RCPU in addition to RCPU (Build In Ethernet)
Description: The driver was improved to clarify how deviceWISE is connected to IQR CPU, via the built-in ethernet port or using an adapter, RJE71.

[MAP-17874] Tool Offsets and System Variables were implemented with Fanuc CNC Driver
Description: Tools Offsets and System Variables access are now supported.

[MAP-18005] -Maximo Schemas and Queries are now visible if advanced properties are selected
Description: In the past we showed all schemas and queries. In this release we only show the basic connection parameters, like url, authentication key and credentials.

[MAP-17871] -Update on the System Monitor Device
Description: All variables under the System Monitor device are now labeled as Read-Only in theDeviceWise Variables.

[MAP-18177] -Handling "Total Variable Count" for Rockwell devices
Description: An improvement was made to avoid cases where the device is started but the tags are not numerated. A check was added to the attributes tab so that, if the "Total Variable Count" is equal to 0, then it is not allowed to start.

[MAP-17441] -

Simulation Extension is available

Description

[MAP-18144] -Optimize MC Protocol Mitsubishi Driver
Description: The Mitsubishi Driver (MC Protocol/SLMP) has been optimized for speed. It implements a block read in addtion to the batch read (default). When in Block mode the performance of the driver increases dramatically as in one I/O request can request many distinct items from the PLC. It is recommended to leverage this driver by updating the mode from batch to block.
[MAP-17633] -Update to the dwmelco driver
Description: Now the dwmelco driver (Windows 64/32) with new ExSocket supports IQR WinCPU.
[MAP-17917] -IFM IO-Link now support writing
Description: IFM driver was updated to allow control of sensors, like a stack light for example.
[MAP-18259] -Update on the AWS IoT Core Extension
Description: The AWS IoT Core Extension MAX Build moves from Tech Preview to GA Folder.
[MAP-17983] -Input value is now formatted to match the user input
Description: The original algorithm was improved to convert a String into a Float8.
[MAP-18292] -Universal VC Runtime Installers provided for Windows Products
Description: Windows installers are now incliding visual studion 2013 redistributable runtimes. Some drivers depend on these redistributables to be present. Customer does not have to install them as they are included and installed during deviceWISE installation..
[MAP-18190] -UPC UA Server/Clients now allow an unlimited number of monitored items setting
Description: The OPC UA Server and OPC UA Clients are now allowed to support an unlimited number of monitored items.
[MAP-18092] -Rockwell SLC500 speed optimizations implemented
Description: Legacy Rockwell Driver was optimized for speed. SLC500, PLC-5, Micrologix. The driver now groups items in one read request yielding speed improvements particularly in serial type communications.
[MAP-18009] -Added new variables to the Nachi Robot
Description: The variables X, Y, IO and D were added to the Nachi Robot driver.
[MAP-18046] -Modem Manager now support automatic port discovery for Telit
Description: Automatic discovery is now allowed to finding ports like ttyACM or ttyUSB.

Issues Fixed on the 22.04 Release

Workbench

[MAP-18120] -Variable Goup Item list was missing scroll bars
Description: Variable Goup Item was missing scroll bars, the issue was fixed at the present release.

[MAP-18303] -Gaps showing in the Trigger Action categories
Description: A fix was done to the aesthetic on the Categories of the Trigger Actions, which were showing gaps.
[MAP-18036] -Issue with deviceWISE_Backup_Utility_Installer
Description: deviceWISE was crashing because of a Backup Utility Installer, the bug was found and fixed.
[MAP-17935] -Issues exporting large trigger reports
Description: Fixed issue that made the Workbench bug when trying to write a large trigger report.
[MAP-18286] -Null alert values causing errors
Description: In occasion, an alert value resolves as null, which then created an error processing of the alert table. The issue was fixed with this release.
[MAP-17933] -Mapping Logs Panel persists
Description: The Mapping Logs Panel were persisting from previous node values when there was an item selected during node switch. The issue was solved after diagnosis.

deviceWISE Runtime

[MAP-17990] -Opto 22 Driver was crashing when reading 2 items
Description: Issue with Opto 22 Driver was addressed.

[MAP-18064] -Mutex Deadlock error in DW 22.03 and 21.10
Description: Issue with the btree lock not being released when reference find cannot get a reference, the problem was addressed and solved.

[MAP-18083] -Mutex Deadlock in AsyncSocketHandler
Description: The lock was attempted after the mutex was deleted.The issue was addressed.

[MAP-18012] -Message to Azure IoT is going to 'Overflow Count'
Description: It was detected that, in occasion, a trigger that is Sending Telemetry to IoT hub, goes to overflow, taking 122053ms (in opposition of 44ms in normal occasions). A diagnostic was found and a fix was made.
[MAP-18242] -Error converting number with scientific notation from string to integer
Description: An issue was found converting numbers represented in scientific notation. A fix was found and is now available on this release.

[MAP-18051] -TSL Warning when Perpetual TSL is Applied
Description: There was notified that when perpetual technical support license was applied to the node, a warning message appeared at the bottom of the Workbench, indicating that the license was expired. This issue was fixed.

[MAP-18138] -deviceWISE crashing while Starting a trigger
Description: When trying to start ReadMachineData, deviceWISE was restarting. The issue was diagnosed and solved.
[MAP-17878] -Tr50 high latency network timeout issues
Description: Optimized the TR50 timeout settings to minimize latencies issues.
[MAP-18243] -Gateway Node not starting up after manual node restart
Description: A fix was done to the Gateway Node, which wasn't starting up after a manual Node Restart.
[MAP-18273] -Issue with libevent when starting up the core
Description: An issue was being faced when starting up the core, the libevent problem was identified and fixed.
[MAP-18228] -Local DB batch count now visible on the regular properties
Description: Local DB batch count taken out of theAdvanced Properties and available on the regular properties listing.
[MAP-18210] -Wait action taking too long
Description: An issue with the trigger report response was found and fixed.
[MAP-18275] -Windows NT (32-bit) fails to install, unable to start up core when running the installer
Description: When running the deviceWISE installer, the installer stalls on starting up the core, eventually failing. The root problem was found and fixed.
[MAP-18189] -Problems with "Thread pool overflow" erros
Description: It was detected an intermittent issue with Thread Pool Overflow errors, causing timeouts in SAP ME, the issue was addressed and fixed.
[MAP-17995] -Wrong result when comparing an empty string to a value
Description: Comparing an empty string with a variable set to any value returned True instead of False. The issue was diagnosed and fixed.

deviceWISE View

[MAP-18309] -Changing display name causing errors
Description: Added validation for the Name Change, fixing issue that generated Object Not Found error.
[MAP-18080] -Bindings not solved, deviceWISE View not working
Description: When trying to connect to pages, bindings were getting slow to fix and the user was logged out, an update was implemented and the problem was fixed.
[MAP-18171] -Changing space padding in deviceWISE View leads to a bug
Description: When changing spacing padding, a bug was found, capable of making elements lose its values. The issue was detected and solved.
[MAP-18115] -View taking to long to display variables values
Description: It was found a big latency in view. A fix for melsic driver fixed the problem.
[MAP-18103] -invalid session/connection interrupted
Description: An error with an invalid session claim was occurring, a fix was made and the issue was solved.

Tunnel Manager

[MAP-18042] -Tunnel not opening
Description: VNC Tunnel appeared as open, but did not work. The specific issue was found and the problem fixed.
[MAP-17876] -Gateway Connectivity Issue
Description: Modem Manager wasn't able to connect sometimes, the problem was fixed with a dwmodem manager redesign.

Drivers and Extensions

[MAP-17895] -Memory leak at the AWS SiteWise
Description: It was found a problem with the connection to siteWISE, making it unstable, it was traced to a Memory Leak of AWS siteWISE and it was fixed.

[MAP-18260] -Problem with the TCP Listener
Description: Fixed a bug with the new libevent that affected some Linux and TCP Listeners.
[MAP-18271] -CompactLogix cannot read string variables
Description: Fixed a bug that impeded CompactLogix of reading string variables.
[MAP-17820] -deviceWISE crashing when reading or writing from Local IO Device
Description: Solved the bug with deviceWISE crashing when attempting to read/write from the local IO Device.
[MAP-18050] -Issues with listeners
Description: Issues with the Listener not releasing licenses has been resolved.
[MAP-17941] -AWS Iot Hub not properly managing arrays of strings
Description: An issue with the code path was found and AWS IoT Hub is now able to correctly manage arrays of strings.
[MAP-18057] -OPC UA Client fails when attempting to connect to the 26th OPC UA Server
Description: There was a problem identified when intending connection with more then 25 servers. The diagnostic was made and the problem was solved by lifting the limit of servers allowed to connect.
[MAP-17998] -MTConnect hanging system when communicating to invalid adapters
Description: MTConnect driver was failing to detect errors and disable the device. The issue was detected and fixed.
[MAP-18031] -Cellular modem manager connect/disconnect few times crashes the node
Description: The Cellular Modem Manager was facing some crashes when connection and disconnection was performed. The disconnect script was updated and the bug was fixed.
[MAP-18027] -OPC UA Enumeration - XML file not created
Description: It was noticed that the XML file, containing tag trees, weren't being generated in some situations. This issue was fixed at this release.
[MAP-17905] -HTTP settings exported weren't being honored during import
Description: An issue was found when exporting HTTP settings from the Admin panel, there, the import wouldn't honor the state. The problem was solved at this release.
[MAP-17556] -device Export fails with Bacnet
Description: Bacnet device export was failing, implying a missing file. The root of the problem was found and a fix was provided at this release.
[MAP-17928] -Azure Event IoTHub Method caused crashes on deviceWISE
Description: The IoTHub Method event of Azure was causing deviceWISE to crash. The issue was diagnosed and resolved in this release.
[MAP-18136] -Modem Manager was not restoring Modem to command state
Description: Existing chat script was not restoring the data port back to the command mode. This issue was fixed at this release.
[MAP-18081] -Error -50037 with the Microsoft Azure IoT Hub trigger event
Description: When a rapid fire of events a concurrency error took place. The issue was diagnosed and addressed.

Supported Driver Versions

Generally Available
Device Driver	Version
AcraDyne driver - Updated in 22.03	1.1.3
Advanced Display Protocol	1.0.1
Allen-Bradley (Rockwell Automation) - updated in 22.03	2.20.0
Apex Cleco driver - updated in 22.03	1.9.3
Atlas Copco driver - updated in 22.03	3.6.4
Azure	2.1.7
Beckhoff driver	2.1.8
Danlaw - updated in 22.03	2.12.3
Estic driver - updated in 22.03	1.1.3
FANUC CNC Driver - updated in 22.03	1.3.1
Fanuc driver	2.3.2
Industrial driver	Updated with each release
Ingersoll Rand driver - updated in 22.03	1.3.3
LDAP – do not use with Linux X86 in versions 21.10 and later	1.1.1
Lua - updated in 22.03	1.1.3
Mitsubishi driver - updated in 22.03	3.3.7
MindSphere – do not use with 22.01 and later	2.0.4
Modbus driver - updated in 22.03	2.11.0
Modbus Server driver	1.1.8
Modem	1.5.1
MQTT driver - updated in 22.03	2.0.9
MTConnect driver - updated in 22.03	1.2.11
NMEA GPS - updated in 22.03	1.0.4
OAuth2 - updated in 22.03	2.3.1
Omron driver- updated in 22.03	3.8.1
OPC-DA Client driver - updated in 22.03	2.7.1
OPC-DA Server driver - updated in 22.03	1.3.0
OPC-UA Client driver - updated in 22.03	4.1.4
OPC UA Server - updated in 22.03	1.2.3
Rockwell ControlLogix driver	Updated with each release
Schneider Electric	2.9.0
Siemens S7 driver	2.11.2
Stanley Tools driver - updated in 22.03	1.1.3
Sysmon	1.0.2
TCP Listener- updated in 22.03	2.3.8
TR50 - updated in 22.03	2.6.0

Pilot Ready
Device Driver	Version
Bosch Rexroth driver - updated in 22.03	1.8.3
ROC Plus driver	2.0.2
SNMP driver - updated in 22.03	1.1.1
Sturtevant Richmont driver - updated in 22.03	1.8.3
deviceWISE View - updated in 22.03	1.6.0

Technology Preview
Device Driver	Version
AWS - updated in 22.03	0.2.5
AWS SiteWise - New in 22.03	1.0.1
BACnet / IP driver- updated in 22.03	3.2.7
Barcode Scanner	1.1.0
CODESYS driver - updated in 22.03	0.6.2
CTI (Control Technologies Inc.) driver	2.1.4
Dell Edge Gateway (Linux 64-bit)	0.5.0
EDU (not built for Windows 64-bit)	1.0.0
E-Sensors	1.0.0
File Watcher	1.0.4
Google Cloud Platform (GCP) - updated in 22.03	0.3.3
GrovePi driver(Only in Raspbian directory)	1.0.1
HTTP Server	0.7.0
IBM Maximo Enterprise Asset Management	1.1.1
IFM-IOLINK - New in 22.03 for Generic Windows and Generic Linux	0.5.0
J1939 IXXAT device Driver	1.1.0
JSON	0.5.2
Kawasaki	0.6.3
Nachi – (Windows Only - Win32 and Win64)	0.5.0
ScanTools OBD-II	1.0.0
OPTO22 - added in 22.03	0.0.2
Pepperl+Fuchs	1.0.1
Sandbox - updated in 22.03	1.2.1
Serial	1.2.1
SICK CLV Scanner- updated in 22.03	1.1.6
Telit SmartIO	2.2.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 22.04

Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 22.04 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 22.04

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 22.04, you will need to add all device drivers and extensions from the new release level.
Restore your node.

Upgrading a Windows Enterprise Gateway product from 19.1.6 or later to 22.04

A firmware update from a release for Enterprise Gateway for Windows before version 19.1.6 to 22.04 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 22.04, you will need to add all device drivers and extensions from the new 22.04 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 22.04 (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 22.04, 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 22.04, you will need to add all device drivers and extensions from the new 22.04 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 22.04 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 22.04

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 22.04

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 22.04, you will need to add all device drivers and extensions from the new 22.04 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 22.04

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 22.04, you will need to add all device drivers and extensions from the new 22.04 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 22.04, 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 22.04, you will need to add all device drivers and extensions from the new 22.04 release level.

A firmware update from 16.1.8 or earlier to 22.04 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.