Phil,
No, please do quote away! This is interesting because the KLM-367
board on this P6 was pretty badly burnt with blue nickel cadmium
pixie dust. It would make sense it suspect further broken tracks
which I might of missed. I will check the data line and the inhibit
continuity for the whole circuit and see if there are any breaks. Can
you just confirm that the receiving mux's output should swing between
+5 and -5 and not +5 and -0.17v! I guess I know what you are going
say...
In my case I am assuming this is why I can't get the MG to oscillate
above 3.4Mhz. If the swing reached -5v then I might get the full 50hz.
Thanks and I will let you know what gives...
Cheers,
Andy
--- In PolySix@yahoogroups.com, "synx508" <philyahoo@...> wrote:
>
> --- In PolySix@yahoogroups.com, "Andrew Jury" <andy@> wrote:
> >
> > Now forgive me if I am wrong
> > but I understood the HA14051 worked like this. You appliy a
voltage
> > to one of the 8 mux inputs marked X0-7. The voltage change is
> > detected and a bitmap is set on data address lines A, B and C
> > according to which pin was strobed. At the other end this bitmap
is
> > decoded the data read on the receiving mux and the appropriate
signal
> > (in this case a voltage) will appear at the correct pin as
determind
> > by the bitmap. The fact that the voltage doesn't swing correctly
> > between the two poles of the pot would suggest a fault with the
> > transmitting HA14051?
>
> That's how it works, but before you go suspecting the mux, are you
sure you're getting
> the full range of digital data on A, B and C at both ends? The at
both ends bit being really
> important, on one of my KLM-367s I had the right signals present
right up to within 1mm
> of the connector, at which point one of my mux selection signals
became something
> entirely different thanks to the wonderful way the nicad redesigned
the board.
>
> Sorry about the over-zealous quote snipping, btw.
>
> --
> phil
>