What VIs do not have block diagram?

Hi,
I'm studying for CLAD and theres a question in the CLAD Topics details about what VI do not have block diagram?. I read in help that polymorphic VIs don´t have Diagram Block or Front Panel ( Labview help / Creating Sub_VIs). However, I can see that if I make double click in a polymorphic VI, for example, Read Key.vi or DAQmx Timing.vi they have front panel, moreover, they have a diagram block, so I am missing about that......
I know too that VI express do no have diagram block or front panel, the have a configure window. If I select open the front panel option, the VI express changes to Sub-VI and I have access to front panel or block diagram. So I think VIs express are those VIs that do not have diagram block. Am I right?
Anyway, there a doc or paper that give me information about this topic?
Thanks for the anwsers....
Solved!
Go to Solution.

The fact that controls have the .ctl extension does not mean that they are not a VI. You could rename a .ctl file to have a .vi or .caribbean extension and it would still work the same.
LabVIEW considers them to be VIs and displays then in the All VIs in Memory property and other places.
Incidentally, looking at the help for the VI Type property shows the following:
Indicates the type of VI. Invalid VI type, Standard VI, Control VI, Global VI, Polymorphic VI, Configuration VI, SubSystem, Facade VI, Method VI. LabVIEW returns the invalid VI type value for invalid VI references.
LabVIEW returns the SubSystem value for subVIs for the LabVIEW Control Design and Simulation Module that you can place only on a simulation diagram.
The Configuration VI type is not supported.
The last two are both used for XControls and both have diagrams.
Try to take over the world!

Similar Messages

Not seeing block diagram when opening vi

Hi,
This is trivial but frustrating. When I open a vi I see the front panel, and then have to press ctrl E to see the block diagram.
Can anyone tell me if there a way of opening the vi and seeing both the front panel and block diagram immediately ?
Many thanks,
Solved!
Go to Solution.

Press control when you double click the sub-vi and that will open both the FP with the diagram on top. On windoze
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?

When I CLICK on a link on a web page, firefox dos lot load the page in a new window. All other browsers load the page under the link. I do not have "Block poups enabled".

When I navigate to a web page that has a link, such as the link to a data sheet and click the link (usually an insert page), firefox does nothing.

Does the new window have a media player in it or use the Flash plugin for any other purposes? If so, it could be the protected mode bug described in this thread: [https://support.mozilla.org/questions/955659 Opening New Windows and Shockwave Flash]. There are some workarounds listed there.
Let us know whether that helps.

What does do not have enough access priviledges means for itunes and cannot be saved ?

Message keeps coming up about access priviledges and itunes cannot be saved what does this mean please?

Hello deborahjael,
Thanks for using Apple Support Communities.
To troubleshoot this error message in iTunes please follow the directions in the link below.
Trouble adding music to iTunes library or importing audio CD
http://support.apple.com/kb/ts1387
Take care,
Alex H.

Saved block diagram wont open

I am a new labview user so this may be obvious, but I have a problem nonetheless:
I have drawn a simple program and saved it but when I open it again, only the front panel opens and not the block diagram as well, which I wish to edit. I am openning labview on the same machine, same version etc. what do I need to do to get this working properly?
Thanks to anyone for their help

Hi Dougonlabview,
Just press Ctrl+E. This will bring you to the diagram. Pressing Ctrl+E again will bring the front panel back on top.
Regards,
Mathieu Steiner, Test System Engineer, Safran Engineering
CLD, ISTQB

Integrating fpga module with standard block diagram

Hi all,
I'm doing an FTIR multitouch table, and I would like to be able to track blobs using LabVIEW then transfer this data to a Spartan 3e FPGA. I have seen the tutorials on how to program the Spartan 3e and have direct communication with LabVIEW, but can I also run image processing via USB-IMAQ VIs in the same block diagram? Basically I need to get coordinate data from the blobs (touch points on the screen) and transfer this data to an FPGA which will act as a primitive graphics card. Any ideas are appreciated.
Thanks...

Zzzyzx,
Hello! You should be able to use your Host VI to talk to Both the FPGA and the USB-IMAQ devices. You would just have two loops running at the same time, one for each device's communication. To pass data between the loops (from the vision to the FPGA) you could use a Consumer Producer Architecture.
I assume you are referring to these tutorials?
Using the Xilinx Spartan 3E XUP Hardware with LabVIEW FPGA
Using LabVIEW FPGA with the Xilinx SPARTAN-3E XUP Video Tutorial
LabVIEW FPGA Module Training for Xilinx Spartan 3E XUP Hardware
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Is Block Diagram Open

Is there a way to tell if the Block Diagram is open when a VI is started? I have a subVI that is set to modal when open. When trouble-shooting, if I run my application, but forget to disable modal for the subVI it causes the system to lock up.
It would be nice if I could set the property of the VI to not be modal if the block diagram was open.
Any suggestions?
Solved!
Go to Solution.

I would attempt this by doing several things:
1) Go to the VI Properties>Window Appearance and click on the Customize button. From there uncheck the "show front panel when called" box.
2) When the VI starts, read the VI Property "Front Panel Window.State" - this will tell you if the window is already openned (ie if the window is openned the window state will be "standard", "Maximized" or "Minimized"). Note: this is the visibility of the front panel, not the block diagram
3a) If the VI is not already opened, set the "Front Panel Window.Behaviour" property to modal and then open the front panel using the VI Invoke Node of "Front Panel.Open". This is basically mimicking the behaviour you describe right now.
3b) If the VI is already opened, set the behaviour property to default or Floating to allow you to click other windows.
4) When finished, if the VI was not already openned, manually close it using the Front Panel.Close invoke node (if it was already openned, leave it openned)
I've attached a screen shot of this kind of thing. I hope this helps,
Shaun
Attachments:
Reading and Changing Front Panel Behaviour.png ‏39 KB

