Problems with startup vi's using TCP on a cRIO, error code 63

[bww]

I'm trying to deploy the "Multiple Connections - Server.vi" from the TCP & UDP examples to a cRIO as the startup application. The vi works fine and I can connect with multiple clients until I deploy the vi and set it as the startup vi on a cRIO device. When the device reboots and I attempt to connect with the"Multiple Connections- Client 1.vi" also found in the TCP & UDP examples, I get "error 63 occurred at TCP Open Connection". Are there additional parameters that need to be enable to allow TCP as the startup vi?

[nathand · Accepted solution]

I'm not sure this is the issue, and I don't have an RT target available to test it, but here's one possibility: property nodes sometimes do not work as expected when running on an RT system with no front panel.  In the case of the Multiple Connections - Server example, the first thing that happens is the VI writes a false value to the property node.  As explained in the link, this will have no effect.  So, if the default value of the "listen halted" control is "True" the upper loop will exit after the first execution, which will stop the VI, most likely leading to the error that you're seeing when you try to connect.

To solve this, I recommend that you remove the "listen halted" control entirely and change the stop conditions for both while loops.  You're running a compiled application on RT, so unless you're going to connect using a remote front panel, there's no need for any front-panel controls including the stop button.

EDIT: if I've correctly identified your problem, please vote for this idea: "Warn about front-panel property node use when building an RT application".

[bww]

Your solution appears to be spot on! Thx.