This overview summarizes the highlights and technology updates of the FabEagle®Connect 3.x and 4.x minor releases. Patch versions are listed for orientation, while individual patch-level fixes are summarized only where they are relevant to customers or operators. Internal implementation details, low-level dependency changes, and security implementation specifics remain available in the original release notes within the product documentation.
Version History
| Version | Release Period | Patch Versions | Status | Platform |
|---|---|---|---|---|
| 4.3 | 16 Feb 2026 - 25 Mar 2026 | 4.3.0, 4.3.1, 4.3.2, 4.3.3 | Active | .NET 8 |
| 4.2 | 23 Sep 2025 - 14 Jan 2026 | 4.2.0, 4.2.1, 4.2.2 | Active | .NET 8 |
| 4.1 | 31 Jul 2025 | 4.1.0 | Active | .NET 8 |
| 4.0 | 30 Dec 2024 - 26 May 2025 | 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5 | Active | .NET 8 |
| 3.2 | 05 Apr 2024 - 25 Nov 2024 | 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8 | Obsolete | .NET 6 |
| 3.1 | 24 Jul 2023 - 08 Mar 2024 | 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, 3.1.8, 3.1.9, 3.1.10, 3.1.11 | Obsolete | .NET 6 |
| 3.0 | 04 Jul 2023 | 3.0.0 | Obsolete | .NET 6 |
Version Details
Release period: 16 Feb 2026 - 25 Mar 2026
Patch versions: 4.3.0, 4.3.1, 4.3.2
Product status: Active
Technology stack: .NET8
- Introduced Audit Trail capabilities for security-, lifecycle-, and configuration-related events, including a dedicated web client view with filtering and auto-refresh.
- Extended OPC UA Server configuration with flexible IP binding and support for multiple configured addresses.
- Added configurable MQTT partner-connection handling and enabled selected application-log writes from Code snippets.
- Improved reliability across OPC UA Client write handling, FileReader processing, Modbus reconnect behavior, Buffer logging, and frontend diagnosis workflows.
- Updated OPC UA components and expanded deployment documentation, including Docker and KontronGrid container guidance.
Release period: 23 Sep 2025 - 14 Jan 2026
Patch versions: 4.2.0, 4.2.1, 4.2.2
Product status: Active
Technology stack: .NET8
- Introduced the settings area in the web client, including general settings, license management, user management, and related configuration options.
- Added user-management functions with role and rights handling, stronger password policy enforcement, and password reset support.
- Extended the installer and release package with PLC interface, SECS/GEM, migration guide, and TestTools content.
- Reworked the component connection-state concept and improved visibility of component states in the web client.
- Strengthened OPC UA behavior across heartbeat, authentication, write sequencing, handshake handling, reconnect behavior, and node-field validation.
Release period: 31 Jul 2025
Patch versions: 4.1.0
Product status: Active
Technology stack: .NET8
- Added the PLC Interface community component and introduced dynamic node support in the OPC UA Server.
- Added HTTPS support for the web client and extended REST component support for XML messages.
- Expanded Docker delivery with release images for future versions and ARM-compatible image variants.
- Improved import/export handling, TCP/IP connection behavior, frontend graph display, and database validation.
- Introduced asynchronous logging as a platform improvement for performance and cross-thread stability.
Release period: 30 Dec 2024 - 26 May 2025
Patch versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5
Product status: Active
Technology stack: .NET8
- Established the 4.x product line on .NET 8 and refreshed the frontend dependency base.
- Added SECS/GEM as a community component and introduced migration guidance for custom components between major versions.
- Improved Code component capabilities, including direct acknowledge support and clearer input/output documentation.
- Enhanced diagnosis, logging, validation, and runtime checks to support more robust operation and troubleshooting.
- Delivered broad reliability updates for ActiveMQ, OPC UA Client, REST, Buffer, File Reader, frontend reconnect awareness, and installer/runtime correctness.
Release period: 05 Apr 2024 - 25 Nov 2024
Patch versions: 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8
Product status: Obsolete
Technology stack: .NET6
- Introduced the Buffer component and expanded connection-state visibility for selected components.
- Improved FileReader partner-connection handling, installer examples, startup backup protection, and TCP/IP server connection-state display.
- Extended development capabilities with shared provider abstractions, richer XMLMessage support, logging checks, and filesystem abstractions for testing.
- Improved operator experience through diagnosis filtering, frontend help-area refinements, editor/layout behavior, and configurable Modbus reading modes.
- Delivered broad stability and maintenance updates across Buffer, Modbus, OPC UA, database components, licensing dependencies, and startup-state handling.
Release period: 24 Jul 2023 - 08 Mar 2024
Patch versions: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, 3.1.8, 3.1.9, 3.1.10, 3.1.11
Product status: Obsolete
Technology stack: .NET6
- Updated the frontend to Angular 16.1.4 and Angular Material with refreshed application UI and installer compatibility improvements.
- Expanded OPC UA Client capabilities, including partial array reading and writing, installer availability, reconnect improvements, and clearer diagnostics.
- Added broad logging improvements, including debug-level logging, helper methods, local font/icon delivery, and improved log access in the web client.
- Improved licensing behavior with component-level licensing, clearer unlicensed-operation handling, and better frontend visibility for demo or unlicensed states.
- Improved operational stability across TCP/IP, MQTT, RS232, code component handling, topology rendering, service installation, backend startup, and browser behavior.
Release period: 04 Jul 2023
Patch versions: 3.0.0
Product status: Obsolete
Technology stack: .NET6
- Provided the initial 3.x baseline release after the 2.x product line.
- Cleaned up obsolete source-code elements and corrected executable error-message content.
- Served as the stabilization basis for the subsequent 3.1 and 3.2 feature and maintenance releases.
Note: For project planning, migration, or support cases, use the detailed release notes and product documentation as the authoritative source for patch-level behaviour and compatibility details.