Posting block diagram in reply

I know how to attach a snippet or vi to my posting. I'm just wondering how do you post a block diagram .jpg image to your posting so others can see it while reading (so that it is a part of your posting along with your text). I have seen others do it. Thanks.
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
Solved!
Go to Solution.

That makes sense about the image gallery. I will give the code capture a try as well. I have noticed changes to my code when using snippets (It's almost like LabView knows more than me). Thanks a bunch for explaining that.
One more question, and sorry for being a nube:
How do I highlight an individuals comment from another post in my own posting? Thanks again.
Edit:
Never mind. I see the quote button.
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home

Similar Messages

Creative Way to Post Front/Block Diagram in Word Document

Hello,
Does anyone have a creative way to post Front/Block Diagram in Word Document in the same calibre as if I used SNAPIT.
Thanks in advance.

You can use the report generation VIs (you should have a palette of them) to do this. If you want another way, have a look at the VI posted here.
Try to take over the world!

Disable block in Vivado block diagram design

I have several blocks in my design which I would like to disable (not delete) from the design so that my build time is faster. Is there an easy way to do this from the GUI or by editing the hdl that doesn't break the block diagram view? Thanks

Hi ,
Use the following TCL command:
set_property is_enabled false [get_files <project_path>/bd/design_2/design_2.bd]
In Vivado GUI. Select the block in File hierarchy and right click to Select Disable file as shown below:
--Syed
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

DISPLAY NAME, BLOCK DIAGRAM

I am new to LabView and our teacher has given us a very small assignment in which we have to create a program that displays a name that I have input. I am also required to show him the block diagram.
Any help plz?

Given that this is essentially the "Hello World" program written in LabVIEW I suggest you try a few things on your own first. I doubt anyone here will post the code since it is a homework assignment and it is a very easy one at that. Take a look at the examples that ship with LabVIEW.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Bug: Front Panel objects relative position change when placing merge VI onto Block Diagram

I've posted a bug report on LAVA, here:
http://forums.lavag.org/Front-Panel-objects-relative-position-change-when-placing-merge-VI-onto-Bloc...
If someone at NI can reproduce, can I please get a CAR #?
Thanks,
-Jim
Solved!
Go to Solution.

Donovan B wrote:
Hi Jim,
After my previous post, I also saw this behavior, so I decided to do another test. If there are no decorations in the VI set to “Merge VI” (“Place VI Contents” for LabVIEW 8.5 and later) the controls and indicators are still not selected when dropping the VI from the Functions palette. I checked this behavior back to LabVIEW 7.1 and it is consistent throughout that controls and indicators are not selected. (Consequently, so is the fact that when decorations are present they don’t maintain the relative position).
I am not sure if this would be better suited as a CAR or product suggestion since it has been this way that long, but it does not appear to be related to the fact that decorations are present in the Merge VI. It does seem strange that the decorations are selected though. Looks like the best way to work around this is to drop the VI from the Controls palette. Hopefully, it’s not too much of a hassle.
Hi Donovan,
Thanks for checking in.
> I checked this behavior back to LabVIEW 7.1 and it
is consistent throughout that controls and indicators are not
selected. (Consequently, so is the fact that when decorations are
present they don’t maintain the relative position).
This just means that not many people use this feature. However, now that VIPM Professional makes it so easy to edit the palettes, I'm sure that others will start complaining that this doesn't work as they expect.
> I am not sure if this would be better suited as a CAR or product suggestion
since it has been this way that long, but it does not appear to be
related to the fact that decorations are present in the Merge VI.
Just look up the functional specifications for this feature and see if all objects are supposed to be selected.
But seriously, is there a reason that only the FP decorations are selected? Surely this would be documented somewhere, if there was a good reason for this current (IMO, buggy) behavior.
> It
does seem strange that the decorations are selected though. Looks like
the best way to work around this is to drop the VI from the Controls
palette. Hopefully, it’s not too much of a hassle.
That's not a reasonably work-around, IMO. It doesn't make sense to drop Block Diagram components onto the Front Panel. For example, this bug affects the JKI State Machine. It doesn't make sense to drop a State Machine onto the Front Panel.
So, I'd file it as a CAR/bug, and then wait to see how LV R&D feels about it. If they can find some valid reason for why Controls and Indicators shouldn't be selected, then that's fine (and hopefully someone will explain it to me).
Thanks,
-Jim

System exec subvi. can't access block diagram for positioning

OK I am back!
my first issue is that for some reason I can no longer attach files here for you all to see...
Second and more to the point is how can I tell the system exec.vi to open where I want it too when access to the block diagram is password protected and I can't seem to make any property nodes for the vi either.
I am using this vi to call the OSK (on screen keyboard) for touch screen panel.
I would have sample to show but see number one...
Solved!
Go to Solution.

Thanks Dennis - again
after posting i made an executible of the project as it stood and put it on my touch panel.
I found that it called it OK and I could just moveit around and resize it as i wanted, just once. then whenever i called up the OSK it was where i left it and the same size.
While this may be a small pain to the end user, I think i will keep it like that for now and just let whoever they are deal with it as part of the initial program protocol.
but what about not being able to add attachments here? do I need an adult?

Default check on the 'Posting block' check box in the Physical Inventory

I am looking for a default check on the 'Posting block' check box in the Physical Inventory document for T-code MI01 or MI31. Can anyone help in this?

Thanks for your reply. Can you send me the detail process how to do it through Transaction Variant.
Regards,
Tt

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.

Posting block in Inventory Mgmt

Hi guys,
what is this posting block which comes
up in material movement recompilation
run, elaboration is of need.
Thanks,
Due points will be assigned

Hello ViJaY,
I read Roberto's reply and made some sense,
I.e. While filling the setup tables there are chances of getting duplicate records into it as the other LO applications update the data while running the setup.
To avoid this, we use the Posting block concept, here u will give the From and To dates so only the records related will be filled in the setup tables. Till this job completes no other postings will be allowed.
Also, Inventory links with many applications like MM / SD / PP, etc. Inorder to avoid the updation from other applications we follow the concept 'Posting block'.
Roberto, Am I correct ? could u give us more info ?!
Best Regards....
Sankar Kumar
+91 98403 47141

DAQ Assist to block diagram code

Hi,
I am fairly new to NI Signal Express.
I am using the NI 9214 for thermocouples and I have sucessfully communicated with the NI using DAQ assistant.
It generated the code below.
How can i have more control of my VI?
I want to be able to turn on and off my CHANNELS
i want to have graphs, etc.
can i expland the DAQ ASSISTANT ICON to something with more control?
thanks in advance.
Solved!
Go to Solution.
Attachments:
TCs.vi ‏102 KB

Oh, you already opened it.
Well we don't know what you want to do. Since you have a real VI to work with YOU need to decide how you want to enhance it. I would start with changing some of the constants on the block diagrams to controls. You can drop a chart on your front panel and wire DAQ out data right to it. If you get stuck, be specific about your goals and post your newly opened VI.
EDIT: BTW, if you want more help I suggest you use File > Save for Previous Version... and make it a 2013 or 2012. Many of us who could help out still haven't upgraded to 2014. I saw that you wanted channel control and graphs but I can't open your code.
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Terminal images for arrays on block diagram

I had always know that the thickness of the wire is representative of the size of the array on the block diagram (Thin wire, scalar, thicker wires, larger dimension arrays)
I never noticed before that the terminal on the block diagram contained the [ ] symbols to indicate it is an array. But also, the larger the dimension of the array, the thicker the brackets are, up to about 5-D. (Probably because I rarely need a 3-D array, and large than isn't any practical, logical reason for a 4-D or larger array.)
However, looking at the image of the terminal, the shaded area containing the outgoing or incoming triangle actually obscures one bracket or the other.
While I wouldn't want the terminal to get any larger (which is why I don't like the icon view, it is way too large), it seems like the terminal should show both the opening and closing brackets to indicate an array rather than obscuring one.
Any comments?
Message Edited by Ravens Fan on 08-22-2009 12:59 AM
Attachments:
Example_VI_BD.png ‏3 KB

Definitely keep the arrows. They are what tell me the direction of the terminals.
As I was saying in another post, there is nothing intuitive about the thick border/thin border differences to tell whether the terminal is a source or sink. I like that they are a bit different, but if you put them side by side with no wires and no arrows, I couldn't tell you which was which.
As for array size, as Christian says, if I want to know the type/dimensions of the array, I'll use context help. I just thought it was interesting (and I had never noticed it before) that the array size was encoded in the image as well.
I myself wouldn't mind if the terminal grew 2 or 4 pixels wider, but I can completely understand how it would bother a lot of people.
I think in the current image, too much is obscured by the arrow and its background, even for the scalar type. Actually, why is there a light background behind the arrow at all. That is the real source of the problem. Eliminate the background, and move the arrow over to the edge, and you can see everything without extra shading and without causing the terminal to grow.
See below:
1. Terminal size maintained.
2. Direction arrow maintained, just slightly moved.
3. Goofy shaded background removed.
Message Edited by Ravens Fan on 08-22-2009 09:48 PM
Attachments:
terminals3.png ‏5 KB

Why does my block diagram change when I copy my code to another system?

I am doing development work on a laptop on Win XP and using LabVIEW 2009 with service pack 1. When I copy the code to the target system, my block diagrams are changed and no longer fit the screen. Much of the code is spread out, mainly down. The target system is running Windows 7 and also has LabVIEW 2009, SP 1.
I notice that any constants that are clusters are expanded when copying the code to the other system. I've gone in and turned off the autosizing for these clusters but they are still expanded. I like to shrink them to a small size for saving space.
I've gone through and manually re-adjusted the block diagram on the target system, but when I copy it back to my development laptop, the same thing happens again. This is not an acceptable way to develop code and it has caused a real problem to proceed. I'm contracting this work and must develop this code offsite. Can anyone please help me with this? I can't keep restructuring my block diagrams every time I copy the code from one system to the other.

Windows XP used Tahoma size 8 as its basic system font. When MS came up with Vista, they changed it to Segoe size 9. I'm not sure what Win 7 is, but I think it is the same as Vista. That font change, and certainly font size change seems to be the underlying cause for block diagrams changing their appearance. (And for front panel controls and labels as well.)
LV seems to use the Windows system font as its default font. Interestingly, it seems like the font sizes in LV are something like size 12, 13, 14, 15. I think a size 9 is equivalent to a size 15, but I'm not sure about the comparisons. (Check out this thread.)
There are a few things you can do to try to make one system look more like the other.
1. Go into the Windows screen settings. In Vista, right click desktop, Personalize. Window color and appearance. Open classic appearance properties. Try changing the color scheme from Windows Aero, to something like Windows Classic or Windows standard. They both use Tahoma 8.
2. Or same as Step 1, but go further into Advanced button. Pick on any option that uses font such as Menu, Message Box, Active or Inactive Title Bar and change the font there. I'm not sure which of the items that has a font setting is the key one.
3. LV uses 3 fonts called Application, System, and Dialog. I think each of those map to one of those Windows options, but I'm not sure which goes to which.
4. In LV, Tools/Options/Environment has a subsection called Fonts. Those 3 basic LV fonts are selectable there. There is also a checkbox for me which is checked and says to use default. If you uncheck that checkbox, a Font Style button becomes enabled. You go in there and you can choose fonts and sizes. And the Application, System, and Dialog fonts as well as all the usual fonts names (Arial, MS Sans Serif, Greek, ....) are selectable along with fonts sizes. Play around in there. The whole section is very confusing, and I have no idea how it works. I recommend going to this idea A better way to specify (default) fonts and putting in a vote. Also this idea, Fix font behavior between windows versions, platforms & executables, deserves some love.
5. Some of these settings can also show up in your LabVIEW.ini file.
FPFont = "0" 15
BDFont = "0" 13 (I think the "0" means app font, "1" means system font, and "2" means dialog font)
Also,
appFont="Tahoma" 13
systemFont="Tahoma" 13
dialogFont="Tahoma" 13
(And if necessary, put these in your built application's .ini file)
As you can see, there are a lot of different things going on and they also seem to conflict with each other. I starting stumbling on the block diagram issue between working on my app on XP at work and on my Vista machine at home about 6 months ago. I think my problem actually started with the front panel when I was trying to align labels, and use some arrow head decals on boolean buttons. I think I did the customization of buttons in a couple different ways (because I did some, came back later to do others, and couldn't remember exactly how I did it.) As a result some decals looked different than others when I changed machines. And I swear going from XP to Vista, or Vista to XP the problem got both worse ways rather than let's say larger one way, and smaller the other way.
Replying to your message is about as much to me trying to combine all the pieces of knowledge I've stumbled across over the past months and year as it is for trying to help you. Hopefully, this information gives you some places you can look at and play with. (I bet #1, would be a quick, easy way to solve your immediate problem, but I haven't really tried it myself to be sure.)
I hope someone from NI who has a better understanding than me about these font issues could jump in and correct any mistakes I made, or add anything I might have left out. What we really need is some sort of "nugget" or National Instruments white paper that really explains all of this in ways we can use rather than us stumbling around in the dark doing things trial and error to figure it out. Generally, any changes to the .ini files require you to shutdown LV and restart it to take effect which can take a couple minutes. And considering all the various combinations of things that can be done above, your talking about dozens of possible restarts, and sending .vi's between two different PC's with two different operating systems, before figuring these things out.

Block diagrams messed up: Win 7 or LabVIEW 1012?

Hi, Everybody --
We just got a new computer for the lab here, and I held off on installing LabVIEW 2012 until after the new machine was installed. All of our computers have been running XP until the new one arrived; it's running Windows 7, and it now has LabVIEW 2012 loaded.
The first time I opened a VI and looked at its block diagram on the new computer, I was floored by how lousy it looked. Icons wereoverlapping, constants and controls were misaligned, the font sizes had changed, and, in general, the whole diagram was a mess. I though it just might have been that one, so I opened others and they all look like they were put together by 5-year olds. (No, I can't drink at work.)
Is this a Windows 7 "feature" or something new with LabVIEW 2012? I haven't had a chance to install or work with 2012 on the remaining XP computer, so I can't do any comparisons here yet.
I have a LOT of VIs written now, and the thought of having to redo all of them so they're readable is giving me the bad kind of palpitations. Is there some way to fix this problem without slogging in and doing all of the realigning, etc., manually?
Thanks a million for your time...
Mark
Solved!
Go to Solution.

Hey, RavensFan!
Thanks for the quick reply. I was afraid it was something like that, but with nothing to compare it to, it was more of a shot-in-the-dark guess.
I've changed a bunch of my VIs already, but I'm thinking that I'll mess with the .ini file and see if it'll reset them, too.
I don't know if you remember, but you wrote to me last year and said that, if the Ravens went 15-1 and lost only to the Texans, that would be fine with you, as long as they got into the playoffs again. Well, you were just slightly off with the season record, but it turns out that you were aiming pretty modestly about the playoffs! Congrats, etc.!
They've been making a big stink here in Houston these days about Ed Reed's not being honest about his injury situation. Nothing is ever easy...
Thanks again for the quick reply (as usual!) --
Mark

I am trying to create an executable vi that will call out another vi and show its front panel in the executable. When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

I am trying to create an executable vi that will call out another vi and show its front panel in the executable. When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

Well the most common way is to enclude the vi's in the build spec either directly in the dependancies that the App builder automatically generates OR by declaring them in the build spec as "additional enclusions" (like you must do for dynamic vi calls in your app.
I have heard rummors about My.app Stuff.vi in a nugget Intaris posted- and I've wanted to dig deaper into Intaris' claims- but have not tried it myself.
If you go down the stuff.vi route Keep us curious guys posted
Jeff

Image of the front panel and block diagram

Hi,
I need to get some info from the block diagram but I don't have labview in my computer. can some one please open it and post a picture of both front panel and block diagram.
It may not open properly, but that is okay.
Thanks,
Sujay.

Here you go

Posting block diagram in reply

Similar Messages

Maybe you are looking for