Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Rigol scope driver(s) #12

Closed
azonenberg opened this issue Apr 16, 2019 · 3 comments · Fixed by #123
Closed

Add Rigol scope driver(s) #12

azonenberg opened this issue Apr 16, 2019 · 3 comments · Fixed by #123
Labels
driver Hardware drivers

Comments

@azonenberg
Copy link
Collaborator

No description provided.

@azonenberg azonenberg added the driver Hardware drivers label Apr 16, 2019
@raplin
Copy link

raplin commented Apr 28, 2019

Rigol scopes are lamentably slow for waveform downloads; extensive discussion here.
https://www.eevblog.com/forum/testgear/ethernet-transfer-speed-for-rigol-ds2072a-and-ds4014/
TL;DR; about 1.7MBytes/sec or less over ethernet or USB.
Somewhat restrictive; if scope is running you can only d/l the displayed waveform (e.g. 600pts); if stopped you can fetch the capture memory (24M samples (e.g. DS1054z full ram) takes 15+seconds.

@azonenberg
Copy link
Collaborator Author

Most scopes are pretty slow over Ethernet/USB because they're not designed for fast downloads. Sadly, fixing this is likely to require custom hardware or a major change of priority at the scope vendors.

Typically glscopeclient will do a one-shot trigger, download the waveform, and repeat as needed.

azonenberg added a commit that referenced this issue May 2, 2019
@azonenberg
Copy link
Collaborator Author

We can now download waveforms and do very basic read-only connections to a DS1104Z. No USB/RS232 connection support and all Set*() functions are still unimplemented.

Sorry, something went wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
driver Hardware drivers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants