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

SG_MUL_VAL_ need to be grouped using message id as well #116

Closed
bmcpt opened this issue Aug 17, 2022 · 0 comments · Fixed by #117
Closed

SG_MUL_VAL_ need to be grouped using message id as well #116

bmcpt opened this issue Aug 17, 2022 · 0 comments · Fixed by #117

Comments

@bmcpt
Copy link
Contributor

bmcpt commented Aug 17, 2022

If the following file is parsed using dbcppp, the New_Signal_4 multiplexer value will be applied to signal of New_Message_4 as well, even though it's message id doesn't match.

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_ 2348873389 New_Message_1: 1024 Vector__XXX
 SG_ New_Signal_4 m0 : 32|8@1- (1,0) [0|0] "" Vector__XXX
 SG_ New_Signal_3 : 48|8@1- (1,0) [0|0] "" Vector__XXX
 SG_ New_Signal_2 m0M : 24|8@1- (1,0) [0|0] "" Vector__XXX
 SG_ New_Signal_1 M : 0|24@1- (1,0) [0|0] "" Vector__XXX

BO_ 2348941054 New_Message_4: 8 Vector__XXX
 SG_ New_Signal_4 : 0|8@1- (1,0) [0|0] "" Vector__XXX


SG_MUL_VAL_ 2348873389 New_Signal_4 New_Signal_2 0-0;
SG_MUL_VAL_ 2348873389 New_Signal_2 New_Signal_1 1-1, 2-1, 5-7;
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

Successfully merging a pull request may close this issue.

1 participant