System Exec.vi doesn't work properly with wait until set to True

[Amit4]

Hello,

Thank you all for your help in advance. My system exec.vi doesn't work properly when "wait until completion?" is set to True. It seems to work partially though. I am trying to program Bluetooth module. This vi is part of larger system. see attach vi and picture.

However it works fine if wait until completion?" is set to False. I need window to be open after it is done programming or output to be display in standard output indicator.

Thank you again for your help.

[RavensFan]

Are you sure it is working if you set it to false?

Does that command work if you don't do it from LabVIEW but from an actual Windows command prompt window?

The error message you show says "Untested Windows 10.0 version detected!".  That seems to be an error generated by the xxxxxxx.exe executable you are running as opposed to the way you are calling it in LabVIEW.  I think that if you set Wait Until Complete to False, it is still generating that error, but you just aren't seeing it.

[Amit4]

Hello RavensFan,

Are you sure it is working if you set it to false? Yes, it is works when set it to false. I have tested out by programming Bluetooth module and checked for transmit and receive on Bluetooth; and it does what it supposed to do.

Does that command work if you don't do it from LabVIEW but from an actual Windows command prompt window? Yes, it works in windows command. Currently, that is how it is being programmed.

This message "Untested Windows 10.0 version detected!" even comes up when programming thru windows command.

[altenbach]

What behavior do you actually want? Do you want the command window to remain open and ready for manual input once LabVIEW is done with it? It is out of the control of LabVIEW how the command window behaves once it is done.

(The wait for completion just determines if the LabVIEW code continues or not while the command prompt window is still executing. As the help explains, outputs are not available if you don't wait, because there cannot be data until the exe completes. Dataflow!)

What is your command line? Are you using the /k switch?

(Why would you concatenate a single string? It's a NOOP.)

[Amit4]

Hello Altenbach,

Thank you for your input. I want the command window to be either open during programming or just labview outputs at standard output at end of programming.

I'm using /c switch. I am okay with /k but somehow it doesn't passes inputs wired to "standard input" (Bluetooth SN). I have to manually input Bluetooth SN again in window command prompt.

[RavensFan]

Could you just redirect outputs to a temporary file and read that in LabVIEW?  So  end the command with something like >> c:\mytempfile.txt  ?

[altenbach]

We cannot offer more suggestions unless you tell us exactly what all your inputs are. We are not clairvoyant!

[Amit4]

Hello altenbach.

It seems like the issue is Bluetooth programming tool that opens up windows command.

Amit

[Yamaeda]

I have a slight memory of reading of standard input issues before. What happens if you create a .bat-file with the parameter and run that instead?

/Y