[kenavt]

We have been having this exact problem for years. We try to "temporarily deploy" by running (pushing down) Robot Main, and get various ways in how the deploying dialog is waiting for the cRIO to respond. We've had trouble identifying a pattern: it occurs across laptops, and now that over different LabVIEW firmwares from different years. The Driver Station reports communications, and the startup robot code (showing green LEDs). I only recall this occurring over wireless.

Its important to note that this doesn't occur with both of our cRIO-FRC II's (both on wireless). The only one running startup code has the problems. I believe reflashing the cRIO was a short-term fix last year; I will try that again as I'm not sure what to try next. Any ideas?