Repository navigation
FAQ
Short answers, each with the page that has the details.
Installing with a second card means opening the scope, and that voids the warranty. The USB install does not open the scope, but it changes the card, and nothing here promises that your warranty survives that. See the Disclaimer.
A DHO924S (the developer's unit) and, by a user report, a DHO804. Models of the same hardware variant differ only in their licensed bandwidth and count as verified. The other DHO800/DHO900 models are prepared but have never run OOS. See Supported models and features.
Yes. OOS runs next to the stock system on the same card. In one-shot mode, the next power-on starts stock. See Going back to stock.
OOS never writes the FPGA flash, /rigol/data, or the uboot, trust and parameter partitions. Self-calibration
writes its results to /oos/cal; the factory files are never changed. A mistake while writing the card can still
destroy the calibration stored on it, so back up the whole card first
(backup).
Option licences of the stock system have been seen to stop working after running OOS, and had to be entered again. Keep your licence keys at hand.
OOS is not a calibrated or certified measuring instrument. Readings can be wrong without any visible sign. Do not use it for safety-relevant, medical, legal, commercial or compliance measurements.
Only on a trusted bench network, never directly on the internet. SSH is the only remote shell. Apart from SSH, OOS has no authentication: SCPI, VXI-11, the web remote and MCP are open to everyone who can reach the scope. Updates require a signature from this project's release key.
By default OOS is one-shot: every start of OOS restores the stock boot. Set System > Boot mode to Persist to keep OOS. See First start and choosing how OOS starts and Troubleshooting.
Open http://<scope>:8080/update and choose the .oosupd file of a release. See
Updates.
Yes, with simulated signals. See Try it without a scope.
SUPPORT.md says where: the repository's discussions for questions and issues for bugs. Security problems go through private vulnerability reporting (SECURITY.md).
This wiki is generated from wiki/ in the repository; propose changes with a pull request.