Data Acquisition Idea Exchange

About Data Acquisition Idea Exchange

Have an idea for new DAQ hardware or DAQ software features?

  1. Browse by label or search in the Data Acquisition Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!
Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 

Post the NI-DAQmx base C Function Reference Help pages on your fora somewhere

I continually come to your site looking for the DAQmx base API manual and have yet to find it.  I eventually have to dig out an old CD to find my copy.


How 'bout posting these online so that we can help ourselves out of jams?




Knight of NI

You mean this?


Could be-- is it inside that proprietary-format "CHM" file embedded in a ZIP file hidden under a title with "Labview" in it?


I want to be able to search for DAQmxBaseReadAnalogF64 and have one of the results be the man page.

Knight of NI

The ,chm is a widows help file that contains the c reference for DAQmx Base. I don't see LabVIEW in the title, just 'C'.


Indeed, a windows help file, buried in a zip file.  Kind of contrary to the whole idea of HTML and platform-independent documentation available on The Internets, no?


And not very useful when I'm using a web browser on a linux box or mac to find the information on the NI web site while I'm up to my eyeballs trying to debug someone else's code and I just need to know "just what ARE the units on that parameter anyway?" and I haven't downloaded the various helper apps and really, why should I have too, I mean, it's the web and HTML is platform-independent by design and surely they want to help me write software that will make their DAQ work in my product so that my company can sell more of our products and thus sell more of their DAQs, so why make it so hard?



And there's that little "I can't find it when I search for DAQmxBaseReadAnalogF64" issue.



Seriously, the DAQmx base API manual needs to be posted on the website.   And accessible by platform-independent means. In Plain Old HTML.  And made searchable. Period.



Active Participant

If the code you're debugging can compile on that Linux box, that means the DAQmx Base C API is installed on that Linux machine, which means that the pure HTML docs for the API are installed on that Linux machine. And they're searchable since they're flat text, and you don't need a network connection ;-)


Try looking at

"/usr/local/natinst/nidaqmxbase/documentation/DAQmxBase C Function Ref Help.html"


And yes, it's aggravating to not find man pages or other online formats, but there are other mechanisms at play that make it difficult to just put the docs in a place where they can be indexed. We're aware of the discrepancy, but there isn't much my development group can do at this time.

Joe Friedchicken

NI Modular Instruments Application Software
Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
Senior Software Engineer :: Modular Instruments Application Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2016)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)

Nice, thanks for the tip Joe-- found it on the build machine.  Which is a headless machine located in the cloud.  Granted, I could copy them to all of the various virtual and physical machines that I could ever possibly use when I'm trying to debug code to sell more NI products to my customers.


I feel your pain on pushing the other mechanisms into the 21st century.  Let this thread serve as notice to the keepers of said mechanisms that the OEM developers trying to make you money are looking for some love.  Hopefully not in all the wrong places.





P.S. to any metrics keepers and product managers:  I still want them online.  On your site.  And indexed for easy access.  From any modern browser.  Like the Eagle DAQ does it:



2+ years later.  Still no joy.  For anyone else who ends up here looking for love, try the Oregon State physics department


It is unbelievable how hard it is to find good documentation on NI's web, especially on the C APIs. Shameful.


I extracted a few CHM files into an easy-to-browse online reference website, hopefully reachable by Google in the future: 



 Enjoy it.