08-23-2005 01:43 PM
08-23-2005 01:53 PM
08-23-2005 02:00 PM - edited 08-23-2005 02:00 PM
I don't have your DOS program so I can't test my attachment, so maybe you can try it. I made some modifications. You don't need to wire in a number to N of the For Loop if you enable indexing on the array input (right click the terminal and select enable indexing). I then deleted the index array function because it is not needed when indexing is enabled. Indexing will choose the first array element and use it on the loop's first pass, then on the second pass the second element is chosen and used, and so on until the loop reaches the end of the array. I also got rid of the sequence structure since it was not useful. I moved the delay from the sequence structure to inside the for loop. You cannot use a Stop button in a for loop, so I deleted it. The loop will execute until the end of the array and then stop. You cannot abort in the middle. If you need to do this, you need to use a while loop instead. It is not necessary to put a Stop vi at the end. The vi will stop on its own when all code has been executed.
Try the attached vi and let me know if it works.
Message Edited by tbob on 08-23-2005 01:01 PM
08-23-2005 03:25 PM
I ran the VI and it still brings up the executable and nothing appears to happen. But when I close the app, the system response field is loaded with the prompts from the app like something is being repeatedly sent during that time.
I attached the screen capture of the VI after running and also what the app looks like when I run it manually.
08-23-2005 05:37 PM
08-24-2005 07:56 AM
08-24-2005 09:00 AM - edited 08-24-2005 09:00 AM
Message Edited by EVS on 08-24-2005 09:02 AM
08-24-2005 12:06 PM
Hi Jack,
In my application the window stays up and does not close, I type in the command (I.E. enumerate) and press return and that command is processed. then the app returns a prompt. I noticed yours closes after each command is passed. I am thinking that this VI was not designed to be interactivly used in a DOS session. If you change the executable to echo the string typed in and then wait for another string instead of closing you might see what I am seeing?
J.R.
08-24-2005 12:21 PM
03-31-2017 10:49 AM
Hi Jim,
Seems that the library is not compatible with 64-bit (we currently use LabVIEW 2016 64-bit for development). Is it possible to upgrade the library to 64-bit?