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] Re: Trying to Restore a P6.

2016-08-30 by Bob Grieb

An interesting idea, and one that I have actually been thinking about over the past few months
after reading posts about debugging KLM-367's.    I was considering making something 
that would plug in in place of the 8048, and allow the user to step through different tests.
I was thinking to test the LEDs first, so that they could be used to display results once they 
were working.   But so far I haven't done any actual work on this.  Just an idea.

Another idea would be to make something that would have a USB interface, and control it
from a PC, so that it could be a more general purpose 8048 circuit tester.

Bob


--------------------------------------------
On Tue, 8/30/16, tlule@gmx.de [PolySix] <PolySix@yahoogroups.com> wrote:

 Subject: [PolySix] Re: Trying to Restore a P6.
 To: PolySix@yahoogroups.com
 Date: Tuesday, August 30, 2016, 2:06 PM
 
 
  
 
 
 
   
 
 
     
       
       
       Man, what a nightmare you have there. And
 you seem to be not the only one.
 I was wondering about the following
 point. 
 It should be
 'quite easy' to set up a jig that replaces the
 programmer CPU, and-or the assigner CPU with a modern CPU.
 It just needs enough pins to look at each of the 8048 pins
 in a row.  (e.g. STM32) , plus LCD interface, or serial
 interface.
 The CPU would run a
 series of 'sanity checks'. If you made that open
 source, everybody could contribute further program parts to
 execute. some parts could ask the user to turn a pot, others
 ask for keypresses. Each part would then report for
 good-intermittent-missing-stuck or whatever contact it finds
 on that pin. 
 That would make
 troubleshooting a piece of cake compared to the hunting of
 the snark you are up to. 
 what
 do you think guys out there?
 
 
 
     
      
 
     
     
 
 
 
 #yiv5784458769 #yiv5784458769 --

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.