Fujitsu FM-TOWNS Marty PSU repair log

 Console Repair Logs, Repair Logs  Comments Off on Fujitsu FM-TOWNS Marty PSU repair log
Jun 172014
 

I got from a German customer this nice Fujitsu FM-TOWNS Marty console.

For the uninitiated FM-TOWNS Marty a Japanese console whose hardware is derived from its “big brother” FM-TOWNS computer.It has some of the coolest perfect arcade ports ever published like Splatterhouse, Bubble Bobble, The New Zealand Story, Tatsujin Oh and others.

As every Japanese device it has to be powered by 100V/110V so European people must use a step-down converter capable to reduce our 220V/240V to proper voltage .

This is what the owner of this console forgot to do by mistake..:)

So, after some seconds the “magic smoke” came out from the console.

Obviously the console did not power at all so i opened it and I immediately noticed some blown components.In particular the main 2A fuse was blown and a 100uF 200V capacitor was literally exploded on its top.The blown fuse was a good sign since it means he made his duty blocking the excessive current flowing in the circuit but the big 100uf 200V exploded capacitor meant  that this overcurrent reached also other components before the main fuse blown up.So, I decided to further investigate.Usually the first component after main fuse and filter capacitor is the bridge rectifier (which, indeed, rectifies the sinusoidal current in continuous one).In my case there was a 600V 1A bridge rectifier marked ‘S1WB S60’, here the datasheet:

https://pdf.datasheetcatalog.com/datasheet/Shindengen/mXqwrsx.pdf

Infact, as I suspected, I tested it with a multimeter and it was shorted.

So, I desoldered these three bad components:

and replaced them with equivalent ones:

Reassembled the console, powered it and got this:

 

 

Mission accomplished.

 Posted by at 8:08 pm

Juno First repair log #2

 PCB Repair Logs, Repair Logs  Comments Off on Juno First repair log #2
Jun 152014
 

So here is the second repair log.
Pretty simple this one but I never took any pictures of the actual fault so Ive taken a snapshot of the event in MAME to show it.

The game plays as normal but when the blue ball enemies spawn into the game the froze up on screen and did nothing as circled in red in the picture below.
juno2

On my visual inspection I noticed a 1K pull up resistor array next to the bank of 4116 RAM chips what cracked in half.
juno2-1

Replacing this fixed the fault.

I did initially think there was another fault as the ship movement in attract mode seemed a bit strange but after checking in MAME this is a characteristic of the non Gottlieb version. In the Gottlieb version this behavior is not present.

Jun 062014
 

This is hopefully one of five Juno First repair logs.
Thanks (I think) to muddymusic I have a stack of these needing repaired. There are two originals and three bootlegs altogether and decided to make a start on the originals first.

This one booted to an unsynced red picture.

Looking at the schematics I could see that the sync is generated by custom chip 082 at location EF13 on the bottom PCB.
Swapping this chip with the one from the other board set brought the sync back. That’s bad news for original board set #2.

So now I just had a red screen with nothing going on.
It was at this point that I learned this hardware uses a custom 6809 CPU known as Konami-1. I was originally going to try and borrow a 6809 pod for the Fluke but that put a swift end it that idea.
Now’s the perfect time to use my beloved Arduino again.
By hooking it up to the address, data, RW, BA and BS lines I wrote a program that would read the program ROM’s back and display the data as well as a bitsum for the ROM.
It worked really well and found my second issue.

This is the original HEX file

and here is what I was actually reading on the board

You can see that bits 0 and 1 are always on.

So the 74LS245 at location D7 on the lower PCB had a two stuck pins on D0 and D1.

Replacing this enabled me to read all the program ROM’s correctly.
I had at this point wanted to be able to test RAM too but due to the timings required and not knowing how those custom chips worked I left it alone.

So now I have a booting game but all the sprites and title screen graphics are missing.

First thing I did was see if I could replicate the fault in MAME.
By creating empty files to replace ROM’s 7C, 7D and 7E on the top PCB I got the exact fault.

Checking those EPROM’s with the probe revealed that none of the chips were ever being enabled.
Following the schematics back to where the ROM selection lines are generated I came to a 74LS273 at location 6D on the upper PCB. Pin 11 is the clock pin for this chip and I would expect it to be pulsing but it was stuck HIGH. Following the /SSEL line back to the lower PCB led me to a 74LS138 at location I6.

This had pulsing inputs but either stuck HIGH outputs or floating pins. Replacing this chip gave me the graphics back.

That’s one down.

Bucky O’ Hare repair log #1

 PCB Repair Logs, Repair Logs  Comments Off on Bucky O’ Hare repair log #1
May 062014
 

Got this original Konami Bucky O’ Hare PCB for quite some time but I never looked at:

100_5295

Once powered on it displayed good graphics but loud, scratchy and distorted sound.Everyone in the arcade world knows that this kind of PCB use an hybrid custom sound module, in this case it’s the  one marked ‘054986A’ (other games like X-Men use the ‘054544’ one) which is famous to go bad (in particular its SMD electrolytic capacitors will leak sooner or later damaging tracks).Well, with these premises, I decided to do a full recap of the module following this chart:

https://jammarcade.net/images/2024/05/KONAMI_HSC.pdf

I opted for a different solution.I used tantalum SMT tantalum capacitors instead of electrolytic through hole or SMD ones.Why will you say?Because tantalum capacitors are extremely reliable, they don’t suffer from leakage and have a lower ESR.Last but not the least, they are also more elegant than electrolytic one like you can see in this comparison at the end of my recap/repaint job :

054986A_combined

Anyway once powered on again the board I got same sound issues.I know this custom module has additional circuitry also on the underneath.So, I was force to desolder again the module but this time I socketed it using a 64 pin SDIP (shrink DIP) socket divided in two stripes for an easy future maintenance:

S-DIP_socket_combined

After desoldering it, I found this scenario:

100_5291

In particular there is a QFP Konami ASIC marked ‘054321’ (probably a MCU which controls the entire sound system, infact if you run the PCB without it the RAM/ROM test will show error on all related sound components -RAM, ROM, 74LS245 and ASIC ‘054539’).Besides there are also a JRC4558 OP-AMP (LM358 compatible) and a AD1868R (Dual 18-Bit Audio DAC), all in SMD package.

Judging from the issue  I started to suspect about the 4558 OP-AMP.So, I borrowed one from a faulty PCB. After a quick soldering  I turned on the PCB again and..the sound was back, crystal clear as it should be.Mission accomplished.

 Posted by at 8:03 pm

Raiden II repair log

 PCB Repair Logs, Repair Logs  Comments Off on Raiden II repair log
May 032014
 

Got a cheap Raiden II (set 4, Italy revision) PCB recently:

Seller claimed PCB had a video SYNC issue so I fired up it sure of the scenario I was going to face :

There was no SYNC at all (measured 549Hz on pin13 solderside of JAMMA edge) but the thing that made ​​me suspicious was that there was no activity on address/data bus of CPU (NEC V30) and program ROMs like the system never got initialized.

So, as usual, I start my visual inspection and found this:

If the missing capacitor  (which filters the +12V for the LA4460 audio amplifier) was not the cause of the issue for sure, I thought the broken track would have been the culprit but  I was wrong since, once restored, I got the same rolling screen above.

PCB has few common ICs (74LS245 and SRAM mainly) but a sufficient number of ASICs so I consulted the MAME source which is like a bible for every arcade repairer since it’s a an inexhaustible source of hardware information.And I found that among the various ASICs, the one marked ‘SEI1000 SB01-001’ is responsible of the main protection, this would have explained why the PCB didn’t boot at all:

Its package was a 184 pin QFP with a fine pitch as you can see from picture.Armed with a small needle I started to test the tightness of each pin and found that almost half of them got detached from the pads when I gave force.So, it was time for a reflow at 390° with my hot air station which I had to repeat 4-5 times plus some final passes with the tip of the soldering iron to get a good result.

Powered up again and :

SUCCESS!Another PCB saved from the trash and a very good vertical shoot ’em up!

 Posted by at 4:15 pm