Digital output DAQ Error

[MAnees]

Hi, 
I am a new labview user. I am trying to send boolean output to DAQ (USB6001) I am getting an error and dont know why it is occuring

Plz see the image attached for VI and error.

(I am able to read data from the same DAQ)

Thanks 

[GerdW]

Hi MAnees,

as you are a new LabVIEW user (which is also recognizable by the way you write the word "LabVIEW") I recommend to go through the free online beginner courses offered by NI.

And I recommend to attach the real VI not just an image of a VI blockdiagram!

One more note: when you use ExpressVIs like the DAQAssistent all the relevant settings are hidden from direct view. Because of that we NEED to be able to check your VI. When you also have made DAQmx settings with MAX and use those settings in the DAQAssistent you also need to supply information on those MAX settings…

[MAnees]

Thanks for the reply. I have gone through the tutorials. The error just says VI non executable. Plz see the attached file. 

[apok]

have you tried looking in help/find examples/hardware input and output/DAQmx/digital output?

[Bob_Schor]

Do you know how to use MAX?  Have you tried using MAX with your device (which I assume is called Dev1)?  Can you toggle Port0/Line0 of its Digital Output line?  [I assume that you know that's how your Express VI is configured].

On my PC, which has a simulated USB-6009 as Dev1, this code runs just fine.  Of course, I have nothing attached to Port0/Line0 so I cannot know if turning the Light Control Boolean on or off actually does anything, but the program runs without error ...

Bob Schor

[MAnees]

apok 

I have looked at them as well. Whwnever I pull an example in labview, it is showing same issue with the digital output. When I open the DAQ block itself and run it, it runs fine and LED turns on (image attached for clarity), but the VI idoesnot run. The error is "The subVI is not executable. You must fix all errors in the subVI before this VI can run." and highlights the DAQ block which has no errors. I gone through this link as well

https://forums.ni.com/t5/LabVIEW/Getting-a-subVI-is-not-executable-error-but-the-subVI-has-no/td-p/1...

but coudnt get what is going on. 

[MAnees]

Hi Bob, 

Thanks for reply, what do u mean by using MAX? 

Whwnever I pull an example in labview, it is showing same issue with the digital output. When I open the DAQ block itself and run it, it runs fine and LED turns on (image attached for clarity), but the VI idoesnot run and gives error is "The subVI is not executable. You must fix all errors in the subVI before this VI can run." and highlights the DAQ block and DAQ block has no errors. I gone through this link as well

https://forums.ni.com/t5/LabVIEW/Getting-a-subVI-is-not-executable-error-but-the-subVI-has-no/td-p/1...

but coudnt get what is going on. 

[Bob_Schor]

---

@MAnees wrote:

Thanks for reply, what do u mean by using MAX?  

---

Boy, you really are a LabVIEW neophyte.  MAX is the Measurement and Automation eXplorer that is installed with LabVIEW drivers.  When it is installed, it shows up on the desktop looking like a stylized "N", something like this:

Note that my desktop background is the dark blue color seen in the background here.

If you have this icon on your desktop, double-click it to get MAX started.  You can use it to explore the DAQ hardware you are trying to program.

If you do not see this icon, then you probably are missing the NI Device Drivers which are required in order for your LabVIEW code to connect with the device you are trying to program.

So my previous question can be changed slightly:  Do you have a MAX icon on your desktop?

Bob Schor

[MAnees]

Bob thanks for replying. Yes MAX is installed and i am able to acquire data as well. The DAQ block also send output if i open it and run it (LEDs do turn on off) but the VI doesnot run. I have attached my VI in the thread, it is very simple one. I am not able to identify where the problem is

[GerdW]

Hi MAnees,

but the VI does not run.

You need to start your VI to have it run - or what is the problem?

Your error description is rather vague, so can you provide more details? Any error outputs from your DAQ Assistent?