Quote:
Originally Posted by Greg McKaskle
I suppose you could go to Tools>>Options and to the VI server tab and ensure that TCP option is enabled. You can also do that on the Target Properties in the project.
|
I did replace the ip listed with "*" to the machine access list of the VI Server page. It had no effect. I've seen this now on two different 8 slot cRIO's. All of our 4 slot are still being used in older robots.
As for trying to ignore the error, I can close the error message and when then the cRIO reboots, there is no code running. I'm deploying it by selecting 'Run as startup'.