‎02-04-2011 08:01 AM
Hi,
Our APP is based on NI-DAQ (Legacy) driver developed function based (nidaq32.lib) and used to run on WinXP. But, as we are moving to Win7(64bit), it needs to be ported to NI-DAQmx which is supported for Win7.
We are using different APIs DIG_* in our app but there is no such APIs in NI-DAQmx c help doc.
I see on ni website, it is mentioned that we can use existing APP developed on legacy driver even with NI-DAQmx using transition libraries developed by NI. I didn't find those.
Could you please help where can I find libraries which could bridge gap between app dev on legacy driver and work with new DAQmx driver??
For users who plan to upgrade to NI-DAQmx but want to use their current Traditional NI-DAQ (Legacy) applications with new NI-DAQmx-supported hardware, NI has created the Traditional NI-DAQ (Legacy) compatibility VIs. These VIs replace certain Traditional NI-DAQ (Legacy) VI libraries with libraries that work with both Traditional NI-DAQ (Legacy) and NI-DAQmx. These VIs look identical to the existing Traditional NI-DAQ (Legacy) VIs and integrate seamlessly into existing applications. The compatibility VIs were created to use while waiting for the application to be rewritten using NI-DAQmx, but you can still use NI-DAQmx-only devices.
Note: These VIs do not support all features on all devices and are not guaranteed to be updated with future revisions. To learn more about these VIs, visit ni.com.
Thanks,
amandil
‎02-04-2011 11:57 AM
‎02-04-2011 12:04 PM
Thanks. This seems to be for application developed using labview. What if application is *daq.exe in C/C++ compiled with functions from NIDAQ like DIG_* with nidaq32.lib? Is there any corresponding lib for NI DAQmx?
‎02-04-2011 12:13 PM
The note says it was for LabVIEW. I'm not aware of any other transition library.
‎02-04-2011 12:15 PM
Thanks again for prompt reply. I will check if labview VIs can be used.
‎03-24-2011 07:14 AM
Dear,
i am looking in ni.com but i can find any evidence about vls for nidaq in win 7
‎03-24-2011 07:43 AM
That is because a driver does not exist.