LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-DAQmx Base: not finding correct subvi's

Hello,

 

I am attempting to revive a project that died with an old windows computer. I am attempting to do this on a different computer that is running Scientific Linux 6.2, so I installed LabVIEW 14.0 and then attempted to find the correct drivers for a PCI 6013 card that connect to some thermal probes. I first screwed up and tried the newest version of NI-DAQmx (8.02) which was compatible with RedHat but not really with my version of LabVIEW. So I uninstalled it and then installed the NI-DAQmx Base 14.0 which is supposed to be compatible with Scientific Linux, PCI 6013's, and LabVIEW 14.0. I confirmed that the software recognized the PCI and then attempted to run some of the old vi's. As I expected, the code had trouble finding the "DAQmx_Read" polymorphic subvi's. But I also expected to simply be able to replace that subvi with the DAQmx Base equivalent and I cannot find it. In fact, I cannot find any DAQmx Base vi's. Can anyone help me interface with my PCI? Otherwise, should I just give in and setup a dualboot with windows?

 

-Roger

 

0 Kudos
Message 1 of 3
(2,585 Views)

Roger,

 

DAQmx Base is a complete different driver than DAQmx. So if the VIs are using DAQmx, an installation of DAQmx Base doesn't work out.

There is no conversion tool which converts a project using DAQmx to use DAQmx Base.

 

So depending on your project, it is very likely that you require a Windows system to use DAQmx. You can, however, modify the project there to use DAQmx Base instead in order to have it runnable on a Linux system.

I think you are aware of this KB....

 

thanks,

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 3
(2,555 Views)

Norbert,

 

Yes I was aware of that kb and was simply going to attempt, as you suggested, to modify all of the vi's to use the DAQmx Base equivalents (here, i mean that if the original subvi is used is DAQmx_Read.vi, I would replace it with DAQmxBase_Read.vi and reconfigure the settings).  My issue was that I was not finding DAQmxBase_Read.vi anywhere even when I used $locate or otherwise. However, in messing around with the Task Configuration Utility, I found them in the functions palette where they were not before. I'm not sure what happened but at least I have access to them now. Any idea what happened? In creating some empty tasks, did I somehow force LV to unpack something I had missed before?

 

Best,

Roger

 

0 Kudos
Message 3 of 3
(2,543 Views)