LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Accidentaly changed Labview built-in VI

Solved!
Go to solution

Hello,

 

I was recently working with the Model Interface Toolkit of Labview. While browsing in the VI structure, I accidentaly moved the blocks and wires of one VI (Take model time step.vi), and now I am getting a gray broken arrow, because the VI cannot execute. Is there a way to get the default vi back to its original structure? I tried to download Veristand again, but it didn't work.

 

Thank you all

Lysandros



0 Kudos
Message 1 of 4
(3,096 Views)
Solution
Accepted by topic author Lysandros

Well unless you have another computer you can get a clean copy of that VI from you have two choices

  1. Figure out what you messed up and fix it
  2. Reinstall the toolkit
========================
=== Engineer Ambiguously ===
========================
Message 2 of 4
(3,067 Views)
Solution
Accepted by topic author Lysandros

Option 3 if you are running Windows and have System Protection enabled.  Find the folder containing the VI and right-click on the folder.  Look for Previous Versions.  The new window will show if there are any and when they were saved.  Open the previous version folder and drag the old file to replace the newer file.

Michael Munroe, CLD, CTD, MCP
Automate 1M+ VI Search, Sort and Edit operations with Property Inspector 5.1, now with a new Interactive Window Manager!
Now supports full project automation using one-click custom macros or CLI.
Message 3 of 4
(3,040 Views)
Solution
Accepted by topic author Lysandros

@Michael_Munroe wrote:

Option 3 if you are running Windows and have System Protection enabled.  Find the folder containing the VI and right-click on the folder.  Look for Previous Versions.  The new window will show if there are any and when they were saved.  Open the previous version folder and drag the old file to replace the newer file.



That's a good idea and worth a shot.

 

All though I think if one was to look at the examples that came with the toolkit you should be able to figure out what you broke in the VI in question. 

 

Sure all the examples will be broken but you will be able to see what connections are supposed to be made to the broken VI and that helps a lot in figuring out what you broke.

========================
=== Engineer Ambiguously ===
========================
Message 4 of 4
(3,018 Views)