Devices / test-instrument

Rigol VS5202

ControllableInstall: mediumImported

Fully drivable by open code over the stock firmware.

Measurement acquisition via libsigrok's rigol-ds driver (oscilloscope). Features depend on the model, firmware and libsigrok version; this is not an OpenDeviceDB hardware test.

Get started

One known way to put open firmware or software on this device, easiest first. Each one links to the project's own instructions.

Before you start
  • Back up your data and settings (and the stock firmware, when the guide says how).
  • Check the exact model, hardware revision and firmware version against the guide: a close model may not work.
  • Charge the battery or use a stable power supply; do not unplug during the install.

Use sigrok (nothing is flashed)

Install: medium

Needs a cable or the command line · sigrok

Device opened
No
Firmware
Upstream profile: 2 analog channels; digital acquisition not enabled in this driver. Check the model's supported acquisition modes and connection in the upstream documentation.

Install a libsigrok version containing this model and its required dependencies. Use sigrok-cli or a frontend appropriate to the instrument (PulseView is for logic/oscilloscope acquisition). Consult README.devices and the driver source for model-specific setup.

No install report yet. · Report how it went

OpenDeviceDB links to each project's own instructions and tools; nothing is flashed from this site. Flashing is at your own risk and may void the warranty.

ID
rigol/vs5202
Category
test-instrument
Vendor support
Unknown
Updated
2026-11-01
Curate this record on GitHubJSONClaim this device

Being worked on

No live claim. If you start working on this device, claim it so nobody duplicates your work.

Interfaces

No interface documented yet.

Projects

ProjectKindOriginLicenseFreedom
sigrok (rigol-ds)drivercommunityGPL-3.0-or-laterStill non-free: not statedThe open driver reads measurements from the device's existing firmware. This model table does not establish the firmware's license or remaining proprietary components.
What "still non-free" and "cloud" mean

What stays proprietary or depends on the vendor's cloud once the project is in use, from the project's own documentation.

vendor blobs
proprietary files extracted from the stock firmware
stock firmware
the stock firmware stays on the device; the project only talks to it
modem
cellular modem firmware
GPU
graphics driver or firmware
Wi-Fi
Wi-Fi driver or firmware
Bluetooth
Bluetooth firmware
camera
camera driver or image processing
sensors
sensor hub or sensor drivers
bootloader
boot firmware
other
another proprietary part
Cloud: none
works fully locally
Cloud: only at setup
a vendor account is needed once, e.g. to obtain a local key
Cloud: optional
cloud features exist but are not needed
Cloud: required
does not work without the vendor's cloud
Cloud: unknown
not known

Verification

Not verified. A "verified on hardware" badge requires a replayable test (hardware-replay) run on a real device with a stated firmware version.

Provenance

AI assistance not stated.

Status and claims as of the build date (2026-11-01). Data licensed CC BY-SA 4.0; imported data keeps its upstream license.