These are some inspiring ideas for designing a tread-bot.





These are some inspiring ideas for designing a tread-bot.





Hi, I’m Hannah, the outreach coordinator. These are costume ideas that I found interesting.
This one I found quite bold because of its design, no top, yet still looks like a dalek. Very interesting, I like it the best out of all of them.I liked that it had easy arm movements. It’s more practical. It can also be used for a boy or a girl.
This one I liked because it the one that looks the most like a dalek.
This one I picked because it looked pretty interesting.
This one looks interesting, bold and cool, that’s why I like it.
This one I picked because it looks totally awesome and flat out cool. I like that you can take this off and on easily. It would be harder to move around in.
http://letsmakerobots.com/robot/project/tachikoma
http://forums.trossenrobotics.com/showthread.php?3637-Alum-Robot-Quadruped-custom-kit
http://www.hexapodrobot.com/forum/viewtopic.php?f=11&t=331
4 legs- http://letsmakerobots.com/robot/project/my-first-robot-quadruped-3-dof-leg
We’ll have to see how well it does getting over and off of the bars on the ramps.
FTC must be near perfect by now!
The new Game Manual part 1 is out.
Some changes I discovered, which is not to say they are completely new but only that I was unaware of them, in the new GAME 1 manual:
This is not new, but somehow we went 3 sessions and several Think Awards without noticing it-
” Attach a “summary page” to the front cover of your Engineering notebook. Your summary should be a brief, one page narrative about your team, your school or organization, and an overview of the highlights of your season. Your summary page should also include your team number and point the Judges to the pages in your Engineering Notebook that you would most like the Judges to consider.”
It was pointed out to me by FTC Team 3595, the new manual had excluded it’s old terminology of “Tasks and Reflections” for the Engineering notebook. But look at the example given by FTC as s shining sample of the Think Award, and you can decide for your team if you want to include it or not.
(This stuff below is all new to the game manual 2015-2016, and often deals with the new wifi system coming in place this season.)
<T3>No Team, Team Member, or event attendee is allowed to set up their own Wi-Fi 802.11a/b/g/n/ac (2.4GHz or 5GHz) wireless communication in the venue. Non-allowed wireless communications include, but are not limited to:
<T4>Wi-Fi Direct® connectivity between the Android devices used as the Robot Controller and the Drivers Station is allowed. No other wireless communication is allowed.
<T5> Team members may be asked by the Event Director to use a specific Wi-Fi channel on the Event day. It is the intent of this rule that Teams must comply with the request of the Event Director if asked to use a specific Wi-Fi Channel.
5.2 Robot Control System – New for the 2015-2016 Season (Just read all of this. It was long, so check it out in the manual.)
<RG07>The Driver’s Station must comply with the following constraints:
(p.27-30) 5.3.3 Robot Electrical Parts and Materials Rules (just read this whole section. Also completely different because of the new wifi system.)
(p.31) 5.3.4 Robot Software Rules
All TETRIX parts are allowed except for the following: (new parts that aren’t allowed)
(p.26) 6.2.2 Robot Parts and Materials Rules <R10>Robot wiring is constrained as follows: (This whole section is new)
Add this to your collective memory, but Remember team captains and coaches! ALWAYS bring a printed Game manual 1 with you to tournaments- and print out any exceptions or new guidelines from the forum posts if you utilize those in your robot design. In 2015, we were sent away from a field challenge, not because we weren’t correct in our challenge, but because the judge said he wanted to see it in print. Maybe the head ref truly was unaware that Samantha control center incorrectly routing the robots so our alliance controlled each other’s partner robot, and not our own robot, was cause for a rematch, but none the less, he requested a Game Manual rule citing and we were denied our rematch 😦 Which, to FTC’s credit, will NEVER happen again since we do not have the S.F.C anymore! But be aware of the rules, they will all matter! For or against you, they will all matter.
Here’s a video series that shows how to set up the Android phone system for the new FTC season. Thanks to GEARSinc for posting these videos.
ON-DEMAND TRAINING: FREE!
Intelitek has teamed up with FIRST and developed 20 hours of learning modules. This training is available on line when you want it! http://first.intelitek.com/
Training will introduce the Android platform hardware, provide training material to master MIT App Inventor programming and Java programming with Android Studio.
ENROLL TODAY here: http://ftc.edu.intelitek.com/login/index.php
Our week long camp has come to an end, but we are left with great friendship forged and great battles fought and won. Thanks to all our campers for making this week worthwhile. We are looking forward to our August camp!
From free build to robotics programming, campers were excited about all the aspects of camp that had them moving, creativing and problem solving.

My favorite instant challenge- the cup challenge! Bring legos over to the far end of the room, when you can’t touch the cups.
A video of the absurd. Thanks to Michael P. for your dedication to sound editing.
Solve today’s problems. Untangle the world’s mysteries. Find an Exciting career. Make a Meaningful contribution

We got into the spirit, and instead of scrimmaging with other teams, we allowed STEM Day participants to drive the robots around. Jr FLL and FLL teams came over from their stations and were able to test out the next level of FIRST play. Thanks to the CNU and the LED Empire for setting up the FTC stations and inviting us.

The kids get really into explaining classes and objects…. sorta. Going over the lessons learned from the FTC forum, we learned A LOT about the path we’ll need to take to get to the first tournament.

The EIs take a break from the java program lesson to eat, drink, and laugh together. All those acronym quizzes Coach Brandy kept throwing at us, we had to stay on our toes. Java introduction is hard work!
Thanks to the LED Empire for coming to the meeting and learning about the new system with us. We will work together ore on the programming in the future!