Protocol awareness

Would it be possible to incorporate some form of protocol awareness into the digital signal analyser, such that standard serial frames like CANBus can be detected and used as a trigger, i.e. wait for an extended CAN frame with a specific arbitration field to arrive and then trigger the 'scope?

Would it be possible to incorporate some form of protocol awareness into the digital signal analyser, such that standard serial frames like CANBus can be detected and used as a trigger, i.e. wait for an extended CAN frame with a specific arbitration field to arrive and then trigger the 'scope?

hello Idlewise,
yup - you've got another item on the development wishlist. We will be doing this fairly soon. Our approach is to use hardware decoders in our FPGA. We have obtained these decoders:
1. RS232 and RS485.
2. SPI.
3. I2C
4. USB
5. CAN
We are making the decoder downloadable (because we want to be able to have future decoders, and because we don't have room in our FPGA for all the possible decoders). So when you specify a decoder, the application will download the decoder to the hardware. While specifying the decoder you will also have to specify some aspects of decoder operation (for example which bits are the data/clock streams, clock/data polarity, number of bits/symbol).

There is some other work to be done before the protocol analyser, but I expect we'll have it done by the end of the year.

Any suggestions welcome.

hello Idlewise, yup - you've got another item on the development wishlist. We will be doing this fairly soon. Our approach is to use hardware decoders in our FPGA. We have obtained these decoders: 1. RS232 and RS485. 2. SPI. 3. I2C 4. USB 5. CAN We are making the decoder downloadable (because we want to be able to have future decoders, and because we don't have room in our FPGA for all the possible decoders). So when you specify a decoder, the application will download the decoder to the hardware. While specifying the decoder you will also have to specify some aspects of decoder operation (for example which bits are the data/clock streams, clock/data polarity, number of bits/symbol). There is some other work to be done before the protocol analyser, but I expect we'll have it done by the end of the year. Any suggestions welcome.

Hi Bart,

Whats the status of the protocol analyser? This will be very useful to us..

Thanks,
Mike

__________________
eDIY New Zealand NZ Webhosting Website Design and eCommerce CMS Software

Hi Bart, Whats the status of the protocol analyser? This will be very useful to us.. Thanks, Mike __________________ [url=http://www.ediy.co.nz]eDIY New Zealand NZ Webhosting Website Design and eCommerce CMS Software[/url]

I'm curious about the status of this as well. I'd mainly be interested in I2C and SPI (and maybe RS232).

I'm curious about the status of this as well. I'd mainly be interested in I2C and SPI (and maybe RS232).

We are still at it. There is some contention with other project areas (Cs328A and charting). It will get done.

We are still at it. There is some contention with other project areas (Cs328A and charting). It will get done.

Hmm, what will sell more? Faster scope or protocol awareness?

I, for one, purchased the CS328 anticipating protocol awareness and would like to see it sooner than later.

Hmm, what will sell more? Faster scope or protocol awareness? I, for one, purchased the CS328 anticipating protocol awareness and would like to see it sooner than later.

I'd like a faster scope myself... and protocol awareness can be added later in software. I am waiting for faster hardware to be available. Our company bought the CS320 which is great... I would like a scope for myself, but am waiting for something better than 100msps.

I'd like a faster scope myself... and protocol awareness can be added later in software. I am waiting for faster hardware to be available. Our company bought the CS320 which is great... I would like a scope for myself, but am waiting for something better than 100msps.