ME 333 end of course schedule - Revision history

Lynch: /* Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms */

2010-03-12T12:42:38Z

Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms

Lynch: /* Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms */

2010-03-12T12:41:59Z

Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms

Lynch: /* Final Wiki Page */

2010-03-12T12:39:38Z

Final Wiki Page

Lynch: /* Final Wiki Page */

2010-03-12T12:38:37Z

Final Wiki Page

Lynch: /* Final Wiki Page */

2010-03-12T12:38:25Z

Final Wiki Page

Lynch: /* Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms */

2010-03-12T02:18:45Z

Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms

Lynch at 23:01, 11 March 2010

2010-03-11T23:01:33Z

Lynch: /* Final Wiki Page */

2010-03-11T22:57:40Z

Final Wiki Page

Lynch: /* Final Wiki Page */

2010-03-11T22:55:33Z

Final Wiki Page

Lynch: /* Final Wiki Page */

2010-03-11T22:54:45Z

Final Wiki Page

@@ Line 29: / Line 29: @@
 == Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms ==
-You should return everything you were issued during the course.  You will return to Rick Marzec:  your lab kits, including (but not necessarily limited to) the 5V wall brick for the PIC boards, USB-RS232 cable, NU32 board + USB cable + LCD display (unless you wish to purchase these; Prof. Lynch will provide more info), multimeter, batteries, battery charger, wall power adapter (+/-12V, 5V), two breadboard power boardlets, large breadboard, small breadboard, wire strippers, LCDs, etc.; all materials lent to you for the purposes of your final project or Lab 5 (e.g., motors, cables, sensors, power supplies, etc.); and all items that you wish to be reimbursed for.  He will be available in the lab during finals week on Monday from 10-11 AM and Thursday from 10-11 AM, and he will verify that everything has been returned.  If anything you are returning is not functioning properly, including your NU32 board, be sure to let Rick know, so that it does not get assigned to another team in the future.
+You should return everything you were issued during the course.  You will return to Rick Marzec:  your lab kits, including (but not necessarily limited to) the 5V wall brick for the PIC boards, USB-RS232 cable, NU32 board + USB cable + LCD display (unless you wish to purchase these; Prof. Lynch will provide more info), multimeter, batteries, battery charger, wall power adapter (+/-12V, 5V), two breadboard power boardlets, large breadboard, small breadboard, wire strippers, LCDs, etc.; all materials lent to you for the purposes of your final project or Lab 5 (e.g., motors, cables, sensors, power supplies, etc.); and all items that you wish to be reimbursed for.  Rick will be available in the lab during finals week on Monday from 10-11 AM and Thursday from 10-11 AM, and he will verify that everything has been returned.  If anything you are returning is not functioning properly, including your NU32 board, be sure to let Rick know, so that it does not get assigned to another team in the future.
 At this time you should also return all lab keys for your group.  If you have a reason you'd like continued access to the lab, email Prof. Lynch with cc to Rick Marzec, r-marzec at northwestern.edu.  Similarly, if you'd like to be able to continue editing the wiki, send an email to Prof. Lynch with cc to Rick.

@@ Line 29: / Line 29: @@
 == Returning Your Equipment and Keys, and Submitting Your Reimbursement Forms ==
-The following items must be returned to Rick Marzec in the mechatronics lab:  your lab kits, consisting of the 5V wall brick for the PIC boards, USB-RS232 cable, NU32 board + USB cable + LCD display (unless you wish to purchase these; Prof. Lynch will provide more info), multimeter, batteries, battery charger, wall power adapter (+/-12V, 5V), two breadboard power boardlets, large breadboard, small breadboard, wire strippers, LCDs, etc.; all materials lent to you for the purposes of your final project or Lab 5 (e.g., motors, cables, sensors, power supplies, etc.); and all items that you wish to be reimbursed for.  He will be available in the lab during finals week on Monday from 10-11 AM and Thursday from 10-11 AM, and he will verify that everything has been returned.  If anything you are returning is not functioning properly, including your NU32 board, be sure to let Rick know, so that it does not get assigned to another team in the future.
+You should return everything you were issued during the course.  You will return to Rick Marzec:  your lab kits, including (but not necessarily limited to) the 5V wall brick for the PIC boards, USB-RS232 cable, NU32 board + USB cable + LCD display (unless you wish to purchase these; Prof. Lynch will provide more info), multimeter, batteries, battery charger, wall power adapter (+/-12V, 5V), two breadboard power boardlets, large breadboard, small breadboard, wire strippers, LCDs, etc.; all materials lent to you for the purposes of your final project or Lab 5 (e.g., motors, cables, sensors, power supplies, etc.); and all items that you wish to be reimbursed for.  He will be available in the lab during finals week on Monday from 10-11 AM and Thursday from 10-11 AM, and he will verify that everything has been returned.  If anything you are returning is not functioning properly, including your NU32 board, be sure to let Rick know, so that it does not get assigned to another team in the future.
 At this time you should also return all lab keys for your group.  If you have a reason you'd like continued access to the lab, email Prof. Lynch with cc to Rick Marzec, r-marzec at northwestern.edu.  Similarly, if you'd like to be able to continue editing the wiki, send an email to Prof. Lynch with cc to Rick.

@@ Line 19: / Line 19: @@
 '''Links.'''  When you include a link to a page on the mechatronics wiki, please make it an internal link instead of an external link, so if the host server for the wiki ever changes, the link will still work.  For example, refer to the accelerometers page [[Accelerometers|like this]] (using the code <nowiki>[[Accelerometers|like this]]</nowiki>) instead of [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this] (using the code <nowiki>[http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this]</nowiki>).
-'''Page content.'''  Your wiki page should have at least one picture of the entire system, showing clearly what it is.  Generally, your wiki page should start out with this picture, names of the team members, a picture of the team (you can use the picture taken of your group during lab, if you wish), and a brief overview of what your project is and how it works.  Then you should have subsections:  mechanical design, electrical design, code, and results and reflections.  The overriding goals are for the page to be useful to future students who will look at the page, and to give enough detail to allow someone else to duplicate your project.  The mechanical and electrical design sections should have lists of parts used (including part numbers, vendors, and cost, when available).  The mechanical design section should have clear drawings, or sufficiently clear pictures.  Circuit schematics should be given for all non-obvious circuits.  The results and reflections section should give an honest assessment of how well your project turned out, and what you would do differently if you could do it again.
+'''Page content.'''  Your wiki page should have at least one picture of the entire system, showing clearly what it is, as well as link to a youtube video.  Generally, your wiki page should start out with this picture, names of the team members, a picture of the team (you can use the picture taken of your group during lab, if you wish), and a brief overview of what your project is and how it works.  Then you should have subsections:  mechanical design, electrical design, code, and results and reflections.  The overriding goals are for the page to be useful to future students who will look at the page, and to give enough detail to allow someone else to duplicate your project.  The mechanical and electrical design sections should have lists of parts used (including part numbers, vendors, and cost, when available).  The mechanical design section should have clear drawings, or sufficiently clear pictures.  Circuit schematics should be given for all non-obvious circuits.  The results and reflections section should give an honest assessment of how well your project turned out, and what you would do differently if you could do it again.
 '''Images.'''  In most cases, the images as viewed in the wiki page should be relatively small -- big enough that the image is useful, but not so big that the page is huge or the flow of the wiki page is disrupted.  When the user clicks on the image, they can see the larger image for more detail.

@@ Line 15: / Line 15: @@
 Following the examples on the [[ME_333_final_projects|ME 333 final projects page]], choose a name for your final project.  Upload a picture (and include it as a thumbnail) and write a couple of sentence description.  Then click on the link to begin editing your wiki page.  '''Make sure that the pages you create have a brief but descriptive title.  In fact, all files you upload and pages you create must have unique names.'''  (For uploaded files, you can do this by inserting the initials of your team members in the file name of every file you upload; for example, if your names are Mike Hwang/Andy Long/Clara Smart, use the file name MH_AL_CS-ProjectPhoto.jpg to make sure there are no interfering file names.)  Ideally, your entire project should be put on a single wiki page (unless you are documenting a useful new capability; see below), along with links to any pdf files, images, code, movies, text files, or whatever helps explain your project.  Be reasonable; don't upload giant files.  Generally, you should keep the total amount of uploaded material to less than 10 MB, often much less.  You should have at least one good video of your project working.  It is fine to include bloopers in the video, but show it working well in at least one video!  Videos are best posted on youtube with links pointing to them.  We will then link these to the NUmechatronics channel.
-'''NU32 PIC board.''' If you "burned out" a PIC on your board, you should document what you think caused it, in your "results and reflections" section at the end.  There are many ways you can destroy the PIC on your board, and most of these are not preventable in the board design.  But if you have a '''specific''' idea for a redesign of the board, please indicate.
+'''NU32 PIC board.''' If you "burned out" the PIC on your board, you should document what you think caused it, in your "results and reflections" section at the end.  There are many ways you can destroy the PIC on your board, and most of these are not preventable in the board design.  But if you have a '''specific''' idea for a redesign of the board, please indicate.
 '''Links.'''  When you include a link to a page on the mechatronics wiki, please make it an internal link instead of an external link, so if the host server for the wiki ever changes, the link will still work.  For example, refer to the accelerometers page [[Accelerometers|like this]] (using the code <nowiki>[[Accelerometers|like this]]</nowiki>) instead of [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this] (using the code <nowiki>[http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this]</nowiki>).

