we all should have known that the ol dual throttle body question would come up on this thread.... Methanol/water injection operates off of a simple tps switch or boost switch, retuning usually means pulling fuel back at the top to avoid overly rich but it's just an on off deal... no pulsing with it. Even still, doesnt cause a jolt or bog when tuned right..... I think just wiring in a tps switch to even allow the 2nd pair of injectors to fire could be tuned no problem. I would assume it would be fairly low setting too.... as close to idle as possible so the transition wasnt so critical. and fuel wouldnt HAVE to double when they came on right? at the exact point where the tps switch was set you could have 4 injectors pulse width change to compensate for 2 more workin? i'm so out of this game but...... my crazy half thoughts just flow out.

Not sure if this helps at all, but I found this in my 9C1's stock cal bin.



Looks to me that the lowest GM wanted the injectors to fire in regular mode (synch) is 0.85ms (850us). I screwed around with some of these a few months ago, trying to bring the ECM out of asynch at hot closed loop idle. I ended up resetting things back to stock as I think those settings are there for a reason. That reminds me - does anyone think it's odd that I have a hot closed loop idle in asynch mode with only 14psi of FP and the stock BPC?

Seems to me the only way dual TBIs and quad injectors would really solve any fueling problems is if 4 injector drivers are used, and they're fired independently in some kind of weird wet manifold sequential system. I mean, I consider the stock injector setup to be sequential. They don't fire in batch. Though you may be able to consider it a bank fire system.

im not sure if this has been touched on, so let me see if i can explain it right.
also im not into TBI & i may well be totally off in my thinking on this.
working with 2 ECMs seems like it would be a real pain to get right.
but how about just using 1 ECM & doing something like this,

my thinking is with 4 injectors you would need 4 drivers, 1 for each injector.
lets says on a stock 2 injector setup you fire each injector 2 times per engine revolution. you add 2 more injectors, which would give you twice the fuel. but now, instead of each injector firing 2 times per revolution, you fire each injector 1 time per revolution, wouldn't this be the same amount of fuel per revolution?
would this be an option, or am i out of bounds on my thinking?

with opening 4 throttle plates all at once, i can see a very touchy throttle doing it like this.

With twin TBI's, in my opinion, just using an additional PCM would be the easiest way. Its got all the driver hardware present and with some minimal code, you could command it via a serial link to fire the second set of injectors. All it would need is some power, the reference pulse, and both sync and async PWs. In asnyc mode, there would probably be some phasing between the two sets of injectors since they would fire at different times, but in async it probably wouldnt matter much, anyway.

Wow, blast from the past. Hiya's terryk
-Carl


p.s. Has the statute of limitations run out for a law suit :P

How about an update on the EBL........ Some feedback from the beta testers and when it might be ready or order ??

Nope, no update . No feedback , and it won't be ready to order until this thread gets 10,000 views. lol
To answer your questions; Bugs are being worked out and it's my slow arse that's holding things up. Every time I fix something, another thing breaks. I fear my job will never be done... Mark, how DO you do it?
Beta testers are communicating with ME and Bob, no need for any of you to know other than progress being made. If I went into the details it would take me longer.
I'll let Bob comment on the hardware side. My impression is that he's so confident that he's coming up with other stuff to do, like 4 TBI injector support.
Sorry guys, I'm doing my best.

Thanks Jon, I know you guys are working on it. Working in the software industry, I know what you are going thru. Don't rush this, just to get it out.

I'm really looking foward to seeing the 4bbl support if it works out.

JP would it be possible to include a dll with the info takken from EBL i will be running a carPC and want to customized the look and feel of things. this would come of course at a much later date after the bugs are worked
just wondering if it was a possibility

Feedback from the beta testers has been positive. One tester has been giving indirect feedback as he posted about the mileage has been improved. From another, quoted with permission: "I love the Launch Mode Spark and the AE routines in this code. Along with the better VE resolution, I seem to have more torque coming off the line and at Tip-In."

And: ". . .the new code runs the engine smoother than I have ever felt. It is super responsive, the TCC seems to work better, and the Highway mode works great. "

With the goal being a better running engine, that just about says it all. If the beta testers would like to add to this please do.

Thanks,

RBob.

Well, as one of the master betas for EBL, I can tell you the code and the higher baud rates are outstanding. Without question, the faster processor speed and the greater granularity for VE, SA and just about every other table makes this so much more responsive than the 7747 I was using. The motor just flat loves it if I can judge it by the sound of the exhaust. RBob warned me to watch first gear when I installed. Well, watch second gear too. I'm looking forward to doing a before/after comparing the 7747 ECM with the EBL at the track this spring. The EBL in combination with Craig's Ostrich is just terrific. Changing/modifying bins is a snap. I've been working with RBob on getting the Digital Dash Display dialed in and it works. Yeah!
The HUD software provides an incredible amount of data. Possibly too much for the initial effort.I'm using the RJ-11 to serial port connector, then going USB via the EASE scantool adapter I have. I tried the RS and Palm USB/Serial adapters with no luck. Having run software product management organizations, I can say that the areas still needing attention are:

1. Facilitating the use of analytical tools like .xls. Right now there doesn't appear to be a way of importing HUD generated data into Excel for instance.

2. Documentation - RBob provided extensive documentation on the EBL code. I've suggested providing some kind of Xref between it and other masks. That could be a done thru the users themselves. HUD needs documentation. Some of the feature/functionality doesn't seem accessible, at least its not apparent on how to modify the Line Charts, for example.

3. I'm all for minimizing feature creep, but I think that with a modded motor, using a WB to tune becomes essential. That's why I would encourage Jon to allow use of alternative input to the "Learn" function. Specify whether you want to use BLM/INT or WB and then the target # ie +/- 128 or +/- 14.7.

To recap, here's my setup using EBL:

84 Xfire Corvette manifold ported and Extrude Honed, lidspacer, w //plumbed 2.13" TBs. 80# Injectors at 20psi.
TFS 23D heads, CompCams HydRlr 269 @ .006 w 528 lift, 108d LCA, TPIS headers, Random Tech Cat, Magnaflow Cat back
ZF-6 Trans-plant/Fidanza Aluminum FW/SLP Camaro disc, D44 3.42 rear, ZR-1 17x 9"F/11"R wheels
ZT-2 WB O2, Moates Ostrich, TP RT
13.3@102.1

My engine is running smoother than it ever has with TBI, has better response, and improved mileage. The highway mode is working well for me. I briefly flirted with the N-Alpha mode as well. Found out that I simply did not need it.

The electric fan control works great for me. It works much better than the aftermarket controllers do, mainly by allowing the fans to turn off at a certain vehicle speed.

In Texas it has been in the 80's lately and response with the A/C running is greatly increased with the Smart A/C clutch control.

PE mode now lights a yellow light to warn of excessive fuel consumption.

I also have a shift light hooked to the shift light output and have gotten rid of the tach.

I run a VAFPR though not made by GM, 32 psi of fuel pressure @ WOT, and 68 lb/hr injectors.

I passed a smog inspection easily, despite a cam that only makes 10 in/hg of vacuum at idle.

I absolutely love the amount of quality data that comes out of the EBL with the HUD. You can actually see the pumpshot or AE. I ran it for a 140 mile trip and literally looked over data for hours. After 140 miles it ran darn near perfect.

The MPG calculations are spot on for me.

Here is my setup

305 bored .040" over, ported 081 305 TPI heads, Big Roller cam, Cast Iron exhaust manifolds, Holley Projection intake, 454 TBI, 68# 350 injectors, lots more.

This is great news, glad to hear everyone is having positive results. Man I wish I had a running vehicle to play with

Just to confirm everyones WAG's I have a TPI manifold that I am running with a 8746 I havent been able to find any unbalance issues yet, recently eldebrock has released a simialar system also, lacking their funding I haent been able to write a prom for it yet.

I know very little of the computer world, never used one till last year, I took the leap and bought an AutoProm and it came with TunerPro, there were problems with the 160 baud stuff at first, but Mansur and Moates put their heads together and fixed it.. Thats a big deal to me.Too much of the hotrod stuff is just touggh titty if it doesn't work. I've used the combo for a year and am really impressed with the capability of the program. you can add to the xdf and data stream def as you stumble onto more stuff, tweaking the tables is really easy with all sorts of goodies in the editor toolbox.. It's easily the best 30 bucks I've spent in a very long time.. The AutoProm has worked every time, and man, I've erased + burned a slew of chips with it. Both high ouality tools.

Was there a comment on the EBL/HUD you wanted to make?

Regarding the dual TBI thing and fueling.

Could Kurt staging be implemented?

http://www.megasquirt.info/Code.htm#kurt

Maybe wire it up so one injector from the rear TBI and one injector from the front TBI are on the same driver. Maybe alternate sides (diagonal).

Kurt spacing

I was thinking the exact same thing - you'd have to use an open spacer between the carb pad and the TBI adapter so you'd be able to feed all four cylinders (in the case of a dual quad intake), but then allow the other injector to come on when desired.

Right, you'd have to rig up something like that. Did you mean one injector (or two in the case of a dual TBI setup) could feed 8? With the stock dual plane, you'd have to cut down that wall, or just go to an aftermarket single plane for this to work. One injector (for single TBI) would have to feed the entire engine. This is what increases the idle pulse widths, yet allows you to still get the max fuel flow because you're still running the same injectors. Like the megasquirt article says, it effectively doubles the fueling dynamic range, which is the entire problem here.

How much HP are we talking about needing to support here?

If we're using dual SBC TBIs, I guess that'd mean a potential airflow of 500+ HP and BBC TBIs might allow us upwards of 700. That is why it would be so hard to fuel with the conventional fueling methods. Injectors big enough to fuel that HP level will be horrendous at idle. IMO, there's no point in going with a dual TBI for anything under the 350hp level. A single BBC TBI should suffice.

Right now there are several people running Xfire TB's with BBC injectors putting out over 400hp. Ben73 comes to mind and his idle is very good.

have an 89 k1500 with 7747 computer, had a edelbrock mpfi kit put on a few years ago and have since changed the intake to the hi flow tpi- vortec . sounds like this unit and the prominator would update the electronics substantially- can the air temp sensor be wired in here? was thinking of going to the 'big stuff 3' ecu, but the wiring doesn't look fun.

You'll are forgeting one thing, most FMU's will actually subtract fuel pressure when you put a vacuum on them. Lets say that you get a 2:1 FMU, normally for ever pound of boost you stick on it, the fuel pressure will go up 2 psi. Now apply vacuum and at 1 lbs vacuum the fuel pressure will decrease 2 psi.

Atmospheric pressure is about 30 in/hg (14.6 PSIA, 100 KPA) a "Hotter than stock" automotive engine typically idles at about 15 in/hg (performance cammed, 7.3 PSIA, 50 MAP).

14.6-7.3=7.3 PSI X 2=14.6 PSI fuel pressure

How is that relevant, you dial in say 35 PSI fuel pressure to get the fuel right for WOT, now you need less volume, therefore pressure for idle, the fuel pressure is now reduced by 14.6 psi at idle. Now lets add a supercharger, at 6 psi of boost the fuel pressure is at 47 psi.

The EBL takes the fuel pressure change(and boost with a 2-bar MAP) into account.

Now when you add a turbo/supercharger you are set there too.

Yes to the air intake temperature sensor. The EBL setup will take advantageof it when used. It is wired in just like the '8746 f-body TBI ECM.

RBob.

The $42 def didn't allow for changing of BPC that happens when a VAFPR is used. As Fast 355 stated, RBob's EBL code now allows you to tune with 10psi at idle but use 20psi at WOT where the extra fuel is needed. Pretty neat. No need for extra injectors.

Does this mean I'm going to need an VAFPR in order to run my setup (around 330hp) when it all comes together?

I put that in mine way back when originally when I set up my ecm, but never got to try it. Im curious to see how well it works. One thing that I thought might be difficult is setting up the filtering to match the pressure rise/fall rate of the regulator.

Dim,

Yes that looks like it would be some work. But its there if you want it. And with the expanded tables in EBL, running 20psi and getting a good 8-850rpm idle doesn't make it seems worth it for my cam and heads setup. Something more radical however very well would.

Nuther subject. How about someone developing a way of deciphering the .dat file from HUD so it can be imported into something like .xls?
RBob, any chance Jon or you could tell us how to read the data?
PLEEEEEEZZZZZEEE!

