LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

VI lost after creating a copy of the project. How to recover original VI?

Solved!
Go to solution
  1. I tried to create a copy of the project to make some additional changes, and later on decided not to, and deleted the copy.
  2. Went back to the original project and I see this. I am unable to locate the MAIN.vi anywhere in related directories such as (temp, user, etc.)

 

Any advise to recover this is appreciate. (Yes I dint back it up)

 

2018-07-06 12_38_02-PCA-a00.lvproj - Project Explorer.png

NI System Configuration:
- NI PXIe-1071, 4-Slot 3U PXI Express Chassis , 1 GB/Slot throughput, Part Number: 781368-01
- NI PXIe-PCIe8381,x8 Gen2 MXI-Express for PXI Express Interface,3m, Part Number: 782522-01
- PXIe-5160 PXI Oscilloscope, 500 MHz, 10 bits, 2.5 GS/s, 2 Channels, 64 MB, Part Number: 782621-01
- Astronics PXIe-1209 2-Channel, 100 MHz PXI Pulse Generator, Part Number: 785033-01
0 Kudos
Message 1 of 14
(413 Views)

Can you grab whatever it was that you deleted from the recycle bin?

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 14
(394 Views)

If you were working in Excel, copied it worked on it, and deleted it, where do you think you'd find the original?

0 Kudos
Message 3 of 14
(392 Views)
Sorry I meant [Shift + Delete]
NI System Configuration:
- NI PXIe-1071, 4-Slot 3U PXI Express Chassis , 1 GB/Slot throughput, Part Number: 781368-01
- NI PXIe-PCIe8381,x8 Gen2 MXI-Express for PXI Express Interface,3m, Part Number: 782522-01
- PXIe-5160 PXI Oscilloscope, 500 MHz, 10 bits, 2.5 GS/s, 2 Channels, 64 MB, Part Number: 782621-01
- Astronics PXIe-1209 2-Channel, 100 MHz PXI Pulse Generator, Part Number: 785033-01
0 Kudos
Message 4 of 14
(388 Views)
It was actually a Shift+Del (sorry, should have added this now I think its too late to edit the post).
NI System Configuration:
- NI PXIe-1071, 4-Slot 3U PXI Express Chassis , 1 GB/Slot throughput, Part Number: 781368-01
- NI PXIe-PCIe8381,x8 Gen2 MXI-Express for PXI Express Interface,3m, Part Number: 782522-01
- PXIe-5160 PXI Oscilloscope, 500 MHz, 10 bits, 2.5 GS/s, 2 Channels, 64 MB, Part Number: 782621-01
- Astronics PXIe-1209 2-Channel, 100 MHz PXI Pulse Generator, Part Number: 785033-01
0 Kudos
Message 5 of 14
(388 Views)
Solution
Accepted by topic author asukumari
07-09-2018 06:50 PM

Before trying to recreate the VI from memory, make sure that your Version Control System (Subversion, Git, Perforce, Mercurial, something else) is properly configured and used every time a significant change is made to the code.  The cost of doing this is very low, especially compared to the pain of losing your work, doubly-especially when you start dealing with Projects with hundreds of VIs.

 

Bob Schor

Message 6 of 14
(359 Views)

I like version control because it makes you bold and daring.  If you're going to try a crazy idea, create a branch.  If it ends up going nowhere, you just delete the branch and start over.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 7 of 14
(356 Views)

@asukumari wrote:

Any advise to recover this is appreciate. (Yes I dint back it up)

 


Then SOL.  Next time, use a Software Configuration Control software such as Tortoise SVN or GIT to save a history of your code in repositories.  Then you can easily recover from disasters like this.  And almost as important, when somebody asks you what you did to the code on day X, you can just look at the history and the notes you put in on the commit will tell you exactly what you did (yes, I just ran into this situation).


There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Message 8 of 14
(327 Views)

@crossrulz wrote:

@asukumari wrote:

Any advise to recover this is appreciate. (Yes I dint back it up)

 


Then SOL.  Next time, use a Software Configuration Control software such as Tortoise SVN or GIT to save a history of your code in repositories.  Then you can easily recover from disasters like this.  And almost as important, when somebody asks you what you did to the code on day X, you can just look at the history and the notes you put in on the commit will tell you exactly what you did (yes, I just ran into this situation).


I always write something in the revision history of the VI, then when I'm ready to commit, I put all those notes into the commit log.  If it seems a bit tedious, I can tell you exactly when each change was made, and makes it a lot easier to hunt bugs down.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 9 of 14
(321 Views)

Going to put in a purchase for a version control system.

 

Never learnt version control. This is my chance.

 

Thanks a lot people !

NI System Configuration:
- NI PXIe-1071, 4-Slot 3U PXI Express Chassis , 1 GB/Slot throughput, Part Number: 781368-01
- NI PXIe-PCIe8381,x8 Gen2 MXI-Express for PXI Express Interface,3m, Part Number: 782522-01
- PXIe-5160 PXI Oscilloscope, 500 MHz, 10 bits, 2.5 GS/s, 2 Channels, 64 MB, Part Number: 782621-01
- Astronics PXIe-1209 2-Channel, 100 MHz PXI Pulse Generator, Part Number: 785033-01
Message 10 of 14
(289 Views)