Quote:
Originally Posted by bob.wolff68
One of the tricky things about FRC programming is that the "no robot code" indicator is sometimes a misnomer. I would say it is highly likely that your code deployed and ran ... and crashed. I have seen this many times with my students.
What to do? RIO_LOG - is your friend.... You should have a tab at the bottom area in Eclipse which is rio_log. Select it, clear it, and then re-deploy - and watch what happens. You will likely get useful information about the crash.
What if that doesn't work? Use the DEBUGGER - Screensteps will take you through it step by step, but the basic concept is instead of "run-as -> Deploy" you'll instead use "Debug-As -> Deploy" and after a few gyrations in trying to get it running the first time (I remember there being some popup dialogs and seemingly errors the first couple times), then the gdb debugger will run your program and if you're crashing, it'll break right where the crash is occurring. It's very cool. 
Good luck and let us know!
bob |
Thanks for your response Bob! We have looked at the rio_logs before and really couldn't find any useful information to guide us how to fix this issue. Or maybe I just dont know how to interpret it right.
We have tried debugging it many times, and that doesn't fix the problem either.
On the other hand. This seemed to fix our issue. At the top of our code(under the robot class), we had this line:
Quote:
|
double Distance = enc.GetDistance();
|
Because we thought we had to have this included to get the encoder distance for our lift system.
But after we removed it. We no longer had any errors relating to the FrcUserProgram.
Im not really sure why this fixed our problem. We occasionally still get the error
"Remote command failed with exit status 1"
But the code deploys right. So we simply just ignore it. Thanks for everyones input! We greatly appreciate it!