A number of improvements and fixes were added to the IoT Gateway 26.01 release.
Summary:
The 26.01 release includes improvements made to the Workbench, deviceWISE View, Transaction Server and multiple drivers.
Production Release Date: April 2026
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-14806] -Set filter based on selected cell in table
Description: Added the ability to create filters directly from a table cell value via the context menu. - [MAP-24635] -Introduce 'Edit as Text' context action for Staging Browser
Description: Introduced an "Edit as Text" context action in the Staging Browser, allowing users to edit staging text files directly without downloading them. - [MAP-25280] -Device definition panel should have filter on "Type" field
Description: Added a filter for the Type field in the device definition panel, allowing users to quickly search and select from available device types. - [MAP-24851] -View Staging Text files with formatting option for certain types (json, xml, html, etc)
Description: Added formatting support in the Staging Browser for text-based files (such as JSON, XML and HTML), including syntax highlighting, code folding and pretty-printing for improved readability of structured data. - [MAP-24639] -Consolidate Scan Panel Subnet and ID/Mask fields into one
Description: Simplified the node scan panel by consolidating subnet and ID/mask fields into a single, unified input, for a more compact appearance. - [MAP-24729] -Table Name prefixed while using Export to CSV Functionality in Local Database
Description: When exporting a database table to a CSV file, the name of the table is now the default name for the CSV file in the dialog. - [MAP-20915] -Allow Trends to be defined from the variable panel
Description: Trends can be created from the Devices Variables panel. With a device variable selected, "Create trend" can be selected from the popup menu to open the creation dialog.
deviceWISE View
- [MAP-22135] -SVG Widget where attributes can be tied to variables
Description: Added SVG Widget where attributes of the SVG can be tied to the variables. - [MAP-25058] -Suppress JSON message from View screens in AI Widget
Description: Improved AI Widget behavior by suppressing JSON error messages in the UI and redirecting them to the console, reducing unnecessary user facing alerts. - [MAP-24933] -Trend Widget filter samples to ensure they are within the range
Description: Trend Widget added filter to samples to ensure they are within the range.
deviceWISE Runtime
- [MAP-24977] -Create an action to activate or deactivate Visual trigger on a given model
Description: Added a new action to enable or disable the Visual Trigger for a selected model. - [MAP-24978] -Create an action to list all models metadata
Description: Added a new action to retrieve metadata for a selected model. - [MAP-25514] -OpenSSL3 - need to support older cipher
Description: Added SSL support for IFM IO-Link IoT Master on port 443. Support allows for older IFM IO-Link firmware to work with newer version of deviceWISE that use OpenSSL3. - [MAP-25059] -Add App Settings to Variable tree - visual assistant driver
Description: Added a new folder named App Settings to the variable tree, exposing application settings as variables. - [MAP-24974] -Add enhanced log message to the GenICam driver when the stream cannot be opened
Description: Enhanced the log message generated when a stream cannot be opened. The update message now clearly indicates that the camera may be in use, improving troubleshooting and diagnostics. - [MAP-23518] -Add P&ID Widgets to deviceWISE VIEW
Description: Added support for P&ID widgets in deviceWISE View, enabling visualization of process diagrams and operational flows within industrial environments. - [MAP-24727] -Log error when items are added to COV list that don't match device id in BACNET driver
Description: Added validation to BACnet COV events to ensure item entries match the associated device ID. An error is now logged when invalid items are provided or when the device ID does not match the event. - [MAP-24958] -Support Variable Type Casting in OPC UA Client Driver
Description: Added support for variable type casting in OPC UA Client connections, enabling handling of UINT1, UINT2, UINT3, UINT4 and UINT 8 data types. - [MAP-25075] -Workbench Entra Authorization Using Core Commands
Description: Added support for external authorization via OAuth2 (Microsoft Entra) enabling users to authenticate and log in to a node using Entra credentials. - [MAP-24637] -Implement advanced properties to turn on functionality
Description: Implement support for additional properties to activate new features in the IOS VI Assistant application. - [MAP-24366] -Add new Nachi action to sync time
Description: Nachi driver now has trigger action to sync robot time with PC time. - [MAP-24365] -Create New Monitor Group and add API variables
Description: Nachi driver variables now contain a Monitor group. - [MAP-24323] -SPC trigger doesn't fire when there is a variable update but the value is the same
Description: New SPC sample action that will send a value to a variable that SPC is being calculated. SPC Trigger now fires on variable updates even when the value remains unchanged. - [MAP-24944] -Core Command to return Entra information and another to accept (encoded) json data to set user permissions
Description: Added new core commands to retrieve Microsoft Entra authentication information. - [MAP-25083] -For License pooling --- if preallocated limit is reached - prefetch an additional 5 pooled licenses
Description: Added buffered dev count and buffered http count. With this improvement additional licenses are preallocated when the pool limit is reached to maintain availability and reduce startup latency.
Drivers and Extensions
- [MAP-25453] -OPC UA Server can't share UA Client Devices
Description: Fixed an issue where OPC UA Client variables were not properly shared when exposed through an OPC UA Server. - [MAP-25172] -CNCnetPDM - add variable sorting the CNCnetPDM device
Description: Variables in CNCnetPDM devices are now automatically sorted alphabetically, making navigation and lookup easier in environments with large variable sets. - [MAP-25139] -OPC UA Server -- when having to restart node -- provide a warning message
Description: Updated the admin panel to include an error message when the device fails to start. Added a warning message when Restart Node is selected. - [MAP-24863] -Refrain from publishing messages that exceed AWS IoT Core broker limits
Description: As AWS defines clear broker/protocol limitations for the IoT Core product. Because of that, a "reconnecting issue" was happening when those limits are surpassed, which made the "Cloud connector" from the Workbench switch to "Reconnecting" state.
This change solves the issue by adding a verification step to check the "topic" and "message" broker limitations before the publish function be called. This way, rather than having the "Reconnecting" state, the success/failure counters will be incremented depending on the input from user filled in the arguments field.
Issues Fixed on the 26.01 Release
Workbench
- [MAP-25488] -Admin Export categories not sorted
Description: Corrected an issue where categories were not sorted alphabetically. - [MAP-25246] -Workbench issue reading scalars as arrays when brackets are in the names
Description: Resolved an issue where scalar variables with bracketed names were incorrectly interpreted as array elements. - [MAP-25074] -Editing HTTP transport map alters field formatting and dropdown values
Description: Resolved an issue where transport fields and dropdown values were not properly retained when re-editing an HTTP transport map, causing fields such as the transport name to appear empty. - [MAP-24218] -Trigger validates when the variable doesn't exist
Description: Fixed an issue where the Write Trigger would fail or behave inconsistently when processing null or empty input values, ensuring stable execution across all cases. - [MAP-24524] -Timing condition with Trigger reports
Description: Resolved a timing issue where the latest trigger report was not correctly selected due to the list updating after selection.
Transaction Server
- [MAP-25187] -HTTP Transport validation fails and takes longer than connection timeout
Description: Fixed an issue where HTTP Transport validation delayed responses until the server replied. The system now returns a response immediately when a connection or transaction timeout is reached. Also, fixed an issue where triggers could be incorrectly disabled when transport operations exceeded timeout limits. - [MAP-21971] -OPC DA client does not restart when it references the local DA Server and it restarts
Description: Fixed an issue preventing devices referencing internal OPC DA server from restarting when the server was restarted. - [MAP-24680] -Unable to connect to Databricks database when pool size is increased
Description: Fixed an issue where the Databricks transport would fail when the connection pool size exceeded supported limits, preventing the transport from entering an active state. - [MAP-24806] -Snowflake transport enters Pending/Failed and changes state to Down with high connection pool size
Description: Resolved an issue where the Snowflake transport could enter a Pending/Failed state and transition to Down when using high connection pool sizes. - [MAP-24618] -Transport State remains "Down" despite successful Plex workflow
Description: Resolved an issue where the transport state remained "Down" despite successful executions of Plex workflows, ensuring it reflects the correct status when the endpoint is reachable. - [MAP-24677] -Enterprise Transport Causes Issues with REST Service
Description: Improved REST service handling to prevent triggers from being disabled when a non-JSON response is returned where JSON is expected. - [MAP-24748] -Pending Connections Delay After Any MSSQL Pool Size Modification
Description: Improved database connection pool handling to eliminate delays after pool size changes, avoiding full pool restarts and allowing connections to scale dynamically. - [MAP-25143] -DeviceWise issue connecting to SAP ME via NetWeaver JMS
Description: Resolved an issue where deviceWISE could fail to reconnect to SAP ME via NetWeaver JMS after a connection drop, improving connection reliability and data continuity. - [MAP-25148] -- 4951 timeout in WS and Trigger goes to Disabled
Description: Resolved issue where WS timeouts could cause triggers to be automatically disabled, ensuring triggers remain active and processing continues as expected. - [MAP-25136] -Store and Forward queue stuck [2]
Description: The HTTP transport validation has been updated to only verify that the endpoint is reachable and does not return an "Unauthorized" (HTTP 401) response. Validation will now be considered successful if the endpoint is available, regardless of application-level authentication requirements.
deviceWISE View
- [MAP-24910] -Date/Time in View
Description: Added support for local time zone handling in the Date/Time input widget, ensuring values reflect the user's local time instead of UTC offsets. - [MAP-25506] -View cant render array of UDT members
Description: Resolved an issue where arrays of UDTs were not properly rendered in the View interface. UDT array elements are now displayed correctly and consistently. - [MAP-25370] -Referenced Images Not Included in Gallery Export
Description: Fixed an issue where images referenced in states (pass/fail indicators and background images for examples) were not included in the gallery export. - [MAP-25208] -Write Widget is Removing Characters for Error/ Errors
Description: Fixed an issue where the Write Widget would truncate strings containing "Error", resulting in incorrect values being written to event variables. - [MAP-25536] -dwView: Version # missmatch between the package version # and the gallery version #
Description: Resolved an issue where the dwView package version did not match the gallery version, ensuring consistent version reporting. - [MAP-24950] -View not assigning Variables properly
Description: Resolved an issue where variables containing special characters could not be assigned in deviceWISE View, causing invalid parameter errors. - [MAP-25146] -dw View - Workbench shows dw View 2.6.3 while browser View shows 2.6.2
Description: Resolved an issue where the Workbench extension and browser View displayed inconsistent version numbers, ensuring alignment across components. - [MAP-20705] -Trend Widget should not query entire data on every update
Description: Improved Trend widget performance by adding caching, so updates only fetch new data instead of reloading the entire dataset each time.
Visual Inspection Assistant
- [MAP-25247] -Valgrind leak on _dwappleiosvi_device_create_app_settings_variables
Description: Resolved an issue where device data continued to be refreshed unnecessarily, improving performance and reducing redundant processing.
deviceWISE Runtime
- [MAP-25051] -Crashing Loop caused by OPC UA_Channel_ResponseAvailable: Request failed! (0x800A0000)
Description: Fixed an issue that could cause a crash loop in the OPC UA client when a read request failed (error 0x800A0000). - [MAP-25047] -Cloud connection through proxy using DPS fails
Description: Fixed an issue where cloud connections using Azure Device Provisioning Service (DPS) failed when configured behind a proxy. DPS connections now function correctly with proxy settings. - [MAP-25353] -Date Event/Subscription -- not working w Variables w [] and "." in the name
Description: Resolved an issue where Data Events, Watch Windows, and subscriptions would not trigger when variable names contained square brackets. - [MAP-25221] -deviceWISE crashing with RunTime Exception Caught: [0xC0000005]
Description: Fixed an issue where deviceWISE could crash with a runtime exception when attempting to access a variable that does not exist during Enhanced Demand Read operations. - [MAP-24819] -SPC Causing Node Crash When Stopped
Description: Resolved an issue where stopping SPC triggers could cause the node to crash under certain conditions. - [MAP-22326] -MQTT Driver. Improve Error Message. Specify which device
Description: Resolved an issue where invalid tag configurations could cause unexpected driver errors, improving validation and stability during execution. - [MAP-25159] -License Client stops syncing with License Server after releasing licenses
Description: Fixed an issue where the License Client could stop syncing with the License Server after releasing licenses. - [MAP-24704] -Okuma CNC Stuck Stopping
Description: Fixed an issue where Okuma CNC devices could get stuck in stopping state, preventing reads from completing. - [MAP-25347] -When writing to OPC UA Client array elements in positions other than position 0, the write is not going through successfully
Description: Fixed an issue where writes to OPC UA Client array elements were always applied to index 0 ignoring the specified position. - [MAP-25389] -OPCUA Server crashes when an OPCUA client device is referenced
Description: Fixed an issue where the OPC UA Server could crash when referencing an OPC UA Client device. - [MAP-25224] -OPC UA Client can't render and operate on tag names with [] (square brackets)
Description: OPC UA Client now correctly handles tag names containing square brackets ([]), ensuring values render and can be operated on as expected. - [MAP-25156] -OPC UA - Event Not Restarting
Description: OPC UA Event subscriptions now reliably resume after a device is restarted, ensuring events continue to be received without manual intervention. - [MAP-25048] -OPC UA Server won't start
Description: Updated the admin panel to include an error message when the device fails to start. - [MAP-25515] -Licenses Being Pulled Multiple Times
Description: Fixed an issue where licenses were repeatedly pulled from the server due to incorrect expiration validation. This fix prevents unnecessary license refreshes and duplication. - [MAP-24828] -GenICam Continuous Capture
Description: Fixed an issue where GenICam capture stopped after the first image when "wait for new frame" was disabled by introducing a continuous acquisition mode to ensure ongoing image capture. - [MAP-25069] -Gateway OPC UA Server Dropping Connection
Description: Fixed an issue where the OPC UA Server could stop accepting new connections when global devices with structured data were configured. - [MAP-25350] -Duplicate folders appear in the OPC UA client
Description: Fixed an issue where the OPC UA Client displayed duplicate folders when multiple child references pointed to the same node.
Drivers and Extensions
- [MAP-25077] -Azure & S/F not working correctly
Description: Enhanced Azure Device Provisioning to automatically reconnect across restarts and ensure Store & Forward functionality is maintained when configured preventing data loss. - [MAP-22854] -Send Telemetry to Event Hub Failing With Extended Status 401
Description: Resolved an issue with Azure Event Hub SAS token handling that caused telemetry requests to fail with HTTP 401 errors. - [MAP-24634] -CNCnetPDM - Write commands send delay
Description: Fixed an issue where CNCnetPDM message processing failed under high throughput. The system now handles high-rate message traffic more reliably without dropping or delaying messages. - [MAP-25235] -Node crashing when starting an IFMIOLINK device
Description: Fixed an issue that would cause the node to crash when starting an IFMIoLink device. IFM IO-Link now supports port 443 (HTTPS). - [MAP-25057] -OPC UA no client events fired
Description: OPC UA Client events are now reliably triggered even when the eventID property is not provided as a binary array, ensuring consistent event handling across OPC UA servers. - [MAP-24571] -SPC - Histogram init returns incorrect ranges
Description: Enhanced node scanning configuration by streamlining network input fields, reducing duplication and improving overall usability when defining scan ranges. - [MAP-25157] -FFMPEG device does not stop when live view is open
Description: Fixed an issue where FFMPEG devices could remain stuck in a stopping stage after using Live View, potentially leading to a deadlock and requiring a service restart. - [MAP-24520] -Reading data from a STRING in a SIEMENS PLC gets truncated (dwsiemens)
Description: dwsiemens: Fixed typecasting issues in version:3.0.7. - [MAP-25282] -Sick Listener, Siemens Listener - REJECTED, could not acquire a license
Description: dwsick_clv, dwsiemens: Fixed Sick CLV and Siemens listener license issues. - [MAP-25119] -Rockwell device listener encountered a socket send() error: -7226
Description: dwrockwell: Fixed issue of variable type casting to fix suspected pkt failures hash value. - [MAP-24017] -Rockwell Listener - REJECTED, could not acquire a license
Description: dwrockwell: Fixed CIP listener license issue. - [MAP-24809] -Node crashes with Exception code: 0xc0000005 at runtime
Description: dwfanuc_cnc: Fixed local buffers to fix the suspected crash. - [MAP-22294] -ABB Flow-X: Permission issues causing Write error
Description: Resolved an issue where variables were incorrectly shown as writable without proper authentication, which could result in write errors during operations. - [MAP-25455] -LWS proxy forwarding to wrong host
Description: Fixed an issue where server should now send a ‘Bad Gateway’ in case the remote host does not replies properly.
Supported Driver Versions
| Generally Available | |
|---|---|
| Device Driver | Version |
| AcraDyne driver | 1.1.4 |
| Advanced Display Protocol | 1.0.2 |
| Apex Cleco driver | 1.9.5 |
| Atlas Copco driver | 3.10.2 |
| AWS | 1.0.2 |
| Azure | 2.1.17 |
| Beckhoff driver | 2.1.9 |
| Bosch Rexroth driver | 1.8.5 |
| Danlaw | 2.12.3 |
| Estic driver | 1.2.2 |
| FANUC CNC Driver | 2.0.5 |
| Fanuc driver | 2.3.3 |
| GPS | 1.0.4 |
| Industrial driver | Updated with each release |
| Ingersoll Rand driver | 1.4.1 |
| Kawasaki | 1.4.0 |
| Keyence | 1.0.6 |
| LDAP – do not use with Linux X86 in versions 21.10 and later | 1.1.2 |
| Lua | 1.1.4 |
| IBM Maximo | 1.1.4 |
| IFM IO-Link | 1.0.3 |
| Melsec | 3.5.7 |
| Mitsubishi driver | 3.3.7 |
| Modbus driver | 2.11.7 |
| Modbus Server driver | 1.1.8 |
| Modem | 1.5.1 |
| MQTT driver | 2.1.13 |
| MTConnect driver | 1.3.6 |
| NMEA GPS | 1.0.4 |
| OAuth2 | 2.3.2 |
| Omron driver | 3.8.2 |
| OPC-UA Client driver | 3.1.31 |
| ROC Plus driver | 2.0.3 |
| Rockwell ControlLogix driver | Updated with each release |
| Schneider Electric | 2.9.0 |
| Siemens S7 driver | 3.0.9 |
| SNMP driver | 1.1.1 |
| Sparkplug B | Included and Updated as part of MQTT |
| Stanley Tools driver | 1.3.1 |
| Sturtevant Richmont driver | 1.8.5 |
| Sysmon | 1.0.2 |
| TCP Listener | 2.4.1 |
| Toyopuc | 1.0.6 |
| TR50 | 2.6.2 |
| deviceWISE View | 2.6.8 |
| Technology Preview | |
|---|---|
| Device Driver | Version |
| Amcrest | 1.1.0 |
| Apple iOS VI | 1.2.7 |
| AWS SiteWise | 1.0.3 |
| BACnet / IP driver | 3.2.12 |
| Barcode Scanner | 1.1.1 |
| CODESYS driver | 1.0.0 |
| CTI (Control Technologies Inc.) driver | 2.1.5 |
| 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) | 1.0.0 |
| HAAS | 1.0.2 |
| GrovePi driver(Only in Raspbian directory) | 1.0.2 |
| HTTP Server | 1.0.1 |
| J1939 IXXAT device Driver | 1.1.1 |
| JSON | 1.0.1 |
| Melsec | 1.0.1 |
| Nachi – (Windows Only - Win32 and Win64) | 1.0.0 |
| 1.0.1 | |
| OPTO22 | 1.0.0 |
| Sandbox | 1.3.2 |
| Serial | 1.3.0 |
| SICK CLV Scanner | 1.1.7 |
| Simulation | 1.0.0 |
| Telit SmartIO | 2.2.1 |
| Trending | 1.3.14 |
| Visual Inspection | 1.0.23 |
| Virtual | 1.3.0 |
| Xirgo | 1.3.0 |
| Zaxis (only built for Windows products) | 1.0 |
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 25.02
Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 25.02 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 25.02
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 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
- Restore your node.
Upgrading a Windows Enterprise Gateway product from 19.1.6 or later to 25.02
A firmware update from a release for Enterprise Gateway for Windows before version 19.1.6 to 25.02 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 25.02, you will need to add all device drivers and extensions from the new 25.02 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 25.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 Enterprise Gateway from a 17.1.14 or earlier release to 25.02, 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 25.02, you will need to add all device drivers and extensions from the new 25.02 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 25.02 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 25.02
Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 25.02 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 25.02
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 25.02, you will need to add all device drivers and extensions from the new 25.02 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 25.02
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 25.02, you will need to add all device drivers and extensions from the new 25.02 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 25.02, 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 25.02, you will need to add all device drivers and extensions from the new 25.02 release level.
A firmware update from 16.1.8 or earlier to 25.02 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.