2017-01-16 (M) Tough Pi-ano

A simple wiring diagram was sketched to show the connections between each position on the Raspberry Pie's GPIO and the corresponding piano key. Since the wiring was done on the underside of the board, which interfaces with the top of the Pie, all the connections looked just like the online diagrams of the GPIO.

Wiring diagram

Wires were run between the thumbwheel and GPIO pins. These were neatly terminated. Long wires were attached to the GPIO pins but left long since the distance to the keyboard buttons wasn't known.

Wires on underside of PiAno octave module

Wires were neatly bundled to keep them clear of the Pie when it gets connected to the board. Bundling also made the project look neater and also helped keep wires from twisting.

Wires on the other underside of PiAno octave module

To make it possible to run the correct wires to each keyboard button, wire colors were added to the diagram. In industrial engineering anyway, this is done with wire numbers on both ends of the wire.

Colors for each key in that octave

Everything was connected and the PiAno was allowed to boot. While holding the bundle of wires and computer cables there was only a wild cacophony of seemingly random piano notes. At first, it seemed as though all the switches were triggering simultaneously, which would suggest that the program was set to read logic LOW when it should have been looking for logic HIGH. When the project was set down but still operational, it silenced itself immediately.

When the breadboard prototype was built it only had short wires but this model had untrimmed wires nearly 1ft (30cm) long. Each of them acted as an antenna and was considered "floating." When my body was close enough to interfere with the floating signal it caused any nearby wire to go high enough to trigger. A video was shot to demonstrate the possibilities of using floating wires as a feature.

Pull-down resistors will have to be added.

Video demonstration of "floating" signal wires


The rest of the posts for this project have been arranged by date.

First time here?

Completed projects from year 1.
Completed projects from year 2.
Completed projects from year 3.

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information in this blog, or linked by this blog, are not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on a post.

This blog, including pictures and text, is copyright to Brian McEvoy.

2016-12-29 (Th)