(Topic ID: 324399)

TAF - F115 blown. MPU to blame - but where.

By Igwiz

5 months ago


Topic Heartbeat

Topic Stats

  • 27 posts
  • 7 Pinsiders participating
  • Latest reply 5 months ago by Igwiz
  • No one calls this topic a favorite

You

Linked Games

Topic Gallery

View topic image gallery

20221024_172915 (resized).jpg
20221023_173601 (resized).jpg
20221023_173615 (resized).jpg

#1 5 months ago

Hi all,

So I was a naughty boy and was fiddling with a non-working pop bumber on my TAF with the machine on and blew out F115. Disconnecting J114 the fuse stays ok so that led me to the MPU. I checked the 4 LM339 using a multimeter (red on ground, black on each leg) and each one was short on the vcc leg. That isn't good right?
I also checked the ULN2803a and this was also short on the vcc and also had a diode voltage drop reading of only 0.06 on leg 16 (I think). The fuse remains ok with the 2803 removed.

Is it possible that I took out all the chips even though the fuse holds with just the 2803 removed? Does all that make logical sense?

Would be grateful for any pointers. Really annoyed as it was working nicely!!!

Many thanks,
Ig

P.S. Also, when I buy a replacement for the ULN, I can't see that there is any difference between a 2803a and a 2803. Could someone kindly confirm if they are exactly interchangeable? Many thanks.

#2 5 months ago
Quoted from Igwiz:

Hi all,
So I was a naughty boy and was fiddling with a non-working pop bumber on my TAF with the machine on and blew out F115. Disconnecting J114 the fuse stays ok so that led me to the MPU. I checked the 4 LM339 using a multimeter (red on ground, black on each leg) and each one was short on the vcc leg. That isn't good right?
I also checked the ULN2803a and this was also short on the vcc and also had a diode voltage drop reading of only 0.06 on leg 16 (I think). The fuse remains ok with the 2803 removed.
Is it possible that I took out all the chips even though the fuse holds with just the 2803 removed? Does all that make logical sense?
Would be grateful for any pointers. Really annoyed as it was working nicely!!!
Many thanks,
Ig
P.S. Also, when I buy a replacement for the ULN, I can't see that there is any difference between a 2803a and a 2803. Could someone kindly confirm if they are exactly interchangeable? Many thanks.

You are right, Vcc and ground pins on a chip should not be shorted.

That said, if you are testing in-circuit, you might be reading a short that's actually elsewhere. Like, the ULN2803A you checked. Or even something you haven't looked at yet. The Vcc and the ground for each LM339 are probably directly connected to the Vcc and ground for other chips on the same board. Did you test the LM339 chips while the ULN2803A was still installed? Did you pull the LM339 chips before testing?

As for the ULN2803 vs ULN2803A question, I don't really know. However, TI's web site says the ULN2803A is obsolete and they only have the ULN2803C now. I suspect that the letter is a revision code and that the parts are indeed interchangeable. If you are looking at a different manufacturer's product, I'd guess they don't have multiple revisions of that chip the way TI does.

#3 5 months ago

Thanks Pete! Yep, I foolishly didn't recheck the LM339 chips after pulling the 2803. Looks like the are actually fine which is good news given they are soldered whereas the 2803 was socketed. Thanks also for the confirm on the 2803 spec. Hopefully a new one in the socket will get me back and running. Just as a precaution, is there anything I should check before turning back on that might still cause the 2803 to short again. I would rather not burn through my limited 3/4 amp fuses! I am not really sure what specific action of me fiddling with the bumper switch leaves was the offending one!

Many thanks!

#4 5 months ago
Quoted from Igwiz:

I am not really sure what specific action of me fiddling with the bumper switch leaves was the offending one!

Somehow managed to short more power to the switch matrix.

If you aren't in there fiddeling with it again with power on. I'd try once more. Not likely you did permanent around the pop bumper. Just the jolt to the board.

LTG : )

#5 5 months ago

as crazy as it sounds I was adjusting a switch on a wcs a couple years ago. Had the game off and adjusted the switch . Problem was driver board caps hadn't discharged yet fully.took out the 2803

#6 5 months ago

Thanks guys. So the good news is a new 2803 has worked and now the games boots etc. Super. But then the agony. I am guessing that the jolt to the board took out more than the 2803. The switch for the thing/skillshot hole has gone and the bookcase won't stop turning so game remains unplayable. So two questions if I may: 1/ does it makes sense these are a direct result of what also caused the 2803 to go? 2/ what switch/sensor is causing the bookcase to not stop moving? Test report mentioned Thing Opto and Opto limits but not the thing hole switch. I also know I have a switch out on a ramp and in the swamp lock and oddly those are not reporting as at fault.

Grateful as always...

Ig

#7 5 months ago

If it's reporting optos as bad, check the opto board power (any other fuses blown?)

The game 'knows' when optos are out because they are normally closed switches, that the ball breaks the beam when present. So it can mark those as bad right away. 'Normal' switches (mechanical microswitches or leaf switches) are not marked as closed for a certain # of balls, or if there is more than one switch that logically has to activate before another; if the game sees the second switch but not the first consistently, it will mark the first as bad. (This type of switch is often costed out of a game as the software can logically assume its function)

#8 5 months ago

Ok, slochar, I will check the opto board but I imagine it will be ok as the bookcase opto switches are registering ok on the switch edges test. Will revert.

#9 5 months ago

Ok. So opto board looks fine. Led1 comes on and, as i say, bookcase greed optos working. Ran the Thing Test and Bookcase Test and this might be the issue (see photos). Surely one and only one box should be checked in each of those? I am guessing it is no coincidence that the Bookcase Open/Close and Thing Optos are on column 8 of the matrix...... What's my next step!?

Grateful as always....

20221023_173601 (resized).jpg20221023_173615 (resized).jpg
#10 5 months ago
Quoted from Igwiz:

I am guessing it is no coincidence that the Bookcase Open/Close and Thing Optos are on column 8 of the matrix...... What's my next step!?

https://www.pinwiki.com/wiki/index.php/Williams_WPC#Opto_Testing

#11 5 months ago

Oh man! I should know better than to try and do anything on a Sunday evening! Have now screwed it up further. Was testing the opto board, saw smoke coming from somewhere (can be sure where) and so turned it off. Now the Led1 on the opto board is out and the bookcase greed optos have gone!

#12 5 months ago

Slotted optos are not controlled by the 7-opto board as opto pairs. The slotted optos are placed directly on the switch matrix.

Once you fix the +12VU issue that you appear to have, take the balls out of the game and post an image of the 8x8 matrix shown on the dot matrix display when in T.1 Switch Edges.

#13 5 months ago
Quoted from Igwiz:

Now the Led1 on the opto board is out and the bookcase greed optos have gone!

Test the fuse in the top left corner of the power driver board.

#14 5 months ago

Ok, 12vu repaired (had blown the F116!) Phew.

Here's a picture of the T1 display. Clearly shows the column 5 bookcase switches out (if I am reading it right). So now do I follow the circuit from that column and hope to find a blown transistor or similar or does something else I'm not thinking about cause this...? I haven't shorted the row/column pins yet to see if they trigger but will do that later if appropriate.

Grateful as always...

20221024_172915 (resized).jpg
#15 5 months ago

Optos are normally closed so that column of five boxes shows that all five are reading. Put your finger in front of the optos and see if they change state.

You can also use switch levels test which will scroll through and tell you all the switches the game sees as closed.

#16 5 months ago
Quoted from Igwiz:

Here's a picture of the T1 display.

You still have two balls in the trough. Take them out. They only add a variable to the equation that's not necessary.

  1. SW32 is "Upper Right Jet" and closed. This is a spoon switch. Check the switch leaves.
  2. SW81 is "Bookcase Open" and SW82 is "Bookcase Closed". One of these should closed but neither of them are. The interrupter cannot be interrupting both slotted optos at the same time. There is something wrong here.
  3. SW84 is "Thing Down Opto" and SW85 is "Thing Up Opto". Same deal here as with the bookcase slotted optos. The interrupter cannot be interrupting both slotted optos at the same time.
Quoted from Igwiz:

So now do I follow the circuit from that column and hope to find a blown transistor or similar or does something else I'm not thinking about cause this...?

The switch matrix only has (Darlington) drive transistors in the ULN2803A.

Quoted from Igwiz:

I haven't shorted the row/column pins yet to see if they trigger but will do that later if appropriate.

