Skip to content

Move 'gap' of canplayer between frames not logs. - #619

Open
JamesB192 wants to merge 1 commit into
linux-can:masterfrom
JamesB192:gap-in-logs-not-between
Open

Move 'gap' of canplayer between frames not logs.#619
JamesB192 wants to merge 1 commit into
linux-can:masterfrom
JamesB192:gap-in-logs-not-between

Conversation

@JamesB192

Copy link
Copy Markdown

For when -t was too fast, and sans -t, takes too long.

For when -t was too fast, and sans -t, takes too long.
@JamesB192
JamesB192 force-pushed the gap-in-logs-not-between branch from 255a37c to e9ceaa3 Compare July 30, 2026 23:15
@hartkopp

hartkopp commented Jul 31, 2026

Copy link
Copy Markdown
Member

I get your point but the patch is wrong IMO.

If you have a bunch of frames that are so tight together that they are needed to be pushed out until the next waiting happens, you simply have to do so. Otherwise you will never get the correct timely behaviour.

This gap setting is more like a "how often the loop is running" than describing the gap between two CAN frames.

And inside such a (1ms) loop multiple CAN frames may be needed to be processed when their timestamps fit into this 1ms section.

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

Successfully merging this pull request may close these issues.

2 participants