reprogram during a competition

[jacob_dilles]

At the risk of poking at a delicate subject – could the robot legally reprogram itself during a competition?

With a normal match the UI and the RC are in constant communication, but until the 15 sec autonomous mode is up, none of the joystick inputs (read – any input that operators can control) are active. As we have covered in other threads, a switch set before the match started could be detected by the robot before the controls were nulled. However it is blatantly wrong to have the robot be reprogram itself based on, say, at the location of the vision tetras: although theoretically possible with a 16F84, a flash card, and some clever coding and a 6 way switch.

My question pertains to reprogramming of the robot, by the robot, at the end of the 15 second autonomous period. My team has had problems with limited memory of the PIC, and with camera tracking and accelerometer algorithms we are close to the maximum size, without any of the operator-assist code.

Consider this example: When the 15 seconds of self control time is up, the autonomous flag is cleared; the RC pulls a digital output high. A carefully programmed microcontroller would emulate the serial port of a PC, putting the RC into boot loader mode and handing it the second set of code from an external EEPROM or “flash drive”. After the 1.5 or so seconds that the process takes, the robot is reset with its new code and on its way for the 2 minutes of user control.

anyone have any comments? does this violates any FIRST rules?
Thanks – jsd

[Kyle]

I am not a programmer but could you explain why you would need to do that after Auto mode is over the robot is in driver mode and the only programing that you would need is what is need to run from the controller to the robot, right?


Just remember that i am not a programmer, I would just like to know why that would be needed. so please be nice if I sound really dumb.

[jgannon]

I would suggest a much simpler way of achieving the same results: optimize your code. It's free, and much less likely to malfunction. I truely doubt that you actually are going to run out of memory, but if you do, come up with creative ways of doing things. Use fewer variables. For example, if you were trying to swap two variables, instead of doing:

int c;
c=a;
a=b;
b=c;

...do:

a+=b;
b=a-b;
a-=b;

The first law of programming is that there are always ways of doing things quicker and in less space than you already are. (The ternary operator will be your friend in this pursuit.) Everyone is going to face the same problems that you are, and I doubt that anyone is going to absolutely need one of these devices. Good luck.

[jacob_dilles]

Originally Posted by Kyle

I am not a programmer but could you explain why you would need to do that after Auto mode is over the robot is in driver mode and the only programing that you would need is what is need to run from the controller to the robot, right?


Just remember that i am not a programmer, I would just like to know why that would be needed. so please be nice if I sound really dumb.

I think what you’re trying to say that the driver code is not complex, or long, because it just takes the values from the joystick and sends them to the Victors.

Our driver code is both complex and long, and we go over it hours at a time trying to make it shorter, and it’s still huge. We use sensors to measure rotation and two direction acceleration, and make changes to the motor outputs based on where the robot is and where the operator wants the robot to be. And all of the arm controls, limits, etc take up space too.

The memory on the RC is limited to start with (a couple of KB). It doesn’t help that the chip was designed to run assembly and we compile C++ to it… C is a complicated high level language that uses lots of libraries that take space. Then IFs “default” code is a beast (its got to be compatible with every team), but you cant ditch it because they wont give you total control over the RC (it’s a boot loader, ugg). And some of our programming team members write crummy code. All and all, memory is precious, and the more the better.

I hope this answers your question, jsd

Originally Posted by jgannon

I would suggest a much simpler way of achieving the same results: optimize your code. It's free, and much less likely to malfunction. I truely doubt that you actually are going to run out of memory.

We work only on code every day for 6 weeks… we can do 80% of stuff with out a second program

Originally Posted by jgannon

I truely doubt that you actually are going to run out of memory.

I’m sorry if you doubt it, but I have run out of memory, and its not fun. Actually the first time it happened was in the pits, but I was writing sloppy code, so it is expected.

Originally Posted by jgannon

The first law of programming is that there are always ways of doing things quicker and in less space than you already are

Incase it wasn’t clear -- This was a theoretical question; the probability that I would implement it is very low. But when my team comes up with another page of stuff the robot is suppose to do by itself; I at least need a worst case scenario


