[e.n335]

Hi,

Shiv invested quite some time developing the latest maps to solve an issue ( multiple error messages thrown at engine startup ) by delaying the time when the PROcede starts to get active. Sure, more corrections have been done in the new maps ( 12-24 and 12-29 ).

What I experienced today was exactly this error but it has nothing to do with the switched power source of the PROcede. Normally I disconnected the battery of my car every time after I loaded new firmware or maps. I also disconnected the battery after changing user torque settings. The last two times I did not disconnect the battery after changes, expecting the car will adapt within 1-2 days.

My car behaved really strange today, same symptomes as others reported on the forum. I loaded v2.0.2 12-29 yesterday. I limped to the next restaurant, disconnected the battery, took one or two beer and reconnected the battery after 1 hour again. Problems disappeared, everything was fine again and I continued my drive back home.

I highly recommend to disconnect the battery of the car after applying any changes to the PROcede so that the ECU is forced to learn the new PROcede behavior from scratch. Especially those customers, who have currently problems should give this a try. For me it solved my problem completely.

Just want to share with you.

- Eugen

[NPDAN]

Thanks Eugen

[cn555ic]

So you think with this new firmware and maps, the car really needs to adapt everytime from scratch....I mean this could possibly be the problem, but have to see...I just raised my torque level yesterday to 95% and lowered my valet to 300 as before 1700 rpms...I think that the constant starting of the car and having to raise the rpms to 1700 to disable valet is causing the ecu to cause these problems during startup....Its fuel injected and when you start , i guess its not normal for the car to need any throttle like the old carburetor days!!! I am thinking that this might be the problem!!

[stressdoc]

But good bier is very hard to find here.

[e.n335]

Originally Posted by cn555ic

So you think with this new firmware and maps, the car really needs to adapt everytime from scratch....I mean this could possibly be the problem, but have to see...I just raised my torque level yesterday to 95% and lowered my valet to 300 as before 1700 rpms...I think that the constant starting of the car and having to raise the rpms to 1700 to disable valet is causing the ecu to cause these problems during startup....Its fuel injected and when you start , i guess its not normal for the car to need any throttle like the old carburetor days!!! I am thinking that this might be the problem!!

If you currently have problems, give it a try. It's for free and probably will solve the problem. I say it helped in my case. In the future I will continue disconnecting the battery after every change, I never had unexpected problems by doing so and got some after loading 2 maps without performing the battery disconnect step.

[CaptOz]

Originally Posted by e.n335

I highly recommend to disconnect the battery of the car after applying any changes to the PROcede so that the ECU is forced to learn the new PROcede behavior from scratch.

After the change? I guess "before" or "after" have the same net result.

Cheers,

CaptOz

[e.n335]

Originally Posted by CaptOz

After the change? I guess "before" or "after" have the same net result.

Cheers,

CaptOz

My usual sequence:

1) Apply the changes
2) Dis- and reconnect battery
3) Use your car

Worked perfect

[cn555ic]

Originally Posted by e.n335

My usual sequence:

1) Apply the changes
2) Dis- and reconnect battery
3) Use your car

Worked perfect

Your not understanding what i am saying....I feel when u have the valet set at 1700 rpms...When you start the car to activate the Procede you need to press the throttle to 1700 rpms...The process of doing so, I think messes up the ecu upon startup...and causes iratic idling of car which induces reduce power limp mode!!!

[scottp999]

Very interesting. Thanks for the info. I have never disconnected the battery during v1 or v2 work.

[e.n335]

Originally Posted by cn555ic

Your not understanding what i am saying....I feel when u have the valet set at 1700 rpms...When you start the car to activate the Procede you need to press the throttle to 1700 rpms...The process of doing so, I think messes up the ecu upon startup...and causes iratic idling of car which induces reduce power limp mode!!!

Sorry but my comment was not a reply to your posting.

However, if you want a reply, get the things to work with valet settings at 300 rpm. If this works and it does not with 1700+ rpm, you got it. You don't have to guess, you can test it .

[cn555ic]

Originally Posted by e.n335

Sorry but my comment was not a reply to your posting.

However, if you want a reply, get the things to work with valet settings at 300 rpm. If this works and it does not with 1700+ rpm, you got it. You don't have to guess, you can test it .

Not trying to test it either, just wanted to know if other OP have experienced this too and use valet function like i do!!!!

[Kbueno]

Originally Posted by cn555ic

Not trying to test it either, just wanted to know if other OP have experienced this too and use valet function like i do!!!!

With the old map, I would always rev out of valet mode (1800rpm), but when going back to idle after about 2 seconds it would gallop and go to limp mode.

3rd day on 12-24 map and no problems, what does the 12-29 map do?

[cn555ic]

Originally Posted by 335lvr

With the old map, I would always rev out of valet mode (1800rpm), but when going back to idle after about 2 seconds it would gallop and go to limp mode.

