Truxton repair log #1

 PCB Repair Logs  Comments Off on Truxton repair log #1
Nov 062016
 

I got this Truxton PCB (export version of Tatsujin) in a recent operator raid:

100_9253

Once powered it up board showed GFX issue, the sprites were blocky :

Besides, there was some kind of video interference, this is a common issue on this board and usually it’s due capacitors in the audio section, indeed I found a 470uF 16V one with bad capacitance :

100_9275 Back to the sprites issue, relevant data are stored in four 1Mbit 28 pin MASK ROMs :

100_9257

I went to dump them and found a faulty one:

b65-04_bad

Replacing it with one from a donor board didn’t fix the issue therefore I went on in my troubleshooting.Each data bit of the sprites MASK ROMs is fed into inputs of four 8-bit 74LS166 register.I probed them with my logic comparator and led on output pin 13 lit for two of them:

100_9259

I desoldered the ICs:

100_9260

They both failed the out-out-circuit testing (obviously they were from Fujitsu) :

74ls16623a-24a

Sprites were fully restored :

100_9304

The last issue I had to fix was that Player 1 Start input didn’t work.The inputs circuitry was previously reworked by someone (note the replaced 74LS240 and some patched traces)

input_circuitry_reworked

I traced Player 1 Start back from pin 17 parts side of JAMMA connector to an end of a 220 Ohm resistor @R17 whose other end was tied to pin 13 of the 74SL240 @21K :

p1_start_tracing

Signal on pin 17 of the JAMMA connector and on first end of the resistor was high and correctly toggling when pressing the button while was totally missing on pin 13 of the 74LS240.Therefore the only culprit had to be the resistor.Indeed I got no reading measuring it on circuit:

100_9265

I removed  and tested the resistor out-of-circuit having confirm it was opened:

100_9269

100_9268

Job done.

 Posted by at 12:09 am

WWF Wrestlefest repair log #2

 PCB Repair Logs, Repair Logs  Comments Off on WWF Wrestlefest repair log #2
Oct 312016
 

When switching ON the game, sometimes it had very fast tempo music.

It happened 1 one out of 10 but it was very annoying.

So I used my frequency counter when it happened and I noticed that the 3.58mhz quartz ran at about 10.58mhz!

I changed it with a know good one but again it happened very often.

I was sure it was something connected to the quartz oscillator circuit and given that the resistances are difficult to be faulty I decided to change the cap C47  (33pF) with known good one.

After testing about 30 cycles of switching on and off the game didn’t develop again the problem

Game fixed.

 

wwf

Liquid Kids repair log #1

 PCB Repair Logs, Repair Logs  Comments Off on Liquid Kids repair log #1
Oct 312016
 

This game had two problem:

  • Glitchy and noisy sounds
  • Blocky background images

liquidk2

 

Given the high unreliablity of Taito maskroms I immediately tested the ones marked in red which with no surprice some pins not connected internally

 

liquidk

 

C49-04 restored the glitchy sound and C49-02 fixed the blocky gfx.

Replacements to be used are 27c400 (4mbit eproms with maskroms pinout)

Game 100% fixed

liquidk3

Toki repair log #1

 PCB Repair Logs, Repair Logs  Comments Off on Toki repair log #1
Oct 312016
 

Got this game for a repair which had all screen with washed out colours

toki2

 

This game has a SEIBU custom named UEC51 which is used as a DAC to output the RGB colours on the monitor.

The input pins were good, but a couple of output pins were fixed, thus creating the images as they had less shades of colours.

I took a good one from another Toki which had other faults and the problem was fixed 100%

 

toki1

toki3

 

Diet Go Go repair log

 PCB Repair Logs, Repair Logs  Comments Off on Diet Go Go repair log
Oct 312016
 

The game had two problems.

First one was the music that sometimes when switching on the game was glitched (very fast tempo or corrupted voices)

The first problem was fixed by replacing  capacitor C7 which was used to reset the chips and didn’t work correctly.

dietgogo

 

Second problem was some black pixels on some elements of the background.

dietgogo2

After shorting some data lines of the gfx maskroms I found the one responsibile for the background images.

Normally when a markrom fails you get blocky graphics. In this case was only some bad pixels.

Looking on the solder side of the pcb I immediately noticed one pin of one address line of the background image markrom touching the network resistance beside which forced the address line to 1.

diet3

Disconnecting it solved the problem

diet4