[RyanN]

Originally Posted by RufflesRidge

Ryan, any chance you can post the DS logs (they will be chopped on each disconnect) from any of the matches where you has issues? I'm curious how they compare to the ones that Joe posted from 330.

From what I saw on the webcast you guys did move a bit in one of your matches on Saturday morning, that would be a good one to get the logs from if possible.

Lucky you, I just wrote an epic email with screenshots of our logs.

I just got through looking at the log files from my MacBook Pro, the Dell, and the Classmate. Everything that I see is pointing to network interference, not related to us. I'm int talks with a person from NI that designed the driver station software and created the logger. I'm supposed to talk with him on the phone sometime today.

I also looked through the log from the 20 minutes we drove on the practice field. We had some latency, some packet loss, and we did have 2 very small, short glitches, which I noticed, and they did show up in the log, but the important thing to note is that we regained control immediately, and actually never lost communication, it was some weird glitch where we would go to disabled for just a split second, the shooter would shut off (which is what I noticed), and then it came right back to teleoperated control.

Looking at field data from Thursday when we practiced, I saw no issues with latency, packet loss, or anything. We actually ran fine Thursday, it was mechanical problems that disabled us that match.



Friday, every single match we played had significantly higher latency and packet loss. What was different? More people with smart phones? All their systems were running?

Here's a sample from one match on Friday taken with my laptop:



Notice before the match starts, the CPU usage is really high as the system boots and gets everything ready to run, that seems normal to me. Once the match actually starts though, CPU usage is pretty normal, and actually really good for an FRC robot. Then we start dropping packets and lose battery voltage for a few seconds. We only run the match for little over a minute until we lose all communication. No battery spikes, no high CPU usage, nothing. This indicates to me the field dropped us after seeing the missed packets. The steady line for the latency (green) when we start dropping packets indicates they could no longer communicate with our robot, as the latency never stays the same. Another indication is the missing battery voltage. Then after 30 seconds, just as the game was ending, we regained control for a split second, then the match ended. Something smells fishy here... this happened multiple times, not just this once.

At the end of Friday, we ran a match with us on the stand. No one else was there, just Fusion and some of the FTA. Crowd was gone, the rest of the people at the FTA Table were gone. Here is what that match looked like:



The code running at this time was our stripped code, but with CAN implemented still. Notice before they ran us, we were connected for a long time while Steve and the FTA guy discussed the situation. Never once did we lose a connection, and we had very low packet loss. We started the match in autonomous, CPU came up as expected, and we transitioned to teleop without any problems and ran until our chain came off, when the voltage became stable. Not once did we lose a connection after the match started. Now let's go to the next morning, first match of the day. Nothing on the robot had changed.



Continued below...