How do I fix the workspace error "because the file is locked, you do not have necessary access permissions..."?

I keep getting the error message "Could not apply the workspace because the file is locked, you do not have necessary access permissions, or another program is using the file. ..." when I try to open a workspace. Any ideas how to fix the permissions and what file does not have permissions. I am on a Mac.

See here:
CS5 "Locked"

Is it possible to build exe with vis that have striped block diagrams?

We can tell that an entity has stolen our code and are using them in their .exe file.
We used to distribute our program as a light exe layer that dynamically loads some source code distribution vis (block diagram striped) off disk and runs them.
What we don't know is whether they actually got our in house source code, or if they are somehow taking the distributed vi's and compiling them into their exe.
So the question is: Is it possible to take vis compiled for a 'source distribution' with the block diagrams removed (but front panels not removed) and compile them into an executable?

It's actually quite possible to use a source distribution VI for a new app. You need to select the "Do not disconnect type definitions or remove unreferenced
members" option in the "Additional Exclusions" page.
I've attached an example on how this can be done. Untitled Project 1 would be your project, which has a build target of your app, along with the source distribution for a VI with the block diagram stripped. Untitled Project 2 would be your competitor's project, which is a VI that uses your subVI directly and builds a separate application. As you can see, I can successfully build an application using your code.
Attachments:
source dist ex.zip ‏76 KB

Hello, I have a problem, my computer is interrupted very often CAN I changed Maveric when working and 15 times a day is very disturbing and nustiu what I do is not only blocking and restarts

hello,
I have a problem, my computer is interrupted very often CAN I changed Maveric when working and 15 times a day is very disturbing and nustiu what I do is not only blocking and restarts

If you are getting Kernel Panics, this article (available in many languages) will explain how to find the reports. You can post the latest one here for Readers to help you:
How to Log a Kernel Panic

Blocks - to have on the block diagram, but not to execute