@@ Line 14: / Line 14: @@
 Following the examples on the [[ME_333_final_projects|ME 333 final projects page]], choose a name for your final project.  Upload a picture (and include it as a thumbnail) and write a couple of sentence description.  Then click on the link to begin editing your wiki page.  '''Make sure that the pages you create have a brief but descriptive title.  In fact, all files you upload and pages you create must have unique names.'''  (For uploaded files, you can do this by inserting the initials of your team members in the file name of every file you upload; for example, if your names are Mike Hwang/Andy Long/Clara Smart, use the file name MH_AL_CS-ProjectPhoto.jpg to make sure there are no interfering file names.)  Ideally, your entire project should be put on a single wiki page (unless you are documenting a useful new capability; see below), along with links to any pdf files, images, code, movies, text files, or whatever helps explain your project.  Be reasonable; don't upload giant files.  Generally, you should keep the total amount of uploaded material to less than 10 MB, often much less.  You should have at least one good video of your project working.  It is fine to include bloopers in the video, but show it working well in at least one video!  Videos are best posted on youtube with links pointing to them.  We will then link these to the NUmechatronics channel.
+'''NU32 PIC board.''' If you "burned out" a PIC on your board, you should document what you think caused it, in your "results and reflections" section at the end.  There are many ways you can destroy the PIC on your board, and most of these are not preventable in the board design.  But if you have a '''specific''' idea for a redesign of the board, please indicate.
 '''Links.'''  When you include a link to a page on the mechatronics wiki, please make it an internal link instead of an external link, so if the host server for the wiki ever changes, the link will still work.  For example, refer to the accelerometers page [[Accelerometers|like this]] (using the code <nowiki>[[Accelerometers|like this]]</nowiki>) instead of [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this] (using the code <nowiki>[http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this]</nowiki>).

@@ Line 1: / Line 1: @@
 '''Thursday, Week 10:'''  Meet in the Mechatronics Lab by 12:30 for final project demos. All projects must be demo'ed in only 80 minutes, so you must be ready to demo promptly at 12:30. You will give grades for each project and vote for the Outstanding Project.
-'''Friday, Week 10:'''  Demo in the Tech lobby. The demo will begin promptly at 11:30 and be finished by 1:00. You should bring your project, ready to demo, to the lobby by 11:30. We will be bringing power supplies from the Mechatronics Lab starting at 11:00. Each group is required to demo, though not all team members must be present.  You should make a sign (a sheet of paper is fine) with the name of your project, printed large, and a couple of sentences that explains what it does.
+'''Friday, Week 10:'''  Demo in the Tech lobby. The demo will begin promptly at 11:30 and be finished by 1:00. You should bring your project, ready to demo, to the lobby by 11:30. We will be bringing power supplies and other equipment from the Mechatronics Lab starting at 11:00. Each group is required to demo, though not all team members must be present.  You should make a sign (a sheet of paper is fine) with the name of your project, printed large, and a couple of sentences that explains what it does.
 '''Finals week:'''  Return your project equipment and lab keys (see below).

@@ Line 13: / Line 13: @@
 == Final Wiki Page ==
-Following the examples on the [[ME_333_final_projects|ME 333 final projects page]], choose a name for your final project.  Upload a picture (and include it as a thumbnail) and write a couple of sentence description.  Then click on the link to begin editing your wiki page.  '''Make sure that the pages you create have a brief but descriptive title.  In fact, all files you upload and pages you create must have unique names.'''  (For uploaded files, you can do this by inserting the initials of your team members in the file name of every file you upload; for example, if your names are Mike Hwang/Andy Long/Clara Smart, use the file name MH_AL_CS-ProjectPhoto.jpg to make sure there are no interfering file names.)  Ideally, your entire project should be put on a single wiki page (unless you are documenting a useful new capability; see below), along with links to any pdf files, images, code, movies, text files, or whatever helps explain your project.  Be reasonable; don't upload giant files.  Generally, you should keep the total amount of uploaded material to less than 10 MB, often much less.  Videos are best posted on youtube (or similar) with links pointing to them.
+Following the examples on the [[ME_333_final_projects|ME 333 final projects page]], choose a name for your final project.  Upload a picture (and include it as a thumbnail) and write a couple of sentence description.  Then click on the link to begin editing your wiki page.  '''Make sure that the pages you create have a brief but descriptive title.  In fact, all files you upload and pages you create must have unique names.'''  (For uploaded files, you can do this by inserting the initials of your team members in the file name of every file you upload; for example, if your names are Mike Hwang/Andy Long/Clara Smart, use the file name MH_AL_CS-ProjectPhoto.jpg to make sure there are no interfering file names.)  Ideally, your entire project should be put on a single wiki page (unless you are documenting a useful new capability; see below), along with links to any pdf files, images, code, movies, text files, or whatever helps explain your project.  Be reasonable; don't upload giant files.  Generally, you should keep the total amount of uploaded material to less than 10 MB, often much less.  You should have at least one good video of your project working.  It is fine to include bloopers in the video, but show it working well in at least one video!  Videos are best posted on youtube with links pointing to them.  We will then link these to the NUmechatronics channel.
 '''Links.'''  When you include a link to a page on the mechatronics wiki, please make it an internal link instead of an external link, so if the host server for the wiki ever changes, the link will still work.  For example, refer to the accelerometers page [[Accelerometers|like this]] (using the code <nowiki>[[Accelerometers|like this]]</nowiki>) instead of [http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this] (using the code <nowiki>[http://hades.mech.northwestern.edu/wiki/index.php/Accelerometers like this]</nowiki>).