Serial Port Utility 6.6.7

Features

• A restricted device is told why, instead of quietly running on: The server can now restrict a machine by device (for instance after a license activated on it was refunded). On the next launch report, the application closes its ports, shows a "Device restricted" dialog with the server's explanation, a contact address and a link to the Terms of Service, and exits when it is dismissed. The verdict is cached on the machine: the next launch asks the server once more (up to 5 seconds) and shows the main window only on an explicit "not restricted"; a refusal or an unreachable server ends in the same dialog, with a hint to connect to the internet and start again if the restriction has been lifted. A machine that was never restricted is untouched, and an unreachable server still lets it through. The App Store build takes no part in this

Interface

• The registration prompt now explains where Free ends and Pro begins: The direct build's "30-day free trial" window still spoke shareware — "after the trial period you must register the program or remove it from your computer" — which is no longer how the product works: Free stays available when the trial ends. The window is now titled "Free and SPU Pro" and says that direct downloads include a 30-day Pro trial from first launch with Free available afterwards; that Free supports one connection and local logs while Pro unlocks multiple connections, bridges, the Modbus request builder, file transfer and settings sync, with saved project files and logs kept either way; that a Personal license bound to an Alithon account activates the signed-in computers and Enterprise activation follows the seat count; and that Live Sync is available in Free within its cloud traffic limits. The buttons read "Buy SPU Pro" and "Continue trial" or "Continue with Free", whichever applies. The App Store build's subscription note likewise opens by saying that Free basic debugging needs no subscription. The Windows installer's license text says the same

Fixes

• A colleague signing in was refused an enterprise key once the buyer had bound it: A bound key answered to its owner's sign-in alone, whatever its edition — but an enterprise key is bought as a number of seats for machines that several people sign in to, and the buyer is rarely the one at the keyboard. Once they ticked the binding, a colleague typing the same key got "This license key is bound to a different account", and signing in with their own account at startup wiped the machine's enterprise activation. An enterprise binding now only says who manages the key: it appears in that account's dashboard, seats can be released from there, and colleagues keep activating seats with their own accounts and keep them on sign-out. Only a personal key is its owner's alone. The binding hint in the license window says so for enterprise keys
• A refunded or disabled license stayed Pro on the machine it was activated on: Once the server disabled a key (refund, administrator action), every launch merely added a "DISABLED LICENSE" warning box; the machine's own license data was left untouched and Pro kept working until the expiry date. A disabled reply now clears the local license the way a sign-out release does, switches to the free edition and warns once; the application keeps running