I drive a standard. It has a feature that stops the engine stalling. It causes the engine to rev up on its own while engaging the clutch.
Anyone seen a software switch to defeat this.....It is my#1 complaint. I find it really annoying.

 

Are you referring to the "rev-match" feature? I don't notice it on my 6 speed unless I am downshifting.

 

No. There is an anti-stall feature. try stalling the car in 1st gear and it will restart. If you let the clutch out with out giving the car gas and the revs drop to say 500 rpm the engine will rev-up as it thinks it is going to stall. Very annoying....IMHO.

 

Rev-matching? You can turn it off by disabling DSC. Not sure if there's a way to code out in ESYS.

 

What I'm talking about is not rev-matching. The car restarts itself when it is stalled.

 

Can't understand why anyone would want the car to re-start after a stall!
I don't have a problem with that. It's only happened a couple time since I got the car last September, and those times were because I wasn't paying attention to what I was doing.

 

I don't care about the restarting so much as the way the throttle is opened when the revs drop. Try letting the clutch out without using much gas. The car surges. This also happened with my 2014 MCS. I just want to switch this function of and allow the care to stall without the revs climbing when it is close to a stall.

 

I've never noticed this on my 2014 MCS. I'll have to check it out again. I recall stalling it once and it did not re-start or rev-up to compensate for the impending stall condition, I restarted the car myself.

 

Gotcha

 

Just verified, mine will not "rev-up" on a pending stall and will not restart by itself. I stalled it on purpose twice. I was in sport mode if that matters (I always drive in sport, habit now when I start the car, switch to sport)

 

It's not nearly as annoying as the differential torque request for the rest of the pedal mapping between gears. Though it appears the latest firmware revision I just got minimizes that delta.

In your case, you're going to have to tip in a little bit, just like you'd have to on a cable throttle car. If you're drooping the revs enough to activate the anti-stall then it seems clear you're not applying enough accel pedal.

Or are you intentionally trying to stall the car and have it not help? I guess I'm not seeing the problem here other than you trying to do something that wouldn't work on another car anyway.

 

Tried it on mine today too. Stalled on purpose. No revving to prevent stall. Everything normal. What is nice is all you do to restart it is depress the clutch pedal. That's a nice feature.

 

has anyone else had this error? I followed directions, or so I thought. . . I went through them twice and got this error.

 

when is this happening? during the install process? upon loading up? after you select F56?

 

Out of range.. Looks like your Ethernet won't detect anything from your car. Is your car ignition turned ON?

 

Has anyone tried coding using Carista and an Android tablet? The dealer had to reset the system when I went in for service. I paid $60 last year for someone else to do it for me. I could spend the same amount and do it myself.

 

"NOT supported: F55, F56"

http://www.caristaapp.com/supported-vehicles/

 

Well, crap.

Are there any Android solutions that do work?

 

I read about one for iOS that could do some minor coding, BMWhat.

It looks like it doesn't do F series cars either.

 

These guys say they're planning to release the F5x version in the 3rd quarter.
http://www.mycarly.com/home-wip/?utm..._campaign=home

 

Thanks. I subscribed to their Android/BMW emails. 3rd quarter's not too far away.

 

Has anyone tried to code for Variable Light Distribution(VLD) on an F56? I've seen on a couple threads people talking about it, but never read anything about anyone trying it before.

On my F30 335i I removed 5AP (decoder for no-dazzle high beams) and 8S4 (decoder for VLD) from the FA to get the functions of these. I've noticed on my F56 Cooper S that it still has the decoder for VLD (8S4).

Has anyone tried removing this and then VO code the FEM_BODY and KAFAS2?

I know there is relatively little harm in doing this since you aren't writing the FA back to the car, but I'd not like to be the guinea pig on this either... haha

 

It can't do any harm. I'd try it and if you are not happy then just put it back the way it was. That's the great thing about coding.

 

Sorry if I missed the "ultimate conclusion " on this question when I scanned this great thread.

Have a 2016 F56 with HK radio, base Bluetooth, no Nav, etc. Like others, I am cheesed that BMW chose to eliminate use of Siri and similar voice phone controls in this model.

I have seen the discussion of activating Bluetooth music streaming with this configuration but unsure if I saw the answer to whether coding can enable the phone voice control such as Siri. Thanks!

Note, if it's codeable, I will be having a serious discussion with Mini and the dealer.

 

Not possible.

By saying you have the base Bluetooth (but with HK speakers?), do you mean you have the base infotainment system? I have the base and there's no way to code Bluetooth streaming. I think the base infotainment system doesn't even have the menu to select Bluetooth audio and that's why even if you are able to add the VO and code it as if you do have it, it won't work. But that's just my thought. To play music, I just keep a 64GB Sandisk Fit USB 2.0 version plugged in. (The Sandisk USB 3.0 version heats up a lot, at least 5 times more than the USB 2.0 version)

Yeah, it sucks that Bluetooth stream is not standard. It's on every new car these days and our F56 already has the hardware but MINI decided we need to cough up more money to get that.