Corning Community College
ENGR1050 C for Engineers
We continue our explorations of the electronics kit, by adding additional LEDs to control them in unison with a C program on our pi, having them count in binary.
Do note, the productive way to go about this project involves taking the following steps:
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.
After exploring, assembling, and testing the intended circuit (4 LEDs), adapt the provided C code to use the bank of connected LEDs to count in binary from 0000 to 1111 (0 to 15).
Using the current value of count, your task is to make use of if statements and bitwise logic to determine from an ongoing count the state of the individual bits.
It is your task to write a C program that interfaces successfully with four independently connected LED circuits, arranged in some orientation to ascertain an order or positioning, where your program will (in endless fashion, or until being manually interrupted) display a count (in binary) of values from 0 to 15 (then rollover, or reset).
If “1” means the LED in that position is ON, and “0” means the LED in that position is OFF, then you want to write a program that performs the following progression (over and over again):
0 0 0 0 0 0 0 1 0 0 1 0 0 0 1 1 0 1 0 0 0 1 0 1 0 1 1 0 0 1 1 1 1 0 0 0 1 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0 1 1 0 1 1 1 1 0 1 1 1 1 <-- 15, the maximum value to display 0 0 0 0 <-- 0, we "roll over" and start again 0 0 0 1 0 0 1 0 ...
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.
lab46:~/src/SEMESTER/DESIG$ grabit DESIG PROJECT
You will want to go here to edit and fill in the various sections of the document:
The general flow of the process (one way of going about it, anyway) can be described as follows:
SET COUNTER TO ZERO
REPEAT:
SHOULD THE ONE'S POSITION HAVE A ONE:
ACTIVATE THE ONE'S PLACE
OTHERWISE:
DEACTIVATE THE ONE'S PLACE
SHOULD THE TWO'S POSITION HAVE A ONE:
ACTIVATE THE TWO'S PLACE
OTHERWISE:
DEACTIVATE THE TWO'S PLACE
SHOULD THE FOUR'S POSITION HAVE A ONE:
ACTIVATE THE FOUR'S PLACE
OTHERWISE:
DEACTIVATE THE FOUR'S PLACE
SHOULD THE EIGHT'S POSITION HAVE A ONE:
ACTIVATE THE EIGHT'S PLACE
OTHERWISE:
DEACTIVATE THE EIGHT'S PLACE
PAUSE FOR HUMAN PERCEPTION
LET THE COUNTER BE INCREMENTED BY ONE
To be successful in this project, the following criteria (or their equivalent) must be met:
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):
lab46:~/src/SEMESTER/DESIG/PROJECT$ make submit
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.
I'll be evaluating the project based on the following criteria:
78:stl1:final tally of results (78/78) *:stl1:used grabit to obtain project by the Sunday prior to duedate [13/13] *:stl1:clean compile, no compiler messages [13/13] *:stl1:program conforms to project specifications [39/39] *:stl1:code tracked in lab46 semester repo [13/13]