hardbyte / hardbyte/python-can

DLC value usage/definition not according to ISO11898

Open
#749 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.6k
Forks
697
PR merge metrics
No merged PRs in 30d

Description

While reading the standards and checking the ixxat interface for fd support, I've seen that the definition of the dlc of the message class in not as in the ISO standard and not as the common unterstanding is.
The length of the data is already encoded in the message data itself, so storing it additionally is reduntant and may lead to errors.
As well the behavior of the classes regarding the data and dlc is somewhat undefinded.
So please agree, that the dlc should be used as in the ISO standard. With the folloeing definitions:
dlc | length of data
0 .. 8 | 0 .. 8
9 | 12
10 | 16
11 | 20
12 | 24
13 | 32
14 | 48
15 | 64

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.