Robocop repair log #1

 PCB Repair Logs, Repair Logs  Comments Off on Robocop repair log #1
Jun 152011
 

Bought a Robocop board from the AO forums. Seller says the jump button didn’t work.
Doing a visual inspection revealed a burnt out track just off pin 23 on the edge connector, which is button 2, in this case, the jump button.

image

I repaired the trace but still no joy with getting the controls back.
Further inspection showed that the custom resistor array had burnt out. This resistor array has some modified characteristics compared a normal array, it passes an input out to a different pin and has a few other differences too. As I don’t have any spares of the custom array I decided to use a standard one pulled from a scrap board.

image

To make this work I had to short pins 6 and 7 together and 8 and 9 together. These are for button 1 and button 2.
The board is now fully working but ill keep an eye out for an original replacement part to fit.

Commodore 64c repair log

 Computer Repair Logs, Repair Logs  Comments Off on Commodore 64c repair log
May 282011
 

The data cassette player would not power up and there was no sound outputted.
There is a big 1.5A fuse inside labelled F1. This supplies the +9v to pin 28 of the SID chip and is also used in powering the cassette unit.
Replacing this fuse brought everything back to life.

The C64c boots up fine without this fuse. I have been using an SD2IEC adapter to load games and didn’t realise at the time that the cassette unit was not working either.

Amiga Apollo 1230 expansion card repair log

 Computer Repair Logs, Repair Logs  Comments Off on Amiga Apollo 1230 expansion card repair log
May 272011
 

My good mate Andy over at RCM gave me his 1230 MK2 expansion card to have a look at last time I was there. The problem was the PLCC socket on the FPU was cracked at one corner.


I did manage to confirm this was the problem by holding the socket together so I ordered some socket from China and removed the old socket
The old one came off easy enough with a hot air gun.

The sockets came and I set about fitting it. I decided to use solder paste as it makes the job quite a bit easier when soldering surface mount things with many pins.
5 or so minutes later the new socket was on and after a quick check under the magnifying glass it was time for a test run.

Workbench reported the extra RAM and my 1200 was now a flying machine so im happy its working. Tried Scorched Tanks to make sure, its the only game that was on the compact flash drive!

Rastan repair log #1

 PCB Repair Logs, Repair Logs  Comments Off on Rastan repair log #1
May 022011
 

Very nearly gave up with this one thinking it was a custom IC fault, glad I never.

Was sold this board as a non worker, the guy said it boots to a white screen and the CPU needed to be looked at.
He was right on both counts.

image
image

Before I did anything that CPU needed socketed. Once I had done that I fired the board up again but got the same white screen. I checked the data lines of the CPU and they were dead. I initially tried a known good 68000 CPU but this resulted in the same screen.
There are 6 ROMs next to the CPU which are the program ROMs. I pulled all these and checked them against MAME. The first 3 checked were fine the last 3 were actually from an Operation Wolf board and 2 of those were dead anyway. Burned 3 replacement 27c512 EPROMs and tested again.
This time I got a white screen with some garbage on.
After this I plugged in the Fluke 9010 and ran some ROM and RAM tests. The ROMs passed fine but one of the RAMs had failed. The TMM2063 @ IC10 was shot, I used a D4364 as replacement as its the first one I found compatible on a scrap board.
Board still booted with garbage.

image

All lines on the CPU had frozen.
Checking the game running in MAME I could see that when you first boot the game the whole screen flashes white for a second then the game boots.
I checked the 3 Interrupt line, IP0, 1 and 2, and found that IPL1 was dead, this came from a nearby PAL @ IC36. The PAL was giving an output so I ran a jumper wire to the CPU and booted again.
This time I got a full white screen with the Hi Score at the top and the game ran but only showing the sprite data.

image
image

I checked all the ROMs that hold the background data and they all checked out fine. These are MASKROMs and can be read as either 27c301 or a couple of reads as 27c512 with a small modification.
Following the data route from these ROMs I eventually came to a 74LS157 @ IC72. It had dead pins at #3 and #11. Pin 3 should go straight to +5v and pin 11 should come from address bus A10. Ran a couple of jumpers for these and got something a little different, the screen was still mainly white but I could see text underneath it and the sprite colours were now messed up.

image
image

Looking underneath the board I found a discoloured track, when I ran the screwdriver over it, it came away from the board looking a little charred.

image

Only a short jumper required but it was underneath the palette RAM. I started checking the palette RAM and found pin 16 was dead. I removed this 2018 RAM @ IC73 and it tested faulty, replacing this with a 6116 brought the graphics back fully.

Mortal Kombat repair log

 PCB Repair Logs, Repair Logs  Comments Off on Mortal Kombat repair log
Apr 292011
 

Simple repair.
The controls were erratic. Using the input test in the diagnostic menu I could see 3 buttons and the right direction were being activated together.
A visual inspection quickly pinpointed the fault. One of the input resistor banks was partially desoldered and cracked.

Trying to remove the IC myself proved quite a task but removed the two parts and slotted in a 4.7k resistor array from a scrap board. Now the inputs work fine.
Just need to find a sound board for it now.