Home Forums Articles How To's FAQ Register
Go Back   Xoutpost.com > BMW SAV Forums > X5 (E53) Forum
Fluid Motor Union
User Name
Password
Member List Premier Membership Search Today's Posts Mark Forums Read

Xoutpost server transfer and maintenance is occurring....
Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management


Reply
 
LinkBack Thread Tools Display Modes
  #1  
Old 06-05-2019, 08:34 PM
Member
 
Join Date: Apr 2009
Location: Columbus, Ohio
Posts: 461
Purplefade is on a distinguished road
I知 thinking DME Ram Backup...

Ok, after weeks of troubleshooting a rough / surging idle in my 05 4.4i after completing the valve stem seals, I had all but resolved to let my Indy give it a go and then I found a thread on performing a DME Ram Backup to 途eset everything and resolve a persistent exhaust vanos issue that has been haunting me on bank 2 (2A89 dme exhaust vanos 2).

I have INPA connected and tools32 running but cannot for the life of me locate the d_motor.grp file to pull up my dme to locate that option. Seems I have only .prg files available?

What am I missing?
Reply With Quote

Sponsored Links

  #2  
Old 06-06-2019, 12:00 PM
X5only's Avatar
Premier Member
 
Join Date: Feb 2008
Location: Bellevue, WA
Posts: 937
X5only is on a distinguished road
Quote:
Originally Posted by Purplefade View Post
Ok, after weeks of troubleshooting a rough / surging idle in my 05 4.4i after completing the valve stem seals, I had all but resolved to let my Indy give it a go and then I found a thread on performing a DME Ram Backup to 途eset everything and resolve a persistent exhaust vanos issue that has been haunting me on bank 2 (2A89 dme exhaust vanos 2).

I have INPA connected and tools32 running but cannot for the life of me locate the d_motor.grp file to pull up my dme to locate that option. Seems I have only .prg files available?

What am I missing?
I致e used it before. Let me look up my system to find it. It didn稚 resolve the issue I had since it was a physical mix of sensors, but it痴 always worth a shot before delving into tearing things down.
__________________
'05 E53 X5 4.4i, '97 E39 528, '07 E92 335i, '16 F86 X6M.
Reply With Quote
  #3  
Old 06-06-2019, 12:12 PM
Member
 
Join Date: Apr 2009
Location: Columbus, Ohio
Posts: 461
Purplefade is on a distinguished road
Quote:
Originally Posted by X5only View Post
I致e used it before. Let me look up my system to find it. It didn稚 resolve the issue I had since it was a physical mix of sensors, but it痴 always worth a shot before delving into tearing things down.


Sounds good! I noticed your post way back when when you went through nearly the same thing. Between that and my Indy痴 thought that a DME Ram Backup May actually work, I thought I would give it a try before 堵iving up and towing it to the shop.

I致e had INPA running forever now, but when I hooked up to the car I got the black bubbles for battery and ignition but no options for selecting the car. Even stranger, Tools 32 loads but I don稚 seem to have access to any of the .grp files to get me in to the DME...

Not sure what I知 missing, any help would define appreciated
Reply With Quote
  #4  
Old 06-06-2019, 12:48 PM
X5only's Avatar
Premier Member
 
Join Date: Feb 2008
Location: Bellevue, WA
Posts: 937
X5only is on a distinguished road
I see the D_MOTOR GRP file in C:\EDIABAS\ECU folder. You should be able to see E53 by pressing SHIFT key in INPA.
Attached Images
 
__________________
'05 E53 X5 4.4i, '97 E39 528, '07 E92 335i, '16 F86 X6M.
Reply With Quote
  #5  
Old 06-06-2019, 01:55 PM
X5only's Avatar
Premier Member
 
Join Date: Feb 2008
Location: Bellevue, WA
Posts: 937
X5only is on a distinguished road
I would reinstall tools32/INPA with updated one. Lots of free downloads on the web.
__________________
'05 E53 X5 4.4i, '97 E39 528, '07 E92 335i, '16 F86 X6M.
Reply With Quote
  #6  
Old 06-06-2019, 03:58 PM
Member
 
Join Date: Apr 2009
Location: Columbus, Ohio
Posts: 461
Purplefade is on a distinguished road
Awesome thanks X5only! I must be missing files, I looked in ediabas\ecu directly and was unable to find the d_motor.grp file, not sure what痴 up but a reinstall may definitely fix it!

Looks like I know what I知 doing tonight! Will keep you posted

Thanks!


Oh, crazy question, not sure how large the .grp file is, would you be able to email me just that file to drop in my ecu folder? May try that before reinstalling with as much fun as the setup is and getting the cable to reconnect... I値l pm you.
Reply With Quote
  #7  
Old 06-06-2019, 05:26 PM
Member
 
Join Date: Nov 2014
Location: SF Bay Area
Posts: 829
oldskewel is on a distinguished road
For anyone who can explain what "DME Ram" is, etc. I'm curious to learn more about what that means.

Back in the olden days when I would work on control systems etc., it would be common to have stuff that never changed stored in ROM. Truly fixed. Never changed. Then you'd have higher level stuff, like your control program, stored in EEPROM, for example. Then you'd have a processor that would boot using the ROM, load the EEPROM contents into its RAM, and run, using the rest of the available RAM while it's running.

