12-29-2009 03:10 AM
Why the "psg.vi" can't open its front panel when the Labview was closed on
the remote computer(Dell-888),But it can open front panel when I opened the
Labview on the Dell-888 firstly? Below is the code of this problem,
I hope someone can help me, Thanks!
Comment: Below code was run on my computer, Dell-888 is another computer
in the LAN. "psg.vi" was located on Dell-888.
12-29-2009 03:31 AM
根 wrote:Why the "psg.vi" can't open its front panel when the Labview was closed on
the remote computer(Dell-888),But it can open front panel when I opened the
Labview on the Dell-888 firstly? Below is the code of this problem,
I hope someone can help me, Thanks!
Comment: Below code was run on my computer, Dell-888 is another computer
in the LAN. "psg.vi" was located on Dell-888.
First of all in order to connect a remote computer through ActiveX you need to configure DCOM and its authentification properly. This is however a major pain in the a** eventhough there exists a runthrough document somewhere from Microsoft about how to do that. From what I can see all the added security in later Windows versions, to plug major security holes in the Windows infrastructure, make DCOM almost impossible to get working without some serious Windows system administrator degree.
Alternative is to use the TCP/IP interface in VI server. You simply replace the Automation Open and replace it by a Application Open node, passing it the IP address or assigned DNS name of your remote computer.
In any case you need to enable the remote access for either ActiveX or TCP/IP in your remote LabVIEW installation and also enable the VI names you want to be accessible remotely. If you have a development system running on that machine you can configure everything in the Options dialog, otherwise you need to configure it somewhere in a development system and then copy te according ini keys from the LabVIEW ini file into your application ini file, eventually adjusting some settings to your remote computer setup during the copy.