The amount of complaints about field connection issues at events this year has been unusually high. There have been cases of teams getting very slow response times from their robots (like 150ms slow). We should document these along with some information about robot setup in this thread. Maybe with enough eyes on the issue the bug will appear.
If you had communication issues at events (high ping times, non responsive robot, laggy controls), will you take some time to post some information here?
Please also post a short description of your issue as well as an upload of the log file that shows this. Located at : Users\Public\Documents\FRC\Log Files
Also, answers to the following questions should be helpful:
- Which event?
- Wireless bridge radio HW revision? (A1, A2, or B1)
Quote:
The label on the DAP says:
H/W rev A1
H/W rev A2
H/W rev B1
|
Quote:
A user can easily tell the difference between the Rev A and Rev B hardware platforms. In addition to being noted on the box and the back of the device on a sticker, the front of the bridge is also visibly different. In the image below, the Rev B is the upper radio, with the Rev A below it.
See http://frc-manual.usfirst.org/TeamUpdates/0 3/6 update for more info
|
- Radio firmware rev? (1.21, 1.4, or maybe something else)
- Programming language?
- Using a dashboard app? Labview, SmartDashboard, or custom?
- Using vision with Axis Camera and cRIO processing?
- Using vision with driver station processing?
- Did you have the radio mounted near motors/large metal structure?
- Using classmate (or similarly slow computer) as driver station?
- 4 or 8 slot cRIO? (FRC-CRIO2 or Old version)
- CAN Jaguars? What FW version?
I know some people are trying to gather data on their own about events they volunteered at. If you are one of these people, can you post your findings here?
EDIT:
Added some other things from Joe, Kevin, and linuxboy. Thanks!
EDIT 2:
Added 4/8 slot cRIO.
EDIT 3: Can jaguar