November Update #3

Accomplished this past week:
Sam - Working on Report, Redesigned power circuit for new IC. Passing BOM to Matt to order.

Ian - Tested parallel code with shared resource using a mutex, wrote section of report.

Ogi - Picked out a camera model and working on report. Dr.Bao proposed buying another model (Canon SX710) and seeing if that one works.

Matt- Finished Poster, working on final report, parts order waiting on Sam

Goals for this week:
Sam - Focus on documenting power circuit design, provide analysis for final report and revise material from midterm report. Get report material finished ASAP. Get Bill of Materials finished ASAP.

Ian - Focus on pseudocode for project, document and analyze software needs (streaming, libraries, everything needed to prove that software needs are analyzed and addressed.) Document this as part of the Final Report ASAP.

Ogi - Focus on more background research -
- Get prototyping parts from work
- Check with work to see if they can/will 3D print our case once we design it
1) Selecting and using an embedded camera (example model)(2nd link)
2) How the technologies of the project are used in a relevant sense (see old reports for examples of what to talk about).
Document these as part of the Final Report ASAP.

Matt - Place parts order when available, write BLE material for final report ASAP.

Meeting activity:
- All members present, all worked on writing and compiling the report. Anticipated deadline following Monday (along with poster submission).

Upcoming Deadlines:
- Design Poster (Monday, 16 November)
- Final Report (Monday, 16 November)

Notifications:
- Everybody must start writing documentation/report material for their work and use Word format, submit to Google Drive folder "FINAL REPORT". All material is PAST DUE. Submit ASAP.

Notes:
- Write Word doc updates on each of your weekly tasks and use them to compile your section of the Final Report.
- Use Word docs for compiling your final report material
- Check your email and this blog frequently

- Here's what we need to develop for the Final Report:


1) A complete parts list for the project must be formed

2) The project circuits/schematics must be captured/simulated to prove design

3) The errors/weak spots of the midterm report must be addressed

4) More background must be researched/provided

5) Review design specs - All design choices must be supported with analysis

6) Provide Analysis of complete design - All design choices must be supported with analysis

7) Schematics include pin-out level, RefDes #s

8) Software flowcharts/pseudocode, algorithms simulated, libraries tested, OS formed

9) processors documented and required software identified, communications described


Breakdown:
Sam - 1, 2, 3,      5, 6, 7
Ian -           3,      5, 6,     8, 9
Ogi -           3, 4, 5
Matt - 1, 2, 3,      5, 6, 7

November Update #2

Accomplished this past week:
Sam - Worked on BOM. Need to find some parts.
Task Incomplete

Ian - Worked on pseudocode.
Task Incomplete

Ogi - Contacted Dr. Bao about camera budget, researching feasible camera models to use.
Task incomplete

Matt- Worked on Poster, set up organization for final report, began forming final report, parts order waiting in Ogi and Sam
Task Complete/Contingent

Goals for this week:
Sam - Focus on documenting power circuit design, provide analysis for final report and revise material from midterm report. Begin to document this as part of the Final Report. Get Bill of Materials finished ASAP.

Ian - Focus on pseudocode for project, document and analyze software needs (streaming, libraries, everything needed to prove that software needs are analyzed and addressed.) Begin to document this as part of the Final Report.

Ogi - Finish camera task ASAP (select model and get it approved for purchase by Dr. Bao). Focus on more background research on how the technologies are used in a relevant sense (see old reports for examples of what to talk about). Begin to document this as part of the Final Report.

Matt - Place parts order when possible, hash out poster design, continue compiling Final Report

Meeting activity:
- Sam and Matt briefly discussed the report.

Upcoming Deadlines:
- Design Poster (Monday, 16 November)
- Final Report (Monday, 16 November)

Notifications:
- Everybody must start writing documentation/report material for their work and use Word format, submit to Google Drive folder "FINAL REPORT"

Notes:
- Write Word doc updates on each of your weekly tasks and use them to compile your section of the Final Report.

- Use Word docs for compiling your final report material

- Check your email and this blog frequently

- Here's what we need to develop for the Final Report:



1) A complete parts list for the project must be formed

2) The project circuits/schematics must be captured/simulated to prove design

3) The errors/weak spots of the midterm report must be addressed

4) More background must be researched/provided

