Used with physical laboratory hardware
The integration has been exercised in real measurement work and is a core commercial target.
Hardware integration
Focused coverage for the instruments laboratories actually use.
Instraxis does not need an unlimited catalog to create value. It needs the relevant environment systems, sources, meters, lock-ins and switching hardware to cooperate inside a complete measurement workflow.
System topology
The experiment is a coordinated system, not a list of independent drivers
The environment controller supplies temperature and field while Instraxis coordinates the complete instrument stack and presents one user workflow.
Hardware matrix
Search the current integration portfolio
Status wording distinguishes field-tested integrations, implemented integrations and hardware that requires a custom assessment.
| Manufacturer | Model / family | Category | Current capability | Status |
|---|---|---|---|---|
| Quantum Design | PPMS | Environment | Temperature, magnetic field and chamber workflow | Field-tested |
| Quantum Design | DynaCool | Environment | Temperature, magnetic field and chamber workflow | Field-tested |
| Stanford Research Systems | SR830 | Lock-in | Multi-lock-in parameter control and acquisition | Field-tested |
| Keithley | 6221 | Source | Current source, waveform and linked-scan workflows | Integrated |
| Keithley | 2182A | Nanovoltmeter | Low-level voltage acquisition and paired workflows | Integrated |
| Keithley | 2000 | Multimeter | General-purpose measurement channels | Integrated |
| Keithley | 3706 / 3721 | Switch / MUX | Multiplexed resistance and slot scans | Integrated |
| Zurich Instruments | MFLI | Lock-in | Demodulator acquisition, range and time-constant control | Field-tested |
| Yokogawa | GS200 | Source | DC voltage / current source workflows | Integrated |
| iMACRT | MMR3 / MGC3 | Temperature / heater | Network-based sensor and heater control | Integrated |
| Other manufacturers | Additional instruments | Custom | Assessment and integration available | Custom integration |
No hardware entries match the current filters.
Support levels
Clear claims are more valuable than a large unchecked list
Commercial documentation should distinguish what has been used on real hardware from what is implemented or offered as custom integration.
Implemented in the product
The driver and user workflow are present, while validation depth may depend on model, firmware and laboratory configuration.
Assessed against a paid use case
New devices are added when they support a real customer workflow and can be tested responsibly.
Integration process
Adding a device starts from the experiment, not only the command manual.
Existing libraries such as PyMeasure and QCoDeS can accelerate the low-level driver work. The commercial effort is still the user-facing workflow: parameter dialogs, conditions, measurement context, data columns, testing and reliable behavior with the rest of the system.
- Define the measurement roleSource, readout, lock-in, switch, environment or custom subsystem.
- Design the operator dialogExpose the parameters users actually need for the target experiment.
- Validate in a complete sequenceTest communication, timing, output and interaction with other devices.
Driver only
- Read and write device parameters
- Low-level transport and parsing
- Developer-oriented interface
Product integration
- GUI parameter workflow
- Sequence commands and validation
- Measurement data and live visualization
Do not see your instrument?
Send the model, connection type, target measurement and the other devices it must coordinate with. The integration can be assessed before quotation.