This page contains a list of features, changes, known issues and known limitations of the Nerve releases.
This version was released on June 15, 2021. Unless otherwise stated, all known issues and limitations of the previous version are still valid.
|Management System||Usage reports added for proper billing.
Customizable system notifications.
Easy node reboot through the UI.
Korean language support.
|Local UI||Easy node reboot through the UI.
Korean language support.
|Workload management||Video output at the Nerve Device for Virtual Machine workloads.
Modifiable resource definition for deployed Virtual Machine workloads.
Monitoring of the system and Docker workloads in Kibana dashboards.
Collection of Docker workload logs displayed in Kibana dashboards.
Workload update feature added for CODESYS and Docker workloads.
Custom configuration files can be added to deployed Docker workloads.
|Nerve Data Services||Added data buffering options to avoid possible loss of data during data transfer from the node to the Management System.
Implemented a GUI for the Gateway configuration.
The local Gateway is now the single point of configuration.
Added support for ZeroMQ Subscriber input and the NerveDB output.
- Fixed an issue where the license update file would disappear from the selection when attempting to activate a license offline on Windows.
- Fixed an issue where Docker logs would fill up the Docker partition.
- Fixed an issue where the CODESYS runtime would be missing after a power cycle.
- Fixed an issue where reverting the Management System to a previous version would cause data loss.
- Fixed an issue where the CODESYS runtime would have no license applied after a node update.
- Fixed an issue where the LDAP authentication switch would be enabled before performing a sync.
- Fixed an issue where an internal server error would be displayed wrongly.
- Fixed an issue where Docker workloads with a network containing
-in its name would not be available after a reboot.
- Fixed an issue where remote tunnels to Docker workloads with a network containing
-in its name would not work.
- Fixed an issue where on-premise Management Systems could not be updated.
- Fixed an issue where notifications in the Local UI would display incorrect messages.
- Restored real-time capabilities for Nerve versions without CODESYS.
- Fixed an issue where workloads would end up in a broken state if an error occurs during provisioning.
- Fixed an issue where workloads provisioned in previous product versions would be rendered undeployable after a node and Management System update.
- Fixed an issue where an
0003error code would appear when accessing the Management System.
- Fixed an issue where VMs would be restarted if there was a problem with a Docker workload.
- Fixed an issue where changing the network configuration for the wan interface would not be recognized immediately. A timeout would occur first and then the internet connection would be established again.
- Fixed an issue where node information at the top in the Local UI would not be displayed correctly.
- Fixed an issue where API permissions would be lost in user roles after a Management System update.
- Fixed an issue where deleted workloads could be falsely deployed again over API commands.
- Nerve Data Services: Fixed an issue where the Management System MQTT broker would stop functioning after a Management System update.
- Nerve Data Services: Fixed an issue where the Gateway crashes when trying to resolve an incorrectly configured namespace of an OPC UA Server source.
- Nerve Data Services: Fixed an issue where the database writer would restart unexpectedly many times.
- Nerve Data Services: Fixed an issue where the Gateway crashes if the source OPC UA server has two or more nodes with identical names but different data types.
- Nerve Data Services: Fixed an issue where only the first set of variables would be accepted by the Gateway if there are multiple sets with the same names from various tasks.
- Nerve Data Services: Fixed an issue where the database preview would not work if there was no space left on the device.
- Nerve Data Services: Fixed an issue where database table previews would not be displayed correctly if the title contained
- Various UI and workflow improvements for the Management System and the Local UI.
- Stability improvements.
- Improved the efficiency of creating workload version clones.
- The clock of the RTVM is now synchronized.
- Nerve Data Services: Enhanced the Gateway's OPC UA Client security features.
Known issues and limitations
- There is a display error for VM resource allocation. The Management System UI remembers the resources of the last clicked VM workload. This means that the resource allocation of VM 1 is shown when VM 2 is selected. Going back and selecting VM 2 again shows the correct resource allocation.
- If a workload is deployed to a node twice in a row while another deployment is still in progress, the node will enter a broken state.
- When updating the Management System from version 2.2.X to 2.3.X, cookies need to be cleared out in order for multiple features to function properly.
- Logging and monitoring dashboards might not open. This is due to duplicate cookies in the web browser. Deleting cookies fixes the issue.
- Exporting a workload may fail with a 403 error code. This is due to duplicate cookies in the web browser. Deleting cookies fixes the issue.
- The LAST SYSTEM START attribute in the node details displays incorrect times when a version 2.2 node is connected to a version 2.3 Management System.
- It can come to unexpected issues when a node loses power while a Docker workload is being updated.
- On Windows, when power is lost on a node that is in the process of a node update, the node will be stuck in the update state and cannot be updated anymore.
- Reverting the Management System to 2.2.X is not possible due to breaking changes in version 2.3.0.
- The CODESYS runtime would not have a decrypted license applied after an RTVM reboot.
- Nerve Data Services: The Nerve Data Services SDK cannot be used in this version.
- Nerve Data Services: Large amounts of data (e.g. 64 variables with 10 million rows) cause Grafana to become unavailable and data is not displayed correctly, causing constantly high CPU usage of the Nerve Device. This is due to an issue in Grafana.
- Nerve Data Services: The Gateway OPC UA Client does not handle arrays with more than two dimensions correctly.
- Nerve Data Services: If there are Docker workloads (e.g. analytics apps or an InfluxDB) using the
nerve-dpnetwork before updating the node to 2.3.0, these Docker workloads will stop working. However, they can easily be used again by changing the network to
nerve-dsfor the Docker workloads in the Management System and updating the deployed workload on the node.
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.|