LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Multifunction I/O (NI USB-6009)

Hello, I am trying to use NI USB-6009 to send out an output voltage to a pulse generator as well as timing a camera on a microscope so that the picture is taken from the microscope when the pulse is generated.

So far I have this created on the VI
blocks.JPG

 

 

Inside the DAQ, I have an error of 50103.

If anyone could provide help on how to structure my VI or how to get rid of the error code, that would be most helpful. thank!!!

0 Kudos
Message 1 of 9
(4,559 Views)

When you put a picture of your code and ask for help, we can't "probe" the picture and see what is "hidden".  For example, we cannot tell how your Express VI is configured.  What I can tell you is that the Sequence frame is unnecessary.

 

What kind of output are you attempting?  Analog Out or Digital Out?  I assume you know that Analog Out capabilities of the 6009 are quite limited -- update rate is less than 200Hz.

 

I could not find an Error description for 50103 or -50103.

 

To get more useful help, attach your actual VI to your next post.

 

Bob Schor

0 Kudos
Message 2 of 9
(4,551 Views)

The Error:  http://digital.ni.com/public.nsf/allkb/485201B647950BF886257537006CEB89

 

You will find that the example finder will help with many problems on how things can be done.

 

Help - Find Example

 

Hardware Input and Output - DAQmx - Analog Output

0 Kudos
Message 3 of 9
(4,548 Views)
Did you look up what the error code means?
Did you try Googling "LabVIEW error 50103"?
Did you try the fixes offers in the results of the above-mentioned search?
What have you tried?
How is the express VI configured?

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 4 of 9
(4,545 Views)

@NoClue2016 wrote:

Inside the DAQ, I have an error of 50103.


That error code means "The specified resource is reserved. The operation was completed by ignoring or overriding the specified resource."  This is likely caused by you not releasing the resource.  There should be a "Stop" input on the DAQ Assistant.  Make sure your stop botton is wired to that.

 

Otherwise, make sure nothing else is using the DAQ.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 5 of 9
(4,508 Views)

Hello all, sorry for the delay, I work M/W on this project only.
I do appologize for any trouble caused, I am very new with labview.

I am using  ANALOG, and I dont believe most of the error cases effect me (at least to my limited knowledge), how do i give the actual VI? 
I have also gone ahead and wired the Stop button, but still have an error.

0 Kudos
Message 6 of 9
(4,430 Views)

When you post a Reply, you should see just below the space where you are typing something called "Attachments" (in bold letters).  Click "Choose File", navigate to your VI, click it, and it will be "attached" when you Post your reply.  Then we can look at it and better understand your question and can provide helpful and relevant responses.

 

Bob Schor

0 Kudos
Message 7 of 9
(4,421 Views)

Here is what I have, its not much, let me know how best to continue.

0 Kudos
Message 8 of 9
(4,413 Views)

You obviously changed something in the DAQ Assistance between the Picture you posted and the VI.  I plugged my USB-6009 (which is called by MAX "USB-6009" rather than "Dev1") into my PC.  I then modified your code very slightly, to look like this:

Analog Out.png

I wired the Stop button to the While Stop, wired some data (a random number) to the Data input, wired a Constant to the Device input (it was initially blank, but then I clicked the little triangle and it showed me the Devices that MAX could see, including the USB-6009, which I'd named "USB-6009").

 

When I push Run, it runs.  I don't have anything hooked up to the output of my USB-6009, so I can't tell if it is actually doing anything, but it isn't crashing ...

 

Bob Schor

 

P.S. -- what you see, above, is a LabVIEW Snippet.  It looks like a picture, but if you have a (blank) Block Diagram open and drag this "picture" into it, it will become code due to NI Magic.  You can tell it's a Snippet by the little "2014" in the upper-right corner.

0 Kudos
Message 9 of 9
(4,390 Views)