09-03-2008 09:52 AM
I use the system exec VI to issue a command using the windows cmd prompt.
The command I execute takes a while to execute and display progress when
called from an actual command prompt. When I set the 'run minimized' parameter
to false, I see a big black empty window while it is running. If I also set 'wait until
completion' to false, I now can see the progress, BUT it breaks my flow control
since the subVI after the System Exec VI assumes the execution is complete.
How can I show progress WITHOUT leaving the System Exec VI?
09-03-2008 10:08 AM - edited 09-03-2008 10:08 AM
09-03-2008 11:29 AM
Thanks for the quick reply.
Some problems though:
1. When I tried adding a ' > outfile.txt' to my labview command, nothing got created. I searched throughout my drive.
2. When I opened a command prompt and performed the operation there, a outfile.txt WAS created, but it didn't get filled until the operation finished, which
really isn't useful for monitoring progress.
Any other suggestions, or some way of getting around these issues for this suggestion?
Thanks...
09-03-2008 02:17 PM
What are you using for your command? You may need to preceded with "cmd /c" or "cmd /k". For example, the command
cmd /c ipconfig > c:\result.txt
will output the result of ipconfig to c:\result.txt.
09-03-2008 03:05 PM
I am using an executable I created.
I can try the cmd /c idea... but even with that, it seems like I will still have the other issue: The file not having any stuff in it until the process is completely done.
09-03-2008 04:24 PM
07-28-2020 11:29 PM
hi
do you get solution for this?