[Alan Anderson]

Originally Posted by gamegeek1995

http://www.applepirobotics.org/wp-co...l Tutorial.pdf

There are two things wrong with following that tutorial. First, it carefully tells you to enter the cRIO's IP address as 10.0.0.2 when creating the project, and even repeats it when telling you to make a new VI to play with. That's wrong -- the middle two octets shouldn't be zeros. They need to match your team number. In your case, it should be 10.47.1.2 instead. That error would keep you from being able to connect to the cRIO in order to send it a program.

Second, it's just a quick example of using the motor functions. It won't work in a competition environment. You need to use the framework (which is there but ignored by the tutorial) in order to create a program that will let you control the robot properly.

Is there any hack-y work around to get the thing to run, even with the current glitched "SmartDashboard" (what program is this? Is it on the Netbook, the robot, or what? Not sure if I've seen anything like this.)

SmartDashboard is a data-sharing scheme built on top of the Network Tables communication protocol. When you run a robot program on the cRIO, it starts a server process. Client programs on other computers connect to it in order to send and receive shared data. The stuff on the Classmate screen is actually two programs; the Driver Station program is the bottom third, and the Dashboard is the top part with the camera view window and various joystick and motor status indicators. The Dashboard program sends and receives SmartDashboard data to and from the robot program. There's a bug right now that keeps the robot from accepting a new program if the Dashboard is running, so you will need to shut down the Dashboard first (the simplest way is to temporarily select "remote dashboard" on the Driver Station's Configuration tab).

And also, referring to "If by some chance you didn't select the checkbox to "always run deployed code" when you reimaged the cRIO, code that you Deploy won't actually be run when the cRIO starts up. To ensure that your code gets run on startup, use the "Run as startup" command instead of the "Deploy" command."
I indeed did not select the checkbox to always run eployed code. Should I go back and do that? Or is that inconsequential to my current issue?

It shouldn't matter, as long as you always follow "Build" by "Run as startup". There's never really a reason to use "Deploy" that I can think of. But if you want to make things a teeny bit more error-proof, you should take the few minutes necessary to set that checkbox.

Finally, my problem seems to be the exact same as BitTwiddler's (save the fact that I've yet to get any movement- not sure if he was able to achieve that).

Your problem is probably that you're following a tutorial example that isn't strictly relevant to the task of programming a competition-ready robot. Try this documentation instead.

Also look at the Tutorials that were included when you installed LabVIEW. On the "FRC 2013 Getting Started" window that appears when you launch LabVIEW, choose the Tutorials tab at the left side. You'll want to read Tutorials 4 and 5.