Modbux 2.1.0

Release Notes — Modbux v2.1.0

Modbux v2.1.0 adds RTU server mode, hostname support for TCP connections, and Linux build support.

Highlights

RTU server mode: Serve Modbus registers over a serial port. Connect physical devices or USB converters directly to the Modbux server. All register types, value generators, and booleans work the same as TCP — just toggle to RTU and pick your COM port. The status indicator doubles as a reconnect button.

Hostname support: TCP client connections now accept any hostname or IP address, not just localhost.

Linux support: Verified builds and packaging for Linux. Privileged port errors are handled gracefully, and the README includes Linux-specific setup notes for serial port access and unprivileged ports.

What's New

• RTU server mode with COM port selection, baud rate, parity, data bits, and stop bits
• RTU status indicator with click-to-reconnect
• Hostname/IP input for TCP client connections
• Linux build support tested on Mint
• Graceful handling of privileged port errors (EACCES) on Linux
• Shared serial port components between client and server
• yarn socat convenience script for virtual serial pair testing

Modbux 2.0.0

Modbux v2.0.0 is here! 🎉

New data types, a completely redesigned server boolean experience, and a bunch of quality-of-life improvements across the board. If you're upgrading from v1.x, your configs migrate automatically.

Highlights

12 data types: Bitmap joins the lineup: expandable 16-bit detail panel with per-bit toggles, colors, and comments. Plus UTF-8 strings, Unix timestamps, and IEC 870-5 datetime, each with a DateTimePicker and UTC toggle in the server.

Server booleans, redesigned: Individual address rows with toggle circles, inline comments, auto-increment add, and hover-to-delete. No more bulk add/remove.

Read configuration: Now shows a group index column so you can see which registers are read together, and displays read errors inline per group instead of a single snackbar.

Configs that just work: Versioned config files with automatic v1 → v2 migration. Endianness is now global per server instead of per register. Old configs load seamlessly; newer ones show a warning instead of crashing.

What's New

• Bitmap data type for client and server registers
• UTF-8 string, Unix timestamp, and IEC 870-5 datetime server register types
• Time-based value generators for Unix and datetime types
• DateTimePicker with UTC toggle for setting Unix/datetime values in fixed mode
• Read configuration improvements: group index column ("G") with alternating tints, and read errors displayed inline instead of snackbar notifications
• Endianness included in client config export/import

What's Changed

• Endianness is now a global per-server setting instead of per-register
• Config files include version, modbuxVersion, and littleEndian fields
• Read configuration replaces the separate View Configuration button, its functionality is merged into the toggle
• Scan dialogs use address + length instead of min/max range
• Address base simplified, conventional address column removed; 0/1 toggle shifts displayed addresses by +1 while the underlying register address stays the same
• Server booleans redesigned with individual rows, comments, and inline editing
• Collapsed boolean panels hide content for a clean overview

Bug Fixes

• Off-by-one in server register arrays, address 65535 now works correctly
• Register not removed from mapping when data type set to "none"
• UTF-8 value column offset after non-ASCII registers
• Client polling resumes on reconnect
• Windows e2e compatibility

Breaking Changes

Important

• Configs saved in v2.0.0 cannot be opened in older Modbux versions, keep backups if you need to downgrade
• Per-register endianness replaced by a global setting, mixed-endianness configs use majority voting with a warning
• datetime register length corrected from 2 to 4 registers (IEC 870-5)

Upgrading from v1.x

Old configuration files are automatically migrated when loaded. localStorage state is also migrated on startup. No manual steps required.

If a v1 config had mixed endianness (some registers little-endian, others big-endian), the most common setting is applied globally and a warning is shown. Ties default to big-endian (Modbus standard).

Changelog

Full Changelog: v1.4.2...v2.0.0

Modbux 1.4.2

Bug fix

Multi-register data types now properly cleaned up on removal

When removing or editing multi-register types (INT32, UINT32, FLOAT, INT64, UINT64, DOUBLE), only the first register was reset to 0. The remaining registers retained stale data, causing ghost values in the server.

This affected:

• Deleting a multi-register entry via the trash button
• Editing a register and changing its address

Example

Adding an INT32 at address 0 with value 70000 writes to registers 0 and 1. Changing the address to 10 would leave register 1 with stale data (4464). This is now fixed — all occupied registers are correctly reset.

Full Changelog: v1.4.1...v1.4.2

Modbux 1.4.1

What's New

Critical Bug Fix

• Coil/Discrete Input Sync — Fixed a critical issue where changes to boolean registers (coils and discrete inputs) were visible in the UI but not actually saved to the Modbus server, causing incorrect values when reading from clients.

New Features

• Update Notifications — The app now checks for new releases on startup and shows a dismissable notification banner when updates are available.
• Improved Add Register Dialog — New "Add & Next" button keeps the dialog open and automatically increments to the next address, making it faster to add multiple registers in sequence.

Quality Improvements

• Comprehensive Testing — Added extensive automated tests to ensure stability and catch bugs earlier.

Full Changelog: v1.4.0...v1.4.1

Modbux 1.4.0

What's New

Features

• Serial Port Autodiscovery — The manual COM port input has been replaced with an autocomplete dropdown that lists all available serial ports (including /dev/tty* on macOS/Linux), with manufacturer info and support for custom paths. Includes refresh and validate buttons.

• Unit ID Range Expansion — Supported Unit IDs now cover the full 0–255 range.

Bug Fixes

• Reconnect Cancellation — A pending reconnect can now be canceled by clicking the connect button, which shows a spinner during the attempt. The duplicate "already disconnected" warning has been suppressed.

• Reconnect Burst Detection — Auto-reconnect now stops after 5 consecutive failed attempts, preventing infinite reconnect loops. The snackbar shows the current attempt count (e.g. "Connection lost, reconnecting (3/5)..."). The counter resets after 10 seconds of stable connection.

Full Changelog: v1.3.8...v1.4.0

Modbux 1.3.8

What's New

Bug Fixes

• Fixed Unit ID dropdown on new servers - The Unit ID selector now works immediately after creating a new server instance (fbb2d2f)
• Corrected Unit ID range - Limited to 0-247 (248 total) per Modbus specification

Documentation

• Complete wiki documentation now available - Check out the full documentation with guides for both Client and Server modes

Other Improvements

• Updated README with clearer feature overview

Full Changelog: v1.3.7...v1.3.8

Modbux 1.3.7

First Public Release 🎉

A Modbus TCP/RTU client & server tool born from real commissioning frustration.

Battle-tested over the past year. Full datatype support, simultaneous interpretation views, address scanning, and device simulation in one app.

Download the build for your platform below and/or check the README for details.

---

Issues and contributions welcome.