deviceWISE IoT Gateway 23.03 Release Notes

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

Summary:

The 23.03 release includes changes made to the Workbench, deviceWISE View, runtime, IFM IO-Link, License Manager and many bug fixes.

Production Release Date: October 2023

New features and enhancements to existing features

Workbench

[MAP-19900] -Workbench doesn't show downloading package version information on update from context menu
Description: Added version information display in package update via context menu prior to download.
[MAP-19634] -Workbench panel layout improvement
Description: Workbench will now indicate when updates are available for the workbench, packages, and gateway firmware. Green dot will appear in the info menu when the workbench update is available. An asterisk will also appear after a package version as well, as an indication in the package info when an update is available. A green dot will appear in Node Administration panel when the gateway node update is available.
[MAP-19368] -Create Telit VI AI/ML Widget - new JSON Format
Description: Added Telit VI AI/ML Widget for Visual Inspection
[MAP-19592] -Allow for Replace from Trigger Search Results
Description: Added ability to replace values from search dialog.

deviceWISE View

[MAP-19325] -View should filter for started triggers returned by trigger_list service request
Description: Added filter to trigger based on the trigger status.
[MAP-19178] -Add configuration to enable/disable device data update during build mode
Description: Added Data Publish toggle button to the deviceWise view build tool bar , to enable/disable device data update during build mode. The configuration is not applicable to live mode and the configuration is not persisted, by default the toggle button is set to "Data Publish On" ,if the data publish is set to "Data Publish Off" the device data changes are not update on the widget
[MAP-19594] -AI VI Widget -- control the object line thickness
Description: AI VI widget added support to change defect and distance thickness.
[MAP-19597] -Logo change when clicking on the "Install app" tool of browser
Description: Logo change as the part of branding when clicking on the "Install app" tool of browser
[MAP-19599] -AI/VI Widget boxes color handling
Description: AI/VI Widget added support for annotated colors for defects and custom style for defects and distance.
[MAP-19716] -Add option to show/hide confidence percentage in the VI widget
Description: Added support to Telit AI/ML widget to show/hide confidence percentage.

deviceWISE Runtime

[MAP-19896] -Workbench doesn't show downloading package version information on update from context menu
Description: Added version information display in package update via context menu prior to download.
[MAP-19033] -Support for Windows XP
Description:Add support for Windows XP SP3 32-bit
[MAP-10806] -Local DB should support SELECT with DELETE and SELECT with UPDATE
Description: changes made as following

localdb delete action:

new property 1: "Returning on Delete", optional boolean, default to False
new property 2: "Max Returning Rows", optional integer, default to 10

if "Returning on Delete" is set to true, output map should be populated with columns from the selected table in array format(size= "Max Returning Rows"). When the action executes, the deleted rows are returned.

localdb change action:

new property 1: "Returning on Update", optional boolean, default to False
new property 2: "Max Returning Rows", optional integer, default to 10

if "Returning on Update" on is set to true, output map should be populated with columns from the selected table in array format(size= Max Returning Rows). When the action executes, the updated rows are returned.

[MAP-19502] -License Manager -- in addition to node name, include IP of license client request
Description: Added IP of the client as a column to the table in the License Server Admin panel.
[MAP-19423] -Keyence -- harmonize dw boolean variables with Keyence s/w variables
Description: dwkeyence: variable type change to INT2 and support Nested BOOL for R, MR, CR and LR.
[MAP-18646] -Dynamic array size in "Enhance Demand Write"
Description: "dynamic" flag is added to json as such
{ "TestCountVar": \{"type":"INT4", "count":5, "dynamic_count":true}
} .
When dynamic count is set to true(default to false), an additional input variable(INT4) in this case "TestCountVar Count", will appear for the user to specify the actually count to be written/read from/to the device. In this example, if this count is set to 3, then only 3 out of the 5 total will be written to the PLC.
[MAP-19528] -License Manager additional system variables
Description: 6 additional system variables added: license.pool.client.preallocated_dev; license.pool.client.preallocated_http; license.pool.client.device_used; license.pool.client.device_total; license.pool.client.http_used; license.pool.client.http_total.
[MAP-19507] -License Manager --- obfuscate the paraphrase (hide it)
Description:License server/client's passphrase is now an encrypted password field instead of plain text.
[MAP-19699] -Telit VI AI/ML Widget add support to load image from server
Description: Added support to Telit AI/ML widget to load image from server
[MAP-19672] -Keep information about previous package/firmware
Description: Added extra information(current version) in the audit log on firmware update
[MAP-10854] -Build deviceWISE using latest Option Cloudgate SDK (currently v 2.7.2 )
Description:Update Option CloudGate v2 to newer Option SDK (2.98)
[MAP-18068] -Add support for MultiTech Conduit 300
Description:Add support for Asset Gateway on Multitech Conduit 300.
[MAP-18196] -Azure IoT Hub, should use primary and secondary keys
Description:Azure IoT Hub connection now supports a secondary key.
[MAP-18671] -Mitsubishi Bit Level Triggers and Data Reads
Description:dwmelsec: Added support for nested bool read from word
[MAP-19289] -IFM IO-Link --- implement DI
Description:IFM IO-Link supports DI on pin 2.