The EEPROM was static unless there was an algorithm update (programming change). The RAM was volatile / dynamic / lost whenever powering down.

Do these DME systems work similarly?

Is the DME RAM really nonvolatile? And if it's volatile, is this like formatting vs. programming?

Is this DME RAM Backup actually a "reset" / "restore" or some similar word, vs. being a backup?

Is there really just one version of the DME firmware, e.g., that comes with the INPA programming software, vs. having each car having a different program based on year/month, options, etc.?

Personally, I would be very cautious about touching the firmware if that's what this is doing.

The DME in my 1985 911 has never been touched and is running fine (simpler days).

I recently, for the first time, did a very minor EEPROM programming to fix the temperature gauge in my 2001 3.0i, and was extremely cautious before making those changes. Maybe it was paranoia, but I did not want to brick my car. One particular thing that concerned me while doing that was that the 3 different examples I found all had different interstitial values between the ones that actually mattered. Never got an answer to that other than to leave them untouched, which worked.

https://xoutpost.com/1163366-post50.html

Trying to find answers to my questions above prior to posting this, I came across a guy whose eventual solution following a DME Ram reset was to strip his car for parts. Seriously.

Last summer, when I had my engine all apart, taking my sweet time with the battery disconnected for about 2 months, I had no problems at all when re-starting. I'd be more concerned about a voltage spike during the reconnection (battery spark) vs. concern for memory corruption over a period of weeks or months.
__________________
2001 X5 3.0i, 180k miles, AT, owned since 11/2014
Reply With Quote
  #8  
Old 06-06-2019, 06:20 PM
X5only's Avatar
Premier Member
 
Join Date: Feb 2008
Location: Bellevue, WA
Posts: 937
X5only is on a distinguished road
Yeah, these tools are low level accessing factory/manufacturing configurations and not consumer configurations. So if one does not know what he is doing, trashing things is easy. I致e done ram backups so many times with no issue.
__________________
'05 E53 X5 4.4i, '97 E39 528, '07 E92 335i, '16 F86 X6M.
Reply With Quote
  #9  
Old 06-06-2019, 06:22 PM
Member
 
Join Date: Apr 2009
Location: Columbus, Ohio
Posts: 461
Purplefade is on a distinguished road
Hey oldskewel, I agree, more concern with the reconnect spike vs the sitting powered down. My Indy said it痴 more like the longer it痴 powered down the more likely it is to 努ake up foggy he called it. If it sits too long it can freeze, like the cmos in a pc freaks out and loses the time & date when that little battery goes dead, and you have to boot, power off and reboot to jump start the cmos, he said the dme ram backup is like that. More of writing a backup to the dme ram per say than backing up what is in the dme. My LIMITED understanding is the wording is backwards to what it actually does, again my limited understanding, is that it is really applying a backup copy of the dme 田ode back to the dme so it refreshes it and it 努akes up fully.

This shouldn稚 mess with the firmware per say, this should be more of a 澱oot sector repair to allow the dme to reach out to and verify all the other modules in the car and recalibrate.

All that said - I am sure someone with significantly more brain capacity than I will jump in and clear that up

I really don稚 want to mess with my firmware, just jump start the dme.
Reply With Quote
  #10  
Old 06-06-2019, 08:34 PM
X5only's Avatar
Premier Member
 
Join Date: Feb 2008
Location: Bellevue, WA
Posts: 937
X5only is on a distinguished road
Quote:
Originally Posted by Purplefade View Post
Hey oldskewel, I agree, more concern with the reconnect spike vs the sitting powered down. My Indy said it痴 more like the longer it痴 powered down the more likely it is to 努ake up foggy he called it. If it sits too long it can freeze, like the cmos in a pc freaks out and loses the time & date when that little battery goes dead, and you have to boot, power off and reboot to jump start the cmos, he said the dme ram backup is like that. More of writing a backup to the dme ram per say than backing up what is in the dme. My LIMITED understanding is the wording is backwards to what it actually does, again my limited understanding, is that it is really applying a backup copy of the dme 田ode back to the dme so it refreshes it and it 努akes up fully.

This shouldn稚 mess with the firmware per say, this should be more of a 澱oot sector repair to allow the dme to reach out to and verify all the other modules in the car and recalibrate.

All that said - I am sure someone with significantly more brain capacity than I will jump in and clear that up

I really don稚 want to mess with my firmware, just jump start the dme.
Yeah, the danger lurking here is applying the wrong backup to your dme. The software being factory level does not offer much protection to the user in making mistakes.
__________________
'05 E53 X5 4.4i, '97 E39 528, '07 E92 335i, '16 F86 X6M.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





All times are GMT -4. The time now is 09:42 AM.
vBulletin, Copyright 2019, Jelsoft Enterprises Ltd. SEO by vBSEO 3.6.0
ゥ 2017 Xoutpost.com. All rights reserved. Xoutpost.com is a private enthusiast site not associated with BMW AG.
The BMW name, marks, M stripe logo, and Roundel logo as well as X3, X5 and X6 designations used in the pages of this Web Site are the property of BMW AG.
This web site is not sponsored or affiliated in any way with BMW AG or any of its subsidiaries.