Investigate and fix loop overrun warnings

first95 / FRC2020

Code base for 2020 robot, initialized with develop branch of 2019 repo.

MIT License

1 stars 1 forks source link

Investigate and fix loop overrun warnings #3

Open jwalthour opened 5 years ago

jwalthour commented 5 years ago

For some reason, our main loop sometimes takes too long to run. It's no longer keeping our robot from working, but it could cause us problems in the future.

Possible causes:

We may have unnecessary CAN interactions. For example, maybe we are applying PIDF coefficients from the smartdashboard every iteration.
We should check for any loops doing a lot more things than necessary
Are we doing any kind of data logging right now?
Maybe we're sending too many items up to the smartdashboard?

jwalthour commented 5 years ago

Someone from CTRE requested we collect some information regarding the issues we've been seeing. We should collect this if/when an opportunity arises: https://www.chiefdelphi.com/t/frc-95-the-grasshoppers-2019-build-thread/338781/139

If nothing else, we should save off and examine a log from the smartdashboard.

NHDinosaur commented 4 years ago

This sounds like something we should fix for 2020

lindsayvallen commented 4 years ago

Note that there's a comment about this issue in the blog post below where it stresses that this is a warning and not an error, and that it results from a Watchdog that was added in 2019 (hence not seeing it previously). I suspect this mention (especially the bold text) means that a lot of teams may have experienced it this season.

https://wpilib.screenstepslive.com/s/currentCS/m/getting_started/l/1028812-new-for-2019

lindsayvallen commented 4 years ago

Iceboxing this issue until determine whether it occurs again this year.