We are attempting to use the Joystick1.c sample program, but the robot is not responding. It compiles and downloads to the NXT, we open the joystick debugger window (simple) and see x and y values, but after starting the program, no response from the motors. Which platform type should be selected? Do we need to use a template, or should the program run as-is? Just getting started......

Thanks, Will

PS..Just noticed that the NXT brick window displays a line about wait for start, even after we click Start in the debugger window??

The easiest way to ensure that your robot isn't waiting for start is to comment out or not include waitForStart(); until late in your development curve. If it still doesn't respond, that's not your problem. You can also try:

Connecting by USB instead of bluetooth

Use joystick debug (game) instead of simple

If all else fails, erase everything on the robot and re-download the latest firmware.

Unfortunately, I think that particular sample file needs to be deleted. For one, it has the motor control lines commented out which is why you do not see any response from the motors.
Here is a better basic example:

This code should do what you were expecting from Joystick1.c, but is pretty trivial and limited in usefulness. For example, it does not properly scale the joystick analog stick values (-127 to 128) to the motor range (-100 to 100).

Assuming you are in fact competing in FTC: Lego Mindstorms NXT + Tetrix

You can run the program as is for now, but will need to use the autonomous and teleop templates available at http://www.ftctraining.com to be competition legal.


What I would recommend is to watch the videos and read the documentation available at:
http://www.ftctraining.com
http://www.robotc.net/content/webinar/index.html
http://www.education.rec.ri.cmu.edu/content/lego/index.htm
That should answer a lot of your initial questions to help get you up and running.

Thanks for the help. As it turns out, I needed to set the joystick control panel to TeleOp Run, I did not notice those radio buttons........Problem solved though!

Will