Yamaha CS80

I originally reported a problem w. my CS80 in that the top octave of keys wasn't triggering any sound. I had some good suggestions from various techs and I verified that the actual keybed was sending the correct voltages from all keys.

The testing and debugging centered around the KAS board. After carefully measuring the values for various keypresses up and down the keyboard, I came to the conclusion that the YM26600 was creating and assigning the right codes, but the YM26700 IC was not working properly.

Thanks to the kindness of a listmember, I popped in a replacement YM26700 and now I have the full range of keys again.

I wonder if this is similar to when the notes above F5 don't go up when I try to bend them up with the pitch bend ribbon?
Tommy

--- On Wed, 3/18/09, tmoravan <moravanskyt@...> wrote:


From: tmoravan <moravanskyt@...>
Subject: [yamahacs80] CS-80 key trigger problem and the fix
To: yamahacs80@yahoogroups.com
Date: Wednesday, March 18, 2009, 12:17 PM






I originally reported a problem w. my CS80 in that the top octave of keys wasn't triggering any sound. I had some good suggestions from various techs and I verified that the actual keybed was sending the correct voltages from all keys.

The testing and debugging centered around the KAS board. After carefully measuring the values for various keypresses up and down the keyboard, I came to the conclusion that the YM26600 was creating and assigning the right codes, but the YM26700 IC was not working properly.

Thanks to the kindness of a listmember, I popped in a replacement YM26700 and now I have the full range of keys again.



















[Non-text portions of this message have been removed]

I think that I might have the same problem. My keybed acts funny from the top key down to the C#. It will trigger, somewhat strange noises, if I have another key pressed in a lower octave. Is this the same problem? How did you troubleshoot it and fix it?

-Mike

--- In yamahacs80@yahoogroups.com, "tmoravan" <moravanskyt@...> wrote:
>
> I originally reported a problem w. my CS80 in that the top octave of keys wasn't triggering any sound. I had some good suggestions from various techs and I verified that the actual keybed was sending the correct voltages from all keys.
>
> The testing and debugging centered around the KAS board. After carefully measuring the values for various keypresses up and down the keyboard, I came to the conclusion that the YM26600 was creating and assigning the right codes, but the YM26700 IC was not working properly.
>
> Thanks to the kindness of a listmember, I popped in a replacement YM26700 and now I have the full range of keys again.
>

http://vimeo.com/11816465

17 minutes of improv


[Non-text portions of this message have been removed]

--- In yamahacs80@yahoogroups.com, "mborish_2000" <mborish_2000@...> wrote:

>
> I think that I might have the same problem. My keybed acts funny from the top key down to the C#. It will trigger, somewhat strange noises, if I have another key pressed in a lower octave. Is this the same problem? How did you troubleshoot it and fix it?
>

Have you verified it is not a problem with a particular voice card? If the problem isn't in the voice card, take a look at the KAS schematic (either the separate one or the full sheet layout). You can see how the keyboard data is sent into the YM26600 and then to the 26700.

What I do is verify that known good data lines are working and see the values and then compare to the problem lines. Monitor a particular note (like C) and press each C key in the octaves and watch the voltage change. If there is a problem in the keyboard itself, you'll see bad data coming in for the top octave. Probably it will be good though.

Next take a look at the N and B lines and verify that the are carrying the correct encoding for each key press. Finally, take a look at the CH 1->8 outputs on the 26700 and verify each channel is putting out the expected voltages.

Take notes along the way and the voltages seen so you have a reference if you ever have to go back.

If the D/A is really bad, you'll see consistently bad data coming from the channel outputs. Sorry I can't be more specific, but that's kind of the nature of debugging - probe around, take measurements, make 1 change at a time, break the circuit down, and repeat until the problem is isolated.

Because the CS-80 often strings connections through multiple boards, sometimes a problem downstream manifests itself earlier in the chain and you only discover it when you unsolder the connection and isolate one board at a time.