Thanks though – jsd

[Max Lobovsky]

I believe your effort would be much better spent optimizing your code to make it smaller as others suggested. There is a lot you can legally and safely strip out of the default code. Additionally, once you have your code debugged and in a stable stage, you can start rewriting stuff to sacrifice manageability and "good" programming practice for smaller size.

BTW, we are programming in C, not C++ and every robots code that I have seen uses very few extra libraries.

[jgannon]

Originally Posted by jacob_dilles

This was a theoretical question

Bah, and here I tried to provide a practical answer.

Look at the Additional Parts flowchart in section 5 of the manual to determine if this device is legal or not. If you don't get a satisfactory answer, try the FIRST Q&A.

One more note on the practicality of this: maybe our programming computer is different from yours (1.8GHz seems like enough), but it takes a bit longer than 1.5 seconds for me to send code to the RC with IFI Loader.

[RbtGal1351]

Originally Posted by jgannon

I would suggest a much simpler way of achieving the same results: optimize your code. It's free, and much less likely to malfunction. I truely doubt that you actually are going to run out of memory, but if you do, come up with creative ways of doing things. Use fewer variables. For example, if you were trying to swap two variables, instead of doing:

int c;
c=a;
a=b;
b=c;

...do:

a+=b;
b=a-b;
a-=b;

The first law of programming is that there are always ways of doing things quicker and in less space than you already are. (The ternary operator will be your friend in this pursuit.) Everyone is going to face the same problems that you are, and I doubt that anyone is going to absolutely need one of these devices. Good luck.

Ok now please bear with me, im a rookie programmer, but why would the above example save any memory space on the actual robot controller? when you build it, it just makes it assembly language (the .hex file), and both those (above) are the same. thats the whole goal.

in order to save memory, my team is using #define s for as much as possible, so when you compile/build it, as much as possible is already done. also, the same for some of the autonomous calculations--look up tables are faster and smaller than calculating something. (especially for trig functions, which you might need for autonomous--distance).

plz tell me if im horribly wrong or something...
thanks,
~Stephanie

[ericand]

If you need a sufficiently small number of values, table lookup will
save space. It just depends on how many you need. In the general
case, an algorithm will save space and table lookup will optimize for speed.

The use of #define will not necessarily save space (except in your
source files, where you don't care). It depends on how you are doing things.
To save space with constants, you want every reference to the value of the
constant to be to the same memory location. If you just use the define, you
will be storing the constant value everywhere it is used.

[russell]

I might be totally missing something, but like jgannon says it takes (me at least) way more than 1.5 seconds to download a program to the RC. More like 1.5 minutes. And why dont you simply do the processing on something else (how much does a 386 cost?) and just use the RC for I/O?

[Mike Betts]

Jacob,

At the risk of sounding condescending, I can't believe that anyone is running out of space. If so, take a good hard look at what you are doing.

Programming an embedded system is absolutely nothing like programming a PC.

First rule: Never, never, ever use floating point arithmetic.

Second rule: Never, ever use dynamic allocation of memory.

Third: Avoid pointer manipulations unless you understand what it does in the machine (some dereferencing manipulations are murder).

Look at the assembly code being generated by the compiler. You can see it in the .lst file that is generated when you build your project.
Good Luck,

[Ryan Foley]

Originally Posted by russell

I might be totally missing something, but like jgannon says it takes (me at least) way more than 1.5 seconds to download a program to the RC. More like 1.5 minutes. And why dont you simply do the processing on something else (how much does a 386 cost?) and just use the RC for I/O?

He brings up a very good point. I believe that in 2003 the Wildstang 111 robot had a Motorola processor on it to do all of the calculations and processing, and the RC itself would be used for only a little bit of the program and the I/O. Go to the Wildstang website and click on "Stang PS" for a bit more information.

[Alan Anderson]

Originally Posted by Mike Betts

At the risk of sounding condescending, I can't believe that anyone is running out of space. If so, take a good hard look at what you are doing.

