[capt_slow]

Lately, I've been getting this strange message on the displays. They go away when I shut off the engine (yes, engine only).



After reading a bit on the message here, it sounds like it's a genuine hardware issue. However, I only experienced the problem after the car was coded.

The message pops up once every 2-3 days, but after I coded EGS for SAT, it's starting to show up more often.

So far, EGS, FEM_BODY, HU_NBT, IHKA, KOMBI, and REM_01 are the only modules that I have touched. Could coding any of these modules throw a false Chassis message?

[steve@codemybimmer]

Originally Posted by capt_slow

Lately, I've been getting this strange message on the displays. They go away when I shut off the engine (yes, engine only).



After reading a bit on the message here, it sounds like it's a genuine hardware issue. However, I only experienced the problem after the car was coded.

The message pops up once every 2-3 days, but after I coded EGS for SAT, it's starting to show up more often.

So far, EGS, FEM_BODY, HU_NBT, IHKA, KOMBI, and REM_01 are the only modules that I have touched. Could coding any of these modules throw a false Chassis message?

I VO coded EGS with a production date of 07/13 on my 2012 F30 328i and I would get a "Transmission is overheating, park vehicle and allow to cool down" error message that would keep popping up.

When I reverted the coding, it was fine.

Try reverting the coding on EGS and KOMBI and see if it still happens.

[capt_slow]

Originally Posted by Aritaurus

I VO coded EGS with a production date of 07/13 on my 2012 F30 328i and I would get a "Transmission is overheating, park vehicle and allow to cool down" error message that would keep popping up.

When I reverted the coding, it was fine.

Try reverting the coding on EGS and KOMBI and see if it still happens.

I had the error before I coded EGS. The car is at the dealership now for the issue. If they end up coding defaults, I will probably drive it stock for a week and see if it returns. The message has definitely been happening more than once a week.

Never thought KOMBI would trigger that message, but seeing how FEM_BODY became the kitchen sink for the front side of the car, I'm not surprised either.

Thanks!

[pikcachu]

i hope you don't mean "Code default values"

[roxxor]

It is normal, I get the same message while the coding is occurring, then it goes away after a couple minutes. It depends on what module it is that you are coding, but since it goes away I never bothered to track down exactly which module it is that causes it to pop up.

[capt_slow]

Originally Posted by pikcachu

i hope you don't mean "Code default values"

Nah. I know better. I meant if the tech decides bring everything back to factory settings.

Originally Posted by roxxor

It is normal, I get the same message while the coding is occurring, then it goes away after a couple minutes. It depends on what module it is that you are coding, but since it goes away I never bothered to track down exactly which module it is that causes it to pop up.

Does it happen consistently with every drive, or only during times after coding? I'm the former and it doesnt go away till I shut off the engine.

I guess we will need to wait and see. The car is in the shop and is staying there for a few days. In the meantime, I'm driving a 320i loaner. Maybe I should code the loaner and see if I can get the message to pop up?

[roxxor]

Mine will go away after a while. For example, I code it then turn the car off. Sometimes when I come back and start the car, it will still be there, but when I drive off it'll go away after a minute or two and that'll be the last I see of it.

[pikcachu]

I got that after the skid pad at the BMWCCA Car control clinic

I'll just clear any code with e-sys afterwards :-D

[capt_slow]

I'm starting to believe it's a legitimate problem: I coded all the same tweaks into my F30 loaner and no message after 100+ miles of driving.

The car is still at the dealer, the line for their "diagnostics" team is quite long. Could be a few days before I get it back.

Meh, could be worse. I could be stuck with a enterprise rental or no loaner at all.

[Halsifer]

Originally Posted by capt_slow

I'm starting to believe it's a legitimate problem: I coded all the same tweaks into my F30 loaner and no message after 100+ miles of driving.

The car is still at the dealer, the line for their "diagnostics" team is quite long. Could be a few days before I get it back.

Meh, could be worse. I could be stuck with a enterprise rental or no loaner at all.

My first instinct if I had that problem would be to just code my car back to stock without your modifications. If it continues to appear, the car has an issue. If it goes away, your coding has some issues.

I'm not sure why you brought it to the dealer with your car coded on it because it's just asking for them to cause a commotion about. Not saying you did anything wrong, but they will give you hassle because it's something they would be able to blame and not have to pay for. They will find anything to try and make you pay. They can say, "You coded the vehicle for a feature you do not have, resulting in the malfunction when attempting to initialize the option." or some BS like that.

