Re: Ye old IFI
 

Surface-charged battery is what we think the problem was (they may have also had heat damage); the motors would start running when told to at the start of the match, but the controller would cut out. The motors would keep running, and yes, that's keep running, at a slow speed, and the E-stop could NOT stop the robot. So there would be someone pushing the E-stop, and the robot would keep driving without anybody at the controls.

You might not see how it could be true, but that's what happened. That's one of the reasons the backup battery was put in place; that came in in 2004. The purpose of the backup battery was to maintain power to the controller so that you could stop the robot remotely--it's not intended to provide enough power to drive around, just to maintain communication. So after 2004, it was a non-issue due to the backup battery.

Re: Ye old IFI
 

I certainly disagree about the purpose of the backup battery.
It only saves the robot from rebooting in the middle of a match when the robot main battery voltage dips. Something that doesn't matter in demo presentations. We use the old controllers constantly and have never included the backup batteries.

That would have been a really bad band-aid if it was to solve a runaway robot problem (from a different generation of control system). It would be a very high risk solution to depend on teams running with a charged backup battery if they couldn't be depended on to run with a charged main battery either.
Estop plays no part. That only works in any case if the robot controller from any generation is listening and responsive.
I do know ways to accidentally power the speed controllers while the Basic Stamp RC from that generation is disabled, but I'd lean towards a corrupted Master controller program allowing that to happen. Which could have been caused by low voltage, but the solution is a circuit/master code redesign.

Re: Ye old IFI
 

Folks,

Like others in this thread, we've been asked to get our students to resurrect an old IFI controlled robot and get it in shape for demos and fundraising events....
The robot we have, has code on it, and runs, but only had limited functions. The marketing folks came to me and said, "Make it So"...or, get it to work and do what we want. I was not mentoring the team during those days and am once again looking at a "black box" I've got to figure out.
The posts here have been very useful, but I am having a very hard time finding the MPLAB V ~7..C 18.....2.4 software. Which if I understand it, has the bulk of the basic code required in files.

Would someone be kind enough to find me a link to that, and apparently the correct or corresponding IFI loader software. There are a considerable number of links out there to MPLAB software, but it's hard to sort through the stuff.

Thanks in advance,
Doc

Re: Ye old IFI
 

Not sure if this would help any Doc, but we used RobotC to program our 2008 robot, which was the last one to use the IFI system.

Re: Ye old IFI
 

vexrobotics.com ;) just sayin ...

Re: Ye old IFI
 

If RobotC can do it, and if it has the bulk of the example code in one of the .h files I'll give it a try. Again, where do I get it?

I've just read conflicting material about the software needed for the RC (I believe this is a 2004 unit).

Once again folks, I'm operating out of ignorance...anything you can post to enlighten me is appreciated.

And yes, I've checked VEX and for $50 I can supposedly get the disk...but will that one work and will it have the example code for FRC robots?

Re: Ye old IFI
 

OK, we'll see if I can remember info from that far back.

2004 units did not have the same compiler/MPLab/whatever else as 2008 units. The good news, they were programmed in C.

But, as a general guide: MPLab was used to write and compile the code (in C, either year in question. I'm not entirely certain what it had/didn't have. The code was then loaded onto the controller using an IFI loader.

I don't know the procedure for RobotC, sorry.

Now, for something that may help you a bit more: http://www.kevin.org/frc/ is the site where Kevin Watson posted a lot of his code from 2004-2008. This is a lot of specialized code, but there should be some basic code around there too. There is also documentation.

Re: Ye old IFI
 

Old Versions of MPLAB can be found here (Version 7.2).
Here is the page for the C18 Compiler (you should be able to get a free academic version or a light version (or something, at least)). I don't remember exactly what version number is required, but I think it's 2.4. EDIT: It looks like you do need MPLAB 7.2 and C18 2.4 to compile 2004-2006 code, but I couldn't find anything about 2007/8. I would suppose the same versions would work, but that's a question best answered by someone actually programming FRC robots then (i.e. not me)
IFI loader and some other resources from IFI can be found here.

I also have some other resources somewhere, because I got the old development environment set up on my laptop this time last year. I'll see what I can dig up again for you.

Best of luck!

Re: Ye old IFI
 

Thanks Phil....got'em

Been spending the evening looking at the Processing language and it's interaction with the Arduino. Found a great library that allow me to read joysticks and game controllers.

Who knows, maybe I'll just drop the IFI controller and go back to Arduinos.

Re: Ye old IFI
 

Folks,

Nothing is ever easy.....

I got the links mentioned by Phil. Problem is, for the MPLAB C compiler the 2.40 version is just an upgrade and requires that you have a previous version installed...which I don't. If you try to use the upgrade with the current version 3.4....things get very unpleasant....

Is there a work around, or a link to the installation directions for 2.40, or a copy of the stand alone 2.40?

This is beginning to become more of a problem than it's worth...and we still have 6 projects to go BEFORE next build season.

Doc

Re: Ye old IFI
 

Well, I found the old resources on my computer. I did find a ZIP with an installer for the student version of the compiler (which I'm mostly sure works - I've compiled stuff with it). I'll PM you with it.

Re: Ye old IFI
 

The school computer (w. a serial port) that we received for programming will take a few days to get running. I have (thankfully) found our teams 2007 and 2008 discs, and in the meantime I am wondering if we can use more recent versions of the software vs. the versions listed above...

Could we use a newer version of the MPLAB IDE, or are we stuck using the version given to us in 2008?

What about the compiler, should I use the one given to us in 2008, or should I use the student version?

Thanks,
Daniel

Re: Ye old IFI
 

The MPLAB IDE version doesn't matter. You can use a modern version.

The latest compiler will work, but only if you use matching FRC libraries (in other words you must use the same compiler that the libraries were compiled with).
The original code libraries available from the IFI archive page will only work with the old 2.4 version compiler.

The newer compiler will work with newer libraries that Kevin Watson compiled.

Re: Ye old IFI
 

I'll say that everything given to you on the disc is guaranteed to work, and that's your best bet.

Other than that, everything else is at your own risk. Kevin has links to libraries for both the 2.4 and 3.0 C18 compiler. My guess about the IDE is that it shouldn't make too much of a difference. If you can get the configuration to work, go for it.
Disclaimer: the above paragraph is my best guess, which is untested and I was not on a FRC team during the IFI days. I can't guarantee that anything other than the disc which was given in the KOP will work as you want it to.

EDIT: Yeah, what Mark said

Re: Ye old IFI
 

Because a majority of different IFI equipment was supplied over different years, a picture of all the equipment you have would be nice to see what you actually have, or better yet model numbers for the modems, OIs, and RCs you are in possession of. Once we know what actual controls you have, then assistance can be provided, and maybe even extra hardware may be kicking around that can help you get a robot running.