After the QSPICE update recently, I noticed that there is an additional SCPI option in the file menu, but I did not find the corresponding introduction in the help document. Does anyone know its purpose?
This feature is currently under development. It will allow QSpice to connect to test equipment that supports SCPI (Standard Commands for Programmable Instruments).
Currently, if you have the Keysight IO Library with VISA connected to your equipment, you may be able to read its *IDN? string via the Set Resource String option. The ultimate goal is to import oscilloscope waveforms or component data directly from LCR meter measurements.
Only limited information at this moment.
5 Likes
SCPI has been renamed to Test Gear. It is still in an early phase, and according to Mike, it currently supports the Hantek 1833C handheld LCR, Rigol DHO924S oscilloscope, Bode 500… and an instrument I recommended, which is the NanoVNA.
The NanoVNA is a low-cost vector network analyzer (~100 USD or less, depending on the model) that measures S11 and S21. If you know how to use a network analyzer, it means you can also use it as a LCR meter with S11 data. I work at frequencies lower than a few hundred MHz, and it works well. This uses a USB COM port; therefore, it is not SCPI, but Test Gear supports it.
Here is what can possibly be achieved with Test Gear in a Qspice simulation currently. (Again, this may be subject to change. As @FunMod raised this question and things more stable just this week, I am sharing this for your information.)
Revision History: 05/08/2026 The NanoVNA is now supported even without the NI-VISA drivers.
4 Likes
Test Gear is formally released and Help Document is added to Qspice.
05/29/2026 Documented interfacing to test gear.
1 Like
I think the Test Gear function in QSpice is a very useful tool. However, according to the reference documentation, it currently only supports Rigol oscilloscopes. My laboratory mainly uses Tektronix and Keysight oscilloscopes. I know that SCPI commands vary slightly among different manufacturers. Can I develop custom code to enable this tool to support more oscilloscope models? That would let me view measured data directly in the simulation tool much more conveniently