Code DME, and CAS.

 

Would it be fembody for a f30 as we don't have cas? Thanks

 

Yes, FEM_BODY then.

 

I wonder if the dealer would say anything. As I purchased a 5 year 80k km service plan. With the car going in more frequent but especially with the vo clear to see? In defense the BMW sib does say 8kl and mine was 11/13 production.

 

agreed,

dont bother changing the interval, and just do it when you want to, when the interval comes up, you can do another one
thats what I do, I for certain DONT wait 15k km's to do an oil change.
put a sticker on your windscreen,
not difficult,
then you dont need to screw around with coding

 

Not trying to resurrect old threads but this seemed to be the only one I could find referencing an F series and changing the service interval. My 2012 F10 535 just turned past 50K so the maintenance is all on me now. I'd like to reduce the service intervals in CBS to 10K to mimic the SA8KL new service intervals for the 2014 and up cars.

I had 8KC in my VO so I changed that to 8KL and then coded DME, CAS, and HU-CIC. Obviously I had to re-FDL code all of my settings in CAS and HU-CIC. The VO change did not change the service interval in iDrive; it still shows 15K. Anyone have any suggestions or has been able to get this to work?

For what it's worth my car is still on the i-level it left Dingolfing with. Any help would be appreciated:thumbup:

 

You must Flash (not Code) DME with 8KL in FA.

 

So some good news and bad news. I was able to flash the DME and after performing a CBS reset with Rheingold the oil change and all other intervals where updated appropriately.

Problem is I get a chassis stabilization DSC issue now after flashing the DME. I pulled up the fault codes in Rheingold (attached).

Here's the fault descriptions:
The control units exchange information via the data bus.

An "interface error" (invalid signal) is stored when urgently required signals are only received in the form of a substitute value or as an "invalid signal".

The fault is logged when the partner control unit (=interface) transmits a substitute value or a value designated as invalid instead of the required information. In this case, a fault code should also be stored in the corresponding partner control unit.

The test plan indicates it wants me to encode the DSC control unit. Does this mean I need to flash DSC2 as well? I didn't see that as a dependency to flash DME. Help appreciated as always:thumbup:

 

Encode means VO Code DSC, so I would VO Code it with the modified FA, and then clear Error Codes.

 

Need make sure all ECU's software were in same iStep level.

 

ZGW is the pre request almost for all other ECU, it should be the first thing to be upgraded.

 

Quick update this morning since I was definitely freaking out a little bit last night. Took the car out and drove it and most everything seemed to clear out of the Check Control in idrive. Still have a Increased Battery discharge warning but that should go away. Pulled up Rheingold after a few mins driving and cleared all of the faults and everything came back green, what a relief!:thumbup:

I would say its definitely a good idea to have the car on a battery tender/charger while doing any kind of coding or flashing, something I've neglected to this point and tried to be very careful about but moving forwards I'm going to invest in one.

Huge thanks to Shawn for all of the quick replies and extremely helpful information, I definitely appreciate it and owe you a 6 pack:thumbup: Happy New Years all :bigpimp:

 

Glad to hear it. Yes, car needs to be driven a bit afterwards to get Sensor Data from all the sensors.

There are different approaches for flashing. I do not subscribe to theory of always flashing whole car when I need only one ECU programmed. I take an incremental approach, and flash the one ECU I need, and then go from there, expanding to others as needed. I flash single ECU's all the time (CIC/NBT, Kombi, and DME), and without incident. But there are many unknown variables involved, and much depends on how far apart firmware levels are on interrelated ECU's. If firmware levels are close, the less chance of needing to flash additional ECU's, and vice versa if the firmware levels are father apart. DSC flashing, because of the Flexray Bus, will often require Flexray be reinitialized, and if that does not clear things up, then ZGW must be flashed as well.

 

do you have a guide for flashing ECU's using E-sys?
also could you send me the full PSdZData for a 2011 f10 please.

 

PM sent.

 

I am also interested in ECU flashing instructions using E-SYS. Can you please help?

 

PM sent.

 

Gents,

Bringing thread back to life, since this seems to be the only post in all BMW open forums regarding change the oil service interval for F series. Despite the success of user JamRWS6, I don't believe it is necessary to change FA and flash DME to have this interval changed. I believe that Rheingold can do it with less effort, and less risk.