Here are some tests that you can do to help differentiate possible causes and locations.

  1. Short (jump) J206-9 with any/all pins on J208 on the CPU board and see if the switches register.
  2. In T.1 press SW86 "Grave 'A'" and see if it registers.
  3. In T.1 press SW87 "Thing Eject Hole" and see if it registers.
  • If the "jump" test on the CPU board passes there the problem is in the connector or the playfield wiring. If it fails you will need to repair this problem yourself or send the board out for repair.
  • If SW86 and SW87 register then check the bookcase slotted opto board and the thing slotted opto board wiring. Check for the presence of power (+12VU) at the GRY-YEL wire and continuity with the switch matrix harness wires.
  • If SW86 and SW87 do not register check the switch matrix harness wires looking for a break.

If you are unsure post images of the switch wiring and the slotted opto boards.

#17 5 months ago
Quoted from DumbAss:

You still have two balls in the trough. Take them out. They only add a variable to the equation that's not necessary.

SW32 is "Upper Right Jet" and closed. This is a spoon switch. Check the switch leaves.
SW81 is "Bookcase Open" and SW82 is "Bookcase Closed". One of these should closed but neither of them are. The interrupter cannot be interrupting both slotted optos at the same time. There is something wrong here.
SW84 is "Thing Down Opto" and SW85 is "Thing Up Opto". Same deal here as with the bookcase slotted optos. The interrupter cannot be interrupting both slotted optos at the same time.

Yep, that all makes sense and agrees with what I posted in post #9. This is indeed odd. The Upper right jet is the one that a fiddled with that set this whole set of screw ups in motion! (Shoved a rag in the ball shoot being lazy!)

Quoted from DumbAss:

Here are some tests that you can do to help differentiate possible causes and locations.

Short (jump) J206-9 with any/all pins on J208 on the CPU board and see if the switches register.
In T.1 press SW86 "Grave 'A'" and see if it registers.
In T.1 press SW87 "Thing Eject Hole" and see if it registers.

If the "jump" test on the CPU board passes there the problem is in the connector or the playfield wiring. If it fails you will need to repair this problem yourself or send the board out for repair.
If SW86 and SW87 register then check the bookcase slotted opto board and the thing slotted opto board wiring. Check for the presence of power (+12VU) at the GRY-YEL wire and continuity with the switch matrix harness wires.
If SW86 and SW87 do not register check the switch matrix harness wires looking for a break.

If you are unsure post images of the switch wiring and the slotted opto boards.

OK, I already know the Grave A and the Thing Eject do NOT register - Is that a clue? Was surprised at the "A" when testing everything yesterday. How is that connected to the root issue?

I will try jump tests tomorrow evening. Thanks. Bringing it all back to the original cause that I blew out the 2803 on the MPU fiddling with the bumper, I would be surprised if it was a wire break issue. I hold hope with the +12vu being dodgy still. Will revert once I have tested.

Thanks as always. I really am very grateful for the time you guys spend helping us.

#18 5 months ago
Quoted from Igwiz:

OK, I already know the Grave A and the Thing Eject do NOT register - Is that a clue? Was surprised at the "A" when testing everything yesterday. How is that connected to the root issue?

Those two switches are also in column 8. Your report indicates that all the switches in column 8 are out (2x bookcase, 2x thing, A and eject, 2x unused). This points to a more central reason rather than a peripheral reason. To differentiate the board versus the wiring you need to do the "jump" test. Once you have the results from that you will know where to look.

If you don't do this test, you could be looking in the playfield wiring for a problem that does not exist (because the problem is on the CPU board).

If the problem ends up being isolated to the CPU board AND you installed a brand new ULN2803A, it could be that the initial event that caused damage to the old ULN2803A caused further damage upstream to the 74LS374.

These are reasons why you need to do the investigation rather than shotgun (not saying that you are doing this but I have seen many examples of people who use the shotgun method on this forum).

#19 5 months ago
Quoted from DumbAss:

These are reasons why you need to do the investigation rather than shotgun (not saying that you are doing this but I have seen many examples of people who use the shotgun method on this forum).

Totally agree and am doing this step by step following the great advice. Learning and understanding along the way which is even better! Will revert once I have had a chance to do the jump tests.

Many thanks.

#20 5 months ago

Okey doke. So I ran the jump test ( I assume the J206 and J208 shouldn't have connectors on them (because mine don't!) and are just run throughs for J207 and J209. That's what the schematic looks like)

What I get is hopefully a good clue to what is going on. I short the J206-9 to each pin on the J208. 1 and 9 do nothing. The others each "open" the boxes in column 5 on the switch test matrix. BUT also a couple cause other "boxes" to close. In particular, pin 2 causes the Jet bumper at 33 and 35 to fire. Does that mean I have someting going wrong in the wiring near the bumpers?

#21 5 months ago

Jump test should be without any connectors. That way anything on the playfield can't interfere.

#22 5 months ago
Quoted from slochar:

Jump test should be without any connectors. That way anything on the playfield can't interfere.

Sure, I appreciate that. What I meant was that the connectors pins have no connector "plugs" associated with them on this particular board.

#23 5 months ago

OMG guys, I may have been wasting your time since post #6. I just took the approach to re-check what I did to fix the original probelm before the new issues then started. So I checked the seating of the new 2803 and found I had bent a leg on insertion. So stupid!!!! Sorted that out and now the bookcase and thing eject hole are working again. Still got an issue on the Thing Opto and a couple of other switches but that is for another day.

Thanks and apologies in equal measure!

#24 5 months ago
Quoted from Igwiz:

OMG guys, I may have been wasting your time since post #6. I just took the approach to re-check what I did to fix the original probelm before the new issues then started. So I checked the seating of the new 2803 and found I had bent a leg on insertion. So stupid!!!! Sorted that out and now the bookcase and thing eject hole are working again. Still got an issue on the Thing Opto and a couple of other switches but that is for another day.
Thanks and apologies in equal measure!

lol...well, these things happen. I'm just glad you figured it out, and that it wasn't anything major!

And I'll bet you're a lot more careful next time you have to seat an IC. So, great learning experience!

#25 5 months ago

Very much so Pete!

Infuriatingly, although everything is back to how it should be and playing/registering properly, the thing eject hole solenoid is now failing to push the ball out of the hole. It fires but the ball doesn't get over the lip. Never used to be a problem at all. Was there perhaps a little "seat" the ball sat in to give it a little height over the edge that may have dislodged? I can't see anything that has fallen under the playfield. Would be a very strange coincidence if suddenly the solenoid wan't nw receiving enough power. All the others seem to be punching their weight when I run the solenoid tests.... Grrr.

#26 5 months ago
Quoted from Igwiz:

Very much so Pete!
Infuriatingly, although everything is back to how it should be and playing/registering properly, the thing eject hole solenoid is now failing to push the ball out of the hole. It fires but the ball doesn't get over the lip. Never used to be a problem at all. Was there perhaps a little "seat" the ball sat in to give it a little height over the edge that may have dislodged? I can't see anything that has fallen under the playfield. Would be a very strange coincidence if suddenly the solenoid wan't nw receiving enough power. All the others seem to be punching their weight when I run the solenoid tests.... Grrr.

There's not any extra part on my machine. Just bare playfield.

I would look for the usual "weak solenoid" suspects. Given the possible handling that's been going on under the playfield, I'd guess things like a dirty EOS switch or broken wires either on the EOS switch or maybe one of the coil terminals is a possibility. Obviously do a manual check to make sure the solenoid itself is moving smoothly, not getting hung up on anything. Make sure no loose part or debris has gotten stuck in the coil anywhere. That sort of thing.

#27 5 months ago

Checked the voltages - fine. Took the solenoid off the playfield - looked fine. Fired it while off the playfield - looked like it was fully extended so fine. Put it back -same behaviour. Then I thought, hmm, I've moved the table a bit to get to the back so maybe it's off level - put a beermat under the back leg and that was enough to help the ball on its merry way! Oh the joys! Now playable again. Yay. I will level the whole machine properly when I have finished the last few switch repairs I need to do!

Promoted items from the Pinside Marketplace
$ 38.00
Various Novelties
Pinball Photos LLC
Various novelties
$ 399.95
Lighting - Led
Pin Stadium Pinball Mods
Led
$ 79.00
Lighting - Under Cabinet
Arcade Upkeep
Under cabinet
$ 26.99
Playfield - Other
Lee's Parts
Other

Reply

Wanna join the discussion? Please sign in to reply to this topic.

Hey there! Welcome to Pinside!

Donate to Pinside

Great to see you're enjoying Pinside! Did you know Pinside is able to run without any 3rd-party banners or ads, thanks to the support from our visitors? Please consider a donation to Pinside and get anext to your username to show for it! Or better yet, subscribe to Pinside+!


This page was printed from https://pinside.com/pinball/forum/topic/taf-f115-blown-mpu-to-blame and we tried optimising it for printing. Some page elements may have been deliberately hidden.

Scan the QR code on the left to jump to the URL this document was printed from.