DIY FBody PiggyBack Harness
The Jolt harness is a "trimmed down" factory harness with needed connections to keep the rest of the car working. The Holley harness is integrated into that, so there is no need to buy a main harness.
The stock PCM stays in its location. The harness is long enough to put the Holley ECU behind the glove box or behind the passenger kick panel.
As long as the work is quality, I told him he should have no problems staying busy.
The Jolt harness is a "trimmed down" factory harness with needed connections to keep the rest of the car working. The Holley harness is integrated into that, so there is no need to buy a main harness.
The stock PCM stays in its location. The harness is long enough to put the Holley ECU behind the glove box or behind the passenger kick panel.
As long as the work is quality, I told him he should have no problems staying busy.
The kit is used is a loom kit. Part number is 555-10659. I used the factory wires - just straightened them out and rebundled them how I felt they would run best through the engine bay. I figure if it doesn't work I can always just get the current performance harness. I just kind of wanted to try it myself. Mainly because I was scared to try it, and I don't like being afraid of anything. Face your fear kind of thing.
But honestly, I think it will work just fine. My biggest thing is I think I messed up on how I routed the coolant temp sensor and the evap connectors. if I have to, I'll leave the evap unplugged so I can test out the coolant temp triggering the fans. If that doesn't work out like I hope, then I think I can figure out how to make the holley trigger the fans for me. Just gotta ID the right wire on the chassis side. And that info is out there. I've seen it in various threads.
To avoid sending people down the re-read rabbit hole, the first swap to the current heads, I missed a lifter cup, and the pushrod bent, scissored the link bar, which broke it, and punched a hole in the intake runner of the head to the intake galley. We patched the head with epoxy, but during the inspection process, we found that the motor was junked, so we built a whole new bottom end. After getting it up and running, the car dyno'd 693 at the tires NA, but the motor was smoking like a chimney. Upon further inspection, we found that the epoxy patch had not fully sealed, and was sucking oil into the running. But I was smart and put the patched head on the driver side so it was easier to pull just in case. While the head was off to be re-patched, I decided to swap over to the Holley ECU. Mechanically, everything was back together other than a few odds and ends. I hope that's enough backstory. Trying to stay on topic.
Initially, the car would crank but not start. Noid light found injectors not pulsing. Spare spark plug on the cylinder head found coils not firing. I missed the smaller red wire. I had run it in a loom to the batter, but had not hooked it up, and it fell out of sight. Hooked it to the battery, and the car would fire for a few seconds and die. Very quickly determined the fuel pump was not staying on after it started. The holley harness comes with a green FP trigger wire that you can tap into the C101 connecter - green and white wire on terminal D. I went ahead and did that to keep the fuel pump running, and sure enough, the car started and stayed running. The idle was actually tamer than it was on the stock ECU.
The holley software is very different from HPTuners / OE computer. There are tables altogether "missing" from the holley, but the tables that are present can be reconfigured easily. For example, on the VE table, you can just change the RPM and MAP axis values to whatever you want. It appears to be far less tricky to set it up for open loop idle and closed loop cruising.
Anywho.... after I got the car running and idling, I let it warm up. everything on the stock gauge appears to be working except the tach - as I mentioned before, I think I have a crank signal issue. That aside, the other thing was the cooling fans did not come on. I believe that - similar to the fuel pump - the ecu does not see the car as "running" so it is not controlling the fans properly. I might chase this down a little bit, but if I cannot solve it quickly, I will run a separate trigger wire from the holley to the stock wiring harness and let the holley control the fans. I have considered the possibility that it's just too much signal conversion with three different systems using the crank trigger, and if that's the case, then my stock harness experiment might be over. honestly, if both were 24x, i think it would have worked fine.
I'm sorry it was so long. I know I have owed you guys answers, and I finally have them - and some more work to do to iron it out.
The Best V8 Stories One Small Block at Time
Another option to look at may be to use the Holley tach output (I know it's a blue/white wire on the 24x harness, I'd imagine it's the same loose wire on the 58x) through a signal conditioner into the OEM computer input, something like the Dakota Digital SGI-100BT.
I know that you can split a hall-effect signal without issues, but the 2-wire signals that use pulsed ground output can get sketchy.
Additionally, to get oil pressure on the Holley too, you could always tee the factory OPSU and run a second LS type sender? Or tap the block off plate above the oil filter.
What's the intended purpose or desired end state for running the Holley, other than it being cool as hell to make it work? Performance goal, or built in data logging?
Additionally, to get oil pressure on the Holley too, you could always tee the factory OPSU and run a second LS type sender? Or tap the block off plate above the oil filter. I had thought about both. In the end, I would need to pull the intake manifold to get to the harness to extend it, and the only reason I would need oil pressure to the holley is if I upgrade the dash. If I get to that point, I'll just ditch the stock ECU altogether anyway. I cannot describe to you how much I really do not want to pull the intake right now.
What's the intended purpose or desired end state for running the Holley, other than it being cool as hell to make it work? Performance goal, or built in data logging?[/QUOTE]
Basically, it's this... I was running a custom OS, scaled tune, on a 1999 ECU trying to control an 8000+ rpm motor, and it's reaching up on too many issues. I really just want this thing to be a good street car that I can drive to the track, hit a 9, get tossed, and drive home. A la drag week. And yes, the built in datalogging and the ability to run closed loop off a wideband. And the easy with which I can run open loop at idle, customizable tables, add additional features later on, etc
Another option to look at may be to use the Holley tach output (I know it's a blue/white wire on the 24x harness, I'd imagine it's the same loose wire on the 58x) through a signal conditioner into the OEM computer input, something like the Dakota Digital SGI-100BT.
I know that you can split a hall-effect signal without issues, but the 2-wire signals that use pulsed ground output can get sketchy.
I'm curious as to the "tuning" that will need to happen with the OEM computer, are there any special considerations to keep it happy without it having the ability to make changes? Essentially it's just a monitor, however if something is set outside of its parameters on the Holley, do you have to re-tune the OEM computer?
By removing all the wires, the ECU will not see any sensor used to control the engine -- map, tps, iat, etc, so all those codes will be set. The ECU also will still internally switch for the spark and injector firing, but the switches won't go anywhere. This might mean I need to adjust all the misfire tables, because the engine won't act according to the stock ECU's commands. But as long as the stock ECU sees the crank signal, despite a severely high number of codes, it will see the engine is running and "assume" it is running the engine. So my plan is to simply disable all the codes that show up after the ECU is responding properly.
I figure that if this fix works, and I see the OE tach responding properly, I will let it warm up, and see if the cooling fans fire like they should. If they do, then I will know that the stock ECU is happy and I'll start disabling codes. I want to wait so I don't disable something I need to leave enabled, if that makes any sense.
By removing all the wires, the ECU will not see any sensor used to control the engine -- map, tps, iat, etc, so all those codes will be set. The ECU also will still internally switch for the spark and injector firing, but the switches won't go anywhere. This might mean I need to adjust all the misfire tables, because the engine won't act according to the stock ECU's commands. But as long as the stock ECU sees the crank signal, despite a severely high number of codes, it will see the engine is running and "assume" it is running the engine. So my plan is to simply disable all the codes that show up after the ECU is responding properly.
I figure that if this fix works, and I see the OE tach responding properly, I will let it warm up, and see if the cooling fans fire like they should. If they do, then I will know that the stock ECU is happy and I'll start disabling codes. I want to wait so I don't disable something I need to leave enabled, if that makes any sense.
9s in a three pedal street car, pretty stout for sure.
On another side note, do you still have ABS? If not, have you had any thoughts in trying to pull signals from the front and rear ABS sensors for VSS inputs to the Holley to be able to set up a more performance based traction control?









