Lab46 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<WRAP centeralign round box>
<WRAP><color red><fs 200%>Corning Community College</fs></color></WRAP>
<WRAP><fs 150%>ENGR1050 C for Engineers</fs></WRAP>
</WRAP>

======PROJECT: Press The Button (PTB1)======

=====OBJECTIVE=====
Revisiting our LED binary counter (with expanded capacity), this time with buttons to control the count (up/down by one), and optimizing our LED lighting logic with a loop to cut down on the individual position if statements needed.

=====PROCESS=====
Do note, the productive way to go about this project involves taking the following steps:

  * starting early
  * reading the project page
  * asking questions regarding things you do not know, are not clear on, or are confused about
  * as information, concepts, processes become clear, that is something you can contribute to the project documentation (so you can better remember)

If you start too late, and do not ask questions, and do not have enough time and don't know what is going on, you are not doing the project correctly.

=====TASK=====
Taking our knowledge of LEDs and buttons:

  * wire up the 10 element LED bar to individual wiringPi GPIOs (have 8-10 usable LEDs for the count)
  * wire up 2 buttons to individual wiringPi GPIOs
    * one button will be the increment button, increasing the value of the count by 1
    * one button will be the decrement button, decreasing the value of the count by 1
  * unless a button is pressed, the count remains on the current value
    * when the increment button is pressed, the count proceeds to count up by 1
    * when the decrement button is pressed, the count proceeds to count down by 1
=====GRABIT=====
To assist with consistency across all implementations, data files for use with this project are available on lab46 via the **grabit** tool. Be sure to obtain it and ensure your implementation properly works with the provided data.

<cli>
lab46:~/src/SEMESTER/DESIG$ grabit DESIG PROJECT
</cli>

=====EDIT=====
You will want to go [[/notes/c4eng/fall2024/projects/ptb1|here]] to edit and fill in the various sections of the document:

  * [[/notes/c4eng/fall2024/projects/ptb1|https://lab46.g7n.org/notes/c4eng/fall2024/projects/ptb1]]

{{page>notes:c4eng:fall2024:projects:ptb1&nouser&nodate&nomdate}}

=====STRATEGY=====
The general flow of the process (one way of going about it, anyway) can be described as follows:

<code>
SET COUNT TO ZERO
REPEAT INFINITELY:
    SHOULD THE INCREMENT BUTTON BE PRESSED:
        INCREMENT COUNT BY ONE
    
    SHOULD THE DECREMENT BUTTON BE PRESSED:
        DECREMENT COUNT BY ONE

    BIT POSITION IS ONE
    LED OFFSET IS ZERO
    REPEAT AS LONG AS LED OFFSET IS LESS THAN TEN:
        SHOULD THE CURRENT BIT POSITION HAVE A ONE:
            ACTIVATE THE LED AT CURRENT OFFSET
        OTHERWISE:
            DEACTIVATE THE LED AT CURRENT OFFSET

        LEFT SHIFT BIT POSITION BY ONE
        LED OFFSET IS INCREMENTED BY ONE
    COMMENT: INNER REPEAT CONCLUDES
    
    DELAY AT LEAST FIFTY MILLISECONDS

COMMENT: INFINITE REPEAT BLOCK CONCLUDES
</code>

=====SUBMISSION=====
To be successful in this project, the following criteria (or their equivalent) must be met:

  * Project must be submit on time, by the deadline.
    * Late submissions will lose 33%  credit per day, with the submission window closing on the 3rd day following the deadline.
  * All code must compile cleanly (no warnings or errors)
    * Compile with the **-Wall** and **--std=gnu18** compiler flags
    * all  requested functionality  must conform  to stated  requirements (either on  this document or  in a comment banner in  source code files themselves).
  * Executed programs must display in a manner similar to provided output
    * output  formatted,  where applicable,  must match  that of  project requirements
  * Processing must be correct based on input given and output requested
  * Output, if applicable, must be correct based on values input
  * Code must be nicely and consistently indented
  * Code must be consistently written, to strive for readability from having a consistent style throughout
  * Code must be commented
    * Any "to be implemented" comments **MUST** be removed
      * these   "to  be  implemented"   comments,  if  still  present  at evaluation time, will result in points being deducted.
      * Sufficient  comments  explaining  the point  of  provided   logic **MUST** be present
  * No global variables (without instructor approval), no goto statements, no calling of main()!
  * Track/version the source code in your lab46 semester repository
  * Submit  a copy of  your source code to  me using the  **submit** tool (**make submit** on lab46 will do this) by the deadline.

====Submit Tool Usage====
Let's  say you  have completed  work  on the  project, and  are ready  to
submit, you  would do the following  (assuming you have a  program called
uom0.c):

<cli>
lab46:~/src/SEMESTER/DESIG/PROJECT$ make submit
</cli>

You should get some sort of confirmation indicating successful submission
if all went according to plan. If  not, check for typos and or locational
mismatches.

=====RUBRIC=====
I'll be evaluating the project based on the following criteria:

<code>
117:ptb1:final tally of results (117/117)
*:ptb1:used grabit to obtain project by the Sunday prior to duedate [13/13]
*:ptb1:clean compile, no compiler messages [13/13]
*:ptb1:each button hooked to unique GPIOs [26/26]
*:ptb1:button state is read, on press code adjusts count [26/26]
*:ptb1:binary value of the count correctly displayed on LED bar [13/13]
*:ptb1:LED display logic optimized with a loop containing one if [13/13]
*:ptb1:code tracked in lab46 semester repo [13/13]
</code>

===Pertaining to the collaborative authoring of project documentation===

  * each class member is to participate in the contribution of relevant information and formatting of the documentation
    * minimal member contributions consist of:
      * near the class average edits (a value of at least four productive edits)
      * near the average class content change average (a value of at least 256 bytes (absolute value of data content change))
      * near the class content contribution average (a value of at least 1kiB)
      * no adding in one commit then later removing in its entirety for the sake of satisfying edit requirements
    * adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
    * content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
      * no contributions, co-efficient is 0.50
      * less than minimum contributions is 0.75
      * met minimum contribution threshold is 1.00

===Additionally===

  * Solutions not abiding  by spirit of project will be  subject to a 50% overall deduction
  * Solutions  not  utilizing descriptive  why and  how comments  will be subject to a 25% overall deduction
  * Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
  * Solutions not organized and easy to  read (assume a terminal at least 90 characters wide, 40 characters tall)  are subject to a 25% overall deduction
Lab46 Wiki

User Tools

Site Tools

Page Tools
