No Robot Code EVER -- Help Please

[Mark McLeod]

Originally Posted by Mark McLeod

If you are using C++ or Java, then fire up Netconsole to see why the code is crashing.

What did it show?

Originally Posted by cjlane1138

Sorry everyone, I forgot to tell you guys that we are coding in C++, not LabView.

Post in the C++ sub-forum next time and you'll get more help.

[Greg McKaskle]

My guess is that the code is crashing very early in its execution. The Robot Code LED is based on getting data from the user framework code via the FRC_Communications.out file.

As others have said, you'll get more help from the C++ forums, but I'd try to use the debugging tools, even just placing print statements every five or ten lines to see how far you are getting will help. STOBbing is another technique many developers find helpful. It stands fore Sync To Old Builds. You use source code control to return to previous builds and determine if the problem existed there. Then you diff the changes you've made in a few at a time to identify the culprit. Personally I find it quicker and more exciting to debug, but both are ways to make progress.

Greg McKaskle

[lscime]

Make sure all of the DIP switches on the front of cRIO are in the correct orientation (one of them may have accidentally changed since the time when you last saw your robot working). In particular make sure that the "No App" switch is in the "off" position.