Will NI add dynamic task support in DAQmx Base for the CF-6004?

[jaustin_UF]

I learned today that DAQmx Base 3.2 does not support dynamic tasks for the CF6004 CompactFlash card. Things will probably stay this way unless NI sees a higher demand for this service.

Does anyone here on the forum see the need for such support?

Jim

[Jaf1974]

I need to build an application for CF-6004 using dynamic task configuration....this is very important to me

[nayer]

Hello Jaf1974

You can put a product feedback as R&D do look at them and implement depending on the need. 

Regards

NI-khil

[Jaf1974]

Thank you NIyer for your advice. I have submitted a suggestion.

when building Labview mobile application for CF-6004 , I faced the following problems:

1) No dll or activex control available to be used by VS2008 or EVC++ to configure and read data from Cf-6004 without using Labview 

2) dynamic tasks are impossible to implement

3) dll can not be built using Labview mobile (no way to build my own dll)

4) linking between VS applications and Labview application is hard to implement (only possible way is File I/O)

5) building time is very long due to saving of too many vi and subvi (M-series, E-series, CFD, .....etc), i dont know why saving all these files each time an application is built?!

For all the above reasons I've found that CF-6004 is not the ideal soultion for building PDA data acquisition system. If NI solve some of the above problems it will be very helpful for programmers and developers.

[jaustin_UF]

I had to abandon my PDA/6004 project for another reason: after numerous discussions with NI support over two months, being clear about the components I was using, I was finally informed that DAQmx Base 3.2 does not run on Windows Mobile 6, the OS on the PDA I selected. Several months later my field engineer let me know NI does not intend to ever provide DAQmx Base support for WM 6 (and I presume beyond).

 

It appears that PDA support from NI is fading. I’m not surprised; the constant reduction in the size of devices (netbooks, UMPC’s) that run a full Windows OS makes development on a ‘different’ OS less important. I just wish I hadn’t been caught in the evolution.

[Jaf1974]

Hi All, I've found a solution for the lengthly building time and large application size....this is because NI adds support for all series of devices in the vi , to remove the unused devices such as M-series, E-series, one must edit the vi which performs the specific action such as DAQmx Base Start Task.vi, DAQmx Base Stop Task.vi and reading/writing vi....etc. But before doing that make a copy of the original vi. I have edited the task start, stop and raw data reading to support only CF-6004 device. The result was reduction in the Dependency vi from 202 to only 37 and size from 2.1M to 900k with much faster and better run.

If someone interested I can post the edited vi's.

regards

Jaferson

[Jaf1974]

Hi there, I know this post is very old but i guess many guys visit it when reading the topic or by googling about CFDAQ6004 driver. Unfortunately CFDAQ6004.dll is very low level driver that support several functions dealing directly with CF6004 card such as ATTset and ATTget... etc. as one can view in any PE explorer for Windows CE. After a month of testing and analysis, i have successfully written a dll based on CFDAQ6004.dll to open, configure, read, write analog/digital data from/to CF6004 card. The new library was given a name CF6004LIB.dll the following is comparison between my dll and daqmxbase driver:

        New Dll                                                                                     DAQmxbase driver

1. Can be used inside any programming environment                        Can only be used inside Labview

    inc. eVC++ , VC++ .net, VC# .net, VB .net

2. Support fully dynamic task configuration                                       Only static configration possible (dynamic task can be done with modified VIs)

3. Remove a lot of overhead by accessing CF6004 directly                Puts a lot of overhead passing through GUI, objects, controls, ...etc.

4. Support full error detection                                                           Some errors can not be catched

5. Full sampling rate can be achieved 200 kS/sec                               system dependent (max. 130 kS/sec in hp ipaq 211 PDA)

6. Support contiuous/limited sampling                                               continuous sampling is possible but at reduced rate`

7. small in size < 10 kB                                                                    Minimum program size 600 kB

Also, I have written some modified VIs for CF6004 including reduced (specifically used for CF6004 card ) VIs and dynamic task configrable VIs.

Bye

Jaf

[AdnanZ]

Maybe you want to mention how people can get access to the driver, if interested.

[Jaf1974]

Hello Adnan,

I'm currently using this driver for my own project to build portable data collector. I'm not sure it is legal to distribute or publish the driver unless NI agree. there may be a LOA or something like. Also, i have written some examples about how to utilize the driver in VC and VB .net

Regards

Jaf