ECMlink GVR4 ECMLink closed loop

[Elpizer2]

My car stays on open loop. All is set for speed density.

Base timing, grounds, wideband, but it stays on open loop

Attached some pictures.

You must be logged in to view this image or video.

You must be logged in to view this image or video.

 

[Justin DuBois]

Throttle closed position switch need to be on to get closed loop.

 

[Elpizer2]

Idle switch 0 at idle and ThrotPos 1% at idle. So ThrotPos needs to be 0% at idle to work on closed loop?

 

[Justin DuBois]

Idle switch 0 at idle and ThrotPos 1% at idle. So ThrotPos needs to be 0% at idle to work on closed loop?

Closed loop requires idle pin = 1. I don't know why your IdleSw=1 when your IdleSw pin = 0

Can you also display "Combined FT" ? Closed loop will adjust your Combined FT to achieve 14.7 AFR at idle. You might try lowering your target RPM to 800 - 1000rpm idle is high.

Please attach a ".elg" log file so we can see the rest of your setup.

 

[Elpizer2]

I am simulating idle switch

Closed loop requires idle pin = 1. I don't know why your IdleSw=1 when your IdleSw pin = 0

You must be logged in to view this image or video.

 

[Justin DuBois]

With regards to TPS - you can try the TPS adjust function. Start a stream - not running - push the throttle to the floor and let up a couple times so the TPS plot is in the log. Stop the stream - Rt click on the plot and select TPS Adjust. What numbers does it populate?

Why simulate - Do you not have a closed position switch on your Throttle Body?

When your engine is up to temp - 88C, or 190F - does the idle come down? Do you have a FIAV plummed to coolant on your Throttle Body?

These are criteria that will switch the ECU to open loop.

