Fixing the pedal effect Zoom 707 II Guitar

If you have a pedal effect Zoom 707 II for Guitar and it makes some cracking noises, probably sooner or later will stop working, as it happened to me. This is an old pedal effect I have since 2003, I remember I paid for it about 270 €. I used it a lot, and apparently because it was always on the floor and sometimes when people walked over it, kicked or stepped on the cables, this jack connectors eventually got damaged.

So I decided to open it and see if I could fix it.

The first thing you have to do is to remove the three potenciometers, right under the brand, pull them off gently.

Then flip the pedal, and start unscrewing. When you are done, be careful when you open it, because there is a cable connecting the cover to the Wah pedal, you can just disconnect it pulling it off.

So here it is, the internal circuit board, after 11 years it doesn't have so much dust.

As you can see there two jack connectors. Mine had the input connector damaged

As you can see in the center of the image below, on the right hand side of the spring, there are 3 weldings, these are, +, - and ground.

When I connected the Jack, and swinged it a bit it, I could see that one of the welding was moving, this avoid the signal to go through.

So I took my soldering machine and I just drop a bit of solder wire on it, and done, I have pedal effect for 10 more years

Modules updated

Re-designing the code

Finally I've got some time to update the files to github. The after having a break for a couple of months I realized that my first approach was wrong, the classes were dependent, therefore I redesigned each of the for having independence among them.

Some tests need to are bounded to several classes, e.g. the most of the class need the class LCD to show the behavior or result of the tests.

When I re-designed the classes I had also to rename some of them. At the time of updating this to github I encountered with a problem. I had removed or rename the files on my local computer so when I did commit and push them to the server, the server kept the old files and the new. There was no way to remove them. Was then when I found the following command that helped me to remove the old files from the server, and update everything as it was on my local computer:

git add . -A
git commit -m "removed some files"
git push origin master

This is the list of new classes:

DHT11
Sensor of temperature and humidity. I took the code from http://arduino.cc/playground/Main/DHT11Lib in which I did some minor changes.

Keypad
Now this class only controls the keypad and does not include the LCD, Even though are both in the same board. I believe this way is more clear for use it, and the code is grouped by functionality and cleaner.

LCD
This class only writes on the display, nothing else. Actually is the wrapping of the LiquidCrystal class where I merged a couple of function to make the writing easier.

LEDRGB
This class remains almost the same, what before was test now is function of the class. So the test only calls the functions.

MenuController
This class controls the index of the menu but is not a menu itself. does not contain titles/text. That will be performed by the class Menu in the future.

Relay4
Represents the board Channel Relays. It offers the basic functions for controlling the relays.

Test samples.
Now the tests are clearer, shorter and easier to run.

What is next.

I'm thinking about a good way to generate a Menu dynamically and reusable, with a main index and each item containing options, any suggestions?