2024-12-20 - Release 1.8

Highlights

Initial support for Unified Namespace: Tricloud Nexus now supports collecting data from a MQTT Broker and write the measurement to other Data connectors. It also supports writing measurements from any Tag to an MQTT Topic.
Introduction of Update Center: Tricloud Nexus now features a new Update Center that allows easy management of both Module and Application updates across all devices in your fleet
Scheduled Deployments: Deployments of Device Configurations can now be scheduled to run at a predefined date-time from both Device Configuration, Deployments and Update Center
Improved Usability in Tag Configuration: Configuration of Tags now got a lot easier with a new and improved UI for easy configuration of Tags, Sampling rates, Access, storage etc.
Added new Tag Editors: Increased usability by adding several new Editors to customize Tag settings including ModBus- & Formula Editor
Import public containers: Added ability to import containers from public available docker registries, configure settings for the container and deploy them to devices

Added MQTT Read/Write support, making it possible to write any Tag to a MQTT Connector publish Topic
Added Update Center that allows updates of Modules or Applications to be performed immediately or scheduled across all devices in a single operation
Introduced UI for viewing and re-scheduling deployments in the management portal
Added new UI to support import and configuration of 3rd party containers from public docker repositories
Added Formula Editor that lets you easily specify advanced operations on the measurements using Tags as references
Added ModBus Editor to improve usability when configuring Tags for a ModBus connector
Improved Monitoring adding ability to see metrics from each running Module on the Information Tab of the Module
Hierarchy validation now supports less restrictive naming rules for data connectors
Management Portal now loads the last selected hierarchy when opening Asset modelling
Added support for Debian 12 in Edge compatibility
And many more...

Deployment is no longer possible if the Device Configuration contains an Application that no longer exist
Fixed delayed synchronization of asset hierarchy to ADX during initial deployments
Resolved errors related to Modbus read address validation
Fixed deployment scheduling issues, including incorrect or missing scheduled deployments
Addressed multiple UI inconsistencies, such as button placements and tooltip visibility
Resolved issues with duplicate modules and outdated deployment logs in monitoring views
And many more...

Removed support for legacy Asset Hierarchy naming convention based on only Asset.Tag naming. ISA95 naming convention is now the future standard

Last updated 7 days ago

Was this helpful?