While you can see a lot on a scope or a logic analyzer, the time it will take you to find the erroneous place by poring over data can be so long that by the time you are where the error is, you do not see it - been there, done that.

e.g. an example of mine: a "functioning" system is suspected of occasionally emitting a record with a bad program calculated checksum, since there is automatic retry, nobody has any idea which record type it is. This "can" (I doubt it) be located by a logic analyzer cum scope but a good protocol analyzer will, automatically, highlight the bad records (or even oly list such). I found a place where an interrupt disable was missing causing the above by running the analyzer overnight and next morning there was TWO (yes, only 2) records shown in the error report. I doubt I could have found that by looking at a logical analyzer.

Thus "is it worth to buy the stuff" often can not be answered "yes" till you see the need, if your ANYbus run flawlessly what do you need an ANYbus analyzer for. Of course if you wait till then, there will be a 3 month delivery time.

As I stated above in the case of trace, one person in one situation may get extreme utility from something that another person in another situation may not.

Erik