PCB Repair Logs – Page 41

R-Type repair log and Irem ‘KNA6034201’ reproduction

PCB Repair Logs, Reproductions 5 Responses »

Jun 282017

Got some months ago in a trade this pretty mint original R-Type board:

Board was faulty, it was stuck on this static screen:

System is made of three boards:

ROM board

CPU board

Video Board:

Swapping all the boards with a good set I could figure out that none of mine was properly working.So I started to troubleshoot the ROM board since it’s the most simple.The program ROMs were dumped as good but I found a bad 74LS245 @1A:

This gave me a working ROM board and a good starting point so I moved on to troubleshoot the CPU board.Analyzing the NEC V30 (uPD70116) main CPU revealed the interrupt line was asserted (active high on this CPU), here’s a screenshot from my scope triggered with RESET signal

The interrupt is generated by the uPD71059C Interrupt Control Unit , probing it revealed that input pin 3 (READ STROBE) was stuck low :

This comes from output pin 12 of a 74LS244 @IC72 :

I pulled it :

It failed the out-of-circuit testing:

Finally the board booted but with multiple issues.First noticeable one was a totally missing sound but this was because the analog audio section was modified (by factory) to work in Nintendo cabinets.I simply reverted the mod by installing the missing capacitors @C101, C102 an C108 and removed the jumper wire:

All the other issues concerned the graphics.Some examples:

Honestly it would take too long to explain in details what I did (and maybe I even lost track of it…) before the board worked fine again :

All I can say is that I had to replace in total 15 TTLs (all from Texas Instruments, are we facing another Fujitsu perhaps?)

But I claimed victory too soon , the board went bad again showing jailbars all over the screen:

I quickly pinpointed this further failure in one of the two ‘KNA6034201’ custom tiles generator on video board:

Testing it on a Kung-Fu Master PCB (where it’s used for sprites too) gave me confirm it was really bad :

Looking at this PCB I noticed that the other custom ‘KNA6034201’ was replaced by a little sub-board:

Technically speaking the custom acts like a big shift register, it can take up to 24 bit of data from tiles or sprites ROM.As you can see in the sub-board picture above the custom functions have been reproduced using six 74LS166.So I wondered myself : why not reproduce it in a more modern way?I fired up my CAD and drawn schematics and touted them to a PCB layout.I sent files to manufacturer and after some time I got the bare PCBs:

Here is the final result compared to orginal custom:

Luckily I made no design mistake and testing was 100% successful.Another board repaired and another custom IC delivered to eternity!

Nintendo VS System repair log #2

PCB Repair Logs Comments Off

Jun 282017

I bought this system in a lot of faulty pcbs.

Game was booting but it had no sync and the graphic was all corrupted.

The OSC 21.477mhz was giving out around 12mhz

After changing it, the game was back to life but it was missing the blue component

Looking at the schematics , I could confirm that the RP004 video chip was giving good signal on the BLUE signal pin, therefore I started

to check the LM324 OP AMPS involved in the DAC circuit.

The output of the LM324 for the BLUE component was dead therefore I proceeded to change it but the game was not fixed yet despite now having a good signal

By turning the blue pot I could see briefly some “sparks” of blue ,therefore confirming that the blue component

was working again.

In the end it turned out that the blue pot had some cold joints on the ceramic base.

I reflowed the solder and the game was 100% fixed

Satan Of Saturn repair log

PCB Repair Logs Comments Off

Jun 282017

Got this game cheap for my collection because the seller stated that it has very noisy sound

When powered, the game had a constant white noise while music and the other sound effects were working correctly.

The sound problem was not due to the amplifier or bad caps but it was produced by the logic of the game.

To make a long story short, this game has a similar circuit to what Space Invaders use to produce analog sounds.

It uses a SN76477, which is a programmable sound chip which has a white noise function.

On Space Invaders and in this game, the chip continuosly output the white noise which is switched OFF and ON using operational amplifiers and it is modulated with capacitors and resistors to produce different sounds.

I downloaded the schematics from the US version ( called Zarzon ) where it is shown how the chip is connected to the LM3900 OP AMPS

Instead of trying to understand which of the two chips are broken, I piggybacked a good one on both chips until

the white noise disappeared.

Problem was fixed by changing the LM3900 Nr.47 on the schematics

Burnin’ Rubber repair log

PCB Repair Logs Comments Off

Jun 282017

I bought this game for my collection some months ago.

I tested briefly and it was OK. After a few weeks I decided to make a good play but the game developed a strange problem:

As you can see from the pics above, the screen was very dark and the brightness was not steady.

Also all the objects left trails of different brightness.

The problem was somewhat similar to when you don’t have video GND connected but as you can see

the text HI SCORE was repeated on top and bottom.

Adjusting the horizontal size of the image with the monitor pots ( vertical on the game) I noticed the screen didn’t shrink, it was like it had no borders.

I had immediately remembered that on the CPS1 hardware , on certain screens of some games ( 3 wonders selection screen for example)

the image is very dark and this is due to a flaw in the video circuit of the CPS1 hardware which doesn’t blank properly the video at the edges

leading to some monitor electronics to loose the black reference and behave strangely.

Charles McDonald on his website https://www.techno-junk.org/ has a fix but right now the link is missing because he is restructuring the page.

Anyway back to the topic, I was convinced that my problem was due to video blanking not working properly, so I downloaded the Bump and Jump

schematics available from Bally ( the japanese ones are impossible to find ) and searched for a video blank signal and tested all the TTLs involved until I found this:

Output pin 5 of 74ls74@1B was floating and didn’t clear the 74LS273 connected to the video DAC

Therefore the video was not blanked properly on the edges.

Changing the TTL@1B fixed the problem

Unfortunately after a couple of plays, the pcb developed two other problems:

Car didn’t go left
car crash sound was broken

The first problem was fixed by replacing the 74LS367@4E on the sound board ( directly connected to the left direction pin)

Second problem was fixed by replacing one AY8910.

The game, for the moment, is working nicely 😉

Defender repair log #1

General, PCB Repair Logs 1 Response »

May 252017

I got for my collection an untested boardset of Defender which was really in great conditions with no battery acid leak.

The boardset is the newer revision of Defender with the red label roms.

The game is very difficult to find it in working conditions nowadays because it has several weak points, expecially the 24 drams 4116 which are very unreliable to due the fact the run very hot and they require +5V, -5V and +12V to be applied at the same time, otherwise they will be damaged.

The old Williams PSU become defective and often they ruin the drams.

After converting it to Jamma and triple checked all the power supply lines I booted it up but the game appeared to be dead.

Fortunately Defender has a lot of bibliography and a very good manual which is also a troubleshooting guide.

I check the clock and it was working correctly, but after checking the reset line I saw it was pulled low all the time.

To make it short, Defender has two +12V power supplies, one regulated and one not.

You have to supply +12V also to the not regulated one because it is needed for the power on reset.

After adding that +12V t, the game booted but as soon as the message ALL UNIT OK was displayed it reset in a never ending loop.

I found out that the problem was caused by the ribbon cable , after reseating it a couple of times, the game booted correctly.

I started the game but the ship kept always going down.

With the test menu , it reported that the down direction was always pushed.

I checked the interface board which has the circuit for the inputs. the hex inverters 4049 were all toggling correctly, the pull up resistors were good therefore there was only one chip to check: the Peripheral Interface adapter 6821P.