From 11:00 PM CST Friday, Apr 11th - 1:30 PM CST Saturday, Apr 12th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CST Friday, Apr 11th - 1:30 PM CST Saturday, Apr 12th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
10-02-2010 06:25 AM
Hello,
This is my log file to install NI-VISA and Py-VISA on Ubuntu 10.04. This log is the compilation of one day of frustration!!
Although it is not very difficult... I am not a specialist and it always takes me some effort to go back to this level of details.
Installation of NI software will always be a pain and Linux users should really think twice about the choice of their distirbution
(see the end of this message where I recently switched to Scientific Linux for peace of mind).
I do it mainly for back compatibility purpose but thankfully I am not in a critical situation as those who are running labview.
I only need it as an abstraction layer in python (great way to interface work).
NOTE: My PyVISA seems broken!
>>> import visa
>>> visa.get_instruments_list()
>>> keithley = visa.instrument("GPIB::12")
It could not find the proper library VI_ERROR_LIBRARY_NFOUND: A code library required by VISA could not be located or loaded. I tried both to compile PyVISA w/ pyhton2.5 or python2.6: same problem! If someone has a feedback experience about it, comments are welcome!
Update of the problem (Jan 12 2011): after extensive search I am convinced that there is a bug in the module NiViPciK inside nivisa 5.0. It does not recognize PCI gpib device !!! Seems like there is some miscommunication w/ the Kernel.
Update (Jan 17 2011): after a long search around the problem, I decided to give up on Ubuntu and I gave it a try to Scientific Linux latest release 6.0. Amazing: it works right out of the box! What a change with the Ubuntu ordeal. Could even succeed to put my latest python package. Well I think that I am going to stick to SL environment for data acquistion. This is for me a rediscovery of Red Hat (my first Linux environement ... back in 94) after some infidelities w/ Slackware, then Debian, a little passage through Libranet and a rather long fidelity to Ubuntu, well it is a pleasant surprise. I discovered the famous yum, which did not exist half a decade ago back when rpms could be scarry: you could send your system to oblivion w/ rpms. First impression, it seems now on par with apt-get. At least with SL6.0 I get a pretty decent environment w/ python 2.6. High five to the SL 6.0 team! Morality, it is way easier to change distribution then try to force the NiVISA encapsulation in Linux.
10-18-2010 05:27 AM
Hi,
I'm trying to install NI-VISA following your advices. I encounter several issues with it. I precise that I have installed ubuntu last week so I am a very new user of it.
I got then the 10.10 version.
So, first I got the "unknown tag error" when executing the alien conversion of the nikali.rpm but it seems it doesn't care according to what I saw on others tutorials.
More troubling, I can't find any 'modshell.sh' file and there is no repertory "nikal" at the '/usr/local' location.
Also, when I try to modify the 'nikalKernelInstaller.sh', I get the information : 'modul nikal not found'.
Could you help me about these issues?
Sorry if my questions appear to be very basic.
Bye
10-26-2010 08:42 AM
It did not work for me. There were several errors and missing steps.
"unknown tag error" - this can be ignored if the .deb file is created
10-26-2010 03:27 PM
thanks for posting this, it is helpful. However, would it be possible to expand it to include instructions on how to install the c api as well?
01-11-2011 06:21 PM
I am hoping this will work for me on my Ubuntu system. I just need GPIB to work as i understand it .
I plan to use matlab/GPIB to send commands to an Agilent Microwave network analzyer.
I am not sure where the NI-KAL comes in. NI web site says that NI-KAL is unsed in every Linux driver.
wbg
01-12-2011 09:22 AM
nikal is the glue to all NI closed-source driver. This is necessary to isolate our binary against changes in the Linux kernel.
06-27-2018 11:05 AM
@irwan wrote:
nikal is the glue to all NI closed-source driver. This is necessary to isolate our binary against changes in the Linux kernel.
That's the idea behind. In practise, it never works well - there're just so many things that can change in subtle ways on binary level, between versions as well as build configurations, that a proper isolation takes something like an own VM (which always have to be kept up to date for each kernel version).
The whole thing is economically ridiculous: properly mainting something like nikal (what NI doesn't really do) is a full time job for several people. OTOH, writing a proper IIO driver for a DAQ device takes about 6 weeks (yes: been there, done that).