[badass335]

Originally Posted by Nick.CBR

Shiv recommended that I go to the 6AT specific 10-9 beta maps. As soon as I did that I had no issues whatsoever. If I'm not mistaken, the 10-9 6AT map back off the boost a bit more before the factory shift point.

If I were to further speculate, because the 10-9 6AT-6MT map has the lag fix in it, it was a little too aggressive for my car (that doesn't mean it won't work in others' cars though). For the most part it ran very well - the only time I would get the CEL was on a downshift from 2nd to 1st much like the OP is talking about (I try to avoid these at all costs but that's how I got my first CEL). There could be a million different things that could cause this (weather, hardware, etc.) - each car is different.

Just my experience - I'm far from being an expert at this stuff. I mean, if I were having these issues, I'd probably start at stage 1 and work my way up instead of going balls out stage 3 right off the bat (or even stage 2). It would be interesting to run the default stage 1 map on the PROcede to see if the car would throw the cyl6 misfire. I know he's done a ton of troubleshooting on this so my guess would be he has.Nick

Thats one of the things i did do. Stage 1 i was limp free. I did hit a limp once but that could have been a boost leak. The issue i have is that i have all the stage 3 mods, with the idea of ' ME WANNA GO REALLY REALLY FAST!' . If i'm stuck on stage 1 only, why bother upgrading everything? I may as well stick with tune only.

Thats interesting though that you had an issue downshifting. My issue was upshifting.

[Mike@N54Tuning.com]

Originally Posted by badass335

ME WANNA GO REALLY REALLY FAST!' .

LOL

So its been a few days.. How are you liking the JB3?

Mike

[badass335]

Originally Posted by Mike@N54Tuning.com

LOL

So its been a few days.. How are you liking the JB3?

Mike

As mentioned before, i did have 1 misfire code. I'm starting to beat up on the car and it's actually not bad. Not to de-rail this thread, i'll do a comparison probably this weekend to get a better difference. But just to update, i loaded up map 7 right at the start and got some knock codes. Lowered down to map 6 and tried and no codes. Just went back to map 7 today and i was pretty happy actually. Map 6 had performance/ lag issues. On map 7 today, no more knock codes (Needed to adapt) and car feels great.

[bimdaddy]

Originally Posted by badass335

Possible since it did happen once. This is why I say it's more the dme software. It seems on jb3, it's a lot less pronounced! To give you an idea, probably 25-30 WOT runs, we limped once. With procede, 25-30 runs, limped 25-26 times!

Mine is 9/06 production Auto and have been running fine for three months now with procede on stage 1 default setting. In the past two weeks, I WOT three times and Limp Mode all three. Restarted the car, all lights went away except today the SES stayed on. Curious to hear what you guys think....thanks.

[bimdaddy]

Originally Posted by Nick.CBR

There is a possibility there is a cyl[x] (x=cylinder number) code hung up in there causing the SES (that's what happened on my car). I went to a local auto parts store and borrowed their OBDII code scanner and cleared it out. No issues since then (no CEL's either). If you have the PROcede CANbus box, you can clear the codes yourself.

This scanner wasn't anything special (just a regular OBDII scanner), just said I had a cyl6 misfire - hit the clear button and the SES was gone. The parts guy just let me bring their rental unit out into the parking lot and do it myself which was kinda cool. BT scanner is the ideal way to go...

Good luck,

Nick

Thanks Nick. I have a regular scanner and will give it a shot.

[bimdaddy]

Sorry OP, didn't mean to jack your thread. I used my regular scanner and cleared code P0306 (cyl 6 misfire). No SES now. I will have to do some WOT and update you guys if anything comes up again. Thanks.

[badass335]

Originally Posted by bimdaddy

Sorry OP, didn't mean to jack your thread. I used my regular scanner and cleared code P0306 (cyl 6 misfire). No SES now. I will have to do some WOT and update you guys if anything comes up again. Thanks.

No worries. It seems your problem maybe related more to bad plugs etc. The reason I say that is that your car ran fine for a while then you had an issue. With my case (and a few others here), we couldn't run the maps at all. Misfire always. Anyways, i'll test my theory soon as I finally got my dealer to agree to update my DME version to the latest.

Give it a try in your car and see if the misfires come back. If it does, check them mileage on your plugs. If you've got over 15,000miles time for a change.

[midlife]

bad ass,
i know u r on the forums alot... so i am surprised you still have 29.2

my car is like yours, a 2008 produced pre march with msd80... a year ago, i got updated to 29.2 and hated it.... LAG ALL OVER THE PLACE.
after reading the 29.2 lag stickey, i immeditately went and got upgraded to 32.x and HAD THE WASTEGATE RETROFIT SOFTWARE OPTION IMPLIMENTED.
...once updated, my lag was much less.

