10-22-2013 03:27 PM
Hello all
While reading a sample project a block stopped me. I couldnt figure out what is it.. once I click on it (offline) it opens a subVi, while runing the labview it is clear that it will automatically call that subVI. My info is that to call a subVi from the main Vi you will need to use a static Vi reference. May someone help me figure out what is this block about ?
I have attached the picture of it and a VI containing it as well.. Just open the block diagram of the file : "Caller.vi" .. The subVI which is linked to this block is attached as well : "Config .."
I like to know What is this block name, how is it linked to that subVI and how the Labview automatically call it. .. I really appriciate any suggestions.
Thanks in advance
Regards
Solved! Go to Solution.
10-23-2013 02:48 AM
Right click the subVI and select Disable Database Access. That should hide it. It has been a long time since I looked at this, but if I remember correctly, it should log the info of the VI as you run it. The help should have more info.
10-23-2013 08:28 AM
The thing is that I want to learn how to use, how to define which subVI it should call. The ctrl+H doesnt give me any info on this block.
10-23-2013 09:40 AM
It's not something that calls a VI. It's something that you enable on a subVI call to do something (this indicates it loads data which was logged on a previous run of the VI instead of running it. As you can see, that article is from 1998 and I doubt that many people are even aware of this feature, if it even still works properly. It was probably enabled by accident). You toggle it from the context menu of the subVI call, just like I described in the previous reply.
10-23-2013 11:00 AM
Hi again
What article are you talking about ? 1998 ?
10-23-2013 11:24 AM - last edited on 12-02-2024 12:05 PM by Content Cleaner
There was a link in that reply - http://digital.ni.com/public.nsf/allkb/C61F1FD208E8C3E2862565A30075580E
10-23-2013 06:19 PM - last edited on 12-02-2024 12:05 PM by Content Cleaner
Hi again,
Can you check this project and help figuring out how the main VI call the subVI. I thought it was that block I attached to this question.. May I was wornge. After I read the 1998 article I undrstood that dataloging has nothing to do with calling a subVI.. So still cant figure out what is the criteria of call the subVIs with out the using of the "static reference" ..
I tried to start with a blanc project and use the block.. It is already programmed to be linked to the subVI ... How to change the SUBVI for the same block ?
This is the link to the project containing the Block and other similar function blocks:
Thanks in advance !
10-23-2013 06:33 PM - last edited on 12-02-2024 12:05 PM by Content Cleaner
@Huthaifa85 wrote:
This is the link to the project containing the Block and other similar function blocks:
This link does not contain any downloadable code. Please explain.
To call a subVI, you simply place it on the diagram of the calling VI and it will execute once dataflow allows it. If you need more specific advice, you need to ask a more specific question.
(... and please don't maximize all front panels and diagrams to the screen as you did in your first attachment. Very annoying!)
10-23-2013 06:53 PM - last edited on 12-02-2024 12:06 PM by Content Cleaner
Hi
Thanks for pointing this out..
This link cotains it :
https://forums.ni.com/t5/LabVIEW/Neural-Network-in-LabVIEW/td-p/333920
Check the file aNETka_ver_1-0.zip 1223 KB which is attached in the second reply...
I just like to know the technique he used to call subVI and how the data log was transfered as well ..
Thanks in advance !
10-23-2013 11:11 PM - edited 10-23-2013 11:12 PM
(You linked to the 5.1 version which is too old to open. The 8.5 version can be found here.)
The subVI is called in frame 0 of the first sequence structure, nothing magic about it.
The subVI is configured to open the front panel when called and close it afterwards. It is also configured to be modal and hiding the menu, titlebar, etc.
So, what is your question??? If uderstanding this poses a problem for you, I recommend to continue with a few LabVIEW beginners tutorials.