|
Match Communication Problems
Our team was wondering if any other teams have been experiencing communication problems during matches. For our robot, it would sync up before the match correctly, sit through autonomous, then as soon as teleop began, we would lose communication. One thing that was also noticed is that our driver jumps on the controls as soon as teleop begins and our robot drives about 2 feet until all of the other drivers get on their controls. As soon as everyone else begins driving, our robot communication drops. In the entire traverse city competition, we were able to play 1 full match properly, 1 for 3/4 of the time, and another for about 20 seconds.
The weird thing is, outside of the match, our robot works fine under both tethered and wireless settings. Also, before the competition today, we were allowed to try and resolve this problem by running on the actual match field before the competition resumed. In this time, we ran through 4 complete cycles of auton/teleop on the match field, simulating the exact technology that we would have to play under minus the other robots. We have tried swapping the wireless gaming adapter on the robot with a replacement and relocating the box, but that did not help.
Another thing brought up was the large amount of data being processed wirelessly during the competition and our code may have to many standby functions that are just sitting in the program. There is also the idea that there may be an ip conflict somewhere in the area causing problems. We will be at the detroit competition and see if this problem still occurs. I'll try to remember and update it after we compete there.
Any feedback on other teams having comm problems would be great.
__________________
|