asammdf icon indicating copy to clipboard operation
asammdf copied to clipboard

Output mismatch from extract_can_logging and extract_bus_logging ?

Open ssat24 opened this issue 2 years ago • 3 comments

Python version

Please run the following snippet and write the output here

import platform
import sys
from pprint import pprint

pprint("python=" + sys.version)
pprint("os=" + platform.platform())

try:
    import numpy
    pprint("numpy=" + numpy.__version__)
except ImportError:
    pass

try:
    import asammdf
    pprint("asammdf=" + asammdf.__version__)
except ImportError:
    pass

Code

MDF version

_please write here the file version (you can run print(MDF(file).version))

Code snippet

please write here the code snippet that triggers the error

Traceback

please write here the error traceback

Description

The fastest way to debug is to have the original file. For data protection you can use the static method scramble to scramble all text blocks, and send the scrambled file by e-mail.

I have a MF4 file, in which there are some CAN.ErrorFrame. I load it with latest version and use extract_bus_logging. It is giving wrong output. When I load the same data in asammdf(version=5.21.0), and module extract_can_logging is giving right output. Can anyone explain the reason for this ? How to deal with CAN.ErrorFrame ?

ssat24 avatar Mar 30 '23 19:03 ssat24

I have a MF4 file, in which there are some CAN.ErrorFrame. I load it with latest version and use extract_bus_logging. It is giving wrong output. When I load the same data in asammdf(version=5.21.0), and module extract_can_logging is giving right output. Can anyone explain the reason for this ? How to deal with CAN.ErrorFrame ?

ssat24 avatar Mar 30 '23 19:03 ssat24

Can you send a file via e-amil and point me to the wrongly decoded signals?

danielhrisca avatar Mar 31 '23 05:03 danielhrisca

Sure !! Thanks, a lot !!

ssat24 avatar Apr 04 '23 19:04 ssat24