Skip to content

Release notes

This page contains a list of features, changes, known issues and known limitations of the Nerve releases.

Version 3.2.0

System Component Version Build information
Management System 3.2.0
Node 3.2.0

This version was released on September XX, 2026. Unless otherwise stated, all known issues and limitations of the previous version are still valid.

Improvements

  • 17465: Workload DNA and Node DNA files can now include user-defined metadata, which is also returned by GET DNA status and used to create a read-only node details label.
  • 17065: Default TPM lockout parameters were adjusted to reduce the risk of temporary node access loss during repeated power cycles.
  • 17030: The Dry run deployment option was removed to simplify deployment workflows and avoid confusion with the standard deployment process.
  • 17020: Individual containers inside a compose workload can now be controlled without affecting the other containers in the same workload.
  • 16916: Customers can now manage customized compose restrictions through an API-based mechanism instead of manually changing files on the node after updates.
  • 16761: Icons in the Management System and Local UI were updated to be more consistent, more visible, and easier to distinguish.
  • 16652: Nodes can now be moved in the node list by drag and drop, making assignment to groups easier and more intuitive.
  • 16637: Docker registry authentication in the Management System now supports the OAuth authentication flow required by newer Docker versions.
  • 16611: The node list and node details view were redesigned into a clearer, easier-to-navigate view for managing and filtering nodes.
  • 16587: Node DNA status information is now available in the Management System, reducing the need to access the Local UI for DNA-related information.
  • 15970: High-level Management System connectivity status can now be shown on the console without login to support faster field troubleshooting.
  • 15944: NTP server configuration can now be provided through DNA, with feedback when synchronization succeeds or is lost.
  • 15748: Local UI API endpoints now provide access to system metrics such as disk usage, CPU usage, RAM usage, CPU temperature, and network interface information.
  • 13938: Access tokens were introduced for automated API access, enabling script-based workflows while keeping user RBAC permissions.
  • 13590: Audit logging was extended to cover remaining Management System and Local UI events, including deployment log deletion and activity log downloads.
  • 13033: The Retry function was removed from deployment campaigns to avoid unreliable behavior and misleading deployment status information.
  • 10801: Pressing Enter while creating a new workload now continues to adding the first workload version instead of creating an empty workload.
  • 10629: Logging parameters can now be configured through DNA, enabling API-based and automated configuration of node logging behavior.
  • 10620: Dialogs, forms, button names, and related wording were standardized for a more consistent user experience across the product.
  • 10603: The Management System main menu design was updated to provide more consistent navigation behavior.
  • 5314: The Remote Connection Manager can now be made downloadable directly from the Management System, making it easier to access the matching version.

Fixed Issues

  • 14631: Fixed an issue where file system corruption due to hard power cycle could prevent Nerve nodes from booting.
  • 14903: Fixed an issue where Codesys workload state was incorrectly reported as idle.
  • 14972: Fixed an issue where snapshots were not properly cleaned up after undeploying Codesys workloads.
  • 14973: Fixed an issue where no workloads were displayed for nodes after node information is updated.
  • 15593: Fixed an issue where stopping a compose workload as part of DNA reconfiguring did not always create an audit log entry.
  • 16491: Fixed an issue where it was possible to forge logs for another node, by submitting log data on it's behalf.
  • 16791: Fixed an issue where DNA signature validation can be outsmarted to keep DNA status applied.
  • 16862: Fixed an issue where node labels were not shown if the node was offline.
  • 16870: Fixed an issue where trying to view Virtual Machine workloads created on older verions of Nerve caused internal server errors.
  • 17131: Fixed an issue where DNA status during reconfiguration was showing Undefined instead of Reconfiguring.
  • 17232: Fixed an issue where node updates can fail if there is too much data in the home directory.
  • 17237: Fixed an issue where the environment variable restrictions were more strict on the Management System UI than necessary.
  • 17611: Updated the Codemeter package to incorporate security fixes.
  • 17918: Fixed an issue where node logs were not written in case of unhandled exceptions.
  • 17919: Fixed an issue where nodes can get into a restart loop.
  • 17971: Fixed an issue where Usage Reports were missing in some cases.

Known Issues

  • 17868: Visual feedback during drag and drop operations on node list are not accurate if metadata or read-only values, like device type are involved.
  • 17903: Offboarding an offline node that gets online later can cause brute force protection to trigger.
  • 17908: Offboarding a node does not restore the node's default user, but the users from the Management System cannot log in.

Compatibility matrix

Refer to the table below for information on the compatibility between different components of the Nerve system with the current version of the Management System.

Management System version Node version MS/node compatibility Nerve Connection Manager (v3.0.8) Incremental node update Full support
3.2.0 2.2.0
3.2.0 2.2.1
3.2.0 2.3.0
3.2.0 2.3.1
3.2.0 2.4.1
3.2.0 2.5.0
3.2.0 2.6.1
3.2.0 2.7.0
3.2.0 2.8.1
3.2.0 2.9.3
3.2.0 2.10.0
3.2.0 3.0.0
3.2.0 3.0.1
3.2.0 3.1.0
3.2.0 3.1.1
3.2.0 3.2.0

Note

Update from Nerve Node 2.7.0 to Nerve Node 2.9.0, 2.9.1, 2.9.2 and 2.9.3 is supported.

Update from Nerve Node 2.10 to Nerve Node 3.0.0, 3.0.1 and 3.1.0 is not supported.

For more information on technical limitations (), and requesting assistance with setting up older versions in the current version (), contact a sales representative or write an issue through the TTTech Industrial support portal.

Scaling and performance limitations

This release has been tested to perform within the following scaling boundaries:

Maximum number of concurrent devices 200 
Maximum number of concurrently logged in users 5 
Maximum workload size 50 GB 
Maximum number of concurrent remote access sessions 3 
Maximum number of workloads in workload repository 200
Maximum data upload per node 5 datagrams per second with at least 10 sensor values for 200 nodes in parallel.