Other then simple programs such as moving forward or back, how many teams are done with their Autonomous code. Our bot is still in the shop and our programmer is just now getting his time with it to figure out how to program everything. How’s the rest of the world going?
Im not on the programming team, but im pretty sure we have about half of our autonomous programs finished.
i dun with it:D 
I’ve got a program written, but our robot still doesn’t drive so I can’t test it. I’ll be lucky to get 15mins with the robot before we ship…
*Originally posted by rbayer *
**I’ve got a program written, but our robot still doesn’t drive so I can’t test it. I’ll be lucky to get 15mins with the robot before we ship… **
Aint it the truth!
*Originally posted by rbayer *
**I’ve got a program written, but our robot still doesn’t drive so I can’t test it. I’ll be lucky to get 15mins with the robot before we ship… **
I know what thats like.
Well, autonomous is done, theoretically. I’ve gotta tweak it, but we went to a scrimmage today @ chatsworth and I kinda made the gears jump off. so we gotta repair drive train b4 the tweakage. The weird thing tho, autonomous didn’t work @ chatsworth at all.
Our autonomous is an adaptable line tracker. It’s cool cuz it adapts motor power values based on how long you’ve been in a particular position and orientation. Pretty nice stuff. Just need to tweak then we’re done.
930 just has some tweaking to do after Sussex Practice Competition.
hehe… our robot has been driveable for 2 weeks:) … and we had 3 auto proggies done and tested and then they switched to 2-wheel drive… so now we have one (nickname: “track line and jump over the ramp”… lol) Now working on an adaptable dead-reckoning proggie now… fun fun. Word of advice for auto programs: hardware timers make it soo much easier! Now if i could just quit running out of EEPROM space…
*Originally posted by randomperson *
**hehe… our robot has been driveable for 2 weeks:) **
Only 2 weeks?..
Why hardware timers? I use a software timer in mine and it works fine. 38 counts = 1 second.
Hmm… yeah, that would work <i>if</i> your program didn’t have lots of branches in it and executed at a somewhat constant speed… but personally hardware is better cuz we can count in 1/4 seconds instead of 1/38th… and like I said, its easier. lol, like 3 lines of code to implement it. much easier methinks compared to some of the solutions ive seen on these boards…
True I guess. My code’s fairly constant in all branches. I’ve tested the timing with feedback LED lights and it seems constant. We have a counter that counts how long the robot’s been on a particular sensor config and adjusts motor power due to that. So I don’t need to be ultra precise, and 1/38 is an annoying number to work with tho.
yeah… i got pissed off about the timing not working correctly and the weird numbers… so i got myself a 555 and stuck it on our prototype. it worked great, so we kept it… definitely gonna have one next year too even if there’s no automatic programming… very useful
ehh, wut was weird was at the scrimmage autonomous didn’t activate for us at all. I wanted to test it out, never got a chance, our drive train jumped a gear. Grrrrr. Oh well, we won the scrimmage like 88-32 so we did well without autonomous.
what scares me is at the kickoff the robots never went autonomous. I mean these are engineers we’re talking about.
What we did was while design worked hard on our design, I got 2 or 3 guys together and made last year’s robot do kinda what this years bot will be doing. We then took this and found out flaws in our design, found better, more efficient and faster methods of working as well as gave us the ability to have different codes designed (such as stack tracking) that can be used if we add and setup the sensors. I have a few different little autonomous codes so we can swap codes to counteract what scouting data brings us.
One last thing, with your dead reckoning codes, be careful! I realized very well that over time those numbers WILL change. The drive system is gonna change after running a bit, as things wear in and hardware changes. Also I’d really suggest using the delta_t counter and add it in to your counter since sometimes that RC can be crazy and lose loops like mad. It keeps it so you have your times closer. That’s my 2 cents though. Good luck programmers. If you guys got that autonomous running well, great job cause you deserve it.
Are code is done we got the auton code working it does perfect 90’s everytime not matter about wheel slip or battery it works everytime.
could you give me an example of how delta_t would be used? I’m interested in how this could be utilized in my own counter.
*Originally posted by rbayer *
**I’ve got a program written, but our robot still doesn’t drive so I can’t test it. I’ll be lucky to get 15mins with the robot before we ship… **
15 minutes? we should be so lucky.
*Originally posted by TOHSlancer *
**could you give me an example of how delta_t would be used? I’m interested in how this could be utilized in my own counter. **
really easy. make sure delta_t is setup in your code like in the default code and use this for your counter…
counter = counter + 1 + delta_t