100% cpu and twitchy too

[Greg McKaskle]

If you didn't explicitly Open and enable the watchdog, you do not need to feed it. Watchdogs are a useful concept for making systems safe, but a few years ago, all languages moved the watchdog underneath the RobotDrive and other outputs and made the feed be a part of the update.

I agree that your teleop isn't causing the CPU usage or the twitches, but since I haven't seen the rest of your code, I can't tell you where the issue is. If you want to solve it yourself, look at vision and periodic tasks. Specifically, look for code that is setting the twitchy motors in parallel with teleop.

Greg McKaskle

[Peck]

Just a quick recommendation, cheek the wireless in the area, The driver station says cpu is at 100% as a default when you loose the packets related to cpu level. If there are to many wirelesses on the same frequency, connection starts to suffer (yes, that is the reason for the no unnecessary wireless networks in competition area) and that can manifest as packet loss which can cause the cpu to show 100% and can also give you microscopically small loss of coms which results in a twitchy robot.

[Greg McKaskle]

Actually, if packets are lost, CPU usage usually drops. This is true for the default LV framework, and I believe for C++ and Java too. If packets don't arrive, some parts of the system will run timed tasks, but other portions will stay asleep.

While it is possible for an excessive number of wifi networks to impact the connection to the robot, especially on 2.4 GHz, this will not cause CPU usage to rise on the robot. The charts tab will show whether the robot is losing comms, getting watchdogged, or running as prescribed. If you post a photo of the log file viewer, I can help point out the patterns.

Greg McKaskle

[Peck]

Originally Posted by Greg McKaskle

Actually, if packets are lost, CPU usage usually drops. This is true for the default LV framework, and I believe for C++ and Java too. If packets don't arrive, some parts of the system will run timed tasks, but other portions will stay asleep.

While it is possible for an excessive number of wifi networks to impact the connection to the robot, especially on 2.4 GHz, this will not cause CPU usage to rise on the robot. The charts tab will show whether the robot is losing comms, getting watchdogged, or running as prescribed. If you post a photo of the log file viewer, I can help point out the patterns.

Greg McKaskle

kk, i was speaking on what the software sub team told me to watch for when driving the robot at our regional. they may have altered something.