Figured I'd start a more dedicated thread - @knuckle47 's issues here just happened to coincide with me recently diving back deep into the land of Holley. I'm not fully done, but progress has been good so figured I'd socialize and share. The more we can all partner and collab, the more we all can learn and avoid reinventing the wheel every time.
One bit of learning that started all of this - AI/Large Language Models do help a ton with drive log parsing, and it's helped me dial in a lot of the finer settings with more precision and more quickly. I still have some areas to go, but it's more the edge cases. Mostly acceleration enrichment while still warming up (as you only get one shot per day really), and possibly a few pockets of AFR and timing twiddles, mostly up at WOT a-la a dyno pull. At this point, it's getting pretty darn dialed in, though.
A lot of the fuel settings should also work for the standard coil (non-Hyperspark) installations, and I attached a version of that --- but I have no way to validate that, so use at your own risk. And for either variant, save your current config before replacing to allow you to return back to what you had prior if needed.
I basically gave my Holley+Hyperspark tune to @knuckle47 as-is, and it seems like it settled in pretty quickly, so there is some promise here I think.
NOTE: the VE (volumetric efficiency) table signature will likely be somewhat engine and install specific based on how your engine breathes and how your fuel system/injectors perform to spec. Ideally, users should retain their own VE table built from driving and layer that into this tune -- it will re-self-learn, but keeping your VE table would minimize that.
I did setup a Github project to track my progress - my latest copy is here, and future changes would get pushed here as well:
github.com
One other (early) finding so far - my install used a pretty typical "dogbone" adapter from the factory heat shield/phenolic spacer to mate the 2300 to the factory spacing. However, that had negative impacts to air velocity at full throttle due to the "two barrels => open adapter => two barrel riser => manifold", made worse by the way an inline 6 manifold flows. I modeled a two port taper-bore "velocity stack" style adapter and gave it a test run in plastic - much better so far. I sent it off to a commercial printer that can do sintered aluminum - curious how well it comes back. That file is also in the Github repo if it pans out.
If anyone wants to try, have at it and give a shout here (but again, all at your own risk). If needed, can also help with a VE-table merge if unfamiliar with the software. (Time permitting of course)
Happy driving...
One bit of learning that started all of this - AI/Large Language Models do help a ton with drive log parsing, and it's helped me dial in a lot of the finer settings with more precision and more quickly. I still have some areas to go, but it's more the edge cases. Mostly acceleration enrichment while still warming up (as you only get one shot per day really), and possibly a few pockets of AFR and timing twiddles, mostly up at WOT a-la a dyno pull. At this point, it's getting pretty darn dialed in, though.
A lot of the fuel settings should also work for the standard coil (non-Hyperspark) installations, and I attached a version of that --- but I have no way to validate that, so use at your own risk. And for either variant, save your current config before replacing to allow you to return back to what you had prior if needed.
I basically gave my Holley+Hyperspark tune to @knuckle47 as-is, and it seems like it settled in pretty quickly, so there is some promise here I think.
NOTE: the VE (volumetric efficiency) table signature will likely be somewhat engine and install specific based on how your engine breathes and how your fuel system/injectors perform to spec. Ideally, users should retain their own VE table built from driving and layer that into this tune -- it will re-self-learn, but keeping your VE table would minimize that.
I did setup a Github project to track my progress - my latest copy is here, and future changes would get pushed here as well:
Releases · lonewolfworks/holley-sniper-oss
OSS Holley Sniper Info - Tunes, Hardware. Contribute to lonewolfworks/holley-sniper-oss development by creating an account on GitHub.
github.com
One other (early) finding so far - my install used a pretty typical "dogbone" adapter from the factory heat shield/phenolic spacer to mate the 2300 to the factory spacing. However, that had negative impacts to air velocity at full throttle due to the "two barrels => open adapter => two barrel riser => manifold", made worse by the way an inline 6 manifold flows. I modeled a two port taper-bore "velocity stack" style adapter and gave it a test run in plastic - much better so far. I sent it off to a commercial printer that can do sintered aluminum - curious how well it comes back. That file is also in the Github repo if it pans out.
If anyone wants to try, have at it and give a shout here (but again, all at your own risk). If needed, can also help with a VE-table merge if unfamiliar with the software. (Time permitting of course)
Happy driving...
