Day 11/22/16 06:00pm - 09:00pm

Attendance:

- Students
Wesley
Owen
Melea
Taylor
John Paul
Joseph
Robert

-Mentors
Coach Jeff
Coach Mike

Rent a Warrior - Helping FTC Team 10591 - Simpson County Future Engineers

Today we helped team SCFE 10591 with programing and gave them some 80/20, the extruded T-slotted aluminum and other parts they may need for their different subsystems. This will be the 3rd season of us giving out 80/20 to other FTC teams; it has been a great way for us to help other teams have more competitive robots. SCFE is the first team we have helped this season and hopeful we can help many more. This is the Simpson County Future Engineers 2nd season so this is a great time to start using new build-materials and becoming more competitive. ~Melea

Team 10591 SCFE needed help designing their arm for the robot. The arm consisted of leadscrew and several hinged sections that would unfold and raise high enough to cap the center vortex. After prototyping the arm we eventually decided to use a conventual lift design consisting of several cascading 80/20 pieces that will raise the cap ball off of the floor and onto the center vortex. - Wesley


For the first half of the meeting Jacob (one of our mentors) and I helped team 10591 with some of the programming concepts that they needed to understand in order to get their robot working. One of the big things we explained is how controls work with "if-else" statements, this was important as if you are not careful your if-else statements might start canceling each-other out if they work with only one motor due to how if-else statements work (explanation found slightly below.) Other than that we helped them clean up the rest of their code: removing unused sections, and clarifying sections that they were using.



"If-else" statements usually work by checking if a condition outlined in the "if" section is true and either running the "if" section or the "else" section of code. The problem you get is when you have multiple "if-else" statements effecting one object (a motor or servo for example being the most likely in our case): the last statement that has influence over the object (motor/servo) is the one that gets priority. Because of that fact, if you want to to make multiple if-else statements that can control a single object in more than one way, what you need is an if-else-if-else statement which works by checking if the "if" is true, if the "if" is true then the "else-if" and final "else" are ignored and the action contained in the "if" statement is run. If the "if" is false then the computer checks if the "else-if" statement is true, if it is then the code contained in the "else-if" statement is run. If both the "if" and "else-if" parts of the "if-else-if-else" statement are false the "else" is run. The only problem can occur at that point if if both the "if" and "else-if" statements are true, then the "if" runs completely ignoring the "else-if." To fix that you simply have to make the "if" a condition which reads as true and runs in a situation where both the original "if" and "else-if" conditions would be true, therefore removing the before mentioned issue and leaving you with an "if-else-if-else-if-else" statement. - John Paul


external image 30827377650_42136aa712_c.jpg
Simpson County Future Engineers with their 80/20. ~Melea


external image 30387565603_d60e83854e_c.jpg
Here I am working with some of the team members con the arm assembly Wesley

external image 30373638644_9b77eefd3d_c.jpg
Me and Jacob helping out the other team with coding. -John Paul


external image 30387613763_71e2b69f4b_c.jpg
Jacob pointing out a specific part of the other team's code to explain something about that section of code. -John Paul