I'm browsing through the $58b TDF and AYBN $58 bin in Tunercat and I've noticed that the %VE vs RPM vs MAP table only goes up to 100 kPa, then there's a BPW Boost Multiplier vs MAP table. I'm guessing that once you go over 100 kPa under a specified RPM, it multiplies the multiplier by what %VE is listed in the first table. What happens if you're over 4000 RPM, though? If I'm under boost at ~5000 RPM (and somehow not in AE mode) what determines what fuel the engine gets?

Can I copy my spark table from the $8D bin over and use that as a baseline?

If I uncheck "Knock Option Enabled" does that disable the knock sensor?

Do I have to change the Road Speed Sensor Constant to match the number in my $8D for speedo calibration?

What's the proper way to disable the EGR since it doesn't work (and in my case doesn't exist) anyway?

Has anyone incorporated WB02 code into $58 yet?

This forum has a wealth of information about $8D tuning, is there a place for $58 tuning?

Am I asking too many questions?

 

Once at max torque in a T/C application the BSFC plateau's.

If you're not in boost, the most you'd be at is 100 K/Pa.

For idle and cruise, sure. As you get to 100 K/Pa, maybe not.

That should disable it.
I'd never suggest not using a K/S in a boosted application.

I just experiment till it reads right.

Set the enable temp to the max value.

Yes, there's a patch for using the WB with the 58 a search should turn it up.

SD is SD. The basics are the same between the two.

 

Ahh, ok. I didn't know that.

Because 100 kPa is the weight of air at sea level? (Approximately.)

I was just curious about the checkbox. I re-enabled my KS when I started using nitrous and it's been on ever since.

I suppose I could calibrate my speedo with my GPS.

That makes sense.

I'll try to search for it, it's hard when the search engine won't accept $58.

True. I'm just used to the labels/tuning of a $8D. It's like starting the learning curve all over again.

Thanks. That was the most efficient 7 conversations I ever had.

 

Is there a $58 patch for actually running a WB02 instead of NB and not just logging it?

I think I saw that it exists for $8D but it's 1.30 AM and I've been reading posts for 2 hours.

 

Not that I know of.
IMO, the oem one is fine if you want to run stoich.. If you want to run other then Stoich., IMO you'll wind up with so many other AFRs, that you'd have to have a real table for commanded AFRs, or just go open loop. While it might take a lil more time, the experience gathered with the extra tuning is worthwhile. Often it's when dinkin with things, other little tweaks are found.

 

I've implemented an open loop AFR table (f(MAP,RPM)) and a simple proportional-integral AFR closed loop into a version of $58 code. It also includes a lookup table within the code to translate WB volts to an AFR reading. My biggest stumbling block (besides not messing around with this since the temperature dropped below 60degF last year....) is determining when the WBO2 sensor is "ready" and reading accurately. I installed an additional bung in the exhaust for the WBO2. So, I have both the NB and WB that I guess I could use to compare against one another as a sanity check. But, it would be nice to be able to remove the NB all together..... There are also issues with the algorithm relative to proportional/integral resolution. It's by no means a done deal. But, I think the major pieces are in place.

I tried to gauge interest in doing this last year : https://www.thirdgen.org/techbb2/sho...hreadid=263280

As you'll see, it appears there wasn't much interest..... Now that it's starting to warm up again, it's about time to get going on this project again! Let me know if you're interested in working on this. It might turn into the first public domained modification to Grumpy's $60 code. (I know he's been waiting patiently for someone to do something with this stuff! )

 

I've never seen a WB take over 45 secs., to come up to temp.. Actually it's more like 30-35, but 45 gives room for error.

Ya, that'd be nice.....

 

A WB $58 or $60 would be great!

I saw that I was the only one replied on your "other" thread.. I think alot of people should be interesed in this, especially know when alot more people using 58/60....

/N.

 

I was originally trying to use a method similar to the stock O2 sensor where the code would look for a certain voltage level before being considered "ready". Maybe a simpler approach using run time would be better...... I'd originally thought the WB output would stay at/around 5V while it was heating up. So, my first attempt was to use that as the criteria. Unfortunately, that wasn't always the case. More often than not, the INT/BLM would rocket to the wrong value before killing the engine.

I probably shouldn't be too critical. This project is probably going to be the type of thing that won't be thought about much until it's being used. Ideally, it would appeal to anyone currently running open loop and using slewed VE tables to achieve the same type of AFR change.