Discussion about the Korg PolySix synthesizer group photo

Yahoo Groups archive

Discussion about the Korg PolySix synthesizer

Index last updated: 2026-04-28 23:40 UTC

Thread

polysix -- What does IC 31 on KLM-367 do?

polysix -- What does IC 31 on KLM-367 do?

2007-11-09 by spistrich

does anyone know what IC 31... on board klm-367  does?  it would be the 
first chip to be damaged from the acid leak....it is a 74LS08 type 
chip. readily available from Digikey, but I really would like to know 
what functions it controls. this info might help explain my polysix's 
odd behavior after battery leakage rather than just blaming the traces.

Re: [PolySix] polysix -- What does IC 31 on KLM-367 do?

2007-11-09 by Chromatest J. Pantsmaker

It's probably the traces... unless the corrosion has leached into that
chip.  Personally, I've not seen anything "break" inside a P6 other
than the corrosion and normal wear and tear.

Sorry I can't help answer your actual question though.

On 11/9/07, spistrich <wasteking@verizon.net> wrote:
> does anyone know what IC 31... on board klm-367  does?  it would be the
> first chip to be damaged from the acid leak....it is a 74LS08 type
> chip. readily available from Digikey, but I really would like to know
> what functions it controls. this info might help explain my polysix's
> odd behavior after battery leakage rather than just blaming the traces.
>
>
>
> PolySix "Digiest" Page: http://www.acc.umu.se/~amber/Poly6
> Yahoo! Groups Links
>
>
>
>


-- 
.sig
-Chromatest J. Pantsmaker
http://www.chromatest.net

Re: [PolySix] polysix -- What does IC 31 on KLM-367 do?

2007-11-09 by klosmon

At 10:55 AM 11/9/2007, you wrote:

>does anyone know what IC 31... on board klm-367 does? it would be the
>first chip to be damaged from the acid leak....it is a 74LS08 type
>chip. readily available from Digikey, but I really would like to know
>what functions it controls. this info might help explain my polysix's
>odd behavior after battery leakage rather than just blaming the traces.

Look at the schematic (and by the way, it's pretty much impossible to 
achieve any successful repairs on the P6 without referring to the 
schematics) -- ICs 31 & 30 are quad AND gates, basically serving to 
buffer the eight data lines between the CPU chip and the rest of the 
circuitry.  Each of these lines is crucial to the correct performance 
of the synth; if any one is missing or shorted, it can cause any 
number of malfunctions of the front panel, memory, patch control voltages, etc.
Also note that each data line connects to numerous points on the 
board;  even if most of them are good, having only one missing can 
still cause havoc.

The easiest way to observe all this is with a scope;  referring to 
the schematic, view each line starting at the CPU & continuing to the 
IC30 (or 31) input, then from the IC30 or 31 output to the other 
indicated points.  Any bad or missing signal should be immediately obvious.
Note that the 4042 latch "IC34" on  the schematics is labelled 
incorrectly;  it should be IC24.

The lengthier process is to use your meter in continuity mode (this, 
of course, is done with the power off);  check for proper  continuity 
for each data and address line (for example, pin 12 of the CPU should 
connect to pin 4 of IC 31 and to pin 14 of the RAM chip;  pin 6 of IC 
31 should connect to IC26 pin 13, to connector CN06 pin 3, IC28 pin 
4, etc etc etc).

It sometimes happens that IC31 (or one of the other CMOS chips in the 
battery leak area) is indeed dead;  but the most frequent cause of 
nonfunction is a bad circuit trace.

~GMM
(repairing battery-damaged PolySixes for longer than I'd care to think about)


>
>
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.503 / Virus Database: 269.15.26/1119 - Release Date: 
>11/8/2007 5:55 PM

  ----------



No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.15.26/1119 - Release Date: 11/8/2007 5:55 PM


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

Re: polysix -- What does IC 31 on KLM-367 do?

2007-11-09 by spistrich

--- In PolySix@yahoogroups.com, "Chromatest J. Pantsmaker" 
<chromatest@...> wrote:
>
> It's probably the traces... unless the corrosion has leached into 
that
> chip.  Personally, I've not seen anything "break" inside a P6 other
> than the corrosion and normal wear and tear.
> 
> Sorry I can't help answer your actual question though.
> 
> On 11/9/07, spistrich <wasteking@...> wrote:
> > does anyone know what IC 31... on board klm-367  does?  it would 
be the
> > first chip to be damaged from the acid leak....it is a 74LS08 type
> > chip. readily available from Digikey, but I really would like to 
know
> > what functions it controls. this info might help explain my 
polysix's
> > odd behavior after battery leakage rather than just blaming the 
traces.
> >
> >
> >
> > PolySix "Digiest" Page: http://www.acc.umu.se/~amber/Poly6
> > Yahoo! Groups Links
> >
> >
> >
> >
> 
> 
> -- 
> .sig
> -Chromatest J. Pantsmaker
> http://www.chromatest.net
>
`well, the reason im wondering about IC 31 is that in the repair 
exaple shown on the Old Crow synth repair site...he said he had to 
replace the IC 31 in addition to trace repair, but didnt describe 
what the problem with the chip was.....i can understand how corroded 
traces could loose continuity...a couple did on my polysix, but the 
odd behavior i see is almost like 'too much' continuity-- things that 
dont turn off.  this could be explained by conductive acid getting 
into the IC... Because i cant see a problem with the traces now, and 
continuities are fine. The replacement 74LS08 chip is cheap ...and i 
would have to pull the old one to check/repair the traces under it. I 
just wonder what the IC 31 does? does it control track selection 
and/or memory  to tape download ? 

(p.s. i have had to replace voice chips on a dead voice...but the 
LED's in each voice channel made diagnosing  that easy.)

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.