Settings¶
Settings are split between per-server settings and application settings.

Per-Server Settings¶
Per-server settings control endpoint, identity, data representation, write behavior, startup memory, and traffic shaping.
Stop the server before changing endpoint or protocol behavior settings.
Open per-server settings by selecting a server and choosing Settings in the main navigation. You can also right-click a server in the server list and choose Server settings.
Application Settings¶
Application settings control preferences shared by the whole app:

- color mode;
- address base;
- classic address display;
- record creation behavior;
- grid layout reset;
- window layout reset.
Use Color mode to choose light, dark, or system theme. Use Address base and Classic address to control how Modbus addresses are displayed across memory, watches, logs, and diagnostics.
When Use last values is enabled, new watches, simulation rules, fault rules, and reactions start from the currently selected row, or from the last row when nothing is selected.
Layout Persistence¶
ModbusLab saves:
- selected page;
- window placement;
- grid column widths;
- hidden columns;
- pinned columns;
- editor window placement.
Use layout reset actions if a grid or window becomes inconvenient after experimentation.
Project Storage¶
ModbusLab stores its active configuration in the current user's local application data folder and keeps best-effort backups when saving.
This keeps runtime configuration separate from the source repository and makes the published executable self-contained.