Difference between revisions of "PCB Repair Logs 1943"
(Created page with "==1943== <p><table class="infobox vevent" style="width:22em;" cellspacing="5"> <caption class="summary" style=""><b>1943</b></caption> <tr class="> <td colspan="2" class="" st...") |
m |
||
(2 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
<tr class="> | <tr class="> | ||
<td colspan="2" class="" style="text-align:center;">[[Image:marquee_1943.jpg|200px]]</td> | <td colspan="2" class="" style="text-align:center;">[[Image:marquee_1943.jpg|200px]]</td> | ||
</tr> | |||
<tr class=""> | |||
<th scope="row" style="text-align:left; white-space: nowrap;">Manufacturer</th> | |||
<td class="" style="">[[PCB_Manufacturers_Capcom|Capcom]]</td> | |||
</tr> | |||
<tr class=""> | |||
<th scope="row" style="text-align:left; white-space: nowrap;">Year</th> | |||
<td class="" style="">1987</td> | |||
</tr> | </tr> | ||
<tr class=""> | <tr class=""> | ||
Line 11: | Line 19: | ||
<tr class=""> | <tr class=""> | ||
<th scope="row" style="text-align:left; white-space: nowrap;">Pin Out</th> | <th scope="row" style="text-align:left; white-space: nowrap;">Pin Out</th> | ||
<td class="" style=""> | <td class="" style="">[http://wiki.aussiearcade.com.au/index.php/File:Jamma_pinout.png Jamma Pinout]</td> | ||
</tr> | </tr> | ||
Latest revision as of 14:03, 4 February 2013
1943
Manufacturer | Capcom |
---|---|
Year | 1987 |
PCB Image | 1943 PCB |
Pin Out | Jamma Pinout |
Repairer: Womble
Forum Thread: 1943 PCB Repair
Another Womble ramble I am afraid...
Now that I have a vertical cab I need to assign it an identity artwork wise, and I have very fond memories of playing 1943 as a kid. There's something about the drone of the engines as you loop the loop that is just very 1980s-arcadey.
So I snapped up a faulty Capcom 1943 board listed on the ebay UK recently, cost more to ship than it cost to buy but still cheaper than a working board locally all up I think.
Buying borked boards is always risky as you never know how the board died, it might be fixable or it might be a total wreck. The seller of this board claimed it was a permanent fixture in his mates cabinet, and that they played it incessantly during the summer, but when powering up after a few months off all they got was a blue screen. They took the board to the other guys house and tried it in his cab and got the same deal. At this point they decided to sell it rather than fluff around with it, as they knew they wouldnt be able to do much with it - these guys deserve a medal for that way of thinking. Assuming the seller was telling the truth and that it died inside the cab, there should be no chance the board had been plugged in backwards, so I took the punt.
It turned out that getting a blue screen is a bit hit and miss and the blue screen is actually the background seascape rather than just a blank blue screen. Powering on and off gives you about 5 different screens of crap
1) Alpha-numeric crap - classic Z80 in distress.
2) Blue seascape with or without music.
3) Repeating pattern of large blocks of ocean wave graphics - assume its part of the tsunami.
5) Black screen with fragment of plane and explosions dotted about 6) Black screen.
Oddly enough hitting the coinup button will often cycle through the above, and or stop the music.
Certain AA members will be glad to hear I have finally sorted out my playroom and my 100Mhz Dual Channel CRO now has a permanent place of honour, after having spent the last 9 months in a cupboard coz its about twice the size I thought it was when I was bidding for it.
Having dumped and verified the ROMs, (a doubely good 1st test as it reseats every Eprom too) I moved onto the second most likely culprit (after power), the RAM. This board has 3 types of RAM, across the two boards. As is fairly standard, 1 board houses the CPUs, game code ROMs, sound system, and clock generation chippery, the other is the Video board which handles the video generation, sprites and graphicsy stuff. As the music could play I was pretty sure I could rule out the sound system and the graphics fragments I could get looked nice and clean, that just left the main system RAM at 10D. Also as they were socketed I was able to test the two Z80 chips in my Galaxians board and prove they worked.
Normally I would just work using a logic probe, in this case the right pins on the SRAM were active, the chip was not in standby and the control lines were busy. Looking at the activity with the scope it showed the control lines (WR and OE) were active and healthy. The address lines were also nice and healthy - healthy as in the voltage levels were transitioning pretty cleanly from logic 0 to logic 1. However the data lines (i.e. the output) were a mess on half of the pins, a number of the pulses were more like spikes and barely reached half way between the two logic states.
.. and fitted a couple of 14pin machined pin sockets side by side to take the 28 pin slim M8464 chip which is pin for pin compatible with the original TMM2063 (cheaper than buying 28 pin sockets).
The original chip failed the RAM test on my eprom burner miserably, it detected that a number of pins were unwell before it even tried the write/read tests.
Slapped in the salvaged M8464 SRAM chip, powered up the board and it booted happily.
The only thing wrong was the sound, everything bar the chip tune was missing. I briefly heard the shot noises very very faintly but that stopped pretty quickly.
Back on the test bench and looking at the board there are two Y2203 sound generators, feeding two YM3014 DACs which feed into the amp section. Hooked up my audio probe to the output of both DACs, the one at 2B was happily pumping out the chip tune, the one at 2C was giving out silence. Probing the input signals to the DAC showed 2C was getting no inputs. Tracked back to the Y2033 and some inputs were active and others not. In the end it was simpler to desolder it, fit a 40 pin socket and drop in a spare YM2203. This brought back all the shot sounds and some of the background noises, but not the classic 1943 drone sound effect, or any of the explosion noises.
At this stage I don't know if either of the two YM2203 chips are in perfect health, the sound effects that are missing are too complicated to be generated by any of the TTL logic in the sound section I would assume so perhaps one of the YM2203s is only half well.
So I reckon that the seller's story checks out - the board could well have just died in its sleep, the YM2203 chip probably died here as I just heard its last gasps. Need to put some more time into the remaining sound issue, but have run out of weekend! It plays well tho, she's definitely a keeper.