RE: R: I: STAR CASTLE PCB with a "little" problem - SOLVED - Yet Another Cine Board to Repair - FIXED

From: vernimark <vernimark_at_vernimark.com>
Date: Thu Jun 23 2011 - 07:45:19 EDT

>I suggested working
>from the video output backwards starting with M2 because it is the
>data latch for the lowest nibble of the Y axis on the video port J2

Yes, that what I wanted to do in the beginning but after some discussions I
had here I was convinced it was an ALU problem so I started from there...

ABOUT YESTERDAY PROBLEM topic: Yet Another Cine board to Repair
This is what I saw...
http://www.vernimark.com/temp/cinematronics01.jpg

FIXED!

It was a faulty 7402 in H8 position ("Line Counter - to LF13331").
Now:
http://www.vernimark.com/temp/speedfreak01.png

it was a CINEMATRONICS BOARD REVISION B with SPEED FREAK ROMs and it seems
roms are not compatible with that PCB release (you can see only the upper
part). I swapped ROMS from my VECTORBEAM PCB with STAR HAWK Roms (working)
and now both of them work fine and (MOST IMPORTANT) a cinematronics game has
a cinematronics PCB and my future speed freak cab will have a vectorbeam pcb
:)

How could I find the damned faulty 7402???
It's a shame but I hadn't ANY IDEA about the reason of that so I just
checked all components with HP logic comparator... I changed some 74107
because I had some false positive, probably because I used for comparison an
HC and it was too fast to compare with LS and lights blinked when 107
chanced status. 4 hours at all, 1x7402, 4x74107, 2xbattlestar galactica
episodes

Regards,
vernimark

-----Original Message-----
From: owner-vectorlist@vectorlist.org
[mailto:owner-vectorlist@vectorlist.org] On Behalf Of William Boucher
Sent: giovedý 23 giugno 2011 1.21
To: vectorlist@vectorlist.org
Subject: Re: R: VECTOR: I: STAR CASTLE PCB with a "little" problem - SOLLVED

Congratulations on your success. Good job. I can't believe how close to
calling this one I was. In my post from June 7, 2011, I suggested working
from the video output backwards starting with M2 because it is the data
latch for the lowest nibble of the Y axis on the video port J2. It actually

turned out to be the very next chip in line, N4 that provides the data
directly to the M2 latch. I think that was a pretty good guess. It feels
good to be at least in the ball park for once.

I saw your picture of your next board to fix that you posted today. I
haven't got a clue about that one.
Best of luck :-)
Keep us posted.

William Boucher
http://www.biltronix.com

----- Original Message -----
From: "vernimark" <vernimark@vernimark.com>
To: <vectorlist@vectorlist.org>
Sent: Wednesday, June 22, 2011 6:28 AM
Subject: RE: R: VECTOR: I: STAR CASTLE PCB with a "little" problem - SOLLVED

As you know I started from this condition:

http://www.youtube.com/watch?v=n9h0c9qYkZM

After some checks the problem was in a faulty 74194 (4-BIT BIDIRECTIONAL
UNIVERSAL SHIFT REGISTERS) in position N4: Secondary accumulator, logic
block 3

regards,
vernimark
www.vernimark.com/arcade

-----Original Message-----
From: owner-vectorlist@vectorlist.org
[mailto:owner-vectorlist@vectorlist.org] On Behalf Of vernimark
Sent: mercoledý 8 giugno 2011 16.43
To: vectorlist@vectorlist.org
Subject: RE: R: VECTOR: I: STAR CASTLE PCB with a "little" problem

Monitor is ok (star hawk and armor attack work well), this evening I'll
check the PCB flat connector

-----Original Message-----
From: owner-vectorlist@vectorlist.org
[mailto:owner-vectorlist@vectorlist.org] On Behalf Of Christopher X.
Candreva
Sent: mercoledý 8 giugno 2011 16.25
To: vectorlist@vectorlist.org
Subject: Re: R: VECTOR: I: STAR CASTLE PCB with a "little" problem

On Wed, 8 Jun 2011, vernimark wrote:

> I'm sorry for the quality of my video, but if you look it carefully you
can see the "rings" of the castle
> shake a little bit. But if you look more carefully the rings don't shake
, they are simply drawn with some
> segment vertex wrong for a short time, just a "frame" (I know we don't
have frames in vector games). The same
> happens with the animy starship: when it rotates in some positions and for
a very short time, some vertex are
> wrong. So definitely it is not a problem limited to one object.
> I already changed 181 TTL RAMs and ROMs

If it's all objects then maybe it's one of the DACs, either a stuck pin or
just one "bit" with a desoldered pin.

==========================================================
Chris Candreva -- chris@westnet.com -- (914) 948-3162
WestNet Internet Services of Westchester
http://www.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

---------------------------------------------------------------------------
** 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 Thu Jun 23 07:45:31 2011

This archive was generated by hypermail 2.1.8 : Thu Jun 23 2011 - 09:50:00 EDT