|
OK, signature analysis:
toggle quoted message
Show quoted text
Put the processor in a no-op loop that effectively reads all locations in memory and wraps.? (the processor sees no-ops on the bus regardless of what's out there. The signature analyzer generally has a start, stop, clock, and ground leads. Instructions on how to connect them are in the manual, as are the settings on how to capture data (clock, active levels, etc). Once connected, you can read the pattern.? It's a hex pattern, with the H, P, U and so on replacing the hex characters.? You can, once connected, take the data lead and connect it to ground and to VCC and get an idea of what the pattern is for a node that is stuck at 1 or zero. All you're looking for is "is the pattern as stated".? You can't really go from a pattern (132H rather than 132P) and say oh, this chip I'm not connected to is bad... What it does tell you is that connection (node) is not performing as desired. You then look at the inputs of the gate/element with the bad output, and look for bad inputs.? Tracing that bad input back to a bad output from something, says that the something is bad.? If all the inputs to the chip you're testing are good, and you have a bad output pattern, suspect the chip. If you haven't used it before, you'd think it did more, but you're really looking at "functional/non-functional" for each circuit node they give you. Hopefully, this fills in the blanks.? If you already knew this, my apologies. Harvey On 11/25/2021 2:54 PM, Brian Nordlund wrote:
I thought my AA5001 was fully working, but have discovered that the GPIB board is not responding to commands. I have over a dozen working GPIB devices, including four other TM modules. Since the AA5001 does not work in any (otherwise working) slots, I have no reason to suspect my controller or chassis. |
