Programming - Getting Started

[nehalita]

this helped me soooo much. thank you all. this is our second yr competing and this is my first year in FIRST. i have a java background and a simple C background from 8th grade...but it was so long ago.

I'm the only one in charge of programming so when i was handed all these Cd's and codes and links and websites, i was pretty overwhelmed. i just learned about this today and I've spend the majority of the day looking through posts to answer my Q's

is there anyone here that i can directly e-mail or talk to if i have questions? (warning: I'm like a pet, i demand a lot of attn: i have questions everyday....or close to it)

also, everyone speaks about a "dongle" and i saw the picture and everything. but what exactly IS it?

[Alan Anderson]

Originally Posted by nehalita

also, everyone speaks about a "dongle" and i saw the picture and everything. but what exactly IS it?

The Operator Interface (OI) has a 15-pin Competition Port connector in the middle of the top. Pins on that connector are used when running on a competition field to enable or disable the robot, select the radio modem frequency, and control autonomous mode. The field also supplies power to the OI through that port.

Teams are permitted to connect to four specific pins on the Competition Port, in order to 1) enable additional frequencies for practicing with multiple robots, 2) activate autonomous mode for testing, and 3) disable the robot. Most teams build a box with two or three switches that connects to the port. That box is called a dongle. The Competition Port Pinout Guide shows how to construct one.

[Mark McLeod]

Here's an updated version for this year with 2005 links included.

Programming Quick Start

• Beginners need the following to program the FIRST robot:

v FRC (Full-size Robot Controller) RC Default Code

v Microchip MPLAB & C compiler



v IFI_Loader
v A standard serial cable
v A Windows PC with a serial port or USB-to-serial converter

• All default code, updates, documentation, and support information is available at http://www.ifirobotics.com/rc.shtml and http://www.ifirobotics.com/oi.shtml , the Innovation FIRST (IFI) website, The 2005 default code http://www.ifirobotics.com/docs/frc-code-1-12-2005v2.2.zip comes ready for basic driving and with a variety of sample I/O usages. Optional 2005 default code is also available for use with the CMU camera http://www.ifirobotics.com/docs/frc-code-1-12-2005v2.4.zip. Consult the CMU documentation for other requirements. Useful software examples and documentation, as well as the demonstration code used at kickoff can be found at Kevin Watson’s website http://kevin.org/frc/ .

• MPLAB is the FIRST supplied Windows based development environment (edit, compile, debug) that runs on your desktop computer and is usually provided to each team on a compact disk in the Robovation kit. MPLAB v7.0 is also free on-line at the Microchip website http://microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName =en019469&part=SW007002 , but the C compiler is not free except via the Robovation CD and is normally only available online as a time-limited trial copy or for purchase. For a limited time the latest compiler is available from a link on http://www.usfirst.org/ (bottom left of the page where it says “Microchip Software downloads”). After the link is removed the latest compiler must be obtained through FIRST.Manuals for using MPLAB come on the FIRST CD.

