THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question
0

Why is OBD2 not a subdissector of 15765

  • retag add tags

Why is OBD2 not a subdissector of 15765?

The standard seems to say it rides on top of 15765 in the case of CAN. I do recognize that it also says it can ride on some other Physical layers but Wireshark doesn't support those. Officially riding on top of the 15765 dissector would also solve my second gripe that the current OBD2 dissector requires 8 bytes in the frame to dissect, which I can't find spec support for. If this or that ECU requires 8 bytes, that's a whole other issue compared to what's allowable in the spec.

But I'm also fairly junior in the industry so, correct me where I'm wrong.

foreverska's avatar
1
foreverska
asked 2020-11-22 00:35:51 +0000
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

Perhaps you can reach out to the latest authors adding to these dissectors (see here and here) and find out what was the reasoning behind it.

Jaap's avatar
13.7k
Jaap
answered 2020-11-22 11:57:32 +0000
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer