Multi DAQ-6008 VS Vernier_SDAQ

[ukmaster]

Hello.

I used to use Vernier SDAQ which is made by NI but distributed by Vernier.com.

I am trying to use SDAQ and NI Multi_DAQ-6008. But, the second is working well, but SDAQ is not anymore.  I guess the problem seemed to start after installing the driver program for multi DAQ-6008.

When I tried to use SDAQ, it shows an error message saying "SDAQ Data Collection VI.vi - You will no longer recieve mouse up events after a drag and drop operation.  You will recieve the Drag Ended event for the drag source control instead".

I have no idea how to solve this error.

Please help me solve the trouble.

Thank you.

Choi

[BrowningG]

Hello Choi,

From your post, I am assuming that you have a functioning USB-6008 and a non-functioning Vernier SDAQ.  This behavior started occurring after you installed DAQmx 8.6.  Please let me know if I have assumed incorrectly. 

The SDAQ is a device based on the USB-6008, so it should function properly if the DAQmx driver is installed correctly.  To make sure the DAQmx driver is installed correctly, try running one of the general DAQmx examples that are installed with the SDAQ driver.  A good one to try is DAQmxEx01_Ch1 located in the path C:\Program Files\National Instruments\LabVIEW x\user.lib\SensorDAQ\EXAMPLES\UsingDAQmx where x is the particular version of LabVIEW installed on your machine.  This example will allow you to read a sensor attached to your SDAQ without much user interface programming to get in the way.  If this example runs as expected, then the DAQmx driver has been correctly installed. 

I found this knowledgebase that goes over one possible issue when using an SDAQ with DAQmx 8.6.  This error prevents a measurement task from running and is not related to the user interface, but it is worth a try. 

Most likely, there is a programming issue with the example SDAQ Data Collection VI.vi.  I looked through the code, but was unable to find where this error code is coming from.  Would it be possible for you to run highlight execution and determine exactly which subVI is throwing the error?  Knowing exactly which subVI is throwing the error will aid greatly in the debugging process.  I do not have an SDAQ, which makes it impossible for me to run this example and find which VI is causing the error.  I believe this is a user defined error code that was written in by Vernier.  As a result, it would probably be most beneficial to contact the Vernier technical support for more information regarding this error. 

[ukmaster]

Hello Browning,

Thank you for your detailed answer.

Your understanding is very right.

Let me try your suggestion and tell you the result.

Thank you again.