[pikkashoe]

I installed the v2 tonight. Everything went smooth until we loaded the firmware and new map. With the ignition on with out the car on, the laptop would not see the procede. Once I turned the car on, then it saw it, and I loaded the Firmware and Map, but during the firmware update the car turned off. The firmware installed properly, and then the new 2.0.1 map installed fine.

Would this cause a problem, having the car on when loading the firmware? I turned the car back on, and it was fine.

As for v2, wow, it pulls like hell to redline. Any of you guys running v2, did the way the engine sounds change, i get a growl/bark in the upper rpm range which wasnt there before? Let me know.

[kenneth]

Growl perhaps, but Bark? wook woof!!! hard to imagine. j/k

[Tuned335i]

Originally Posted by pikkashoe

I installed the v2 tonight. Everything went smooth until we loaded the firmware and new map. With the ignition on with out the car on, the laptop would not see the procede. Once I turned the car on, then it saw it, and I loaded the Firmware and Map, but during the firmware update the car turned off. The firmware installed properly, and then the new 2.0.1 map installed fine.

Would this cause a problem, having the car on when loading the firmware? I turned the car back on, and it was fine.

As for v2, wow, it pulls like hell to redline. Any of you guys running v2, did the way the engine sounds change, i get a growl/bark in the upper rpm range which wasnt there before? Let me know.

I thought the car had to be on to update maps...or was that only with V1.x?

[pikkashoe]

Well when I updated the firmware with the car on it turned off.
But it didnt throw a limpmode or anything. I turned the car back on and it was fine. I just disconnected the battery, so just waiting to give it some time.

Im just concerned about the growl in the upper rpm range when gunning it. I need some other v2 owners to chime in.

[sflgator]

Originally Posted by pikkashoe

I installed the v2 tonight. Everything went smooth until we loaded the firmware and new map. With the ignition on with out the car on, the laptop would not see the procede. Once I turned the car on, then it saw it, and I loaded the Firmware and Map, but during the firmware update the car turned off. The firmware installed properly, and then the new 2.0.1 map installed fine.

Would this cause a problem, having the car on when loading the firmware? I turned the car back on, and it was fine.

As for v2, wow, it pulls like hell to redline. Any of you guys running v2, did the way the engine sounds change, i get a growl/bark in the upper rpm range which wasnt there before? Let me know.

Hooray, you got v2...congrats!!! Give it a few days for the ECU to adapt; it will get even better, and you should probably stay @ the default TQ curve or experiment in small increments. Now you're ready for Moroso! btw -- I didn't notice any change in terms of engine or exhaust growl...it could be a placebo effect.

[pikkashoe]

If the car throws a code, will the check engine light come on? Or limpmode

[pikkashoe]

Sflgator, did your car sound different in the upper rpm range when getting on it hard, my car sounds like its got a growl only when i gun it, which wasnt there before.

Car pulls like crazy now to redline, its amazing, but the new sound is concerning me.

[sflgator]

Your "growl" in the upper rpm range wasn't more like a loud clicking, was it? Also, you are running with the default TQ curve, right? Don't go to 100% across the board for now.

[sflgator]

Originally Posted by pikkashoe

Sflgator, did your car sound different in the upper rpm range when getting on it hard, my car sounds like its got a growl only when i gun it, which wasnt there before.

Car pulls like crazy now to redline, its amazing, but the new sound is concerning me.

Try lowering all TQ curve values down 5%...see if that eliminates this "growl" noise. Are you sure it's not a loud "clicking?" Either way...lower your TQ curve values or make sure you're at default TQ curve values and go easy on it for a few days while the ECU adapts.

[pikkashoe]

How do I know what the default torque settings are.