MAYBE the latest JB· or proceede tunes can help with 29.2 lag... but why chance it !!
...imho get that crappy 29.2 software updated... but remember.. after updating... the tech needs to find and run the wastegate RETROFIT software fix.

i hope this retrofit is still available, cause i fixed my 29.2 lag problem many, many months ago.

godd luck and hope you enjoy your JB3.

production

[badass335]

it's good to know! I've never had issues before so the dealers never upgraded. After the canbus procede came out, I started having issues. I took the car in thinking it may be some hardware issue but again, nothing found. I kept on my dealers to upgrade but they wouldn't without a reason. Just saying I have lag wasn't a reason up here! Finally found a TIS and they agreed. Again this just maybe a theory that the dme upgrade would fix my issues. I wonder if I would still need the wastegate fix with the latest dme software? I'll let you guys know!

Originally Posted by midlife

bad ass,
i know u r on the forums alot... so i am surprised you still have 29.2

my car is like yours, a 2008 produced pre march with msd80... a year ago, i got updated to 29.2 and hated it.... LAG ALL OVER THE PLACE.
after reading the 29.2 lag stickey, i immeditately went and got upgraded to 32.x and HAD THE WASTEGATE RETROFIT SOFTWARE OPTION IMPLIMENTED.
...once updated, my lag was much less.

MAYBE the latest JB· or proceede tunes can help with 29.2 lag... but why chance it !!
...imho get that crappy 29.2 software updated... but remember.. after updating... the tech needs to find and run the wastegate RETROFIT software fix.

i hope this retrofit is still available, cause i fixed my 29.2 lag problem many, many months ago.

godd luck and hope you enjoy your JB3.

production

[Tag]

I just got my car back today for a similar issue but mine is a little different. I put on the 11-2 6AT maps and about a week later I finally got a chance to got WOT and felt/heard what seemed to be a misfire just over 6k rpm but nothing as far as alerts came up. Then the following day on cold start up it went into limp mode within 30 seconds of idling. This continued to happen over the next few days on cold starts.

A couple of days later I cold start the car and it began to idle really rough which didn't happen before and then I got the dreaded "service engine soon" light. Once the car warmed up however it drove fine. At this point I didn't push my car and drove it like a granny in fear or breaking her. It kept going into limp mode with "service engine soon" on cold starts over the next 3 days so I decided to yank out PROcede. I still got the same behavior for the next couple of days with PROcede not in my car until suddenly on its own the idle started to smooth out and then I stopped going into limp mode.

Took the car in and they found it's fault codes for misfiring and the cause was SIB 12 05 09. They also checked my gas for ethanol levels and found it to be within acceptable limits. They upgraded my car using ISTA/P to ver. 35.3.0.1 and kept it over the next two nights testing it on cold starts and deemed it fixed.

At this point I have no idea if PROcede was the cause of any of this but being it's winter I'm not putting it back in until spring anyway so I guess I won't find out any time soon... unless it happens again while my PROcede is not installed.

One interesting note, they knew the battery had been disconnected. Thankfully they never asked me about it but it was on the invoice. This sucks because that's a sign I may have a tune. Now I need to come up with excuses for pulling the plug if I have to bring her in next time.

[Hunter399]

I am having misfires in 5 and 6 too.

Im going to remove the PROcede tomorrow and see if the problem persists.


My software was recently upgraded, all injectors and plugs changed too.

[badass335]

that's really interesting! I'm taking my car in this week to get the software updated as well! Mine ran fine daily but as soon as I went WOT, misfires. I went to JB3 and it's been running like a champ. Zero issues after it adapted. I still think it's the canbus integration with old software. I'll be finally able to test my theory this weekend!

Originally Posted by tag824

I just got my car back today for a similar issue but mine is a little different. I put on the 11-2 6AT maps and about a week later I finally got a chance to got WOT and felt/heard what seemed to be a misfire just over 6k rpm but nothing as far as alerts came up. Then the following day on cold start up it went into limp mode within 30 seconds of idling. This continued to happen over the next few days on cold starts.

A couple of days later I cold start the car and it began to idle really rough which didn't happen before and then I got the dreaded "service engine soon" light. Once the car warmed up however it drove fine. At this point I didn't push my car and drove it like a granny in fear or breaking her. It kept going into limp mode with "service engine soon" on cold starts over the next 3 days so I decided to yank out PROcede. I still got the same behavior for the next couple of days with PROcede not in my car until suddenly on its own the idle started to smooth out and then I stopped going into limp mode.

Took the car in and they found it's fault codes for misfiring and the cause was SIB 12 05 09. They also checked my gas for ethanol levels and found it to be within acceptable limits. They upgraded my car using ISTA/P to ver. 35.3.0.1 and kept it over the next two nights testing it on cold starts and deemed it fixed.