Hello,
In standard programm languages there are possibilities to mark some lines in code not to execute them (for example, if we have written some code and want to use keep it in programm, but don't need to execute it right now)
e. g.
Does LabView allow to mark several blocks on block diagram, to have them on it, but not to execute?
Thank you in advance.
Anna

Hi Anna,
in newer LabView versions you can disable parts of a block diagram by using the "Disable" structure. This will work even with unfinished, buggy code.
In older versions (pre-8) you can use a case structure to put the "not to be executed"-code in the not-executed case - but here the code has to be executable...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel?

How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel? On the Front Panel I am making a complex control that consists of a Slider and a Numerical Input box. Both Controls display the same information and either can be used for Input. When one changs, the other is made to display the same value.
But I only want the Slider to display the Label on the Front Panel, to avoid confusion. On the Block Diagram however, I want both controls to display their Labels so that I know what they are. How do I display the Label for a Control on the Block diagram, but not display its Label on the Front Panel?

No. The Label Visible property is separate for the front panel control label and the block diagram terminal label.
How did you start out with the block diagram's label not being visible? Whenever I drop a control or indicator, the label is always visible on both the FP and BD by default. Maybe there is a LabVIEW option that causes new controls/indicators not to have their labels visible by default, but I have yet to find it. I don't think an item should ever be dropped without the label visible, good LabVIEW coding practice demands that the labels for control terminals on the block diagram be visible so that you know what control or indicator a wire is going to.
That being said, I have seen a lot of VI's posted where the label for the terminal on the BD is not shown (against good programming practice.) I've gone to the BD and right clicked to show the label. Sometimes, the people have an empty label (which will turn off the visibility for both the FP and BD) and I'm forced to add some text of my own into the label so I can figure out what their code is doing. When I add some text to the label, at that time, I find both the BD and FP labels become visible.
Are you dealing with controls that have empty labels to start?
Good programming practices:
1. Always have a name for all of your controls, never use and empty label by deleting the text in the label.
2. Make the labels unique. For example, don't have two controls both called Stop. How do you know quickly know which terminal relates to which control?
3. Always show the labels on the block diagram, so you know the function of a control's terminal. If you want to hide the label on the FP, that's okay.
4. If you want a different label to appear on the FP than whatever you actually called the control, then use the caption. You can hide the label and show the caption. This is useful if you need to programmatically change what the "label" is on the front panel such if you are making an application that needs to change its user interface such as for a foreign language.

What is the best way to keep the block diagram/ front panel clean?

Hello,
I am relatively new to Labview so I'm not able to tell if I'm overcomplicating my programs or making my block diagram too cluttered. I was wondering if there were some ways to tell whether I could simplify my programming just by looking at it (perhaps only experience helps for these things) ?
I have attached my VI here. Currently, it has the capability to monitor the voltage and current from two motors. On display, you can see a indicator with the voltage and current values and there are charts toward the bottom that can display waveforms from different motors with a drop down menu.
The front panel is rather clean in my novice opinion, but the block diagram seems messy to me, just at first glance. I foresee a problem occuring in the future however. In the future, I will have to scale the VI to monitor 50 motors. All the programming will be the same as the one I have now, except it will have 50 indicators and unfortunately 50 times pretty much everything. I would like to avoid this, but I'm not sure how I could.
I am using a USB 6009. I am using its four differential inputs to monitor the voltage and current of two motors. In the future, I will be getting more DAQ units (25 total because 2 motors can be monitored for each DAQ). The new DAQs will help will help with more resource space, but I think complicate things with the additional potential of 24 more DAQ Assistants (as used in my code).
Thanks for any help you might be able to provide!

It usually is mainly experience that will teach you the best methods to make your code look pretty. I don't know anyone who is proud of their first from-scratch application. There are a few resources out there to help with best practices, like this group on ni.com, but you'll learn the most from your own development.
Your front panel looks great. FPs in general are really up to you. You can make it look as ugly or pretty as you want. When you have some duplicate controls and indicator groups, you should utilize clusters and arrays to simplify. You could use a little bit of cleanup in that regard, but not much. Also, personally, I hate reading red text unless it's a warning of some sort.
Your block diagram could use some cleanup in a modularity sense. You have a lot of repeated code, which you could consolidate in to a subVI that is used in multiple locations, or in a For loop. A general rule of thumb is to keep your block diagram within a single monitor. You shouldn't have to scroll. Your application is pretty simple, so it's hard to mess it up
Here are some specifics about your block diagram:
Right click your terminals on the block diagram and uncheck "View As Icon". You're welcome.
Duplicate operations on each waveform "(x*2-4)/16": create subVI and/or run the waveforms through a For loop.
You do a lot of 2-element arrays and then indexing. Just replace those with a Select node based on the numeric.
All of your code is running every time, including your property nodes at the bottom, which is unnecessary. As you learn LabVIEW architectures, you will learn how to bypass this with initialization and exiting code, but for now you should put a case structure around those for only when the motor numbers change.
I'm not sure how you're timing your main loop, but you should put a delay in there because you don't need the DAQmx node to be pulling as fast as your CPU will allow.
There are free intro videos you can watch to learn what NI would suggest in terms of coding and teach you some of the basic features and such. Here's a three hour course, and here's a six hour course.

'Control terminals on connector pane not on top level block diagram.' comment on CLD report

Hello All
Could anybody enlighten me please , what does that comment mean on CLD report
'Control terminals on connector pane not on top level block diagram.
Does it mean that some terminals are hidden within some case structures and not showing on block diagram without going into case structures or by 'top level block diagram' it means
main.vi and controls on main.vi must also be connected to its connector pane?
Thank you
K.Waris
Solved!
Go to Solution.

For one thing it means that they run VI analyzer on your VIs since that is a verbatim warning that you receive. It simply means a terminal which is wired to the ConPane is not on the top level diagram, ie. inside a case structure.
As to why it is often not a good idea to do this read this classic thread:
http://forums.ni.com/t5/LabVIEW/case-structure-parameter-efficiency/m-p/382516#M191622

My ipad is blocked after update asking me to enter a code that I do not have

Please I need some help, I was proposed today to update my ipad and uknowingly I just clicked on to launch the update. Now it's asking me to enter a code to install the update but I do not have nor received any code for that, I tried to enter my apple account password just to see if can work but without success. Now it's completely blocked on this only display and if I try to enter any code again it deactivate my ipad. I do not know what to do. Please help! Thanks a lot for your kind attention.

You were most likely asked to create a code. That passcode is then used to unlock the device. This is turned on by the installation of iOS 7 as a security measure. Once the installation completes you can turn this off if you want but you must have the passcode to do that.
If your iPad is now locked you will have to connect to iTunes on your computer to restore the device. Be sure to install the latest version of iTunes which is 11.1 or greater. When restoring you will most like have to enter the Apple ID and password that was used previously on the device.

What VIs do not have block diagram?

Similar Messages

Maybe you are looking for