Change Log

2 min lire

December 5, 2025

v0.6.0 (2025-12-05)

Timeline Scrubbing: You can now jump to any point in a profile’s timeline using the new slider. This is available in both the Profile Card and the main Playback controls, allowing for quick adjustments to the elapsed time.
Pressure Cylinder HOLD: Double-tapping UP on the joystick now triggers a “HOLD” function. This captures the current pressure as the new setpoint and automatically switches to Auto mode to maintain it. This feature can be enabled/disabled via settings.
Settings Memory: The machine now remembers your “Interlocked” and “Mode” settings for the Pressure Cylinder even after a restart.
Pressure Profiles: There are now 4 instead of 1 pressure profiles.
Warmup Notification: A buzzer now sounds when a temperature profile completes its warmup phase and begins running.
Sound feedback for Temperature Profiles: The machine now makes a sound when a temperature profile warmup phase is completed.

Pressure Cylinder:
- Unified manual control logic for single and multi-cylinder modes, ensuring consistent overload protection.
- Improved stability of mode transitions and loadcell handling.
Visual Feedback:
- Added a “Disconnected” icon (crossed-out WiFi) to Controller Cards and Pressure Cylinder controls. This appears immediately if the connection is lost, so you know when data is stale.
- Added a “Profile” badge to Controller Cards to clearly show which profile is currently active.
- Enabled buzzer sounds for key profile events.
Profile Editor:
- Fixed text readability in the description field when using Dark Mode.
- Optimized button layout for better usability on mobile devices.
Safety:
- Added safeguards to prevent accidental pressure application when no profile is running.
Fixes:
- Better handling of disconnected devices over Modbus.
- Restore IsSlave, ComWrite after reboot.
- Restore Omon & Temperature profile enabled state after reboot.
- Profile Timing: Fixed an issue where the profile timer would start counting during the warmup phase. The timer now correctly starts only after the profile enters the running state.