Narrowband Simulation in ECMLink

[dceptn]

So i just setup my narrowband simulation in ECMlink, I've read though the wiki, and the threads on here but I'm still confused if its working correctly. Is the AFRaitoEst supposed to be close or match what is displayed on the gauge or is it supposed to match whats being logged in Link?

Right now AFRaitoEst and the gauge are petty close with a little lag in the log

 

[LiquidX]

You would still need to setup the tune to match AFRest and the wideband. Narrow band simulation just allows you to use a wideband in the front o2 location by simulation the narrow band signal inside the ECU.

 

[gofer]

Before we get into your question I wanted to let you know you've got an old version of ECMLink V3 and I suggest you take the time to update it.

First download the most recent stable version v3.21.40 and then download early access v3.21.109 from the ECMLink Downloads page. After doing this you'll want to update your firmware as well but to do so its a bit trickier than just clicking a link.

1. You'll want to submit a firmware request and to do it requires you to connect to your cars ECU. Click ECU from the drop down and click Create Firmware Request... paying close attention to where its saved on your computer.
2. Request Firmware Upgrade... and select Choose File and find your firmware file you just saved.
3. Download the new firmware to your desktop or somewhere you can easily access it and then open up ECMLink.
4. Click the ECU drop down menu and select Upgrade Firmware and then pick the file you just downloaded while your connected to the ECU in the car.

Your AFREst is just an estimate and has nothing to do with your narrowband simulation or WB readings. Once you update to the new V3 software the AFREst in your logs is being pulled directly from your OpenLoopMax/MinOct tables in direct access.

Narrowband simulation is working perfect, you can see it cycling from .2 - .8v just like a front o2 sensor would if you had one. As far as getting your WB gauge to log exactly whats being displayed might be a bit tricky, I see the logged WB AFR's switching around 13.4:1. You'll notice that in the ECU Inputs tab, where you selected the connected sensor for the front o2 input, there is more than one AEM UEGO gauge type. You'll have to experiment a bit and see if any of those AEM WB gauges log accurately with whats actually being displayed on your WB.

It is possible to get both the WB display to line up with the logged WB AFR even if none of the AEM UEGO sensor types work. It just requires a bit more work and some playing with numbers, I'll give you the info to do it if you need to but for now just try the different AEM UEGO sensors.

 

[dceptn]

Before we get into your question I wanted to let you know you've got an old version of ECMLink V3 and I suggest you take the time to update it.

First download the most recent stable version v3.21.40 and then download early access v3.21.109 from the ECMLink Downloads page. After doing this you'll want to update your firmware as well but to do so its a bit trickier than just clicking a link.

1. You'll want to submit a firmware request and to do it requires you to connect to your cars ECU. Click ECU from the drop down and click Create Firmware Request... paying close attention to where its saved on your computer.
2. Request Firmware Upgrade... and select Choose File and find your firmware file you just saved.
3. Download the new firmware to your desktop or somewhere you can easily access it and then open up ECMLink.
4. Click the ECU drop down menu and select Upgrade Firmware and then pick the file you just downloaded while your connected to the ECU in the car.

Your AFREst is just an estimate and has nothing to do with your narrowband simulation or WB readings. Once you update to the new V3 software the AFREst in your logs is being pulled directly from your OpenLoopMax/MinOct tables in direct access.

Narrowband simulation is working perfect, you can see it cycling from .2 - .8v just like a front o2 sensor would if you had one. As far as getting your WB gauge to log exactly whats being displayed might be a bit tricky, I see the logged WB AFR's switching around 13.4:1. You'll notice that in the ECU Inputs tab, where you selected the connected sensor for the front o2 input, there is more than one AEM UEGO gauge type. You'll have to experiment a bit and see if any of those AEM WB gauges log accurately with whats actually being displayed on your WB.

It is possible to get both the WB display to line up with the logged WB AFR even if none of the AEM UEGO sensor types work. It just requires a bit more work and some playing with numbers, I'll give you the info to do it if you need to but for now just try the different AEM UEGO sensors.

Thanks, I forgot to mention I have the lite version I did just make sure it was up to date though.

I played with the settings and manged to get the wideband in link logging almost exactly the same as on the gauge, let me know how I'm looking now

 

[LiquidX]

That log looks pretty good. I did take notice that you have your RPM set to 950 yet you are idling around 1100 rpm.

I did just take notice you removed your FIAV. How did you "remove" it? Did you use a bypass plate or close the internal valve?

 

[dceptn]

That log looks pretty good. I did take notice that you have your RPM set to 950 yet you are idling around 1100 rpm.

I did just take notice you removed your FIAV. How did you "remove" it? Did you use a bypass plate or close the internal valve?

I believe it is a bypass plate, it was like it when I bought the car
Yeah I think I might need to play with the BISS some more to try bring it down? I was pretty close until I was trying to get the ISCPosition closer to 30 at idle

I also noticed since I enabled the narrowband sim the car is hard to start and won't stay running for the first 60 or so seconds unless I keep giving it gas, it keeps wanting to stall

 

[gofer]

Your log looks great and I apologize for not noticing you were running the lite version, I guess I didn't realize they had updated to look similar to V3 since my buddies lite version doesn't have MAFComp. Looks like he needs to update his software and not you.

It looks like you can move your WB switch point to about 2.35v, thats where it appears to be switching over at. You do need to adjust your BISS to drop ISCPosition to 30- and your rough cold starts are more than likely due to your FIAV being blocked off.

I'm impressed since this is the first question I've seen you post about your logs or about ECMLink in general. Either you've been using the ECMLink forums too or you've been doing your research and watching those demo videos, either way good job! Most ask for help before they even read the setup instructions.

 

[LTUDSM]

im just wondering,why your global is set to -10.5%? ? for 680's its supposed to be -34.5%

 

[dceptn]

Your log looks great and I apologize for not noticing you were running the lite version, I guess I didn't realize they had updated to look similar to V3 since my buddies lite version doesn't have MAFComp. Looks like he needs to update his software and not you.

It looks like you can move your WB switch point to about 2.35v, thats where it appears to be switching over at. You do need to adjust your BISS to drop ISCPosition to 30- and your rough cold starts are more than likely due to your FIAV being blocked off.

I'm impressed since this is the first question I've seen you post about your logs or about ECMLink in general. Either you've been using the ECMLink forums too or you've been doing your research and watching those demo videos, either way good job! Most ask for help before they even read the setup instructions.

Thanks for the help, I really like to try figure things out rather then asking for help all the time.

Anything I can do about the hard starts, or will I just have to teach the wife how to give it some gas

im just wondering,why your global is set to -10.5%? ? for 680's its supposed to be -34.5%

I'm guessing I have a fuel pressure issue to deal with next