Team 1280 here and we had some major problems at the Davis competition. On Thursday we ran fine all day. Once we got into matches though, we had problems.
- Match 8: Ran successfully, had spike of 33 dropped packets early in autonomous mode. No latency issues. Max CPU at 90%
- Match 14: Robot froze 3 seconds into autonomous. No spike in latency or dropped packets. Max CPU at 85%
- Match 18: Ran fine at operator end however there was high latency and lots of dropped packets throughout the match. Peak latency at 50ms, packets at 15, Max CPU at 96% mostly under 90%.
- Match 28: Failed early into teleop. Spike in dropped packets at 58 packets at the start of autonomous, we ran through autonomous fine, but a few seconds into teleop we froze and had spike of 18 dropped packets and our CPU drop from around 72 to around 17 and then go all the way down to idle. Latency hovered around 5ms for the entire match.
- Match 37: Ran fine. Spike of 33 dropped packets at start but CPU averaged around 68 during teleop.
- Match 45: Ran fine. We unplugged the camera and our CPU spiked at over 100% and was oscillating between 45% and 100% at regular intervals from when we powered on the robot. Latency had one spike at 22ms, but other than that it stayed around 5ms. We had regularly had dropped packets but they never went above 10
- Match 51: Did not run autonomous. Had an oscillating CPU usage between idle and 100% at the same interval as Match 45. We think the camera was still unplugged. We only lost 5 packets at the start but had latency spike of 25ms.
Saturday things went worse. - Match 65: We did not run. 41 lost packets at the start of autonomous coupled with a latency spike of 17ms. Our CPU usage did not go above 10 before it stopped.
- Match 70: We did not run again. No dropped packets, we had CPU drop to idle after autonomous, latency was pretty consistent at 5ms.
- Match 77: We ran fine. There was a 38 dropped packet spike at the start of autonomous but latency stayed around 5ms. CPU usage stayed around 80%
- Match 84: We did not run. We had 98 dropped packets just after the start of autonomous and after the last time our robot said it was in autonomous. Latency stayed at 5 while we lost the packets. CPU never went above 15% before we lost communication.
We made minor code changes throughout the weekend. As you can see, our problems got worse as the competition went on and there was no consistent pattern to it. The only consistent thing about the loss in communication was that our robot mode line disappears from the log charts when we lose communication, while the driver station mode line stays. We are not sure if this is a symptom or a cause. We are getting complete loss in communication, rather than temporary loss of communication. We are hopefully going to find out more on Thursday in San Jose, but for now any help would be great.
- Team 1280
- Which event? Sacramento/Davis
- Wireless bridge radio HW revision? (A1, A2, or B1) A1
- Radio firmware rev? 1.40
- Programming language? C++
- Using a dashboard app? Currently using SmartDashboard for display statements using log function. FRC Dashboard is on the side for the camera feed.
- Using vision with Axis Camera and cRIO processing? 1 Camera with vision processing on 8 Slot cRIO. Resolution at 320x240 @ 7fps
- Using vision with driver station processing? No, but we do have a camera feed (FRC Dashboard)
- Did you have the radio mounted near motors/large metal structure? Mounted at top of robot near shooting motor.
- Using classmate as driver station? No, using 6730b HP laptop (Win7)
- 4 or 8 slot cRIO? (FRC-CRIO2 or Old version) 8 slot
- CAN Jaguars? What FW version? No Jaguars