poor little newbish programmer needing help

[Oumonkey]

We tried moving the joysticks everytime and the samething happened.
And I am almost positive that I was loading the right file. That was something I thought of and checked it out many times.

[Dave Scheck]

Josh

I am confident that the code is getting downloaded to the RC correctly, and that there is some other problem with your setup.

Since you're seeing the "x = 0 y = 0", try this...find the line in your code that is doing the console print. It will look something like

printf("x = %d y = %d",x,y);

Change the "x = " to "x2 = ", recompile and download your code. This time if you should see "x2 = 0 y = 0" scrolling on your console you know that your code is being downloaded correctly. (When you're done with this test, don't forget to change the x2 back to x)

Moving on, here is a list of things you may want to check...

1. Do you have the joystick in the right port? I think that the default code uses port 1.

2. Do you have the motors connected to the right outputs on the RC? The default will send the right drive signal to PWM13 and PWM 14 and the left drive signal to PWM 15 and PWM16.

3. PWM outputs 13-16 are a little different than 1-12 in that the user has to specifically generate the outputs. This is called as follows and should be found in the Process_Data_From_Master_uP function after the call to Default_Routine.

Generate_Pwms(pwm13,pwm14,pwm15,pwm16):

4. Is your robot enabled? Most teams create an enable/disable switch so that the robot can be safely disabled while debugging. If you aren't using one, I would highly suggest making one for your safety and the safety of anyone within arms reach of your robot. Plans can be found here

If you're still having problems after checking the above things, post your user_routines.c and we can take a closer look as to what your program's actually doing. (Don't forget to put it in a code block if you do)

By the way, Mark McLeod started a pretty good thread about starting to program FIRST robots. You may want to take a look here.

[Oumonkey]

Originally Posted by Dave Scheck

Josh

I am confident that the code is getting downloaded to the RC correctly, and that there is some other problem with your setup.

Since you're seeing the "x = 0 y = 0", try this...find the line in your code that is doing the console print. It will look something like

printf("x = %d y = %d",x,y);

Change the "x = " to "x2 = ", recompile and download your code. This time if you should see "x2 = 0 y = 0" scrolling on your console you know that your code is being downloaded correctly. (When you're done with this test, don't forget to change the x2 back to x)

Moving on, here is a list of things you may want to check...

1. Do you have the joystick in the right port? I think that the default code uses port 1.

2. Do you have the motors connected to the right outputs on the RC? The default will send the right drive signal to PWM13 and PWM 14 and the left drive signal to PWM 15 and PWM16.

3. PWM outputs 13-16 are a little different than 1-12 in that the user has to specifically generate the outputs. This is called as follows and should be found in the Process_Data_From_Master_uP function after the call to Default_Routine.

Generate_Pwms(pwm13,pwm14,pwm15,pwm16):

4. Is your robot enabled? Most teams create an enable/disable switch so that the robot can be safely disabled while debugging. If you aren't using one, I would highly suggest making one for your safety and the safety of anyone within arms reach of your robot. Plans can be found here

If you're still having problems after checking the above things, post your user_routines.c and we can take a closer look as to what your program's actually doing. (Don't forget to put it in a code block if you do)

By the way, Mark McLeod started a pretty good thread about starting to program FIRST robots. You may want to take a look here.

Well I am going to check everything cause I am about to go to my robotics meet in a few secs, but first
1. Ya we check the controllers in all the slots and it was the original code.
2 I am not personally sure but the person doing electrical says it in the right ones.
3I'll check this as soon as I can. My laptop didn't have the correct port to program into the bot so I had to use a different one so I am going to see If I can borrow it till after the competition.
4 I don't think we are using one but I'll talk it over with my electrical guy to see if we can do it.
I'll try and use a different code this time as well. Cause the code for the robot is the one from out last composition so he might have dint something different to it and I'll get a clean one from the website.

[Oumonkey]

OK, We got it fixed! A guy named Jason and Flo...Not sure how that is pronounced or if that is even right, I'm kinda tired and hyped up on caffeine. There wasn't anything wrong with the programming . Jason said the terminal window having all 0s had to do with the controller. Apparently something was wrong with one of the victors or the wiring and it runs now! ITS ALIVE!!!!
So thanks for the help guys. And know it looks like after seeing Jason work with the programming, he added some stuff and cleaned it up a bit, we will have another programmer
Thanks y'all!

[mechanicalbrain]

Glad to see you fixed up your problem.