We can’t communicate directly with instruments or DUTs via Runner. This means I can’t, for example, manually perform a measurement using the multimeter via the panel.
Will this API ever be expanded?
Why isn’t the runner open-source?
We can’t communicate directly with instruments or DUTs via Runner. This means I can’t, for example, manually perform a measurement using the multimeter via the panel.
Will this API ever be expanded?
Why isn’t the runner open-source?
Hi!
You’re correct that the Runner/Session API today is oriented around the sequencer: loading, editing, and running test plans; managing ComponentSettings and streaming logs and results. It does not expose a generic “call this method on that Instrument instance” channel, and it has no concept of opening an instrument’s front panel.
The Runner is initially developed with the goal of being able to recreate a remote version of KS8400.
The API of the Runner grows regularly and we are not dismissive of an API like the one you’re requesting. Can you elaborate on the details of the API you are looking for?
The Runner is a Keysight-maintained product and is licensed as part of the PathWave Test Automation Cloud ecosystem rather than released under an open-source license.
I can’t speak to longer-term licensing decisions.