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!

Similar Messages

  • How to import an assignment block into a word document

    hi all,
              how to import an assignment block into a word document ,actually we an option called import to Excel,
            but i don't know make it for Word document.....
    Regards
    Sunil Kumar SA

    Use the Media Browser in Word, which you can access via the Ribbon (Insert -> Picture) or via the Insert menu.
    Regards
    TD

  • 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.

  • Right way to insert graph or chart from Word document?

    I have a content given in word format. I place the document to indesign using Place command. All content is put except the graph / chart.
    That graph/chart is linked to source data in excel that I don't have access to.
    I manually copy paste from word it resulted as non editable raster image.
    I can't paste to Illustrator first too.
    I have searched the forum but doesn't get a right answer.
    Any help would be appreciated.

    I finally got the excel files. I could copy paste the chart to illustrator, the results was vector line. Only sadly the data label appear error (screenshot attached)

  • 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

  • Nugget: Open block diagram programati​cally

    There are a way to open a block diagram programatically. Exists a undocumented function located in
    "%Program Files%\National Instruments\LabVIEW 8.6\vi.lib\Utility\sysinfo.llb\Set Block Diagram Open.vi"

    My good old 7.1. (ok, I run that in hyper-boost mode ) has a property node 'VI.Block Diagram Window.Open'. Should be available for anyone and documented in 2010.
    Felix
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • Removing block diagram

    Is there any way to remove the block diagram on a single file basis (just like in the old good LV 7) without creating a source code distribution project?
    I'm trying to create hook scripts for SVN and I'd like to remove the Block Diagram before publishing my code..., I'm using LV8.2.1 and will be moving to 8.5 soon
    Please help!!!!
    <<N>>
    Message Edited by << - N - >> on 04-08-2008 11:09 AM

    Hi Mike,
    I think they work the same way in both 7.0 and 7.1 but in 8.2 and 8.5 there is no "Save with options" and the only way to do this seems to be creating a project...
    Hopefully this functionality is 'hidden' somewhere otherwise I won't be able to create my script =S...
    Does anyone know if this is possible for LV8.2/8.5???
    Thanks for your help !!!
    <<N>>
    Message Edited by << - N - >> on 04-08-2008 01:53 PM

  • Turn off showing block diagram on pause

    Hello,
    Is there a way to disable the block diagram popping up when I pause a running VI?

    No, there is no possibillity.  But why do you want to pause it?
    There are many ways to let your program go into idle if you want to without pushing the pause button.
    Pause, highlight execution, stepping are debugging tools of labVIEW and most of the time in debugging you want to see the blockdiagram to see what is going on.
    Kind regards,
    - Bjorn -
    Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's
    LabVIEW 5.1 - LabVIEW 2012

  • 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-relati​ve-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

  • 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

  • Close front panel but leave open block diagram

    Is there a way to do this? I would like to have my block diagrams of a few subvi's open but front panels closed so my task bar isn't so cluttered. It's not a big deal, I was just curious
    CLA, LabVIEW Versions 2010-2013

    Chris_VH wrote:
    No current way unfortunately.
    A colleague and I actually just put in a product suggestion for this yesterday.
    So if they fix this do I give you or them credit for the solution?
    CLA, LabVIEW Versions 2010-2013

  • 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.

  • How to lock block diagram alone from editing leaving front panel for editing?

    i want to lock block diagram from editing but front panel can be edited for creating controls, moving controls editing properties...

    executables will be delivered to customer and they can create new vi and edit frontpanel and link tag through databinding. but i dont want them to open block diagram...
    Natasftw is right - you seem confused about the difference.
    If the customer can "create a new VI and edit frontpanel" then they have to have LabVIEW Development System.
    If you give them an EXE, and they don't have the DevSys, then they can use your VIs, but not edit them or look at the code.
    If they have the DevSys, then they can edit your VI and look at the code, UNLESS you protect it.
    If you save a VI with protection (VI PROPERTIES - PROTECTION ) then you can LOCK it (user has to explicitly unlock it with an extra step), or you can PASSWORD PROTECT it (user has to explicitly unlock it by giving a password).  Either way requires the DevSys.
    There is no situtation where one can edit the front panel without being able to edit the block diagram.
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

  • How can I create multiple front panels for a single block diagram?

    Hello,
       I have developed a VI with multiple controls and indicators that needs to run on computers with screen resolutions ranging from 800x600 to 1680x1050. The problem I'm having is that the front panel does not properly scale for this range of resolutions by checking the options in the "VI properties" option. Is there a way to create multiple front panels of various sizes for my block diagram and programmatically select the appropriate front panel based on the screen resolution?
    Solved!
    Go to Solution.

    See the attached Zip file.
    I have two different front panels.  Open either one and run it.  They both call MainCode.vi which takes the references passed to it and register for events.  From there, it does all the work of the code you would have put in your front panel .vi.
    This way each front panel can be laid out however you want for each screen resolution.
    Attachments:
    MainCode.zip ‏22 KB

  • 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

Maybe you are looking for

  • Activate photoshop elements 12 on multiple computers

    Hello Im trying to rollout photoshop elements 12 to 30 pc's Tried the slient install method by putting the serial number and ul in the command line and creating the application.xml.override file which works On launching the programme it s asking for

  • Sales Order Number from BSID.

    How can I find Sales order no using the table bsid or bsad Regards

  • Is it possible to activate CS (original)?

    I can install using the original discs and serial number however, there is no way to activate the product (online and phone number don't work anymore). Is it possible to activate the CS, the original?

  • Ipad apps not updating either auto or manual

    Any attempt to update apps on my ipad3 fail. appears to start then stops and returns to "x" number of updates waiting. Not having this issue with IPhone Have done both soft and hard reset & synced with ITunes. Based in UK

  • Editing help please

    Hey I was hoping someone could help with out with a bit of basic editing because I cant find any tutorials on it and I really need to get this piece of work quickly but I am unable to use my computer (sony vegas pro user) so have to make a clip at un