Got fed up trying to hand copy definitions I already have in DBC over to realdash format.
I have written a converter that will do this automatically. I’ve tested on some files I have, and seems OK for most cases. Seems to do a good job with the 301 signals in the full MegaSquirt DBC. No multiplexing as yet, I’ll get to it eventually
Output files are saved in the DBC path.
In theory it should work with DBC, KCD, SYM, ARXML 4 and CDD formats
Added support for realdash enumerated values where lookups exist in the DBC. It will create a second signal with suffix _enum. Also moved to bitstart and bit count rather than offset and length. This should allows signals that overlap partial bytes. @jani -I wasn’t sure if there was a way to have enumerated values in the same signal (and then just have realdash allow choice of numerical or lookup values) can you confirm?
Thanks so much for attempting this. I just wanted to let you know i did try converting a DBC file from the below link.
Unfortunately nothing works in realdash. I dont think its your script, its the DBC file is not formatted in a way to link up with the Realdash target ids.
If I am understanding your issue - It won’t link to default built in realdash IDs like RPM/speed etc (too many permutations to know what part of your DBC should go to which!) They all come in as custom (named from the DBC) values - you just need to choose the those data channels for each gauge by editing the dash… (Or just tweak the XML file once converted to change <value name=“” to <value targetId=“” for the signals you want attached to the default ones in RD)
