Skip to content

ASCReader: Skip J1939TP messages #701

New issue

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

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

Already on GitHub? # to your account

Merged
merged 5 commits into from
Sep 20, 2019
Merged

Conversation

bessman
Copy link
Contributor

@bessman bessman commented Sep 11, 2019

.asc files can contain J1939 Transport Protocol messages, which look something like this:
0.297743 1 J1939TP FEE3p 6 0 0 - Rx d 23 A0 0F A6 60 3B D1 40 1F DE 80 25 DF C0 2B E1 00 4B FF FF 3C 0F 00 4B FF FF FF FF FF FF FF FF FF FF FF FF
This change makes ASCReader skip such messages, instead of breaking.

@codecov
Copy link

codecov bot commented Sep 11, 2019

Codecov Report

Merging #701 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #701   +/-   ##
========================================
  Coverage    68.34%   68.34%           
========================================
  Files           69       69           
  Lines         6199     6199           
========================================
  Hits          4237     4237           
  Misses        1962     1962

@christiansandberg
Copy link
Collaborator

Could you also add a line in test/data/logfile.asc?

@bessman
Copy link
Contributor Author

bessman commented Sep 12, 2019

Of course. In a real logfile the J1939TP entry would be preceded by a number of normal CAN messages containing parts of the J1939TP message. Should I also include those in the example file?

0.098426 1 18EBFF00x Rx d 8 01 A0 0F A6 60 3B D1 40 Length = 273910 BitCount = 141 ID = 418119424x 0.148421 1 18EBFF00x Rx d 8 02 1F DE 80 25 DF C0 2B Length = 271910 BitCount = 140 ID = 418119424x 0.197693 1 18EBFF00x Rx d 8 03 E1 00 4B FF FF 3C 0F Length = 283910 BitCount = 146 ID = 418119424x 0.248765 1 18EBFF00x Rx d 8 04 00 4B FF FF FF FF FF Length = 283910 BitCount = 146 ID = 418119424x 0.297743 1 J1939TP FEE3p 6 0 0 - Rx d 23 A0 0F A6 60 3B D1 40 1F DE 80 25 DF C0 2B E1 00 4B FF FF 3C 0F 00 4B FF FF FF FF FF FF FF FF FF FF FF FF

@felixdivo
Copy link
Collaborator

We should probably document that behavior in the class. Can you do that?

Besides, is there some official documentation of the file format we can link to?

Of course. In a real logfile the J1939TP entry would be preceded by a number of normal CAN messages containing parts of the J1939TP message. Should I also include those in the example file?

Why not add the J1939TP in a few places, like at the start, in between and at the end? It shouldn't hurt.

@felixdivo felixdivo added enhancement file-io about reading & writing to files labels Sep 12, 2019
@felixdivo felixdivo assigned felixdivo and bessman and unassigned felixdivo Sep 12, 2019
@bessman
Copy link
Contributor Author

bessman commented Sep 12, 2019

Besides, is there some official documentation of the file format we can link to?

Not to my knowledge.

@felixdivo
Copy link
Collaborator

felixdivo commented Sep 20, 2019

Thank you @bessman for these improvements!

@felixdivo felixdivo added this to the 4.0 Release milestone Sep 20, 2019
@felixdivo felixdivo merged commit 68855df into hardbyte:develop Sep 20, 2019
@karlding karlding mentioned this pull request Oct 25, 2019
hardbyte pushed a commit that referenced this pull request Dec 28, 2019
Skip J1939TP messages
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement file-io about reading & writing to files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants