I've been so busy with school, work, and girlfriend, that I haven't had much time to get the ebl running. My first run had signifigant surges, which I believe is caused by excessive iac counts, however, I'm not sure if that's where I should start. Motor is a bone stock L03 with cadillac/tpi air intake and exhaust mods.

Also, since I've had to switch between old 8746 and ebl, I have not completely removed the ccp or egr. As long as I disconnect the two electronic connections and plug the two vacuum ports on the tb, will I be fine?

 

EGR & CCP: plugging the vac ports on TB and disconnecting the connectors will do it. An FYI: there is a new version of the EBL code that supports both the EGR & CCP. So you can keep them if you'd like.

{edit: the new code has not yet been released. It is in the final stages of testing. I'll post once it is ready for prime time. thanks}

Surging is usually a lean area. Can increase those areas of the VE table where it surges. Make sure the timing is set correctly, the fuel pump pressure is good, and the injectors are spraying correctly.

The attached zip is corrupted.

RBob.

 

Did a little work on it today. The surging comes directly when the injectors go Async, its easy to verify even in the driveway. The o2 volts go from 800 range down to 40 almost instantly when this occurs.
Second, I keep having to refresh the wud display by reselecting the com port, probably not an ebl or software issue, but still bothering me.
Finally, when doing a learn ve, numbers should appear in the cells after a period of time, correct?

Hopefully the zip below will show the idle data and not end up corrupt again.

Edit: Thinking about it more I realize the blm's are low (mostly 116-120 range) which indicates rich however the surges seem lean.

 

pre EBL i had a surge. caused by too large an injector at idle CL. asynch is turning off fuel causing the rpm to drop and IAC stall saver raises up rpm.
and repeats.

post ebl - no surge. idles OL (asynch) at about 13.5/1 and IAC counts are zero. in fact my IAC counts are probably considerably less than stock in my .bin. also i followed some of the tips given in EBL tutorial and made some slight adjustments . throttle follower routines etc.

i used VE learn to creat a new .bin. learn from .bin in ECU and creates a new one with corrections. also datalogged only once with no ve learn and looked at the corrections in tables in WU. reads % as i recall. typically 2-8% corrections. seems easier just to use new .bin. you can also create a new .bin afterward (on kitchen table)from running the log. did that once.

 

I think I could figure this out if I could get "what's up display" to keep updating. The screen will keep updating for a few seconds then stop. I can select the com port again and it will repeat the process. Just for small amount of grins, I lowered the async values and not much change. When I changed the bpc vs vacuum higher (since I thought it was lean, it would be quick way to get fuel everywhere) and that made it die easily. My neighbors think this old junker is about to die for good.

Finally after reviewing the original bin the ebl lo3 bin, the max async pw is 45.75 usec versus 11994 usec. The min is 0 usec versus 686 usec. This probably isn't my problem just something different

 

For the WUD, if you are going directly to the laptop serial port, it may be the laptop is a little on the slow side. Try data logging with the SA screen showing. This will lower the load and possibly allow logging.

If you are using a serial to USB adaptor, it may be the adaptor. Can also try the above and see if it is better. Other wise a different adaptor may be needed.

The max async in the EBL BIN should also be the 11994 usec. value. And the min async should be around 680 usec.

RBob.

 

My max matchs but my min is only 503 which it came with. How does the lower number affect how the car runs?

DM

 

So I'm jumping back on the horse this week. The ebl is exactly like I left it, a giant lean dip when switching to async mode. However, I'm going to figure it out even if means working in the rain a little bit. What is the best way to upload datalogs?

Here is a link to the datalog, but you have to wait 45 seconds to download it.

 

You may want to try the original BIN as provided. Switching to async mode can cause a lean dip. However, the stock EBL BIN should be a good starting point.

Best way to post data logs is to zip them (WinZip) and then post them as an attachment. If you do a Quick Reply, will need to click the 'Go Advanced' button in order to get the upload screen.

RBob.

 

Would using the original ebl bin be better than lo3 bin that you gave me awhile ago?
Did the datalog I posted work for any one?

 

I didn't have any luck getting the data log. Browser kept timing out on it.

You can try the original EBL BIN, just to see how it is. I responded to your email. MOstly about getting the data logging working first.

The going lean in async mode. To disable async mode can set these 2 parameters to 0:

INJ - Async transition Hi
INJ - Async transition Lo

I do know that transistioning from sync to async mode does tend to make the AFR go leaner. On a stockish engine usually doesn't matter much. Above that I usually disable async mode.

RBob.

 

Doing better today, I can data log all day long now. The lower I take the async transition, the better the motor is. Eventually I will phase it out.
One problem I have had was with learn ve. I can have the proper bin loaded and see the blm fluctuates but when I go to the corrections% chart I still have zeros. I have the green "learn" light lit on the whatsup and I am within the coolant temperature range, but am still not getting any values. Do I have to meet any other parameters to get learn ve?

Also try looking at about 5:35 on the attached log, it goes quite lean. Is that just ve needing tweeked?

 

I took a look at the log and ran a VE Learn. Using BLM and 60 C low, 104 C high CTS a bunch of cells learned in. Did you get the green box on the VE Learn screen? In general the VE is a little rich.

The lean area at 5:35 is because the BLM has made a large adjustment elsewhere. Which is not required at a different MAP point. Once the VE table is closer this issue will go away.

RBob.

 

Looks like its coming together now. I keep showing up rich from learnve, however, it has slight surge, possibly from a lean condition. I have removed all of async and I think I'm starting to pick ebl up. Its exciting!