07-31-2012 04:01 AM
i want to know advantages of VISA over GPIB in labview when we connect our pc with a device which has GPIB interface
what could be reason behind using VISA programming
i want atleast 5 advantages of visa over GPIB .
Solved! Go to Solution.
07-31-2012 04:20 AM
Hi,
1.VISA Write is equivalent to a GPIB write except the VISA Write returns a VISA Reference Out that is much easier to use. You pass that to the next VISA function instead of wiring a GPIB address to all.This will make your blockdiagram cleaner.
2.portability:-VISA supports GPIB, Serial, Ethernet, USB, PXI, VXI, and PCI. So, with a single piece of code, you can support all of the interfaces and even GPIB controllers from different vendors.
3.VISA supports aliases. You can assign logical names to the resources. Instead of trying to remember the GPIB address in a rack full of instruments, you can reference 'DMM', 'Scope', etc.
4. If you are programming multiple devices that communicate over more than one bus type, it might be easier to use VISA for your entire system.
5. In VISA, you must always call viEnableEvent() prior to being allowed to receive events, this is required in VISA to avoid the race condition of trying to wait on events for which the hardware may not be enabled.
6.The VISA Resource Control allows you to pick from a list of available resources.
Enough
07-31-2012
04:48 AM
- last edited on
10-16-2024
01:36 PM
by
Content Cleaner
VISA is capable of controlling VXI, GPIB, or Serial instruments and makes the
appropriate driver calls depending on the type of instrument being used
GPIB ,Serial communications comes under VISA
07-31-2012
07:24 AM
- last edited on
10-16-2024
01:36 PM
by
Content Cleaner
@garg1989 wrote:
i want to know advantages of VISA over GPIB in labview when we connect our pc with a device which has GPIB interface
what could be reason behind using VISA programming
i want atleast 5 advantages of visa over GPIB .
This sounds like you're trying to sell something to upper management, as opposed to asking a programming question. Perhaps you should start here: https://www.ni.com/en/support/documentation/supplemental/06/ni-virtual-instrument-software-architect...