lsdaq pci daq board not found

[simmer]

Help!   I have red hat linux 5, and installed the latest ni-daq base drivers 3.4.0f2.   Running lspci I see my national instruments pci-6070e board:

07:04.0 Class ff00: National Instruments PCI-MIO-16E-1

But when I run lsdaq, I it finds nothing:

--------------------------------
Detecting National Instruments DAQ Devices
Found the following DAQ Devices:

--------------------------------

Any ideas ?

[TimmTheEnchanter]

Hi Simmer,

It looks like your computer is recognizing that the PCI device exists, but the drivers are not finding it correctly.  Could you confirm that you're using the NI-DAQmx Base drivers?  They are different than the legacy NI-DAQ drivers.  Here is the main page for the driver which does support Red Hat 5 (you find it by going to ni.com, clicking Support, then Drivers and Updates).

NI-DAQmx Base

Also--could you provide some history on this board?  Did you inherit it or did you just purchase it?  There are some leads on ni.com about using DAQmx Base with a USB device that previously had DAQmx firmware installed:

USB Device Firmware Incompatible with DAQmx Base 3.0 or Later

Also, these questions might be a little more obvious, but have you restarted your computer since installing the drivers?

-Andrew

[simmer]

Andrew,

Thanks for the tips.  Unfortunately after 3 days of trying to port to linux platform, aborting the mission.  There are just too many things which do not work.  For example the 3.4 version although stated to work with Red Hat WS 4, includes a patch library which is incompatible.  Downgraded to previous version.   Also, the base ni-daq package doesn't seem to provide the API to read continuously (using callbacks) or even manipulate low level registers in a DAQ board.  I suppose there might be undocumented API, but I don't have the time to go there.  Amazingly NI-DAQmx 8.0.1 can not be made to work with RH5, but Labview2010 does work!  This appears to me a mess...

Thanks,

Simmer

[TimmTheEnchanter]

Hi Simmer,

I apologize for the confusion.  I'll be the first to admit that sometimes finding the resources to answer your questions is not always easy or intuitive.  Nevertheless, I'm happy to help assist you in checking compatibility for your application.

Could you show me where you found the patch library which isn't compatible with Red Hat 4?  Also, could you describe what you are actually trying to do in your application with reading continuously using callbacks or driver level programming?  Check below for more info on a Measurement Driver Development Kit you may be interested in.

Looking through some of the links I found there, I found a KnowledgeBase article: What Linux Distributions Do National Instruments Drivers and Software Support?  As you mentioned, this does appear to confirm that Red Hat 4/5 is supported with DAQmx Base 3.4/3/2 and LabVIEW 8.6, 2009, and 2010, but it isn't compatible with regular DAQmx 8.x or Red Hat 3.  While this KnowledgeBase is helpful in comparing side-by-side, it is not the golden standard--you need to look in two different locations for LabVIEW and driver support on certain OSs.

The golden standard for what LabVIEW supports are in the Release Notes (here is the link for the Release Notes for LV 2010--look on Page 5 for the machine and OS requirements.)

The golden standard for the drivers (such as DAQmx) is the ReadMe file.  To search for a particular driver and find it's readme file, you can go to ni.com/drivers and type in the driver under question.  That will pull up all the versions of that driver, and you can look at the readme to find out if there is any linux compatibility.  (I linked DAQmx Base 3.4 in my earlier post).

Whether or not your application can work is (of course) highly dependent on what you're donig; however, from what I've found so far, it looks like Red Hat 4/5 should work with DAQmx Base 3.4 and LabVIEW 2010, but if you're looking for more DAQmx functionality, you may need to look into the Measurement Driver Development Kit.

[simmer · Accepted solution]

Andrew,

Thanks for the note about the DDK.  

Wanted to let you know by putting the DAQ boards into another linux workstation also running RH, lsdaq did find the cards.

I still maintain there is no way of knowing the difference between mx and mx-Base without downloading both and reading the helpfiles.

Also the word "subset of functionality" is misleading also because you have to change all the function names.

Jonathan