Fields in multiplexor message get renamed when exporting to dbc

Professional Windows® software to communicate with CAN and CAN FD busses and its add-ins: Plotter, CANdb Import, Instruments Panel, and J1939
Post Reply
joejh
Posts: 3
Joined: Mon 5. Apr 2021, 22:12

Fields in multiplexor message get renamed when exporting to dbc

Post by joejh » Mon 5. Apr 2021, 22:17

When I export the attached AQ_V6.sym to a dbc it renames fields in the multiplexed messages, how do I stop it from doing this. I have attached the 2 files, the AQ_V6.dbc is exported from PCAN using the sym to dbc tool.

Thanks
Attachments
AQ_V6.sym
(9 KiB) Downloaded 300 times
AQ_V6.dbc
(6.45 KiB) Downloaded 288 times

M.Riedl
Software Development
Software Development
Posts: 34
Joined: Wed 22. Sep 2010, 13:28

Re: Fields in multiplexor message get renamed when exporting to dbc

Post by M.Riedl » Tue 6. Apr 2021, 15:58

Hi,

Thank you for the hint.

If you mean the names of the signals with
fields in the multiplexed messages
This seems to be an an old automatism to prevent double signal names.
If a signal is used in more than one multiplexer and not in all multiplexers of the symbol, the multiplexer value is appended to the signal name.

Right now, you can't stop this behavior.
But we will investigate and correct it if necessary.

Best regards
M.Riedl

joejh
Posts: 3
Joined: Mon 5. Apr 2021, 22:12

Re: Fields in multiplexor message get renamed when exporting to dbc

Post by joejh » Mon 7. Jun 2021, 20:13

Yes I would very much like this fixed as i have to hand correct all of the exported dbc's at the moment...

would this be possible?

joejh
Posts: 3
Joined: Mon 5. Apr 2021, 22:12

Re: Fields in multiplexor message get renamed when exporting to dbc

Post by joejh » Mon 7. Jun 2021, 20:20

It also duplicates value tables too...
Attachments
multiple tables.PNG
multiple tables.PNG (51.07 KiB) Viewed 4128 times

M.Riedl
Software Development
Software Development
Posts: 34
Joined: Wed 22. Sep 2010, 13:28

Re: Fields in multiplexor message get renamed when exporting to dbc

Post by M.Riedl » Wed 9. Jun 2021, 11:38

Hi,
joejh wrote:
Mon 7. Jun 2021, 20:20
It also duplicates value tables too...
This is a normal behavior.

In the CANdb++ Editor, each value table that you assign to a signal is duplicated when the DBC file is saved. This seems to be the only way to connect a table to a signal in the current DBC file format.

Sample:

Code: Select all

VAL_TABLE_ New_Value_Table_1 2 "Description for the value '0x2'" 1 "Description for the value '0x1'" 0 "Description for the value '0x0'" ;
...
BO_ 0 New_Message_1: 8 Vector__XXX
 SG_ New_Signal_2 : 8|8@1- (1,0) [0|0] "" Vector__XXX
 SG_ New_Signal_1 : 0|8@1- (1,0) [0|0] "" Vector__XXX
...
VAL_ 0 New_Signal_2 2 "Description for the value '0x2'" 1 "Description for the value '0x1'" 0 "Description for the value '0x0'" ;
VAL_ 0 New_Signal_1 2 "Description for the value '0x2'" 1 "Description for the value '0x1'" 0 "Description for the value '0x0'" ;
I have tested the behavior again with the lastet CANdb++ Editor (Version 3.1.9).

Best regards
M.Riedl

Post Reply