Understanding trigger specifications
Question asked by deninnh on Jan 22, 2015
Latest reply on Jan 23, 2015 by deninnh
Like •
Show 0 Likes
0
Comment • 4
I've been using scopes for over 30 years up to the latest and thought I knew them fairly well. I've purchased several high end scopes in the past and have to admit that trigger specifications were not high on my list of concerns. They just worked !
After acquiring a personal 54846A which will not trigger above 1GHz on a clean sine wave (Agilent source), I decided I should read the spec.
It was surprising to find that trigger sensitivity for this 2.25GHz scope is only spec'd up to 1GHz.
So then what happens ?
Funny thing is that it *will* trigger on very fast events like an avalanche pulser or airborne ESD event (from a distance of course) with risetimes below 200ps. But it just can't handle a sine wave. I've looked at the source output and it is very clean spectrally. On another 3GHz scope, the sine wave is perfect.
Is the scope broken? All channels are identical in behavior. Deleted cal files and ran full cal with no change. Unit is very clean and has the last software version offered and also the last, fastest motherboard.
I realize that current models have much improved triggering. On another unmentioned brand of scopes I've always been able to trigger right up to the specified scope bandwidth before aliasing and other things kick in.
Generally, the HW Trigger BW of scopes, in the past, has been approximately half the scope BW. There are also sensitivity specifications, so depending on the signal magnitude, you can trigger on higher BW signals. Newer Agilent/Keysight scopes have a "Trigger Sensitivity" button, that can give higher BW triggering.
That said, there are also digital scopes that 'fake' a higher BW. They use a hidden 'Auto' trigger mode (which forces a trigger if there's no trigger event within a short period of time), then look for an edge near the center of the trace in SW, and move that to the middle of the display. If it happens fast enough, it is indistinguishable from a 'real' trigger. It's very hard to determine if this is being done.
You don't indicate the brand on the 3 GHz scope, or the frequency of the sinusoidal signal you used to test it, so I can't comment on that part .
Al
Like •
Show 0 Likes
0
Actions
deninnh
deninnh @ algoss on Jan 23, 2015 12:38 PM
Hi Al,
Thanks for the quick reply.
I was applying a clean sine wave between 1GHz and 2.5GHz, but suspended the BW test of my "new" scope when it wouldn't get past 1GHz. (it will actually trigger at all up to around 1.2GHz but with much jitter on the trace).
Last night I ran the trigger sensitivity test in the service manual and it passes, but tests are only at 100MHz, 500MHz and 1GHz.
The "other" was a TDS694C and it delivers a cleanly triggered waveform almost up to 3GHz (its BW).
SInce there is no spec beyond 1GHz for this model, I may not have a leg to stand on for returning this scope to the dealer.
We have a 3000X (1GHz) and 4000X (2.5GHz) at work and I noticed that the trigger spec no longer mentions at what frequency (as far as I recall). Likewise for the other brand. It is Y range sensitive but not frequency dependent. These models are converting me to Agilent but my home lab budget says "old Agilent".
So, if this scope triggers "ok" at 1GHz, would you say that was normal for the model?
Thanks for your help.
Den
Like •
Show 0 Likes
0
Actions
algoss
algoss Employee @ deninnh on Jan 23, 2015 12:56 PM
Yes, I would say that since it triggers at 1GHz, it is working as specified. The fact that it's "jittery" at 1.2 GHz is proof, at least to me, that it's a real trigger, not one of the "fake" triggers I mentioned.
The 3000X and 4000X only talk about trigger BW in terms of trigger sensitivity at different bandwidths.
For many measurements that people are making with higher speed scopes, Edge trigger BW becomes less important. When looking at jitter, for instance, the trigger location is not part of the equation at all. The only thing that matters is the timebase, and the location of the edges.
Al
Like •
Show 0 Likes
0
Actions
deninnh
deninnh @ algoss on Jan 23, 2015 3:27 PM
Thanks again Al.
I decided to be practical about this and try it in a real world application, USB HS verification. The trigger was good enough but of less importance since the test is done on data from a single sweep, triggered by a pulse width condition.
It worked flawlessly and blows away the old TDS in terms of ease of use and fast storage (good old 1GB flash drive under Win98).
Den
Here's the 54846A. Just two resistors need to be de-populated, so my drawing is at least correct for the 54846A.
Here's the 54846A. Just two resistors need to be de-populated, so my drawing is at least correct for the 54846A.
I have a fully working 54845A that pass all test and calibrate without problem and I did the change to make it a 54846A.
It detect that it is a 54846A but testing give a lot of error and finally crash!
This mean that software is different and maybe attenuators and other parts …
It could be as well that during installation of the software that is encapsulated in the installation software different versions are installed depending of the resistor selecting the model.
Here's the 54846A. Just two resistors need to be de-populated, so my drawing is at least correct for the 54846A.
I have a fully working 54845A that pass all test and calibrate without problem and I did the change to make it a 54846A.
It detect that it is a 54846A but testing give a lot of error and finally crash!
This mean that software is different and maybe attenuators and other parts …
It could be as well that during installation of the software that is encapsulated in the installation software different versions are installed depending of the resistor selecting the model.
It's not the software. I have one Symantec Ghost image that works in all the scopes in this series with the FIC motherboard.
The scopes are 54810A, 54815A, 54820A 54825A, 54835A, 54845A, and 54846A.
In some miraculous way, my Agilent 54845A turned into 54845B (at least so it is now shown).
I made a motherboard update and a software update v.4.5 for 54845B. I tried different versions of software, but only with this I got success.
Previously, there was an Atlas PCI-III Series 757 motherboard based on Socket 7 and AMD K6-2 300 MHz processor and 64 MB RAM.
Now the most advanced motherboard for AT-form factor with Intel 440BX chipset and Socket 370, with 133MHz bus, where the Coppermine core Pentium III processor can be installed, up to 1133MHz (or with a small upgrade of Tualatin 1400MHz) and 3x256 MB of RAM max.
The new motherboard is designated Tomato (ZIDA) BXv98-CU/v693
Hi Jwalling,
It looks like there really is a ZIDA motherboard with exactly the same external design, but with VIA chipsets. But on my board a set of Intel chips is actually installed. On my board there is only an inscription: 60-cbxict1 30-00 (I edited my previous post).
The manual was not found, but the display shows: -440BX-
BIOS allows to overclock the processor bus up to 150 MHz, which corresponds to the specification 440BX.
Thanks for the clarification. Have you thought about upgrading it to a 2.25GHz 54846A/B?
Thanks for the clarification. Have you thought about upgrading it to a 2.25GHz 54846A/B?
Yes, I want to follow your example. In any case, I will try. Has someone succeeded in the calibration procedure after changing 54845 to 54846?
I also have a couple of questions: how to get access to the Windows desktop in this device? What drivers are needed to use usb flash memory to save screenshots in it?
Thanks for the clarification. Have you thought about upgrading it to a 2.25GHz 54846A/B?
Yes, I want to follow your example. In any case, I will try. Has someone succeeded in the calibration procedure after changing 54845 to 54846?
I also have a couple of questions: how to get access to the Windows desktop in this device? What drivers are needed to use usb flash memory to save screenshots in it?
Jay, your manual seems to fit (page 14).
I tried to reset the jumper, as you described. It really does now show 54846B. However, the calibration was not successful for each of the 4 channels. I do not know what is the reason, I think there are hardware differences that do not allow to make an upgrade 54845 to 54846 (or fine-tune the input amplifiers).
eurofox, thanks, I'll try to do it. I correctly understand that now you have the opportunity to use a usb flash to save the screenshot files?
Maybe someone managed to upgrade to Windows 2K?
That's the one thing I think is impossible. The problem is that there's no 2K drivers for the acquisition controller.
It's surprising that the 54845A can't be upgraded to a working 54846A. All the magic in these scopes are in the attenuator assemblies and A/D converters. Both models use the same parts - the A/D converters are part #1NB7-8353 and the Attenuator modules are 54512-63402 for both models.
Here's another difference I found on the solder side under PGA device U91
Two resistors are not installed on the 54846A!
Are you sure that the presence of these resistors is essential? It would be good to check this: remove these resistors and try to do the calibration procedure without them. If you get the same negative result as I do, it will be a breakthrough (by the way, what is the value of these resistors?).
Are you sure that the presence of these resistors is essential? It would be good to check this: remove these resistors and try to do the calibration procedure without them. If you get the same negative result as I do, it will be a breakthrough (by the way, what is the value of these resistors?).
What I'm saying is that the 54846A does not have the resistors installed so there's nothing to remove. Your 54845A (if I'm right) has them installed. They are 261 Ohms in the 54845A.
Looking a bit closer now; there may be a little more to this:
The other two resistors right next to those that are installed in both boards have different values as well.
On the 54845A they are 90.9 Ohms (marked in blue). In the 54846A (also marked in blue) they are 68.1 Ohms.