Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

VXI to PXI software compatibility

We have a test system running CVI 5.5 that uses all VXI stuff and we want to make a new one just like it. Is there any foreseeable software conflicts in going from VXI to PXI if we use all VISA commands? I want to say No but maybe I'm overlooking the obvious or just don't know something entirely. Please let me know your thoughts about moving from VXI to PXI from a software standpoint. Thanks,

Grant
Grant M. Johnson
Project Engineer
LECO Corporation
0 Kudos
Message 1 of 2
(3,117 Views)
Grant:

The answer is that while VISA provides exactly this kind of multi-interface interoperability, it really depends on the modules you are using.

If you are using NI modules such as a VXI-DIO and a PXI-DIO, and you are using the NI-DAQ API, then yes we make that transition transparent.

If you are using third party modules, it depends on how they present their functionality. We recommend that vendors write instrument drivers and use VISA to do the I/O for both VXI and PXI. An example of a company that has done this is Ascor - you can use their switch modules with their instrument drivers and VISA makes that work seamlessly.

I cannot speak for all vendors, although I do know that many of those who provide modules in PXI format do use VISA for their inst
rument drivers. If you are programming directly to VISA and not using instrument drivers, you will need to take into consideration the interface differences. For example, VXI has A16/24/32 spaces, whereas PXI has BAR0/1/2/3/4/5. But as long as the registers within a given address space behave similarly, then all the other operations like viMapAddress and viIn16 and viOut32 work identically.

I hope that helps you.

Dan Mondrik
Senior Software Engineer, VISA
National Instruments
Message 2 of 2
(3,117 Views)