Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse info on DLT network trace frames and contained protocols #22

Open
kruss opened this issue Jul 25, 2024 · 0 comments
Open

Parse info on DLT network trace frames and contained protocols #22

kruss opened this issue Jul 25, 2024 · 0 comments
Assignees

Comments

@kruss
Copy link
Collaborator

kruss commented Jul 25, 2024

According DLT specification PRS_Dlt_00621 if the MSTP field is set to 0x2 (DLT_TYPE_NW_TRACE) the Message Type Info field (MTIN) will provide the type of the contained network protocol, which could be of kind:

  • 0x1 (DLT_NW_TRACE_IPC)
  • 0x2 (DLT_NW_TRACE_CAN)
  • 0x3 (DLT_NW_TRACE_FLEXRAY)
  • 0x4 (DLT_NW_TRACE_MOST)
  • 0x5 (DLT_NW_TRACE_ETHERNET)
  • 0x6 (DLT_NW_TRACE_SOMEIP)
  • 0x7-0xF (User Defined)

The dlt-core library would need to return this information on parsing DLT-Frames, so a callee can further process the contained network trace payloads.

A possible implementation would be to extend the returned dlt::PayloadContent of parse::dlt_message with an enum-item NetworkTrace providing the possible network types.

As DLT network traces are flagged as non-verbose, but may contain several DLT payload arguments, the NetworkTrace items should already provide the list of the raw bytes of those arguments.

@kruss kruss self-assigned this Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant