Fabrication Marathon: 1/29/08
Not sure what's going on with the Blog recently, but
whatever. Big enough news that this needs to be posted~
Subteam Updates: 1/27/08
Drivetrain: Design has been finalized. Currently in the
process of ordering/purchasing/otherwise obtaining parts for
the crab module and chassis
---
Fabrication: We realized that more holes and other
measurements are off; therefore, we may have to remake
several parts. Basically, we did the same things as
yesterday: drilling, deburring, filing, sandblasting, etc.
---
Software: Worked more on programming. Decided what encoders
to use for driving--had to figure out how many ticks per
revolution would work.
Subteam Updates: 1/26/08
Fabrication and Drivetrain: Since there weren't enough parts
for drivetrain, we [fab and drivetrain] all did fabrication.
We drilled holes, deburred holes, filed, used the
sandblaster, etc.. Kyle, Jim, and Branden were cutting parts
and such in the auto shop.
---
Software: Worked on IR controller and PID. They ended up
scrapping the PID idea.
Subteam Updates: 1/25/08
Software: They fixed their joystick code for polar and
rectangular driving styles.
---
Fabrication: Made parts? I'm not really sure...
Subteam Updates: 1/23/08
Electronics: Finished shopping list.
---
Drivetrain: No idea...wasn't there. If someone can please
inform me of what happened. Thanks.
Subteam Updates: 1/21/08
Team: We decided to have absolute encoders instead of
continuous rotation pots, multi-turn pots, single-turn pots,
or incremental encoders for turning.
---
Electronics: Got wood for an electronics board and started
working on more ideas for the placement of parts.
---
Drivetrain: Discussed motors..etc. [I don't really remember
so if someone else on drivetrain does...please leave a
comment to this blog or email me, thanks!]
---
Software: Worked on drivecode--possible use of a dial, work
on coding for gyroscopic sensor, and have the robot move
relative to driver. Also asked to create a backup program in
case the gyro or encoders have a failure.
---
Fabrication: Found out whether we had enough noodles,
cloth, etc. to make the bumpers, which we don't. Made a
shopping list.
Subteam Updates: 1/19/08
Drivetrain:
We decided to use a one stage reduction (6:1) using belts
instead of using or buying a transmission.
We continued planning on the placement of the CIM motors
and the mounting of them to the wheel modules.
Branden Gunn brought in a 1/2" stainless steel chassis we
got to play with as well as other cut outs.
We discussed driving options further and played with
programs brought in by Jim Troy and Sean Reilly.
Hope to begin assembling soon. [qtd. Elyse]
Worked on gearbox.
---
Software:
Worked on a general idea for how the joystick will work and
programming for it.
---
Electronics:
Looked at the IR board. Got the batteries made and the
chargers built [attached quick connects to both batteries
and chargers].
---
Spirit:
Worked on design of hoodie.
Olympia: 1/18/08
We left school at approximately 11:00am for Olympia. Shortly after we got there we had lunch and then Paul Gudonis met up with us. After we finished eating we headed to Hearing room B in which the video was played and Elyse, Kyle, and Peter B made their presentation. Members from team XBot [488] and TRC [2046] showed up as well. After the presentation we had a tour of the capitol. We then headed home [or accidentally to Portland ^_^]. Good job presenters!
Olympia Preparation/Subteam Updates: 1/17/08
We watched the video that was made for Olympia and the
presenters discussed what they were going to present. We
found out that Elyse, Kyle, and Peter B would be on King 5
the next morning.
---
Mechanism:
Though no one stayed... We DID have a Mechanism meeting
after Kyle went "You know what, you guys can go home."
-It was... Interesting. We discussed ideas for Outriggers
and Ears. The Ears idea was multi-jointed, with a tension
string to prevent flopping one direction but still allow
flopping another (blah, being vague sucks).
-Outriggers... Well, actually got mentioned on the side of
a proposed Poker mechanism. Study up on your music, and
stand on your side to get the rather random hint. Actually
seems like an interesting way to deploy Outriggers (since we
likely won't want the outriggers dragging on the ground when
we don't need them. I'm not sure how well such a design
works though when you only want Outriggers, or when you are
going the other direction)
-That's about it that people missed. We really SHOULD look
into outriggers a bit more, 'cause a Gyro won't help you
right yourself should some robot hit you and knock you over.
A deployable Outrigger can kick you up right should you lie
on your side :/
[qtd. Rai]
Seattle Times/Subteam Updates: 1/16/08
The Seattle Times photographer came again to retake photos.
Afterwards there was an electronics meeting until 4:00 in
which we made a shopping list for the electronics board and
OI. The electronics meeting ended early and the mechanism
meeting was canceled due to road conditions.