Re: Tempest displays on scope, but not 6100

Where are these? The 6100 harness has X/Y deflection & ground connections, and RGB + ground, which seems to be the entirety of the video signal. It's my understanding that the RGB outputs *are* the "Z" levels for each of the color guns, and mixing different intensities of RGB are what produces the color. But maybe you mean something upstream, in the digital section?

I'm pretty convinced that it isn't the Z outputs at all. Even if Z was totally disconnected, if I had XY inputs and cranked the screen control, I should see *something* as the beam was deflected. But I have no deflection, only on the 6100.

On Jun 29, 2013, at 3:47 PM, Kevin Moore <talon.k@gmail.com> wrote:

> You will probably get a RGB signal with out a Z signal. You need to check the Z0-Z2 signals for output.
>
> Kevin
>
>
>
> On Sat, Jun 29, 2013 at 5:19 PM, IAN EURE <ieure@mac.com> wrote:
> I tested the GBR outputs, which I think is what you mean. They are present and look good vs. a working PCB.
>
> The more I think about it, the more I think it has to be that the game board is putting out a signal that is triggering the input protection circuit, since that's the only thing I can come up with that would kill deflection in the 6100 while the scope continues to show the image.
>
> I don't have an input protection riser board on my 6100. Were these integrated into the deflection board in later revisions? If not, that blows away my only theory.
>
> On Jun 29, 2013, at 2:19 PM, Kevin Moore <talon.k@gmail.com> wrote:
>
> > You did check Z0 Z1 and Z2 right?
> >
> > Kevin
> >
> >
> >
> > On Sat, Jun 29, 2013 at 4:06 PM, IAN EURE <ieure@mac.com> wrote:
> > I got back to this today, and I'm still completely stumped. I checked the RGB outputs, and they seem fine. I compared the X and Y sections individually on the scope to a working board, and everything is within range. On the RGB outputs, I see them turning off and on like they should — nothing stuck there. I also compared those to a working boardset, and they seem fine.
> >
> > I checked the X and Y grounds, and they are fine. It looks like there's an error in the schematics, as the video return line is marked as pin M of the AVG edge connector, but this hooks to the collector of Q7, which is for the middle coin mech. Either way, the ground pins on the 6100 connector have continuity to the ground plane on the PCB, and the ground is correctly hooked to Q10.
> >
> > My understanding is that the SK operates by shutting off the beam current, no matter what causes it to activate — which is to say, if deflection is present, it is unaffected by the spotkiller. This is where I'm hung up: I /have/ deflection on the scope, but even when I turn up the brightness on the 6100, I have no deflection.
> >
> > Any other ideas?
> >
> >
> > On Jun 22, 2013, at 8:13 PM, Rodger Boots <rlboots2@gmail.com> wrote:
> >
> > > If X is good and Y is good make sure ground is also good. A long shot.
> > >
> > > Well the voltage output on x and y could be out of range for the monitor. So I would take the scope out of xy mode and measure the voltage output of the x and y. It's probably good from reading your write up.
> > >
> > > I can't recall if the color output circuit would cause this problem, typically I've only seen 1 color go bad before, but maybe you are missing all three?
> > >
> > > I would most likely suspect the z outputs from Data shifter H7 Try checking those outputs, and reseat the 2 VG Eproms JIC.
> > >
> > > Kevin
> > >
> > >
> > >
> > > On Sat, Jun 22, 2013 at 6:02 PM, IAN EURE <ieure@mac.com> wrote:
> > > I have this Tempest PCB I've been working through. I have it displaying a self-test screen indicating some errors that need work, but I can only get the screen to come up on a scope. Because I have no Z channel and only have 10x probes, I can't read the error codes on the scope. When I hook the game to a K6100, I just get a spotkiller.
> > >
> > > Has anyone seen this before?
> > >
> > > I know it's not the monitor, because I'm testing in a working cabinet. I thought it might be the PCB adjustments, but I used the scope to calibrate them to the same levels as another PCB, which does display in this cabinet. I turned off & disconnected the scope, in case that was interfering with anything; no change. I'm hooking the scope to the X/Y out test loops on the board. I thought there might be a broken trace between there and the edge connector, but I checked and there is continuity. I turned the screen control up on the 6100 to bypass the spotkiller, and all I have is a dot in the center; no deflection at all, despite seeing a signal on the scope.
> > >
> > > What am I missing here?
> > >
> > > Background: Got the board resetting in game mode and blind in test. Cleaned & reseated ROMs, and got it playing blind as well. But it went back to resetting a day later, which indicates dodgy ROM sockets. I'd prefer not to replace all 10, so I decided to get self-test going so it would tell me which were faulty. Replacing the TL082s got me a box in self-test with no text, and swapping the ROM @N/P3 got me a reasonable looking test screen. But I can only see it on the scope.
> > > ---------------------------------------------------------------------------
> > > ** Unsubscribe, subscribe, or view the archives at http://www.vectorlist.org
> > > ** Please direct other questions, comments, or problems to chris@westnet.com
> > >
> >
> >
> > ---------------------------------------------------------------------------
> > ** Unsubscribe, subscribe, or view the archives at http://www.vectorlist.org
> > ** Please direct other questions, comments, or problems to chris@westnet.com
> >
>
>
> ---------------------------------------------------------------------------
> ** Unsubscribe, subscribe, or view the archives at http://www.vectorlist.org
> ** Please direct other questions, comments, or problems to chris@westnet.com
>

---------------------------------------------------------------------------
** Unsubscribe, subscribe, or view the archives at http://www.vectorlist.org
** Please direct other questions, comments, or problems to chris@westnet.com
Received on Sat Jun 29 19:30:24 2013