In order to spend our development resources on what our customers want, we would like to get some feedback on what class decoders you would like to see us develop for the 1480A USB Analyzer. Class decoders are very time consuming to develop and test so we would love to get some feedback to make sure we are not spending time on writing class decoders that have little actual use.

We are in the process of developing mass-storage class-decoders since these are likely often used in an embedded environment.

Thank you.

Audio Class decoding is a must!

Communications Device Class too!

Thanks. We have bumped these up on the priority list.

Video class decoders would be useful also. I know this is a large set of descriptors to decode. Just implementing some of the top level ones would be useful.

An alternate idea is to allow users to enter in their own decoding. I would happily enter in the tree of descriptors that interest me. If that could be contributed back for inclusion in future releases, that would be fine too.

Yes, i t is of course very costly to add decoder support. We are considering releasing a separate software version for those users that need decoder support. This will allow us to continue selling the base version for the $399 price. So far, however, very few users are interested in decoders so this is still low on the feature priority list.

We've put video class decoders on our todo-list.

Some of the most common classes are also quite simple. I would suggest that these would be good ones to start with.

CDC-ACM
HID - Generic/basic even. No need for report descriptor parsing.
MIDI

These are not complicated and I would suggest they would cover a large portion of the analyzers user base.

I must say I was a little disappointed to receive my 1480A today and not have it identify very common CDC-ACM class requests.

Put this down as a "mild" gripe. Otherwise I got it up and running in minutes and was pleased at how simple it was to use first up.

I may well do a more detailed write-up as soon as I have more experience.

-JTR

To add my tuppence worth as we would say in the UK

I currently use the following

Audio 1.0
Audio 2.0
Midi1.0
HID

Thanks for a great product

Colin

In my opinion, without class decoders, any USB analyzer's value is greatly diminished.  At an absolute minimum, the following class decoders would be required in order for me to consider purchasing a USB protocol analyzer:

HID
CDC
MSC
Audio

In just the past 6 months, I have had to develop/debug all of these.  If I have to hand-decode the packets, errors can creep into my debugging work, especially if I have the packet layout incorrect.

I vote for a basic set of class decoders as well. HID, Audio, Serial, perhaps Video

What else would be great is providing a decoder SDK and a plugin model to let people who needs them the option to do the work themselves