Anyone using a SMEC with the 0-1V output from a wideband?

[ShelGame]

Ok, I'll put that one back. Its ok though if the graph doesn't include the same AFR range? It used to only have 19.xx for the maximum value of the x-axis.

Yes, that 2nd table needs to match your wideband output; AFR vs. Volts.

[wheming]

You don't want to adjust that first pictured table. That converts the measured AFR into a simulated NB signal for use in the O2 feedback control.

You only want to adjust the WB voltage to AFR table.

The offset will only affect part throttle. You can use it to force the ecu into running richer or leaner in closed loop.

The table description of WidebandAFRToO2TransferFunction says should be matched for sensor/driver output. So i put the table basically back as close as i could get it after changing the min & max on AFR.
Does this look correct?

[ShadowFromHell]

I'm using the 0-1V output on my AEM UEGO on my LM.

I thought the AEM didn't have a narrow band output?

[player1up]

I thought the AEM didn't have a narrow band output?

The instructions for the 30-4110 show a mode for an analog output voltage .070 to .905v ... that should be close enough

I'll be using the 0-5v range on mine in the next week or so.

[ShelGame]

The table description of WidebandAFRToO2TransferFunction says should be matched for sensor/driver output. So i put the table basically back as close as i could get it after changing the min & max on AFR.
Does this look correct?

The bent line is correct. The straight line is NOT.

[shackwrrr]

Never thought of the during warmup output of the wideband. On the TechEdge it is set to default to a 14.7 output during warmup so I have never had an issue.

[wheming]

The bent line is correct. The straight line is NOT.

Ok, in that pic the bent line was my correction. Thank you!
I might try this out again now that I've determined i had a bad ignition coil causing the stumbling and stall. The lean conditions observed must have been when it was breaking down and misfiring.

[player1up]

ok, so to sum up: ( this is how I understand it from this thread, please correct me if I've got something wrong )

NarrowBandOffsetValue -- Only needs to be changed to make part throttle leaner or richer if during closed loop operation ( couldn't I just use the standard fuel tables to accomplish the same goal? )

WidebandAFRToO2TransferFunction -- Needs to be left alone. This uses measured AFR from the WB and converts to NB signal for the rest of the cal to use ( This will work as long as your WidebandAFRTransferFunction is setup to match your brand of WB output 0-1v or 0-5v )

WidebandAFRTransferFunction -- Needs to be setup to match the output from the WB. This can be 0-1v or 0-5v as long as it matches your WB input v with AFR

[ShelGame]

ok, so to sum up: ( this is how I understand it from this thread, please correct me if I've got something wrong )

NarrowBandOffsetValue -- Only needs to be changed to make part throttle leaner or richer if during closed loop operation ( couldn't I just use the standard fuel tables to accomplish the same goal? )

WidebandAFRToO2TransferFunction -- Needs to be left alone. This uses measured AFR from the WB and converts to NB signal for the rest of the cal to use ( This will work as long as your WidebandAFRTransferFunction is setup to match your brand of WB output 0-1v or 0-5v )

WidebandAFRTransferFunction -- Needs to be setup to match the output from the WB. This can be 0-1v or 0-5v as long as it matches your WB input v with AFR

All correct.

To answer your question (couldn't I just use the fuel tables...); No. Even if you lean out the fuel tables, the O2 controller will try to get the AFR closer to the controllers limits (very near stoich).

The offset value I added will make the O2 controller think that its running near stoich, when in reality its richer or leaner.

[player1up]

All correct.

To answer your question (couldn't I just use the fuel tables...); No. Even if you lean out the fuel tables, the O2 controller will try to get the AFR closer to the controllers limits (very near stoich).

The offset value I added will make the O2 controller think that its running near stoich, when in reality its richer or leaner.

Ah, ok that makes sense now, that's why I asked

This is going to be a ton easier than logging 2 inputs and trying to combine them later.
Can't wait til I've gotten the clutch broken in to really beat on it with a tight tune.

[shackwrrr]

Note: By default the offset value is set at -2.5v, this needs moved to zero for correct operation.

[wheming]

Note: By default the offset value is set at -2.5v, this needs moved to zero for correct operation.

Absolutely! I noticed that too.

[ShelGame]

Note: By default the offset value is set at -2.5v, this needs moved to zero for correct operation.

Oops. I'll fix that in the next release.

[player1up]

Thanks guys.
I noticed that I can't change it to 0 in the table, I have to use the slider to set it -0.010 or 0.010 I assume that's close enough but when I tried to type 0 in the table it told me that's an invalid point...is this because 0 on the table isn't 0 on the slider/scale.
Also, once I tried to type something in the table it wont let me save and no value is valid..just keeps throwing the error..says it saves, but value is the old value when i reopen the template.
I'm just mentioning this in case someone runs into it.

[wowzer]

definitely a problem in mpt2. i'll need to look at it this weekend. i'm able to get some other weird errors also. it's using a table type that has not been really tested before so i need to figure out what's happening. sorry.



***edit****
just posted version 2.0.4.3. start mptune, give it 10 - 15 seconds, exit and it should update. then get back in, make sure its version 2.0.4.3 and you should be good to go.

[player1up]

ok, cool. I'll try to get it wired up this weekend and give it a try.

[ShelGame]

Thanks guys.
I noticed that I can't change it to 0 in the table, I have to use the slider to set it -0.010 or 0.010 I assume that's close enough but when I tried to type 0 in the table it told me that's an invalid point...is this because 0 on the table isn't 0 on the slider/scale.
Also, once I tried to type something in the table it wont let me save and no value is valid..just keeps throwing the error..says it saves, but value is the old value when i reopen the template.
I'm just mentioning this in case someone runs into it.

That's also a display scale issue. I'll recalculate so that 0 equals 0.

In the meantime, 0.1 is actually 0 as far as the ECU knows.

[player1up]

ok, wiring is done, new cal is on the ecu. Started but not driven yet.

MPScan still shows 20.0:1 for AFR.
Is there anything that needs to be changed on the settings for the gauge?

I have it mapped to AFR ( 206 )

[ShelGame]

ok, wiring is done, new cal is on the ecu. Started but not driven yet.

MPScan still shows 20.0:1 for AFR.
Is there anything that needs to be changed on the settings for the gauge?

I have it mapped to AFR ( 206 )

Using the 'AFR Display' in MP Tune?

I'm not sure that works yet.

You'll need to rescale the AFR input channel also to match your WB output.

[player1up]

Using the 'AFR Display' in MP Tune?

I'm not sure that works yet.

You'll need to rescale the AFR input channel also to match your WB output.

Using the 'AFR Display' in MP Tune?

I'm not sure that works yet.

You'll need to rescale the AFR input channel also to match your WB output.

Huh?
I know the AFR yellow line in MPTune is a visual representation of how it's manually configured for the cal in the "AFR Settings"
The tune is configured to match the WB output and seems to be running fine, but I can't log actual AFR in MPScan. I suppose I should try o2v
I've got no problem setting up logging with hyperterm from the AEM, but thought I could log with MPScan so I could have all of my tuning info in the same place at the same time

***UPDATED****
Not sure what I did but AFR (afr) is working now, but it's off by 4-5 points and O2v shows correctly...meaning .9v matches the afr on the AEM gauge but AFR ( 206 ) in MPscan shows 15ish

The AFR settings in MPScan wont let me make any changes