You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a kind of generic dbc-File for a couple of J1939-Messages. As far as I can see, the coding of the messages in the dbc file uses complete IDs, for example 0x8CF0047E. Now I have a machine that uses another source address and changes the priority resulting in message ID 0x0CF004F0, which seems to make the dbc file useless. I wonder if SavvyCAN could do the decoding just using the PGN part, 0xF004 in this case, so one dbc file would be usable independent of results of address claiming and manufacturer specific priority settings. Am I thinking wrong?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a kind of generic dbc-File for a couple of J1939-Messages. As far as I can see, the coding of the messages in the dbc file uses complete IDs, for example 0x8CF0047E. Now I have a machine that uses another source address and changes the priority resulting in message ID 0x0CF004F0, which seems to make the dbc file useless. I wonder if SavvyCAN could do the decoding just using the PGN part, 0xF004 in this case, so one dbc file would be usable independent of results of address claiming and manufacturer specific priority settings. Am I thinking wrong?
Beta Was this translation helpful? Give feedback.
All reactions