Difference between revisions of "ME 333 Lab 5"

From Mech
Jump to navigationJump to search
Line 1: Line 1:
In Lab 5, you will create your own wiki page describing some useful PIC-related function. Good resources include this mechatronics wiki itself (some of these functions may be partially documented), the [http://www.ccsinfo.com|PIC C compiler website] and sample code that comes with the compiler, the two manuals with the PIC C compiler, application notes at the [http://www.microchip.com|Microchip website], and just general google searches on the topic.
In Lab 5, you will create your own wiki page describing some useful PIC-related function. Good resources include this mechatronics wiki itself (some of these functions may be partially documented), the [http://www.ccsinfo.com PIC C compiler website] and sample code that comes with the compiler, the two manuals with the PIC C compiler, application notes at the [http://www.microchip.com Microchip website], and just general google searches on the topic.


Each page should have four headings: Original Assignment, Objective, Circuit, and Code. See the [[Example Writeup]] for an example. The Original Assignment indicates what you were assigned to do, and will eventually be erased from the final page. The Objective is your rewritten version that clearly indicates what the page is about (to future students accessing the page), the Circuit shows a professional-looking black and white circuit diagram as well as a photo of a neatly wired implementation of the circuit, and Code gives a listing of the liberally commented code, which should otherwise be as simple as possible (do not have extraneous lines of code that don't relate directly to the objective of the page).
Each page should have four headings: Original Assignment, Objective, Circuit, and Code. See the [[Example Writeup]] for an example. The Original Assignment indicates what you were assigned to do, and will eventually be erased from the final page. The Objective is your rewritten version that clearly indicates what the page is about (to future students accessing the page), the Circuit shows a professional-looking black and white circuit diagram as well as a photo of a neatly wired implementation of the circuit, and Code gives a listing of the liberally commented code, which should otherwise be as simple as possible (do not have extraneous lines of code that don't relate directly to the objective of the page).

Revision as of 11:59, 26 January 2008

In Lab 5, you will create your own wiki page describing some useful PIC-related function. Good resources include this mechatronics wiki itself (some of these functions may be partially documented), the PIC C compiler website and sample code that comes with the compiler, the two manuals with the PIC C compiler, application notes at the Microchip website, and just general google searches on the topic.

Each page should have four headings: Original Assignment, Objective, Circuit, and Code. See the Example Writeup for an example. The Original Assignment indicates what you were assigned to do, and will eventually be erased from the final page. The Objective is your rewritten version that clearly indicates what the page is about (to future students accessing the page), the Circuit shows a professional-looking black and white circuit diagram as well as a photo of a neatly wired implementation of the circuit, and Code gives a listing of the liberally commented code, which should otherwise be as simple as possible (do not have extraneous lines of code that don't relate directly to the objective of the page).

You are welcome to change the structure of your page to something other than the four headings if necessary to improve the clarity of the page, but don't erase the Original Assignment.

Every topic that uses interrupts to implement a function should report how long it takes the interrupt to complete the service routine. One way to do this is to set a digital output pin "high" at the beginning of the interrupt service routine, then set it low at the end. Then look at this digital output on an oscilloscope. If the interrupt routine is occurring every 1 ms, then you should see a pulse every 1 ms, and the duration of the pulse tells you approximately how much time it takes your ISR to execute. If you don't clearly see a pulse of less than 1 ms every 1 ms, then your ISR may be taking more than its allotted time, and you need to either increase the time between ISR calls or decrease the complexity of your code in the ISR. Remember that bitwise operations such as &, |, >>, or << are fast, math operations on unsigned integers are slower, math operations on signed integers are slower still, math operations on floats are slower still, and trigonometric and other complex functions are very slow. If you have two different ISRs, say one at 1 ms intervals and another at 13 ms intervals, use a different pin to time each and display the two channels simultaneously on your oscilloscope to understand the timing.

Your lab will be graded on functionality (how well you have completed the objective) and the usefulness of your wiki page (how clearly it is written and documented with images or other supporting material). If you use figures or information you found elsewhere on the web, give a citation (link) to the original source.