Programming with the EDU

[Cuog]

I have a 2004 EDU robot controller that i am trying to use to start developing code at home(my team needs the large RC at school so they can start putting it on the robot) and the problem that i am having is that when i edit the default code and compile then add it to the RC it does not do what i want or it does nothing at all,

is there any sort of special areas to edit code for the EDU RC also i am not using a radio modem so i dont know if that will have some sort of effect on it.

[Eldarion]

I have a 2004 EDU robot controller that i am trying to use to start developing code at home(my team needs the large RC at school so they can start putting it on the robot) and the problem that i am having is that when i edit the default code and compile then add it to the RC it does not do what i want or it does nothing at all,

is there any sort of special areas to edit code for the EDU RC also i am not using a radio modem so i dont know if that will have some sort of effect on it.

The EDU RC is not cross-compatible with the full-size FRC controller. I would suggest using either the 2004 or the 2005 full-size RC for this application.

[Cuog]

I would love to get a full size RC but my team is dead set on not pirating from these 2 previous robots but i am pretty sure that the EDU can still be used for testing sensor algorithms right?

[CmptrGk]

are you adding the needed files to the edu's default code?

[Eldarion]

are you adding the needed files to the edu's default code?

I think you are talking about this thread: http://www.chiefdelphi.com/forums/showthread.php?t=42181

[Pat Fairbank]

In case you weren't aware, the EDU RC uses a slightly different default code than the full-size RC. It can be found on the IFI Legacy Docs page (http://www.ifirobotics.com/first-legacy.shtml) under "Mini RC".

Also, the EDU RC runs the code whether or not you have a radio modem hooked up to it.

[Cuog]

I took the EDU default code off of IFIRobotics.com and added a little addition to cycle the pwm01 up until it reached 255 and start over again and the pwm would just stay at 58.( i added this in default_routine then in procces data from local io and niether one worked)

[Mark McLeod]

If you post the EDU project we can help.
We're using the 2004 EDU to drive our prototype shooter's velocity control.

[Cuog]

I am using the project file i downloaded from the link Pat put up there then in Proccess_Data_From_Local_IO() i added the lines:

pwm01++;
if(pwm01 == 255)
{
pwm01 = 0;
}

[coldabert]

The EDU RC will run the same type of code as the full size RC. Just be sure to include all needed library and header files. Sensor algorithms can be tested by the EDU but be sure that any outputs are compatible with the hardware.

[Mark McLeod]

Process_Data_From_Local_IO() is definitely the wrong place to update a PWM. The PWM output will only change with each call to Putdata() inside Process_Data_From_Master_uP(), so move your code there.

Comment out the call to Default_Routine() unless you've disabled the pwm01 set in there.

I downloaded a fresh copy of the Edu default code and added your lines with a print in Process_Data_From_Master_uP(), commenting out the call to Default_Routines() so pwm01 doesn't get clobbered. I also attached a servo to pwm01 on the Edu for positive feedback that it works, and it happily ticks away, rewinds, and ticks away again.

[Cuog]

Ok since u have had the code work im going to go and upload what u just made and see if it works and if it doesnt then i will call up ifi since it will likely be a firmware problem, i have no idea if the EDU RC we have is any good since it has been sitting around for the past 2 years, and thanks everyone this will really get me moving on more advanced sensors since i can test now