Automated testing
After changing the settings on your function generator and switching the next button for the 100th time you start to become a big fan of automated testing. The ability to test a given process/project in either hardware or software without significant user action is a time saver, and an incredible tool. The ability to get results out of your tests in minutes rather than hours gives you more time to get the design right.
My team has been using the Rigol DG1022 and DS1000 series scopes for testing hardware and software. The issue is that they’re wasting too much time getting settings right, or reading values when they could be spending their time doing development. To help the be more productive, I’ve been working on some Rigol usbtmc drivers. As it stands right now, it works well with Linux. I’m in the middle of resolving some issues with Windows and Mac (still need to test the result on OS X).
Why another attempt to do this? I’ve had the code sitting around from previous projects and it’s not that complicated. Ideally, I would like to create a NIVisa free interface for all systems. It’s a fantastic bit of kit, but it’s a pain in the neck to get a reliable response on our Windows machines, and I’m really not impressed.
### New Toys On The Way ### Another reason I want the ability to add scripting interfaces to these tools; the fantastically priced DS1054z! I’ve ordered mine and promise to put some pretty pictures up once it’s delivered.
Hence the Github Project…
I’ve created a python 2.7 project (using PyQt 4.8) to allow the scripting of the DG1022 function generator. I’ve also developed a basic GUI using PyQt. Feel free to have a look and give me some constructive feedback.
https://github.com/tsunderland/RigolUSBTMC_Python
I’m currently testing with the NI-Visa libraries as my team needs to use the tool on Windows. When I get the chance to replace the visa libraries I’ll be sure to include the update.
Issues I’ve noticed
Channel 2 on the Rigol Function generator requires a function update after sending on update voltage command. I’ve no idea why this is, but unfortunately that’s the way it works for now.
On Windows, some people are unable to control the output on either channel using the Visa libraries.