-
Notifications
You must be signed in to change notification settings - Fork 506
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
CAN dbc not converted to dbf #980
Comments
To analyze the issue, please provide the below details:
|
Hi, This is not the solution though. There is some kind of name abbreviation scheme in dbc that is not considered by the converter tool. There is a list of all message names but later a trunkated name appears, sometimes with the ending _0000 and _0001 etc.. Sometime the name is cut. So CANdb++ editor resolved this, when I saved it again it resolved all these, and the full name is used now. My 800 kB dbc grew to about 900kB. I can't currently attach an example, because it was from some proprietary project. UPDATE: I thought the issue was that the signal names were sometimes more than 32 characters long.. this is not the case. However in the beginning of the file there is a listing: NS_: the issue in my case turned out to be that our generated file had a single space in front of NS_DESC_, CM_ etc.. and CANdb++ editor would use a single \t character. This difference causes the conversion to fail. |
@whitefalk just have a look at the PR #1184 |
Hello,
I converted my CAN dbc to dbf using BUSMASTER converter tool.
When I assigned this dbf to BUSMASTER,it shows no message and signal in the busmaster. Eventhough the dbf file is no blank.
please help.
The text was updated successfully, but these errors were encountered: