Re: Programming Vex w/ MPLab
 

Your MPLAB version doesn't affect this problem. It's really a C18 Linker issue.
If you're seeing that particular error it means you are somehow pulling in pre-compiled object files that don't happen to match the compiler/linker version you are using, e.g., Vex_alltimers.lib.

What do you have set for your "Language Toolsuite" paths?
In MPLAB:
Project->Select Language Toolsuite...
then click on each of the tools: "MPLINK Object Linker" and "MPLAB C18 C Compiler" and verify the paths displayed under "Location."

Have you ever used your current setup with a full-sized robot controller or other PIC?

Without more information, such as the compiler/linker status output from a complete build from scratch, I'd recommend resetting all your paths to use everything that came with the vex kit, including the C18 compiler, e.g.,
C:\Program Files\Intelitek\easyC\Mcc18\bin\mcc18.exe
and mplink.exe.

Re: Programming Vex w/ MPLab
 

It worked, no build errors! Thank you very much.

Re: Programming Vex w/ MPLab
 

I'm having a bit of trouble getting this to work.
I set up a new project with the project wizard:
Device: PIC18F8520
Active Toolsuite: Microchip C18 Toolsuite
MPSAM Assembler: C:\Program Files\Microchip\MPASM Suite\MPAsmWin.exe
MPLINK Object Linker: C:\Program Files\Intelitek\easyC\Mcc18\bin\mplink.exe
MPLAB C18 Compiler: C:\Program Files\Intelitek\easyC\Mcc18\bin\mcc18.exe
MPLIB Librarian: C:\Program Files\Intelitek\easyC\Mcc18\bin\mplib.exe
Project Name: Vex Controller
Project Directory: C:\Documents and Settings\W4TK3\VexControllerProject

and I imported all the files from Vex Starter Code @ http://www.vexlabs.com/vex-robotics-downloads.shtml

I get the following output when I go to project>build all:

What's going on and where do I get the rest of the code? (missing part its complaining about)

Re: Programming Vex w/ MPLab
 

It looks like you missed specifying the path for your system include files.
The MPLAB checks to make shown in post #10 should help.

Re: Programming Vex w/ MPLab
 

Ok, I specified the path variables mentioned in post #10 and now I get the following (The error is at the end):

Do I have incompatible versions of something like the person above?

Re: Programming Vex w/ MPLab
 

Sorry, I got dragged away before I could finish my answer last night.

The root cause of the problem you see is there are way too many files included as part of the project. The Vex starter code folder actually contains several different projects and variations on the projects lumped together, making it confusing. There are multiple variations of the same file included in your project. When you run Project Wizard don't include every file in your project.
Here is a more readable version (well okay, "readable" is probably an overstatement. I just put each part of the command on a separate line) of the last link step of your compile that you posted, so I can point out what I mean about duplicate files. The files sharing common colors you only want one of in your project. There are others you also don't need, including the assembly file that actually gave you the current error.
I've attached a screen shot of the only files you should have in your project for starters (you can play with the differences later). Delete all the other entries from the MPLAB project by highlighting them in the MPLAB window and hitting "delete."

----------------
The actual error you got was because the assembler used is too new. It's producing the newer type of COFF. You would have seen other errors if you got past this one.

I assume that you are not writing your own assembly code? So you don't need to be including any assembly files.

Re: Programming Vex w/ MPLab
 

Mark--

Thanks! The build is successful now, the extra files were the problem.

A question, though, if and when we start to write our own code for the Vex bots , what files should be included and left out so that the build is successful? Or is any code we write just going to be modifications of the default files already outlined?

Thanks again.

Re: Programming Vex w/ MPLab
 

I'd suggest first starting with the basic working version of the code you have now and trying modifications to it. Save working copies of the whole folder periodically, so you can easily fallback to a working version if some of your changes go terribly wrong.

If you plan on making major changes, then I'd suggest you create brand new files to put all your customized code in. Then just add those new files to your existing project. You can add whatever you want to a project, just be careful not to add two versions of the same file or routine.
For instance, we put all our autonomous code in it's own file, and we put sensor specific code in a separate file of it's own. It makes it so much easier to reuse our code in new projects when we can just include a file, such as, Line_Follower.c.

When you advance to the point where you're comfortable replacing everything with your own code, you basically need to keep or provide your own version of most (not all) of the functionality found in the files that begin with "ifi_". You need a main.c, but you can rewrite it to fit your needs. You'll also need bits and pieces from user_routines.c and user_routines_fast.c, such as, User_Initialization() and the InterruptHandlerLow(). Probably the easiest course to follow would be to first replace specific routines with your own versions. For instance, the most obvious routine to begin modifying is Default_Routine(). That's where you setup all your driving controls and responses. The next obvious routine to replace is User_Autonomous_Code().

One caution about replacing existing files. There are special files included by the code with a C statement such as:
You'll see these "include" statements near the top of most c source files.
The compiler is going to go looking for a file by that exact name, in this example that would be "user_routines.h", regardless of what file name you may have used in the project list, so if you decided to replace the existing file by that name with one of your own devising and you call your's "my_user_routines.h" you'd better change all those include statements too, or the program will keep pulling in that old file even though it's not listed as part of your project.

Re: Programming Vex w/ MPLab
 

Is Brad's Library available? If so, under what project name? Thanks!

Re: Programming Vex w/ MPLab
 

I'm sorry I didn't check back in sooner on this thread (had exams a week or so ago). I came back today, checked the thread, and followed your instructions. Anyway thanks for your help, the build succeeded after I moved my folder to a different location (that pesky 62 byte limit).

Re: Programming Vex w/ MPLab
 

You can get rid of that also by changing a setting in MPLAB, so you can put your folder however deep you want.

Project -> Build Options... -> Project
Under the "MPLINK Linker" tab put a check by: Suppress COD-file generation

That's the sole reason for the 62 character limit and you don't use the COD file anyway.


At least you have something to do now that exams are over and done with.

Re: Programming Vex w/ MPLab
 

This might be a dumb question, but I was looking at this tutorial ( http://roboticsguy.com/tutorials/vex...with_mplab.php ) and it looks like to me that in order to program vex with MPLAB you need to buy EasyC ????? Is that true or am I missing something?? I think this because it says to navigate to a folder that belongs to EasyC. Thanks for any help!

Re: Programming Vex w/ MPLab
 

GGCO - Sorry for the confusion. No, you don't have to own EasyC. What you need is a copy of the C18 compiler and the WPI Lib(assuming you want to use Brads library).

So if you want to, download the student edition of Microchips C18 compiler here, and then download the WPI Lib here. You should still be able to follow that tutorial, just changing the file paths to wherever you install the software.

One note though. Even if you just get the trial of EasyC, I believe the C18 compiler still works after the IDE demo expires. So alternatively (probably easier) you could download the trial of EasyC and just follow the tutorial.

Short answer - No, don't need EasyC :D