Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Changes after VISA 3.2 for ethernet

I have developed some software to communicate to some custom hardware using VISA 3.2  ethernet sockets.  The software works great when using VISA 3.2.  When I try to upgrade to something greater than VISA 3.2,  the software stops communicating through normal running of the software.  Using a VISA that is greater than 3.2, I can get it to work by stepping through my software in Labwindows/CVI 7.1.
 
Does anyone know what has changed that could cause this problem and any recommendations to fix it? 
 
0 Kudos
Message 1 of 2
(3,092 Views)
hi gsflat,

The problem you're seeing may be no problem at all. There were many optimizations in each release of VISA. This means some of the functions that used to take a while are now going faster... sometimes too fast. In your application there are probably some areas that depended on those functions taking a while to run. If it works using the new NI-VISA when you step through the application, that means that it should also work if you just add a small delay where ever you're having this problem. Find out what function is failing. You'll probably just need to add a small delay before that function.

Regards,
Matt S.

LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.
0 Kudos
Message 2 of 2
(3,079 Views)