3rd day on 12-24 map and no problems, what does the 12-29 map do?

Thank you, I just wanted to know if there was something to do with the VALET function upon startup...I think revving the engine to get out of valet triggers this galluping....Shivs can you see if you can address this, if indeed it is the problem...Are are other people like 335lvr and I that has these issues using valet set to 1700 or 1800 rpms...Please chime in...I kind of like the function but have turned it off because i feel and think that this is the inherent problem!!! But like i say i don't know for sure if it is indeed the problem!

[M3EST]

I think you change adaptation values when you use the stock map and then again you adapt when you choose back the tuning file.

[DreX3M]

Originally Posted by cn555ic

Thank you, I just wanted to know if there was something to do with the VALET function upon startup...I think revving the engine to get out of valet triggers this galluping....Shivs can you see if you can address this, if indeed it is the problem...Are are other people like 335lvr and I that has these issues using valet set to 1700 or 1800 rpms...Please chime in...I kind of like the function but have turned it off because i feel and think that this is the inherent problem!!! But like i say i don't know for sure if it is indeed the problem!

I've got my valet mode set at 300rpms but still get the gallops.

[cn555ic]

Originally Posted by dre335

I've got my valet mode set at 300rpms but still get the gallops.

I think we are going to have to wait till Jan 3 to see what Shiv has to say about this....This seems like its a problem that alot of us have and need to be addressed!

[LACA335i]

Originally Posted by e.n335

Hi,

Shiv invested quite some time developing the latest maps to solve an issue ( multiple error messages thrown at engine startup ) by delaying the time when the PROcede starts to get active. Sure, more corrections have been done in the new maps ( 12-24 and 12-29 ).

What I experienced today was exactly this error but it has nothing to do with the switched power source of the PROcede. Normally I disconnected the battery of my car every time after I loaded new firmware or maps. I also disconnected the battery after changing user torque settings. The last two times I did not disconnect the battery after changes, expecting the car will adapt within 1-2 days.

My car behaved really strange today, same symptomes as others reported on the forum. I loaded v2.0.2 12-29 yesterday. I limped to the next restaurant, disconnected the battery, took one or two beer and reconnected the battery after 1 hour again. Problems disappeared, everything was fine again and I continued my drive back home.

I highly recommend to disconnect the battery of the car after applying any changes to the PROcede so that the ECU is forced to learn the new PROcede behavior from scratch. Especially those customers, who have currently problems should give this a try. For me it solved my problem completely.

Just want to share with you.

- Eugen

i dont have any issue on the new map 12-29 map speed limit one. I did not disconnect my battery. I setted at 92 % torque curve. It does not feel torque or kick when i do WOT. Currently i used 91 octane gas (conoco Gas 76). I might need to change to MOBIL gas to see different. I Think MObil Gas run much cleaner than 76 conoco. I could be wrong on the assumption. ANyone in here pump MOBIL 91 octane?

[Tuned335i]

Originally Posted by e.n335

I highly recommend to disconnect the battery of the car after applying any changes to the PROcede so that the ECU is forced to learn the new PROcede behavior from scratch. Especially those customers, who have currently problems should give this a try. For me it solved my problem completely.

Just want to share with you.

- Eugen

+1

I don't understand why people have such an aversion to disconnecting the battery. I have done it every time since you started suggesting it and have NEVER had an issue. The only thing that has to be reset is the clock. Such a simple step and solves so many issues. If someone is having an issue with a map, disconnect the battery for an hour and see if the problem is solved. If not, then post something on the forum.

[cn555ic]

Originally Posted by Tuned335i

+1

I don't understand why people have such an aversion to disconnecting the battery. I have done it every time since you started suggesting it and have NEVER had an issue. The only thing that has to be reset is the clock. Such a simple step and solves so many issues. If someone is having an issue with a map, disconnect the battery for an hour and see if the problem is solved. If not, then post something on the forum.

Dude i have disconnected the battery already and its still galluping...Its not the problem...Its something else...Taking out the negative terminal is not difficult and I have tried this...Can u offer anymore advice, what else should i do besides the battery disconnect?

[Tuned335i]

Originally Posted by cn555ic

Dude i have disconnected the battery already and its still galluping...Its not the problem...Its something else...Taking out the negative terminal is not difficult and I have tried this...Can u offer anymore advice, what else should i do besides the battery disconnect?

Ok, sorry, I'm not following the "galloping" threads. Did this develop over time or did it show up when you loaded a particular map? I have a feeling that it's going to take Shiv's input to resolve.

[e.n335]

Originally Posted by cn555ic

Dude i have disconnected the battery already and its still galluping...Its not the problem...Its something else...Taking out the negative terminal is not difficult and I have tried this...Can u offer anymore advice, what else should i do besides the battery disconnect?

Did you try to go back to constant power with the PROcede unit only ? You can leave the V2 harness on switched power and connect the PROcede unit to permanent power. I would try it.