gravitar, x-output issue

coolveco

Newbie
Feedback
1 (100%)
Credits
2CR
Hi Guys !

I am trying to fix a Gravitar board. It was watchdog-resetting, and after a lot of effort, I finally found out that the pokey was messing with the address lines. After removing the pokey, the board boots but the vector address custom chip is dead, so I replaced it with a BXAVG, and I now Y output. X, however, is at zero volts.

A10 (TL082) was very hot, so I replaced it. Still no output, so I suspected the DAC. Replace it with a socket and a new DAC, same issue. The suspect is now XREF signal, which is always at 0V. This is weird, because YREF is just fine. The ref signal, available on R165, R166, R167 and R168 is ok. On the other side of R166-R90, YREF appears perfect, but the same circuitry R167-R91 gives 0V. Removing the DAC restores the signal, as expected (the resistors are fine). Since this is a brand new DAC, I have a hard time believing that it's also dead (I ordered 3 dacs, checked with 2 of them, same result).

The power rails are all fine, checked at the DAC pins. Removing the op-amp or the LF13201 doesn't help either.

Any clue ? ;)

Thanks

-Fred
 

Mitchell Gant

Active member
vacBacker
Feedback
2 (100%)
Credits
888CR
How about checking that the DAC @ A/B9 has valid changing digital inputs? Could be that you've fixed the analogue part but the digital part has a fault that is just telling the DAC to output nothing?

Although I think you should still see XREF show some reading even if the DAC is not getting changing data, so it's not much of a clue I'm afraid.
 

coolveco

Newbie
Feedback
1 (100%)
Credits
2CR
I checked the digital inputs. There is activity, and it looks legit. Hard to tell if it's really legit unless I hook a logic analyser and capture the 12 bits... but xref should not be 0V at all time. And too bad that this dac has current output, so it's hard to see activity on pin 18.
 

coolveco

Newbie
Feedback
1 (100%)
Credits
2CR
Board is finally fixed ! It had multiple issues, and the analog section was completely hosed. (I suspect a bad voltage +15 or -15 killed many components).

That particular issue above was a dead LF13201, which had 2 switches always on, so the X signal and the X signal inverted were tied together, resulting in an almost 0V signal...
 
Top