The logs and drive station dashboards have a continual output of CommandScheduler loop overrun errors that makes it hard to see anything else going on, and likely are a signal that there's robot responsiveness latency caused by the command loop frequently running over its allotted 20ms (0.02s)