Greetings,
We have a 34702B with two 16557D Analyzer cards in it, both in slot B. One is connected to one processor board, the other to a second processor board.
We have several different configuration files for verifying the timing of commands from the first processor to the second, and most work fine, except for a couple of them - they always "crash", but only the first time you load and run them.
The crash is either an "Acquisition Error" (which I haven't found in any manual) in the Run Status window , which states:
Slot B: Acquisition Error. Data Discarded, Possible causes:
- Poor state clock quality
- State clock faster than specification allows
- Inadequate probe grounding.
The other crash is that it says that the analyzer stopped without a trigger. However, in that case Machine 1 arms Machine 2 (when Machine 1 triggers), however there is no data for Machine 1 and there is for Machine 2.
Since we have several hundred other tests that run fine, it doesn't appear to be a hardware error as the message states.
Any insight on these would be greatly appreciated, since we're trying to get into our Final Quality Run and these are holding us up right now.
Thanks in advance,
Mark
Edited by: bakersacres on Jul 24, 2015 11:31 AM
We have a 34702B with two 16557D Analyzer cards in it, both in slot B. One is connected to one processor board, the other to a second processor board.
We have several different configuration files for verifying the timing of commands from the first processor to the second, and most work fine, except for a couple of them - they always "crash", but only the first time you load and run them.
The crash is either an "Acquisition Error" (which I haven't found in any manual) in the Run Status window , which states:
Slot B: Acquisition Error. Data Discarded, Possible causes:
- Poor state clock quality
- State clock faster than specification allows
- Inadequate probe grounding.
The other crash is that it says that the analyzer stopped without a trigger. However, in that case Machine 1 arms Machine 2 (when Machine 1 triggers), however there is no data for Machine 1 and there is for Machine 2.
Since we have several hundred other tests that run fine, it doesn't appear to be a hardware error as the message states.
Any insight on these would be greatly appreciated, since we're trying to get into our Final Quality Run and these are holding us up right now.
Thanks in advance,
Mark
Edited by: bakersacres on Jul 24, 2015 11:31 AM
I would not characterize either of your problems as "crashes". They are just cases where you did not capture the data that you expected.
On the first issue:
The messages that you are getting usually indicate poor signal quality on the clock line(s). It could be noise, or incorrect thresholds, or any number of other things. I assume that "nothing" changes in your HW between this test and any previous tests. Is there anything different between these configurations and other ones that you load, in terms of the signal setup?
On the second issue:
Are you sure that you have Machine 1 set up to store data? It is possible to trigger without storing, and store without triggering. Have you defined a trigger for Machine 2? It could be "trigger on anything, armed by Machine 1" or something like that. I have long since forgotten the grammar for these analyzers.
You say that these tests only fail the "first time you load and run them". If you run them again, without reloading, do they work? If you load twice without running, do they work?
All of this HW is VERY old. The 16702B became unsupported in 2010, and the 16557D became unsupported in 2007. Support usually lasts for 5 years after discontinuance. Having this in your critical path for release is probably not a very good idea.
Al