My car came with oil service interval defined in the V.O. as 8KP = 8.000 km. However, the CBS is set to 6.000 km (probably, it was changed by the dealer). So, as V.O. remains the same (I read it with esys and is still 8KP), it means one can change the interval without changing the V.O.

In this thread of MHH Auto forum (to which I don't have access), one can say that with Rheingold you can simply set the interval with CBS reset.

http://mhhauto.com/Thread-BMW-F30-F...ad-BMW-F30-From-UK-How-to-change-Oil-service-interval-from-25000-Km-to-10000-Km

I gave it a try with Rheingold, and used function CBS RESET UDS as below:



This set my oil interval back to what was specified in the V.O. (8.000 km), however, it didn't pop up to request which interval is to be applyed. So, probably there is some other function that allow you to choose this interval.



Some day I'll give it another try and post results here. If anybody has acces to the mhhauto, please share the content of that post.

 

Well, my car at the time was built prior to the existence of that interval in the flash files. Therefore for cars built prior to the interval it is absolutely necessary to flash those modules at a minimum. If you are trying to reset to an interval in the psdszdata that already exists just change your VO and do a regular service reset using Rheingold.

 

Hi Jam,

Thanks for your answer. So, what you say is to edit V.O. and write it back to car? Wouldn't it also be necessary to code any modules? Anyway, it still looks odd to me. As I said, how can it be that the interval that was set in my car was different from the V.O. that I acctually read from the car? And, for last, how can the dealer make this kind of change if they can't edit V.O.? In the thread I've mentioned of MHH auto, when I google it, I'm able to read the beggining of the thread:

"Yes with rheingold you can set your next oil service in 10000kms. Just connect & start test. Then In the documents search Reset CBS and you'll have all the ..."

 

I see what you are saying, sorry I did not read your original post closely enough. I do recall an option in one of the modules to pick the interval which did not work for me because the interval I was looking for didn't exist. Now granted I did not try a service interval reset after messing with that value which may entirely work. In general unless there is some campaign by BMW I haven't seen a dealer willing to mess with those values. It may work to modify that but I am 100% sure that changing the VO, FDL coding, and resetting with Rheingold will work. When you VO code it'll set the appropriate values based upon what is in the FA anyways.

 

" I do recall an option in one of the modules to pick the interval which did not work for me because the interval I was looking for didn't exist. "

That's exactly what I'm looking for! If you can remeber how to get to this point, I would really appreciate. My goal is to get this interval adjusted to what is now applied to all cars manufactured in brazil (yes, there is a BMW plant in brazil), which is 12.000 km (don't know the V.O. code for that). I would really like to keep my original V.O., but, if there is no work around, then I'll V.O. code for this interval.

 

Hi, can you help me? i need change oil interval of my f22. in this moment my service oil say 4800 km, here is some way to overtake the km service to 500 km. (I want bmw idrive say me change oil)

i tried with ESYS....i read FA car, i change 8KM to 8KP, only edit FA , but intervale service not down km.

can you say me if i have coding module in ESYS?, Only i change FA, what other parameters should I change.

i hope answers
thanks

 

Hello!

I have v.4.10.13_PSdZData and E-Sys 3.31. Trying to flash the DME with modified FA (8KM instead of 8KA). I am doing flashing as described in "E-Sys - Flashing ECU Guide v.1.0.1.pdf". But I can not see any modules in the ECU tab list under TAL Processing. Car just had all modules updated by the dealer.
Car has IStep current F020-18-03-511, IStep last: F020-18-03-511, IStep shipment F020-16-07-506

Can it be, that the modules are updated by latest firmware and because of that nothing shows up in ECU tab? But if they are and because of that not showing up here, then how can I flash DME to change the service interval?

 

Update...

Yes, the issue with no modules, including DME not seen on ECU tab was, that the software in the car is latest and because of that nothing was there to update.

I got help from shawnsheridan and it worked.

When TAL calculating read SVT Actual, save file, edit file and change DME ecu versions to 000. For an example like this:
id 00000792
mainVersion 000
subVersion 000
patchVersion 000

After that save file, read saved file under SVT Actual. The proceed to SVT Target calculation and TAL calculation.

OK, that worked and I got te DME flashed with modified FA (8KM). But... service interval seen in HU and Kombi are still indicating 30000km interval. Any ideas?

 

If there is no update, then you have to manipulate SBT for DME current firmware to force update.

 

Can you give me the steps to do that please ? I have downloaded the latest Psdz but haven't looked into it yet so I'm not sure there will be anything new for my 2013 F30 soi I will most likely have to go the other way and force an update.

Cheers

 

v.4.27.31_PSdZData_Full:

File folder on MEGA

mega.nz

To flash with same software, edit SVT_ist, and for applicable ECU(s) to be flashed, change Main, Sub, and Patch versions to 000, e.g.:

id 00000792
mainVersion 000
subVersion 000
patchVersion 000

Do for all buy HWEL/ HWAP.

Then calculate SVT_soll, TAL, and then flash.

 

v.4.27.31_PSdZData_Full:

File folder on MEGA

mega.nz

To flash with same software, edit SVT_ist, and for applicable ECU(s) to be flashed, change Main, Sub, and Patch versions to 000, e.g.:

id 00000792
mainVersion 000
subVersion 000
patchVersion 000

Do for all buy HWEL/ HWAP.

Then calculate SVT_soll, TAL, and then flash.

Thank you so much !!

 

I have been playing with this (to get 8KL) and made the mistake of coding the DME while running. Have injected CAFD and all good again. Before I try again I wanted to check a couple of things with those that might know.

I have a 2014 F10 M5 LCI and there are two DME modules in the list in E-SYS. Can anyone explain the difference between the two?

1. Should I code both to 8KL, or only one?
2. If both does it matter which one I code first?
3. Do any of the other module orders matter?

As I understand it the process (for an F10) is:

1. Change VO to 8KL (or whatever is desired)
2. Code DME (1 or both?)
3. Code HU_NBT
4. Code FRM
5. Code CAS
6. Code JBBF
7. Code Kombi

And finally it seems DME does NOT need flashing, but I havent seen this confirmed for a F10 but suspect its related to whether the code (eg 8KL) is in the firmware already or not?
Is there a way to tell what intervals are in there before deciding if flashing is required?

 

Ok, I tried today and all went pretty well. My service interval went from 30000km to 15000km.
The date is still 24 months though (8kl should be 12months/15000kms) so not sure if that will update on the next reset or not (Suspect a CBS-reset is required to reset the date but not sure and don't want to reset this far from last oil change).

What I noticed is I get a drivetrain error when coding the second DME2. I definitely did not have the engine running this time so must be something to do with coding the second dme after the first. This went away when I coded the first DME2 again, (same as when i had to inject cafd back into them) so best to code them in reverse order.

I would recommend the following sequence.

1. Get FA
2. Edit FA from 8ka to 8kl
3. Write new FA to car
4. FP calc and activate and VO code to
5. DME2[13] This is for my car, module number would vary with ecu count.
6. DME2[12]
7. CAS
8. FRM
9. HU_NBT
10. JBBF
11. KOMBI

Note: I have also read that DME and Kombi is all that’s required and this is probably true (some others had made the VO change to all modules then looked to see which FDL codes actually changed).

So if someone wants to try this they could code just these two ECU's then drive around for a day or two and confirm.

 

Ok, thanks.

 

Just sharing my experience on this topic.
Car is 2016 F30 340i, Canadian spec with 12500km factory set service interval but as I changed my cluster because mine was tinkered with, the service interval became 19000km.
VO coded "8KP" with Esys, coded "KOMBI" and "DME" with the new VO, service interval changed to 16000km/12mo.
Reset from clutser was impossible, opened Bimmerlink, did an oil service reset from there, the new interval is 8500km, shown as 9000km at startup.

 

When you coded the DME, was your IGN set to on? Mine keeps failing to code the DME (Kombi coded just fine). Every time I try to code the DME, I lose the CAFD and I have to re-inject it

 

After all these stuff, can somebody tell me procedure to change from 8KA to 8KL?
Also I have retrofitted NBT Evo ID6 from NBT ID4 fully coded, so I don't want to ruin something with it.

 

@shawnsheridan Will doing this overwrite the re-map?

 

If you flash DME, any custom Tune will be lost.