Holley efi can and dbc

General
42

Yes, on Linux, Raspberry Pi OS latest. Rpi 5 16gb. Two SocketCAN inputs. One from Holley and one from BMW K-Can (for car stuff like fuel level, etc). Works perfectly and very smooth.

I haven’t had a chance to go out and test without the BaseId. I’ll try it. I can’t remember if I did.

44

So I did two tests:

  1. Using the built in Holley: HP Dominator & Terminator x selection in the garage —> works just choosing it and seems to mask the bits for the baseId.

  2. used the xml file from Github dominator_and_terminator_x_can.xml → works fine without baseId.

So this confirms it is masking the baseId bits correctly. Sorry for the confusion.

45

Alright, thank you for verifying this. I also tested on simulator and it was masking the CAN id correctly.

1 Like
46

So, to expand this a bit more. Could we start writing messages back to the holley on the canbus? I believe you can use the prodash button setting in the software.

image
image1920×1040 223 KB

2 Likes
47

Sure, as there is working CAN connection, you can also send CAN frames from RealDash to Holley. There are multiple options:

  • Use ‘Send CAN Frame’ action to send a static frame.
  • Describe your custom CAN frames that are sent by RealDash in your XML file. Then make a button or trigger to change the value that is in XML file. When value changes, its associated CAN frame is automatically written to CAN bus.
  • You can also use ‘writeInterval’ attribute on your custom frames to periodically send the values from RealDash to CAN device.
48

hello i want to do the same go from realdash button to a holley input so if i want to use input #1 i would use 0x1E4A9000
i will be trying this weekend

49

I have tried setting up the Holley to read a Real Dash switch input using LCD input as the input device with no luck. There is a few different lcd screen to choose from so I’ve tried a few and nothing so has anyone got this to work ? I was thinking does Holley read there lcd screens with a different Can ID’s # like with Holley Can I/O add-on module it needs a serial ID# or is there something I’m missing ?

Thanks

50

One thing comes to mind. If you extent the Holley XML with customization, please note that last hexadecimal XXX of the CAN ID is masked out. So CAN ID:s that use those last 3 hex values are masked out and will not work.

51

Yes in my case it’s 621 I have only been trying it in can monitor page and savvy can
Thanks I’ll keep trying

One thing on Holley Can expansion module it also needs a can ID# and happened to have a Holley add-on can I/o expansion module I unplug it from the system and powered it up by it self and hookup the can I/o to savvy can I get no signal even on a oscilloscope all I get the can signal goes high +5. l was hopping to see how Holley deals with it own I/o I would guess it needs an input to wake it up ??? Or it’s on a different level

52

We do not have any Holley devices to test on, so we are solely relying on RealDash users to help on these connections.

I think I can do something about CAN ID masking so that you could use unmasked CAN IDs on same XML file. Let me think about it.

53

So I’ve added a flex fuel sensor to my setup. It’s connected to the I/O plug on input #2. The holley gauge panel in the software sees it and reports it correctly with a percentage value. Anyone have any ideas of what source to pick to display that value in realdash?

54

So, here’s how it can be viewed from the 3.5" and other holley dashes.

It’s coming from a advanced table. I know the sensor reads from a frequency, so I’m guessing there’s some math happening within the holley side of things. I guess since it’s being displayed on the dash, it’s put out there on the can bus as a value. I’m guessing we’ll have to modify the xml to add a value for it. Also I’m guessing it’ll be kinda problematic since this is something that can be setup dozens of different ways.

56

Well I’ve managed to completely screw up my dash I’m afraid. I’ve tried all the xml files I’ve post here, as well as the ones already published. I am getting data over the interface using the can monitor. Just zero data populating my dash.

I’m running the latest version of the APK from the dropbox. (v249-rc1)

I’ve tried adding to files as well as that previously got mine to work correctly. Also tried the holley terminator from the drop down list.

Realdash works fine with my dashbox and it’s updating the screen correctly.

I’m kinda at a loss what’s gone wrong. I also noticed that my speedo mileage went from 6 miles to like 217 miles.

Edit: none of the later xml files work. But the very old holley_efi_can.xml file DOES work with an updated baseId.

Edit: if I edit that file to try to include the extra frame id I’m looking for, it no longer works. Here’s a copy of it edited to just my baseId and the one extra frame id.

holley_efi_can(3).xml (9.8 KB)

57

We are investigating this issue.

58

Let me know if you’d like me to pull a log or anything off my devices. I also tried it on a tablet and it gave the same result.

Anyone have any pointers for me as a work around for the time being on how to use the old holley_efi_can xml and get it to play nice with the one last frame ID I’m looking for? I also tried changing the end of it’s frame from float=“true”/ to conversion=“V*0.00390625”/ like the other frames.

Or alternatively, everyone else that’s running the other xml files, are you running the dropbox v249-rc1 that is most recent? Or running the app store version of real dash? Just trying to sort out the difference why mine doesn’t work when others do.

Also, what are you using on your dash for the data sources? Are you just using the generic ecu data or are you going in gauge by gauge and pointing them to the specific holley data points?

Edit: for the time being, I went back to the holley_efi_can xml to get my dash working again. After a lot of poking and prodding I found out the input #1 actually puts out the data I’m after and that works under the old xml file. So I’m “working” now for everything I’m after. But I still would like to not have to use the old xml file and in the future it’d be nice to have access to all the data points.

59

Could you try RealDash-v249-rc3.apk from Dropbox.

60

Installed. Works with my modified old xml. Doesn’t work with the included terminator/dominator file from the list. Should I try downloading the xml from the github and see if that makes any sort of difference?

61

It should not make any difference.

This is bit of a mystery, we tested the CAN connection with all our adapters and simulators, including couple of real ECUs and found zero issues.

62

If there’s anything I can run or files to share please let me know.

I do have a question for the ones that are working with the newer xml/versions. What is your holley setup? I think I might be the only one running a Holley Terminator X Max, but that’s really only an expansion of the normal terminator to run the transmission control.

Also what type of interface are you running? I’m using one of the generic slcan interfaces with slcan 6/29/2023 version firmware.

63

So that reminded me, mine wouldn’t work until I flashed the slcan firmware. I flashed it back to the candlelight firmware and it won’t talk to the holley. I guess maybe I’ve got some sort of issue with the interface and the real dash code. I guess I need to try a different interface.