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 memory problem

polysix memory problem

2008-09-05 by wasteking1

my polysix has had a few 367 corrosion problems but after some rewiring 
it now has all leds and switches working ,(it used to have 5 led's on 
all the time and wouldnt switch sounds)  
    BUT NOW THE PROBLEM IS new sounds wont stay in the memory... if you 
store a sound on lets say B2  then go and store another on C3 you loose 
the first sound.  Any suggestions as to which chips, or traces  are 
involved with memory input?  could the 'memory enable' switch not be 
actually working ? any ideas?

Re: polysix memory problem

2008-09-05 by Andrew Jury

Hi,

First check the continuity for the tracks around the data bus (DB0-DB7)
connected to IC22 (CPU) and IC30/31/26/34.

However, I have had just such a problem in the past and it was 
corrected by replacing the SRAM chip IC32 which is a 1024x4bit type. 
The original TC5514APLs are a bit thin on the ground, however, you can 
use an HM6514 which is still available if you look around. Having read 
past posts it seems not uncommon for this to fail! If you are going 
change any integrated circuits I find it is best to solder in a DIP 
socket before you reconnect the new device. This will help you in the 
future with troubleshooting and it will also protect you against 
destroying the device with heat when soldering.

If you have trouble getting hold of the above chip let me know and I 
will try and point you in the right direction.

Bests,
Andy

--- In PolySix@yahoogroups.com, "wasteking1" <wasteking1@...> wrote:
>
> my polysix has had a few 367 corrosion problems but after some 
rewiring 
> it now has all leds and switches working ,(it used to have 5 led's on 
> all the time and wouldnt switch sounds)  
>     BUT NOW THE PROBLEM IS new sounds wont stay in the memory... if 
you 
> store a sound on lets say B2  then go and store another on C3 you 
loose 
Show quoted textHide quoted text
> the first sound.  Any suggestions as to which chips, or traces  are 
> involved with memory input?  could the 'memory enable' switch not be 
> actually working ? any ideas?
>

Re: polysix memory problem

2008-09-07 by radek_tymecki

It can be found here

http://www.jameco.com/webapp/wcs/stores/servlet/ProductDisplay?jameco_page=42&langId=-1&productId=43238&catalogId=10001&freeText=43238&storeId=10001&search_type=jameco&ddkey=http:StoreCatalogDrillDownView




--- In PolySix@yahoogroups.com, "Andrew Jury" <andy@...> wrote:
Show quoted textHide quoted text
>
> Hi,
> 
> First check the continuity for the tracks around the data bus (DB0-DB7)
> connected to IC22 (CPU) and IC30/31/26/34.
> 
> However, I have had just such a problem in the past and it was 
> corrected by replacing the SRAM chip IC32 which is a 1024x4bit type. 
> The original TC5514APLs are a bit thin on the ground, however, you can 
> use an HM6514 which is still available if you look around. Having read 
> past posts it seems not uncommon for this to fail! If you are going 
> change any integrated circuits I find it is best to solder in a DIP 
> socket before you reconnect the new device. This will help you in the 
> future with troubleshooting and it will also protect you against 
> destroying the device with heat when soldering.
> 
> If you have trouble getting hold of the above chip let me know and I 
> will try and point you in the right direction.
> 
> Bests,
> Andy
> 
> --- In PolySix@yahoogroups.com, "wasteking1" <wasteking1@> wrote:
> >
> > my polysix has had a few 367 corrosion problems but after some 
> rewiring 
> > it now has all leds and switches working ,(it used to have 5 led's on 
> > all the time and wouldnt switch sounds)  
> >     BUT NOW THE PROBLEM IS new sounds wont stay in the memory... if 
> you 
> > store a sound on lets say B2  then go and store another on C3 you 
> loose 
> > the first sound.  Any suggestions as to which chips, or traces  are 
> > involved with memory input?  could the 'memory enable' switch not be 
> > actually working ? any ideas?
> >
>

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.