Changelog
What changed in ATS Mini Controller, newest first.
September 11, 20262026.09
Added
- The app now recognises which firmware a connected radio runs and adapts to it. Radios on the official firmware need nothing configured: they are recognised silently, with no banner and no question.
- A profile for the ATS Mini Monster fork — its wider status frame, and its own faster commands for setting a band or mode directly and recalling a memory slot in one go. Written from the fork’s documentation and never exercised on a working radio: Monster publishes only an octal-PSRAM (OPI) image, and on the one radio this project ran it on, PSRAM failed to initialise and the app was left with nothing to control. A quad-PSRAM board is the likely explanation, though that board’s memory type was never established.
- ATS Mini Monster on GitHub(opens in a new tab)
- Support for H. J. Berndt’s firmware, which shares no wire protocol with the official one. Four controls are offered on it — screen capture, the memory listing, the station listing and the data-output toggle. Memory editing, the theme editor, calibration, sleep, the spectrum scanner and seek are absent from the page.
- That firmware accepts about one command every five seconds: buttons stay clickable, a countdown says when the next one can go out, and a change needing a burst of commands is refused rather than attempted. Its screen captures arrive as a raw image and took about six seconds on the bench.
- Switching to Berndt’s firmware always asks first, and the answer is remembered per radio. The app never adopts it on its own — that console reuses several of the official firmware’s characters and what they do there has not been established.
- H. J. Berndt’s firmware page (German)(opens in a new tab)
- A radio answering in a shape the app does not know is named as no firmware at all, and everything it is sent is paced at the slowest rate any supported firmware needs. Any choice is reversible: “Not this firmware?” in the Connection panel clears it and re-detects on the next connection.
Changed
- Controls a connected firmware cannot serve are absent from the page rather than shown greyed out — what is not there cannot be reached by its keyboard shortcut either.
- Keyboard shortcuts follow the connected firmware: only the ones it understands are listed and active.
- Status readings a firmware does not send show as a dash rather than 0, so an empty field cannot be read as a real measurement.