Modbus Connect v0.3.1: Hotfix & Stability
A focused hotfix release addressing critical bugs in connection handling, register configuration, and chart synchronization.
What's Fixed
- Modbus connection error handling (error 10053)
- Register configuration persistence
- Linear scaling in MonitoringLive
- Chart popout synchronization
- Chart data overlapping between registers
Major Fixes
Connection Error Handling (Error 10053)
Fixed critical I/O error handling by detecting unhealthy connections and discarding them. The application now forces fresh connection creation on the next poll, preventing cascading failures.
Register Configuration Persistence
Fixed configurations not persisting when switching sessions. Configurations are now properly loaded from the backend when a session is selected, and the workspace is marked as modified when configurations are saved.
Linear Scaling in MonitoringLive
Fixed scaling calculations by ensuring register format is set in the backend before applying scaling configuration. Scaled values now display correctly with proper units.
Chart Popout Synchronization
Fixed chart popout windows not syncing historical data. lastUpdateTime is now reset to include all historical data when initial sync is received from the main window.
Minor Fixes & Improvements
Fixed chart data overlapping between registers by including address in duplicate detection
Fixed chart point disabling by updating datasets in-place instead of replacing them entirely
Resolved all cargo clippy warnings for cleaner codebase
Fixed logger not creating new file when logfile is deleted while logging is active
Fixed Create chart menu label editing by restructuring modal layout
Fixed "Keep current devices" checkbox to be checked by default (opt-out instead of opt-in)
Removed redundant HEX/DEC/Binary format buttons from MonitoringLive and ModbusLogDialog
Fixed start address validation to allow address 0
Fixed workspace loading to restore start address and offset in ModbusReader
Fixed DataLoggerManager logging output to include function code specific register address
Fixed DataLoggerManager CSV output to include label field
Fixed TypeError when clearing workspace
Fixed register format not persisting in ModbusLogDialog
Fixed formatted register values not displaying in logging output
Fixed scale factor and offset not getting default values when enabling custom calculations
Fixed label not loading in RegisterConfigModal after being set in MonitoringLive
New Features
Documentation Offset Support
Added documentation_offset field in ModbusReader to align with documentation that starts at register 1 instead of 0. This makes it easier to work with device documentation that uses 1-based indexing.
Why This Hotfix Matters
v0.3.1 addresses critical stability issues that could impact production monitoring:
- 🔌Reliable Connections:
Better error handling prevents connection cascades and ensures monitoring continues reliably.
- 💾Configuration Persistence:
Your register configurations now persist correctly across sessions.
- 📊Accurate Data:
Scaling calculations and chart synchronization work correctly for accurate monitoring.
- 🧹Code Quality:
All clippy warnings resolved for a cleaner, more maintainable codebase.
Download v0.3.1 Today
Modbus Connect v0.3.1 is available now as a free download for Windows, macOS, and Linux.
Recommended for All Users
If you're using v0.3.0, we recommend upgrading to v0.3.1 to benefit from these critical stability improvements.
Download v0.3.1What's Next
We're already working on v0.4.0 with major UI improvements, write operations, and Modbus RTU support. Stay tuned!