LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Copy & Paste Error hello!

I have no problem to copy & paste from one vi to another. However when I tried to copy & paste the sub vi from one vi to another I get the message hello! printed on the recieving LV.  How do I copy a SUB VI from one lv to another?
0 Kudos
Message 1 of 9
(3,771 Views)
That doesn't make any sense. You say "I have no problem to copy & paste from one vi to another" and in the next sentence you say can't do a copy and paste. Do you really mean that you can't copy from a VI in one version of LabVIEW to another VI in a different version? If that's what you're trying, then no, you can't do that. The only way to get a VI from a newer version to an older one is to save the VI to a previous version from the Save with Options menu.
0 Kudos
Message 2 of 9
(3,762 Views)
The easiest way is to just drag the subVI icon from one block diagram to the other.

What OS and LabVIEW version are you using, I don't have that problem when I try a copy and paste.

Ed


Ed Dickens - Certified LabVIEW Architect
Lockheed Martin Space
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
0 Kudos
Message 3 of 9
(3,761 Views)
How to have TWO block diagram from differen LV's on the monitor screen. I am using LV6.0 I have no problem with parts of a sub vi. However I cannot do copy & paste  with the entire sub vi.  What is hello!.
0 Kudos
Message 4 of 9
(3,754 Views)
Could you send us a screenshot of this error?  ...I'm curious to see what it is
0 Kudos
Message 5 of 9
(3,748 Views)
You keep saying "different LV's". I would interpret that to mean different LabVIEWs (as in two different versions). If you are copying from one block diagram of one VI to another block diagram of another VI, all you have to do is select the code in the diagram and drag it to the other block diagram. You can also select it in one block diagram with the CTRL+C, move to the other window and do CTRL+V. Copying and pasting a part of block diagram is no different than copying and pasting the entire block diagram so if you're having problems, I don't know what to say. Are you sure you actually did a CTRL+C when you tried to copy? Provide the exact procedure that you're doing to do the copy and paste.
0 Kudos
Message 6 of 9
(3,747 Views)
If you have two instances of the same version of LabVIEW running, it still won't work.

LabVIEW has it's own internal clipbaord for copying and pasting so the real code behing the diagram/subVI is retained. But if you try to copy something from within LabVIEW to something out of LabVIEW, even if it's a separate instance of LabVIEW, it has to go through the Windows clipboard. Once that happens, it's no longer LabVIEW code. It gets converted to an image of what was copied.

Does that shed any light on what is happening?

Ed


Ed Dickens - Certified LabVIEW Architect
Lockheed Martin Space
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Message 7 of 9
(3,738 Views)

I have managed  to drag the sub vi from one  block diagram to another. Thanks.However I still get the hello! for the normal copy & paste . I discovered that if I copy & paste someone else reply as a quote in this forum, I also get the error hello! I suppose my PC might have a virus. However there is no problem with dragging. I have attached the vi, I am trying to fix a broken line. Can anyone help?

0 Kudos
Message 8 of 9
(3,736 Views)
Right click on the tunnel on the edge of the For loop where your broken is and select, Disable Indexing.

By default, when you wire out of a For loop it will always build an array of the values generated in the loop. Be warned that only the last value generated in the loop will be passed out of the loop after it has finished all of it's iterations. Be sure this is what you want.

Ed


Ed Dickens - Certified LabVIEW Architect
Lockheed Martin Space
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Message 9 of 9
(3,729 Views)