Products > Test Equipment

Choosing equipment for automated PSU testing in LabVIEW

(1/2) > >>

Betonmischer:
I'm looking to build a small lab for testing computer ATX power supplies, which includes voltage regulation, ripple, efficiency and power factor. For that I need a power analyzer, a four-channel scope and a rack of electronic loads. All controlled with NI LabVIEW to set up an automated test sequence that would measure everything with multiple load combinations on different PSU rails.

I think about buying PEL-2000A/B loads from GW Instek for their fast slew rate, option to drive loads synchronously in dynamic mode and reasonable pricing, GDS‐1054B scope and GPM-8213 power meter of the same brand. Would you recommend those or something else for a similar price? Programmability is the main concern for me, as I'm afraid of potential issues when trying to tie it all together in LabVIEW.

Also, I've been recommended to choose equipment with GPIB over USB, and that raises a lot of questions for me. Is there any advantage to use GPIB ? Would mixing GPIB and USB devices work (the scope is USB-only)? If GPIB is indeed the way to go, would a cheaper clone GPIB to USB adapter work in LabVIEW instead of the original one from NI?

Any piece of advice is welcome.

nctnico:
I'd go for LAN (ethernet) instead of GPIB nowadays. With LAN you can connect equipment to a network more easely and use off-the-shelve cables and equipment (like ethernet switches). USB can be finicky to keep going reliably as the USB bus can be upset quickly / easely in a lab environment. USB just isn't as robust as GPIB or LAN.

Not sure whether using LabVIEW is the best choice. If your requirements are not that high, then using the Python programming language + Pyvisa (together with the VISA layer written in Python) is likely easier to get going compared to getting all the NI layers to play nice. With ethernet connected equipment, there is no benefit from using NI's obfustigated Visa layer as you know the IP addresses. In my own lab I have all my equipment on fixed IP addresses and can access these directly over the network. Python has all the libraries needed to do analysis and visualisation.

Betonmischer:
Thanks, Ethernet it is then. Speaking of Pyvisa, that seems promising, but I couldn't find any VISA libraries on GW Instek's website, only LabVIEW drivers. Although, I'm not familiar with either of those, so I could be missing something.

nctnico:
I'm always using SCPI commands as described in the remote programming manuals to control instruments. A Labview driver probably hides that from the user for easier integration in a visual environment like Labview. I have used Labview over 30 years ago but I recall it had a learning curve. If you have some programming experience, the Python way may be easier. If you are more geared towards using a visual 'click it together' environment, then Labview may be more suitable.

Betonmischer:
I'll try it both ways then when I get the hardware. SCPI commands don't look very complicated. Thanks for the advice.

Navigation

[0] Message Index

[#] Next page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod