Datasocket Open Timeout in built cRIO exe.

[viScience]

I have observed that from my project I can run a vi that opens a DataSocket Reference to a NSV with the following URL:

\\192.168.0.2\Remote\'Remote Command'

When I built an exe and run on my cRIO then I get an error 56 timeout in the DS Open.  I have verified that the library containing

this variable is deployed by using the Distributed System Manager and it does appear in the remote target under the correct process.

Just for kicks I have undeployed and redeployed but no difference.

Any Ideas?

[Jennifer_R]

Hi sachsm,

I have a few additional questions and suggestions.  When you say that you can connect to the shared variable from the project, is that VI running on your PC or the cRIO?  Can you connect if you run the RT code from the front panel and not as a startup executable?  Where is the shared variable being hosted?

1. Verify that DataSocket for LabVIEW Real-Time, Network Variable Engine, and Variable Client Support are included in the software on the cRIO.

2. Use the DataSocket Select URL VI and run the cRIO code with interactive front panel communication to see if you can browse to the correct URL.

3. Try to drag the shared variable from the project onto your cRIO block diagram to see if you can connect through a shared variable node instead of DataSocket.

Also, as a side note, for future cRIO questions you will likely receive more responses from the community if you post on the LabVIEW Real-Time board instead of just LabVIEW. . 

[viScience]

I have a few additional questions and
suggestions.  When you say that you can connect to the shared variable
from the project, is that VI running on your PC or the cRIO? 

cRIO

Can you connect if you run the RT code from the front panel and not as a
startup executable?  Where is the shared variable being hosted?

Yes, and the NSV's are hosted on the cRIO

1. Verify that DataSocket for LabVIEW Real-Time, Network Variable Engine,
and Variable Client Support are included in the software on the cRIO.

Yes it is

3. Try to drag the shared variable from the project onto your cRIO block
diagram to see if you can connect through a shared variable node
instead of DataSocket.

Yes I can do that and it works