Happy with my new Cobb AP.
02-28-2012, 08:42 PM
#1
mmm... tastes like jesus
Thread Starter
Join Date: Oct 2003
Location: Jacksonville, FL
Posts: 165
Likes: 0
Received 0 Likes
on
0 Posts
Happy with my new Cobb AP.
Ok,
I just got my COBB AP (used from comebackqid). I have been battling a P0610 vehicle options error code for the past... oh... let me see... 3-4 years. Also haven't had cruise control either
.
Installed the AP, loaded stage 1 and *POOF* no cell... YES!
Startup... stall...
Startup... low idle...
Test drive, pulls fine, no discernible difference in power/performance (vehicle is 04 mt stock)...
CRUISE CONTROL WORKS!!!!
I haven't had a reliable cruise control in the last 3-4 years!
If i don't use this thing for anything other than killing this code and restoring my cruise control i'm happy! To clarify I didn't have to mask the cell, it is gone, as in the vehicle options error is no longer an error. I believe the code originated around the last time the car was flashed at the dealer.
Finally,
Something good happened today!
Ray
I just got my COBB AP (used from comebackqid). I have been battling a P0610 vehicle options error code for the past... oh... let me see... 3-4 years. Also haven't had cruise control either
.Installed the AP, loaded stage 1 and *POOF* no cell... YES!
Startup... stall...
Startup... low idle...Test drive, pulls fine, no discernible difference in power/performance (vehicle is 04 mt stock)...
CRUISE CONTROL WORKS!!!!
I haven't had a reliable cruise control in the last 3-4 years!
If i don't use this thing for anything other than killing this code and restoring my cruise control i'm happy! To clarify I didn't have to mask the cell, it is gone, as in the vehicle options error is no longer an error. I believe the code originated around the last time the car was flashed at the dealer.
Finally,
Something good happened today!
Ray
02-29-2012, 07:27 PM
#5
mmm... tastes like jesus
Thread Starter
Join Date: Oct 2003
Location: Jacksonville, FL
Posts: 165
Likes: 0
Received 0 Likes
on
0 Posts
ugggg.... back to the pile! <-- yah, that was a south park reference :-)
Started it up this morning and.... DING... CEL is on and cruise is not responsive, DAMNIT!
Oh well... nothing i haven't become accustomed to. :-/
Also stuck with a lack of idle quality. I'll be swapping out the coils, plugs, and wires soon and cleaning out the ssv. hopefully get back to normal.
Ray
Started it up this morning and.... DING... CEL is on and cruise is not responsive, DAMNIT!
Oh well... nothing i haven't become accustomed to. :-/
Also stuck with a lack of idle quality. I'll be swapping out the coils, plugs, and wires soon and cleaning out the ssv. hopefully get back to normal.
Ray
02-29-2012, 11:16 PM
#7
Very interesting problem.
On series Is, the throttle is actually controlled by a second microprocessor. I believe it is from the Freescale 823xx family. This is probably because controlling an electronic throttle is quite computationally complex, especially when it is being used for idle control. Minute corrections to throttle angle must be made constantly to maintain idle. It also maintains a memory to account for variances in the throttle bodies performance due to aging, buildup on the throttle blade, etc. This is a big part of the reason that some cars idle poorly after a reset.
However, the main micro also has code for controlling the throttle, I believe this is to provide redundancy should the main throttle controller fail, however I imagine it can't do it as well as the dedicated chip.
On series IIs, there is a new section of code for throttle control, and all of the throttle tables are loaded to ram to speed things up. The main ecu chip is twice as fast, so it seems that the full throttle control algorithm was brought on board.
So, I will speculate that the ecu is detecting a problem with its throttle control chip during the 1st drive cycle, and consequently switching to the failsafe routine, which gives you poor idle and no cruise control.
On series Is, the throttle is actually controlled by a second microprocessor. I believe it is from the Freescale 823xx family. This is probably because controlling an electronic throttle is quite computationally complex, especially when it is being used for idle control. Minute corrections to throttle angle must be made constantly to maintain idle. It also maintains a memory to account for variances in the throttle bodies performance due to aging, buildup on the throttle blade, etc. This is a big part of the reason that some cars idle poorly after a reset.
However, the main micro also has code for controlling the throttle, I believe this is to provide redundancy should the main throttle controller fail, however I imagine it can't do it as well as the dedicated chip.
On series IIs, there is a new section of code for throttle control, and all of the throttle tables are loaded to ram to speed things up. The main ecu chip is twice as fast, so it seems that the full throttle control algorithm was brought on board.
So, I will speculate that the ecu is detecting a problem with its throttle control chip during the 1st drive cycle, and consequently switching to the failsafe routine, which gives you poor idle and no cruise control.
03-01-2012, 02:35 PM
#11
There seem to be two styles of DBW throttle calibration. Pedal position dictates output torque more or less linearly, or pedal position dictates throttle position more or less linearly.
The RX8 is more toward the latter.
However, it seems like enthusiasts make the same complaints regardless of the control strategy. Too touchy off idle, goes full throttle too soon.
It makes me think that the "average" focus-group driver actually likes the throttle that way, and DBW just means manufacturers can tune for the lowest common denominator.
The RX8 is more toward the latter.
However, it seems like enthusiasts make the same complaints regardless of the control strategy. Too touchy off idle, goes full throttle too soon.
It makes me think that the "average" focus-group driver actually likes the throttle that way, and DBW just means manufacturers can tune for the lowest common denominator.
03-01-2012, 02:37 PM
#12
mmm... tastes like jesus
Thread Starter
Join Date: Oct 2003
Location: Jacksonville, FL
Posts: 165
Likes: 0
Received 0 Likes
on
0 Posts
Very interesting problem.
On series Is, the throttle is actually controlled by a second microprocessor. I believe it is from the Freescale 823xx family. This is probably because controlling an electronic throttle is quite computationally complex, especially when it is being used for idle control. Minute corrections to throttle angle must be made constantly to maintain idle. It also maintains a memory to account for variances in the throttle bodies performance due to aging, buildup on the throttle blade, etc. This is a big part of the reason that some cars idle poorly after a reset.
However, the main micro also has code for controlling the throttle, I believe this is to provide redundancy should the main throttle controller fail, however I imagine it can't do it as well as the dedicated chip.
On series IIs, there is a new section of code for throttle control, and all of the throttle tables are loaded to ram to speed things up. The main ecu chip is twice as fast, so it seems that the full throttle control algorithm was brought on board.
So, I will speculate that the ecu is detecting a problem with its throttle control chip during the 1st drive cycle, and consequently switching to the failsafe routine, which gives you poor idle and no cruise control.
On series Is, the throttle is actually controlled by a second microprocessor. I believe it is from the Freescale 823xx family. This is probably because controlling an electronic throttle is quite computationally complex, especially when it is being used for idle control. Minute corrections to throttle angle must be made constantly to maintain idle. It also maintains a memory to account for variances in the throttle bodies performance due to aging, buildup on the throttle blade, etc. This is a big part of the reason that some cars idle poorly after a reset.
However, the main micro also has code for controlling the throttle, I believe this is to provide redundancy should the main throttle controller fail, however I imagine it can't do it as well as the dedicated chip.
On series IIs, there is a new section of code for throttle control, and all of the throttle tables are loaded to ram to speed things up. The main ecu chip is twice as fast, so it seems that the full throttle control algorithm was brought on board.
So, I will speculate that the ecu is detecting a problem with its throttle control chip during the 1st drive cycle, and consequently switching to the failsafe routine, which gives you poor idle and no cruise control.
very plausible. too bad there is no good way to replace just that chip set... oh well!
Thanks for the great info.
Ray
03-01-2012, 05:38 PM
#13
when you loaded the program it cleared the PCM memory and it just took several cycles for the code to register and indicate
you need to apply to Cobb for a copy of Accesstuner, which you can use to adjust the flash to force block the problem cel code
you need to apply to Cobb for a copy of Accesstuner, which you can use to adjust the flash to force block the problem cel code
03-01-2012, 07:21 PM
#15
mmm... tastes like jesus
Thread Starter
Join Date: Oct 2003
Location: Jacksonville, FL
Posts: 165
Likes: 0
Received 0 Likes
on
0 Posts
already playing with it :-)
03-05-2012, 08:34 PM
#16
As much as I love my theory...
What is the code you are getting?
I stumbled on this from a Mazda 3 manual:
Maybe the dealer tech just screwed up the programming job... nah, those guys are just too good.
What is the code you are getting?
I stumbled on this from a Mazda 3 manual:
1. Connect the WDS or equivalent to the DLC-2.
2. Set up the WDS or equivalent (including the vehicle recognition).
3. Select "Module Programming".
4. Select "Programmable Module Installation".
5. Select "PCM" and perform procedures according to directions on the WDS or equivalent screen.
6. Select "Programmable Parameters". [with DSC HU/CM]
7. Select "Tire Size/Axle Ratio", then select the applicable body type on the WDS or equivalent screen. [with DSC HU/CM]
Note
• If the PCM is replaced with a new one, the PCM stores DTC P0602 and illuminates the MIL even though no malfunction is detected. This means the PCM has not been configured yet.
2. Set up the WDS or equivalent (including the vehicle recognition).
3. Select "Module Programming".
4. Select "Programmable Module Installation".
5. Select "PCM" and perform procedures according to directions on the WDS or equivalent screen.
6. Select "Programmable Parameters". [with DSC HU/CM]
7. Select "Tire Size/Axle Ratio", then select the applicable body type on the WDS or equivalent screen. [with DSC HU/CM]
Note
• If the PCM is replaced with a new one, the PCM stores DTC P0602 and illuminates the MIL even though no malfunction is detected. This means the PCM has not been configured yet.
03-06-2012, 07:10 PM
#17
mmm... tastes like jesus
Thread Starter
Join Date: Oct 2003
Location: Jacksonville, FL
Posts: 165
Likes: 0
Received 0 Likes
on
0 Posts
P0610: Vehicle Options Error
Something that may support your theory... I just reviewed a data log run of my ride home tonight. I noticed that under all of my confirmed WOT runs that the Throttle position is pegged at a max of 66.69%
This does not seem to be the case as the car certainly responds as though it is indeed at or close to WOT. perhaps the 66% reading is a symptom of the chipset failure you described earlier or is this common on rx8 logs?
Ray
Something that may support your theory... I just reviewed a data log run of my ride home tonight. I noticed that under all of my confirmed WOT runs that the Throttle position is pegged at a max of 66.69%
This does not seem to be the case as the car certainly responds as though it is indeed at or close to WOT. perhaps the 66% reading is a symptom of the chipset failure you described earlier or is this common on rx8 logs?
Ray
Thread
Thread Starter
Forum
Replies
Last Post