I'm also not sure why you coded you 320i loaner. If these values you are coding in come from the cheat sheet, then clearly nobody else will have a problem coded them. I think that would be more helpful if you told people what you were coding. Can you list the values you are changing in these vehicles?

[capt_slow]

You're absolutely right. Coding the car back to stock would have been a good troubleshooting step. I guess the reason why I skipped it this time was that none of my edits (attached) were "chassis" related. The only exception is EGS, but I had the problem before I coded this module.

You are also right that I should have coded the car back to stock before handing it over to the dealer. I researched it a bit and noticed most of others experiences involved either nothing or this...

Dealer: Something is fishy with the coding on your car
Owner: ...
Dealer: We need to code it back to defaults before we can do any troubleshooting

The above, the fact that I brought the car coded to the same dealer before, and the fact that burden-of-proof lies with the dealer probably influenced my decision. What are others opinions on this? Should one bring a coded car to the dealer or revert to defaults?

The edits I made to my car and loaner come from cheat sheets and posts. I'm not the brave sort to go poking around ECU options...in German.

[SergioK]

Pretty much every time I drop by car off at the dealer they push the latest and greatest software updates to my car and most of the others have the same experience as well. I suppose BMW keeps fine tuning and developing the software, etc. Coding or not, they will update & reset everything back to factory specs then diagnose the issue.

[Halsifer]

Originally Posted by capt_slow

The above, the fact that I brought the car coded to the same dealer before, and the fact that burden-of-proof lies with the dealer probably influenced my decision. What are others opinions on this? Should one bring a coded car to the dealer or revert to defaults?

If you are bringing it for regular service (maintenance) or repairs with something physically wrong like a leak or rattles, then don't worry about coding back to factory settings. However if something is coming up as a light on the iDrive or the instrument cluster, and it's clearly computer related in any way shape or form, then code your modified ECUs back to factory settings.

Also, I checked your list and I have applied all of your codes plus a LOT more codes (except the LED turn signals, fog lamps welcome lights, and Sport Auto) and I can assure you I have no issues. Your list seems fine, make sure you coded the Sport Auto correctly. Otherwise, it's most likely an actual issue with your Chassis. Maybe something wrong with your DHP?

[pikcachu]

please don't say "code default values" you may confuse people..... say "Code" to bring the car to the factory settings...

somebody reading this could go and click "code default values" button and screw up the whole car

[Halsifer]

Originally Posted by pikcachu

please don't say "code default values" you may confuse people..... say "Code" to bring the car to the factory settings...

somebody reading this could go and click "code default values" button and screw up the whole car

Fixed. And I really hope people coding have backups in the first place.
There should be a big sign on the front of this subforum saying, (DO NOT PRESS "CODE DEFAULT VALUES").

[pikcachu]

ya i make a CAFD backup everytime and add a changelog.txt for the record :-D

there is not such thing as too much money or too many backups

[capt_slow]

Originally Posted by Halsifer

Your list seems fine, make sure you coded the Sport Auto correctly.

I'll admit, I did this one wrong. I FDL coded EGS only instead of editing the VO and coding all the impacted modules.

I dont think that's causing the problem though, since the message appeared well before I touched anything related to the Sports Auto tranny.

[pikcachu]

Did you try clearing the codes with e-sys of the tool32.exe ?

[Halsifer]

Originally Posted by capt_slow

I'll admit, I did this one wrong. I FDL coded EGS only instead of editing the VO and coding all the impacted modules.

I dont think that's causing the problem though, since the message appeared well before I touched anything related to the Sports Auto tranny.

Well, it's in your dealers hands anyways right now. They'll fix it. Drive it uncoded once you get it back for a bit, like you suggested, and then recode it, only if you are worried though. Your coding seems fine to me. If it comes up during the recode, then maybe readdress on here. Keep us posted!

[capt_slow]

I got it back from the dealer last night.

Turned out it was a bad vertical acceleration sensor for DHP and dealer replaced it. They didnt even recode any modules.

I immediately VO coded SAT when I got back home, properly this time.

I'll drive it coded for now, if the message comes back I'll go back to stock.

Thanks to all for the help!

[capt_slow]

"Chassis: Drive Moderately" popped up on my way to work.

Looks like I'll be coding back to stock tonight.

Should I leave the LEDs in and let them flicker for a while, or should I swap them out for the OEM bulbs?

[Halsifer]

Originally Posted by capt_slow

"Chassis: Drive Moderately" popped up on my way to work.

Looks like I'll be coding back to stock tonight.

Should I leave the LEDs in and let them flicker for a while, or should I swap them out for the OEM bulbs?

LED bulbs shouldn't be and better not be affecting your Chassis sensors.