SetPWM and our IR controls

[ham90mack]

It appears that that may work, except there is no such function as SetPWM in Kevin's code. Instead, use:

pwm01 = 65;
pwm02 = 192;

So your code appears to do one thing: if the first programmed IR signal is sent, drive forward forever (or spin forever, depending on how your motors are mounted). That sounds a little dangerous for a first test unless your robot is off the ground. I suggest having a signal to stop the robot as well.

[Vanquish]

Originally Posted by ham90mack

It appears that that may work, except there is no such function as SetPWM in Kevin's code. Instead, use:

pwm01 = 65;
pwm02 = 192;

So your code appears to do one thing: if the first programmed IR signal is sent, drive forward forever (or spin forever, depending on how your motors are mounted). That sounds a little dangerous for a first test unless your robot is off the ground. I suggest having a signal to stop the robot as well.

Yea, I realize that I just wanted to know if the format looked alright, thanks

[taggartbg]

Hey guys, thanks for the help, I think i'm getting there; however, I'm still having some struggles.

I'm begining to think that I'm just doing something really simple wrong. Here is the process I undergo to test my code.

1) Code in easyC Pro in the OperatorControl function (I've also tried in Autonomous)
2) Power up robot
3) Hold down "prog" until the "Program Status" LED turns a solid orange
4) In easyC, I hit Build & Download
5) Once it is loaded, I power down the bot
6) When I power it back up, the code should automatically execute, yes?

[Branden Ghena]

Do you have a operator interface hooked up?

[laultima]

Originally Posted by tawnos23

Do you have a operator interface hooked up?

you do need the OI connected to the RC either by radio or tether before the code will run

[itsme]

Make sure you put your OperatorControl function inside the main function.
And I don't think you have to power down your robot, it should automaticly work well.
Make sure you are not programming in competition mode (when it's divided to 3 functions). 'Cause that way I don't think it can work (I think it only works when you are in a competition [when the competition port on the OI is connected]).
Just to the following:
1) Open a regular new EasyC pro project.
2) Make your OperatorControl function (in the user functions).
3) Drag and drop the OperatorControl function you just made into a while(1) loop in the main function.
4) Power up the robot.
5) Hold down "prog" until "Program Status" LED turns orange.
6) Press Build and Download in EasyC pro.
7) Now it should work

I suggest you first build and download a simple program (like putting your motor in half speed) and check if it works well.
Again, check if the PWM cables are connected to the victor that is connected to the motor you want to activate.
Hope it helped.
Team 2217

[taggartbg]

AHH! I've been creating competition projects ...I'll post back when I get a chance to create a standalone and try it out.

Thanks again.

[Branden Ghena]

A competition program will work if you plug a switch into the competition port that enables the robot.

[itsme]

Originally Posted by tawnos23

A competition program will work if you plug a switch into the competition port that enables the robot.

Oh sorry, forgot about that..
But I'm guessing taggartbg didn't do that either (correct me if I'm wrong).

[taggartbg]

Hey everybody,

Thanks for all you're help, our code is up and functional now, thank you

/Taggart