Quote:
Originally Posted by BuzzKillerOfFir
Our roborio is being detected, but is only accepting code for a second, after that it switches between no code and teleop disabled. We were able to enable teleop for a fraction of a second, and heard the compressor turn on.
|
It sounds like your code is dying. Some of our rookie programmers have been having the same problem, and it always turns out they've dereferenced a null or uninitialized pointer.
You can check this by ssh'ing into the roboRIO
Code:
ssh admin@roborio-XXXX-frc.local.
You probably have no password set.
See if your robot code is running (I bet it isn't):
Code:
ps -ef | grep -i frcuserprogram
If it's not running, all you'll see in that listing is "grep -i frcuserprogram". If it IS running, kill that process:
Code:
killall FRCUserProgram
Then run it manually
Code:
cd /home/lvuser
./FRCUserProgram &
Try driving your robot. When it fails, look in the ssh window and see what error shows up. If you see "Segmentation Fault" or "Bus Error", you've done something wrong with a pointer or a reference. It's time to get together with your mentor for a code review.
(This is how we all learn. If someone ever claims to be a C or C++ programmer but tells you they've never had problems with pointers, they're a fraud, and you should run away.)