Questions:

• What walls did you guys use? What kind of materials?
• Do you guys have pictures of the locations you guys used for your testing?
• What are your deliverables for the end of the semester
• What is the difference between the XBee X3B and Xbee 900?
• Is the information about the problems you had with metal documented on the wiki?
• What are the pros/cons of using the XBee 900?

Comments:

• It would probably better to continue to use the laptops today
• For the next meeting, think about how your team falls into place in the lab. What is the purpose of your team?
• Good, mentioned things that other teams could use
• Tables are too small to read (reformat these)

Questions:

• What are your deliverables for the end of the semester?
• Other problems and concerns for the semester?
• Did you guys write down your comments about the power budget? If not, you should guys should write it down somewhere. The wiki is a good place.
• What sensors do you have that are 3v that need to communicate to the 5v microcontroller

Comments:

• Make sure you test the caps in series (to achieve the same result)
• Make summerizations about each of your spreadsheets and also present that next time
• (It was good that you guys showed the tables)
• Receiving 3v signals on a 5v micro-controller is fine for some applications - depends on the application.

Questions:

• Can you share eagle parts easily?
• Have you guys been writing down a change log?

Comments:

• Good summary of the power budget!
• The slide about inter-team collaboration is good. Thanks for including that.
• Via Dr. Kuh (write some best practices down for other people)

Ideas:

• We might want to have a place on the wiki that documents best practices
• Maybe a place to put parts for everyone also

Questions:

• What are your deliverables for the end of the semester?
• How long do you expect the box to last without sun?
• What is the size of your housing box?
• Is Andy's thesis and any other relevant papers on the wiki?
• What other teams are you communicating with?

Comments:

• Block diagram instead of circuit so that people can follow
• Good job splitting the presentation between multiple people

Questions:

• Not tackling power? Can you explain this a little more?
• What are your final deliverables for the semester?
• You mentioned an anemometer?
• Is the checklist on the wiki somewhere?
• Are you sure of your team's place is now? Can you write it down?

Comments:

• Block diagram should be more detailed
• Same thing as before - showing the schematic might be hard to follow if you're just explaining it.
• You should communicate with the other teams to know what you're doing.
• At the end of the semester, communicate with apple to merge your documentation (you mentioned this).
• Thanks for documenting the microcontroller… we should setup a review date for the documentation sometime.
• The other teams should be along enough to ask more questions. If not, ask questions from the advisors/leads.

Questions:

• What are your final deliverables?
• Do you have plans to add documentation to modify the firmware for someone else?
• Are you guys using versioning?

Comments:

• Images of code might be hard to read for the audience. Suggest you summarize them in text.. or use a block diagram
• Specific code segments are implementations are okay.
• Might think of a way next semester to generate documentation.

Questions:

• Manual packing - what does that mean?
• What are you final deliverables for the end of the semester?

Comments:

• Images of code might be hard for the audience to read. Suggest you summarize them in text.. or use block diagram with function headers.
• Make sure that you have a block diagram of where your system is?
• Need more details in the CDR - you should have almost all of your system implementation by this point.

Questions:

• How are you guys accounting for direction?

Comments:

• Maybe talk to the firmware team to talk about implementation details
• Should explain how direction is working next time for the final presentations
• Good technical material.

Questions:

• Final deliverables?
• What are you guys attempting to do in terms of forecasting?

Comments:

• Could integrate more into the other teams next semester; comments regarding what type of data you guys need.
• Real time data processing - could have the other teams implement it later on.

• We need to anticipate to have more questions
• Need a way to measure the current consumption for a device - this way we can accurately measure the power profile for an XBee. This could be a project that we do next semester with someone since it would be a good tool for our lab. Possibly look if there is already a tool that can do this.
• We need a logic analyzer for our lab? Debug logic signals…

• Continue development of the power budget template.
• Maybe we should include something in the requirements for the CDR regarding communication with other teams.. maybe this should be in the other presentations as well.
• Comments about putting circuit diagrams in presentations - they're hard to follow.

• This semester's recruits: “Cohort #1”. We could do something for the next semesters as well, and group people like that.
• Guidelines regarding putting code in a powerpoint → shouldn't screenshot code
• Need to have a section for guidelines in the project management page about if people fall behind for something
• These presentations should have schedule.

• We need to define these presentations a little more for students, or at least tell them they should watch out for certain things. Audience, presentation type (technical, non-technical, etc).
• Might need to split the final presentation into two sessions (they're meant to be longer).

• The way you present matters in these kinds of presentations - word choice matters. Don't say we're pretty sure. (Need to get the rest of the comments from Jon).

Contributing authors:

Created by kluong on 2015/11/21 20:48.