I'm an involved participant in FTC, who needs to set up a simple robot with the new FTC kit. I have received all of my parts, and have also constructed a simple robot. My problem begins with getting the motor's to turn. I have followed the instructions on the website and have set up the parts according the picture one that came with the FTC kit. I have been able to isolate my problem to an issue between the NXT and the motor controllers, or the motor controllers and the motors themselves. There seems to be no communication up until this point. Please let me know if this is a known issue or if there is something that is common for people to miss?

In addition, the sample program for the FTC kit uses motor d and e, however on the NXT there are no such motors (just a-c) where to these ports map to?

Did you use the Motor and Sensor Setup wizard on the Robot menu to tell RobotC what stuff you plugged into what ports?

The instructions that came in the FTC kit have the motor controllers plugged into NXT Sensor Input 4. You can plug them into any port using ROBOTC, but by default, ROBOTC configures them to be in port 1. If your motor controller is plugged into port 4, try moving it to port 1.

Charge your 12V battery.

There is a feature to disable the motors when the external battery is low to prevent too deeply discharging the battery. The setting for this threshold appears to be too high a level. This may cause the motors from not moving.

See the 7th post in this topic http://www.robotc.net/forums/viewtopic.php?p=3396. for more information. I've repeated it below.

Both of above values are stored in flash memory. So they only have to be set once per firmware download.

i'am the programer for my team and we can get the two joystick program working with the bot that is only nxt when the moters are changed to "A" and "B" . but it work work when we try to move moters "D" and "E". we have changed the battery, changed the hook up to the exact book digram and tryed every port on the nxt. i can't even get the severos to work i poke you for infomation plz help

It sounds like you have a wiring problem.

Please post your program, including the #pragmas the Motor and Sensor Setup wizard created.

program is :
#pragma config(hubs, S1, HTMotor, HTServo, none, none)
#pragma config(Motor, motorD, , tmotorNormal, PIDControl, )
#pragma config(Motor, motorE, , tmotorNormal, PIDControl, )
//*!!code automatically generated by 'ROBOTC' configuration wizard !!*//

#include "JoystickDriver.c"

TJoystick joystick;

task main()
{
while (true)
{
getJoystickSettings (joystick) ;
motor[motorD] = joystick.joy1_y1;
motor[motorE] = joystick.joy1_y2;

if (joy1Btn(1))
{
motor[motorA] = 50;
}
else
{
motor[motorA] = 0;
}


}
}





now the button works because it is motor a, but for some reason the other motors don't. if i change D,E to A,B then thouse motors will work. if it a wire problem then what should it look like. a picture would be helpful cause right now it looks like the dieigram in the tetrix book. i poke you for information plz help
note i put in spaces but they won't show.

My guess is that you either have something wired incorrectly or your 12V battery is too low or not turned on.

Do you have your encoders installed on your robot? If not, you may want to go into "Motors and Sensor Setup" and disable the PID control.

Also, upgrade to ROBOTC 1.46... you don't need the "TJoystick joystick;" line anymore.

Also, make sure that you have the Joystick debugger window open, or else joystick messages won't be sent to your NXT.

there are incoders on one but that one won't run and in the debug windows the one that shown the statis of the motors the value for motors D/E is changeing but the motors won't turn at all and i keep changeing the battery but it won't work any way and the switch is on. we also have the program that they sent us for robotc. i poke you for information plz help
the sampul program is also different i had it attached to this post we also have the program that they sent us for robotc

Please verify that your wiring looks like the attached (corrected) diagram.

Update: The picture above is correct for the training and samples included with ROBOTC.

Thanks Jeff!

Thank you for pointing out the error in my diagram Tim. I have corrected the picture.

i conected it like the digram and it still does not work with motors attched and it is on i noticed somthing in the joystick sampule from robotc but it did not help. normaly when first brought up it says "error motor defined twice" then i deleted the motorD/motorE part and was left with: mtr_S1_C1_1/mtr_S1_C1_2. the encoders are also atached and hooked up. when i tryed to move the motors manuly throu nxt hook up window the normal nxt motors worked but when i tryed the D/E it sayed it was moveing but wasn't!!!! *in order*