>
YAMAHA
STRINGS
SS-30
RACK-MOUNTED WITH MIDI
MIDI STRINGS

Friday, October 17, 2014

G Board Restoration

Here are the SS30's main PCBs.

It's about 50% wires!

G boards on the left, K, boards at the back and the rest in the middle. During the hiatus I'd cut out a piece of MDF to fit everything to.

I'd checked the power was okay so I decided to start with G boards and see if the oscillator and tone generator ICs were all working. It's a good place to start as all the sound originates there so anything else would be hard to test until they were verified. Also a faulty tone generator chip might be difficult to replace. Yamaha said they had spares when I got the service manual from them way back when, but would they still have these chips? I;d need to find out early on.

I took everything out of the case to gain access.
Don't worry, I've got a wiring guide.
I prodded the scope probes around the G2 board, which is the top most of the stack, and straight-away found that there was a problem. Only one of the tone generator chips was outputting anything. The other IC had no input clock. I wasn't surprised, a quick look around the G boards and I could see several wires that had worked loose at some point.

-26V and -9V supply rails broken on G4
 These wires were all easily fixed, although I did have to check a few more than once on the schematic and wiring diagrams. One group of wires in particular seemed to be linked in a circular fashion. I'm not even sure what they do - something to do with suppressing noise I guessed - so I decided to move on and come back to that mystery later.

I checked the traces again and was disappointed to find that there was still no output on the tone generator ICs. Now I was worried. Damaged ICs would slow things down and a potentially be expensive. However, I've spent enough time fixing electronics to know that you need to be careful not to just swap out an expensive IC because it's appears faulty.

By the way, the SH-101 I'm also fixing does seem to have a broken oscillator chip, but I double checked everything around before condemning it. When I get the replacement I'll still be nervous until it's in and working though.

I went all round the circuit and traced the problem back to the oscillator on the G3 board. There are two identical oscillators built from discrete components, one on G3 and one on G4. This is great as I could A/B compare them to see where the problem started. The first problem I had was using my scope! I was comparing two wave forms and getting one at the right the frequency (around 500KHz) and the other was... well it seemed to be beyond the range of the scope! It was already late, so I went to bed.

Spot the mistake? (the chocolate wrapper is not a clue)
The next evening I started again and got the same problem. This time I went through and systematically worked out that the scope was not showing me the right trace if both signals were connected. I'd got the trigger set-up incorrectly. In the picture above you can see that only channel A is being used as a trigger source. The oscillators are not synced so triggering one from the other gives the problem you can see in the photo.
Once I triggered each input off it's own signal I got two comparable traces. The night before I'd quickly ascertained that the signal from the G3 oscillator was DC shifted negatively by several volts. Having excluded any other issues I was sure this was the problem. It's supposed to be between 0 and -15V, so what was causing this anomaly?

G3 Oscillator being negative.


I eventually disconnected a cable - which I'd just reconnected - that feeds the clock from G3 to G4. Now the signal was biased correctly. So, it was something on the G4 board.

There's something
 When I was fixing that cable I'd noticed this capacitor on the underside of the G4 PCB. It was obviously a modification and didn't appear on the schematic. It also wasn't present in the same position on the G3 board (where the G4 clock enters that board). So, I took it off. Now everything worked perfectly. This cap was clearly an afterthought. It was pulling the signal too low and served no apparent purpose. I suspect that once everything is running I may find out what it was for, but that bridge can be crossed if I get to it.

Test Points 1 and 2 (A and B triggering!)
So, I could now see clean, strong signals from both of the first two test points on the schematic, indicating all was well with the oscillators.

The next job would be to reconnect the wires from K1 and K2 to G1 and G2.





No comments :