• Picture 1
  • Picture 2
  • Picture 3
  • Picture 4
  • Picture 5
  • Picture 6
  • Picture 7
  • Picture 8
  • Picture 9
  • Picture 10
  • Picture 11

News

Table of Contents

  1. Day 17 – Waiting (1.23.12)
  2. Day 15 – Catching Up (1.21.12)
  3. Day 12 – The Bridge (1.18.12)
  4. Day 11 – AMM (1.17.12)
  5. Day 5 – Work and Hamburgers (1.11.12)

Limit Articles

years ago

months ago


23
Jan 12

Day 17 – Waiting (1.23.12)

Today, we decided to not have a design meeting. Although we are not where we want to be right now, we still ended up taking a day off. We are waiting for some of the robot parts that we have ordered for testing and using.

Some of us went to Michael C’s house to test out some of the paint. We tried out a couple different shades of yellow to see which color(s) would look best on our soon-to-come robot.


21
Jan 12

Day 15 – Catching Up (1.21.12)

Yes, we are a bit behind. Our new “Trac” system says that we are about one week behind. Not good. This morning, we met at Lynbrook to get as much work done as possible. The software guys reflashed our 2011 robot, the hardware guys tried to make a finalized version of our drivetrain, and the events guys finished up planning our trip to New York.

While all this was going on in room 612, Mr. Xie and Mr. G were giving lectures about software design. Mr. Xie went over drive train control. He talked about the differences between PID (proportional-integral-derivative) and Lead Lag control designs. Mr. G explained our current CAN Bus (Controller Area Network) system, and how information flows from the cRio to the 2-CAN, and then to the individual robot motors and parts. He also talked about our Jaguar speed controllers. Next, Mr. G went over some of the important points for newcoming programmers. This includes destroying previous commands, looking at previous years’ code, and learning from experienced programmers.

We didn’t finish all of the item on the agenda, because we ended up drifting to room 612 to get more work done. After a short lunch break, many of us returned to continue working. At the end of the day, the drivetrain was looking better and better. Only a few more tweaks left!


18
Jan 12

Day 12 – The Bridge (1.18.12)

Today, we finished building the team version of the bridge. Turns out, our bridge is just over 60 pounds, while the official bridge is calculated to be over 200 pounds. (We used the battery test given by FIRST to help calculate the weight.) This means that our bridge will not act like the official competition bridge. We haven’t decided how we are going to make our bridge more like the official bridge. We will probably end up placing some weights in specific places on the bridge, after we learn more about the real bridge’s characteristics. On the other hand, Mr. Peake, a mentor, mentioned that it may be to our advantage to practice using the lighter bridge. A lighter bridge would make it harder to balance.

At night, we had, once again, a design meeting. First, Brian showed the team a new tasks system, called “Trac.” This is a system for keeping software projects on track, but we will be using it to keep track of the entire build process. Next, we went over interesting things that were found on Chief Delphi. One was a ball intake system that would give the robot more space to suck up balls (found by Miles). Currently, because of the bumper rules, robots would only have ~12 inches to suck the ball up. However, with this system, the balls in front of the robot would automatically be moved to the intake area by three sets of deployable rollers.

Then, we had a discussion about our robot design. We are still debating whether to have the robot’s shooter point forward or to the side. Pointing it to the side would make it easier to fine-tune when aiming, since we would be using the driving system. On the other hand, if it were pointed forward, we would need to aim by turning in place, which, for us, is not as precise. Also, we looked at good positions, or (as we like to call them) “sweet spots,” that we would like to shoot from. Ideally, we would need more than one zone where we can consistently score from, so opposing teams would have a harder time defending. Mr. Xie also brought up the idea of having a basket/hopper to allow other teams to feed us balls. However, some people had doubts, since other teams would probably not aim for us, and instead aim for the hoop. Also, the robot-to-robot interaction could easily lead to robot damage, whether it is from the fired ball or from a collision.

After the meeting, some of us played around with the bridge to get an idea of its physics and properties. We ended up trying to stay between “balanced” and “unbalanced”. It was fun.


17
Jan 12

Day 11 – AMM (1.17.12)

Since it was a Tuesday today, many of us got out of school at 1PM. However, we didn’t just leave school. Some of us stayed and worked in room 612. We started on building the bridge. We also continued fixing up our CNC and made more calculations and tests.

At night, we were again at school. Funny how we seem to love school so much… We had our weekly Active Member’s Meeting (thus, the title of this entry). We talked about purchasing a team flag, the t-shirt and sweater designs, the upcoming spring newsletter, awards, and the trip to New York. More detailed notes can be found here. Interestingly enough, this meeting ended in just 89 minutes. Anyways, we were able to get much done in this short time period. Tomorrow, we will continue working on the robot design during the design meeting.


11
Jan 12

Day 5 – Work and Hamburgers (1.11.12)

Today, we did more work in Room 612. We tested a previous shooter, mounted the CNC, assembled the barrier, fixed up the 2010 robot to run tests on the barrier, and mounted the de-burring wheel. We also had our second design meeting later at night.

Shooter: One team took the 2009 robot to test its shooter’s accuracy and power. We also laid it on its back for a vertical test. The ball ended up flying just 38 inches in the air. The distance from the max robot height to the highest rim just happens to be 38 inches as well. If we decide on going for that top hoop, we will need to add some extra power. (Workers: Miles, Michael L, Pradeep, Annie, Eric)

CNC: A second group continued to work on the CNC. Yesterday, we managed to get the machine into the room. Today, we mounted it onto its base. Of course, we used a small crane. Just imagine having a group of students and mentors trying to to lift a 1300 pound device that costs thousands of dollars… (Workers: Michael L, Anurag, Mr. Peake, Mr. G, Mr. Haas, Mrs. Haas, Mr. Harrison, Mr. Lowd)

Barrier: With help from Mr. and Mrs. Haas, some of our students completed the task of making the barrier. Brian, one of our software guys, took our 2010 robot (yes, we reuse our past robots quite a bit) and fixed up the code so we would be able to run tests later. (Workers: Miles, Annie, Pradeep, Mr. Haas, Mrs. Haas, Brian)

De-burring Wheel: Akshat took our de-burring wheel and mounted it on a new black stand. Now, whenever we go to de-burr something, we will be able to admire the shiny new stand.

At night, we had our second Design Meeting. There wasn’t much time between 612 work and the meeting, so some people did not even have the opportunity to go home. Others ran home, grabbed dinner, and headed right back. (I watched Miles as he ate his hamburger. It looked pretty good.) The meeting started off with Ms. Zhang giving a presentation about project management. This focused on how to stay on schedule and finish with a working robot.

Mr. Xie then continued his presentation from Monday. We went over some ideas and design concepts. Originally, we were going to split up into different groups, but we ran out of time. Hopefully, we will be able to do so on Friday!