Moon Patrol PCB Repair
Moon Patrol December 20th, 2007Greetings earthlings! This post is a continuation of this mess. Basically, when I first got my Moon Patrol cabinet, I got a PCB along with it. That PCB had some major issues which I tried to fix. I got nowhere with it, and decided to just buy a working one. I’ve had the old dead board sitting here and figured I would take another crack at fixing it for fun.
Before this round of screwing with it, one of the things that was most noticeably wrong with it can be seen here:
That should read BEGINNER COURSE GO! Half the letters are incorrect. In diagnostics mode, there was a RAM error, but it was difficult to read because of the character problem. I’ll try not to bore you too much, but here’s what I did for this round…
Moon Patrol is a 4 PCB stack. Now that I have a working set, I figured I could use it to isolate the problem to a particular board in the stack. I swapped each board from the bad stack into the good stack one by one, powering it on in between to see if the problem would follow. Doing this lead me to figuring out that the main CPU board, #2 in the stack, was the one with the problem.
With that out of the way, I noticed in the manual that if you don’t have any characters on screen at all, the ROM inĀ 3F on the scrolling video board is bad. I swapped it with a good one, and the problem was still there. I guessed that maybe something connected to 3F was bad, and if I remember correctly, I traced 5M on the CPU board back to that chip. It’s a logic chip - 74LS245. I searched the RGVAC newsgroup for this chip, and many people were reporting that they fail pretty often in a lot of games. I then did a test I learned from Randy Fromm on that chip, checking each pin to see if any were out of wack. The basic idea is you put your meter on the diode test setting, put the red lead on ground, and probe each pin on the IC. All pins on the chip except for ground and Vcc (+5v) should read around .5 to .9. Anything way lower (like .004, for example) or way higher is probably bad. You can then compare any suspect pins to another of the same chip on the board if there is one. I did my comparison to the same chip on the working board. I found that pin 18 read .002, and was shorted to ground. I thought this was pretty cool, because I really am clueless with this stuff.
So, I removed 5M, put a socket in, and replaced the chip. With the old chip out, I tested it again. While pin 18 still read wrong, the short was not there. The short was actually on the board somewhere else. I went over every single trace on the board visually looking for problems, hoping to find the short that way. While doing this, I spotted this on the chip in 1K!
That is definitely wrong. I checked the same chip on the working board and it wasn’t intentionally not soldered. So, I removed that chip, bent the pin back, put a socket in and popped it back in. I still had that pesky short however. I read through the schematics, and wrote down every thing that was in circuit with 5M pin 18. That gave me a list of about 6 or 7 chips. I figured I could test them one by one, but the fastest way was to clip pins on the chips in question. I had replacements for them, so I started clipping hoping I would get lucky. I found the suspect chip at 1D. Pin 8 was shorted to ground. I replaced that chip and the short was gone. In the process of finding the short, I clipped pins on 3 other chips so I changed those as well.
BOY this is long and boring.
Anyways, after all that, I hooked it back up and the character problem was solved. The board still has issues however. It keeps resetting, the tank is missing sometimes, and the background looks a bit weird. In diagnostics mode it says RAM NG 8000, which according to the manual means RAM 3C on the scrolling video. board is bad. I know that’s not the case because I had already changed that RAM prior to this, so I have no clue what’s causing it. I’m taking another break from this board but maybe I’ll get back to it in the future.


December 20th, 2007 at 2:02 pm
Man 4 pcbs? And I thought galaga was bad with two ;). I’m sure you probably thought of this, but could it be that the socket for the RAM at 3C is faulty? If it is a socketed chip and not soldered to the board maybe replace it with a new dual wipe socket?
December 20th, 2007 at 2:54 pm
Yeah, 4 is hard to deal with. It makes fixing it more time consuming because I have to keep taking it apart and putting it back together.
I actually replaced the RAM in 3C before, and when I did I put a machine socket in. I’m probably going to change it again just in case the new one is bad, but I’m not planning on messing with this for awhile…maybe after the holidays.
April 28th, 2008 at 9:56 pm
Hello,
I have been reading you blog with great interest (not as boring as you thought huh). I am also trying to fix my Moon Patrol board-set. Like you I’m not a genius at electronics, but I’ve fixed many boards through simple logic and sheer persistence.
I too have a repair site:
http://web.mac.com/lord_philip/Arcade/Moon_Patrol.html
…although it looks like our problems are different.
If you have any advice I’d love to hear it. I don’t have the manual, so that makes things much more difficult
Anyway, good luck.
P
May 1st, 2008 at 9:59 am
Hey Phil,
Thanks for commenting! Sorry it took so long to approve your comment. I’ve been swamped with my real job and have been neglecting my site the past couple of weeks.
Glad you like my site.
I am really clueless with this stuff, but if it were me I’d go after fixing that ROM error you have. Maybe it has something to do with it?
I linked to you, btw. —>
May 5th, 2008 at 5:56 am
Hi, me again,
I’m still battling away with the board when I find a few spare moments. Any more luck with yours?
I don’t suppose you know what the error codes mean?
I sometimes get the following errors:
RAM NG :E000 55 A3
ROM0 NG FC
ROM1 OK FF
ROM2 OK FF
ROM3 OK FF
Thanks again
May 5th, 2008 at 9:04 am
Hey Phil,
I haven’t touched my Moon Patrol PCB in a long time. I ended up buying a working one awhile back, and might try and fix my broken one again at some point.
If you need it, the manual and schematics are here in 2 separate files:
http://arcarc.xmission.com/PDF_Arcade_Williams/
Checkout page 5 of the manual. It has info on the RAM test. That should tell you where to start looking to fix that RAM error. Good luck…hope you fix it!
May 8th, 2008 at 6:00 pm
Thanks Jamie,
The manuals helped a lot. I reburnt ROM 0 and replaced the 6116 RAM, Now I get no errors in test mode. The game still does not start, but it now shows the blue score area along with a bunch of garbage (often the image can’t decide if its flipped or not). when initially turn on in test mode there are a few nebulous graphics on the screen (an explosion, blocks etc) that stay there through the scrolling test. I’m sure these are not supposed to be there. They disappear once the ROM and RAM report is displayed. Anyway, progress. I’ll post a quicktime on my page.
May 10th, 2008 at 5:07 am
Hi Jamie,
Nice to finally have a chance to chat yesterday.
So I have good news, I fixed my Moon Patrol! It seems that the onscreen ROM test can not be completely believed. After a few hours of prodding and probing I finally decided to burn a complete set on ROMs. That fixed it right up. Maybe this is something to think about on your boardset. Thanks for all your help. Phil
May 11th, 2008 at 10:05 am
Hey Phil,
That’s great! Glad you got it working. I *think* I swapped all the ROMs from my working board into the non working board and it didn’t help my problem. I haven’t burned any ROMs yet. Could you recommend a good burner?
May 11th, 2008 at 10:17 am
I got a Needham EMP20 from ebay for about $60:
http://www.maxipub.com/electro/specs/needham_emp20.jpg
I did a bunch of research before deciding on this one. Firstly it was cheap(ish) and it also burns a wide variety of EPROMs, including of course 27XX’s and also 2532’s which many burners have difficulty with.
There is an Needham EMP11 on ebay now, but I’m not sure what the difference is between the models.
May 11th, 2008 at 10:58 am
Thanks for the info. I’ll grab one of these at some point.