My 2001 Italian Stallion money pit build
#42
So the tune is pretty much dialed in. Couple things outstanding:
1) the car takes quite some time to sync timing after startup. it will fire/start, and the CEL is on for at least 5-6 seconds after startup (CEL is set up to illuminate when MS is out of sync). This is not a deal breaker, but kinda weird.
2) since the car doesn't have dual-baro sensors, the only options for baro correction now is initial MAP reading and no correction. Initial MAP reading DOES NOT WORK properly. Something is wrong with the software, causing the car to peg rich no matter what. Disabling it makes everything peachy again.
COINCIDENTALLY - the other Rev Built MS3's I've set up all had this same problem. The latest being Gordons (EO2K) which did the same thing, pegged rich any time "initial map reading" was selected for BARO correction. Disabling BARO correction solved the issues. Not a big deal for EO2K since he's only a few hundred ft higher elevation than I.
The problem with OP is he's gonna be traveling from my area (100-200ft elevation) all the way up to the mountains (7,000-9,000ft elevation) relatively frequently. We're both a bit nervous about the tune getting all out of whack with such large elevation changes without BARO correction.
1) the car takes quite some time to sync timing after startup. it will fire/start, and the CEL is on for at least 5-6 seconds after startup (CEL is set up to illuminate when MS is out of sync). This is not a deal breaker, but kinda weird.
2) since the car doesn't have dual-baro sensors, the only options for baro correction now is initial MAP reading and no correction. Initial MAP reading DOES NOT WORK properly. Something is wrong with the software, causing the car to peg rich no matter what. Disabling it makes everything peachy again.
COINCIDENTALLY - the other Rev Built MS3's I've set up all had this same problem. The latest being Gordons (EO2K) which did the same thing, pegged rich any time "initial map reading" was selected for BARO correction. Disabling BARO correction solved the issues. Not a big deal for EO2K since he's only a few hundred ft higher elevation than I.
The problem with OP is he's gonna be traveling from my area (100-200ft elevation) all the way up to the mountains (7,000-9,000ft elevation) relatively frequently. We're both a bit nervous about the tune getting all out of whack with such large elevation changes without BARO correction.
Last edited by 18psi; 02-20-2016 at 05:40 PM.
#43
@thumpetto007 wants me to install the WB into the cluster in place of the dummy OP gauge.
Initial measurements:
Has anyone done this with this wideband into a NB cluster? I've seen a couple on NA's, but can't find any info on this for NB.
It looks liek both the cluster and the gauge have to be grinded a bit.
Initial measurements:
Has anyone done this with this wideband into a NB cluster? I've seen a couple on NA's, but can't find any info on this for NB.
It looks liek both the cluster and the gauge have to be grinded a bit.
#53
Thanks
The only issue I need to figure out is the backlighting from the cluster coming through onto the gauge from the sides, since it's not in the housing any longer.
You can see it in pics 2 and 3. Might just black out the pointless little led dial altogether, unless OP wants me to leave it as is.
The only issue I need to figure out is the backlighting from the cluster coming through onto the gauge from the sides, since it's not in the housing any longer.
You can see it in pics 2 and 3. Might just black out the pointless little led dial altogether, unless OP wants me to leave it as is.
#56
Former Vendor
iTrader: (31)
Join Date: Nov 2006
Location: Sunnyvale, CA
Posts: 15,442
Total Cats: 2,100
Willing to share what settings you tweaked to play with this? It's one of the few things I haven't been able to figure out about my cold start. I've tried a wide variety of cranking fuel settings, tried with and without priming pulse, tried playing with the cranking advance, and while it will always stumble to life on the first key hit, it won't do it cleanly like the OEM ECU does, or like other MS cars I've tuned.
#59
Elite Member
iTrader: (10)
Join Date: Jun 2006
Location: Athens, Greece
Posts: 5,979
Total Cats: 356
99% I'm pretty sure it's a decoder thing. I swear I never had this issue when I installed the 36-2 wheel. I'll write a new decoder once I get my car back, and if it works well, I'll send it to the firmware developers to update the main code.
#60
Great, thanks Rev.
I agree, and was just about to say: I think it's related to this specific/Rev built MS3 basic unit taking quite a bit longer to time-sync, as I mentioned a few posts up regarding the two ISSUES I noticed with this unit. The CEL stays illuminated for at least 3-4 seconds after startup, each and every time, indicating a sync loss. It always clears after the above mentioned few seconds indicating it finally sync'd.
Savington/Pat/Jesse,
With the last two cars it had a lot to do with the actual VE and Spark maps in addition to the normal startup settings. The 1st 2-3 columns on each table that the car sweeps through on startup, usually 0-1000rpm and 10-100kpa seem to affect this issue. It's still not flawless but much better and almost there on this car.
Pat,
I tried logging it and it never really captured what I'm talking about. It's something you can feel/hear.
Just a tiny stumble midway through cranking. "Kickback" might be too harsh a term, but it's a very mild version of kickback.
Too much advance during startup usually causes or increases it, but too little and the car will take longer to start and often will flood, which will cause a rough start.
What I noticed on many cars is they usually like between a couple to a few degrees more timing in these areas and usually fire pretty clean at 11.2-11.8afr during crank/fire
Too much timing and it will crank longer and eventually flood. Too little and will flood. Same thing with fuel: too much it floods, too little and it cranks longer and eventually floods as well.
Finding the perfect compromise is the frustrating goal here.
I agree, and was just about to say: I think it's related to this specific/Rev built MS3 basic unit taking quite a bit longer to time-sync, as I mentioned a few posts up regarding the two ISSUES I noticed with this unit. The CEL stays illuminated for at least 3-4 seconds after startup, each and every time, indicating a sync loss. It always clears after the above mentioned few seconds indicating it finally sync'd.
Savington/Pat/Jesse,
With the last two cars it had a lot to do with the actual VE and Spark maps in addition to the normal startup settings. The 1st 2-3 columns on each table that the car sweeps through on startup, usually 0-1000rpm and 10-100kpa seem to affect this issue. It's still not flawless but much better and almost there on this car.
Pat,
I tried logging it and it never really captured what I'm talking about. It's something you can feel/hear.
Just a tiny stumble midway through cranking. "Kickback" might be too harsh a term, but it's a very mild version of kickback.
Too much advance during startup usually causes or increases it, but too little and the car will take longer to start and often will flood, which will cause a rough start.
What I noticed on many cars is they usually like between a couple to a few degrees more timing in these areas and usually fire pretty clean at 11.2-11.8afr during crank/fire
Too much timing and it will crank longer and eventually flood. Too little and will flood. Same thing with fuel: too much it floods, too little and it cranks longer and eventually floods as well.
Finding the perfect compromise is the frustrating goal here.