NIDAQ MXbase cfg files

[moonrec]

Hello,

I am using an USB 6009 module. I installed NIDAQ MXbase CD. The configuration utility was run and saved.MAX recognizes the device, the example datalogger works, yet when you are going to program an application, the system returns an error message stating that there are no tasks created. When you click to create a new task, it says that the device identifier is invalid. When you try to browse tasks on the MXbase VIs, the list comes out blank! I also have a third party application that can talk to NI NIDAQ MX devices, and the application returns a device identifier invalid error.

What is going on? I have run some examples and they seem to work with one or two channels, but thats it. I have configured more channels, but they don't show up. Where is Labview going to look for the CFG files? Do I also need NIDAQ MX in addition to MXbase for this to run? Help!

Gariel Sierra, UCC

[LYu]

Hi Gariel,

The DAQmx Task control used is only populated with DAQmx tasks, hence it's normal that the list is blank. You can type in the DAQmx Base task name manually to run it. You do not need to install DAQmx to run your USB6009 tasks. The reason you're receiving an error message is likely because LabVIEW was opened before the task was created and saved in the Configuration Utility. To resolve this, simply re-open LabVIEW, or make sure you save the task in the Utility before opening LabVIEW. You can find more details from the following article:

Error -200428 Occurred at Unidentified Location When Trying to Use a Task in NI-DAQmx Base

The task configuration is written to a .cfg file. You can see a similar file when you select "Export Task List".

I'm not familiar with your third party application, hence cannot make any suggestions. Can you describe what kind of software it is and how it's communicating with your 6009 device?

Thanks,
Lesley Y.

[moonrec]

Hi!

The third party software is WinWCP.

http://spider.science.strath.ac.uk/PhysPharm/showPage.php?deptID=2&pageName=software_ses

I did a closer look to the driver area at the recording configuration and I noted that the support is for NIDAQMX and not MXBase, so maybe this is it. I will e-mail the author to and ask for MXBase support.

I did close Labview and restarted, but the tasks still do not show. If I type the task name, when I run the VI, it reports that the task is invalid. If I go to the configuration utility, the tasks are there (!!). I have no problem with traditional NIDAQ, as this is what we have been using at the labs.

Thanks

Gabriel

[LYu]

Hi Gabriel,

The software does not appear to support DAQmx Base devices, which is likely why you couldn't communicate through it. However, since the program communicates with the device through the driver installed, it may be possible to use it. You can contact the software creater for more information.

When running the task in LabVIEW, are you using DAQmx Base VIs (just want to be sure since they look similar to the DAQmx VIs). Try using the shipping examples (from Windows, go to Start >> Program Files >> National Instruments >> NI-DAQmx Base >> Examples >> LabVIEW 7 (or LabVIEW 7.1) >> Static. Also, make sure you create the task in the utility, then open LabVIEW.

Thanks,
Lesley

[moonrec]

Hi!,

I already talked to the program's author and he stated the he will not be supporting the 6009 device because of some critical timing issues that would render the device useless to the intended application.

I have already tried creating the task with the configuration utility; it simply does not show up in Labview. If I use the I/O assistant, it says I have no hardware present, even with it showing up in max.

The examples work OK and the hardware work if you use a dummy task. But not with a pre made task.

I also noted that this hardware has a serious calibration problem. Reading voltage, I apply 9 volts, it reads 11.3, and reversing polarity it shows 7.3 volts. I never had this with traditional DAQ devices. We are ready to give up on using this toy and will continue using the good and proven PCIs.

[Sean_C.]

Hello,

Are you able to create a new task within the DAQmx Base Configuration Utility? If so, open the DAQmx Base Static example, Acq&Graph Voltage-Int Clk.vi which can be found at: C:\Program Files\National Instruments\LabVIEW 7.1\examples\daqmxbase\Static\ai . This task name will not appear under the "DAQmx Base Task" control because that control is, in fact, a DAQmx Task control. It will only be populated with DAQmx Tasks. Simply type the DAQmx Base Task name in that control and you should be able to run the VI.

Additionally, you will not be able to use DAQ Assistant with this device. The DAQ Assistant only supports DAQmx devices.

Do you still get incorrect values when you run this example?

Regards,
Sean C.

[SteveP]

The voltage error readings may be due to the 6009 input circuitry.  It passes a voltage reference (2.5V) through a resistor dividor and the input is connected through a resistor to their junction.  The source signal appears to have to have a relatively low impedence to be able to "drive" this configuration.

Message Edited by SteveP on 07-12-2005 10:35 AM