Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/23/2015 in all areas

  1. You have two options: Create a LabVIEW Remote Panel: http://www.ni.com/tutorial/4791/en/http://www.ni.com/tutorial/4791/en/ , OR Set up a Windows Remote Desktop connection, to let your supervisor log into your PC: http://windows.microsoft.com/en-au/windows/connect-using-remote-desktop-connection#connect-using-remote-desktop-connection=windows-7 Option #1 is more secure. Note: Option #2 doesn't use a HTML file, while Option #1 does. However, you don't convert your program into HTML. Instead, you create a HTML file to let your supervisor control your LabVIEW program through the Internet. You must still run your LabVIEW program on your local PC.
    1 point
  2. Hi Logman, As you suggest, VC can (should?...) be merged into one VI in my opinion. We design most of our code with VC merged into one VI (actually offen multiples VI for different interfaces) while the Model is really just doing its core task. Also, we try to not use the GUI of the Model/Actor directly so it can run in a higher priority thread instead of in the UI thread. It makes a difference for us in some cases on Windows and it helps us when using our libraries on a Real-Time targets as we already have the all GUI clearly separated and are able to easily debug from any PC (assuming your actors support some kind of TCP communication) even when the Target is running independently.
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.