Quote:
Originally Posted by Morgeno
For some reason when we attempt to deploy code, about 90% of the time an error comes up at a completely random time in deployment that says:
"Error: waiting for real-time target CRIO to respond"
[...]
Has anyone run into this problem before? If so how did you fix it?
|
We've been regularly losing contact with the cRIO during code deployment for weeks. Our lead programmer just discovered that having it in Test mode when trying to load new code was a reliable way to have it fail, and after he started making sure it was in Teleop it hasn't broken again. I don't know what is really going on, but I do know that Test mode pegs the CPU usage at 100%.
Quote:
Originally Posted by silas13579
Hello all,
I'm from the same team and as an update, when we try to connect we get error 44002 about 50 times: Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-GOOD, robot radio(.1)-bad, cRIO(.2)-bad, FMS-bad Driver Station.
|
The "DS radio(.4)-GOOD" part is highly peculiar. It's not typical to have anything respond at the 10.23.37.4 IP address. Besides the D-Link, do you have another wireless router in the network?