Error 89120 when running SVT swept sine example with USB6251

[autoaudio]

When I try to run the SVT Swept Sine DAQmx example with a USB6251, I get error code 89120 - Source Terminal to be routed could not be found on the device.   When I use MAX, I can generate and acquire signals with the USB6251.   All other programs work fine also.     When I run the example on a PCI 6281 (my Dev1) it works fine.   I switch the device to Dev2 (USB6251) and I get the error.    Any suggestions? 

[Brooks_C]

Hello Autoaudio,

I have tried running both the SVXMPL_Getting Started with Swept Sine (DAQmx).vi and SVXMPL_Getting Started with Swept Sine Express VI (DAQmx).vi examples on my PCI-6251 successfully so it should work with yours.  There are a couple things that we can try.

1.  Run the example using Dev1 (the PCI 6281) to confirm that it’s working correctly.

2.  Go into the MAX and rename the PCI-6281 to be Dev3 (or some other name that isn't already taken) and rename the PCI-6251 to be Dev1.

3.  Without changing anything in the example VI try running it again.

If the example program works this time then it’s likely that you need to specify which device to use in a couple of places in your VI.  That is, when it throws this error it’s because it’s still trying to use Dev1 on some control even though you've specified Dev2 once. 

If the example program still doesn't work after you've renamed the PCI-6251 then it’s possible that your card may be damaged.  To check this you can run the DAQ Diagnostic Utility.  Once you download and install this utility run the executable.  You should see a window pop up with a drop down window in the top left corner where you can select your device.  Choose the name of the PCI-6251 and then start the diagnostic using the button in the bottom right of the window.  NOTE:  disconnect any connections you have to the PCI-6251 before running this utility.  The utility internally routes signals to and from inputs and output so if you have external connections to any of these pins it may skew results.

If you find that you board is failing some part of this diagnostic then you should contact National Instruments directly to arrange for a repair using the contact information at www.ni.com/contact.

If the example program is still not working and the device is passing the diagnostic utility then it would be helpful to know the following:

1.  What is the exact title of the example program you're running?

2.  What VI throws this error?  (You can use highlight execution to find this out.  To do this click the light bulb in the top left of the block diagram before running the example.)

3.  What is the full error text?  A screen shot of the error would be preferable.

I hope this helps, and have a great night!

[autoaudio]

Brooks, Thanks for your diagnostic help!!!!  

I tried running with USB 6251 as Dev1 and still got the error.  I then ran with Dev3 (PCI 6281) and it worked.   I ran the diagnostic utility and everything passed.    Here are my specifics:

LabView 7.1

Sound and Vibration Tool Kit 3.1

DAQmx 8.6

Example:   SVXMPL- Getting Started with Swept Sine (DAQmx).vi

The problem is occuring in the SVT Start Swept Sine (DAQmx).vi.    I opened this vi up and found that it is the DAQmx Write (analog 1D DBL 1 chan Nsamp).vi that is flagging the error.    I have enclosed an Excel spreadsheet that shows the actual error I am getting and the probed vi's.   

Could it be a LabView 8 vs 7 conflict?   I do have LabView 8.0 but haven't updated yet.   If I do update, do I uninstall 7.1 and the SVT 3.1 and then install LV 8.0 and reinstall SVT  3.1 ?  

I have other vi's I have written using the USB6251 and they work fine, it is just the swept sine portion that is causing issues.   Thank you VERY MUCH for looking into this!!!!!

[autoaudio]

UPDATE - GOT WORKING BUT DATA SUSPECT - TRIGGER LINE IS UNRECOGNIZED TERMINAL.

In the SVT Start Swept Sine (DAQmx).vi there is a string PXI_trig0.   When I disconnected this line, the SVXMPL Getting Started with Swept Sine (DAQmx).vi did work, data was suspect but at least it worked!    Do USB devices require a different trig terminal in order to run properly?  

[Stuart_G]

Yes...unfortunately my DAQ is not working for me now 🙂 so I can't fully verify, but the USB device will not have a trigger line called PXI_trig0.  You will have to use whatever the external trigger for that device is.

StuartG

[Brooks_C]

Hello Autoaudio,

Stuart is correct, if you're trying to use the PXI trigger line you'll need to change that value.  I also wanted to add that I just tried running the example on a USB-6251 and it worked just fine for me.  That means that your VI (or one of its subVIs) has likely been modified and saved over the original example VI.  If you haven't intentionally changed this VI then you can perform a Windows repair of the installation to restore the correct example program.  If you've intentionally changed this VI then I would follow Stuarts advice to make sure you use an available trigger line.

Cheers,

[autoaudio]

I changed the trigger to PFI0 and it worked, data looked good.   I didn't intentionally change any *.vi's so will check on the repair as well.   Thanks for all your help, it was greatly appreciated!!!!

[PBear]

Hi autoaudio,

This VI has been changed in subsequent versions of the Sound and Vibration toolkit that have been released. Specifically the trigger line has been changed to be more compatible with more DAQ devices. Your S&V toolkit was designed before many of our USB DAQ solutions were created and thus this error is expected behavior. On the other hand, the correct workaround is exactly what you implemented so I'm glad you were able to reach your goals!