5) Review design specs - All design choices must be supported with analysis

6) Provide Analysis of complete design - All design choices must be supported with analysis

7) Schematics include pin-out level, RefDes #s

8) Software flowcharts/pseudocode, algorithms simulated, libraries tested, OS formed

9) processors documented and required software identified, communications described


Breakdown:
Sam - 1, 2, 3,     5, 6, 7
Ian -           3,     5, 6,    8, 9
Ogi -          3, 4, 5
Matt - 1, 2, 3,     5, 6, 7

November Update #1

Accomplished this past week:

Sam - Completed power circuit design; Completed Digikey shopping cart for power circuit - will confirm with Supel.
Task complete

Ian - Got servos moving on Beagle. Tested input values.
Task complete.

Ogi - Long camera list is presented. Still need to select top model picks and propose to Dr. Bao.
Task incomplete

Matt- Developed parts ordering, developed budget management, compiled BOM - still needs Sam's parts to order.
Task complete.

Goals for this week:

All - CATME survey

Sam - Work on documenting power circuit design, provide analysis for final report and revise material from midterm report.

Ian - Develop pseudocode for project, document and analyze software needs (streaming, libraries, everything needed to prove that software needs are analyzed and addressed.) Begin to document this as part of the Final Report.

Ogi - Finish camera task (select model and get it approved for purchase by Dr. Bao). Develop more background research on how the technologies are used in a relevant sense (see old reports for examples of what to talk about).

Matt - Order parts, hash out poster design by next week, begin compiling Final Report

Meeting activity:

- Ian and Igor got the HS-422 servo up and moving on the Beaglebone. Ogi and Sam absent. Matt began laying out the poster design and discussed Beagle PWM with Ian.

Upcoming Deadlines:

- Design Poster (Monday, 16 November)
- Final Report (Monday, 16 November)

Notes:

- Write Word doc updates on each of your weekly tasks and use them to compile your section of the Final Report.

- Use Word docs for compiling your final report material

- Check your email and this blog frequently 

- Here's what we need to develop for the Final Report:

1) A complete parts list for the project must be formed

2) The project circuits/schematics must be captured/simulated to prove design

3) The errors/weak spots of the midterm report must be addressed

4) More background must be researched/provided

5) Review design specs - All design choices must be supported with analysis

6) Provide Analysis of complete design - All design choices must be supported with analysis

7) Schematics include pin-out level, RefDes #s

8)  Software flowcharts/pseudocode, algorithms simulated, libraries tested, OS formed

9) processors documented and required software identified, communications described

Breakdown:
Sam - 1, 2, 3,    5, 6, 7

Ian -           3,    5, 6,    8, 9

Ogi -          3, 4, 5

Matt - 1, 2, 3,     5, 6, 7

Power Supply BOM

Good Morning Gents,

I've attached a link to my digikey shopping cart here:

http://www.digikey.com/classic/Ordering/AddPart.aspx?lang=en

This is the majority of the parts I will need but I would like to have Supel take a look at it to see if it can be optimized (cost etc.) because after talking with him Friday he knows a lot about these sorts of components.

Cheers

Mechanical Models

< CAD Models for the servo mounting hardware >

MJT

Digital Cameras - Ogi

So I've gone through the whole camera list and this is the list i came up with. Amazon has the best prices by far due to the fact that we can also buy used ones! Keep in mind this list is not that long. A lot of the cameras are just the better version of the previews one! We can all sit down tomorrow and find the top 3 we like! we will look at price, weight, availability, look, etc. Okay ill see you guys tomorrow and run through this list with all of you! Cheers Ogi!!!!! 

· Canon PowerShot A80

· Canon PowerShot A85

· Canon PowerShot A520

· Canon PowerShot A620

· Canon PowerShot A640

· Canon PowerShot G6

· Canon PowerShot G7

· Canon PowerShot S40

· Canon PowerShot S45

· Canon PowerShot S230

· Nikon CoolPix 880

· Nikon CoolPix 5700

· Olympus C-2040Z

http://gphoto.org/doc/remote/

Some potentially useful products I've found recently:

Metal Gear Servo
Feedback Servo
Reference Servo
HS-422 Servo
Mounting Kit
Shoe Mount
D Screw
1/4in Screw
Adapter screw

MJT