Open Elmue opened 1 week ago
This is fair feedback. It's desirable for other DBC tools to be able to open any of these files. Writing a DBC linter has been on our wishlist for a long time, see #579.
In terms of Vector official DBC format compliance, the generated DBCs are the worst offenders, because they're not composed in the right order and use invalid comments. But after that, details like the ones you name should be identified and cleaned up.
Is your tool something you plan to open source? If so, drop us a link. If it's simple and has few external dependencies, perhaps @adeebshihadeh could be persuaded to open a bounty to integrate it with opendbc CI. We could then start cleaning up these issues and prevent new errors from being merged.
Hello jyoung8607
Is your tool something you plan to open source?
It is not ready yet. I'am still working on it. I will implement it into the next version of my software HUD ECU Hacker which is charity-ware: https://netcult.ch/elmue/hud%20ecu%20hacker
I have been searching for a useful DBC parser on Github but I found nothing that I can use. Most are written in C or C++ or Python which is useless for me. I need C#. And mostly the error handling is implemented very poorly. So I wrote my own parser, which additionally is highly speed optimized.
I worked on it the last days and added more functionality. Now it even displays MUCH MORE errors!
I uploaded a beta version for you. Simply put it into a folder and the DBC files into the same folder. Then it will parse all files and show the results.
I followed the few rules with sparse descriptions in the PDF file from Vector Informatik GmbH. However this document is so poor that it is quite useless. But I implemented nearly all except Environment Variables. If a section is not checked a hint will be printed like "Section EV_ skipped". But in your files all sections are parsed.
If you should find any bugs please send me an email, which you see when you start the program.
You can download it here: https://netcult.ch/elmue/download/DBC_Parser.zip All you need is .NET framework 4.0 or higher.
And here a screenshot:
I uploaded a new version 1.1 which finds even more errors.
Hello
I wrote a DBC parser which prints a lot of errors when I feed it with your files.
For example in Mazda you have the line: BO_ 1178 2017_6: 8 XXX where "2017_6" is an invalid signal name. All identifiers must start with an alphanumeric character.