The noise is definately a growl, sort of sounds like an m3 when you hit, that distinct metal sound (those of you who own m3's).

Im reconnecting the battery now. I will baby it for a couple days as well.

[sflgator]

Default TQ settings are in place when you connect v2 and download the v2.0.1 s/w map. You don't necessarily have to "baby" it but just allow the ECU to adapt for a few days; e.g. don't push it ALL the way to redline for a few days.

[pikkashoe]

Ooops, shivs instruction say nothing about not pushing it to redline. Pushed a couple times tonight. 4th gear is acting funny, but im sure its just needs to adapt.

My tq settings are this (untouched)
2500 - 94.902
3000 - 90.1961
3500 - 90.1961
4000 - 90.1961
4500 - 92.12569
5000 - 94.902
5500 - 96.86
above - 100

Does this sound like stock. I think it is. Well I will just baby her for the next few days. But wow its amazing.

[NPDAN]

I can connect to the PROcede just fine with the car off. I have never once had the ignition on when loading any maps or messing with the tq settings...They seem to stick fine...

[pikkashoe]

Does having the car on hurt it though when connecting to procede. I dont think so. I had it on now to check the torque settings and the rpm valet switch.

Well the car is done for the night. Im going to post a quick v2 review. Im guessing the new engine tone im hearing is because all the new added power up to the redline.

No one else has experienced this? Like sflgator said, i wont red line it for the next few days, and let the car/ecu adapt.

[OpenFlash]

With v2, the whole PROcede set-up now runs on switched power. This mean that you will have to have the ignition ON (but engine not running) when uploading map/updating firmware. Before with v1, when the PROcede was running off of constant power, it didn't matter if the ignition was OFF since the PROcede was getting power nonetheless.

Oh yeah... leave the default torque settings alone. No need to change them. Especially when we are just about to release v2.0.2.

Shiv

[Tuned335i]

Originally Posted by sflgator

Try lowering all TQ curve values down 5%...see if that eliminates this "growl" noise. Are you sure it's not a loud "clicking?" Either way...lower your TQ curve values or make sure you're at default TQ curve values and go easy on it for a few days while the ECU adapts.

Didn't Shiv post someplace the values to put in across the board to replicate a stock tune, and also the values to replicate V1.47? That noise would concern me too. My guess is that it will go away when the ECU adapts. I don't recall any other V2 users report that type of sound. I'm curious to see what happens over the weekend.

Pikkashoe, what's the butt-dyno say about V2?

[335iheLLraiseR]

Originally Posted by pikkashoe

Does having the car on hurt it though when connecting to procede. I dont think so. I had it on now to check the torque settings and the rpm valet switch.

Well the car is done for the night. Im going to post a quick v2 review. Im guessing the new engine tone im hearing is because all the new added power up to the redline.

No one else has experienced this? Like sflgator said, i wont red line it for the next few days, and let the car/ecu adapt.

congrats! me and Joyride were talking the other day, he said he knows you, so HI.

i don't know, but mine will be here tomorrow morning. i'll let you know, though. and none of that default shit. 100% across the board. slight maybe i'll tone it down between 1k and 2k.

Eugen did mention something about disconnecting the battery when changing torque values, although i don't know how that works for the initial install.

again congrats, so whats the south florida total for V2......umm 2 people?

[pikkashoe]

Shiv two quick questions.

Why did the car turn off when uploading firmware?

Also should the car sound different at high rpm range at full load.

Thanks for a wonderful product. The car is a super beast now.

[pikkashoe]

Im posting a review now in the forum.

[pikkashoe]

335hellraiser,

I keep reading not to do 100 across the board. Trust me you wont need it. PM me tommorow, im curious to see if you experience the same noise im hearing.

I did disconnect the battery afterwards. SFLGator said it will take a couple days to fully adapt, so for now I will just drive normal. No more redlining!!

[NPDAN]

Originally Posted by shiv@vishnu

With v2, the whole PROcede set-up now runs on switched power. This mean that you will have to have the ignition ON (but engine not running) when uploading map/updating firmware. Before with v1, when the PROcede was running off of constant power, it didn't matter if the ignition was OFF since the PROcede was getting power nonetheless.

Oh yeah... leave the default torque settings alone. No need to change them. Especially when we are just about to release v2.0.2.

Shiv

Hey Shiv, I've never had the car in the on position when when I uploaded V2.0.1. Does that mean it's not loaded? Whats loaded then?

[335iheLLraiseR]

Originally Posted by pikkashoe

335hellraiser,

I keep reading not to do 100 across the board. Trust me you wont need it. PM me tommorow, im curious to see if you experience the same noise im hearing.

I did disconnect the battery afterwards. SFLGator said it will take a couple days to fully adapt, so for now I will just drive normal. No more redlining!!

i already have that growl, its my exhaust.

edit: and a bark...lol