LabVIEW move things on different computers block diagram

Similar Questions

• How to set a menu of VI function to generate a copy of it self when it is move and dropped on the block diagram

  Is any way to put a VI that I placed on a palette in the menu functions to create a copy of it self when I place it on the block diagram?

  My example is as follows. I create a palette for a messaging configuration. The 'send message', 'message' and so forth will work normally with just called when necessary. But 'Create queues messge' must be specific for each instance, because I'm going to create a different number of queues each time I use it. (See system messages in queue OR for the "Continous Measument and Logging" model).

  So every time I drag and drop that VI (Create message Queues) in the palette, I want that it ask me where I want to save the VI.

  Is this possible?

  See you soon

  Henrik

  There is always the file-> new... that opens a new window.  You can have your models in this window by putting them somewhere (I can't remember where at the moment).

• Bug: Façade objects relative position changes when you move the fusion VI on block diagram

  I posted a bug report on the LAVA, here:

  http://forums.lavag.org/front-panel-objects-relative-position-change-when-placing-merge-VI-onto-bloc...

  If someone at home OR can reproduce, can I please get a CAR #?

  Thank you

  -Jim

  Hi Jim,.

  This was reported to R & D (# 139212) for further investigations.  I don't know if it's more embarrassing fall into the range of functions and reorganize the façade or drop out of the front and hope that the code of the Subvi is not disseminated in the block diagram.  Because the code (or orders) are selected after a fall, and you can switch between diagram and panel above all keeping this selection, at least you can move the code as a whole, right?

• ALT-click to move the items connected on block diagram

  Often, in the diagrams, I would like to be able to drag all the elements connected together to keep them in the same relative position to each other.  Currently, to move multiple items, you will need to select them (stretching), then click and hold to move.  It would be convenient if you could just hold Alt, then click and have Labview automatically select all connected items until you have clicked.

  You can not. If you really want to delete a thread, you can send a note to the facilitator. Simply select 'Report to moderator' in the menu Options (above and to the right of the message). I'm assuming you want it to enter the exchange of ideas of LabVIEW.

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

• Constant error cluster appears different in two places on a block diagram

  I am a newbie to LabVIEW. I took Core 1 and 2 and Vision and I did not com on this before.

  The right image is of course a constant of cluster of error used in the block diagram to create a cluster of error and it lead to an error on the terminal. As far as I can tell the left image is the same thing, but why is it different? The causes of different appearance raises a concern that there is a difference in behavior that I don't understand. LabVIEW help season both are constants for error. When I create a new constant of error, it always appear as the image on the right above.  I was not able to create something similar to the image on the left.

  Could someone please confirm what the image on the left on a blck diagram?

  Thank you

  Bill

  The left image is a mistake of cluster control. He has a presence on front panel and can be set via the front panel or by a property node or a local variable. The image on the right is a cluster of error constant. It is a static value.

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

  

• 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

  
  

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

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

• Corrupt the VI block diagram (try to view the BD accidents LV)

  The attached corrupt version 2010 VI in the room is '8810A control.vi.'  I put work a few days into it, so it would be nice to get it back.  I can open it fine to display the front panel.  When you try to view the block diagram, an outline of the BD window appears and freezes LV.  Usually, after a few moments, LabVIEW itself disappears completely.  No error message; no sign of it in the taskbar or any where.  I tried to save the VI to a previous version, but LV will receive an error.  In trying to "Double hierarchy to the new location", I get a popup saying "LabVIEW: file generic i/o error.»  I then did a copy of VI, open and tried to delete everything from the face before completely.  Still can not go to the BD.

  I think that what caused the error was when I accidentally clicked my mouse button that I arrived to move the cursor quickly through the BD of this VI.  I couldn't tell if it hit or moved something on the comic.  I don't remember for sure, but I think that at this time there LV froze and I had to kill him and restart.  After happened yesterday, I moved on to work on other screws which have not been affected.  I guess I'll have to recreate (because I had not yet created backups).  in the future, I hope that I can remember save projects at least twice a day.  I've used Mercurial and it works well.  Hard lesson learned.

  Try this.  I saved to LV9, opened with LV9 then did a cleanup of comics.

• block diagram error

  Hello

  I do a charge battery discharge cycle using labview 2011... On the block diagram, I using node of the formula to change the operation of discharge of charge when the battery reaches a certain level, the battery is connected to the entry DAQ assistant... but when I connect the wizard entry to the formula node DAQ, an error pops up...

  Block diagram errors
  -You have connected two terminals of different types.

  Details
  These can be wired together as their data types (digital, string, array, cluster, etc.) do not match. View the contextual help window to find out what type of data is required.
  The type of the source is Dynamic Data.
  The type of the sink is a double [64-bit real (precision ~ 15 digits)].

  Please help me...

  You have incompatible data types. You need convert the data type to express dbl

• How can I activate on labels in the block diagram, but not on the front panel?

  This question may have been asked before, but searching the Forum did not.

  In LabVIEW 2010, I have 16 indicators of chain on the front panel. I can't have the label for each Visible on the front panel, so I turned it off. But in the block diagram, I need distinguqish one of the other, so I need to make the label (name) visible.

  In the block diagram, if I select indicators Sting all together and go to properties and make the label visible, it makes visible labels on the front but not visible in the block diagram. What good is that?

  How the help of labels (name) of the indicators String visible in the block diagram, but not visible on the front?

  dbaechtel wrote:

  This question may have been asked before, but searching the Forum did not.

  Don't remember already asked this question and get help in this thread?

  Have you tried the things I said in that thread?  How did they not work?

  Right-click on the terminal of BD and make visible > labels.

  It probably will be the FP control show its label as well.  Then go to the FP control, right-click and go to Visible > labels and uncheck the box.

  The terminal of the comics will have a label, and control of the FP will not.