[FTC]: Can anyone lend assistance?

[HAL3019]

@BLAQ: Yes... I am a twitterbug XD (guess its sticking... hope this doesnt affect my VB code)... and how would I go about compiling my code- because I became accustomed to last year's build and am having a bit of difficulty converting.

@Chris: I have a couple designs for the pickup and storage... but am having issues with the mounting of the NXT and battery. would you know of any method to go about mounting these, because we current have our battery in a clip between our two back motors (this makes me nervous, our team has poor luck with the tabs on the motors).

[BLAQmx]

You can build your VI into an RXE file in one of three ways, but all require the VI to be targeted to the NXT. This is done by navigating to File»Target to NXT. Please be sure to have your NXT turned on and connected to the computer when doing this. If you are using a USB connection LabVIEW should automatically find the NXT. If you are connected via Bluetooth and have not established the Bluetooth connection in LabVIEW yet you will be prompted to establish connection (just follow the on screen instructions).

Once you are connected to your NXT (you should see your NXT's name in the bottom left-hand corner of the block diagram and front panel windows) you can either press the Run, Deploy, or Debug button. All of these will compile you code and automatically download the RXE file to the brick. The functional difference between these 3 buttons is as follows.

Run: Compiles, downloads, and immediately begins running the program.
Deploy: Compiles and downloads the program.
Debug: Compiles, downloads, and immediately begins running the program. The front panel window for the VI goes into a run state and Front Panel controls and indicators can be used to interact with the program running on the brick.

[HAL3019]

Originally Posted by BLAQmx

Once you are connected to your NXT (you should see your NXT's name in the bottom left-hand corner of the block diagram and front panel windows) you can either press the Run, Deploy, or Debug button. All of these will compile you code and automatically download the RXE file to the brick. The functional difference between these 3 buttons is as follows.

Run: Compiles, downloads, and immediately begins running the program.
Deploy: Compiles and downloads the program.
Debug: Compiles, downloads, and immediately begins running the program. The front panel window for the VI goes into a run state and Front Panel controls and indicators can be used to interact with the program running on the brick.

Okay thank you (finally found the quotes!) now could you... recommend (?) any programming methods for this year? (ie. conditions, loops, nxt usage)
And the template installed w/ LV is the template that we should be using, right?

[BLAQmx]

I recommend using the templates. The most essential part of the teleop templates is the communication loop. If you decide against using the templates please use the same communication loop in your code. Great care was taken to optimize this loop to give the greatest possible remote control over the robot.

I recommend beginning your development with your VIs targeted to the computer. This will allow you to utilize the full suite of LabVIEW debugging tools (Highlight execution, single stepping etc). Once you have your code working you should then target the VI to the NXT deploy the code to the brick.

When developing code with the VI targeted to your computer try to stick to the NXT programming palette when adding structures, functions, etc. This will prevent you from writing code with an unsupported function that will throw a 1003 error at compile time.