|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: reprogram during a competition
Quote:
The way I solved this was to just enable more obtimizations. If you do advanced debuging, read the compiler manual first. A few of them change break points, which I presume apply to the simulator, too. |
|
#2
|
||||
|
||||
|
Re: reprogram during a competition
Quote:
|
|
#3
|
||||
|
||||
|
Re: reprogram during a competition
Quote:
Quote:
Quote:
|
|
#4
|
||||||
|
||||||
|
Re: reprogram during a competition
im sorry if you misunderstood my question. i was wondering if reprograming the robot was legal durring the compitition.
Quote:
Quote:
Quote:
Quote:
Quote:
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 Quote:
, 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 |
|
#5
|
||||
|
||||
|
Re: reprogram during a competition
"<R14> Prior to the competitions: After the close of the "FIX-IT WINDOW"and prior to the competition, the team must put down their tools, cease fabrication of robot parts, and cease all software development. Take this opportunity to rest, recover from the build season, and relax. Teams may scout other teams, gather and exchage information, develop game-playing strategies, collect raw materials, prepare tool kits, plan how to make repairs, etc. in preparation for the upcoming competitions. But no construction or fabrication is allowed."
I take this to mean that you cannot create unexisting code, but you can tweak existing code to make it function properly. Also, <R16> states: "The purpose of this Rule is to allow teams to make critical repairs to existing parts to enable them to compete in following events." Also, the total weight of Repair parts cannot excede 25lbs. First of all, critical repairs can mean non-wroking coding that you did not have the time to fix. Second, existing parts includes the code since the code is a part of the robot, else it would not work. Third, total weight<25lbs. A floppy disc with the correct code weighs alot less than 1 lb., and the code can be uploaded easily, as long as someone brings along a laptop or some other method of moving code onto the robot. All in all, I believe that tweaking code after the "FIX-IT WINDOW" is allowed, just as long as it tweaks already existing code on the robot. However, this is not an official ruling, just a rookie's opinion. |
|
#6
|
|||||
|
|||||
|
Re: reprogram during a competition
Quote:
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 Quote:
Quote:
Quote:
Thanks though – jsd Last edited by jacob_dilles : 24-01-2005 at 22:25. |
|
#7
|
||||
|
||||
|
Re: reprogram during a competition
Quote:
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. |
|
#8
|
||||
|
||||
|
Re: reprogram during a competition
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. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| CMUcam II and competition lighting environments | dlavery | Programming | 5 | 16-02-2005 02:07 |
| 2004 WPI EBOT Competition (using Robovation robots) | ahecht | Off-Season Events | 3 | 04-11-2004 21:25 |
| FANATIC - Offseason Animation Competition | opnickc | 3D Animation and Competition | 15 | 10-06-2004 20:54 |
| New Competition in MI, Mailing List | Allison K | Off-Season Events | 0 | 29-03-2004 19:53 |
| Robots prepped for competition | Brandon Martus | FIRST In the News... | 0 | 24-03-2004 17:06 |