Significant processing between operator input and motor action.
Navigation (and all the trigonometry it requires).
Multiple independently-tuned PID controls.
Adaptive autonomy.

Finally, lots and lots of text for communicating with the camera.

I can easily understand someone running out of space. Last year's robot only did about half of what we have planned for this year, and it's using about 65 percent of the space.

[Mark McLeod]

I have to agree with Alan that if you try to dump everything possible this year into the program it can grow large.
Maybe not what you are looking for, but have you tried using the built-in compiler optimization to reduce your program bulk?

In MPLAB

• Project -> Build Options... -> Project
• MPLAB C18 tab
• pulldown categories and select Optimization
• click "enable all"

I tend not to use the compiler optimization unless necessary, because we've all had problems with optmizers in the past. Just test afterwards to make sure everything is working properly.

You have gotten rid of the IFI printf code, right?

[jgannon]

Originally Posted by RbtGal1351

Ok now please bear with me, im a rookie programmer, but why would the above example save any memory space on the actual robot controller? when you build it, it just makes it assembly language (the .hex file), and both those (above) are the same. thats the whole goal.

There are only about 1300 bytes (1200? I forget the exact number.) of variable space available to the user. My first example requires three ints, for a total of six bytes. The second example requires two ints, for a total of four bytes. I understand that variable allocation is not the only concern with respect to memory, but teams will discover that if they start wildly instantiating global variables, they'll start getting a lot of weird compiler errors, indicating that they've run out of space.

Originally Posted by RbtGal1351

look up tables are faster and smaller than calculating something

Faster, maybe, but definitely not smaller. I've been seeing all of these lookup tables that teams are using for desensitizing their joysticks, when all they really need is a simple quadratic equation, which I'm certain will take up significantly less space on the bot.

Originally Posted by Mark McLeod

have you tried using the built-in compiler optimization to reduce your program bulk?

Hm... no I haven't. I didn't even know that existed. That may very well come in handy for all of us. Thanks.

[jacob_dilles]

im sorry if you misunderstood my question. i was wondering if reprograming the robot was legal durring the compitition.

Originally Posted by Mike Betts

Programming an embedded system is absolutely nothing like programming a PC.

again, thanks -- ive been programming MCUs since i was 9 and got my first BOE-BOT kit... 7 years later i think i can tell the difference between a IBM platform PC and a PIC microprocessor

Originally Posted by Mike Betts

First rule: Never, never, ever use floating point arithmetic.

i don’t like the thought of using chars, ints are pushing it...

Originally Posted by Mike Betts

Second rule: Never, ever use dynamic allocation of memory.

external EEPROM is better then internal memory if you want to map data, but i generally use algorithms anyway (DMA isnt my cup of tea)

Originally Posted by Mike Betts

Third: Avoid pointer manipulations unless you understand what it does in the machine (some dereferencing manipulations are murder).

this i most hardly agree with

Originally Posted by Mike Betts

Look at the assembly code being generated by the compiler. You can see it in the .lst file that is generated when you build your project.

I used to write assembly for fun, thank you very much - thus my habits of not using as few IFs as possible; i much prefer boolean algebra.

Im not a "newbie" programmer, ive have been the head of our programming team since my freshman year. I have taken collage level CS in JAVA and C, as well as many, many courses on programming in just about every other modern high level language.

However, i have been doing this for a relatively short period of time -- there are people that are much better at this then i will ever be, and many of them participate in FIRST. i never pretend to know everything, so i respect everyone on the forums, and assume they know more then me, and in turn I hope they respect me

also i try very hard to keep delphi threads to the point... but stuff like

Originally Posted by Mike Betts

At the risk of sounding condescending, I can't believe that anyone is running out of space.

is unnecessary. i am sorry that you dont believe me , i never thought that i would have to take a screnie for something like that.



external processing is what our team has planned thus far. and i will be sure to try Marks optimization process... i wasnt looking for a lecture on how to optimize code (read the thread title!) i was looking for the legal implications of reprogramming the robot during a match. Thanks anyway – jsd