Reading the data stream is a not an easy task. You really don't want to have to do that. Being able to graph/export the data is being worked on. One thing about exporting the data is the volume. There is just a lot of data. So it doesn't do any good to output a 4 meg file (100's of thousands of records) in order to view a small portion .

RBob.

Rbob,

The software that comes with the ZT-2 allows for the user to define and export only the portion of the scan and/or the parameters of interest. This would go a long way to cutting down the amount of data that actually needs to be exported. With the speed of the EBL, there's also less of a need for very long datalogging sessions unlike what I have had to do with the 7747. Keep up the good work.

Does anybody think I'll have to re-pin anything on my 6965? I'm thinking I won't but I figured I'd ask anyway.

EDIT: Regarding the vAFPR compensation, is it just a table of BPC vs manifold pressure? Perhaps a BPC multiplier vs manifold pressure? Or maybe you've got a really sophisticated setup where the user enters the idle vacuum, the FP at idle vacuum and the zero vacuum FP and the software calculates the BPC changes it would need to make across the load range.

I assume it is user-configurable anyway, as the fuel pressure change versus vacuum is not the same on all setups, between the different springs, or even diaphram area.

I don't want to take Rbob's glory ,and would rather let him say what he wants about it, but its user adjustable.

Lets just say that the one from Xtreme EFI is compatible.

What about the re-pinning issue?

What ECM was this modeled after again? 8746? So I guess I'd have to make sure all my sensors are on the same ports/pins as an 8746-equipped F-body? Or not?

The 7747 is a direct plug in if that helps you understand the pinning requirements.

So I would have to repin my harness as if I was going to convert to a 7747?

To the extent that your current pin configuration doesn't match the 7747 config.

Hopefully it's close, since my ECM is a 7747 derivative. Are there pinouts somewhere online? I'll compare them to my FSM diagrams next time I am near the book.

Here's a start

http://www.thirdgen.org/techbb2/show...hlight=pinouts

Hi, just wanted to let everyone know that I'm still here. Been busy working on some new analysis application software along with building EBL boards. Which is why I've been no-where to be found.

A different approach is being taken with regards to the PC/Laptop analysis application. Once this is usable the EBL system will be available.

An area that I can state as ready, is the ECM code, ECU, and calibration table documentation. Once I have a suitable analysis application program I will be offering the Embedded Lockers system. I'd like to offer it now, but that would not be fair to the end-user. It needs a usable data logging and an analysis program to go with it.

This post is a little short, but that just means I've been working on the data logging/analysis end of things.

RBob.

Hopefully this turns out. It is in HTML and is the full pinout for an EBL converted ECM:
<html>
Full ECM Pin out:
Usage:
<table style="text-align: center; width: 687px;" border="1"
<tbody>
<tr>
<td style="width: 156px;">Fuel Pump Relay </td>
<td style="width: 120px;">DrkGrn/Wht </td>
<td style="width: 32px;">A1 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B1 </td>
<td style="width: 120px;">Orange </td>
<td style="width: 156px;">Battery+</td>
</tr>
<tr>
<td style="width: 156px;">A/C Clutch&nbsp;Relay </td>
<td style="width: 120px;">DrkGrn/Wht </td>
<td style="width: 32px;">A2 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B2 </td>
<td style="width: 120px;">Tan/Wht </td>
<td style="width: 156px;">Fuel PumpVoltage Input</td>
</tr>
<tr>
<td style="width: 156px; background-color: rgb(255, 204, 0);">Shift
Light </td>
<td style="width: 120px;">DrkGrn/Yel </td>
<td style="width: 32px;">A3 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B3 </td>
<td style="width: 120px;">Blk/Red </td>
<td style="width: 156px;">EST Ref Low Input</td>
</tr>
<tr>
<td style="width: 156px; background-color: rgb(255, 204, 0);">N2O
Active </td>
<td style="width: 120px;">Gray </td>
<td style="width: 32px;">A4 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B4</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">SES Light </td>
<td style="width: 120px;">Brn/Wht </td>
<td style="width: 32px;">A5 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B5 </td>
<td style="width: 120px;">Ppl/Wht </td>
<td style="width: 156px;">EST Ref &nbsp;HighInput</td>
</tr>
<tr>
<td style="width: 156px;">Ignition Power </td>
<td style="width: 120px;">Pnk/Blk </td>
<td style="width: 32px;">A6 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B6 </td>
<td style="width: 120px;">DrkBlue </td>
<td style="width: 156px;">VATS Input</td>
</tr>
<tr>
<td style="width: 156px;">TCC </td>
<td style="width: 120px;">Tan/Blk </td>
<td style="width: 32px;">A7 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B7 </td>
<td style="width: 120px;">Black </td>
<td style="width: 156px;">ESC Signal Input</td>
</tr>
<tr>
<td style="width: 156px;">ALDL Serial Data </td>
<td style="width: 120px;">Orange </td>
<td style="width: 32px;">A8 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B8 </td>
<td style="width: 120px;">DrkGrn or LtBlu </td>
<td style="width: 156px;">A/C Request Input</td>
</tr>
<tr>
<td style="width: 156px;">ALDL Diag Pin </td>
<td style="width: 120px;">Wht/Blk </td>
<td style="width: 32px;">A9 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B9</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">B9
Input (N/U)</td>
</tr>
<tr>
<td style="width: 156px;">VSS Input </td>
<td style="width: 120px;">Brown </td>
<td style="width: 32px;">A10 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B10 </td>
<td style="width: 120px;">Org/Blk </td>
<td style="width: 156px;">Park/Neutral Input</td>
</tr>
<tr>
<td style="width: 156px;">Sensor Ground </td>
<td style="width: 120px;">PPL or Black </td>
<td style="width: 32px;">A11 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B11</td>
<td style="width: 120px;" valign="undefined">&nbsp;
</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">System Ground </td>
<td style="width: 120px;">Blk/Wht </td>
<td style="width: 32px;">A12 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">B12</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px; height: 26px;"></td>
<td style="width: 120px; height: 26px;"
valign="undefined"></td>
<td style="width: 32px; height: 26px;"
valign="undefined"></td>
<td style="width: 13px; height: 26px;"
valign="undefined"></td>
<td style="width: 32px; height: 26px;"
valign="undefined"></td>
<td style="width: 120px; height: 26px;"
valign="undefined"></td>
<td style="width: 156px; height: 26px;"
valign="undefined"> </td>
</tr>
<tr>
<td
style="width: 156px; background-color: rgb(255, 204, 0); height: 26px;">PE
&nbsp;Active </td>
<td style="width: 120px; height: 26px;">Blk/Pnk </td>
<td style="width: 32px; height: 26px;">C1 </td>
<td style="width: 13px; height: 26px;"
valign="undefined"></td>
<td style="width: 32px; height: 26px;">D1 </td>
<td style="width: 120px; height: 26px;">Blk/Wht </td>
<td style="width: 156px; height: 26px;">System Ground</td>
</tr>
<tr>
<td style="width: 156px; background-color: rgb(255, 204, 0);">Fan
</td>
<td style="width: 120px;">Brown </td>
<td style="width: 32px;">C2 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D2 </td>
<td style="width: 120px;">Purple </td>
<td style="width: 156px;">MAP Ground</td>
</tr>
<tr>
<td style="width: 156px;">IAC B Low </td>
<td style="width: 120px;">LtGrn/Blk </td>
<td style="width: 32px;">C3 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D3</td>
<td style="width: 120px;" valign="undefined">&nbsp;
</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">IAC B High </td>
<td style="width: 120px;">LtGrn/Wht </td>
<td style="width: 32px;">C4 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D4 </td>
<td style="width: 120px;">White </td>
<td style="width: 156px;">EST</td>
</tr>
<tr>
<td style="width: 156px;">IAC A High </td>
<td style="width: 120px;">LtBlu/Wht </td>
<td style="width: 32px;">C5 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D5 </td>
<td style="width: 120px;">Tan/Blk </td>
<td style="width: 156px;">Bypass</td>
</tr>
<tr>
<td style="width: 156px;">IAC A Low </td>
<td style="width: 120px;">LtBlu/Blk </td>
<td style="width: 32px;">C6 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D6 </td>
<td style="width: 120px;">Tan </td>
<td style="width: 156px;">O2 Ground</td>
</tr>
<tr>
<td style="width: 156px;">4th Gear Sw </td>
<td style="width: 120px;">LtBlue </td>
<td style="width: 32px;">C7 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D7 </td>
<td style="width: 120px;">Purple </td>
<td style="width: 156px;">O2 Input</td>
</tr>
<tr>
<td style="width: 156px; background-color: rgb(255, 204, 0);">N2O
Armed Input </td>
<td style="width: 120px;">LtBlu/Org </td>
<td style="width: 32px;">C8 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D8</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">Crank Signal </td>
<td style="width: 120px;">Ppl/Wht </td>
<td style="width: 32px;">C9 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D9</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">CTS Input </td>
<td style="width: 120px;">Yel </td>
<td style="width: 32px;">C10 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D10</td>
<td style="width: 120px;" valign="undefined">&nbsp;
</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">MAP Input </td>
<td style="width: 120px;">LtGrn </td>
<td style="width: 32px;">C11 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D11</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">IAT Input </td>
<td style="width: 120px;">Tan </td>
<td style="width: 32px;">C12 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D12</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">TPS Input </td>
<td style="width: 120px;">DrkBlu </td>
<td style="width: 32px;">C13 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D13</td>
<td style="width: 120px;" valign="undefined">&nbsp;</td>
<td style="width: 156px;" valign="undefined">N/U</td>
</tr>
<tr>
<td style="width: 156px;">5V Ref Output </td>
<td style="width: 120px;">Gray </td>
<td style="width: 32px;">C14 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D14 </td>
<td style="width: 120px;">DrkGrn </td>
<td style="width: 156px;">Inj 2 Driver</td>
</tr>
<tr>
<td style="width: 156px;">Inj 2 Driver </td>
<td style="width: 120px;">DrkGrn </td>
<td style="width: 32px;">C15 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D15 </td>
<td style="width: 120px;">DrkBlue </td>
<td style="width: 156px;">Inj 1 Driver</td>
</tr>
<tr>
<td style="width: 156px;">Battery + </td>
<td style="width: 120px;">Orange </td>
<td style="width: 32px;">C16 </td>
<td style="width: 13px;" valign="undefined"></td>
<td style="width: 32px;">D16 </td>
<td style="width: 120px;">DrkBlue </td>
<td style="width: 156px;">Inj 1 Driver</td>
</tr>
</tbody>
</table>
Notes:
<div style="margin-left: 40px;">Those highlighted in
yellow are no longer used as GM intended. They
are used for new EBL functionality.<br>
</div>
<div style="margin-left: 40px;">Wire harness colors may
vary from what is listed here.<br>
</div>
</html>
RBob.

P.S. Looks like a large gap in before the table (whitespace), but it seems to be readable (in Firefox at least). Note that very little wiring has changed. Many of the pins are dedicated to specific hardware within the ECM. This makes it easy to retro-fit.

For those of us who are just going to change ECMs, what should we do to re-tune the existing calibration? Can anything cut and paste or is it going to be like re-tuning the engine all over again?

If you currently have a decent tune, a lot of calibration information can be carried over. The look and feel of the calibration tables will be familar. What you will find is some new tables along with expanded tables. As for the expanded tables one in particular is the VE tables.

(example): The EBL VE tables are two separate 3D tables, NO adders. It is a matter of filling in the locations that match from the limited stock table(s), then filling in between. The autolearn can take it from there.

Another item is that the supplied bin is from a tuned engine. This helps in getting set up and running.

RBob.

kevm,

It took a while but some of us who beta'd EBL may be able to provide a x-ref on some of the tables. You'll find that what was a constant in the original ECU is now a table with greater flexibility.

RBob,

You know there are people out here very willing to help you.

You haven't heard much from me, because the 312 is running darn near perfect.

Rob or Jon, will EBL have the capability to convert over to a wideband oxygen sensor? Just thinking that wound enable closed loop even at WOT and peg the target AFR (12.5:1 or so) all the way to redline. Sorry if this question has already been asked.

I'd rather not have the code adjust the AFR while at WOT. This I have played with and have a working sample. The issue as I see it is that the health of the engine would be dependent upon another piece of hardware: the WB.

Anything gets a little off with the WB and the engine can be history very quickly. That is why I didn't keep that code in place. But it was fun to develop and see it in action.

RBob.

91Rock,

There is a place for you to use the WB analog output to sub as the NB. As RBon and Jon know, I would like to see WB input as a selection for Learn. Being able to see both the WB and NB trace side by side in HUD, you can see how the NB lags the WB. For modded motors, I believe a tune using the WB rather than BLM is much more useful and accurate. On e question I would have is what happens when you unlock the BLMs after having tuned with the WB.

The BLMs will bring the AFR in line according to the O2 window values. How much the BLM moves depends upon how far from 14.7:1 (the commanded in closed loop) the O2 window values are.

RBob.