Community coverage
Help confirm instruments
420 of 426 supported models were written from the manufacturer’s programming manual and are waiting for someone with the real instrument. One person connecting one instrument once is enough to tell everyone else it works.
What the labels mean
- Bench-tested - runs on the maintainers’ bench; every reading and setting was checked against the real instrument.
- Community-confirmed - BenchMesh users connected it and it worked; the website lists the app versions it was confirmed on, and the app shows them in Instruments → Supported.
- Awaiting confirmation - written from the manual, built on the same engine as the tested instruments. Highly likely to work; not yet seen live.
How to confirm an instrument
- Install BenchMesh and connect the instrument by USB, serial or LAN.
- Open Instruments → Detect. BenchMesh asks each port who is there and offers to add what it finds.
- Watch the readings, change a setting or two, and open the instrument console (the icon in the panel header) to see the traffic.
- Report the result. Until in-app reports arrive (see the roadmap), open an issue on GitHub with the model and paste the console’s Copy output - it already contains the instrument’s identify reply, the connection and the app version.
Something did not work?
That is just as valuable. The console’s copied evidence shows exactly what was sent and received, so a definition can be fixed without the instrument being here. Most fixes are a few lines of YAML in the instrument’s definition - no new software needed.
Your instrument is not listed?
Ask for it on GitHub with a link to its programming manual. Instruments that speak SCPI over USB-TMC, LAN or serial usually need only a new definition.