[PhilBot]

When debugging the new environment, there are several things you can do to determine what's breaking down.

1) To debug the Bluetooth link and NXT code, you can do something OTHER than move the wheels... try displaying the motor drive value on the NXT display, or BEEP when a button is pressed. Make sure you have a link.

2) To debug the motor drive, you can hook up the motors and just pre program the NXT to turn the wheels. Forget about operator input. Make sure you can turn the wheels.

If you think the wheels should turn, but they don't... check the yellow fuse in the battery cable. Mine blew so there was no power going to the control module.

Another debugging tool is the LabVIEW debug mode. Instead of using the download and run button on the NXT Terminal, try the Debug button. After a few seconds the Labview front panel will become active. You can put some numbers or LED displays on it, hooked up to the internal NXT "wires". I like to display the incoming joystick values and the wheel drive values.

Bottom line, don't try to debug everything at once.... divide and conquor.

Phil.