EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: EGDima on April 19, 2014, 10:47:22 pm
-
Hello,
I am struggling to find any information on this topic. Does Agilent 54622D support decoding serial buses and actually show data in hex or binary?
Thanks!
-
At the Agilent website they say "I²C, SPI, LIN, CAN and USB triggering". But nothing about decoding. So , it will not be able
http://www.home.agilent.com/en/pd-1000000811%3Aepsg%3Apro-pn-54622D/portable-mso (http://www.home.agilent.com/en/pd-1000000811%3Aepsg%3Apro-pn-54622D/portable-mso)
-
Interesting, thanks for the information. Does it mean that MSO/logic analyzer features of this unit are useless. Why would anyone use a logic analyzer without being able to see the data?
-
Here you can see an Agilent 54642D in action (from minute 6). The Agilent guy says something about decode and triggering.
What's All This Femtoampere Stuff, Anyhow? (https://www.youtube.com/watch?v=B4G3YPlO6Wg#)
The agilent webpage about the 54642D also tells you nothing about decoding, only triggering. Maybe you have to look deeper in the manual.
-
Thanks for the video link. It looks like it can actually decode data for triggering purposes but can't show the arbitrary data itself. Not sure how useful such triggering is though, sigh. But maybe I just don't know proper uses for this.
-
Here you can see an Agilent 54642D in action (from minute 6). The Agilent guy says something about decode and triggering.
Triggering is one thing, which it does well. Decoding is something else entirely, where it interprets a bit-stream and displays bytes in various formats. It doesn't do that at all. Only newer devices can do that.
The agilent webpage about the 54642D also tells you nothing about decoding, only triggering. Maybe you have to look deeper in the manual.
That's no accident. You can look infinitely deep, but find nothing, because there is nothing.
-
Not sure how useful such triggering is though, sigh. But maybe I just don't know proper uses for this.
Triggering without decoding is useful for determining the presence, timing, and relative location of data within a bit-stream. You can see if it's structured properly, and if there are things like runt pulses, or spurious noise. You can't see the actual data values, without decoding them yourself (which I've done on occasion in the past, though it's a PITA). But sometimes you don't need that. If you do, these are not the tools you want to be using.
-
Thanks for all the answers. I think I will stick to 54622D + saleae combo. Using agilent trigger and decode by using saleae.