Instead of a printed final report, ME 333 uses web reports. With very little more work than a written report, you can create a site that is accessible to others and much more effective at communicating your design.

You are free to design the web site as you like. Content is more important than style, and your site must meet the following guidelines.

• The site must have an "index.html" (or "index.htm") file for the home page.
• There should be no spaces or commas in any of the file names.
• Our file server is case sensitive. So if you have a file called "picture.jpg", you must refer to it as "picture.jpg" when you link to it, not "picture.JPG" or "PICTURE.JPG".
• All files for the site must be in a single directory (no nested sub-directories).
• The site must have at least one photo showing the whole project. Other photos, which help demonstrate the functioning of the system, are encouraged.
• The site must have an introductory page, with a picture of the mechatronic system and a brief description of what it does.
• The site must have a "results and reflections" page which describes how well the project worked and how it could have been improved.
• The site must have a software page which includes the complete .mdl file of your final project, as well as information on any workspace variables that must be set when compiling the model file (e.g., the timestep used or other data). This page should also have screen shots showing the model, with descriptive names for the blocks so the function is clear. It should have an overview of how the software works and how the user interacts with it after startup. You may use flow charts, for example. Finally, you should highlight lessons you learned in programming in Simulink that would be useful to future groups.
• Give sufficient information on how the project was built that it could be reproduced without excessive effort. You can break this down into mechanical, electrical, and software subsections, or however you want. You should include
  • A list of parts and materials used, and where possible, the vendor, part number, and price.
  • Circuit diagrams for non-obvious circuits. These may be carefully hand-drawn and scanned, but preferably generated using a drawing program. Any drawing program is fine.
  • Drawings, or sufficiently clear pictures, of the mechanical systems with brief supporting text descriptions.