NICE work
!
I am glad you liked it. I may well post other 'repair stories' if I
consider them to bne interesting enough (i.e. mroe than replacing a
trivially obvious componnent). At least until I get flamed for it :-)
Please post repair story Tony. I enjoyed reading it, and it gives me
the feeling that there are people that actually "think through" the
I am convinced (and it will take a lot to unconvince met) that htis is
the only way to solve _any_ such problem. Making changes essentially at
random never seems to help.
hardware to get the puzzle solved. You nicely told how
to got to
the solution, and showed us that in the end it often comes down
to simple things.
Err, yes... If I'd been more of a beginner, I'd probably have started by
testign those components I could easily test (like switches) and would
have foudn the fault in no time :-). But anyway...
Anyway, note that there was no board-swapping,
and no random
changes. As I said, I spent most of the time looking at signals
and working out what was going on, not changing things.
:-) Yes that was clear, and it only shows more clearly that using
brains is the most important tool.
I am sure we all know here that there's no magic box you can connect to a
defective defice and which says 'The 1k resistor at location R10 is too
high'. but an amazing number of non-technical people seem to think there
is. All the test equipment in the world won't help you find the fault
unless you use it and interpret the results intellegently.
-tony