Doing MS3x on a stock 91
11-29-2012, 01:28 AM
#63
Junior Member
Thread Starter
Join Date: Nov 2012
Location: Safety Harbor, FL
Posts: 72
Total Cats: 2
My Spartan wideband showed up today. Got the wiring done for it (and fixed the AC/Fan outputs) today. Will install it tomorrow.
Since Joe wanted some info on it, I tweaked my idle and just off-idle area to a stable 14.7, turned off EGO and AE, and recorded a short log of a slow run-up from idle to about 2500. Stock O2 voltage stayed between about .44 and .48, should be about 14.9-14.5 AFR.
I'll log the same run on the same tune after I install the WB tomorrow and then post a product review thread somewhere.
Since Joe wanted some info on it, I tweaked my idle and just off-idle area to a stable 14.7, turned off EGO and AE, and recorded a short log of a slow run-up from idle to about 2500. Stock O2 voltage stayed between about .44 and .48, should be about 14.9-14.5 AFR.
I'll log the same run on the same tune after I install the WB tomorrow and then post a product review thread somewhere.
Reply
0
0
11-30-2012, 02:14 AM
#64
Junior Member
Thread Starter
Join Date: Nov 2012
Location: Safety Harbor, FL
Posts: 72
Total Cats: 2
Discovered a few issues today that I thought I'd share. The answers weren't too hard to find, but they were interesting problems that someone else may run into. So, here we go:
#1 - I wired my WBO2 to EGO2 because I wanted to leave the NB sensor on the O2 input for testing. TunerStudio does not, by default, log data from the second O2 sensor. (EGO2 in the wiring... AFR2 in the software) Easy fix with some custom.ini code: Megasquirt MSEXTRA / MS3EFI • Megalogviewer and dual widebands (View topic)
#2 - I keep seeing "O2 out of range" errors while autotuning. WTF? If it's maxed out lean, make it richer; maxed out rich, make it leaner! But, it's a failsafe thing to keep Autotune from disastrously leaning out an engine in the event of a failed sensor. On my NA engine, I'll take my chances. Another easy ini file tweak: Megasquirt MSEXTRA / MS3EFI • Release 0.991 - VE analyser (View topic)
(instead of editing the default ini, I copied that code to my custom.ini and edited it there)
#3 - The one that was really frustrating me today: Autotune kept leaning my **** out! It was weird. I could go in and manually make the table rich... hit autotune, and it would go right past my AFR setting and just keep on going! The problem is that Autotune doesn't filter MAP-based enrichment. If you don't have a VTPS and you're using all MAP for AE... this is a problem. This one is an even easier fix, just a custom filter applied on the front end in Autotune: Megasquirt MSEXTRA / MS3EFI • VEAL pulling to much fuel? (View topic)
Perhaps I'll be able to do some proper tuning tomorrow?
#1 - I wired my WBO2 to EGO2 because I wanted to leave the NB sensor on the O2 input for testing. TunerStudio does not, by default, log data from the second O2 sensor. (EGO2 in the wiring... AFR2 in the software) Easy fix with some custom.ini code: Megasquirt MSEXTRA / MS3EFI • Megalogviewer and dual widebands (View topic)
#2 - I keep seeing "O2 out of range" errors while autotuning. WTF? If it's maxed out lean, make it richer; maxed out rich, make it leaner! But, it's a failsafe thing to keep Autotune from disastrously leaning out an engine in the event of a failed sensor. On my NA engine, I'll take my chances. Another easy ini file tweak: Megasquirt MSEXTRA / MS3EFI • Release 0.991 - VE analyser (View topic)
(instead of editing the default ini, I copied that code to my custom.ini and edited it there)
#3 - The one that was really frustrating me today: Autotune kept leaning my **** out! It was weird. I could go in and manually make the table rich... hit autotune, and it would go right past my AFR setting and just keep on going! The problem is that Autotune doesn't filter MAP-based enrichment. If you don't have a VTPS and you're using all MAP for AE... this is a problem. This one is an even easier fix, just a custom filter applied on the front end in Autotune: Megasquirt MSEXTRA / MS3EFI • VEAL pulling to much fuel? (View topic)
Perhaps I'll be able to do some proper tuning tomorrow?
Reply
0
0
12-06-2012, 01:27 PM
#65
Junior Member
Thread Starter
Join Date: Nov 2012
Location: Safety Harbor, FL
Posts: 72
Total Cats: 2
Quick update:
Tuning is going well. I'm too poor for dyno tuning, so the only data I have is my baseline 0-60 runs (easily repeatable 7.5ish using an old G-Tech). So far, I've got the idle, idle recovery and AC idle-up working well. I've autotuned it and settled on the DIYPNP timing map for now. And I've got AE working pretty well, in spite of having no VTPS installed.
The idle was giving me fits until yesterday. I'd get it all dialed in perfectly in the driveway. It would handle any load I threw at it, AC idle-up worked, recovered from revs, etc. But, when I drove it, it would get weird. It would sometimes hang at high rpm (16-1800ish) and sometimes stall.
I finally decided to fiddle with the Idle Activation Adder. The manual recommends setting it to 2-300 rpm. I had set it to 500 because of my lightweight flywheel and then promptly forgot about it. I found that raising it made for a much more controlled idle-down, and ended up setting it at 650. So, it now begins "catching" the idle at 1525 (650 + my 875 idle speed) rpm and settles nicely every time. Rarely does it dip, and it hasn't stalled or hung yet.
Current power status is that I got two 0-60 runs in yesterday at "the test facility". Both with crappy launches, 7.8 and 7.6 seconds. So, I'd say I've at least found stock power, which is okay given that I haven't even removed the MAF yet.
Before I do anything under the hood, I plan to do a little more refining of the tune. It's currently hitting 12.8-12.5 at the top end and I'm going to cut that down to 13.2 and also experiment with up to 2-3 degrees more timing (It's topping out at about 31-32 degrees at WOT). I'm hoping to free up a few more HP and see at least a repeatable 7.2-7.4 0-60 time. Then I'll be happy and start pulling the MAF and doing other fun stuff.
Tuning is going well. I'm too poor for dyno tuning, so the only data I have is my baseline 0-60 runs (easily repeatable 7.5ish using an old G-Tech). So far, I've got the idle, idle recovery and AC idle-up working well. I've autotuned it and settled on the DIYPNP timing map for now. And I've got AE working pretty well, in spite of having no VTPS installed.
The idle was giving me fits until yesterday. I'd get it all dialed in perfectly in the driveway. It would handle any load I threw at it, AC idle-up worked, recovered from revs, etc. But, when I drove it, it would get weird. It would sometimes hang at high rpm (16-1800ish) and sometimes stall.
I finally decided to fiddle with the Idle Activation Adder. The manual recommends setting it to 2-300 rpm. I had set it to 500 because of my lightweight flywheel and then promptly forgot about it. I found that raising it made for a much more controlled idle-down, and ended up setting it at 650. So, it now begins "catching" the idle at 1525 (650 + my 875 idle speed) rpm and settles nicely every time. Rarely does it dip, and it hasn't stalled or hung yet.
Current power status is that I got two 0-60 runs in yesterday at "the test facility". Both with crappy launches, 7.8 and 7.6 seconds. So, I'd say I've at least found stock power, which is okay given that I haven't even removed the MAF yet.
Before I do anything under the hood, I plan to do a little more refining of the tune. It's currently hitting 12.8-12.5 at the top end and I'm going to cut that down to 13.2 and also experiment with up to 2-3 degrees more timing (It's topping out at about 31-32 degrees at WOT). I'm hoping to free up a few more HP and see at least a repeatable 7.2-7.4 0-60 time. Then I'll be happy and start pulling the MAF and doing other fun stuff.
Reply
0
0
Thread
Thread Starter
Forum
Replies
Last Post
StratoBlue1109
Miata parts for sale/trade
21
09-30-2018 01:09 PM
