[Terry335]

Originally Posted by sflgator

I know it's all related, but let's not get too far off topic. I would like Shiv and others to chime in with some more info and advice. Thanks.

Best we sweep this back under the carpet where Shiv wants it.

[SoCal335i]

Originally Posted by Terry335

Best we sweep this back under the carpet where Shiv wants it.

Calm down terry, i dont see AA or Eurobahn addressing the topic.

[sflgator]

Originally Posted by Terry335

Best we sweep this back under the carpet where Shiv wants it.

STFU! Actually, I wish you would just get the flock out of my thread...your input is neither wanted nor productive. :mad:

[OpenFlash]

Regarding Terry's comment about certain codes being a common problem with both the Procede and Xede, I'd like to remind them that there are hundreds of Procedes on the road (not 7). If there were any 'common' problems, we would certainly know of it and would have adresses it by now. We aren't exactly playing 'catch up' over here.

Also, there is no truth to the new progman update acting as a procede watchdog. I'd be flattered if that was the case. And I'd be impressed if it were even possible. I have the newest firmware update on our car, btw. So does a tech and the parts manager at our dealership...both of whom have procedes.

Regarding sflgator's code, we can guess all we want as to its cause. The only definitive thing to do would be to get the code read by the dealership. Personally, I would do this if it became an reoccurring problem. But judging by the number of stock cars behaving similarly, I would not jump to any conclusions or point any fingers anywhere.

The only thing I would like to see swept under the carpet is Terry's disingenuous and ill-informed comments.

shiv

[bnj]

Originally Posted by sflgator

Yes, 25.01.01 which fixed the broken RTTI.

How much have you been driving since the progman update?

[Ryan(e92)]

Its funny when u have a combination of first year car on top of first twin turbo application in a high production car in over 20 years AND then modifying it and then assuming you know exactly whats wrong with it when someone gives you a brief description over the internet.

[sflgator]

Originally Posted by bnj

How much have you been driving since the progman update?

It's been almost 2 weeks, so ~ 800+ mi. without a problem, until today.

[sflgator]

Originally Posted by shiv@vishnu

Regarding Terry's comment about certain codes being a common problem with both the Procede and Xede, I'd like to remind them that there are hundreds of Procedes on the road (not 7). If there were any 'common' problems, we would certainly know of it and would have adresses it by now. We aren't exactly playing 'catch up' over here.

Also, there is no truth to the new progman update acting as a procede watchdog. I'd be flattered if that was the case. And I'd be impressed if it were even possible. I have the newest firmware update on our car, btw. So does a tech and the parts manager at our dealership...both of whom have procedes.

Regarding sflgator's code, we can guess all we want as to its cause. The only definitive thing to do would be to get the code read by the dealership. Personally, I would do this if it became an reoccurring problem. But judging by the number of stock cars behaving similarly, I would not jump to any conclusions or point any fingers anywhere.

The only thing I would like to see swept under the carpet is Terry's disingenuous and ill-informed comments.

shiv

