2017-01-15 (Su) Tough Pi-ano

Each octave in the PiAno was meant to be replaceable so the programming has been done. Since this project will not likely be reproduced there's little point in optimizing this now. Ideally, there would be a better way to get the 48 key inputs to a Pi where it could play a note based on the input but the Pi Zeros were inexpensive so it seemed simplest to go this route and it shows the value of a modular based system which could be changed later to include a replaceable octave option.

Header pins were soldered to the Pi Zero in the same way they would appear on a full-featured Pi board. This does not ensure compatibility but it would be possible to alter the software, maybe not even necessary, to work with a full Pi board.

Header pins and header sockets soldered in place

The circuit board of a thumb-wheel switch was trimmed to remove unnecessary laminate which was obstructing how it would fit on the board. Unfortunately, this destroyed the razor saw blade.

Razor saw for cutting the excess plastic from a thumb-wheel board

After destroying  a saw blade, the header pins selected to go into the thumb-wheel switch wouldn't fit. Spacing on the switch was not the same pitch as the header pins, 0.1" (2.54mm). Instead of a simple job soldering header pins, short lengths of wire were cut, stripped, and tinned.

Short wires soldered to a thumb-wheel switch

All the parts were assembled to the board. This was only the first step in one octave module. Connections to the switches will have to be installed and connections to the thumb-wheel switch will have to be made. This was simply to mount the components. After one module is correctly wired, it will have to be copied three more times but the subsequent copies won't require figuring out the pattern.

Computer module for a PiAno octave

Downloads


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-27 (Tu)

Comments