NickB34

I think I may travel down the python socket server road with this one. It is probably the best way to implement what I need since I won't have to install any NI stuff on the server side. If only I knew more about programming in python... I'll update if I ever come up with a solution.

Here is a picture of what happens when I send a string after I send the py directive. It gives me an error 56 on the pipe read, seems like a pretty generic error code.

I've been able to download the pipes package and have been able to execute the test VI's that are included. Whenever I send the py directive to a command console, I can see it change to python mode. Any command that I send after that causes an error. I see the same behavior when I open python.exe using pipes (instead of cmd.exe py). Any ideas? System Command (cmd.exe) Test.vi

Todd, thanks for the links. I was able to install using VIPM, but for some reason the palettes didn't show up. I've never used pipes before so I will have to try and figure out how the VI's work. Yes, I did cross post this. I will update both posts if I am able to come up with a working solution.

Darin, please elaborate if you can.... I would love to see an example of this. I'm not on a Linux box, using windows here.

Thanks for the response. I'm not a python programmer, but I may be able to get some help with this. I'll ask around and see if somebody here has some experience with this.

I've posted this in the NI forums, but I thought I might get some more traction here... Does anybody have any ideas on a way to stream commands to a python console? A little background on the issue: I am able to control instruments in a system through a .dll that I call using python. I have already implemented a VI that can create a script "on the fly" and execute it to perform simple commands. The problem is that this creates a new instance of python every time I execute a command. It would be very advantageous for me to keep python running and only stop execution when I'm done sending commands. I have tried accessing python directly from the python .dll through LabVIEW, but this got ugly very quick and I'm not a software engineer I have also tried using labpython, but it doesn't seem to be compatible with python 3.3 which is a requirement in the system. Please let me know if you have any suggestions on what path I should head down, Thanks.