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

Message

Re: [PolySix] Some advice please....

2002-06-11 by The Old Crow

On Tue, 11 Jun 2002, Tony Allgood wrote:

> I hope he's a good friend. The battery replacement can be a long job.
> Typically towards a day to do it properly, but it very much depends on
> the damage. I have seen four now, and all took between four to eight
> hours.

  I am working on a KLM-367 now that so far has over 20 hours of work 
done.  It is _the_ worst case I have ever seen.  Even so, I think it can 
be revived.  I really need to get to making a new PCB layout to replace 
these basket cases...

> The rest of the parts are all available from various sources, although
> finding a replacement u-proc would be difficult, although Crow was
> having a bash at doing one. Any luck with that one Scott?

  The EPROM version of the processor, an 8748(H), is still available,
though of course it has no program loaded to make it the "KLM-367 CPU". I
have the code file for the KLM-366 key assigner CPU (use an 8749(H)) which
is also the exact same program for the Mono/Poly key assigner.  Attach a
switch for unison/share on a Polysix and you can get that mode--only for 4
of the voices, however.  I also have the code file for the KLM-367 patch
manager CPU, which is also the same code for the KLM-380 (Trident Mark II) 
patch manager CPU.  I keep forgetting to copy the files over to my web 
server as they are on an un-networked workbench PC, but I'll remember 
eventually. :)

  Programming an 8748 or 8749 is no big deal, provided one has a device 
programmer that can handle these.  The 8749 can be used in place of an 
8748 on the KLM-367, incidentally.  The only difference is the '49 has 
twice the  memory of the '48.  All other functions are the same.

Crow
/**/

Attachments

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.