deviceWISE IoT Gateway 24.02 Release Notes
A number of improvements and fixes were added to the IoT Gateway 24.02 release.
Summary:
The 24.02 release includes improvements made to the Workbench, deviceWISE View, Transaction Server and multiple drivers.
Production Release Date: July 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-20916] -Live Trending Graph in Watch Window
Description: Added graphical trending of watch window variables. - [MAP-21277] -Feature Request - Multiple Trigger Reports
Description: Added ability to view multiple reports from an exported reports .xml file. - [MAP-20887] -Macro Variable - last error action id added
Description: Macro variable - last error action id is added. This variable contains the action id of the error code from last action. - [MAP-21367] -Start Project as admin --- similar to start trigger by Admin
Description: Added Start Project as admin as a menu option in Workbench.
deviceWISE View
- [MAP-21238] -Add cancellation to the speech
Description: Added support to stop speech. Before, sound was possible of being cancelled, but not speech. - [MAP-19177] -Enhance Table widget
Description: Add support to read from variable defined as single dimension array.
Transaction Server
- [MAP-21515] -Create New Field (Resource URI) in Http Transport for OAuth
Description: Added resource uri text file for OAuth authentication in Http Transport.
deviceWISE Runtime
- [MAP-21137] -Rename gefanuc driver to fanuc robot driver
Description: GE Series 90/Rx3i devices now show up under Emerson. ROC 800 Series device show up under Emerson. Fanuc Robot shows up under Fanuc as just Robot - [MAP-21306] -Change the voucher system to duration based(currently you can only use it once)
Description: The feature was implemented that only one restart was allowed, the subsequent reboot will lose the acquired licenses effect. The change is made so that the acquired licenses will be valid for the entire lease duration regardless of number of restarts. - [MAP-21180] -deviceWISE Edge License - SKU Reverse Lookup
Description: Licenses will be pulled from the cloud now even if the person has licenses generated before the new SKU mechanism. - [MAP-21375] -TCP Listener device should not consume a device license itself
Description: TCP listener itself will no longer consume a device license. - [MAP-20851] -Trigger setting --- w/o opening the trigger --- report N times
Description: Added support to command 5431 and 5438 to take in an optional 3rd parameter (count), which is the number of subsequent reports that will be generated.
deviceWISE View
- [MAP-21365] -Cast Array if UINT1, INT1 w chars to strings
Description: Added support for ASCII to text in Value Card.
Drivers and Extensions
- [MAP-21165] -Added delete image option to Inference Action
Description: Inference action for Visual Inspection now contains an option to keep or delete image. - [MAP-21077] -Allen-Bradley Power Monitor 500 --- add to the modbus XMLS
Description: Modbus driver now contains map for Allen Bradley Power Monitor 500. - [MAP-21055] -Siemens PAC3200 --- add to the modbus XMLS
Description: Modbus driver now contains mapping for the Siemens PAC3200. - [MAP-20739] -IP Variable in Siemens Event Data includes Port No
Description: dwsiemens: Removed port number from ip address field in Siemens(TCP Send) Event Data. - [MAP-21402] -Siemens IOT2000 is now TP
Description: Siemens IOT2000 extensions is now TP, the extensions provide serial number for the gateway. - [MAP-20739] -IP Variable in Siemens Event Data includes Port No
Description: dwsiemens: Removed port number from ip address field in Siemens(TCP Send) Event Data.
Issues Fixed on the 24.02 Release
Workbench
- [MAP-21359] -Local DB action does not show input tab
Description: Corrected issue with input/output values not showing on action with var substitution field. - [MAP-21431] -Writing element in Rockwell String Array >1000 elements doesn't work
Description: Fixed variable panel r/w of large array ASCIISTRING structures on devices using lazy enumeration. - [MAP-21387] -LocalDB - Error when importing DB with Data
Description: Fixed import of localdb table with exported data. - [MAP-21386] -Add trigger fire on start checkbox for data event on 24.02+ gateways
Description: Added ability in trigger data events to set "fire on start" for any condition. (Relates to MAP-20897)
Visual Inspection
- [MAP-21170] -Error when triggering an Inference Action with Binary Variable
Description: Visual Inspection inference action can take either a base64 encoded or raw JPG image in a binary buffer as its input. - [MAP-21373] -Siemens_S7-1200.Q[0] level variable is not selectable in the dwview
Description: Fixed issue with Siemens device where some variables were not selectable from the dwview variable picker.
Transaction Server
- [MAP-21272] -Deloitte LOP#233 Store&Forward not dequeuing messages
Description: S&F Transaction Timeout, would result in thread overflow. The issue was fixed and doesn't take place in the current version.
deviceWISE View
- [MAP-21138] -Camera snapshot is not writing on its widget variable - broken functionality
Description: Fixed defect with camera snapshot. It is now correctly writing on its widget variable. - [MAP-21124] -VI Widget -- flickering issue at technotecs
Description: Resolved the repainting of text. - [MAP-20609] -Typography Settings do not Work
Description: Removed unused typology settings from Style tab. - [MAP-21242] -Display of variable name as a label cannot be disabled
Description: Added capability to disable label for Radial Bar/Gauge widget. - [MAP-21171] -Y-Axis Range Breaks After Clearing Min/Max Values
Description: Fixed Y-Axis Range. It won't break anymore after clearing Min/Max values. - [MAP-21341] -dwVI Local/Remote issue
Description: Fixed local/remote mime issue. - [MAP-21305] -Table widgets can only be selected from the borders
Description: Fixed issue with table widgets. Now they can be selected from a larger portion of its area.
deviceWISE Runtime
- [MAP-21104] -Exports of previously imported local databases with data do not always work
Description: Old export of localdb table data might not have the right link. New table/data export works properly now. - [MAP-21245] -Custom Thing Key with embedded blanks fails the TR50 start --- panel should check for valid chars/symbols
Description: TR50 connection panel will validate the TR50 custom thingkey on save now. Allowed characters in a thing key are: Alphanumeric (upper and lowercase), hyphens, underscores, and colons. - [MAP-21126] -TSL from License Server not functioning properly when you start the client a second time with the same device/HTTP counts
Description: When the setting is saved the second time, the cache was being used and was not recalculating the newly retrieved technical support feature from the server. This was fixed, so it will always refresh on "Save". - [MAP-21074] -Subscriptions not publishing at correct rate
Description: When switching the priority in the variable watch panel from lower priority to higher priority, the change did not take effect since the last change made to the data publisher in 24.01 version. A fix is applied to avoid the defect. - [MAP-19095] -M90 Fibocom AG Linux --- not working on 22.03, 23.01
Description: Fibocom modem was broken since 22.04 (after putting in automatic modem discovery feature), it was issuing a call that's proprietary to Telit modem which is not supported by others. - [MAP-21393] -Device Create action does not acknowledge "Enumerate Controller" parameter
Description: The problem was in fact a cosmetic issue, the device actually recognized the correct setting. The issue was detected and fixed, therefore the Workbench will now recognize it. - [MAP-21364] -Simulation device doesn’t generate values on Node Runtime restart
Description: Fixed a problem where Simulation devices not working if multiple of their names have the same first 4 characters. - [MAP-21353] -Erroneous message "REJECTED, could not acquire a license" seen in debug logs
Description: System variable "device.license.rejected" was not updating correctly, but the license system was rejecting new connections correctly. A fix was conducted to have the number updated every time.
Licenses
- [MAP-21103] -When importing a TSL for the wrong HWID, the status message does not necessarily reflect this issue
Description: Now TSL status will always overwrite "Newer Technical license is needed", so that the customer can see why newer TSL is needed.
Backup Utility
- [MAP-21351] -BackupUtility: not giving error when password is not correct
Description: Fixed backup utility issue not logging error when password incorrect.
Drivers and Extensions
- [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-21236] -CNCNetPDM - Account for Part System parameter when writing data
Description: Part System parameter now supported for Citizen CNC (citizen.dll). - [MAP-21235] -MQTT - Client ID Field Type is platform dependent
Description: MQTT device can now be exported and imported across Windows and Linux platforms successfully when Machine ID is used as the client ID. - [MAP-21234] -MQTT - Client ID Type: System Serial Number does't work in any config
Description: System Serial Number can now be used as a client ID for a MQTT device. - [MAP-21164] -MQTT Node Crash when subscribing event is not finished and client is disconnected
Description: Fixed crash when MQTT device has subscriptions and the broker terminates communications. - [MAP-21115] -MQTT - Not possible to import project if devices are disabled
Description: MQTT Publish triggers can be exported and imported successfully even if MQTT device is stopped. - [MAP-21113] -MQTT - If MQTT Connection device is disabled, MQTT Publish action doesn't show Input tab
Description: MQTT Publish action can now be configured even if MQTT device is in the stopped state. - [MAP-21258] -dwsiemens symbols: Issue with STRING Read/Write with odd size and as Array
Description: dwsiemens: Fixed Symbols parser for array of struct and symbols string array with odd size issue. - [MAP-21169] -Creating new device by using the TIA_Portal_DB_file feature fails
Description: dwsiemens: Fixed Symbols parser for array of struct and symbols string array with odd size issue. - [MAP-21391] -Improve & Fix Siemens parser
Description: Siemens symbol parser used to append .db extension if file doesn’t end with .db. The mechanism was removed in order to support .awl files. - [MAP-21376] -MTConnect Client System Error : -8142
Description: Issue when validating MTConnect device resolved. - [MAP-21358] -Device(s) Causing Node to Crash - Rockwell
Description: dwrockwell: Fixed crash in DF1 code on request expiry. - [MAP-21257] -dwsiemens symbols: Parse Struct within STRUCT
Description: Added STRUCT support for Siemens Symbol parser.
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.9.1 |
| 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.1.3 |
| FANUC CNC Driver | 1.5.2 |
| Fanuc driver | 2.3.3 |
| Industrial driver | Updated with each release |
| Ingersoll Rand driver | 1.3.4 |
| 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.4 |
| 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.2 |
| SNMP driver | 1.1.1 |
| Stanley Tools driver | 1.2.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.1.7 |
| 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.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.1 |
| 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.13 |
| Visual Inspection | 1.0.5 |
| 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.