Drivers and Extensions

[MAP-19425] -Keyence --- Issue with STRINGS
Description: dwkeyence: swap has been added for Keyence device for STRING to match the Keyence STRING type (MSG->LSB)
[MAP-19369] -Support UA Server Discovery Server
Description: Supports local and remote discovery server.
[MAP-19536] -Toyopuc driver (Technology Preview)
Description: dwtoyopuc: Added new driver for Toyopuc PLC.
[MAP-19729] -IFM - Node crash when losing connection to sensor
Description: Better handling in the driver when sensor are added, removed, or swapped within the IO-Link hardware. Relates to: MAP-19733; MAP-19764, and MAP-19832.

Issues Fixed on the 23.03 Release

Workbench

[MAP-19405] -Abrupt PC restart when Uninstalling 23.02.09
Description: Windows Only - When performing a firmware update via the Workbench from versions prior to 23.02.10, deviceWISE may initialize an automatic restart of the OS. This issue has been resolved in the 23.02.10 release.
[MAP-19527] -When node scan localhost, it is not added to the recent group
Description: Fixed adding nodes scanned by name into recent group.
[MAP-19470] -Azure Event Hub -- hangs loading the admin panel
Description: Admin panel hangs when no previous connections are persisted has been fixed.
[MAP-19663] -Disabled data mappings should be restarted in started state
Description: Load protection is added to mapper, just like triggers and devices. The state of starting/stopping triggers will set to started if devicewise is restarted in the middle of starting and stopping.
[MAP-19612] -At times, editing a windows won't popup to the front
Description: Fixed editor display issue on some multi-display setups.

deviceWISE View

[MAP-19928] -Display bugging when Copy and Pasting Style < between Table Widget and Value Card widgets >
Description: Display error when Copy and Pasting Style between Table Widget and Value Card widgets
[MAP-19198] -dwView login window keeps on popping up less than a minute after logged in
Description: The test outcomes suggests that ‘login window keeps on popping’ issue has been resolved. dW View seems to recover the session properly, even after computer sleeps.
[MAP-19609] -Right-click options on Widgets: Paste Style function not working
Description: Fixed Paste Style function not working.
[MAP-19604] -Trending Widget -- Timezone issue
Description: Calendar widget fixed defect with timezone.
[MAP-19767] -Display bugging when Copy and Pasting Style < between Historical Trend and Value Card widgets >
Description: Display error when Copy and Pasting Style between Historical Trend and Value Card widgets
[MAP-19731] -Datetime Shifts to local + 4 HRS when Switching between "devicewise" and "Trend" at the Query Metadata > Data Source type menu
Description: Line Chart Trend added support to store/retrieve data in UTC format

deviceWISE Runtime

[MAP-19537] -Triggers failed to execute when both Project & Triggers are in started state
Description: If the project is stopped and then started while the trigger is still in progress, the "project start " would actually fail half way through, and leave the trigger in a weird state(started, but unloaded). A fix was made so when the start project would fail if there is any in progress trigger.
[MAP-18576] -Customer stores data into the QDS system which gets corrupted
DescriptionIf deviceWISE detects corrupted store and forward disk files, it will remove and rebuild the profile and files.
[MAP-19870] -Missing File Systems action group
Description: With File Watcher extension loaded, the Copy action now appears under File System group in the trigger editor instead of the Strings group.
[MAP-19824] -HTTP server settings are not being exported
Description: HTTP server settings is now part of the backup/restore mechanism.
[MAP-19715] -deviceWISE crash with Runtime exception caught: [0xC0000005]
DescriptionWhen the variable subscription expires (5 minutes), the runtime removes the subscription object in from the btree(per session), and if there are no other subscriptions for that session in the btree, the runtime would delete this btree. At the same time if a new subscribe is called, it can acquire a handle that is going to be delete, thus inserting to a deleted btree and causing the crash.
[MAP-19670] -Connection timeout issue when connecting to AWS IoT Core
Description: Connection timeout setting now configurable via admin panel.
[MAP-19874] -Devicewise application Issue on concurrent licensing
Description: Linux ID is removed as Hardware ID from standard build since it's not reliable(not unique) for modern systems and it should not be used.
[MAP-19160] -deviceWISE crashes after MQTT or AWS IoT core connection loss
Description: AWS IoT Core will no longer crash when disconnect and connect are performed in admin panel while triggers are running.

Installers

[MAP-19868] -Release driver for Amcrest camera
Description: dwamcrest is now included for Linux and Windows install.

Transaction Server

[MAP-18832] -TS fails to send transaction to Rest Service with HTTPStatusCode -1
Description: If Http Transaction timeout, HttpStatusCode Variable will not be Severed instead of -1

Drivers and Extensions

[MAP-19535] -MAX Bundle - Create Toyopuc Driver as GA Driver
Description: Toyopuc driver now included in MAX Bundle.
[MAP-19393] -Keyence -- Reading MR Bools
Description: dwkeyence: Fixed indexing issues for BOOL type variables, Supported Nested Bool Read.
[MAP-19245] -Enable FIFO has no effect for remote trigger SAF
Description: FIFO mode for remote trigger S&F is now working as it should.
[MAP-19412] -AWS IoT Core - update publish action overview text
Description: AWS IoT Core publish action overview text accurately describes action function.
[MAP-19539] -AWS IoT Core - use MQTTAS in Windows_NT version of driver
Description: Driver now supports encryption for Windows 32-bit platform.
[MAP-19608] -IFM IO-Link --- Keep connection open for variable reads
Description: Connection is no longer disconnected when doing variable reads.
[MAP-19614] -IFM IO-Link --- Erroneous exception logging
Description: Extra logging removed when sensors of the same device id exist on the same IoT Hub
[MAP-19669] -Keyence - Demand Read not reading properly
Description: dwkeyence: Fixed Var->status set to '0' when the read/write completes in multi request which was missed.
[MAP-19627] -Crash on IFM IO-Link when existing sensor, configured, used then removed
Description: Fixes crash if sensor used in a trigger is removed.
[MAP-19464] -MT Connect:: Node crashed when attempt to start MT connect device
Description: MTConnect device start crash when processing header fixed.
[MAP-19831] -deviceWISE is restarting due to possible mutex deadlock
Description - dwrockwell: Indirect_unget fix for df1 device stop issue which in turn avoid the watch dog timer restart of deviceWise.
[MAP-19741] -IFM IO-Link Issue at ATT
Description - Device no longer gets stuck in "Starting" when two sensors with the same device id are connected to the same IFM IO-Link Master and the IODD file does not exist.

Supported Driver Versions

Generally Available
Device Driver	Version
AcraDyne driver	1.1.3
Advanced Display Protocol	1.0.2
Allen-Bradley (Rockwell Automation)	2.20.0
Apex Cleco driver	1.9.4
Atlas Copco driver	3.9.1
AWS	0.2.9
Azure	2.1.11
Beckhoff driver	2.1.9
Danlaw	2.12.3
Estic driver	1.1.3
FANUC CNC Driver	1.4.0
Fanuc driver	2.3.2
Industrial driver	Updated with each release
Ingersoll Rand driver	1.3.4
LDAP – do not use with Linux X86 in versions 21.10 and later	1.1.2
Lua	1.1.4
IBM Maximo	1.1.4
Melsec	3.5.4
Mitsubishi driver	3.3.7
MindSphere	2.0.4
Modbus driver	2.11.2
Modbus Server driver	1.1.8
Modem	1.5.1
MQTT driver - Updated with 23.03	2.1.2
MTConnect driver - Updated with 23.03	1.3.2
NMEA GPS	1.0.4
OAuth2	2.3.2
Omron driver	3.8.2
OPC-DA Client driver	2.8.0
OPC-DA Server driver	1.3.1
OPC-UA Client driver - Updated with 23.03	4.1.12
OPC UA Server	1.2.6
Rockwell ControlLogix driver	Updated with each release
Schneider Electric	2.9.0
Siemens S7 driver	2.11.4
Stanley Tools driver	1.2.0
Sysmon	1.0.2
TCP Listener	2.3.12
TR50	2.6.2

Pilot Ready
Device Driver	Version
Bosch Rexroth driver	1.8.4
Kawasaki - Updated with 23.03	1.2.1
ROC Plus driver	2.0.2
SNMP driver	1.1.1
Sturtevant Richmont driver	1.8.4
deviceWISE View	2.0.4

Technology Preview
Device Driver	Version
Amcrest	0.5.0
AWS SiteWise	1.0.3
BACnet / IP driver	3.2.12
Barcode Scanner	1.1.1
CODESYS driver	0.6.3
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	1.0.5
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
IBM Maximo Enterprise Asset Management	1.1.1
IFM-IOLINK	0.5.6
J1939 IXXAT device Driver	1.1.1
JSON	0.5.3
Keyence	1.0.3
Nachi – (Windows Only - Win32 and Win64)	0.7.0
ScanTools OBD-II	1.0.1
OPTO22	0.0.4
Sandbox	1.3.0
Serial	1.3.0
SICK CLV Scanner	1.1.7
Simulation	0.5.1
Telit SmartIO	2.2.1
Trending	1.3.1
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.