At this point I have no idea if PROcede was the cause of any of this but being it's winter I'm not putting it back in until spring anyway so I guess I won't find out any time soon... unless it happens again while my PROcede is not installed.

One interesting note, they knew the battery had been disconnected. Thankfully they never asked me about it but it was on the invoice. This sucks because that's a sign I may have a tune. Now I need to come up with excuses for pulling the plug if I have to bring her in next time.

[badass335]

Originally Posted by Hunter399@Motorwerks

I am having misfires in 5 and 6 too.

Im going to remove the PROcede tomorrow and see if the problem persists.


My software was recently upgraded, all injectors and plugs changed too.

Are you sure they upgraded the software? To which version? I had an engine swap this year and they didn't upgrade my software! (I thought they did but later found out they didn't)

also, what map? Stage? And what rpms? Auto? You don't need to remove procede. Just use valet and see if you misfire. I couldn't. As soon as I select a map, misfire just over 6000rpms

[jpsimon]

My car is a manual 08' XI with msd80 with the 33.4 software with no issues running stage 3 11-2 map.

just throwing the info out there for comparisons sake.

[orientblue3]

Originally Posted by badass335

I believe in my case, there seems to be a conflict with the new CANBUS maps and the older DME software on the MSD80 DME that is causing the misfires. After spending a few dollars on 3 new sets of plugs, a coil pack, a new injector and labor to calibrate it, i still had the misfires. New charge pipe (in case this was the cause) and second set of forge DV's, still misfires.

I finally bought the JB3. (will do a comparison on another post). Plugged it in and tried it. No issues. As simple as it is, it worked fine. This was more a test for my car though. I drove today, and had misfires. Pulled the Procede out, threw in JB3 running map 6 (Boosting at 15.5 - 16 ) but the big thing.. NO MISFIRES AND NO LIMP!!!

Shiv definitely tells everyone to do all the bolded above first. It's amazing how little it actually solves the problem and all the money you wasted when really it was his map that caused the problem. I'd be pissed if I spent all that on his advice and it didn't fix anything.

[jpsimon]

in most cases the issues he was having are solved by the steps he took to help fix them. his problem is very rare though clearly since that didn't help... if I rememer correctly he got misfires with the jb3 as well (unless I'm thinking of someone else)

[dzenno]

Originally Posted by orientblue3

Shiv definitely tells everyone to do all the bolded above first. It's amazing how little it actually solves the problem and all the money you wasted when really it was his map that caused the problem. I'd be pissed if I spent all that on his advice and it didn't fix anything.

Not really true. I had misfires and my problem was a coil on one of the cylinders. I'm running very very smoothly now...i've made a mistake of blaming the tune right away before too but learned my lesson...to really think of it, the only problem i ever had that was related to procede was its O2 simm logic and that was fixed.

[Tag]

Being that the injectors cost the most can't you swap the one in the misfiring cylinder with one that doesn't just to test?

[Hunter399]

Originally Posted by badass335

Are you sure they upgraded the software? To which version? I had an engine swap this year and they didn't upgrade my software! (I thought they did but later found out they didn't)

also, what map? Stage? And what rpms? Auto? You don't need to remove procede. Just use valet and see if you misfire. I couldn't. As soon as I select a map, misfire just over 6000rpms

Positive they updated it, I went in for the wastegate issue and he told me they had to run an update.

All the latest firmware.

Misfire when I start the car.

[dzenno]

Try coils first dead easy

[Tag]

Well I've had my car back less than a day and just went to start it back up after it's been sitting for about 14 hours. Wandering revs upon cold start and then *BAM*, service engine soon light. SOB! Taking it into the dealer as soon as they call me back and confirm they have a loaner for me.

[JerzeySux]

Im having the same problems with the procede. I have the JB3 1.3 pin out and procede rev 1 v3 running the stage 1 AT map.
My car has no limps whatsoever with the JB3 but with the procede while cruising at 70~90 mph and i floor it after the car shifts that gear i get a misfire cylinder 6 all the time. I dont get a limp mode but i get an Service Engine sign and car would just SHAKE on throttle afterwards so i would need to restart my car. But sometimes restarting the car doesnt even work. So i need to clear the codes with the BT cable than the car would run fine again.
This is a on going problem. So my cars currently running JB3.
I do like the smoothness and daily driving of the procede better but seems like my car cant handle it.
When im at a stop and floor it straight to max i would have no problems with the procede either. It only happens at higher gears cruising speed and flooring it. When it changes gear that time it would feel like shit and give me SES light right away.

When i just floor it from 1st gear all the way i would have no problems.
It only happens at cruising speeds and when i floor it and gear changes than SES light on.