Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

During importing of dbc/trc files, call to mexParseCANMessageLogFile always returns empty #1

Open
snoop911 opened this issue Nov 23, 2023 · 1 comment

Comments

@snoop911
Copy link

When I run the script, it gets the 1.trc file
(
;$FILEVERSION=1.1
;$STARTTIME=45252.6317937269
;
; Generated by PCAN-View v5.1.1.908
;
; Message Number
; | Time Offset (ms)
; | | Type
; | | | ID (hex)
; | | | | Data Length
; | | | | | Data Bytes (hex) ...
; | | | | | |
;---+-- ----+---- --+-- ----+--- + -+ -- -- -- -- -- -- --
1) 6379.3 Tx 0016 8 15 22 33 44 55 06 00 00
2) 6683.2 Tx 0016 8 15 22 33 44 55 06 00 00
3) 6899.0 Tx 0016 8 15 22 33 44 55 06 00 00
4) 7114.3 Tx 0016 8 15 22 33 44 55 06 00 00
etc
)

and generates Converted_1.asc
(
6.379300 Tx 0016 8 d 15 22 33 44 55 06 00 00
12.015200 Tx 0016 8 d 15 22 33 44 55 06 00 00
12.048500 Tx 0016 8 d 15 22 33 44 55 06 00 00
32.699300 Tx 0016 8 d 10 22 33 44 55 06 00 00
32.891000 Tx 0016 8 d 10 22 33 44 55 06 00 00
33.235100 Tx 0016 8 d 10 22 33 44 55 06 00 00
46.963600 Tx 0016 8 d 03 22 33 44 55 06 00 00
47.029400 Tx 0016 8 d 03 22 33 44 55 06 00 00
47.062400 Tx 0016 8 d 03 22 33 44 55 06 00 00
47.095600 Tx 0016 8 d 03 22 33 44 55 06 00 00
47.195400 Tx 0016 8 d 03 22 33 44 55 06 00 00
47.227500 Tx 0016 8 d 03 22 33 44 55 06 00 00
47.260500 Tx 0016 8 d 03 22 33 44 55 06 00 00
71.625800 Tx 0016 8 d 36 22 33 44 55 06 00 00
71.658800 Tx 0016 8 d 36 22 33 44 55 06 00 00
71.692900 Tx 0016 8 d 36 22 33 44 55 06 00 00
76.712400 Tx 0016 8 d 10 22 33 44 55 06 00 00
76.745200 Tx 0016 8 d 10 22 33 44 55 06 00 00
76.778100 Tx 0016 8 d 10 22 33 44 55 06 00 00
76.811000 Tx 0016 8 d 10 22 33 44 55 06 00 00
)

The dbc file contains a message/signal
VERSION ""
NS_ :
NS_DESC_
CM_
BA_DEF_
BA_
VAL_
CAT_DEF_
CAT_
FILTER
BA_DEF_DEF_
EV_DATA_
ENVVAR_DATA_
SGTYPE_
SGTYPE_VAL_
BA_DEF_SGTYPE_
BA_SGTYPE_
SIG_TYPE_REF_
VAL_TABLE_
SIG_GROUP_
SIG_VALTYPE_
SIGTYPE_VALTYPE_
BO_TX_BU_
BA_DEF_REL_
BA_REL_
BA_DEF_DEF_REL_
BU_SG_REL_
BU_EV_REL_
BU_BO_REL_
SG_MUL_VAL_
BS_:
BU_:
BO_ 22 NewMessage_0001: 8 Vector__XXX
SG_ NewSignal_0001 : 7|8@0+ (1,0) [0|0] "" Vector__XXX

The message_list.txt contains that message:
NewMessage_0001

However, stepping into trc_dbc2csv line 83
log = canMessageImport(converted_trace, 'Vector', canDatabase(input_dbc));

It calls
[status, importedMsgStructs, messageCount] = mexParseCANMessageLogFile (fullFilePath, vendor);
Unfortunately, while the full path to Converted_1.asc is correct, and contains the data above, the mex file always returns a messageCount of 0

@snoop911 snoop911 changed the title During improting o f dbc/trc files call to mexParseCANMessageLogFile always returns empty During improting of dbc/trc files, call to mexParseCANMessageLogFile always returns empty Nov 23, 2023
@snoop911 snoop911 changed the title During improting of dbc/trc files, call to mexParseCANMessageLogFile always returns empty During importing of dbc/trc files, call to mexParseCANMessageLogFile always returns empty Nov 23, 2023
@whitemoyu
Copy link

I have met the same problem.But I can't open the function "mexParseCANMessageLogFile".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants