Testing 4116 mem chips

invadarr

User
Credits
52CR
I am repairing some cosmic alien boards using the ABI System 8 BFL and I cannot find a way to test the 4116 Memory chips I have put a BDO (green) on the Xtal to stop the clk inputs and have done the same to the Reset on pin 26 of the Z80 cpu but cannot get a pass for the mem chips.

What am I doing wrong?

Is there another way of testing these chips on the board to see if any are bad as they are all soldered in place I want to find a way to test them without having to Desolder them all.

I have a problem with the same chips on a Defender board Chip No 1 was cracked across the top as if it had been Blown by a voltage fault ,again i do not want to desolder all the chips to see how many have been affected.

Any help would be most appreciated

Thanks invadar
 

cliff_poole

Active member
vacBacker
Feedback
6 (100%)
Credits
1,069CR
I don't think I have any answers but what are the failures you are seeing ?, is it the same for all chips ?. I'm wondering if there is a bus fault that the ABI can't get around.

I used to fix ZX Spectrums before I had any fancy equipment. The circuit that supplied the -5V and +12V to the 8 4116s was always on the ragged edge and would blow a transistor with the slightest short. It is a bit brutal, but I used to snip and lift all the -5V and +12V legs on the 4116s, then test them with a multimeter diode test. Most of the time I'd end up having to replace the lot anyway.

I have been considering making a little 4116 adapter pod for the ABI that generates a -5V and +12V from the 5V line so that I can test them out of circuit. The ABI PSU doesn't have a -5V line, not sure if it supplies 12V to the test socket either.
 

invadarr

User
Credits
52CR
Hi Mes,
Thanks for your reply I'm not sure how to reply, Take the Defender board for example

I have one chip that is cracked due I suspect to a voltage problem, I have of course replaced that chip

But still have a mem problem, Now I don't relish having to unsolder all the rest of the 4116 chips to replace the chips, if they are not all bad.

I had two thoughts about the problem First how would the professional repairers go about this problem, being self taught I wondered if there was a trick I was missing or do they have to replace the chips one at a time testing the board after each replacement.

Or do they use another piece of Test equipment that they use to test each chip in circuit which can immediately tell which chip is bad.

On the subject of making a Pod for the ABI would that not be dangerous? to apply -5v and +12volts to the board under test as the test clip on the ABI can be attached to the chip in any orientation thus the danger of putting the the test clip on the mem chip in the wrong position.

In the menu of chips supported by the ABI it has a list of mem chips that can be tested and among them are multi voltage chips including the 4116. I just can't find a way to do it.

Perhaps there's a Guru on this BB that can Help

Thanks again pete (invadar)
 

Equites

Chief Sheesher®
vacBacker
Feedback
35 (100%)
Credits
3,329CR
To be honest, the only real way to see whats going on is to fire up the scope, and check the data/IO lines to make sure there are clean signals there.

The problem with RAM is that they will try to go on for as long as they can, and so using a probe does not always yield results unless some lines start to float or fail completely.
 

Macro

Active member
vacBacker
Feedback
4 (100%)
Credits
2,009CR
I must admit I usually use the Fluke for testing things like this - fire the board up with the fluke pod attached, and as long as the ram is accessible from the main CPU (which it is on most boards) then you can run a long or short ram test.

only board I couldn't do that on was cosmic guerilla, 'cos there seems to be no such thing as a 9980 fluke pod! (or at least, I don't have one)

incidentally I don't have a 6809 one if anyone has one spare - dead or alive ?
 

Equites

Chief Sheesher®
vacBacker
Feedback
35 (100%)
Credits
3,329CR
Macro said:
incidentally I don't have a 6809 one if anyone has one spare - dead or alive ?

Mike could you not convert a 6800 pod to 6809? Im not aware of the differences but I do have documentation of how to successfully convert a 6800 pod to 6502 for example.
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
For a little bit of insight into how the professional repairers would do it...

I'm not a professional repairer as such, but was doing it for money at one point. But anyway, looking at a BZ board with lots of faults at the moment. As Mike says, first thing I do is to stick it on the Fluke (9100FT in my case) and test the RAMs. In this case the RAMs are all 2114's, but same principle.

First up, the program RAMs these are directly accessible by the MPU so a simple test shows them to be bad. So I cut all the legs off and remove the chips. Fit sockets and new RAM. Program ram is now ok.

For the vector RAM, they're still directly accessible by the MPU but now they're also MUX'd together with the vector stack / program counter. This time, as well as memory errors I'm getting address line errors (address lines tied). So my suspicion is the LS157's that are multiplexing the two addressing mechanisms. Sure enough, one of the LS157's is bad so I replace it.

At this point I'm now getting just plain old RAM errors. With the Fluke I can tell that one of the 6 x 2114's is bad as when I piggyback a good one on top the error goes away so that one is cut out. Next though I'm getting errors that don't go away with piggybacking a good chip so at this point I'm suspecting the faulty chip is holding a data line in a state that excludes that method of testing. Little choice at this point but to unsolder the remaining RAM, fit sockets and test them individually. Which I didn't do last night as it was 2am by this point and de-solder stations are noisy!

So really, my point is that even when you have all the tech kit in the world that allows you to pinpoint things properly desoldering and removing is often still the only sensible option when more than one device is powered up on the data lines at once.

Obviously when things are working properly a bad ram shouldn't affect the others. In my case there are 6 2114's. Each 4 bit data. So A1, B1, C1 are the high bits for 2000-23FF, 2400-27FF & 2800-2BFF respectively, A2, B2, C2 are the low bits for the same. When A2 was bad it only affected it's own memory space. But one of either B1 or C1 is also bad with a fault that is holding one or more of the data lines high. Therefore I won't know which it is until I remove them, one at a time, or just both at once and fit sockets. Even snipping the power pins for the chips so they're not powered up won't help if they have dead shorts in them holding one or more data lines either low or high.

Thankfully, the scenario I've described isn't too common. But sometimes desoldering is the only way!
 
Top