February Update #2

Weekly Tasks accomplished:
- Beaglebone Servo control running
- PCB design completed
- Parts received (SDM, BT)

Tasks left:
-Fab power circuit

- Characterize servos
-Connect Camera Cape
-Connect bluetooth module
-Stream video via camera cape
-Connect bluetooth to phone
-Build app
-Environmental testing

Status breakdown for this week:
Ogi - Found ribbon cable parts
Sam - Completed power circuit PCB design
Ian - Got servo library working on BBB, began work on external camera connection
Matt - Bluetooth model selected and received, servos tested, oversee cable research

Task breakdown for this week:
Ogi - Order ribbon cable parts
Sam - Fab power board, prototype TH circuit
Ian - Get external camera to take pictures, store them
Matt - Characterize servos, try BT module

Resolved issues:
- Servos working
- Ribbon cable parts identified

Current issues:
- Ordering Ribbon cable parts in timely manner

Potential upcoming issues:
- Not getting ribbon cable on time

Ribbon Cable Parts

5' Ribbon Cable - $6 ea
Connector Piece - $6 ea

These are from Digikey. Ogi is looking into whether Mouser/Newark would have cheaper alternatives.

-M

Camera Pick

I have narrowed down the camera options to the best possible one.
We will be working with the Canon Powershot SX110IS and the link for it is below.

http://www.amazon.com/Canon-Powershot-SX110IS-Stabilized-Black/dp/B001EQ4C8U/ref=sr_1_1?s=photo&ie=UTF8&qid=1454434867&sr=1-1&keywords=Canon+PowerShot+SX110+IS

It is super light and fits our dimensions best as well as all the gphoto capabilities.

-Ogi

February Update #1

Weekly Tasks accomplished:
- Drake OS up and running
- PCB design progress
-PAS digital camera selected

Tasks left:
-Fab power circuit
-Set up Drake OS
-Connect Camera Cape
-Connect bluetooth module
-Stream video via camera cape
-Connect bluetooth to phone
-Build app
-Environmental testing

Status breakdown for this week:
Ogi - Investigated ribbon cable parts, selected new PAS camera
Sam - Progressed on power circuit layout
Ian - Investigated new BL modules, began Drake OS, installed libraries, beginning coding
Matt - bluetooth researched, servos tested, new mounting hardware found, 3D model progress

Task breakdown for this week:
Ogi - Find good price for ribbon cable, order
Sam - Lay out schematic and PCB of power circuit, fab
Ian - Lay out Drake OS, set up subversion
Matt - Find new BT module, design TITAN 3D case, confirm servo test

Resolved issues:
- Lighter POS cam selected
- Libraries installed on BBB
- Ribbon cable parts identified

Current issues:
- RadiumBoards unresponsive
- Ribbon cable parts from digikey expensive
- Analog Servo maybe no work
- Laying out TITAN case dimensions

Potential upcoming issues:
- Not finding part libraries (Sam)

January Update #X

Tasks accomplished:
- Initial Parts Order
- Initial Hardware design
- Initial Parts research
- Parts recieved

Tasks left:
-Build power circuit
-Set up Beaglebone
-Connect Camera Cape
-Connect bluetooth module
-Stream video via camera cape
-Connect bluetooth to phone
-Build app

Status breakdown for this week:
Ogi - Emailed Radium boards to get longer ribbon cable
Sam - Developed TH schematic, studied layout with Igor, began developing SMD schematic
Ian - Research packages to install, servo working, OS laid out, software layout worked out
Matt - Hardware researched, bluetooth researched, servos assembled

Task breakdown for this week:
Ogi - Contacting Radiumboards & protoboards, bring mini USb cable+Charger, research cam
Sam - Lay out schematic and PCB of power circuit, fab if ready on time
Ian - Set up Beaglebone, connect camera cape, bluetooth if ready
Matt - Solder leads to prototyping parts, design TITAN 3D case

Resolved issues:
- Radium boards contact - Ogi has established email contact
- Power board layout - Sam is now familiar with PCB layout
- Bluetooth module selection - completed by Ian and Matt

Current issues:
- Bluetooth module footprint
- Setting up beaglebone
- Analog Servo size
- Laying out TITAN case dimensions
- Getting Amazon parts

Potential upcoming issues:
- BBB not getting internet on campus (Ian)
- Not finding part libraries (Sam)

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