Discussion about the Korg PolySix synthesizer group photo

Yahoo Groups archive

Discussion about the Korg PolySix synthesizer

Index last updated: 2026-03-31 14:03 UTC

Thread

Memory Problem

Memory Problem

2003-09-15 by petercaja

Hi Everybody!

I have a problem with my PolySix regarding saving patches.
There are already some presets in SRAM, but i'm unable to overwrite
it. I checked KLM-367 board and it seems that WriteEnable signal,
from IC22, Pin 10 never goes to 0, to enable writing to SRAM
i doble checked it with Mutimeter and Logic Analyzer.
Since SRAM acctualy holds presets, i doubt this chip (IC32) is bad.

When i press Write the LED blinks, and when i choose program to write
to - LED stops blinking, as it should, but the program is not
overwritten.

There was a battery leakage, but previous owner fixed it.
I also checked those fixed connections and everything seems to be ok.

It seems that everything else is working OK.

Any suggestions are welcome!

Thank you and best regards,
Peter

Re: [PolySix] Memory Problem

2003-09-16 by greg montalbano

Hi-
you don't mention if you've checked the front panel "write enable" switch --
if the switch is physically bad (or needs to be cleaned), or if the signals
from that switch (P12 & D07?) are being shorted or otherwise compromised
(possibly by the battery-leak damage), it could result in what you've observed.

~G


At 11:07 PM 9/15/03 +0000, you wrote:
>Hi Everybody!
>
>I have a problem with my PolySix regarding saving patches.
>There are already some presets in SRAM, but i'm unable to overwrite
>it. I checked KLM-367 board and it seems that WriteEnable signal,
>from IC22, Pin 10 never goes to 0, to enable writing to SRAM
>i doble checked it with Mutimeter and Logic Analyzer.
>Since SRAM acctualy holds presets, i doubt this chip (IC32) is bad.
>
>When i press Write the LED blinks, and when i choose program to write
>to - LED stops blinking, as it should, but the program is not
>overwritten.
>
>There was a battery leakage, but previous owner fixed it.
>I also checked those fixed connections and everything seems to be ok.
>
>It seems that everything else is working OK.
>
>Any suggestions are welcome!
>
>Thank you and best regards,
>Peter
>
>
>
>Yahoo! Groups Sponsor
>ADVERTISEMENT
>
>To unsubscribe from this group, send an email to:
>PolySix-unsubscribe@yahoogroups.com
>
>PolySix "Digiest" Page:
><http://www.acc.umu.se/~amber/Poly6>http://www.acc.umu.se/~amber/Poly6
>
>Your use of Yahoo! Groups is subject to the
><http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.


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

Re: [PolySix] Memory Problem

2003-09-16 by The Old Crow

If IC22 pin 10 to IC32 pin 10 tests OK for continuity, and either of
these tests OK to pin 8 of IC25, then either that trace is being held high
by a short, IC25 has failed in such a way to pull the signal high, or
IC22's !WR signal is possibly dead.

Crow
/**/

On Mon, 15 Sep 2003, petercaja wrote:

> Hi Everybody!
>
> I have a problem with my PolySix regarding saving patches.
> There are already some presets in SRAM, but i'm unable to overwrite
> it. I checked KLM-367 board and it seems that WriteEnable signal,
> from IC22, Pin 10 never goes to 0, to enable writing to SRAM
> i doble checked it with Mutimeter and Logic Analyzer.
> Since SRAM acctualy holds presets, i doubt this chip (IC32) is bad.
>
> When i press Write the LED blinks, and when i choose program to write
> to - LED stops blinking, as it should, but the program is not
> overwritten.
>
> There was a battery leakage, but previous owner fixed it.
> I also checked those fixed connections and everything seems to be ok.
>
> It seems that everything else is working OK.
>
> Any suggestions are welcome!
>
> Thank you and best regards,
> Peter

Re: [PolySix] Memory Problem

2003-09-16 by The Old Crow

Oh, Greg has a point; if the write enable is not actually getting
through, then it won't write anyhting.

/**/

Re: Memory Problem

2003-09-16 by petercaja

Guys, thank you for replays!

After spending a little more time with PolySix, i discovered one more
broken trace, caused by battery leakage, i found out that i can
acctually copy preset from let's say A2 to A1, so write is working,
however, i can't write from MANUAL mode.
If i set a patch in manual mode and then write it, the preset is
overwritten, but not with the patch it should but with - something.
I also found out that if i make drastic changes to the sound and
rewrite the patch, there is a difference, but it's far from the sound
from MANUAL mode :-)

