Roadmap
Where the project is now, the steps to 1.0, and why merge requests for instruments make sense from 1.0 on.
- Public
- 0.7.0
- Next
- 0.8
- Launch
- 1.0
- Merge requests for instruments
- from 1.0 on
Why this road
benchControlPlatform started as the owner's tool for the instruments on their own bench. It is being rebuilt so that adding your instrument is easy, and so that every instrument added keeps the project clean: shared parts for what all instruments need, and one place for what is yours.
Until 1.0, the code under an instrument changes with every step on this road. A merge request for an instrument written against today's structure would have to be redone after the next step, and that would waste your work.
So merge requests for instruments make sense from 1.0 on.
Until 1.0
The most useful things you can do now:
- Try the app without hardware, in demo mode: Getting started.
- Read the guide to see how an instrument gets in: Add an instrument.
- Tell the project which instrument you would add: open an
Instrument-requestissue on GitLab. It asks for the maker and model, the interface, the protocol documents you know of, and whether you can test on the hardware.
You can add an instrument for yourself today, as the guide describes. For a merge request, 1.0 is the right time.
The steps
Each step is a minor version. Now: 0.7.0 is public, and 0.8 is next.
-
0.6
public
Fixed pages, open source, the front door
A fixed page for each instrument instead of movable cards. The license, the contribution rules, the templates and the pipeline. The new name, the README, the manual, the architecture and device pages, the guide for coding agents, and a Linux build. What it brought: Changelog.
-
0.7
Nowpublic
Supply kit
One contract and one shared worker for every power supply, a device list,
BCP_DEVICESto pick the active devices, and a simulated supply. A supply with a protocol of its own is now one folder, two lines in the device list and its doc page. What it brought: Changelog. -
0.8
next
Supply profiles
A power supply that speaks Modbus RTU is described by one config file in the repository, without Rust code. The HM310T becomes the first profile. A device that nobody has confirmed on the hardware starts with readings only.
-
0.9
planned
Scope and meter on the device list
The oscilloscope and the USB meter move behind the same device list as the supplies, so that the app itself names no instrument.
-
0.10
planned
Guides
A guide for each way to add an instrument, proven by letting coding agents add instruments from the docs alone: each has to pass the checks and touch only the files its way allows.
-
1.0
planned
Launch
A tagged release with release notes and the first issues for newcomers. From here on, merge requests for instruments are welcome.