[PhilBot]

Hi

At the beginning of this season we also encountered some really long deploy times (doing a run as startup). Based on past experiences, we quickly adopted the approach of using the Imaging tool to set the "No App" switch at the beginning of each development session.

This effectively leaves the cRIO idle/blank after a REBOOT so the deployment process seems more reliable (completes quickly more often). You just need to remember to turn the switch back off at the end of the session otherwise you won't have code next time you boot.

At our recent regional, we tried doing the deployment without the "No App" switch set, and it seemed to work OK, so I'm not sure what caused our initial slow deploys.

Something else to note. At our facility we have two high speed wireless routers that share the same network. We can download to the robot if the laptop is connected to either of the two routers, but we do find that connecting to the SAME router that the robot is using makes for a much faster deployment (even with the No App switch set.)