• Throttle position too high (varies by RPM)
• Airflow too low (units are tricky, but it's very low)
• Coolant temp < 87F
• The O2 sensor did not switch around 0.5v for over 20 seconds while running in closed loop mode. In that case, the ECU locks itself in open loop mode.

fueltrimupdatepoints [ECMTuning - wiki]

www.ecmtuning.com

 

[Elpizer2]

Can you also display "Combined FT" ? Closed loop will adjust your Combined FT to achieve 14.7 AFR at idle. You might try lowering your target RPM to 800 - 1000rpm idle is high.

Please attach a ".elg" log file so we can see the rest of your setup.

You must be logged in to view this image or video.

Why simulate - Do you not have a closed position switch on your Throttle Body?

I don't have idle switch. That's why I'm simulating it

 

[Elpizer2]

These are criteria that will switch the ECU to open loop.

• Throttle position too high (varies by RPM)
• Airflow too low (units are tricky, but it's very low)
• Coolant temp < 87F
• The O2 sensor did not switch around 0.5v for over 20 seconds while running in closed loop mode. In that case, the ECU locks itself in open loop mode.

fueltrimupdatepoints [ECMTuning - wiki]

www.ecmtuning.com

I don't have a MAF, only MAP and IAT

 

[Justin DuBois]

Ah! and you also don't have a stock narrow band o2 Sensor. Without a narrow band signal, the ECU will not go into closed loop. Try enabling narrow band sim

You must be logged in to view this image or video.

ALSO you can enable ECU Input lock "Lock intake temperature and barometric pressure"

You must be logged in to view this image or video.

 

[Elpizer2]

Ah! and you also don't have a stock narrow band o2 Sensor. Without a narrow band signal, the ECU will not go into closed loop. Try enabling narrow band sim

You must be logged in to view this image or video.

ALSO you can enable ECU Input lock "Lock intake temperature and barometric pressure"

You must be logged in to view this image or video.

Ok but do I need to put my AEM gauge into narrowband simulation P4??. Or I can use it as a P0 wideband analog output.

Enable intake temperature?. So uncheck or check it? I'm confused

 

[Justin DuBois]

ECMLink does the narrow band sim - You don't need to adjust your AEM WB setup - just enable the sim checkbox.

Locking the ECU input for baro and intake temps only affects the stock ECU code. Enabling the lock will bypass the error checking that might throw a check engine light - it won't affect general Speed Density operation.

 

[Elpizer2]

ECMLink does the narrow band sim - You don't need to adjust your AEM WB setup - just enable the sim checkbox.

Locking the ECU input for baro and intake temps only affects the stock ECU code. Enabling the lock will bypass the error checking that might throw a check engine light - it won't affect general Speed Density operation.

Alright I got it.

But another question

My wideband is a AEM 30-4110 gauge + 4.9 LSU sensor. The better reading was AEM analogic wideband. All others didn't work

Any suggestions? I tried linear wideband but couldn't make work as well

I attached the table for this AEM wideband outputs

You must be logged in to view this image or video.

 

[Justin DuBois]

Alright I got it.

But another question

My wideband is a aem 30-4110 gauge + 4.9 LSU sensor. The better reading was AEM analogic wideband. All others didn't work

Any suggestions? I tried lineal wideband but couldn't make work as well

I attached the table for this AEM wideband outputs

You must be logged in to view this image or video.

The default mode P0 will provide ECM Link a 0-5v linear wideband input voltage, while displaying AFR on the gauge. This is the typical mode to use.

 

[Elpizer2]

The default mode P0 will provide ECM Link a 0-5v linear wideband input voltage, while displaying AFR on the gauge. This is the typical mode to use.

No, P0 and P1 are 0 volts to 4,250 volts. It's on the picture attached here

Check it out

You must be logged in to view this image or video.

 

[Justin DuBois]

No, P0 and P1 are 0 volts to 4,250 volts. It's on the picture attached here

Check it out

You must be logged in to view this image or video.

ECM Link o2 input voltage is 0-5 volts. The chart shows Mode 0 and Mode 1 output 0- 4.250 volts. Use mode 0. In the US we use a decimal point instead of a comma. 4.250 is the same as 4,250. (these are not more than 5 volts output)

 

[We're on Boost]

I agree with what Justin is telling you about the wideband setup. And about commas

My wideband is an AEM 30-4110 gauge + 4.9 LSU sensor.

Thanks for telling us the actual model number of your wideband. Most people don't seem to ever be able to do that.
That model is the old one. It's the one I have, so I'm familiar with the chart you posted for it.
I agree, leave it set in the default P0 mode, and reading "AFR (Gasoline)" on it, no matter how much ethanol is in your fuel.

Display the raw voltage value for "WIDEBAND ANALOG".
It will be labeled "RawAEMAnalogWB".
It's the actual voltage that is sent to your FrontO2 input by the AEM wideband.
I'm looking at it right now, and I'm seeing that the scaling that WIDEBAND ANALOG is giving you doesn't agree with the AEM chart.
For instance, 2.73 volts should be an AFR of about 15.5 according to the chart, but your WIDEBAND ANALOG says 13.8 AFR.

So, you should probably try to custom scale it, like this:
On your ECU Inputs page, in the Connected Sensor drop down for Front O2, pick "Linear wideband".
Setup your Graph Item Preferences for it like this:

You must be logged in to view this image or video.

It wants lambda values at the 2 voltage points but that's ok because the AEM table has a column showing the lambda value at each voltage.
So you can verify that the lambda values I put in the picture agree with the AEM table.

Well here's the sad part. Doing this is how it is supposed to work, but it doesn't necessarily mean you will be getting accurate AFR numbers.
My 30-4110 never did log correctly. But it was set up initially on the EGR input, and that killed it. So now I have no analog output at all from my AEM wideband.
The 1g Front O2 input is a much better input, so you might have better success with it, I hope.

One more sad thing - since you aren't also using a regular narrow band O2 sensor, you don't have a good way of checking your wideband for accuracy.
If you had a good narrow band O2 sensor to run closed loop, you would know that when the O2 is cycling, that you are right around stoic (14.7) AFR, and that would be a good check on your wideband.

But if you add a narrow band O2 temporarily for checking, don't put the AEM wideband on the EGR input. It might ruin it like it did mine, and it probably won't give you accurate numbers even if it seems to "work". If you want to try a temporary setup that uses both a narrow band O2 and the wideband, I'd suggest putting the wideband on the Intake Temp input. That means you would temporarily have no IAT sensor so your tune would be a little off. But so what, you would still get decent closed loop operation so you would be able to see if the wideband is giving you about 14.7 when the narrow band is cycling. Actually my car doesn't use an IAT sensor at all. But it was set up and tuned that way right from the start, so it works ok. It uses coolant temperature only for the temperature compensation.

If you need it, here's the ECMtuning wiki page for how to set up user defined Linear items like Linear Wideband:

linearitems [ECMTuning - wiki]

www.ecmtuning.com

 

[Elpizer2]

If you need it, here's the ECMtuning wiki page for how to set up user defined Linear items like Linear Wideband:

linearitems [ECMTuning - wiki]

www.ecmtuning.com

Well. Closed loop is working. I did the linear wideband and it's very accurate I gotta use analogic old version table AEM wideband to make it work

 

[We're on Boost]

Well. Closed loop is working. I did the linear wideband and it's very accurate I gotta use analogic old version table AEM wideband to make it work

Ok good! Could you post a log of it? It would be interesting.

 

[Elpizer2]

Ok good! Could you post a log of it? It would be interesting.

I used this data for the wideband

You must be logged in to view this image or video.

You must be logged in to view this image or video.

 

[Justin DuBois]

I agree with what Justin is telling you about the wideband setup. And about commas


Thanks for telling us the actual model number of your wideband. Most people don't seem to ever be able to do that.
That model is the old one. It's the one I have, so I'm familiar with the chart you posted for it.
I agree, leave it set in the default P0 mode, and reading "AFR (Gasoline)" on it, no matter how much ethanol is in your fuel.

Display the raw voltage value for "WIDEBAND ANALOG".
It will be labeled "RawAEMAnalogWB".
It's the actual voltage that is sent to your FrontO2 input by the AEM wideband.
I'm looking at it right now, and I'm seeing that the scaling that WIDEBAND ANALOG is giving you doesn't agree with the AEM chart.
For instance, 2.73 volts should be an AFR of about 15.5 according to the chart, but your WIDEBAND ANALOG says 13.8 AFR.

So, you should probably try to custom scale it, like this:
On your ECU Inputs page, in the Connected Sensor drop down for Front O2, pick "Linear wideband".
Setup your Graph Item Preferences for it like this:

You must be logged in to view this image or video.

It wants lambda values at the 2 voltage points but that's ok because the AEM table has a column showing the lambda value at each voltage.
So you can verify that the lambda values I put in the picture agree with the AEM table.

Well here's the sad part. Doing this is how it is supposed to work, but it doesn't necessarily mean you will be getting accurate AFR numbers.
My 30-4110 never did log correctly. But it was set up initially on the EGR input, and that killed it. So now I have no analog output at all from my AEM wideband.
The 1g Front O2 input is a much better input, so you might have better success with it, I hope.

One more sad thing - since you aren't also using a regular narrow band O2 sensor, you don't have a good way of checking your wideband for accuracy.
If you had a good narrow band O2 sensor to run closed loop, you would know that when the O2 is cycling, that you are right around stoic (14.7) AFR, and that would be a good check on your wideband.

But if you add a narrow band O2 temporarily for checking, don't put the AEM wideband on the EGR input. It might ruin it like it did mine, and it probably won't give you accurate numbers even if it seems to "work". If you want to try a temporary setup that uses both a narrow band O2 and the wideband, I'd suggest putting the wideband on the Intake Temp input. That means you would temporarily have no IAT sensor so your tune would be a little off. But so what, you would still get decent closed loop operation so you would be able to see if the wideband is giving you about 14.7 when the narrow band is cycling. Actually my car doesn't use an IAT sensor at all. But it was set up and tuned that way right from the start, so it works ok. It uses coolant temperature only for the temperature compensation.

I've been in a weird mood today

 

[We're on Boost]

I used this data for the wideband

Looks like some EMS setup data. It's completely different from the table up in post #18.
Interesting!

 

[We're on Boost]

I've been in a weird mood today

Well I got a bang out of the commas comment because I run into it now and then.
Another thing I've run into is, you know how when we write a number that's in the millions or billions, if we write the whole number out we put a comma in every 3 places. In some countries they don't do it that way, it's some different number of places, not 3.

 

[We're on Boost]

since you aren't also using a regular narrow band O2 sensor, you don't have a good way of checking your wideband for accuracy.

Chances are pretty good that the AEM wideband gauge will read accurately. Mine seems ok (But I have a narrow band O2 to check it against). It's the analog output from them that has been not so good. So if your newly scaled AFRs in the log agree with what you see on the gauge, then the logged numbers are probably ok.