Discussion about the Korg PolySix synthesizer

Ben,
Greetings! 
Sorry to hear about your Polysix problems. Your problem seems a bit 
strange, but I can give you a couple of things to try. First I would 
ring out all the lines between the CPU chip, the latches, etc. on KLM-
367 and the SRAM chip on the same board. Maybe there's a faulty trace 
on that board that's causing the problem. Second, make sure that the 
backup battery is at least 2 volts when off. That SRAM chip needs at 
least that much to hold its memory correctly. My own Polysix needed 
the SRAM chip replaced because it wouldn't store anything to memory 
at all. One big thing to check is the overall traces in the area 
surrounding that new battery you put in. Most of these strange memory 
or patch-related problems are related to corroded traces from a 
previously (or currently) leaking battery. My old battery wasn't 
gushing junk on the board, but none the less had destroyed a bunch of 
traces near the memory circuits. It is definitely this 
keyboard's "Achille's heel". Please let us know any more symptoms 
that might be helpful for us to diagnose. ~JIM


> I recently got my Polysix working fairly well but I seem to have 
> developed a new problem: when trying to save a patch to a new BANK, 
> it seems to overwrite all banks for that PROGRAM number.  For eg, 
say 
> I'm using PROGRAM 8 in BANK A, then I make some changes and want to 
> save the changed sound to PROGRAM 8 in BANK B, I'm able to save 
this 
> new sound but it overwrites the orignial sound in BANK A (and all 
> other banks for PROGRAM 8.)
> 
> I recently installed a new battery, could this be the problem?  
Even 
> though it's worked fine for a few weeks?
> 
> Any ideas greatly appreciated!
> 
> Cheers,
> 
> Ben, Sydney AUS.