Dark Seal repair log

 PCB Repair Logs  Comments Off on Dark Seal repair log
Aug 032017
 

Got a Dark Seal PCB in a lot of faulty boards recently acquired.For the uninitiated Dark Seal (also known as Gate of Doom in USA) is an action game with isometric perspective and R.P.G. elements released by Data East in 1990.

My board did nothing upon boot giving a solid black screen.Applying pressure on one of the custom ’55’ (the one in the upper right corner) restored the video output, a closer inspection revealed some lifted pins so I did a reflow.I got stable video output now and could play the game but image was rolling, this was a clear sign that SYNC signal was missing :

There are no documentation available but other Data East games share same design.Desert Assaul for example, here’s a snippet from its schematics :

As you can see SYNC signal is generated by pin 157 of the custom ’55’ and then inverted two times by a 74LS04 before reaching the JAMMA edge.I could measure a good signal on this pin :

but nothing on pin 13 solder side of JAMMA connector  :

So the problem was in the middle.Looking at solder side of board I noticed the area of the 74LS04 that inverts the SYNC signal has been badly reworked in order to socket the TTL itself, some rivets were ripped off:

Signal was present on pin 1 of the 74LS04 and correclty inverted on pin 2 but, following the scheme of Desert Assault, it was absent on the adjacent pin 3  (pin 4 is connected to JAMMA SYNC pin via a 47Ohm resistor) so the trace between pin 2 and 3 of the inverter had been severed by the previous attempt repair.I simply bridged these two pins restoring the SYNC on JAMMA.But, once I got a stable image, I  noticed the blue color was very strong and after some time it disappeared causing a yellowish screen:

Color generation circuit is pretty the same of Desert Assault:

As you can see bits of the tree colors from the 8-bit latches are converted to analog by a resistor ladder and, lastly, each color is amplified by an NPN transistor.Signal was absent on the emitter and base of transistor so problem was upstream.Going back I found nothing abnormal until I got to the palette RAMs, three 2018 :

The one highlighted in the above picture was burning hot to the touch, with a termocouple I could measure an external temperature of 69°C  compared to 48°C of the other two (RAMs in palette circuitry run usually warmer than other since they have greater power dissipation due very fast access time, 35ns on these ones)

Analyzing the suspicious RAM with a scope revealed all data lines were stuck low (healtly signal on left, bad on right of the below picture)

Once removed, the chip failed the out-of-circuit test:

Fitting a good RAM fixed board completely.

 

 Posted by at 9:29 pm

Turbo Force repair log #2

 PCB Repair Logs  Comments Off on Turbo Force repair log #2
Aug 022017
 

Bought this faulty Turbo Force PCB for cheap on Ebay:

Seller claimed board had a sprites issue, I had confirm once powered it up, some objects were missing parts or disappeared when scrolling:

Before starting my troubleshooting I remembered that some weeks ago I repaired another Turbo Force with similar issue, you can read log here:

Turbo Force repair log #1

In first repair the issue was due a faulty ‘VS8905’ sprites address generator (there are two of them on PCB)

When I put my fingers on the one @U115 (same location of the faulty one in previous repair) it was quite hot, this was a clear sign that internal junctions were bad and a proof that this part is prone to failure.I  removed and replaced it:

Success!Another archivied repair.

 Posted by at 11:02 pm

Ordyne repair log

 PCB Repair Logs  Comments Off on Ordyne repair log
Aug 012017
 

I received some days ago an Ordyne PCB for repair.Game runs on a powerful system called “Namco System 2” made of a CPU board:

and a VIDEO board:

Here are some specs:

  • Main CPU: Motorola 68000 @ 12.288 MHz (16/32-bit instructions @ 2.1504 MIPS )
  • Sub-CPU: Motorola 68000 @ 12.288 MHz (16/32-bit instructions @ 2.1504 MIPS)
  • Sound CPU: Motorola M6809 @ 2.048 MHz (8-bit instructions @ 0.86016 MIPS)
  • MCU:
    • Hitachi HD63705 @ 2.048 MHz (8-bit instructions @ 2.048 MIPS)
    • Namco C68 (Mitsubishi M37450) @ 8.192 MHz (8-bit instructions @ 1.024 MIPS)

My board was faulty since it was sitting after performing the SELF-TEST without reporting any error  :

First of all I swapped a good motherboard but this didn’t lead to any improvement so the fault was located on VIDEO board.At a closer inspection I found some scratches on solderside of this board:

One trace was really severed, it was the one connected to pin 9 of the KEY custom ‘176’.Problem was caused due the board has been crushed under some weight hence solder sides of the two boards were touching and scratching each other:

After patched the trace, the board successfully entered in game but I could not coin up.I quickly pinpointed this fault to a missing ‘CUS95’ resistor array @1K near the JAMMA edge:

No further issues were found so board 100% fixed.

 Posted by at 6:40 pm

Moon Cresta (Nichibutsu) repair log

 PCB Repair Logs  Comments Off on Moon Cresta (Nichibutsu) repair log
Jul 162017
 

Received this original Moon Cresta PCB (board ‘SMC-2FJ’ manufactured by Nichibutsu) for repair :

Board booted up but some sprites were upside down and partially doubled :

Some Fujitsu TTLs were present so I went through them with my logic comparator.I quickly found a suspicious 74LS08 @6H:

It was really bad once tested out of circuit:

Now sprites were correctly placed but I noticed that the bullets were missing:

Looking at schematics there are two separate circuitries which generate yellow and white bullets.Probing them I found that the two active LOW signals /YBPS and /WBPS were stuck HIGH all the time also when you pressed the fire button and generated the bullets:

 

 

The signals are geneated by a 74LS139 @4C:

My logic comparator complained about pin 11 everytime I pressed the fire button and hence activated the selection line B on pin 13:

I pulled the TTL and I had confirm it was bad in that specific gate:

Fitted a good TTL and bullets were displayed again.Board 100% fixed.

 Posted by at 10:49 am

Turbo Force repair log #1

 PCB Repair Logs  Comments Off on Turbo Force repair log #1
Jul 092017
 

Got this faulty Turbo Force PCB for repair:

 

First of all I soldered back an hanging wire:

Then I powered the board up : the fault concerned some sprites, they were scrambled:

The relevant data are stored in four devices :

Probing them revelead that some address line had abnormal activity (good on left of the below picture)

Address lines for the sprites devices are generated by one of the two surface mounted custom ‘VS8905’ (the one @U115)

I played the card of replacing it :

And this was successful, board fixed.

 Posted by at 7:28 pm