Cox Abele
10+ Year Contributor
- 485
- 54
- Jul 4, 2010
-
Roanoke,
Virginia
First off, here is my current tune:
http://www.scottabele.com/Spyder/DSMTunersTune.bin
In April of 2011, my stock engine decided to jump time. While replacing the head, I went through and did a fair number of upgrades and supporting mods. I also picked up everything I'd need to tune the car. I decided to have it tuned by Jestr on Central Florida Turbo's dyno. He got it all dialed in and I made some pretty satisfactory power. Before driving the 8+ hours to CFT, I'd disabled the rear o2 sensor since I'd set up my wideband to log 5v to the ecu pin. I still had all of the emissions control garbage hooked up, so I hadn't messed with the periphery bits much.
So, the dyno day came and went. I drove the car about 100 miles or so with no problems, then headed 8+ hours back home. After about 7.5 hours, I threw a CEL. The car didn't run any differently. I wasn't getting on it by that leg of the trip. It just kicked the CEL out of nowhere.
Skip ahead to July of 2012. I hadn't driven the car all winter due to a cooked clutch (happened while playing around after the dyno session). I was planning to swap the car to AWD anyhow, so I figured I'd let it sit until I could really dive in.
This past summer I finally got around to reading the code, but nothing came through my OP2.0 cable or an Actron scanner. I would clear the light, but it would come on again immediately after startup, again not setting a readable code, just that pesky light.
So, I'm looking at my tune now and seeing that I have a few things I now need to adjust.
1.) ECU Periphery0 Bits (272), bit.01, Do not edit, Leave = 1 is set to 0.
I also see that ECU Periphery00 Bits (262), bit.01 is set to 1. It has no notation to leave it alone. I'm just curious if this bit is normally set to 1, or if this may have also been bumped by accident.
This could have been an accident that happend durring my tuning session. Should I in fact set this back to 1? I have no idea what it controls. Could it be the cause of my CEL?
2.) Now that I've completed the AWD swap, I have a number of emissions items that will need turned off. I used a 95 as a donor car in my 98, so the evap and purge solenoids are no longer in the vehicle. Additionally, I've completely removed the rear o2 sensor, so I need to disable whatever is necessary to keep the CEL off for it, including the heater circuit codes. Before, I'd left it connected. and in the exhaust, but I've since switched exhaust setups. For what it is worth, I still have a functional EGR.
http://www.scottabele.com/Spyder/DSMTunersTune.bin
In April of 2011, my stock engine decided to jump time. While replacing the head, I went through and did a fair number of upgrades and supporting mods. I also picked up everything I'd need to tune the car. I decided to have it tuned by Jestr on Central Florida Turbo's dyno. He got it all dialed in and I made some pretty satisfactory power. Before driving the 8+ hours to CFT, I'd disabled the rear o2 sensor since I'd set up my wideband to log 5v to the ecu pin. I still had all of the emissions control garbage hooked up, so I hadn't messed with the periphery bits much.
So, the dyno day came and went. I drove the car about 100 miles or so with no problems, then headed 8+ hours back home. After about 7.5 hours, I threw a CEL. The car didn't run any differently. I wasn't getting on it by that leg of the trip. It just kicked the CEL out of nowhere.
Skip ahead to July of 2012. I hadn't driven the car all winter due to a cooked clutch (happened while playing around after the dyno session). I was planning to swap the car to AWD anyhow, so I figured I'd let it sit until I could really dive in.
This past summer I finally got around to reading the code, but nothing came through my OP2.0 cable or an Actron scanner. I would clear the light, but it would come on again immediately after startup, again not setting a readable code, just that pesky light.
So, I'm looking at my tune now and seeing that I have a few things I now need to adjust.
1.) ECU Periphery0 Bits (272), bit.01, Do not edit, Leave = 1 is set to 0.
I also see that ECU Periphery00 Bits (262), bit.01 is set to 1. It has no notation to leave it alone. I'm just curious if this bit is normally set to 1, or if this may have also been bumped by accident.
This could have been an accident that happend durring my tuning session. Should I in fact set this back to 1? I have no idea what it controls. Could it be the cause of my CEL?
2.) Now that I've completed the AWD swap, I have a number of emissions items that will need turned off. I used a 95 as a donor car in my 98, so the evap and purge solenoids are no longer in the vehicle. Additionally, I've completely removed the rear o2 sensor, so I need to disable whatever is necessary to keep the CEL off for it, including the heater circuit codes. Before, I'd left it connected. and in the exhaust, but I've since switched exhaust setups. For what it is worth, I still have a functional EGR.
