I am missing the IVI and NI Visa .NET DLLs. This is both on a new system and a system that was updated 1/2/2017 using the latest patch (16.0.1)
Thanks
David
Hi,
I'm having the same problem a user srms. I have installed all the Keysight IO library Suite, and I have enabled the tulip in MAX. I can communicate with the instrument using the Keysight softwares, and I can see the instrument in the NI MAX, but I can't see the instrument in the dropdown list of the VISA resource name in labview. Is the any additional step to see my instrument in the VISA resource name dropdown list?
Has anyone figured out a way to use the Ocean Optics 2000 4000 labview drivers with a Flame-NIR spectrometer? I've used these drivers with the USB 4000 spectrometer and am hoping to use them for my new Flame-NIR spectrometer, but so far it doesn't even detect the Flame-NIR. I see driver's list of supported devices that the "Flame" is listed, but "Flame-NIR" is not.
Maybe there will be an update from NI on this driver soon?
After successfully installing Labview 2016 and NI-VISA on a new SL machine, I attempt to run Visa Configuration and get the following:
$ visaconf Can't load library /usr/local/lib/liblvrt.so.15.0 libXinerama.so.1: cannot open shared object file: No such file or directory To download the LabVIEW Runtime engine, go to http://www.ni.com/rteFinder?dest=lvrte&version=15.0&platform=Linux&lang=en
But when I attempt to install the 2015 RTE I get pushback from the 2016 RTE:
./INSTALL Preparing... ########################################### [100%] package nissli-16.0.0-f0.i386 (which is newer than nissli-15.0.0-f1.i386) is already installed package nissli-16.0.0-f0.x86_64 (which is newer than nissli-15.0.0-f1.i386) is already installed package nisslcerts-16.0.0-3.0.noarch (which is newer than nisslcerts-15.0.0-3.1.noarch) is already installed package nicurli-16.0.0-f0.i386 (which is newer than nicurli-15.0.0-f1.i386) is already installed package nicurli-16.0.0-f0.x86_64 (which is newer than nicurli-15.0.0-f1.i386) is already installed package nicurli-16.0.0-f0.i386 (which is newer than nicurli-15.0.0-f1.x86_64) is already installed package nicurli-16.0.0-f0.x86_64 (which is newer than nicurli-15.0.0-f1.x86_64) is already installed package nitdmsi-16.0.0-f0.i386 (which is newer than nitdmsi-15.1.0-f0.x86_64) is already installed package nitdmsi-16.0.0-f0.x86_64 (which is newer than nitdmsi-15.1.0-f0.x86_64) is already installed package nitdmsi-16.0.0-f0.i386 (which is newer than nitdmsi-15.1.0-f0.i386) is already installed package nitdmsi-16.0.0-f0.x86_64 (which is newer than nitdmsi-15.1.0-f0.i386) is already installed package nisvcloc-16.0.0-1.noarch (which is newer than nisvcloc-15.0.0-1.noarch) is already installed package nissli-16.0.0-f0.i386 (which is newer than nissli-15.0.0-f1.x86_64) is already installed package nissli-16.0.0-f0.x86_64 (which is newer than nissli-15.0.0-f1.x86_64) is already installed package labview-2015-rte-15.0.1-4.x86_64 (which is newer than labview-2015-rte-15.0.0-4.x86_64) is already installed package labview-2015-rte-15.0.1-4.x86_64 (which is newer than labview-2015-rte-15.0.0-4.i386) is already installed Installation completed.
Do I need to downgrade to LV2015?
Hello,
Problem:
I have a third party software communicating with two COM ports, when i run my VI this interferes with labview VISA and throws out an error. I'd like to find a way of running both programs at the same time.
Details:
The relevant part of my VI is very similar to the example "http://www.ni.com/example/27757/en/". A find resource function creates an array of all resources using the command "ASRL?*::INSTR". This array is fed into a For Loop and read by an Open VISA function. However because the third party app is running in the back ground, when Open VISA tries to open the COM port, it throws out an error.
Due to the nature of the devices involved everytime the devices get plugged into the computer they may be assigned different COM port entries, hence I believe I have to you the above method.
I am trying to find a solution that will either;
a) allow Open VISA to communicate with the device at the same time as the 3rd party app or
b) filter the results of the VISA Find Resource Function before they are fed into the Open VISA function. The only difference in the devices are the "VI_ATTR_INTF_INST_NAME" attribute and come in the form "ASRLXX (COMXX - USB Serial Port), ASRLXX (COMXX - USB COM Port) and ASRLXX (COMXX - Prolific USB-to-Serial Comm Port)", where XX is the COM Port Number. It is the "ASRLXX (COMXX - USB Serial Port)" ports that i am trying not to feed into the Open VISA function.
Any help would be appreciatted
Cheers
Pete
Hello all,
I have been trying for some time to troubleshoot an issue where VISA just cannot see my Lakeshore 218 Temperature Controller. This instrument is connected via RS232 directly into the back of the PC. Windows Device Manager sees that port fine. I can successfully communicate with the it through RealTerm and also through pyserial. Lakeshore makes a proprietary Communication Utility and Chart Reader and both of those can communicate with the instrument fine. Neither NI-VISA Interactive Control nor pyvisa can see this device, but they are able to see other devices that I have connected. It may also be relevant that NIMAX cannot see any of the devices, but if I manually add the RS232 device it can see it and communicate with it until I restart the software. Then, it cannot communicate again.
Right now I am just using pyserial, but that is not an ideal situation. I would really like to be able to use VISA.
Here are the things I have tried:
-reinstalling NI-VISA
-using different VISA instances (from Agilent for example)
-using a RS232 to USB converter and a USB port
Thanks in advance for any help
HI,
I'm trying to connect to an ATS-810 over GPIB-USB-HS (PC -> USB -> GPIB-USB-HS -> GPIB Cable -> ATS-810). I can see the device clearly with the address "GPIB0::7::INSTR" in NI-MAX under "Devices and Interfaces." I can even open the "Communicate with Instrument" panel and query with *IDN. However, when i click "Open VISA Test panel" i am unable to open the resource.
I am currently trying to set up some automation in Visual Studio and call the .Open command which fails in the same way.
It's curious that the device shows up in NI-MAX but not the VISA Interactive Control. In NI-MAX, the version shows up as 16.0.0f0. I'm not a professional with this software so if you need other information to diagnose, please let me know and I will provide.
The error text:
Error opening resource:
GPIB0::7::INSTR
VISA: (Hex 0xBFFF00A5) The interface type is valid, but the specified interface number is not configured.
I would like to test a bunch of sensors. Each sensor has a DB15 connector with mixed digital and analog signals (bw ~5MHz, Z ~120R).
I am looking for an instrument where I can control which couple of sensors I would like to interconnect to the measurement PC. I've seen commutation switch such as the Keithley 3706A, but these guys does not accept custom commutation board when I can populate my own connectors and my own relays.
So I am thinking to make my own commutation system with a MCU, a FTDI and a bunch of analog switch and relays.
I feel this is a very common need in the testing area and I would like to know what commercial solution can be used in my case.
Hi All,
I am using NATIONAL INSTRUMENTS NI PCI-GPIB WITH NI-488.2 778032-01 (system controller) to communicate with two tester.
Here is the problem, the bytes i write sometimes is not match with the ibcntl and cause EABO(6). Please see the attached picture from NI trace.
ibwrt(UD1, "S
:C?" ,6) but the ibcntl is only 0x0001, where ibcntl indicates the number of bytes that were successfully transferred during the last I/O operation.
Is this hardware problem or my software problem? Please help.
Lately I am using this plug and play driver to control a oscilloscope but I am not sure I understand how this Read Multiple Waveforms VI works. In my programe I firstly let user configure all channels using Configure Channel VI and then try to read the waveforms from enabled channels using Read Multiple Waveforms. The description for Read Multiple Waveforms says "Initiates an acquisition on all channels that you enabled with the Configure Channel VI." However it doesn't work that way. It seems it only accepts specified channels from the channel input and if you don't input anything the default value is channel 1 and 2. It doesn't matter what you do with Configure Channel VI. Even you specify that the channel is not enabled, as long as that channel is input into the Read Multiple Waveforms, that channel would be automatically enabled. Am I misunderstanding something or I didn't use it correctly.
I try to control a Keithley 2306 by using VISA (the goal is using it
from python).
After installing NIVISA541full.exe, syscfg1601full.exe and
NI4882_1500f0.exe I started NI MAX but I get following error:
Error opening resource:
USB0::0x3923::0x702A::010A65AB::RAW
VISA: (Hex 0xBFFF0072) The resource is valid, but VISA cannot
currently access it.
Sending IDN? from VISA Test Panel gives only:
Write Operation (*IDN?\n)
No Error
The Windows device manager shows an NI-VISA USB Device: "Device Model
Name", status: working correctly.
Maybe interesting also:
C:\Windows\system32>py -m visa info
Machine Details:
Platform ID: Windows-7-6.1.7601-SP1
Processor: x86 Family 6 Model 42 Stepping 7, GenuineIntel
Python:
Implementation: CPython
Executable: C:\Users\vos\AppData\Local\Programs\Python\Python36-32\python
.exe
Version: 3.6.0
Compiler: MSC v.1900 32 bit (Intel)
Bits: 32bit
Build: Dec 23 2016 07:18:10 (#v3.6.0:41df79263a11)
Unicode: UCS4
PyVISA Version: 1.8
Backends:
ni:
Version: 1.8 (bundled with PyVISA)
#1: C:\Windows\system32\visa32.dll:
found by: auto
bitness: 32
Vendor: National Instruments
Impl. Version: 15728640
Spec. Version: 5243904
#2: C:\Windows\system32\visa32.dll:
found by: auto
bitness: 32
Vendor: National Instruments
Impl. Version: 15728640
Spec. Version: 5243904
Any help would be appreciated!
Regards
Volker
We are receiving this error from one of our systems where we are using a USB scanner (for scanning bar codes) and this error doesn't let application go ahead as it is designed. User has to kill the application from task manager and restart. Please refer attached image.
Regards,
Gorakh
Hi,
i tried to find a solution for my problem in the forum, but i could not find any solution. I try to control the device via USB.
I can set and read the CR-options, but any other specific READ-command will fail with a timeout
VOLT:L1?
Read Operation
Error
VISA: (Hex 0xBFFF0015) Zeitüberschreitung, bevor der Vorgang abgeschlossen werden konnte.
Any SET-Command does nothing - no change in the display.
VOLT:L1\s120
I already tried to change the VI_ATTR_TMO_VALUE, but still no success.
Thank you for your help in advance.
best regards
hschenk
Hello Community,
I'm working on reading a Watlow F4 temp controller
Background details:
The watlow's RS-232 port is connected to a serial to ethernet device that connects to the main network PC that has a running labview program to constantly monitor the watlow
This main PC sends commands to the watlow and reads all key information such as temp, profile name, status, set points, alarms, etc etc.
This part is fully functional and works no problem.
Next step:
I need to add a local PC (it can't be connected to the network due to multiple constraints on how our network is setup) next to the chamber that the watlow is controlling, that I can create my own program to do different tasks according the the information thats being retreived on the watlow.
My plan:
I recently purchased an rs232 cable splitter. The rs232 signal coming out from the watlow will be split, one end going to the main server controlled by the main network PC, and the other end going to my local PC.
The problem is if I run my program on the local PC, it works, but it leaves an error on the main network PC (i'm assuming because we can't transmit commands to the watlow from 2 different devices).
Now if I shut off my program on the local PC, the main network PC's program will resume normal function, error free.
What I need help on:
Is it possible for me to just read the output buffer ONLY on my local PC's labview program? that way I can still retrieve key information from the watlow, but not transmit any commands?
It's MODBUS RTU that the main network PC uses to send commands to the watlow controller.
Am I correct in my assumption that I can perform read on the "recieve" line from the rs232, on multiple PCs, but only one PC can utilize the "transmit" line?
Hi All,
We used ibrd() and ibwrt() when GPIB communication to save time for our customer. It is no problem in VS2005.
But for VS2010, it always pop up this dialog box when executing ibwrt() as the attach.
Could you help try to find why the dialog box was found and how to fix it, thanks!
Below is the sample code
>
> int Device = 0; /* Device unit descriptor */
> int BoardIndex = 0; /* Interface Index (GPIB0=0,GPIB1=1,etc.) */
>
>
> int PrimaryAddress = 2; /* Primary address of the device */
> int SecondaryAddress = 0; /* Secondary address of the device */
>
>
> Device = ibdev( /* Create a unit descriptor handle */
> BoardIndex, /* Board Index (GPIB0 = 0, GPIB1 = 1, ...) */
> PrimaryAddress, /* Device primary address */
> SecondaryAddress, /* Device secondary address */
> 13, /* Timeout setting (T10s = 10 seconds) */
> 1, /* Assert EOI line at end of write */
> 0); /* EOS termination mode */
>
> ibclr(Device);
>
>
> ibwrt(Device, "*RST", 4);//the dialog box pops up here.
Hy you all,
I know there ar lots of topics arroud concerning this problem. And yes I have tried a lott. The closet thread I have found might be this one, but that also seems to hang:
https://forums.ni.com/t5/forums/v3_1/forumtopicpage/board-id/170/thread-id/985238/page/1
So to come to my problem:
I have an ADLINK USB-3488A USB to GPIB converter. With this there is an Agilent Power-Supply 6655A conected.
I worked with this setup quite well with a Win7-32bit LV2014-32bit system (except that it is an old slow PC). So I wanted to shift to a new system with Win7-64bit and LV2014-64bit were I cannot see the device in my LV-VIs.
All relevant system settings could hopefully be seen in the attached imaged (one for the 32bit and one for the 64bit system).
- I do not see the GPIB device in MAX in the "Geräte und Schnittstellen" (nether in the 32bit or the 64bit system)
- I can do the *IDN?\n in the VISA Interactive Control in both systems
- I see the alias in the 32bit
- do not see the alias and I nether can directly (with a string constant) talk to the VISA in the 64bit
Any sugestions are warmly welcome. I'm at a point were I'm stuck.
Hi all,
I have a scenario, I was able to work with the NI USB RS485 communication cable yesterday and today when I started my PXIe system it's not detected.
I physically need to unplug and plug it back so MAX detects. Is there any work around for this because I don't want to unplug and plg action to be performed here.
Has anyone already controlled this DMM with LabVIEW ?
I'm using the "Agilent M918x.lvlib" driver which ships with the DMM but it doesn't allow to communicate simultaneously with several instruments.
Many thanks in advance for any advice.
Hi,
I have some trouble with my fresh built application.
The little program uses serial/visa communication to gather data from a device via serial port.
Everything is working well on my development machine: The device is found and the COM port is assigned.
But when building an application and run it on the destination machine the serial device is not found.
So I built an application from the vi which is finding the communication port (e.g. COM4) to my device and it works properly on the desination machine.
Can you help me please.
development computer:
- W7 32bit
- LV 2012 Sp1
- LV Run-Time 2012 SP1
- NI-VISA 5.4
- MAX 5.5
- DAQmx 9.7
destination computer:
- W7 64bit
- LV Run-Time 2012 SP1 32bit
- NI-VISA 16.0
- MAX 16.0
- DAQmx 16.0
Any hint is welcome.
Many Thanks and Best Regards,
Christian
.