[Greg McKaskle]

I attached an image of the log file.

Since the laptop CPU usage is quite low, I think you do truly have pretty bad wifi comms in this location. At the beginning and end, you basically can't stay connected due to the timeouts of comms. I mention the laptop CPU because sometimes, plots like this are actually due to a laptop that is installing updates or otherwise max'ed out and unable to process return packets.

The other thing that is quite odd in your log is that your code trace shows that the DS is requesting that teleOp run, but the code is reporting that it ran auto instead. I suspect that it isn't that simple, and that you are actually running teleOp but the trace has been delete somehow. But are you running auto too? Does that shed any light on why the robot is behaving that way?

I certainly see lots of gaps in processing, lots of times when the robot was disabled, and I suspect that there are periods when the control packets will not make it to the robot very often, causing the robot to enable/disable like shown.

Because the CPU usage is low, I wouldn't expect any issues reading keys or joystick, and a timeout will disable the robot. So I think the next thing to understand is why the code claims to be running auto.

Hope this helps.
Greg McKaskle