Oct 232015
 

I recently repaired a friend’s dead Ikari Warriors PCB.

It had a black screen on boot with no sound.

This game is a bit tough to diagnose as it is composed of 3 PCBs mounted on each other. Fortunately I had another working Ikari Warriors PCB so I could swap boards in order to track which board(s) were faulty. Top board and middle board were tested ok on my working Ikari so, fortunately, only the bottom board was faulty.

Here is a picture of the faulty bottom board with the faulty chips I replaced in red. I’ll explain every step below.

ikari1b

1. There was something that was avoiding the game to boot on that board. First, in order to reduce the field of investigation, I disconnected each of the 3 connectors on my working Ikari to see when the game was booting or not. It was booting only with the two bottom connectors on, the one above is only related to the sprites and doesn’t prevent the game to run. So I needed to focus on and around these two bottom connectors. I checked the signals on every pins to track a possible missing signal. After comparing the signals, I found one that was “floating” on my faulty board and was pulsing on my working board. This was connected to pin 9 of the 74LS367 (marked 1 on the PCB picture). Piggybacking a working chip on that one bring the game booting back again !

2. Well, the game worked but the characters had missing legs and were always looking down whatever movement you did, enemies had wrong visuals and background scrolling was jerky…

As previously seen, the sprites are related to the upper connector. I started to check the signals on the upper part of the board and quickly found a 74LS273 (marked 2 on the PCB picture) with a seemingly dead output (my working board confirmed this). Piggybacking the chip with a new one bring back the characters’ movements and visuals. I still had the jerky scrolling though…

3. This one took a bit longer as I had no real idea where to look on the board for the chip that was responsible of this jerky scrolling. After more than an hour, comparing signals between the working and faulty boards, I found a suspicious signal on a 74LS86 (marked 3 on the PCB picture). This was indeed a dead output (pin 6). Piggybacking a good chip on it bring back the smooth scrolling.

As an example, here is what the signal looked like on the pin 6 of that 74LS86 before and after replacement.

ikari4

Board is now fully fixed.

Frogger (Sega/Gremlin) repair log

 PCB Repair Logs  Comments Off on Frogger (Sega/Gremlin) repair log
Oct 202015
 

Got this Frogger PCB from my friend Josef for a repair.Actually it was the Sega/Gremlin version which uses Konami Classic pinout (like Gyruss, Scramble and many others):

Frogger_PCB

PCB played fine but had a strange issue where sound was very quiet on my supergun while was completely silent on a cabinet.All audio circuitry is located on upper board.Looking at i I could notice that someone had previously reworked (replacing it perhaps) the M51516L amplifier ending with break some traces and using some jumper wires to fix it:

M51516L_reworking_

Luckily schematics were available so I went to check every connection in this part of circuit.Everything seemed fine until I came across to something odd : PIN 6 (ground) of M51516L amplifier was intentionally jumpered to positive terminal of a 100uF 25V electrolytic capacitor (so both terminals was shorted to ground) :

100uF25V_PCB

while schematics showed it connected to collector of a transistor through a 1KOhm resistor :

100uF25V

Removing this jumper wire restored full sound.

 Posted by at 10:45 pm

Ghox repair log

 PCB Repair Logs  Comments Off on Ghox repair log
Oct 192015
 

I got this Ghox PCB from my friend ‘robotype’ for a repair:

Ghox_PCB

On the power up I was greeted by this static screen:

boot

Address/data bus of 68000 main CPU was inactive.As usual I went to loot at MAME source (that is a bit like a bible for us repairers) and I found this interesting comment:

// Ghox 68K reads data from MCU shared RAM and writes it to main RAM.

I could identify the HD647180 MCU RAM in a 6116 @U14 :

RSCN0566

So I went to probe it with my analog oscilloscope and found weak signal on some address lines (good one on left picture, bad on right) :

address_lines_comparison

I piggbacked this RAM and board booted showing this error message:

palette_RAM_error

After replaced the MCU RAM (which actually failed the out-of-circuit test), I traced the palette RAMs in two 6116 chips @U41 and U42 :

palette_RAMs

One of them had already been replaced so I went to piggyback the other one @U41 and board successfully booted:

fixed

Obviously the chip failed miserably the test on my programmer:

6116@U41_failed

End of job.

 Posted by at 11:21 pm

Nintendo Playchoice-10 repair log

 PCB Repair Logs  Comments Off on Nintendo Playchoice-10 repair log
Oct 152015
 

I got this board from my friend Joachim for a repair.A Nintendo Playchoice-10 system:

Playchoice_10

For the uninitiated, Playchoice-10 is the arcade hardware developed by Nintendo to run its most popular NES games inside an arcade cabinet.The games for this system are in the modular form of carts which are plugged into one of the ten open slots on the PlayChoice-10’s motherboard:

Playchoice10_cart

When I first powered it up, I was greeted by a solid black screen, no activity on main Z80 CPU.A closer inspection revealed a missing 8MHz crystal @X1 which supplies the clock to main CPU:

missing_8MHz_crystal

Once fitted a new crystal I had clock signal on pin 6 of the Z80 but the watchdog circuti was active ( /RESET line was constantly going to HIGH to LOW state in a endess loop).I pulled the Z80 and tried it in a good board having confirm it was faulty.With a good CPU all I got was a green screen:

green_screen

While probing chips I came across a TMM2115 (6116 compatible) RAM @4K which was burning hot to the touch, I remove it and my programmer reported it as shorted:

TMM2115@4K_shorted

With a good RAM I got always that green screen but could hear sound sign that the board was playing ‘blind’.This was a good chance to use my Fluke 9010A troubleshooter.MAME reported this memory map:

0000 – 3fff = Program ROM (8T)
8000 – 87ff = RAM (8V)
8800 – 8fff = RAM (8W)
9000 – 97ff = SRAM (8R – Videoram)

I could successully perform a RAM LONG test on address space of RAM @8V and 8W but I got an error on the videoram @8R (all these RAMs were 6116 compatible):

RAM_LONG@8R

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

TMM2115@8R_failed

Finally I got it running:

Playchoice10_fixed

but, since the motherboard (PCH1-01-CPU) was a dual monitor type, I could not display the playfield (although it came with this JAMMA adapter which provides also outputs for a second arcade or VGA monitor)

Playchoice10_JAMMA_adapter

 

 Posted by at 11:44 am

Knuckle Bash repair log #2

 PCB Repair Logs  Comments Off on Knuckle Bash repair log #2
Oct 142015
 

I got this Toaplan Knuckle Bash from my friend Josef for a repair.

Knuckle Bash PCB

He said board showed graphical issue which he could clear only by raising the 5V to +5.5V.After powered it up I had confirm of what he told me, actually colors were bleeding (you can notice it on right part of the picture below):

color_issue

Schematics for this board were available so I could identify the part of circuit which generates the color palette:

Knuckle_Bash_colors_circuitry

Data from the two 6116 SRAMs are latched by two 74LS273 (actually my board mounted two 74HCT273).When I went to piggyback the one @U9, colors were restored.I desoldered the IC but it succesfully passed the test in all my programmers, also comparing it with a good one on a tracer showed no abnormality:

74HCT273_comparing

Probably it was not really bad but its thresholds were altered.Despite this, I socketed and replaced it:

74HCT273@U9

Another cool game fixed.

colors_fixed

 Posted by at 10:35 pm