PolySix Repairs

[Drew Smith]

        Hey folks,

        Well, I gambled and bought that cheap PolySix from the pawnshop. 
Brought it home last night, opened it up - the battery looked fine at
first glance, but a closer look showed reasonable oxydization on the
part hidden from view.  No leakage yet!  Good find, IMHO.

        So I went down to the nearest Radio Shack on my bike and picked
up a
CR-2032 and holder, and I already had the appropriate diodes in my
drawer - I followed the instructions on Scott Rider's pages very
carefully, and now I have what appears to be a fully completed PolySix.

        But no.  It doesn't work.

        Scott's site says that if all of the program buttons are lit,
then the
problem is probably a blown CPU, and that I should mail him if this is
the case.  Well, that's the case - all the LED's are lit up.  I've
mailed him, last night, but haven't received a reply yet.  I'm *itching*
to find out how this synth feels in my setup, so I'm going to ask here,
if that's ok with everyone.

        Symptoms:

        I turn the synth on.  The LED in the "MG" section (MG == LFO, I
assume?  Modulation <something>?) flashes slowly, then speeds up until
it's on fulltime - elapsed time, about five to six seconds.

        If the machine has been off for a while, when turned on, the
LED's
marked 16, 8, 4, 2, etc - oh yes, this machine has a "Miditec" MIDI
retrofit in it, hope that's not the problem... - wait a few seconds
before all coming on at once.  I'm not sure what these buttons are
originally labeled; the retrofit kit added some nice stickers over the
original labels.  The program LED's - all eight - are alway all on.  All
other buttons with LED's are on fulltime as well.

        The arpeggiator section - the LED is working.  Twiddling the
"speed"
knob makes the light blink faster or slower appropriately.

        There is NO SOUND whatsoever, apart from a hum at full volume
that
isn't affected at all by pressing keys or twiddling knobs.

        I've still got my fingers crossed that this is just the lack of
processor, but the only reason I believe that is Scott's site.  Thought
I'd open it up to the group for discussion, as I'm antsy to get this guy
running! :)

        Any help is appreciated, thanks for your time...

        Cheers,
        - Drew.


--
Drew Smith, UNIX Network Administrator
Pacific Corporate Trust Company, Vancouver