Monthly Archives: January 2013
Oh, the Korg Polysix. A wonderful piece of vintage awesomeness, except for the unfortunate tendency for the on-board battery to self-destruct, taking the programmer board with it. I’ve done several of these in the past; this was by far the most challenging to work on.
This unit was not unusual in that the battery had indeed leaked, and I could immediately see several components were damaged. It was unusual in that not only did it have MIDI, it had an original Korg MIDI retrofit installed from the factory. I honestly didn’t know that Korg even made an interface for this. I also had no idea how difficult it was going to make the repair.
The first hint came in trying to access the KLM-367 programmer. The retrofit sits on top. Two of the larger CMOS chips that are normally on the programmer are instead installed on the retrofit, with ribbon cables leading back the the original sockets. There are also hard-wired (soldered) connections to the front panel controls, the key assigner, and the voice board. I pulled the ribbon cables, but had to leave everything else connected.
When I first looked at it while the customer was present, the damage didn’t look too bad. With the board out of the unit, though, it was as bad any I’ve seen previously. One of the quad logic chips and one electrolytic capacitor were completely shot. The cap would be removed for the battery modification, but the chip had to be replaced. In addition, many of the traces were bad.
These repairs are not normally difficult, just time-consuming. I removed the old battery and the damaged components, then cleaned the board. Using the component diagram from the service manual, I marked the traces that would need to be repaired. For the new battery, in addition to removing the capacitor there’s a resistor that has to be replaced with a diode. I also installed a socket for the new logic chip. Once all that was in place, it was time to start adding the wires to bypass all the bad traces.
Double-checked everything, installed the new components, put everything back together, hit the power, and…success! Sort of.
The programmer seemed to be working. Kind of. The synth section, though, was not. There were several dead keys. Some of the controls worked and some didn’t. I could create a patch and it would store, but they all sounded horrible. Powered it off, pulled the board, and went over it again. I found one wire that wasn’t soldered correctly, and also noticed that the metal mount for the retrofit was shorting a couple of resistors. A quick dab of solder, a minor change of position, and after I pulled the keyboard and took care of the bad keys it seemed to be working – almost.
This time, the synth section was perfect and it sounded fantastic. The arpeggiator didn’t work, though, and while I could still store patches the behavior of the programming section seemed odd. Realizing that the retrofit might be causing an issue, I tried to locate documentation. A web search turned up a user’s manual, but no schematics. At least I was able to disable the external sync for the arpeggiator, so now the whole synth side worked as it should.
Ignoring the odd behavior, I tried reloading the factory patches from known-good WAV files. No dice. They’d partially load, but then I’d get an error. I ended up entering the missing patches manually. I also verified that not only does the MIDI interface work, but the additional patch storage locations are accessible.
In the end, the customer picked up the unit and was extremely happy, even with the quirky issue saving patches. It doesn’t affect playability at all, or patch selection. I told him that if I can locate the service information for the retrofit, he can bring it back.
And of course the other positive note is that after this one I’ll never be afraid of doing a Polysix battery repair again.