lakeffect2

OK, so the Prominator has died, and been replace by the EBL P4 within the past few days. First off is my thanks to RBob (Bob R) & company for the swift service, and carrying out their vision to create this great product for the rest of us folk. I was able to install the ECM OK, and find it via the "What's Up Display" I can see things functioning. good so far.

EDIT: By the way when setting up the com port, I could see that Com port 1 was open, 2-5 were closed, but I could not get a flash or even connection to the EBL? WHY? Because Com 1 was not the only port that was open, simply the first one I found. I went past Com 5 to find that Com 7 was also open, and that's were the EBL was to be found, So the mistake was assuming that the first open Com port was the one I wanted. The actual port needed, turned out to be further down the list.


A few initial issues though. After searching the 60+ pages of the EBL Tuning that started many years ago,I can't say I see my answers there, so I figured I might as well get a thread going for my specific questions and needs. I'm on the EBL P4 system. with 400 TPI'd system, 7730 ECM and using Tunerpro for editing software. So here's goes.

First issues:

1)Never reaches closed loop after any length of time or temp. ( no "CL LP" light on What's up)

2)Idle doesn't budge off of 1400, should be 800-900. ( Ok it goes down to 1200 when I hit the breaks because I'm giong 45 in a 35 zone with that 1400 rpm idle situation.
.

3) AFR in Open Loop stay in the 10-11 area, even after lowering what I believe were AFR vs coolant temp related charts (wasn't the same name as in Super AUJPV4, but looked simliar)

4) Although fan temps were lowered in program (Tunerpro)to down to 185F, neither fan has ever come on, even when engine hit 230F (ouch, but I put in manual over rides switches and at least got home.

5) VE learn does make any difference, as Closed Loop does not get enabled, so VE really isn't learning.

5A) Another quicK question related to saved VE learns. I understand that it updates the current bin being used in the EBL p4 memory, but is it also updating the bin in my Tunerpro files as well? It wouldn't seem to make sense to do one, without doing the other at the same time. Otherwise when you go back into Tunerpro it wouldn't really be the same bin that was being run anymore as the VE changes that were "learned" into the EBL bin wouldn't have been carried over to the laptop bin.

Since many terms and item descriptions from Super AUJP V$ to the EBL XDF file have changed. I'm not recognizing what I'm after to change things.

Many thanks ahead for your inut and comments. Any insight that you may have already uncovered would be most appreciated to tame an unruly beast.




Dave Buchholz

RBob

iTrader: (1)

Check that the O2 sensor is either high or low (< 200 mV or > 700 mV). The ECM needs to see that it is active.

What was the IAC doing? And what was the CTS at this time? The CTS will also affect closed loop enable.

Was this the commanded AFR or a WB reported AFR? There are two open loop AFR tables that can be adjusted.

CTS?

Correct, can't use the BLM VE Learn unless the ECM is in closed loop & learn mode.

It doesn't update the BIN that is in the ECM. It creates/updates the BIN that you give the WUD when setting up the VE Learn. The first BIN you give the WUD is the current one being run in the ECM. The second BIN you give the WUD is the created/updated BIN.

If you want to use the new BIN it then needs to be flashed in.

See the EBL P4 Flash Program Group. There are three help documents, one of is for the calibration terms.

RBob.

lakeffect2

Once again, many thanks.

I am showing an error code on the wideband display itself. So that will be the first place to start looking. Doing a factory reset on it was of no avail this morning, So I'll look for continue to look for loose connections that may have occurred when pulling the ECM out. Also pulling the O2 Sensor would seem to be in order to see how fouled it may be.

Since the fans were not coming on, temps were over 220*f and the idle was still 1400rpm.

Will post up with my discoveries. later in the week.

Dave

RBob

iTrader: (1)

Next time you start the engine also start a data log. With that you can see what the ECM is seeing and doing.

RBob.

lakeffect2

Choke AFR thoughts, using Tunerpro Rt

I noted the range of temps for Choke AFR goes from -40* to +151*c

I will never be starting the car at -40*, as it is stored for winter, and never gets to that temp here anyway, even on the worst of days. (This is also true of several other temp related conditions I'll never see) So... why not modify the range to those temps that I would more likely see in actual use. I would think that a good thing, to allow more control in the reality range of my true temps under warm up conditions.

I figured out how we can edit the table rows, easily to -20* to +140* by 10* increments. Is changing the actual range as simple as changing the rows in the table to get a different range of control, or am I really only fooling myself by changing the "label" of the range of what I see, and not the true range of control?

Dave

RBob

iTrader: (1)

Would also need to change the code so that it also uses the ranges that they are changed too.

RBob.

lakeffect2

So, if I understand correctly, my work would in fact only changes the label range that I view when opening the table, not the actual conditional range that the ECM uses.

Getting back to the Lack of 02 wideband reading. I've confirmed with the manufacturer (Glowshift) the the wideband O2 Sensor module is fried, and they are sending a replacement . So I should be back in the datalogging business by the weekend.

Dave

lakeffect2

To make a long story short, the tech at Glowshift Gauges was wrong. It wasn't the module, it's the sensor. (Bosch LSU 4.9 Since they want a song and dance to send the sensor only AFTER I return the module first and pay them more for it and pay for shipping their error both ways, I simply ordered a sensor online.

I got no love from them. No offer to pay for shipping, no reduced price for the cost of my wasted time and loss of ability to use the vehicle while they play games for $35.00 (plus me paying for shipping both ways.) I 'll just return the module and get a refund.

It looks like the sensor may have been banging against the frame rail, So It would be wise to angle the bung upward slightly. It will also help to keep moisture from collecting in it as well.

I'll keep you posted ion the results.

morgsie

iTrader: (1)

You actually want to mount it on a slight (~10*) downward angle.

lakeffect2

As was mentioned, there is a rather large physical obstruction preventing that. It would mean cutting a hole in the frame. It's already whacking it.

It would also contradict the manufacturer's installation instructions . They clearly indicate by both word and diagram, upward, so moisture doesn't collect and foul the sensor. By that, the diagram shows the sensor tip as being pointed down ward, and tipped below the wired harness end, which is pointing up. That's what they consider as being "up".

Hopefully it's just a question of what is referenced as up. But, unless you can counter that with overwhelming insight as to why I'd want to cut up the frame, I can't say I'd have reason to consider any thing but follow the Bosch recommendations.

Dave