Is there a way to use USB-6008 with LV 6 student edition?

[schaffer124]

I have tried installing the NI-DAQ v8 drivers and it won't take unless I uninstall the older drivers that come with the LV 6 student edition.  This makes it possible to use the VI logger, but then makes it impossible to use applications like DAQ Solutions.  The manual for this usb daq does say that it is only compatible with LV 7 or higher, but I wonder if there is a way to make it work?

[Tom_W_[DE]]

Hi Schaffer-

No- there is no driver for the USB-6008 that will work under any version of LabVIEW prior to 7.0. 

Thanks-

[terrill]

DAQmx is aweful. Is there any way to get documentation so I can write a nonDAQmx driver?

[Tom_W_[DE]]

Hi terrill-

You don't say specifically, but I'll assume you're also working with the USB-6008 since your post was added to this thread.  Unfortunately there is no documentation available externally for writing your own driver for the USB-600x series.  NI provides NI-DAQmx and NI-DAQmx Base for interface with the USB-6008.  If you would like to log specific requests for driver development needs with my team, please feel free to email USBDDK@ni.com with details about your application, target platform, and why the existing driver solutions don't meet your needs.

That said, I would like to help with some of your issues with NI-DAQmx if possible.  If you could please elaborate on why it doesn't meet your needs I will be happy to help with any suggestions to hopefully improve your experience.

Message Edited by Tom W [DE] on 04-07-2008 04:28 PM

[terrill]

Thanks Tom,

You are right, I have just been tasked to a project that specifies that I use this board. I do not like the added complications that DAQmx adds to setups or the effects it has on certain code. For this project, there is no real issue that I have with DAQmx programming. The group I am codeing for is extremely nontechnical. Soon after I am finished with the project I will not be able to support the application. I do not like the added measurement and automated explorer needed to specify the device. It is just one more item that can break. I am also not even sure how that works after I compile the code into an application. I would prefer to only introduce one application for this project.

My main issue with DAQmx is the way it handle sessions. I make "object like" drivers that use dynamic calls. Using DAQmx in a dynamically called driver in TestStand, I have not found a way to keep the session open. Ther result of this is that I have to do everything at one time, so I have to save all the settings and then apply them when I make the measurement. NIs attempt to make things simple has made things more complicated for me.

I do not think NI should force a codeing style on people. It is bery easy to offer DAQmx coding and traditional style drivers. I would prefer to have full control of the board so I can tweek functionality as I need. There will always be people who do not like express type code. I have also seen some of the code the NI releases. NI should at least follow the coding guideline that they insist developers use to get certified (the modulation toolkit is one). There are tradeoffs for all coding decisions and I believe I should have some say on them. Because of the reasons stated, I have avoided purchasing NI cards that use DAQmx. I can buy competitors hardware and use traditional drivers. I will admit that it has been a couple of years since I have dealt with DAQmx so there is a good chance that I will learn something from this.

Terrill

[Dennis_Knutson]

I don't understand your comment about MAX. MAX was shipping with NI DAQ devices a long time before DAQmx was available and it's role has not changed. The installation of MAX is optional (though very handy for testing pruposes) but it isn't necessary any more than it was for traditional DAQ. You certainly don't have to use the Express VIs. Exactly what 'full control' did you have with tradtional DAQ that is missing with DAQmx?

Also, can you expalin a bit more about what you are seeing with TestStand?

[terrill]

TestStand opens and closes vis as needed. If I open a session and pass the session as a variable. The LabVIEW garbage collector will make the session invalid. With the DAQmx I have seen, when the session reference is cleaned, all settings are no longer valid. The garbage collector will clean all references that are created from a dynamicall called VI.

Wanting more control is a generic statement. I have no idea what control I would like to exploit because I am not given any information.

I also never said I had to use express VIs. I made an anology of DAQmx to express VIs. It's purpose is to make programming simpler. I do not know any engineer that like express VIs and most of the ones I have worked with do not like DAQmx.

[Dennis_Knutson]

Well, I like DAQmx. I don't know any engineer that likes to spend more time on a task than he or she has to.

I'm still confused by some of your statements. You say you want more control but can't explain what control you are missing. I think the information about DAQmx is at least as comprehensive as the information about traditional DAQ.

I will, however, see if I can reproduce your issue with TestStand. I never used a DAQ card with TestStand before - it was always GPIB/serial/USB instruments but that is about to change so I'm curious to see what is going on.

[terrill]

We can agree to disagree about DAQmx. My question was if I could get the information needed to code my own driver. If you would like to reproduce what I see in test stand, you will need the following following vis called in a TestStand.

1. An initialize vi that dynamically calls a vi that opens a session.

2. A setup vi that dynamically calls a vi that sets up the instrument.

3. A measurement vi that dynamicall calls a vi to make the measurement.

You should see the reference is invalid is step 2.

[Dennis_Knutson]

There is the DDK and a dedicated board.