[iScream]

Originally Posted by meyergru

There is a simpler way to check if v31 addresses the problems in the first place: There should be target status numbers for that version so that he can check if the DME version # has changed. Also, usually, there are release notes that show what has been addressed. I have just e-mailed my shop's foreman.

I bet they won't upgrade my car unless it is clear that there will be no more problems. And I won't let it be flashed before that is the case, either.

About the JETstream thing: There are Progman revisions that are big enough to justify a whole new DVD, while smaller changes (such as v30.x as my foreman told me) are sent out via an online update (supposedly called JETstream) to the diagnostic units.

That's an easy problem to solve. Use one of the cars on the lot as a guinea pig. Don't let them touch your precious 27.4 until you are sure it won't f@#$ it up.


Just wondering, BTW, has anyone actually pulled the trigger and played chicken with BMW? For example, either submit a BBB claim, or take the car in and tell them to fix it or you want your money back? Or is everyone getting sweet talked and strung along by our dealers?

[meyergru]

Originally Posted by ezatnova

On the DVD thing...so this update is big enough to warrant the whole new disc? Well, hoepfully bigger is better!

I don't quite understand this: "There is a simpler way to check if v31 addresses the problems in the first place: There should be target status numbers for that version so that he can check if the DME version # has changed." What does DME version # have to do with it? Isn't DME the V80/V81, etc which is the hardware side of things?

No, what I meant is the DME software release (the hardware is either MSD80 or MSD81). A Progman release contains a number of software releases for "targets", that is, units in BMW cars - like for example, the DME. This means, that for a given Progman release, there are a list of software releases for any car type. Some units are shared between car models.

