Hi Andy, thanks for your reply.
Sorry I wrote 366 instead of 367 :)
I checked all the PIO on the CN10 but this time I pressed the relatives buttons during the measurement, for example:
I put the scope on P10 and the level was 0, then I press 1-5-A-Manual and I can see the two logic states on the oscilloscope. I did this for every P on CN10 and all works fine.
So the problem should be on the 367. The board was repaired for the usual acid problem. And the original blue socket too was changed whit one with this kind of pin-holes
http://rocky.digikey.com/weblib/Mill-Max/Web%20Photos/117-93-640-41-005000.jpgthe board was cleaned and the broken tracks wire-jumpered.
I tested all the PIO directly connected from to the CPU to the CN and I can't find any interruption.
I have to say the synth has not any particular problem, every parameter works good. But I'd like to understand the cause of this problem (a firend of mine has this same problem too).
Do you think the problem could be caused by a malfunction of IC3 on 371?
I see P26 and P27 are directly connected on this IC.
Aniello
--- In PolySix@yahoogroups.com, Andrew Jury <andy@...> wrote:
>
> Hi Aniello,
>
> I¹d doubt very much if it is the 366 at fault. The data and PIO bus have
> transitioning logic states on them so it is not really a good idea doing a
> DC check on them as the result are meaningless. You¹d be better off using a
> scope or even a logic probe (one with with CMOS and a pulse train setting).
> However, having 0v on the whole PIO bus doesn¹t sound good. I can only give
> you general advise here as you haven¹t got all the test gear, but if you
> have had a battery leak and still have the original blue 40 pin CPU holder
> installed it might be worth checking for damage underneath it. I have seen
> some very bizarre problems before in the past and have had to resort
> removing, cleaning up and then replacing it with a new socket. The
> programmable IO bus (P lines) are connected directly to the CPU! If you are
> really at the end of your patience with the board and can¹t get any further,
> drop me a private message as I may be able to help you.
>
> Cheers,
> Andy
>
>
> On 18/09/2010 19:34, "aniello iaccarino" <ani.bliss@...> wrote:
>
> >
> >
> >
> >
> >
> > Ok the problem should not be on the KLM 371
> > I checked all "Pxx" and "Dxx" and all works good.
> >
> > So the problem should be in the KLM 366?
> >
>
>
>
> [Non-text portions of this message have been removed]
>