From what I can see, all the videos I've created are there.

It's explained in the video. If you need help with Windows C programming, you will have to look elsewhere.

Can't trust the media these days.

It contains all declarations for the LabVIEW API.

Interfaced with arduino ?

I'm barely using LabVIEW anymore, and Bluetooth functionality seems to depend quite much on the device. Plus I get the impression that Bluetooth functions in LV are not very mature. The forums are you're best bet, sorry.

do you have file install labview 2016 x64 sir?

감사합니다.

What do you mean? You have to be more specific.

LabVIEW Tricks can I open any other applications from labview Front panel by just clicking one button like PDF file.

I think so. You can always run command line scripts, if nothing else.

I don't get this error. From where are you dropping it? What LabVIEW version are you using? I do get another error however. Seems I've missed to include "Error Base" and "Error Create" VIs in the build, which should generate some complaints if you install the package and drop from the toolbox.

I am using 2015 version. Also, there is problems with the DLL. When you drag and drop from the tool pallet it cannot find the KVstore.dll. I remember that I fixed that problem, but after that when the DLL is executed there is an error coming from this dll that I could not figure out how to solve.

Did you install the toolset from the included compiled package (.vip)? Or did you build your own version? Have you tried dropping the VIs from the included lvlib file?

Wow, I completely missed that. I presume you mean the "Browse Relationships" menu item. Still, it seems a bit clumsy to me, since you still need to know what you're looking for. Thanks for the tip.

+LabVIEW Tricks yes, exactly. And yes, it is clumsy, but sometimes when you have everything prepared with your probes inside the clones then its sometimes easier to have look there, instead of reopening the project, that is as well very clumsy! There was once a project in labview with which you were able to see all the clones running....

File -> New... -> Other Files -> XControl

In Other Files i don't see XControl. Where can I find it?

+ayman sarti I did solve the problem of that message but when i imported it to labview the same message box appear telling me that the dll i ve created is a 64 bit dll !!

+ayman sarti Hard to say off hand. So are you using 32 bit LabVIEW? Is your version of VS setting 64 bit by default?

+LabVIEW Tricks thank you for your answer.Well actually I am using a 2010 VS setting 32 bit by default and a 2014 64 bit Labview

+ayman sarti 64 bit LabVIEW should only accept 64 bit DLLs. Did you make it 64 bit and LabVIEW still complained?

+LM Yes that is exaclty what I did, and I didn't understand where this problem come from. The message that they gave me is : "The library selected is not valid for current platform. for example, you are running 64-bit Labview and the library might be a 32-bit library"

+Donald Kallberg No idea. My best guess is to create a C++ DLL that calls your VB DLL, then call the C++ DLL from LabVIEW. Just use 'extern "C"' for your C++ functions.

+LabVIEW Tricks ; I figured it out. you have to use the constructor node in conjunction with invoke node to use dlls that are dot net.

+Donald Kallberg Interesting. Which constructor did you select? I looked through the list, but did not see which one to choose.

+LabVIEW Tricks ; Since we are dealing with .net dll's, under connectivity select .net and you will find one constructor. Click on it. You will have to browse for your dll (it has to be located in the project folder). Then you can select the part of the dll you want. Note, I originally made my dll using modules. that didn't work. Labview said no constructors found. I stumbled around looking for explanations, I finally wrote my dll as a CLASS. It worked. I don't know why. Also, the framework version has to match. At this point you should be at the part where it generates the invoke node. The crucial part to understand next is that the ref of constructor node has to connect to the invoke node ref. It took me a long time before I found that out.

+Donald Kallberg Cool, nice trick.

+IThinkThat It's just a convenience. Controls will show their label by default. This way the label is automatically hidden.

+LabVIEW Tricks I got it, thanks a lot !

+Samuel Lozada Huitzil Great!

+Abofaliha I don't know.

Jack Trexler OK, good to know.

I had the same Issue but I tracked down the location of the files and once the paths are added to the property>VC++ Directories the DLL would build fine! Thanks for the awesome Tutorial! Help: stackoverflow.com/questions/15053337/fatal-error-lnk1104-cannot-open-file-kernel32-lib

Did you see the note I added about connecting the inputs of the "Run VI" method? For some inexplicable reason, the XControl doesn't work anymore if the inputs aren't connected.

5:47 here at the "wait until done" you should creat a constant and sit it as "false"

@@chaimaakremi2054 Thank you very much, I have the same problem and your advise works for me.

@chaimaakremi2054 thanks so much your advice helped me

Is the stop button inside the while loop?

LabVIEW Tricks yes. In oder to stop the while loop that is why it is inside.

Bibi Bibi Found it. The "Run VI" method requires the inputs to be wired. Right click on the connectors for "Wait Until Done" and "Auto Dispose Ref" and choose "Create" -> "Constant". Dunno if this is a new bug, haven't noticed it before.

LabVIEW Tricks Thank you. I just tried it. It is working, when both constants are false. :) Thank you for noticing it now. :)

Tinkering with xcontrols easily break them, and then you have to start over. If you like, can you PM me the error message?

LabVIEW Tricks I found the reason. When adding new event for the button, the wiring for Data in and Display state were not done. Any way I got new problem. In my program I have just a while loop and using start button causing that loop stop button does not work. But when running VI normally it works. Thanks alot dude. I was thinking to do it for about two weeks

juanarash1 Sorry for the late answer. Did you put the stop button inside the loop?

Unfortunately, there's no way that I know of to access the Run Continuously button. If you absolutely need this functionality, the best I can think of is to have the start button start a subvi asynchronously that monitors your main vi, and have it run your vi again when it goes idle. Then you need a stop button xcontrol that stops the subvi. That solution is obviously very costly and quite impractical.

thanks for reply.......... anyway i m getting extra marks for my project from this start button thanks alot dude.. god bless u................. :) if it is possible den please upload video for continuous run button.., m also thinking on dat.. if i will get some solution den i will tell u.. keep watching all of yours video ... really nice work..

Divyang Patel Thank you! I don't know how useful a cont. run tutorial will be, plus there are a bunch of other tutorials I want to make first. We'll have to see. If you find something out, please tell.