Choose the guide
Connect the scope and open Hardware → Configure from programming guide…. Select the programming guide for your model, including its SCPI command reference.
Instrument and design compatibility
Bring the scope already on your bench
Use a built-in profile, upload your SCPI oscilloscope's programming-guide PDF, or import a waveform file. YProbe shows which configurations have been checked on real hardware so you can choose the right path for your instrument.
Support depends on the model and its command set. Each connection shows its validation status. For an unrecognised scope, use the programming-guide setup below, select a known compatible profile deliberately, or verify the pairing with the bench self-test.
Upload your oscilloscope's SCPI programming guide
If your model is missing from the built-in list, you can upload the manufacturer's programming-guide PDF in the desktop app. YProbe uses its documented commands and waveform format to prepare a configuration for the connected instrument.
Enable the setup
Enable the AI setup routes and, for hosted processing, approve the separate guide-upload permission. The selected guide is processed only with your consent.
Check the instrument
YProbe reviews the configuration, checks instrument controls and reads a waveform. If a required check fails, the draft is not activated.
Use the checked configuration
A successful setup is saved for that instrument and labelled AI-configured. Run the probe-compensation self-test to verify amplitude and frequency against a known signal.
The guide must describe a command set and waveform format YProbe can support. AI-configured profiles remain distinct from bench-validated profiles; uploading a guide alone does not establish measurement accuracy.
Request early beta access →Built-in oscilloscope profiles
| Profile | Example generations | Current grade | What that means |
|---|---|---|---|
| Rigol | DS1000Z-era and compatible Rigol SCPI | Bench validated | Control, scale read-back and chunked waveform readout have been exercised on real hardware. |
| Siglent legacy | SDS1000CFL/A/CML+, SDS1000X/X+/X-E/X-C and SDS2000-era word dialect | Bench validated | Validated on an SDS1202X-E for connection, scales, trigger, acquisition and waveform readout. |
| Siglent current | SDS800X HD, SDS2000X+, SDS5000X, SDS6000A and related :CHANnel dialect | Guide-derived | Implemented from the vendor programming guide and labelled unvalidated until a real instrument passes the workflow. |
| Keysight | InfiniiVision-style SCPI and binary waveform readout | Guide-derived | Available for deliberate use; not presented as bench-validated. |
| Tektronix | TBS/MSO/DPO and legacy TDS/TBS/TPS command families | Guide-derived | Current and legacy profiles are separated by model family and remain visibly unvalidated. |
| User JSON profile | Rebadges, OEM twins and models newer than the build | Manual or self-tested | Imported through the safe profile loader; destructive commands and unrecognised waveform readers are refused. |
How YProbe handles an unknown instrument
Read the identity
YProbe queries the instrument ID and matches vendor and model to a known profile where possible.
Show the confidence
The connection chip states whether detection is simulated, validated, unvalidated, forced, self-tested or guessed.
Block unsafe automation
A guessed dialect disables automated capture because the wrong readout formula can return plausible but incorrect volts.
Choose your setup
Upload the programming-guide PDF, select a compatible profile deliberately, run the probe-compensation self-test, import a waveform file or use the simulator.
No compatible live-control profile?
Import CSV or TXT
Export a waveform from Hantek, OWON, PicoScope or another instrument application. YProbe runs it through the same extraction, expected-signal comparison and diagnostic workflow; automatic scope setup is the missing piece.
Use the simulator
Exercise guided probing, startup captures, protocol decode, intermittent faults and rework-aware diagnosis without any instrument. The simulator is a complete evaluation path, not a screenshot mode.
Supported design inputs
| Input | Supported forms | Role in YProbe |
|---|---|---|
| Netlist | KiCad; Altium/Protel; Altium Wire List; Cadence Telesis for Allegro/OrCAD; Mentor/Siemens PADS-PCB; EDIF 2 0 0 | Builds the board graph and validates every AI-returned net and component name. |
| BOM | CSV; Excel XLSX; legacy XLS (save as XLSX or CSV before import) | Adds reference designators, values, footprints and manufacturer part numbers. Common column headings are matched automatically. |
| Board layout | Optional IPC-2581 | Adds physical probe-point locations when available. |
| Waveform file | CSV or TXT exports | Feeds the same comparison and diagnosis pipeline without live scope control. |
If a USB scope does not appear
A USBTMC scope needs a driver bound to that device. On Windows, NI-VISA provides one route; WinUSB can also be bound with Zadig. Until a driver is present, a scan may look exactly like an unplugged instrument: an empty list with no useful error. LAN instruments can be entered directly using their VISA resource string when network discovery is unavailable.
Instrument support and transport are separate questions: detecting the device proves the connection, while a validated or self-tested profile proves that control and volts are trustworthy enough for automated evidence.