11-15-2010 04:44 PM - edited 11-15-2010 04:44 PM
Hi, im using Labview 10 with NI opc servers. I have built a standalone application that uses i/o variables (shared variables) to take data from the NI OPC servers which is done locally and works fine. So i assign the Shared variable to work remotely from another PC making sure the shared variable uses the psp address so it will work remotely, For some reason it won't work remotely, the shared variable defaults to a local address when built as part of an application. Why is this??
11-16-2010 08:58 AM - edited 11-16-2010 08:59 AM
LV exe's use a .alias file that is adjacent to your exe and resolves target logical names to physical IP addresses.
So first make sure that the PSP URL is derived from the project so that it will have a logical target name.
For example:
if your NSV URL is: \\cRIO1\process\NSV1
then the alias file will contain a line like:
cRIO1=192.168.0.2
11-17-2010 02:33 PM
Hi, tried that. Still defaults.
Stu
11-25-2010
09:20 AM
- last edited on
01-15-2025
05:49 PM
by
Content Cleaner
Hey Stu,
Have you tried binding the shared variables to the data source on OPC server? Perhaps this may solve the issue, let me know if this helps.
Use the instructions in the link below:
11-29-2010 05:16 AM
Hi, it seems to be a problem with the shared variable establishing comms remotely with the NI OPC server software. I've tried using a 3rd party OPC client to establish comms with the NI OPC Servers remotely and it can't establish, comms. I also have a 3rd party OPC server installed with NI OPC Server and that works fine.
Stu
11-29-2010
02:33 PM
- last edited on
01-15-2025
05:50 PM
by
Content Cleaner
Hey Stu,
I have a few links that I want you to try the first is to ensure that the variables are being setup correctly, so as to ensure the communication between the host and OPC is correct. The second is a debugging page which may prove useful. The page covers data-binding, firewall settings and setting the correct communication ports using the OPC server. Apologies for not being able to find a cut an dry solution, however this problem is not easy to replicate.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x2CMCAY&l=en-US
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019M1mSAE&l=en-US
11-29-2010
02:33 PM
- last edited on
01-15-2025
05:50 PM
by
Content Cleaner
Hey Stu,
I have a few links that I want you to try the first is to ensure that the variables are being setup correctly, so as to ensure the communication between the host and OPC is correct. The second is a debugging page which may prove useful. The page covers data-binding, firewall settings and setting the correct communication ports using the OPC server. Apologies for not being able to find a cut an dry solution, however this problem is not easy to replicate.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x2CMCAY&l=en-US
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019M1mSAE&l=en-US
11-30-2010 04:25 AM
The error is the exact problem i'm having. I'am using Labview 8.6, not 8.6.1 and still have the problem when i deploy as application. Could it be a fact that i could be using a newer version of the runtime engine thats causing this issue??