Could it be a DAC problem?
Another thing that i'm not sure about is Reset Circuit calibration.
According to the manuals, BANK A-D, MANUAL, TAPE ENABLE and PROGRAM 1-
8 leds should be lit, what about HOLD, CHORD MEMORY, UNISON and POLY?
If i set VR1, sometimes POLY led goes out and UNISON led become lit,
sometimes all four leds are lit (during the calibration process).

So, to be short: I can COPY preset from one place to other, but if i
write from MANUAL mode, the values stored are different from those
set by pots :-)

Best regards,
Peter

--- In PolySix@yahoogroups.com, The Old Crow <oldcrow@o...> wrote:
>
> Oh, Greg has a point; if the write enable is not actually getting
> through, then it won't write anyhting.
>
> /**/

Re: [PolySix] Re: Memory Problem

2003-09-17 by Johannes Hausensteiner

This is not an unusual pattern: your polysix
suffers from battery leakage, you repair it,
but some functions do not work. If you
investigate, you find that even more pcb traces
were affected by the battery acid. It is very
important to clean the pcb thouroughly. I use
alcohol for this purpose. Only when you are
really sure that all acid is gone start building
up the pcb. Additionally I route wires on traces
that are still intact now but have this ugly
dark look. You can expect them to fail within
a short time. The acid crawls under the solder
mask along the traces and is still there.
---
So I wish you the best in finding ALL affected
traces and lines.
It certainly is not a DAC problem when you can
here your other patches (from memory) normally.
It couls be a problem of the analog multiplexers
found on KLM-369, KLM-370. You can check this
easliy: put a scope to IC27/pin1. The schematic
says that there is a test point but I cannot
find it on the PCB drawing. Trigger the scope
with the signal from test point "Clock" near
IC22. You can se now the multiplexed analog
control voltages as output by the DAC. Now
move the probe to CN11-pin2 (this is called
"data" in the schematics). Here you can see
the multiplexed CVs as they come from the
control panel. In MANUAL mode the individual
CVs' levels must be the same. The signal will
look different timing-wise as the DAC also
"converts" all other data bus activity.

Good luck,

Johannes


--- petercaja <pero@radiocity.si> wrote:
> Guys, thank you for replays!
>
> After spending a little more time with PolySix, i
> discovered one more
> broken trace, caused by battery leakage, i found out
> that i can
> acctually copy preset from let's say A2 to A1, so
> write is working,
> however, i can't write from MANUAL mode.
> If i set a patch in manual mode and then write it,
> the preset is
> overwritten, but not with the patch it should but
> with - something.
> I also found out that if i make drastic changes to
> the sound and
> rewrite the patch, there is a difference, but it's
> far from the sound
> from MANUAL mode :-)
>
> Could it be a DAC problem?
> Another thing that i'm not sure about is Reset
> Circuit calibration.
> According to the manuals, BANK A-D, MANUAL, TAPE
> ENABLE and PROGRAM 1-
> 8 leds should be lit, what about HOLD, CHORD MEMORY,
> UNISON and POLY?
> If i set VR1, sometimes POLY led goes out and UNISON
> led become lit,
> sometimes all four leds are lit (during the
> calibration process).
>
> So, to be short: I can COPY preset from one place to
> other, but if i
> write from MANUAL mode, the values stored are
> different from those
> set by pots :-)
>
> Best regards,
> Peter
>
> --- In PolySix@yahoogroups.com, The Old Crow
> <oldcrow@o...> wrote:
> >
> > Oh, Greg has a point; if the write enable is not
> actually getting
> > through, then it won't write anyhting.
> >
> > /**/
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> PolySix-unsubscribe@yahoogroups.com
>
> PolySix "Digiest" Page:
> http://www.acc.umu.se/~amber/Poly6
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Patch manager V1.4

2003-09-24 by Johannes Hausensteiner

Hi all!

I uploaded the latest version (1.4) of the patch
manager to:
http://groups.yahoo.com/group/PolySix/files/P6PATCH.ZIP

New features:
* printing is in correct scale regardless of
printer resolution
* a file name is accepted as command line parameter
(this enables opening *.P6 files from explorer with
doubleclick or drag-and-drop)
* CTRL P hotkey in patch preview window

Note that it is important when recording patches
from the Polysix that there is no gap at the
beginning of the recording; i.e. press first the
"TO TAPE" button on the Polysix and then the "OK"
button in the "Record" Message box.


Have fun!

Johannes



__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com