aioscilloscope / Instruments

The instruments NovaOS runs on

NovaOS is one platform for test equipment of any make: our own Linux, our own acquisition and instrument software, and the same UI, SCPI, web control and AI tools on top. Each new instrument needs its own kernel port, board support and FPGA support; everything above that is shared. Here is every instrument we have NovaOS on or are bringing it up on, and how far each has got.

CH1Oscilloscopes

Rigol DHO800 / DHO900

NovaOS runs daily on our DHO924S: Linux 6.12 on the RK3399, the scope screen about 14 s after power-on, 2.5× stock's waveform rate. DHO802 to DHO924S. Download opens after a legal review.

 Rigol MHO900

NovaOS runs daily on our MHO934, from the same image as the DHO: 4 GSa/s, both generators, interleave spurs below stock's. MHO934, MHO954, MHO984.

 Owon ADS800A

NovaOS boots on our ADS802A, on kernel.org Linux 7.2.10 with the scope UI on its own screen and the FPGA loaded. Acquisition is next. ADS802A to ADS924A, and the Voltcraft DOV702/DOV704 and CEI914/CEI924 rebrands.
Siglent SDS800X HD

On the bench: two SDS814X HD, on Siglent's own firmware for now. Its firmware is mapped (Linux 5.10 on a Zynq UltraScale+, the FPGA loaded from a file at every boot); NovaOS does not run on one yet.

By model: DHO802 · DHO804 · DHO812 · DHO814 · DHO914 / DHO914S · DHO924 / DHO924S · MHO934 · MHO954 · MHO984

CH2Other test equipment

Rigol DL3031 electronic load

Our own AI firmware runs bare metal on the load: CC, CV, CR and CP, transients, lists, battery tests and remote control. It is firmware of its own, not NovaOS. Download opens after a legal review.

 Siglent SSA3000X Plus spectrum analyzer

In bring-up: its boot chain and FPGA are mapped from our SSA3021X Plus. NovaOS will boot from a USB stick into RAM, never writing the analyzer's flash, so a power cycle without the stick is stock again.

CH3How an instrument gets NovaOS

  1. Read it: the stock firmware, its remote interfaces and its update road, from a unit we own.
  2. Open it: every chip, how the FPGA is loaded and how samples reach the processor, each claim checked on the unit (the hardware pages).
  3. Boot our kernel: a current Linux with board support we write, and a way back to stock that is tried before anything is written.
  4. Drive the FPGA: our own acquisition engine, through the FPGA's open-source link driver, then the shared NovaOS scope stack on top.
  5. Measure it: against stock on the same unit, the same way, before a feature is called done.

We call a model supported only once NovaOS runs on a real unit of it. Which instrument should be next? Tell us on NovaOS's EEVblog thread.