|
No Robot Communications
Our cRIO suddenly stopped communicating. I was running new code as a startup (we use LabVIEW by the way) and the deployment failed twice due to losing connection with the cRIO (which was odd in itself). The third time it succeeded, but when it rebooted the DS didn't get any communication from it. After rebooting it a few times, I tried pressing the reset button on the cRIO, since so many teams are having the problem where the cRIO boots before the wireless bridge, and the way to solve that is apparently to press the cRIO's reset button. That didn't work though, even after trying it repeatedly interspersed with more reboots. Until now, the only wireless connection issue we had had was initially, when we got a sporadic connection since we had some IP addresses set wrong. So I tried tethering the DS to the cRIO. In fact, I tried it with both of the crossover cables we have, since sometimes the wired connection will fail to work until we switch crossover cables, although which cable works varies. Through all of this, the best I could ever get was that when I was using the wireless connection and reset the cRIO, I would momentarily get "No Robot Code" before it returned to "No Robot Communications".
|