Quote:
Originally Posted by Alan Anderson
The "good/bad" indications in those first two messages look perfectly fine to me.
If you don't have an active wired network connection, you'll see "link-bad". If you aren't using a separate wireless router on the DS, instead using built-in WiFi of a laptop, you'll see "DS radio(.4)-bad". If you aren't connected to a competition Field Management System, you'll see "FMS-bad". If you are connected directly to the cRIO without going through the D-Link router, you'll see "robot radio(.1)-bad".
So everything looks the way I'd expect based on how you said it was set up.
The final message is warning you that your code is taking too long to run each time a driver station data packet arrives. If you can parallelize the complex processing so the motor control can occur without being delayed, that will help.
|
thank you for your answer.
we found out something wired: the first time we run the code, everything seems fine but if we try to run a different code, we get the timeout error. after reboot, everything work again for the first time.
do you have any idea what cause this problem?