Team Three/Journal

Revision as of 15:33, 8 January 2015 (view source) Team3 15 (Talk | contribs) (→1/7: Team Three/Journal/Jan7) ← Older edit		Revision as of 19:30, 8 January 2015 (view source) Team3 15 (Talk | contribs) (→1/8: Team Three/Journal/Jan8) Newer edit →
Line 26:		Line 26:
	* Goals:		* Goals:
	** Hardware:		** Hardware:
−	** Software:	+	** Software: SCF: Make I2C work.
		+
	==== 1/9: [[Team Three/Journal/Jan9]] ====		==== 1/9: [[Team Three/Journal/Jan9]] ====
	* Goals:		* Goals:
	** Hardware:		** Hardware:
	** Software:		** Software:

---

Revision as of 19:30, 8 January 2015

Contents 1 MASLAB Documentation 2 Deadlines 3 Journal Entries 3.1 Week 1 3.1.1 1/5: Team Three/Journal/Jan5 3.1.2 1/6: Team Three/Journal/Jan6 3.1.3 1/7: Team Three/Journal/Jan7 3.1.4 1/8: Team Three/Journal/Jan8 3.1.5 1/9: Team Three/Journal/Jan9

MASLAB Documentation

Deadlines

• Determine specific hardware parts (motors, shields, etc) by 1/7
• CAD every part of the robot by 1/11
• Initial workingish prototype by 1/14
• Have autonomous code for the prototype by 1/16
• Finish actual robot (mechanical portion) by 1/21
• Finish debugging and testing everything by 1/28

Journal Entries

Week 1

1/5: Team Three/Journal/Jan5

• Goal: Brainstorm. Get a general "game plan".
  • Decisions: Using C++; teams -- hardware: EM/LAZ software: PS, SCF, GW; came up with some ideas to prototype

1/6: Team Three/Journal/Jan6

• Goals:
  • Hardware: LAZ + EM: Build kit bot, install Solidworks, make hardware system game plan
  • Software: SCF: Learn C++ PS: Learn OpenCV GW: Make software game plan

1/7: Team Three/Journal/Jan7

• Goals:
  • Hardware: LAZ + EM: Determine specific hardware parts (motors, shields, etc)
  • Software: SCF: figure out how to interface with motors, ir sensors

1/8: Team Three/Journal/Jan8

• Goals:
  • Hardware:
  • Software: SCF: Make I2C work.

1/9: Team Three/Journal/Jan9

• Goals:
  • Hardware:
  • Software: