This page contains a list of features, changes, known issues and known limitations of the Nerve Blue releases. Updates are listed in reverse chronological order.
Version 2.0.0 is the initial release of Nerve Blue. It was released on August 23rd, 2019.
|Base System||Debian 10 (Linux Kernel 4.19.0)
|OS Support||Linux and Windows (as virtual machine)|
|Management System||Management system available on premise and/or cloud based
Deployable as Linux Docker with browser-based GUI
View status of connected edge devices
Secure onboarding of new edge devices
Supports low bandwidth and intermittent connections to edge devices
Over-the-air patching and bug fixes
|Workload Management||Workload (virtual machine, container and CODESYS program) repository in Management System
Workload management (deployment and updates) remotely via Management System
Assignment of device resources to workloads
Selective application deployment to mitigate user error
Workloads accessible from the external network
|Soft PLC||CODESYS 3.5 (PROFINET Master/Slave, EtherCAT, Modbus TCP/IP)
Hosted as real-time virtual machine to ensure isolation from interference
Cycle time 1ms
Program management (deployment and updates) remotely via Management System
High performance connection of the application to the datapath
|Database||Timescale Time-Series Database locally
MongoDB in the Management System
|Cloud Protocols||MQTT / JSON|
|User Management||Basic Role-based access control to Management System|
- When ports are reserved for Docker containers, they are always reserved on all interfaces.
- UDP port mapping is not available for Docker containers.
- To provision a CODESYS workload, the CODESYS project files have to be obtained via SSH in the command line.
- Registering a node in the Management System requires a command line tool.
- Ports 443 and 8883 have to be open for communication between node and Management System.
- Updating to a later version of Nerve Blue is not supported.
- Persistent variables for CODESYS workloads do not work. Values are reset when a CODESYS workload is stopped.
- The RAM display in the local UI does not show the total memory of the device. The amount of memory that is displayed does not include the memory that is reserved for memory pinning.
- The docker0 interface receives an IP address in the default Docker network range. Assigning an IP address manually is not possible.
- A deployed workload cannot be updated. To deploy a new version of a workload, the old version of the workload needs to be undeployed first.
- Once a deployment has been started, it cannot be canceled by the user.
- When a Virtual Machine workload is deployed with the name codesys, the CODESYS runtime is removed from the system.
- When a registered node is disconnected from the network, the WAN address does not refresh automatically in Management System.
- Deleting a CODESYS application from the Nerve Device using Delete application from device in the CODESYS Development System causes the deployment process of CODESYS applications from the Management System to break.
- Renaming the header of the application in the CODESYS Development System from Application to something else causes the deployment process of CODESYS applications from the Management System to break.