Hi Frank,

Thanks for the reply. Lets see if I have this right

The scope you are using can capture the packages and display them as code, in whatever format you require. Also you can set the trigger to capture just the bit of code that you want to see.

Question is how do you know what the code means in real terms. For example if you have a speed signal missing from a node, with a DTC telling you that, how can you tell which bit of code is that signal and where it comes from?`

It would be nice to be able to watch a DTC set and see the relevant signal drop off the data bus (although that raises other issues like code setting criteria and timed out signals etc) along with being able to see where the signal broke down. How close do you think we are to that?

Thanks

Alan