HOLLEY TERMINATOR X SAFETIES TUTORIAL (NO ADVANCED TABLES NEEDED)
HTML-код
- Опубликовано: 22 окт 2024
- This is my tutorial on how to setup safeties for you guys who want them. The customization is endless and only limited by your imagintation. I know alot of guys are burning through their 1D and 2D tables trying to setup some basic safeties. For you guys doing that, you can get alllll those tables back and use them for the stuff you really want to use them for. Hope you guys enjoy, leave a comment and a like if this helped!
Thank you so much for dropping this info, im in a state of constant fear of blowing my motor and these safeties will give me some reassurance!
Great info, thanks for dropping science.
This is 90% how I do it, but with less triggers. But instead of the FP to boost table I have a table called FP Delta. There is a free spreadsheet on the FB Holley group. It calculates how much pressure you should have per boost. 1% duty cycle is 1 psi. So in theory it should always output 0%. -10% is a 10 psi loss. For a 43 psi base system -10% is where I turn the output on. The FP Delta PWM is also great for looking at logs and on your display instead of trying to do the math with fuel pressure. I usually do FP Delta, Duty cycle, Closed loop after its tuned (I do it a bit tighter), and oil pressure (based on datalogs). You can make the oil pressure more dynamic as well with another PWM output. You can also do that with target afr/actual afr, but I would rather cut the engine/revert to wastegate before it goes lean not after. One thing about the ignition cut is you need the outputs to turn off or you will have a permanent 2500 rpm limiter.
All of this is true, this was something I just threw together to show some examples. I know alot of people have been burning their 1D tables as ignition cuts and don't ever touch the I/O because they don't know how to use it. I like the FP delta PWM table and target vs actual afr. I'll probably use a time delay with target vs. actual afr though, don't want a single spark blowout or less than perfect accel enrichment to cut ignition. How are you cutting ignition before going lean, that one doesn't make sense to me. Good input on the additional PWM tables though, I dig it.
As for the ignition cut, it won't be permanent because the main safety output not only requires "something unsafe" but is anded to TPS (or accel pedal) & Boost & RPM in this case. So, if I could still drive the truck around as usual while still in an "unsafe condition", I just can't thrash it. The main thing to take away is you can combine a whole slew of things together and create 1 output, which you clearly understand. You clearly weren't the target audience lol.
@@scrapmetal_sleepers Well in theory if you compensate for small fuel pressure drops, and have safeties for a large pressure drop and 100% duty cycle (injectors going static), you should never go lean in the first place.
@@allansimonson8971 I see what you are saying, the IDC is another good one, I still have to build all the tables and logically organize it all but thank you for giving me some more things to add! Now to figure out why my Closed loop boost PID isn't working again, about to say screw it and go back to the target vs actual table.
@@scrapmetal_sleepers Thanks for the vid, you are very good at explaining things. Give me a shout on FB if you need help with anything.
This video is a hidden gem
Tell a friend!
Haha Boolean logic let's go! I knew I wanted termi but this just seals the deal.
Excellent content!
Thank you sir.
So if I wanted to make a table for anytime the car is running, not just when racing for if the fuel pumps getting tired or not working right, couldn't you do a setup like you did for the fuel pressure vs boost but then make that be what triggers the main safety? Instead of it being a linked output?
I'll PM you. I wouldn't want any safeties interfering with my actual driving, just in case of a faulty sensor. You could also have a safety override switch, or tied into lower boost numbers on your dialaboost
@@scrapmetal_sleepers idk if you can PM on youtube?! But I don't use it very often. Basically I have two fuel pumps on my car. And anytime I'm driving it, if I start to hammer on the car I want to make it so that if a pump has failed or is failing, it'll basically kill ignition when it starts to build boost. So I could still drive the car home NA and fix the issue, but I wont blow it up from a super lean condition.
The way I currently did it is I made a 2d table per Devin Vanderhoof thats fuel pressure vs RPM and did -4000 of a fuel offset above like 4000 rpms if the pressure drops bellow 35psi. But I feel like the safety setup to kill ignition may be a better way to do it.
At 6:39, you make the comment that with the linked outputs, you have to have a linked output trigger AND the "current" logic be true, for the current output to flag true. I believe that not to be the case. I've got some feedback from a gentlemen at Holley, that the linked outputs act as an "instant activation" type of relationship, rather than a logical qualifier. In your example here, that would imply that if either "AFR and Pressures", "FP to boost table", or "Knock Safety" are true, "Main Safety" will be true, regardless if it's internal logic has been met as true as well
I understand what you are saying however, in practice, I've seen first hand that both the criteria of the main output AND the linked output must be satisfied in order to trigger the main output. So while I may not have the Holley reps ear, I have experimented with this for some time. I've been using this on more than just safeties, including anti-theft, rolling antilag, etc. If the logic were not that way, my tables would be prematurely activated. I'm going to double check though because if I am completely wrong, then I have just been getting lucky. I'd rather be accurate, not lucky.
@@scrapmetal_sleepers That's honestly better news to me, as its more usable as a qualifier than an enable condition. If you do execute some follow up testing to confirm, please post your confirmations or findings here when you do. Would love to test myself, but unfortunately don't have the equipment setup for bench testing anymore
@@ProModsPerformance Ill set something up for when I leave work. I always have my laptop with me haha
@@ProModsPerformance I tested it out last night, Linked outputs are AND statements to the main output. For my test I created a "ground" output that activated when RPM was greater than 2500. I created a second "ground" output that was enabled when TPS was above 40%. The TPS based output used the RPM output as it's linked output. I have multiple instances where only one side of the equation is satisfied, and the output isn't, when both conditions are met (RPM>2500 and TPS>40%) the output is enabled. I doubt the Holley rep intentionally lied to you, but he is misinformed.
@@scrapmetal_sleepers Honestly, great news from my perspective. I have quite a few safety conditions that I wanted RPM as a qualifier for, so they didnt trigger in startup/stall conditions. Rather than having to make an individual output for each, with RPM as an "ANDed" enable condition, and then a separate output to Link all of them, I can Make ONE output, with my conditions ORed, and link that to ONE output who's criteria is simply my RPM qualifier. Super clean.
For na setups i cant add a boost table. It makes me switch to a 2 bar map
Did you find the answer from na car? Ran into the same 2 bar issue.