Skip to content
This repository was archived by the owner on Feb 2, 2026. It is now read-only.

20160421 add rigol ds1000z#47

Open
ianrrees wants to merge 10 commits intopython-ivi:masterfrom
ianrrees:20160421-add-rigol-ds1000z
Open

20160421 add rigol ds1000z#47
ianrrees wants to merge 10 commits intopython-ivi:masterfrom
ianrrees:20160421-add-rigol-ds1000z

Conversation

@ianrrees
Copy link
Copy Markdown

@ianrrees ianrrees commented May 9, 2016

Hi Alex,

Thanks for putting python-ivi together! I've added basic functionality for the Rigol DS1000Z series of scopes here - is this up to scratch? Can chip away at the remaining bits as required, but would like to know whether I'm on the right track before sinking more time into it. -Ian-

@ianrrees ianrrees force-pushed the 20160421-add-rigol-ds1000z branch from e2d07fc to 8608b4e Compare May 9, 2016 09:47
@ianrrees ianrrees force-pushed the 20160421-add-rigol-ds1000z branch from 0ecc24e to 28ab939 Compare May 21, 2016 03:57
@evilmav
Copy link
Copy Markdown

evilmav commented Jul 29, 2016

I'd second the request: DS1000Z is very popular with hackers and hobbyists these days, having it supported in an official release would be very appreciated. I hope python-ivi organisation isn't abandoned.

@ianrrees
Copy link
Copy Markdown
Author

Thanks @evilmav! I'm assuming you have a one of these scopes - would you mind trying my branch and reporting back how it goes for you?

@evilmav
Copy link
Copy Markdown

evilmav commented Jul 30, 2016

@ianrrees I have a small project for the next couple of weeks which involves capturing data from the DS1000Z, I'll report if I run into any issues (or successes =) )

@evilmav
Copy link
Copy Markdown

evilmav commented Jul 30, 2016

@ianrrees I've been also looking forward to attempt to add one or two additional instruments myself (a signal generator from siglent for now), but I'm confused where to fork from if python-ivi/python-ivi is not properly maintained any more =(

@ianrrees
Copy link
Copy Markdown
Author

Sounds good! Funny coincidence - I have one of those same signal generators coming in the mail ;).

Would suggest you go ahead with adding your driver to python-ivi; I haven't looked around a whole lot, but it seems like this project is the best Python test & measurement framework to build on. @alexforencich is probably just busy with other things - if that's the case then I imagine good changes will get merged in eventually, or perhaps someone else could be brought in as a collaborator.

@alexforencich
Copy link
Copy Markdown
Contributor

Yeah, you hit the nail on the head with that one...I have been extremely busy with a number of other projects recently. Just look at my commit history; lots and lots of FPGA stuff. Anyway, I'm going to take a look at this in detail as soon as I get a chance, hopefully soon. I don't have access to any Rigol hardware though, so I can't do any rigol driver development work myself unless there is some donation of money or equipment. It might be nice to have collaborators as well, but so far nobody has expressed any interest. And I also have no idea how many people are using python-ivi, what they are using it with, or what they are using it for...I don't hear squat unless something is broken.

@ianrrees
Copy link
Copy Markdown
Author

Hi Alex, thanks for the response!

Just to be clear - I wasn't intending this to be the final PR for DS1000Z support; there's still a bit left to implement, some gaps in documentation, etc. More interested to find out if the parts that are there are in line with what you want for Python-IVI.

Seems like we'll always have issues with developers not having access to all gear, which I suppose means there will be somewhat variable quality/interface/etc for different instruments.

I'm up for being a collaborator if you want, perhaps could restrict my changes to adding drivers in the short term, or something along those lines.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants