Quote:
Originally Posted by Greg McKaskle
Jared, can you find two log files of the two states? One that is the correct procedure with the warm boot and another with the code start.
Post all three files, .dslog, .dsevent, and .pdplog. If it isn't easy to post to CD, PM me and I'll give you a place. I think they may help indicate what ran differently.
Greg McKaskle
|
Currently, I've only got the log files I've saved to my home computer.
From those, I've found one sequence of events that may help.
The first log file (2015_03_01 13_06_11 Sun) shows the robot connecting while tethered (cold boot), and enabled in teleop for a few seconds to adjust the elevator. There was a significant amount of control lag here, and if we had run autonomous, we would have had a problem. The dsevents file shows that I requested robot code restart at the end.
The next log file is when the code restarts and connects while I was tethered and in line, but is saved at the school computer.
Finally, I have the connection to the field (warm boot), where we play our match and things run well. This is the 2015_03_01 13_23_59 Sun file.
It makes sense that the CPU usage is high, as the controller is attempting to run the PID and drive controllers as fast as possible to catch up.
https://drive.google.com/folderview?...1U&usp=sharing