benchControlPlatform
Project

Changelog

What is done, by version, newest first. It starts at the rebuild of the interface. What comes next is on the roadmap.

Version 0.7.0 public

Public on GitLab since 2026-11-15. The supply kit: every power supply goes through one contract and one worker, a list of devices decides which ones a run has, and a new supply is a folder of its own.

One contract and one worker for every supply

  • Every power supply implements one contract, SupplyDriver, and says what it has in its SupplyInfo: its fields, rows, memory slots and connection settings. The supply page draws from that and names no device.
  • The HM310T and the IPS3608 run on one shared supply worker, a thread per supply. What they send to the instrument, in which order and how often, stays the same.
  • The Logs page and the status bar name a supply by its device id, such as fnirsi-ips3608.

The device list and the devices of a run

  • src/devices/mod.rs lists every device, one entry per device folder, and a page is picked by the device's id.
  • BCP_DEVICES picks the devices of a run by id, in tab order and at most five, in demo mode and in a normal start, for example BCP_DEVICES=fnirsi-ips3608,fnirsi-fnb58. Without it the app takes active_devices from settings.toml, else the four starter devices. A device that is not active has no tab, no worker, no port scan and no demo data, and "All outputs off" leaves it alone.
  • BCP_TAB takes a device id. The old names rigol, hanmatek, fnirsi and fnb58 still work, and so does logs.
  • A slip in active_devices costs only that key: an unknown or repeated id is left out with a warning on the Logs page, a value that is not a list of ids is left out as a whole, and the rest of settings.toml loads.
  • A settings.toml without selected_tab loads and opens the first page; before, the whole file gave way to the defaults.

A settings table per supply

  • Each supply keeps its connection settings in a table of its own, such as [devices.fnirsi-ips3608].
  • A file of before loads with every value. The app writes the older keys alongside, so a build of 0.6.0 still reads the file; when that build saves, it drops the tables.

The simulated supply sim-psu

  • A power supply in memory, with no instrument and no port: setpoints, OVP, OCP and OPP, an output, six presets and a fixed 10 ohm load. It works in CV or CC and trips when a reading goes above a protection value.
  • It gets a tab only when you name it: BCP_DEMO=1 BCP_DEVICES=sim-psu cargo run. Its status is simulated, and its page is docs/devices/sim-psu.md.

Adding a supply

  • A supply with a protocol of its own is now its folder, its doc page and two lines in src/devices/mod.rs, and touches no other central file. The one to copy is src/devices/sim_psu/.
  • Guard tests check the device list against the head tables of the device pages and the README rows of the four starter devices, scan for device names the app's shell must not use and for the imports between the layers, and check each supply's contract. The tests of the supply page run for every supply of the list.
  • The Device merge request template asks for the device page. A change to the registers or writes of a verified device needs the template's evidence again, or sets the device back to experimental.

Merge requests for instruments

  • The README, CONTRIBUTING.md and the Instrument-request template say that merge requests for instruments make sense from 1.0 on, and that until then an instrument request as an issue is welcome.

Version 0.6.0 public

Public on GitLab since 2026-11-15. It has three parts: the interface rebuilt as fixed pages, the paperwork of an open source project, and a front door for people who want to add their own instrument.

The UI rebuild: fixed pages instead of movable cards

  • One window with a fixed page for each instrument: nothing to drag, resize or collapse.
  • A tab bar on every page with the connection, the state and the key values of all four instruments, Connect for one that is not connected, and "All outputs off" for the supplies.
  • The oscilloscope page: a toolbar, live waveforms with cursors, four channel tiles, an inspector with measurements, cursors and acquisition, and a SCPI console under the plot. Values can be typed with a unit, such as 500 mV or 1.5 ms.
  • One page layout for both power supplies: readouts, setpoints, protection limits, six memory presets and a trend. A stepped value is sent only when you apply it.
  • The meter page: readouts, three trend strips, session totals, and a recording of every sample to a CSV file.
  • Actions without undo need a second click: a memory recall while the output is on, and the reset of the meter's totals.
  • Demo mode: the whole app with fixed sample data and no instrument, to try it and to make screenshots.
  • A status bar with the latest log entry, and a Logs page.

Open source paperwork

  • The license: MIT OR Apache-2.0, at your option. Contributions are licensed the same way; there is no agreement to sign.
  • Contribution rules in CONTRIBUTING.md: when a device is verified or experimental, a test from bytes captured on the real instrument, a doc page for each device. And a code of conduct, CODE_OF_CONDUCT.md.
  • Issue templates Bug and Instrument-request, and merge request templates Default and Device.
  • A pipeline on GitLab with four checks, each of which has to pass: formatting, clippy without warnings, the tests, and the licenses of all dependencies.

The front door

  • The new name: benchControlPlatform, was homeControlPlatform. The binary is bench-control-platform and the variables start with BCP_. A start that finds no settings in the folder of the new name copies them from the old one, if there is one.
  • A README that leads with adding your own instrument.
  • A manual for every page, the settings file and the hardware tests; a description of the architecture; a page for each instrument with its protocol, timing and limits; and a page on the platforms that marks what was tried.
  • AGENTS.md, the guide for coding agents: the commands, a map of the code, the hard rules, what to reuse, the files a device touches and the definition of done.
  • The old card interface, Classic, is removed: the fixed pages are the only interface.
  • Linux: the build and the tests pass in the rust:1.94.1 container. The app was not started on a Linux desktop.
  • The screenshots come from one script that runs the app in demo mode.

Everything before the UI rebuild is the baseline the project started from, and is not listed here.