RealDash_Holley EFI From DBC.xml (70.9 KB)
***UPDATE: see post below for a version with both targetId to match original and a named value. So you can choose which you prefer.
I took the DBC file Holley published a while back that has been floating around for the Holley terminator/dominator systems and changed it to RealDash XML. This adds quite a few additional IDs compared to the XML file built into RealDash ( and the XML file on the RealDash Extras Github page). 512 total IDs vs 276 IDs. The upside is it adds almost all the things you can see on the 3.5" screen, and some you can’t. The downside is it’s a LOT more to scroll through in RD to find stuff if you don’t know what to search for.
A few things to make it backward compatible with what is in RD default:
- if a targetID was defined in the existing, I did not give a name but kept the targetID so nothing would break
- if a name had been changed from what was in the DBC file, I changed the name to match what is in the RD xml file so nothing would break
That doesn’t mean I didn’t miss something and something might break, so let me know if I missed something.
1 Like
I updated the file. I had targetID instead of targetId
Thank you for sharing, I will take a look and probably update it to next release.
I created a new version that has both a mapped targetId where the original had one, and also adds the name version to those too. I’ve found in some cases when I map to a targetId the data doesn’t make sense, but when I map directly to a named value it works fine. For example, fuel pressure. I’m not sure why, maybe RD is doing some calculations are units are getting things off, but it has occurred a few times.
So I created another version with both for those that have a targetId mapped. I’ll test it tonight and share here in case it helps anyone.
RealDash_Holley EFI From DBC_ver2.xml (73.8 KB)
This version has the named and targetId versions. So all frames have a name version. The ones that had a targetId in the original built in version still have that too.
Why do you need custom input for all values?
Do you mean why I added the “name” in addition to the “targetId” for those that aleady had a targetId? if so, it’s just adding the option to use that instead of the built in identifier. I’ve had issues for some when I use the identifier (targetId) but if I map it to the name directly it works fine. Fuel Pressure was the latest. Works fine if I map it to the named input. Gives incorrect numbers if I use the built in field mapped with the targetId. Other fields work without issue when using targetId.
The two xml files above have all the same fields. The second just adds the “name” in addition to the targetId for those that just had a targetId.
I would rather fix the issues than introduce dual set of inputs.
Let me know when you find and fix it. For now, dash is working great so I’ll keep it as-is.
I actually am working on this to get my ethanol content values in my car, I see your file is much more encompassing. But I’m guessing there’s an issue with my version of realdash since I’m no longer seeing any data. I’m going to try adding in my baseId to the file and see if it works.
RealDash_Holley EFI From DBC_ver2.xml (73.9 KB)
Ethanol content on terminators would come in through an input. Are you able to datalog in Holley and see the %? If so, try to just map to the input directly instead of feeding through a targetid and see if that works.
It’s a weird way that holley processes the information. Yes, it’s via a input. But I had tried all the “2” inputs but couldn’t find any sort of data. The GM flex fuel sensor output is a frequency, so I don’t think it’d be usable to realdash. That said, the way people “read” the data on the holley side is with a 1D advanced ICF. Then plug in the table into the holley display. I believe this is the bit of data I’m after. (I did confirm that adding in a digital menu on my 3.5" display for AT 1D4 did display the ethanol value)
<frame id="0x1E435000" endianness="big">
<value name="Holley EFI: ADV_AT_1D4" offset="0" length="4" float="true"/>
That said, I’ve gotta figure out why I now have NO data at all from the holley side of things.
I tried yesterday but the logs were only 1K in size. I tried to send them anyhow. Also emailed afterwards, haven’t heard anything though.
Been somewhat busy, I try to take a look within next few days.
1 Like