Thanks, Shiv for your input...I tried calling you on your cell, but got your voicemail (and couldn't leave a message since your mailbox is full ), btw. So, what would you recommend...just watching it, and if it occurs again...take it in for service? What would be your best guess about the cause? Thanks.

[bnj]

Might not be related to Progman then. Nothing can be terribly wrong if the cel has gone away. I would wait and see if it is going to throw them more.

[Terry335]

Originally Posted by shiv@vishnu

Regarding Terry's comment about certain codes being a common problem with both the Procede and Xede, I'd like to remind them that there are hundreds of Procedes on the road (not 7). If there were any 'common' problems, we would certainly know of it and would have adresses it by now. We aren't exactly playing 'catch up' over here.

shiv

I counted 5 procedes with this error in this (short) thread alone. How many posts before you'll start working on a fix?

[gonzo]

Originally Posted by Fabster

I'm hearing with the progman update to 25.00.04 or greater, BMW has adjusted the monitoring parameters to check boost and fuel variations with their engine systems. This was specifically designed to address piggyback type mods with units such as the procede, xede, and RD sports modules. I hope this is not true, however, if the piggybacks were working okay prior to the progman updates and now you are having issues with CEL's / limp mode after the software upgrade, then this could be due to BMW zeroing in on these types of modification. The errors generated do not affect vehicles running turbo tuner as of yet.

[Kbueno]

Is there any way I can put the "quotes" from Terry on my Ignore List too?

[Park2670]

I have the c-reader if you want to buy it. Asked to not get it when I bought the procede but was charged and recieved it anyway.

[gonzo]

Originally Posted by Terry335

I counted 5 procedes with this error in this (short) thread alone. How many posts before you'll start working on a fix?

As soon as I start to think another way about you. BAM, you go back to being a twirp.

[OpenFlash]

Originally Posted by Park2670

I have the c-reader if you want to buy it. Asked to not get it when I bought the procede but was charged and recieved it anyway.

If that's the case, we're sorry. Just send it back and we'll credit you for it as well as shipping.
Shiv

[OpenFlash]

Originally Posted by Terry335

I counted 5 procedes with this error in this (short) thread alone. How many posts before you'll start working on a fix?

Let's get a list going of these 5 people. And under what conditions they threw a code (full boost, cruising, etc,.). As well as frequency (once, twice, reoccuring)

Shiv

[Fabster]

Originally Posted by shiv@vishnu

Regarding Terry's comment about certain codes being a common problem with both the Procede and Xede, I'd like to remind them that there are hundreds of Procedes on the road (not 7). If there were any 'common' problems, we would certainly know of it and would have adresses it by now. We aren't exactly playing 'catch up' over here.

Also, there is no truth to the new progman update acting as a procede watchdog. I'd be flattered if that was the case. And I'd be impressed if it were even possible. I have the newest firmware update on our car, btw. So does a tech and the parts manager at our dealership...both of whom have procedes.

Regarding sflgator's code, we can guess all we want as to its cause. The only definitive thing to do would be to get the code read by the dealership. Personally, I would do this if it became an reoccurring problem. But judging by the number of stock cars behaving similarly, I would not jump to any conclusions or point any fingers anywhere.

The only thing I would like to see swept under the carpet is Terry's disingenuous and ill-informed comments.

shiv

That's great that the progman wasn't the cause of the problem... all I know is the problems for me popped up after the dealer update and I was told that it was either the update in the progman or my gps that probably caused an issue. I guess I received some incorrect information. I'm sorry to all for the misinformation. Next time, I'll just keep my mouth shut as my ex-wife would tell me. Nevermind.. screw that, I hate to see my ex-wife happy.

[sflgator]

Originally Posted by Terry335

I counted 5 procedes with this error in this (short) thread alone. How many posts before you'll start working on a fix?

Just had a good conversation with Shiv about all of this, and we both agreed that what happened with my car today had absolutely nothing to do with the PROcede and/or the boost/timing control from the PROcede. I just drove around in my car again, and nothing popped up.

I will continue to monitor this, and should it occur again, I will take it to the dealer to have it checked out. However, judging from what other ppl have experienced, it seems that this might be an ongoing and sporadic problem with stock 335i's that BMW may in fact be dealing with. I do not have a code reader, so I don't know exactly what caused the "Engine Malfunction" which put it into "limp mode." Like I said in my 1st post, the light turned off and malfunction resolved itself after I shut off the car and restarted (after filling up my gas tank). My car runs as it should...with PROcede of course.

For the record though, I would like to say that I'm confident that it's cause does not stem from the PRocede, but rather something else in the 335i's engine electronics and monitoring system (that just happened to arise at 9,300 mi.). If it does not appear again, I will forget all about it!

[itsbrokeagain]

Originally Posted by shiv@vishnu

The only thing I would like to see swept under the carpet is Terry's disingenuous and ill-informed comments.

ZING!

[e46SilverM3]

I received the Procede chip today from Shiv, installed it on the car (800 miles on it) and got the same kind of CHECK ENGINE light with engine malfunction. The car would stutter at idle, make a weird pinging noise, and choke up when i would be accelerating starting at low rpms (<3000 RPM). Called Shiv, who has been polite and helpful, and he had me return the car to stock (first we tried disconnecting some of the wires, etc). NOW, in stock form, the car is STILL stuttering and the check engine light is still on.... WHAT should I do? The c-reader gave me error msg 0304 which stands for malfunction of cylinder number 4. ??? i feel like returning the car to the dealer and have them fix it...

[sflgator]

Originally Posted by Black335

I received the Procede chip today from Shiv, installed it on the car (800 miles on it) and got the same kind of CHECK ENGINE light with engine malfunction. The car would stutter at idle, make a weird pinging noise, and choke up when i would be accelerating starting at low rpms (<3000 RPM). Called Shiv, who has been polite and helpful, and he had me return the car to stock (first we tried disconnecting some of the wires, etc). NOW, in stock form, the car is STILL stuttering and the check engine light is still on.... WHAT should I do? The c-reader gave me error msg 0304 which stands for malfunction of cylinder number 4. ??? i feel like returning the car to the dealer and have them fix it...

Just so you know...your problem is NOT the problem I had today; I had absolutely no stuttering, no "pinging" noise, and no "choking." The only thing that happened today with my car was while I was cruising on the highway at 65mph, my "Engine Malfunction -- Reduced Power" Light came on (indicating my car was put into "limp mode") and it went away after I turned my car off and restarted (after I fiilled up my car with gas). That's it for me.

The problem with your car today sounds way different than my experience.

[cupspeed]

Originally Posted by Black335

I received the Procede chip today from Shiv, installed it on the car (800 miles on it) and got the same kind of CHECK ENGINE light with engine malfunction. The car would stutter at idle, make a weird pinging noise, and choke up when i would be accelerating starting at low rpms (<3000 RPM). Called Shiv, who has been polite and helpful, and he had me return the car to stock (first we tried disconnecting some of the wires, etc). NOW, in stock form, the car is STILL stuttering and the check engine light is still on.... WHAT should I do? The c-reader gave me error msg 0304 which stands for malfunction of cylinder number 4. ??? i feel like returning the car to the dealer and have them fix it...

That does not sound good. Do you think it is proceed related??

Hopefully you get it squared away quickly & painlessly.