I thought about my post a little more after sending it. One thing you might try is
downloading a service manual for a different analog synth from about that same time
period. The Sequential Six Track comes to mind. The implementation is quite different,
but the basic idea of how it works is similar. Scanning the front panel, scanning the pots,
feeding out the voltages to the S&H circuitry. That sort of thing. And there is a lot of
text that explains how the different sections work.
The Polysix has a lot in common with a lot of other designs from the early 80s.
Many mfrs gave nice descriptions of the basic circuit operation in their service manuals.
(Which you can find with Google in about 10 seconds)
Bob
BTW, The assembly code may not be that easy to follow, but my listing has comments
throughout that explain what the code is doing. That's why I mentioned it.
Unfortunately, if you really want to understand what a microprocessor-based system
is doing, the answer is in the code. Of course it's possible to troubleshoot without
knowing. Just look for floating signals and bad voltage levels, in the case of the KLM367.
You could print a copy of the KLM schematic and highlight the connections as you test
them with an ohmmeter set to beep on a connection. It's tedious, but luckily it's not
that big of a board, and the battery damage is usually in a fairly small area.
I guess you are thinking that this may not be from the battery, but some component
failure, right?
From: "noddyspuncture@hotmail.com [PolySix]" <PolySix@yahoogroups.com>
To: PolySix@yahoogroups.com
Sent: Tuesday, May 12, 2015 5:40 PM
Subject: Re: [PolySix] PolySix CPU question...
Thanks Bob, I couldn't open the download, but if that "asm" file is computer code...?!.. I will still have no idea...:(
I was asking if I could get to understand the way it all works using simple words and explanations...?
Computer programming and code is also beyond me.
When I am scoping all the data busses etc... it would be nice to understand what should and shouldn't be there. Just a basic understanding is what I am after so I can stand a chance of tracing faults in that section.
Cheers,
Tom