You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did some tests with BLF/ASC/LOG conversions and discovered a problem with the latest develop branch (at least):
Usually the CAN interface names for SocketCAN look like can0, can1, vcan12 and so on. The BLF to LOG conversion lead to CAN interface names that are numbers like 1, 2, 33 - which is unusual but works too.
When converting a LOG file to ASC the channel2int() function should assign unique CAN interface numbers for the converted CAN interfaces for the ASC file. In the logfile below channel2int() maps two CAN interfaces can1 and can11 to the same CAN interface number 2 - which is definitely wrong:
Converting a SocketCAN logfile with (unusual) numbers as CAN interface names:
(1643782223.031881) 11 128#70000000000000 R
(1643782223.032020) 1 206##160E87E0000F80F0000000000000000000800FE03000010F4 R
(1643782223.032033) 11 148#100000 R
(1643782223.032041) 14 12DD54DB##1000000000000000000000000000000000000000000000000 R
(1643782223.032059) 7 5E9##100FF1F7FFF070000 R
(1643782223.032077) 4 268##10000FFFFF7FF7FFFFFF7FF7FFFFFFFFFFF000000000000000000000000000000 R
(1643782223.032241) 11 118#D20000000003 R
(1643782223.032244) 1 0B6##1E30A058005800003805A78000280028000000000000000000000000000000000 R
(1643782223.032415) 11 138#10000000 R
(1643782223.032492) 14 0B6##1E30A058005800003805A78000280028000000000000000000000000000000000 R
(1643782223.032515) 1 1BFDDA0A##1E48B8C2B80808080000000000000000000000000000000000000000000000000 R
(1643782223.032625) 1 09F##1950DFE4F006A80F0 R
(1643782223.032756) 4 09F##1950DFE4F006A80F0 R
(1643782223.032762) 14 09F##1950DFE4F006A80F0 R
Converting a SocketCAN logfile with usual CAN interface names (like can3):
(1643782223.031881) can11 128#70000000000000 R
(1643782223.032020) can1 206##160E87E0000F80F0000000000000000000800FE03000010F4 R
(1643782223.032033) can11 148#100000 R
(1643782223.032041) can14 12DD54DB##1000000000000000000000000000000000000000000000000 R
(1643782223.032059) can7 5E9##100FF1F7FFF070000 R
(1643782223.032077) can4 268##10000FFFFF7FF7FFFFFF7FF7FFFFFFFFFFF000000000000000000000000000000 R
(1643782223.032241) can11 118#D20000000003 R
(1643782223.032244) can1 0B6##1E30A058005800003805A78000280028000000000000000000000000000000000 R
(1643782223.032415) can11 138#10000000 R
(1643782223.032492) can14 0B6##1E30A058005800003805A78000280028000000000000000000000000000000000 R
(1643782223.032515) can1 1BFDDA0A##1E48B8C2B80808080000000000000000000000000000000000000000000000000 R
(1643782223.032625) can1 09F##1950DFE4F006A80F0 R
(1643782223.032756) can4 09F##1950DFE4F006A80F0 R
(1643782223.032762) can14 09F##1950DFE4F006A80F0 R
leads to an assignment of can11 and can1 to the same CAN interface number 2
python-can/can/util.py
Line 284 in 4d9b32c
I did some tests with BLF/ASC/LOG conversions and discovered a problem with the latest develop branch (at least):
Usually the CAN interface names for SocketCAN look like
can0
,can1
,vcan12
and so on. The BLF to LOG conversion lead to CAN interface names that are numbers like1
,2
,33
- which is unusual but works too.When converting a LOG file to ASC the
channel2int()
function should assign unique CAN interface numbers for the converted CAN interfaces for the ASC file. In the logfile belowchannel2int()
maps two CAN interfacescan1
andcan11
to the same CAN interface number2
- which is definitely wrong:Converting a SocketCAN logfile with (unusual) numbers as CAN interface names:
results in
Which is ok!
Converting a SocketCAN logfile with usual CAN interface names (like
can3
):leads to an assignment of
can11
andcan1
to the same CAN interface number2
Which is wrong!
The text was updated successfully, but these errors were encountered: