LabVIEW block diagram icons became invisible

I'm a bit of a loss here.

I worked on a fairly large vi of higher level for a while when suddenly several vi system developed display problems.  In particular, all the screws of the FPGA module no longer appear on the block diagram.  They are there, because I can move the properties and thread them, but they are invisible.  Even if I add a new menu, it is invisible.  Is the same for the control on the structure of timed loop block.  The loop is visible, but the controls are not.

I have attached a picture of a part of the vi that shows what should be a 'open FPGA reference' and a timed loop.  As you can see, the wires are connected and it compiles and works very well, but there is nothing on the screen

It is specific to this vi.  If I create a new vi and add the same vi they look very well.  As far as I know, I did not change to any display settings.

Any suggestions?

Hi Nathan,

You should be able to get a global position by moving one of the scroll bars.  When you click or drag the scroll bar a small box should appear (right of the cleaning if the BD is enlarged or below the bar of horizontal scrolling if the BD is is not maximized) giving the global coordinates.  If you find that you are outside about 15000 pixels (I don't know if it is a hard cut) are trying to move close to the origin.

You should not recreate anything.  Actuall you can find the line where the icons become visible.  In a quick test here he looked about 15000 pixels.

Tags: NI Software

Similar Questions

  • CAN SOMEONE EXPLAIN PLEASE (IN EASY TERMS) WHY MY DESKTOP ICONS BECAME INVISIBLE AFTER WINDOWS AUTOMATIC UPDATES & WILL NOT RETURN OR RESTORE?

    I tried several times now to be able to find the shortcut icons on the desktop, I had before my last batch of automatic updates. I also tried since to add new... but it's like there's an invisible on shield! Looks like they are copying as they would normally, and yet they are still not appear on my desktop... I searched many boards of friends now also with no luck... surely, someone here must know why it happened? I'm goin' out of my mind... try it please help!

    Hello

    Right click on the desktop to get a menu, click on view/show desktop icons. Good luck, Rick Rogers, aka "Crazy" - Microsoft MVP http://mvp.support.microsoft.com Windows help - www.rickrogers.org

  • Copy and paste between versions of labview block diagram

    I try to reuse code from labview labview 2015 2013 (because I need this code with a 13 rio compatible).

    So I just tried to copy and paste items hitherho comics.

    He ended that the elements of the comic have been pasted as a bitmap instead of the original objects.

    Do I have to use a few different copy / paste possibility that strg-c and Ctrl-v or do I have to register each sub - vi in 2013, which would be

    do useless?

    You can't copy + paste between versions of LabVIEW.

    You will need to save for the previous version and open in the LabVIEW version that you want to paste to.

  • Block diagram is broken

    Hi all

    I have a very frustrating problem. The block diagram of my VI has become perhaps a bit too large (though I tried to keep it as small as possible, there is a lot of stuff going on there) and after my last diagram cleanup some objects have disappeared!! I looked in the forum and it appears that there is a solution

    http://forums.ni.com/t5/LabVIEW/Labview-block-diagram-icons-became-invisible/m-p/1119848#M49439

    based on moving the objects of the diagram towards the origin but this does not work for me... When I try to scroll to the right most end of the diagram in order to pickup the objects with broken graphics and move them towards the origin labview crashes

    Please note that I have no other problems with the PC I am working with and that my graphics card drivers are up to date!!!

    Any help?? I really really want to avoid rolling back a version in my VI...

    Thanks a lot,
    Harry

    Ok

    It seems that I had not been paying attention... The solution described here is valid in my case as well...

    http://forums.NI.com/T5/LabVIEW/LabVIEW-block-diagram-icons-became-invisible/m-p/1119848#M49439

  • Index Array icons: Palette and divergence of block diagram

    Hi all

    Why are the Index Array icons discrepants?

    There is a small difference between the two of them...

    ... That's how you see when you look at the table Palette...

    ... But this is how it appears when it is placed in the block diagram.

    Compare yourself:

    Is there a reason for this? I don't really know. I also looked for a thread about this, but I have found no.

    Have you ever noticed this?

    BTW, I'm using LabVIEW 2012 SP1.

    Best regards

    Hi João,.

    so to summarize:

    -l' icon changes when wiring to a 2D array entry rather than a 1 d of entry table

    -l' icon changes too much wiring when a 2D array input and, in addition, all the wiring index entries

    -l' also shows context help leaves how to index more than one element of an array

    -the range (maybe) shows an old version of the icon

    There is more than a simple icon fixed to IndexArray function, but that only one version is displayed. You will notice this behavior for many more functions...

  • Impossible to select and place the Instrument Driver VI icons on the block diagram

    I am trying to automate some of the RF measurements using a Rohde and Schwarz Spectrum Analyzer. I downloaded the Rohde and Schwarz spectrum analyzer pilot named 'rsspecan' version 2.6.1 for Labview on Rohde and Schwarz site to use in my version of the software labview 7.1.

    I copied the files in the appropriate folders in the Labview software on the C drive files. I am able to access those files through the functions---> Instrument I / O---> range of Driver of instruments in the Labview diagram, but when I select the VI icon that I want to put, I am unable to place it on the block diagram. Instead of hovering under the cursor by clicking on the VI icon, by clicking on the icon of the VI has no answer whatsoever.

    Any help would be greatly appreciated.

    Thank you

    Thank you very much for the help.

    So, is there a way to get the above mentioned pilot online Spectrum Analyzer, which will be also compatible with LabVIEW 7.1, so that I don't have to go through the conversion of version Board?

    Thanks again,

    Vivek

  • How to find the position of the VI icon currently run on the block diagram of the appellant

    Dear forum,

    I am currently trying to use a LabVIEV VI as a simple sequencer: several (very slow) actions must run one after the other. Each action is represented by a Sub - VI, some actions are executed several times. My task is to view the Subvi somehow executing.

    My first intention (just manipulate the icon of the VI running with 'Icon.Get VI as Image data' / 'Icon.Set VI of Image data' invoke nodes) has failed, because it changes all instances of the VI icon. If you use the same VI several times, all these VI icons are changed (see here: http://forums.ni.com/t5/LabVIEW/How-to-change-animate-icon-of-currently-running-VI/m-p/3120754/highl... )

    My current approach is to use an image of the block diagram (with "VI: block diagram: get resized Image ' call method) in a picture of the front panel control and working within this control. But for this I need to know the position of the icon of the VI running. I know that I can assess the limits and Position via the properties GObj, but how to find the VI running (note that a VI can be installed several times on the block diagram, so the name of the VI is not unique)? IMHO the easiest way might be if a VI might find its icon on the block of the appellant diagram itself when it is run...

    It is clear that this position is not yet the position on the photo, but this conversion is a small piece of work...

    Kind regards

    cpschnuffel


  • LabVIEW 2015 scrollbar bug on block diagram

    Hello!

    I'm using Labview 2015 SP1 Professional. I use windows 10. Whenever I have do an action on the block diagram I get annoying move right on my scroll bar. Does anyone else have this annoying "feature"? I tried on three different computers and evertime same also on windows 7.

    There was a bug with nested structures that had enabled ' automatic'. Try disabling the automatic extension on all of your structures.

  • LabVIEW move things on different computers block diagram

    We have a site here license to my work, and I use several computers to develop and deploy our test code. However, I discovered that between computers, often things move on the block diagram simply by opening them on different computers. Mainly text fields. We have some text fields next to rows of a table of block diagram that are alliged with the lines of table on a single computer, while the same without code change when opened on another PC, all text fields are compressed vertically so that they no longer align with the rows of the table. This could be the cause, and is it possible to fix it?

    Thanks for the replies. It is the size of the police which was the issue. However, although I have tried to change the default Application font size (by the "default font" settings of "modification of the characteristics of text") to match the computers that had "correctly" it was not solved the problem. I finally realized that I had to change the police system from the Options > environment > fonts > menu fonts application of the front screen of "Open/create", then completely restart LabVIEW. Problem solved.

  • How to display the drop-down list box in MS excel by using labview report generation toolkit? pleasepost code block diagram?

    How to display the drop-down list box in MS excel by using labview report generation toolkit? Please post the block diagram of the code so that I can able to generate from the drop-down list box in excel with the menu drop-down...

    Like this. (edition, use the reference forms instead of the reference to the worksheet)

    Ben64

  • LabVIEW: Null window... stopped to stranger on the block diagram

    Hello

    I have a pretty important program that has been written in Labview 6.0. Recently, we have upgraded to Labview 9.0 and this program has been exported to an executable file with the new version.

    When you run the executable file, I sometimes have the following error as seemingly random places. I was not able to crash when not to use the executable file. LabVIEW: Window zero. The first level VI ".vi" stopped to stranger on the block diagram of ".vi".

    I apologize for having empty on the names of vi, but I can't give names of vi, say what is the software or code. I can tell it uses NI USB-6212 IO cards, interfaces with the instruments of Rhode and Swartz and uses a lot of file i/o.

    I was hoping someone could give me a hint on how to debug such a mistake. I noticed that when this error occurs, the memory usage almost doubles.

    Thank you

    James


  • What is the best way to keep the block diagram / cleaning of façade?

    Hello

    I'm relatively new to Labview so I'm not able to say if I'm overloading my programs or make my too crowded block diagram. I was wondering if there was some ways to tell if I can simplify my programming just by looking (perhaps only experience contributes to these things)?

    I enclose my VI here. Currently, she is able to monitor the voltage and current of two engines. On the screen, you can see an indicator with the voltage and current values and there are cards that can display signals of different engines with a menu drop-down.

    The façade is pretty clean, in my opinion of novice, but the block schema seems messy to me, just at the first glance. I foresee a problem occurring in the future however. In the future, I will have the VI to monitor 50 engines globally. All of the programming will be the same as the one I have now, but it will have 50 indicators and unfortunately 50 times just about everything. I would like to avoid this, but I don't know how I did.

    I use a USB-6009. I use its four differential inputs to monitor the voltage and current of the two engines. In the future, I will get more units DAQ (25 in total because 2 motors can be monitored for each data acquisition). The new Renault will help will help with more resource space, but I think things complicate with the added option of 24 more Assistants of data acquisition (as used in my code).

    Thanks for any help you might be able to provide!

    Usually, it is above all the experience that will teach you the best methods for making your code to do pretty. I don't know anyone who is proud of his first application of claws. There are some resources out there to help with best practices, as that group on ni.com, but you will learn most of your own development.

    Your façade is superb. FPs in general really are to you. You can do it as ugly or pretty as you want. When you have a few controls in duplicate and the Group of indicators, you should use clusters and berries to simplify. You can use a bit of cleanup in this regard, but not much. In addition, I personally hate read red text unless it is a warning any.

    Your block diagram could use a little cleaning in a sense of modularity. You have a lot of repeated code, which you might consolidate in to a Subvi, which is used in multiple locations, or in a loop For. A general rule is to keep your block diagram within a single monitor. You should not scroll. Your application is quite simple, so it is difficult to BUMBLE

    Here are a few details on your block diagram:

    • Click with the right button on your devices on the block diagram and uncheck the "display as icon". You are welcome.
    • Operations on each waveform "(x*2-4)" / 16 in double ": create a Subvi and/or run the waveforms through a loop."
    • You do a lot of 2-element arrays and then indexing. Just replace the ones that have a Select node based on digital.
    • All your code runs every time, including the knots of your property at the bottom, which is not necessary. As you learn LabVIEW architectures, you will learn how to get around this with the initialization and the output of code, but for now, you should put a case around those structure for only when the engine numbers change.
    • I don't know how you're timing your main loop, but you should put a delay in there because you don't need the DAQmx node shoot as fast as your CPU will allow.

    There are videos of intro free that you can watch to learn what OR think 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.

  • Clean using SubVIs block diagram

    Hi guys and welcome to my first post!

    I m a bit new to labview, so be a little patient, if I do not understand everything immediately

    Im working on an existing program that is used to control an MCU on BabyLin on my front, although I have a visualization to see live changes to the system. The program works very well so far, but I m trying to clean up the block diagram. This should be done by subvis, right? I ve read a lot about the size of the block diagram should not increase my screen. Well, im at a length of about 3 x 2 screens (24 "!) after trying to use subvis and to shorten the distances between structures. The only things remaining are huge amounts of local variables and references (they existed already before I got to know the program), mainly for viewing. If I create a Subvi part containing the people of the country, it will change the references that does not make the program more readable (and small), and I guess I can't put a new Subvi on references + Subvi.

    You have any ideas what to do? I hope that I forgot something, otherwise, do not hesitate to ask.

    Kind regards

    Leo

    Bob_Schor wrote:

    To get a handle on the structure of your high-level code, write down (as if you were telling your boss or tell your wife - who knows, they might be the same person!) that you are trying to do.  Keep it pretty General.  You specified a number of steps?  So maybe the top level should be a State Machine, or a message in queue manager.  Describe you something that works at a constant speed, generating data that you have to manage "on the fly"?  Maybe it's a design of producer/consumer.

    You have a lot of initialization?  Put in a Subvi, bring the 20 son out in a bundle (it's "Boss-word" for a Cluster).  Your main program must have a few loops, with values that persist (possibly changing) during the program running in Shift Registers near the top of the loop, with tables and Clusters used to keep related items "consolidated".

    Not too bothered by the size of your routine - I recently downloaded a monster 50-monitor the Forums (I did not even try to understand), up to 6 monitors is nothing!

    Let "encapsulate the function" and "hide details" to be your guide in the reflection on the creation of the screws.

    Bob Schor

    To develop on the analogy of Bob, each talking point can be a Subvi.  In other words, code group associate subVIs.  The advantage of this is that it is much easier to solve problems because all errors will be localized to a Subvi.  Errors no longer Chase around the block diagram.  I guess you can use your current VI as an example of what NOT to do on the block diagram.

  • block diagram window becomes higher in win7 64-bit using LV2011 32-bit sp1

    I have a strange problem and I wonder if anyone has ever seen this behavior. Often, when I go to the block diagram window, it will become the top window that is it is located at the top of all other windows including LabVIEW non-windows! I have to close the VI and really open to fix the problem. I see this on 3 machines, all the dell of m6600 laptops so I think it's maybe a graphics driver issue. Any ideas?
    Thank you
    Michael.

    Tori,
    I confirm that this problem can be solved by removing the Dell Premier color utility that installs with the driver dell put on hardware compatible color first. The question of the window occurs when LabVIEW works so there is some kind of conflict. Anyway, problem solved for me.

  • Reduce clutter in the control on my block diagram reference...

    Is it possible to reduce the amount of clutter on my block diagram when needing to enable and disable controls so that the tests are running? I know that I can place the instruction box in a Subvi, but I'm looking for the best method recommended to reduce clutter when listing references. Using LabVIEW 2015.

    Here is a small example of what I speak, there will be only for references to be added as the devlops of VI.

    Thank you

    Kellen

    rkmadse wrote:

    When you say I can clustor FP, say things that I did, and I have a group of controls such as those below in a clustor. I still have to generate reference constants, which are then placed in clustors. If I want to disable I would have then to consolidate each reference in the clustor, then ungroup and disable each control individually. I bet I'm really missing the point here and I'd love more explanation.

    Thank you

    Kellen

    My main problem is not being able to place real dangerous in a Clustor.

    You think about transportation, when I talk about the horse. Your façade elements can be in a cluster, and then you can use the reference to the pole to disable all. See:

    You will get a façade looking slightly different between the two options if you use disabled and Grayed out because when you grey on the whole cluster, the gray edges. When you gray unique items in the cluster, the cluster edges remain normal.

Maybe you are looking for