Did anyone get that bad feeling in the pit of your stomach when the demo robots FIRST had weren’t working in autonomous mode? The autonomous period scares me…
10 Seconds of Human time + 15 seconds of robots moving in circles = 25 seconds of dead air.
I think most teams will make it happen, if I learned one thing from last years game it’s that teams will acomplish amazing things even those seemingly impossible. But I sure wouldn’t wan’t to be the guy charged with programing the auto-mode.
It’s only my first year, but I’ve done a lot of programming before…I don’t think that seeking a target with reflective tape on it or following a line is that difficult to program. The latter I have done before with the Lego RCX robotics kit and it was surprisingly easy. The fact that NONE of their robots seemed to work leads me to believe that something was wrong with their entire control system, maybe?
The autobalancing routine that was posted by the TechnoKats (?) is an example of a dead reckoning program. Shouldn’t be too tough to program a forward, turn, forward, turn, forward that would plow over the ramp.
Remember, like all the mechanical engineers say- “let them fix it in software!!”
I suspect the autonomous period is to distract from the naysayers who always use the ‘it isn’t a robot because it is remote controlled’ type lines. 15 seconds isn’t that much time, I think it will be very interesting to see what people come up with.
So during autonomus period, will the robots be basically like huge Lego RCX’s??? … I mean, will you be able to program in go right, straight for 2 seconds, left, back, etc. ?
They tried operating the robots after the autonomy period and could still not get them to work, as well I saw the drivers station lights blinking on the off a couple of times. My guess is that they werent getting power to the drivers stations, and/or they transmitters weren’t seding signals to the robots. I dont think it had anyting to do with the programming.
I instantly had visions of robots crashing into each other.
Personally, I would have several programs loaded, and communicate with my alliance partner as to who’s doing what befire hand, so there aren’t and (wince) crashes.
how exactly is the bot switched from autonomous mode to regular? do we have to put in an autonomous subroutine or if statement to make it function on its own? I took a look at the new program but the number of tokenizing errors made it difficult to understand some of it. Any help would be appreciated.
In the code there is already an alias defined to see if you are in autonomous mode called “auton_mode” . It is bit 6 of the PBmode variable.
There is an example of how to code for this in the Programming Reference Guide, which can be found in the documents section at Innovation First’s web site The example is written as
If auton_mode = 1 then do_autonomous_stuff
'Normal drive code
goto end_of_autonomous
The Programming Reference Guide is well done. It will be a big help to new PBasic programmers.
As one of the coaches of the control team I am really looking forward to developing the autonomous mode code. Of course I say this now, talk to me in six weeks.
One correction, only the 15 seconds are apart of the actual 2 minutes of the game. The other 10 seconds for the human players are seperate from the game time.
I liked the direct drive robot in the demo;) All that crashing was funny.
I don’t think anyone will go it on all AI for the game but who knows.
I don’t like the idea of having the bots run around for 15 seconds without anything to keep them from ramming eachother. I think FIRST decided to make scoring for fans easier, but actually forming a strategy for it harder than anything.
*Originally posted by Ian Mathew *
**I don’t like the idea of having the bots run around for 15 seconds without anything to keep them from ramming eachother. I think FIRST decided to make scoring for fans easier, but actually forming a strategy for it harder than anything. **
That’s why the disable button was created. If you’re concerned about what your robot’s gonna do, hit the button. You can re-enable it when the human-controlled match starts.
If anything, just program your robot to go forward (or backward) at the start of the match. Then hit the button when you’re at the spot where you want to start.
Well just remember, there is no where in the rules where it says your robot must do something in the autonomous period. So anyone that is afriad for their bots sake, or for injury from a poorly coded automater… can just sit tight for 15 seconds.
everyone is complaining. i think this is great! i finally have something to do as one of the main programmers. sure, it’ll be hard, but hey, i plan to have at least 2, maybe more mini programs. if you guys don’t want to do anything for the first 15 seconds, fine by me. more time for my robot to work with :).
*Originally posted by Spikey *
**One correction, only the 15 seconds are apart of the actual 2 minutes of the game. The other 10 seconds for the human players are seperate from the game time.
I liked the direct drive robot in the demo;) All that crashing was funny.
I don’t think anyone will go it on all AI for the game but who knows. **
I believe I read in the manual otherwise…
15 seconds of autonomy, and then 1 minute 45 seconds of Human controlled robots…
Anyone know if there will be a stop between the human controlled and autonomy, or will it just turn on the human controlled with no stopping transition?