It's a pity, because it is really a thing which is not too good on F56.
But maybe one day a solution, my not

 

Any other comments on whether this is true or not???

So, are you saying all of us who have bought the ODB II adaptor and downloaded e-sys and the datafiles are going to have the "fun" end?

I just got my adapter this week, and am downloading software and datafiles today, with the plan to do stuff this weekend.

 

From what I've read on the BMW forums its a possibility.

 

It's reality. But if your lucky and your car is not updated to I level 54.2 then you are still good and can code the car. If you bring it to the dealer and they do an update then you will not be able to code the car once they update to 54.2. If your car is still codeable then make sure when you bring the car into the dealer to tell them Under NO circumstances do you want your car updated. Anyone that has coding already done to the car if you want to keep the features best not to even take it to dealer.

 

Can anyone provide a link to where this change by BMW is discussed?

I've only got $4.65 invested for my adaptor, so I really don't care too much. But if I understand it correctly E-Sys is used by the dealer, so BMW make's it not work for "us", then it would seem they're breaking it for the dealer too. Either that, or there's a different way to code, and that way will likely be learned / hacked later.

And it looks like E-Sys forums have been around for quite some time. If it was that easy for BMW to put an end to this, why now and not earlier?

 

It sounds like they change some identifiers. If you're patient, it will get solved.

They can't spend enough money to stop people from doing what they want.

 

Can anybody PM me the links to E-sys and the lite PSDZ data files?

 

PM sent

 

I hope it'll work again with updated psdz files. The most important coding for me was disabling auto climate control on start, disabling automatic airconditioning, and opening doors turn off radio and everything when parking the car. I don't have the fancy display so pretty basic stuff. If I had navi, disabling the agreement popup would be the first thing.

But I would choose the firmware update over coding because I don't want to experience my engine clunking again, possibly damaging something.

 

Thank you so much aaflyer!!

 

Quick question for the eSys experts out there... I have everything installed and extracted and placed in the correct folders, but when I go to connect, It see's the car's VIN number, but nothing shows up in the target window above for me to select (F056). Because nothing is selected in the target window, I am unable to click the connect button. Wondering if maybe this is part of the issue with BMW removing the coding ability or if I am just doing something wrong. Any suggestions would be greatly appreciated. Thanks! - Andrew

 

There is an annoying warning-sound when doing handbrake turns, which I do a lot now in the snow. Can that be disabled?

 

found but not tested

"bright daytime instrument display a lot better than the nighttime orange display.
KOMBI-->3007 -->DIM_NACHT_EIN-->Werte=FF

The default value is Werte=0A (10%) . This hexadecimal value relates to the sensitivity of the sensor that determines the threshold at which the display changes into its nighttime mode. When set to FF it stays on the daytime mode constantly."

 

That's what I've tried. It doesn't work.

 

This happens when E-Sys can not find the data files needed. Sounds like you don't have the PSDzData files in the proper location. They need to be in C:\DATA and E-Sys needs to be told they are located in this directory. If the above is already true you either have a bad download/data set or the files were not extracted properly.

Are you trying to use PSDzData full or lite?

 

And with the orther line AUS.
or with EIN but nicht_aktiv.
is it the same ?

 

I've tried both at different values, no dice

 

Grrrrrr ..

 

Ran the files through the extraction again, and replaced them, and now it works. Thanks for the help!

 

while you fixed your problem, the issue i had got resolved by making sure that an empty "dist" folder exists in C:\Data\psdzdata\mainseries\F056\F056_14_11_501\od x\

if you just add it to the F056 series, only F56 will show you up. if you have another series BMW, add the empty dist folder to that series ODX folder and that will show up on the list.

 

Edit: fixed this

 

What options did you code? We can likely find a solution for you but need to know what was changed first.

 

I've seen that warning on mine when trying to code tilting mirror or something, but it went away right after shutting everything off and on again.


Anyone have an update on what to expect after the ECU software update from the dealer? Does E-SYS completely see nothing? Does previous coding changes disappear and set back to default values?

I went to MINI today for Second Date, they didn't have any software updates for my 2014/9 built F56.

 

My car was at the dealer on 12/22/14 and I am still able to see everything.


Nothing looks blank or empty to me, and I coded my mirrors to fold in and video to play while moving yesterday without any issues :-)

 

Hey everyone, just finished a few long sessions of coding today did almost everything provided in F56 cheats sheet and was wondering if anyone knows how to deactivate the rear side marker lamps, I got the front amber ones done, but have no idea where the rear red ones would be, I'm going to try to put Euro arches on my car. Also has anyone messed around with the Active Sound Design settings, I activated it at ASD_CONFIGURATION=Aktiv & ASD_SOUND_4=Aktiv but when I go in my Settings menu in my car and bring up MINI sounds and try to pick an option, nothing happens, I'm guessing something else has to be activated, maybe in the ASD menu, I'll check later and post if I find something.