This repository has been archived by the owner on May 7, 2021. It is now read-only.
When used on a busy can bus on Linux/socketcan we had overruns as soo… #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Miller Lowe [email protected]
UDS interface was loosing packets on a 500kbps bus running around 50%, socketcan allows filtering so that the application will only see the UDS receive ID. This change will automatically utilize filtering if a UDS Interface is created.
Note that if the dispatcher is going to receive messages other than the UDS receive ID they will need filters added. The filter in only created automatically if you hand the dispatcher to the UDS interface constructor.
This commit enables the use of socketcan filtering when used as a UDS device.
overall commands Sent : 6000
overall average response time: 0.0048991614580154415
overall standard deviation : 0.002319849086112244
overall max delay : 0.05056476593017578
overall min delay : 0.0018734931945800781