CAN Triple Device Manager 1.1.16 — the per-user install can install the drivers (device firmware 1.0.5)

A small release with one functional fix, and a large change to what this repository publishes. The application itself is unchanged from 1.1.15 — same features, same device firmware 1.0.5. If your installs are the ordinary administrator kind and you are already on 1.1.15, there is nothing here you need.

The fix: a per-user install can install the drivers

Setup offers a per-user install for machines where you would rather not elevate. That route was silently skipping the ST-Link USB drivers, so the Initial Programming Tool could not talk to a probe and a blank board could not be programmed — with nothing on screen explaining why.

Windows does not allow a per-user driver install: the driver store is machine state, and no installer can arrange around that. What Setup can do is ask, and now does.

• A per-user install shows a Device drivers checkbox, ticked, that raises one elevation prompt after the files are copied.
• Declining is a supported answer, not a failure. The Manager talks to a programmed device over the serial port with no driver at all; only SWD programming of a blank board needs one. Setup says so once and carries on.
• A Start Menu entry, Install ST-Link USB Drivers, does it later — after a declined prompt, after admin rights arrive, or after another vendor's tool overwrites the driver store.

Administrator installs are untouched: still silent, still automatic, and the checkbox is hidden there so nobody is asked twice for the same thing.

The firmware is no longer published as source-shaped headers

This repository is meant to carry the firmware as a file — the .ctf, the bootloader, the programming kit — alongside the application's source and the installer. It was also carrying firmware/include in full: 22 headers, including the complete command table, the record layouts, the flash store's design and the licence record.

firmware/include is now four generated files: script_vm.h, script_exec.h, fw_image.h, and a protocol.h reduced to the one struct the others need. They are produced by stripping every comment from the firmware's own headers, so the declarations are byte-identical to the binary they describe while none of its reasoning travels.

A public clone still builds. That is checked rather than assumed: configuring and building this tree from scratch links both CANTripleDeviceManager.exe and CANTripleInitialProgramming.exe.

DESIGN.md is redacted to match. It keeps what a host integrator needs — the command table, payload shapes, chunk sizes, the capacities the application enforces, the store version Send checks — and loses the device's storage internals.

The repository's history was rewritten to remove those headers from earlier commits and release tarballs. If you have an old clone, re-clone rather than pull.

Documentation

The manuals and the published headers were corrected extensively against the code: a wrong device capacity, a command table missing nineteen opcodes, write-chunk sizes computed from record widths that had changed, and a stale description of what one access password gates. These were documentation errors only — no behaviour changed — but the wrong chunk size would have sent an oversized payload, so they are worth naming.

---

Install: download CANTripleDeviceManager-Setup_Windows_x64.exe below and run it. Windows 10/11 x64; the installer carries the Qt runtime, device firmware 1.0.5, the initial programming kit and the ST-Link drivers.