52 Weeks of Pi
I read about Shekhar Gulati's "52 technologies in 2016" idea, where he's learning something new and posting it to GitHub every week. You can see what he's up to here.
Inspired by his goal, I've decided to set my own goal of 52 Pi projects over the next year, since I've been trying to get more familiar with it. That doesn't mean they'll be big or anything... I'm going for consistent learning more than anything else.
I intend to write up instructions for each of these, along with helpful diagrams, extra resources, etc. If you're looking for more resources, check out my other repo: 314 (or so) Awesome Raspberry Pi Resources
Transmit Morse Code Via LED: A Python script for translating input (via the keyboard) into morse code, and transmitting it via on-off LED blinks (or anything else you connect to a GPIO pin).
Send Morse Code Via Button Click: A Python script for accepting incoming signals (via a button on the bread board that "closes" the circuit), and translating the input into morse code.
Blink LED When New Email Arrives: Authenticates to your Gmail account, then polls your unread message account via their API every xx seconds. When unread mail arrives, an LED blinks. When you mark it read, the LED turns off.
Simon Clone: A clone of the Simon pattern-matching game from the 80's.
RGB / LED Experiment: Experimenting with an RGB LED, getting it to randomly cycle through different color combinations. Also uses software PWM (pulse-width modulation) to make the cycling smooth.
Candle Simulation Using an RGB LED and PWM: Simulating a flickering candle that dies down and then brightens up again, using PWM (pulse-width-modulation) and an RGB LED.
Using an Analog Joystick to Display Colors on an RGB LED: Used an MCP3008 analog-to-digital converter to connect a joystick to the Pi. Using it to select the colors of an RGB color wheel and display the color on an RGB LED.
What is Charlieplexing?: Demo of "charlieplexing", or arranging LEDs in such a way as to minimize the number of GPIO pins required to make them light up.
The "mock" GPIOmock.py script allows for development on a machine that is not the Raspberry Pi, and thus doesn't have the RPi.GPIO package installed. It just outputs a message to the console that indicates its usage. I created it by referencing the comments available in the source/py_gpio.c file in the RPi.GPIO module, also available on GitHub.
Copy the file into the same directory as any of the above scripts, then comment out the
import RPi.GPIO line:
# import RPi.GPIO as GPIO
And add this line after it:
import GPIOmock as GPIO
Issues? Errors? Comments?
If you notice a typo or something that's blatantly wrong, I'd appreciate pull requests with fixes. I don't know much about the Pi yet, and the last thing I want to do is steer someone wrong...
Alternatively, feel free to post an issue if you want to bring something in here to my attention. Thanks!