Since you can compare the target status numbers of version X and version Y, you can see if anything has changed at all for the unit in question. My foreman told me that all v30.x DME status numbers for the N54 DME were the same and also match that of v29.2 (up to some point, don't know if that has changed for a later v30.x version). Thus, it is very plausible that v30 does not fix the v29.2-induced problems (since the DME software release is the same).

If that is the case for v31, there is no use in even trying it.

Something to remember: There is no such thing as a "car's software revision". Each any every car has a (hopefully) consistent array of software releases for any of its programmable units. At least one of which has the target status number of the Progman release it was programmed with. That one unit was what the programming was done for. The other units are only updated if neccessary. That's how a measurement plan works. It is possible that the measurement plan does touch all units, but that is not guaranteed or even wanted (for time saving reasons).

[King335i]

Called my local dealership in Eugene again to ask about the possibility of installing old software on the car like 27.2, all I got in a very stern voice was, "Its IMPOSSIBLE.....IMPOSSIBLE.."

I asked him further questions and the only response he was able to muster for everything was, "I don't know". This is a load of crap, the whole situation.


I called BMWNA as well, but [B]still[B] have not heard back from them, I almost don't expect to..

[iScream]

Originally Posted by meyergru

No, what I meant is the DME software release (the hardware is either MSD80 or MSD81). A Progman release contains a number of software releases for "targets", that is, units in BMW cars - like for example, the DME. This means, that for a given Progman release, there are a list of software releases for any car type. Some units are shared between car models.

Since you can compare the target status numbers of version X and version Y, you can see if anything has changed at all. My foreman told me that all v30.x DME status numbers for the N54 DME were the same and also match that of v29.2 (up to some point, don't know if that has changed for a later v30.x version). Thus, it is very plausible that v30 does not fix the v29.2-induced problems (since the DME software release is the same).

If that is the case for v31, there is no use in even trying it.

Not the whole story... the release month is the same (08-03) but the last number changes from v29 to v30.0.1. v29's and v30's target status ends in 530 and v30.0.1 and v30.0.2 both end in 540.

This info is per this guy, who seems to know what he is talking about:
http://www.bimmerfest.com/forums/sho...32&postcount=7

[nOOgz]

@ iScream

Your link helped me in understanding, at least a little bit, what the E89x-numbers mean.

In V31, the target data status will be E89x-08-09-515. So I don't know if this helps you guys, but I hope you will soon have your 335i's back to what they once were...

[King335i]

Who was it on here that said they'd made a folder full of evidence of 29.2's detrimental effects on performance?

To whomever took the time to do that, you should make all of your evidence available to us as well, or at least tell us what evidence you used so we can all follow in your footsteps and hopefully make some kind of difference in the whole situation.

[ezatnova]

Originally Posted by iScream

That's an easy problem to solve. Use one of the cars on the lot as a guinea pig. Don't let them touch your precious 27.4 until you are sure it won't f@#$ it up.


Just wondering, BTW, has anyone actually pulled the trigger and played chicken with BMW? For example, either submit a BBB claim, or take the car in and tell them to fix it or you want your money back? Or is everyone getting sweet talked and strung along by our dealers?

I told the Regional Tech I wanted to discuss a partial refund or credit towards a new car. But, of course. The Stig that is the Regional Tech is not allowed to talk to me, so I guess they just gave me the finger in response....for now.

[ezatnova]

Originally Posted by King335i

Called my local dealership in Eugene again to ask about the possibility of installing old software on the car like 27.2, all I got in a very stern voice was, "Its IMPOSSIBLE.....IMPOSSIBLE.."

I asked him further questions and the only response he was able to muster for everything was, "I don't know". This is a load of crap, the whole situation.


I called BMWNA as well, but [B]still[B] have not heard back from them, I almost don't expect to..

Lol. Sometimes (well, most of the time) this is so frustrating you just have to laugh at the time and effort the boys in blue and white put into snubbing us.

You should have yelled back. "YOU'RE IMPOSSIBLE...ASS!"
Obviously it isn't impossible. I countered that excuse before it was thrown back at me by referencing Meyer's case where he WAS flashed back (don't worry Meyer, not by forum name or anything, just in general that I KNEW it could be done).

On the BMW NA no response by phone thing. Just CALL EM UP AGAIN. That's what I did. My guy hates the $hit out of me now, and I love it!

[ezatnova]

Originally Posted by King335i

Who was it on here that said they'd made a folder full of evidence of 29.2's detrimental effects on performance?

To whomever took the time to do that, you should make all of your evidence available to us as well, or at least tell us what evidence you used so we can all follow in your footsteps and hopefully make some kind of difference in the whole situation.

'twas me. It was a physical folder of paper that the Regional Tech took with him, so I don't have it anymore. Actually, I'm GLAD he took it. Even if he's just using it as toilet paper, I would have been more fired up if I came back to my car and it was there untouched. Hell, maybe the dealership threw it out before The Stig could even drive the car.

Anyway, I posted a few pages back a list for everyone to follow in gathering data and fighting their case most effectively. You can go check that. But, off the top of my head, I printed:
- Autoblog article
- N54 tech documents (describing wastegate operation which is now lies)
- Official BMW 335 documents (describing "eliminated lag" which is now a lie)
- Official BMW dyno chart showing plateud peak tq at 1400 rpm (I think this is likely a lie now)
- Printout of all 40 names of the "29.2 Check-In" thread
- A two-pager I typed up going into depth about bait-and-switch with the lag and also the annoying exhaust noise. I also gave him my phone #'s and signed it and all to make it as personal as I could. As I've mentioned though, it seems The Stig will not be calling me back, per my Service Manager.

[Vyruz Reaper]

Add me to the lag list.

i used to feel power come on at around 1800-2000 RPM.

Now i dont feel that power until 2800-3300 RPM depending on what gear i am in.

It really sucks... i am really starting to hate driving my car. Its sooo erratic at those lower RPM's i cant even drive smoothly.

Lemme know what i can do to contribute. I also got that burble sound when i let off the gas after accelerating. im a 29.2 with v80...

My fuel economy has only dropped to 20 from 21, but still not as dramatic as some others on here (down to 13 or so)

[meyergru]

Originally Posted by iScream

Not the whole story... the release month is the same (08-03) but the last number changes from v29 to v30.0.1. v29's and v30's target status ends in 530 and v30.0.1 and v30.0.2 both end in 540.

This info is per this guy, who seems to know what he is talking about:
http://www.bimmerfest.com/forums/sho...32&postcount=7

Yup. As I said, "up to some point, don't know if that has changed for a later v30.x version". As it turns out, only the first v30 had the same DME target number.

But it seems like the new release has a major number change:

v28.x E89X-07-12-515
v29.2 E89X-08-03-530 (actually, even v29.1.1 is the same)
v30.0 E89X-08-03-530
v30.x E89X-08-03-540
v31.0 E89X-08-09-515

I'll wait and see what my foreman tells me about the changes in that version. Let's hope for the best!

[King335i]

Thanks ezatnova!

I will follow in your footsteps and use the evidence to back up my argument.


I just now got off the phone with BMWNA, and guess what they told me?
That my dealership has to handle the problem, even though they caused the problem in the first place and have now told me they can't help. I asked BMWNA to put a call through to BMW of Eugene and inform them of these problems I've been having, but I'd already done the same and I don't expect any results from all of this.


Just what the hell do we do now? Wait for a new update that may, or may not, fix the problems we're all having?


(could someone provide a link to the 29.2 check-in thread?)

[Prof3ssor]

Originally Posted by Vyruz Reaper

Add me to the lag list.

i used to feel power come on at around 1800-2000 RPM.

Now i dont feel that power until 2800-3300 RPM depending on what gear i am in.

It really sucks... i am really starting to hate driving my car. Its sooo erratic at those lower RPM's i cant even drive smoothly.

Lemme know what i can do to contribute. I also got that burble sound when i let off the gas after accelerating. im a 29.2 with v80...

My fuel economy has only dropped to 20 from 21, but still not as dramatic as some others on here (down to 13 or so)

Welcome to the club.. Make sure you sign in here http://www.e90post.com/forums/showthread.php?t=149136

[Vyruz Reaper]

Originally Posted by Prof3ssor

Welcome to the club.. Make sure you sign in here http://www.e90post.com/forums/showthread.php?t=149136

i dont want to feel welcomed

but thanks anyways

[VDPHB]

OK...Just read through the thread and can't find the answer, so if anyone can answer this, please feel free to....

Progman v.29.2...is this only on iDrive vehicles? From what I understand, non-idrive vehicles use a different system and if that's the case, have they been affected?

Thanks.....

[Manboy]

No iDrive here, but affected BIG TIME!

[meyergru]

Originally Posted by VDPHB

OK...Just read through the thread and can't find the answer, so if anyone can answer this, please feel free to....

Progman v.29.2...is this only on iDrive vehicles? From what I understand, non-idrive vehicles use a different system and if that's the case, have they been affected?

Thanks.....

iDrive is completely unrelated to this issue. It does not matter if you have it.

Progman v29.2 does not even mean an iDrive version number. Progman is a bundle of software packages for a diagnostic unit (a PC) that is used by a BMW shop to flash several programmable units in the car. iDrive is the collective name of a subset of these units (an LCD screen, a control knob, some buttons, a radio, a navigation system a.s.o.). The problem discussed here is about the firmware for a completely different unit, namely the ECU (electronic control unit) or DME (digital motor electronic).

The DME firmware version that went sour on us has target data status E89X-08-03-530 and came first with Progman v29.2 (or as we know by now, v29.1.1). Any N54 x35i flashed with a diagnostic unit with at least that version can be affected, has it iDrive or not.

[VDPHB]

Originally Posted by meyergru

iDrive is completely unrelated to this issue. It does not matter if you have it.

Progman v29.2 does not even mean an iDrive version number. Progman is a bundle of software packages for a diagnostic unit (a PC) that is used by a BMW shop to flash several programmable units in the car. iDrive is the collective name of a subset of these units (an LCD screen, a control knob, some buttons, a radio, a navigation system a.s.o.). The problem discussed here is about the firmware for a completely different unit, namely the ECU (electronic control unit) or DME (digital motor electronic).

The DME firmware version that went sour on us has target data status E89X-08-03-530 and came first with Progman v29.2 (or as we know by now, v29.1.1). Any N54 x35i flashed with a diagnostic unit with at least that version can be affected, has it iDrive or not.

Got it...thank you for explaining this so thoroughly....now I'm worried about my upcoming 15K service on my November 07 build 2008....

Thanks again...

[mistermojorizin]

Is 30.2 the answer?

check this out, from australia: http://www.1addicts.com/forums/showthread.php?t=15004

"I had trouble with a recent software upgrade, lag, noises etc. so over the past few days the car was put on a live computer link with BMW Munich. They tested the car and decided to installed new software version 30.2. The car feels amazing, no lag and the engine progression under load is buttery smooth. The car feels faster than ever and the exhaust note is about 50% louder. I have run the car down to 800 rpm in 5th gear and floored it and by about 1200rpm it is at full haul through to 6000+ rpm. I think this software will put an end to all the worries 135 and 335 owners have had with lag with 29.2 software. The 30.2 will be released for general dealer use soon but I was one of the first lucky 135 owners with it"

[meyergru]

Originally Posted by VDPHB

....now I'm worried about my upcoming 15K service on my November 07 build 2008....

You should. Mine was built September 07, BTW. You could try to make them skip any software updates (I actually would these days). Here in Germany, if there are no ongoing internal recalls, the shops don't do any s/w updates usually. Since the first service is mainly for oil change, theoretically, a non-BMW dealer could do the work as well. Another shop probably does not even have a diagnostic unit.

Or you can at least wait until it is clear if Progman v31 does fix the problem.

Or even better: Be a guinea pig yourself! Wait until v31 becomes available and request an upgrade!

[munu]

Originally Posted by mistermojorizin

Is 30.2 the answer?

check this out, from australia: http://www.1addicts.com/forums/showthread.php?t=15004

"I had trouble with a recent software upgrade, lag, noises etc. so over the past few days the car was put on a live computer link with BMW Munich. They tested the car and decided to installed new software version 30.2. The car feels amazing, no lag and the engine progression under load is buttery smooth. The car feels faster than ever and the exhaust note is about 50% louder. I have run the car down to 800 rpm in 5th gear and floored it and by about 1200rpm it is at full haul through to 6000+ rpm. I think this software will put an end to all the worries 135 and 335 owners have had with lag with 29.2 software. The 30.2 will be released for general dealer use soon but I was one of the first lucky 135 owners with it"

Now the question is if he is talking about 30.2 or 30.0.2. Even I was thinking I got 30.2 last week but when checked the papers it was 30.0.2.

With 30.0.2 there is still turbo lag and other problems.

I read somewhere that version v31 is going to be released in Sept 3rd week, maybe that will help

[meyergru]

Originally Posted by munu

Now the question is if he is talking about 30.2 or 30.0.2. Even I was thinking I got 30.2 last week but when checked the papers it was 30.0.2.

With 30.0.2 there is still turbo lag and other problems.

I read somewhere that version v31 is going to be released in Sept 3rd week, maybe that will help

The same person is talking here about having problems after an upgrade to "v31.0". This was on 08-22-2008.

Now, he talks about an "upgrade" to v30.2, which solved those problems and which supposedly "will be released for general dealer use soon".

I seriously think he mixes up numbers BIG WAY:

His first upgrade on 08-22-2008 was most probably not v31.0 as this will be released only 09-05-2008 in Germany first, all other countries later.

The second "upgrade" on 08-29-2008 to v30.2 (he was asked if that is v30.0.2 or really v30.2, but did not answer that question) must have been a downgrade if he was right. He should have wondered or pointed out that fact in his second thread. Also, the version that is about to come out is v31.


<edit>It was actually v29.1 that caused the problems. So, apparently, v30.2 was a pre-release of the upcoming v31.0 and solved it. This looks good!</edit>