copy labview code while running

[craftindo]

dear all,

I want to minimize the downtime of the machine running. Am I able to copy the Labview code while the labview is running without disturbing the system?

If that is possible of copying, is there any other way? 

thanks

[Coq_Rouge]

Then you say copy, you mean copy the Labview source files then system is running?

[craftindo]

I want to copy the Labview source code while the code itself is being executed? (so i dont stop the code, the machine in the factory plan can still run as per normal).

(copy labview source files)

Is it possible?

[shjukheter]

You mean that you want a copy of your code. If the code fit exactly to your desktop window then use "print screen". It works even in runtime.

Sorry, i though you need image.

[Dennis_Knutson]

Copying the VIs is possible at any time.

Everyone - repeat everyone, should be using some sort of Source Code Control program (i.e. the free svn) so the source code would always be available from the SCC server. Even if you don't take this basic step, all code should be at least backed up someplace. If you only have one copy of the program, you are already flirting with disaster.

[Coq_Rouge]

So the only copy of code. Is on the machine used to control a plant process. And if this machine crash. The source code will be lost. Somewhat dodgy 😉 However I guess not your fault.

In principal you can do it. But what I do not know, is that if the copy process itself will cause problems. The copy process it self. Will need some CPU time. And how this influence on the running Labview app. I do not know. If the Labview app. Is poor written it could be a problem. That is the best answer any can give I am afraid

[Matthew_Kelton]

Are you trying to copy FROM the machine running or TO the machine running?

[craftindo]

from the machine running to my laptop

[Matthew_Kelton]

You should be able to copy it then with no problem.  The only potential issue is if the system is doing heavy hard drive access or is using a lot of the CPU resources.  You could see some performance hits during that time, which could end up causing errors or test failures, depending on the code.

As others have pointed out, you need to have the code stored somehwere else for reasons such as your problem and so that a system crash doesn't wipe out your code base.

[Mark_Yedinak]

To be honest I wouldn't have any code on the production machine. I would build an executable and use that for the production machine. Much easier to track the applictaion version on the machine that way.