Closed surendrasah closed 4 years ago
Hi, The error trace is not complete or at least I hardly understand it, some copy paste mistake ? I do not think flexray is specifcally the reason why mdfreader is crashing, others reporting possible to do so from CANoE with also CAN etc.. why do you think so ?
Hi @ratal Thanks for the response. Would you be able to guide me which set of commands/code shall i use to read the flexray .mf4 file? 20161129_IN-x1234_Erprobungsort_0000032.zip this file is based on version 4. I guess, I am using the wrong commands to execute.
Hi, Thanks for sharing this file. There is indeed a bug. Mdfreader can read in general Flexray but your specific file has one composed channel (flexray) that is Variable Length. Current code is not including this corner case yet. I will check how to fix this.
I pushed a fix in dev branch, you could have a try. By the way I found malformed VLSD channel FLX_NullFrame.DataBytes completly null.
I just released version 3.3 that include the fix, you could more easily try it.
Thanks @ratal . I can get the signals from my file but not the required flexray signal. I guess its because there is no fibex parse available.
Indeed mdfreader does not parse fibex files. You get only the data the way it is written in the mdf file. So you do not have signal name alone but instead frameName.signalName
I do not plan to implement fibex parser but I guess data is anyway usable, closing
Python version
python 3.7
Description
I have recorded .mf4/mdf version 4 with FLEXARY on CANOE. Its not able to read the file. I am not sure if your program can read signal information from FLEXARY based .mf4.
====