Here is a test using Hippy's code.
Moving the stick doesn't seem to make any difference.
Correction, snapping the stick gave some low readings.
Also experimented with moving the output lead to the x and y axes. Numbers change but don't correlate with the hammer strikes.
I see no obvious problem with your wiring or setup. In the post above, I see one spot where the numbers drop from the 900s to 267. Does that correspond to a strike? You are looking for numbers significantly lower than the baseline. I don't know why your baseline is 900-something when mine was 480-640.
Did you have a resistor in series with the input pin?
Another thought, does that C.1 pin need those two resisters installed as we did for the hammer inputs?
Perhaps we are getting a floating pin readout?
Finally got the LED matrix repaired. bad ground. i didn't do myself any favors when we used solid bell wire to wire the array.
The code ibenson wrote is operating perfectly.
(Still have not done anything with the latest code that includes the LCD screen.)
Question, where do we write the "wait for the hammer" command?
we changed the note speed from 8 to 15 but in the terminal window it still says 8.
At the beginning of the program, make sure bLEDFlag is set to 1 so you go to preprocess and turn the LED on; make sure bPlayTune is set to 0 so the TUNE command is not executed. Then put your "wait for the hammer" code in postprocess. Any further PAUSE you want may be put here before the "wait for the hammer" code.
Within that stream there are some pretty high (1023) and low (252) numbers, so it may be a case of needing to filter or process the data to detect strikes.
That 1023 is the maximum limit of the READADC10 is interesting and suggests something perhaps isn't quite right. I am not sure however what hardware you are using nor what would be expected. 12 pages in and near 450 posts makes it rather difficult to go back to find out.
It might be worth starting a separate thread on detecting strikes and nothing else.