• IFI_Loader (from the CD or IFI website http://www.ifirobotics.com/docs/ifi-loader-v1-0-10.zip) is used to download the compiled code into the RC via a serial cable from your desktop or laptop computer.

• Check the IFI website periodically for updates to the software that corrects issues and fixes problems. For instance, the first update that must be performed is the downloading of a new Master Controller “patch” http://www.ifirobotics.com/docs/master-software-ver10.zip . Follow directions included with the download.

• The programming language used is “C” or PIC assembly. Tutorials in C can be found on the web, in your local bookstore or on the FIRST website, e.g.,

v C Programming Resource Library http://www.usfirst.org/robotics/C_help.htm has a great overview of the programming process.
v Learn C Programming - Developed by Carnegie Mellon and the National Robotics Engineering Consortium specifically for FIRST, this interactive website will get your team prepared for the FIRST Robotics Competition. http://www.rec.ri.cmu.edu/education/robot_builder/

v FIRST Robovation - A Primer for Success Learning Modules http://www.usfirst.org/robotics/robovation/primer/index.html

• Newer laptops no longer come with serial ports. If you have this problem one solution is to use a USB/Serial converter. Various models are available at Radio Shack, CompUSA, or online, however, some models can be temperamental and they generally take longer to download than a built-in serial port (60sec vs 10 sec). Good results have been reported using: Bafo Technologies BF-810 (~$15) and a Radio Shack USB-to-Serial port cable #26-183 ($42).

• Documentation is your friend. Take the time to at least leaf through each manual, so you have an idea of where information can be found. Most of the basic information beginners require can be found in the IFI documents or MPLAB documents available from the websites:
  • IFI Quick Start and Overview documents, the 2004 versions apply to 2005 as well http://www.ifirobotics.com/docs/frc_system_quick_start_2004-1-14.pdfhttp://www.ifirobotics.com/docs/control-system-overview-2004-01-07.pdf
  • IFI Programming Reference Guide – basic how to hookup, program and download to the RC, hookup switches and sensors and do normal robot operations. http://www.ifirobotics.com/docs/rc-ref-guide-2005-revnc2.pdf
  • Useful programming and compiler documents come with the tool installations or are available from the Microchip website. http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName =en010014 or http://microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName =en019469&part=SW007002

v c18_getting_started_2.4.pdf http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_C18_Getting_Started_51295d.pdf
v c18_libraries_2.4.pdf – details on timers, interrupts, and various other utility functions available to the programmer. http://ww1.microchip.com/downloads/en/DeviceDoc/C18_Lib_51297d.pdf

v c18_users_guide_2.4.pdf - table of max numbers each variable type will store, compiler options, error messages, detailed descriptions of pragmas and some other advanced topics. http://ww1.microchip.com/downloads/en/DeviceDoc/C18_UG__51288e.pdf

v Microchip pic18f8520 data sheet - PIC assembly instruction set and details on EEPROM and other chip specific topics, and several others. http://ww1.microchip.com/downloads/en/DeviceDoc/39609b.pdf and mistakes in the datasheet http://ww1.microchip.com/downloads/en/DeviceDoc/80157d.pdf

v Microchip PICmicro 18C MCU Family Reference Manual – all things great and small (in excruciating detail) about the processor we use. http://ww1.microchip.com/downloads/en/DeviceDoc/39500a.pdf

v MPLAB Quick Start Guide.pdf - basic how to use MPLAB and set options. http://ww1.microchip.com/downloads/en/DeviceDoc/51281d.pdf

v MPLAB Users Guide.pdf http://ww1.microchip.com/downloads/en/DeviceDoc/51519a.pdf

• Programming limits to the 2004 RC:
  • 30,720 bytes of program space is available to the user, after 2004 IFI code.
  • 1,343 bytes of ram available to the user, after 2004 code overhead.
  • 256 bytes of global variables available within any one MPLAB project file, such as user_routines.c
  • 120 bytes of variables can be declared within any single routine.
• The program and data space your code has used can be checked either by the status line at the bottom of the IFI_Loader window or via the optional .map file that you can set MPLAB to generate for you. Note: the .map file lists % of program space used, but the user will have only 90% available to him or her. The .hex is ASCII and file size is no indication of code size.

Visit the ChiefDelphi Programming forum for discussions on all programming topics, problems, and issues http://www.chiefdelphi.com/forums

[katkana]

*waves hand* hi... I'm another of the newbies with little (read, none) experience working with C. I am also the only one on my team doing the programming dance. At the moment I'm teaching myself from whatever tutorials I can find, but if anyone can spare a moment or ten through e-mail or IM to answer my questions, I would be muchly indebted to you.

AIM- daemonlvr856
e-mail- krystal_dragon9@yahoo.com

THANK YOU!!!

~kat

[695programmer]

I'm another newbie, with probably less experience than the other two and just as hopeful maybe someone could give me some time cause i'm running into problems i don't know how to solve. Any help is welcome via im or e-mail or anything.

Team 695

[695programmer]

I have another one i forgot about, when I try to build the error is that it can't locate the build tool, any insight?

[russell]

I really am a newbie. Heres proof. Can I call the function Limit_Mix as it exists in the v2.4 code from the autonomous mode section of user_routines_fast.c? I was under the impression that I can, but when I just tried to compile it gave me warnings about no function prototype (whatever that is ), but it seems to have compiled anyway. Anyone?

[Matt_Kitts]

can anyone help me out with programming the buttons on the joy sticks`

[Mark McLeod]

Originally Posted by Matt_Kitts

can anyone help me out with programming the buttons on the joy sticks`

Each OI joystick port has the 2005 KoP joystick buttons available in the default code as follows:
For Joystick Port 1:

• p1_sw_top - thumb button
• p1_sw_trig - trigger button
• p1_sw_aux1 - button to the left of the "hat" switch on the front face
• p1_sw_aux2 - button to the right of the "hat" switch on the front face

The other Port buttons follow the same naming convention, e.g.,
p2_sw_top would be on joystick Port 2, p3_sw_top on Port 3, etc.

They are used in your code like this:

if (p2_sw_top == 1)
printf("Hello FIRST\r");
else
printf("Goodbye cruel world\r");

There are also two analog inputs unused by the KoP joystick and the analog "hat" switch (that returns odd values).

[RIgnazio]

also, everyone speaks about a "dongle" and i saw the picture and everything. but what exactly IS it?

A dongle can be made with a RS-232 (serial) end, specifically the metal part. If you look at it, there are pins you can solder wires too. What you should do is solder a wire to each pin that would complete the circuit in the Pin Layout for the RC. Now, instead of just attaching a wire and having done it (the easy way) attach a push button switch that is normally in the off or open position. When you press it, (15 seconds), it will simulate the signal that the FIRST computer sends to the robots to start autnomous. When you let go, autonomous will be over and the robot will be live.

Now, why do you say use a switch you may wonder? And why use a normally off/open switch? If your robot goes on an evil plot to kill you and you start to run away, you will let go of the switch, and the robot won't do autonomous anymore.

OK, newcomers, there are a few tips that I myself have:

1. Programming takes time. If it doesn't work correctly/compile on the first attempt, and you can't figure out what is wrong, Save the file, close out MPLAB, and go do something for an hour then come back. It will probably hit you then.

2. Pay attention to the default code. It is your friend. It will tell you just about absolutely everything you need to know to program the robot.

3. Autonomous mode is not hard, you just need to think about it. Remember, there is a 40ms clock in the RC, so 1 second = 26.2ms. This would be a good time for a calculator.

4. NEVER DELETE OLD CODE.

5. Always put new code, even if you're only changing a comment, in a new folder. SAVE AN ENTIRE SEPARATE COPY!

6. NEVER DELETE OLD CODE.

Those should be your ground rules. Enjoy

[Matt Krass]

Originally Posted by RIgnazio

If your robot goes on an evil plot to kill you and you start to run away, you will let go of the switch, and the robot won't do autonomous anymore.

Funny, the guy we had holding our kill switch seemed oddly fascinated with the robots attempt to kill our teachers 7 year old son, so fascinated he held the switch tightly, preventing us from intervening and killing it. Until of course we realized we could just..unplug the dongle...yeeeeah.

Originally Posted by RIgnazio

3. Autonomous mode is not hard, you just need to think about it. Remember, there is a 40ms clock in the RC, so 1 second = 40ms. This would be a good time for a calculator.

I'm assuming you meant 1 cycle = 26.2ms

I'm not sure where you got 40ms, but my memory is bad, and I remember two loops running in the RC, perhaps you're referring to a separate one than I am.

[Budster]

>> 3. Autonomous mode is not hard, you just need to think about it. Remember, there is a 40ms clock in the RC, so 1 second = 26.2ms. This would be a good time for a calculator.

Maybe it should read 40MHZ clock in the RC.
There is a 26.2ms sample time in the outer/main loop where you get new input from the operator station so in 1 second that is 40hz, i.e. 40 samples per second (actually is 28.167...hz, but 40hz is probably close enough)? Not really sure what the intent was, I'm having trouble parsing the line.

Bud

[mallot1243]

who knows which files are allowed to be transferred to the bot. ie <stdio.c>

[Mark McLeod]

Originally Posted by mallot1243

who knows which files are allowed to be transferred to the bot. ie <stdio.c>

You are allowed to use any files in your project you like, even write your own as long as you include the ifi required libraries and supporting include files.

However, be aware that the PIC is limited in it's capabilities and will not support or fully support the functions you may want to use in a typical stdio.c file. You can't just drag one in from a PC and expect it to work. You can check the documentation (C:\mcc18\doc) to see what is supported by the C18 compiler.
The document that might interest you for the C18 v2.4 compiler is at:
http://ww1.microchip.com/downloads/e...Lib_51297d.pdf

[mallot1243]

thanx