I’m getting the error below when I try to deploy our code to an older 8 slot cRIO. The code runs just fine if I run it from my laptop. I’ve tried reformatting it just before I deploy it, still get the same error.
Check the dip switches.
Does the cRIO reboot? That is unfortunately, not an error I’ve seen during deployment.
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. That is what it is complaining about, but I’m not sure why. Please let me know if that changes anything. You may also want to see if you can ignore the error, as it seems that the deployment succeeded, but perhaps was unable to access the controller afterwards for some cleanup step.
Greg McKaskle
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’.
I suppose you could always try re-imaging…