What are we supposed to do!?!?!?!??!?!

[Bomberofdoom]

Yes, I know about the PWM numbers of forward and backwards and I'm expirienced with C(even with Visual c++), but what am I supposed to do now? You say the drive system is easy, but I don't understand what am I supposed to look at that it shows that it's easy!
I've asked someone from another team in my country and from what I understood, he said that it is all written there.
But I don't see it! I only see that they put the values of p1_y(which is what?!?!) to pwm01 and all kind of other stuff, but I don't see anything with number values(mabye except with the leds). Is that where I'm supposed to write the engines part??

[P1d40n3]

Originally Posted by Bomberofdoom

Yes, I know about the PWM numbers of forward and backwards and I'm expirienced with C(even with Visual c++), but what am I supposed to do now? You say the drive system is easy, but I don't understand what am I supposed to look at that it shows that it's easy!
I've asked someone from another team in my country and from what I understood, he said that it is all written there.
But I don't see it! I only see that they put the values of p1_y(which is what?!?!) to pwm01 and all kind of other stuff, but I don't see anything with number values(mabye except with the leds). Is that where I'm supposed to write the engines part??

p1_y -> Port 1's y-axis (Ie: The y-axis of the joystick plugged into port 1)

pwm01 -> this is the code representation of PWM01 on the RC

the code pwm01 = p1_y would map the y-axis of port 1's joystick to PWM output 1.

I recommend the RC Reference guide, found here. Reading that should answer your questions.

[SoD]

Hello, I am from team 2230 too.

We have a default code in our mplab program (like everyone else).
What are we supposed to change in it? It seem to be quite complete

[Matt Krass]

There is a function in user_routines.c called Default_Routine(). This is basically your playground, this function runs about 38 times a second (26.2 milliseconds) and you put all your logic in here. Your OI data (joystick values, buttons pushed) is all available in aptly named variables (p1_y, p2_x, p2_sw_trig, etc) that you can check with if statements. For example to make the trigger on the joystick connected to Port 1 drive the robot forward and your motors are on pwm01 and pwm02 you might try this:

// in Default_Routine()
...
	if(p1_sw_trig) // If the trigger is pushed
	{
		pwm01 = 255; // Left motor full speed forward
		pwm02 = 0; // Right motor full reverse since it's likely facing the  opposite direction
	}
	else // Trigger is not pushed
	{
		pwm01 = 127; // Motor stopped;
		pwm02 = 127; // Motor stopped;
	}

Note this is not a recommend way to drive, you're better off mapping the pwm outputs to the joystick inputs like this:

...
pwm01 = p1_y;

That should be enough for you to get started, it's all just basic logic.
Good luck!

[Bomberofdoom]

Ok, so I read about the joystick movment thing.
Do we need to build that code of if's? Do we need to make these macros to check the joystick axis status?

[Matt Krass]

Originally Posted by Bomberofdoom

Ok, so I read about the joystick movment thing.
Do we need to build that code of if's? Do we need to make these macros to check the joystick axis status?

Every loop the controller updates the values in the P*_* variables, including axes and buttons. All you have to do is use logic on the values and set your pwm** variables.

[Bomberofdoom]

What do you mean by setting our own PWM** values?

[SoD]

Ok thanks alot for your help.

What do we have exactly in our code allready, and what should we use with it?