Far better off with any generic FX2 based logic analyzer and sigrok - check your signal integrity with the scope, if you want to look at data, capture it into something useful.
Agreed. I have an Agilent DSO7014A. It's old now but pretty capable - unusally for its time, and possibly still now, it has hardware serial decode. This means that you can trigger on the serial pattern, not just edges. Frustratingly, it will only decode two channels : it ought to use the hardware decode for the trigger channel and software-decode other channels.
But although I occasionally use that feature because the scope's on the bench and usually switched on, for any substantial serial decode I use a salae analyser. It doesnt have hardware triggering (I think the latest software does have a software trigger) but the ability to capture and work with a practically infinite length of capture is a killer feature - and available at very low cost if you use Sigrok instead of Saleae.
Even though later scopes have deeper capture than my agilent, searching, panning and listing on a PC interface is worlds away from doing it on a scope screen, even a big one like the 7014.
Put all your effort into the first line features - update rate, sample rate, readability - and leave the features like serial decode, function generators etc. to dedicated boxes. In some circumstances it can be attractive to have everything in one box but the upgrade route is restricted and 'jack of all trades is master of none'.
Hardware decode is not prerequisite to serial triggers. Siglent, for instance has software decoding but hardware based serial triggers.
Also hardware decoding has benefit of speed, but has big drawback that you have to capture data with the decoder in a first place..
Which means you have to setup everything perfectly, and then capture to get data decoded.
On scopes with software decode, you can simply capture any signal, and then turn on decoding and keep setting it up until it recognizes data protocol properly. You can try different speeds, setting, or even protocols while trying do figure out what kind of protocol is that.
On Picoscope you can even decode from Math channel, which allows you to precondition signal before decoding.
Decoding on a scope is very convenient. It allows you to look at data in analog and digital domain simultaneously. When you have problems with something you need to check both.
But I already said before, for debugging software layer, and lots of data a USB protocol analyser that logs unlimited data to PC is better.
I was planning to get one long time ago (and got 2) but realized that for this type of work Picoscope with deep memory will do great job of both...
So never bought a Saelae (which I could have bought while it's price made more sense than today).
If I buy any LA in the future, it will be 32 channels... I had occasional need for more than 16 inputs...Maybe DSLogic U3Pro32?
I have older Zeroplus LAP-C 16256 and don't use it. It has limited memory and cannot stream to PC directly. It decodes loads of protocols though. New LAP-C Pro 32064M sounds fantastic, but is expensive for a thing I would use very rarely. I would rather buy DMM6500 or new VNA...
I also have Digital Discovery. About which I have mixed feelings. It has some unique features (like pattern generation or ROM mode) and I mostly use it for that. It's biggest problem is that it's inputs a very fragile. They directly connected inputs to FPGA over some resistors and that's it. All my MSO scopes have good protection and variable thresholds. (MSOX3104T: Maximum input voltage ± 40 V peak CAT I; transient overvoltage 800 Vpk).
But maybe an input conditioning board could be made and it is very useful device. For instance, I used it test two communications problems, where I used it to generate random signals simulating sensors triggering, and looking for relay activations and serial messages being sent... After few hours of that running on it's own, I found there was one state that went into interlock. Some changes in code, and that was it..