[MechX3M40i]

Originally Posted by muzzalad

ASD as in Active Sound Design?

I think it goes into other models too.
My 30d definitely doesn't sound like a diesel from the inside.
Not sure whether it's Harman Kardon /region specific.

Had a look on RealOEM and it seems that the part that's on mine is available on other models too?

The box in the back looks pretty similar to the one on my M135i which definitely did have ASD (on top of a pre-OPF & EU sound regulations exhaust).

Hmmm... I know the 4 cylinder engines (e.g. 30i) don't get ASD, and the M40i/M40d have it. Really not sure about 30d which has a 6 cylinder diesel...

[muzzalad]

Originally Posted by MechX3M40i

Hmmm... I know the 4 cylinder engines (e.g. 30i) don't get ASD, and the M40i/M40d have it. Really not sure about 30d which has a 6 cylinder diesel...

It's the same base B57 as the M40d but from what I understand a different turbo unit and tune.

I honestly don't know. If it's not ASD, then BMW have done an absolutely epic job of making a 6 cylinder diesel engine sound like a 1980s Rover 3.5 Petrol V8.

30 odd years might affect memories, but swear it sounds pretty similar to my dad's 1984 Range Rover.

[BobsM3Coupe]

Originally Posted by nogren

You should not be able to arm the alarm with it plugged in. I couldn't, until I coded that thing off in the FZD2 ECU.

But remember that it will be powered constantly when parked, draining your battery. As discussed in other threads.

If parking only short times, should be okay to leave it plugged in.

I know that over time with the OBD reader plugged in, it would drain the battery.
But as soon as I locked the doors, the alarm went off. I then unlocked the car, the alarm then stopped sounding. The alarm is pretty loud when you're standing right near the car. Didn't want to try that again.
Maybe it's normal for it to act that way in the US?

[gugin]

My car behaves the same way. When I leave the UniCarScan plugged in the OBD port and lock the car, the alarm goes off after maybe 20 seconds. This only occurs if I lock the car. If I leave the UniCarScan plugged in when the car is sitting in my garage (I don't lock it, but take the car key with me in the house), no alarm sounds.

[BobsM3Coupe]

Originally Posted by gugin

My car behaves the same way. When I leave the UniCarScan plugged in the OBD port and lock the car, the alarm goes off after maybe 20 seconds. This only occurs if I lock the car. If I leave the UniCarScan plugged in when the car is sitting in my garage (I don't lock it, but take the car key with me in the house), no alarm sounds.

I did forget to mention that after locking, the alarm did wait a little bit till it sounded off. Same thing as you, if left unlocked, alarm doesn't sound.

[MechX3M40i]

Originally Posted by BobsM3Coupe

I know that over time with the OBD reader plugged in, it would drain the battery.
But as soon as I locked the doors, the alarm went off. I then unlocked the car, the alarm then stopped sounding. The alarm is pretty loud when you're standing right near the car. Didn't want to try that again.
Maybe it's normal for it to act that way in the US?

My understanding is that locking doors will activate the alarm system, which can detect a constant power drain at the OBD socket and treat it as a threat, hence audible alarm is triggered. Once the car is unlocked, the alarm system gets deactivated even the battery drain continues.

[teaston]

Originally Posted by gugin

My car behaves the same way. When I leave the UniCarScan plugged in the OBD port and lock the car, the alarm goes off after maybe 20 seconds. This only occurs if I lock the car. If I leave the UniCarScan plugged in when the car is sitting in my garage (I don't lock it, but take the car key with me in the house), no alarm sounds.

Must be a US spec thing, my alarm has never gone off with it plugged in, and the alarm is definitely armed as the led on the rear view mirror flashes.

[MechX3M40i]

Originally Posted by teaston

Must be a US spec thing, my alarm has never gone off with it plugged in, and the alarm is definitely armed as the led on the rear view mirror flashes.

Here's from my manual

[b.guggenmos]

Why would you leave it in the OBD II port all the time?

My M40I is still at the port according to the myBMW website. I will be coding some things off and will order the adapter soon.

[nogren]

Originally Posted by teaston

Must be a US spec thing, my alarm has never gone off with it plugged in, and the alarm is definitely armed as the led on the rear view mirror flashes.

Well, my manual, and car, function the same way. Must be a UK spec thing.

And like I have mentioned in other posts, it's possible to code it off in the roof module ECU.

[nogren]

Originally Posted by b.guggenmos

Why would you leave it in the OBD II port all the time?

My M40I is still at the port according to the myBMW website. I will be coding some things off and will order the adapter soon.

I am using BimmerLink app to show sensor values in a dash board-view, and it auto connects to the unicarscan, if plugged in...

[nogren]

Originally Posted by gugin

I very much dislike the speed limit sign in the HUD, so I tried to code it off just now. The first photo shows iDrive settings before coding. I then coded HUD_CB_SPEEDLIMITINFO under 300C HUD to "aktiv" (the default setting is "nicht_aktiv"). The second photo shows iDrive settings after coding. Things looked promising, except nothing happens when I click on "Speed limit information." It's basically a non-functional checkbox. Any ideas how to proceed?

There should be some coding needed in Kombi as well, and perhaps you can find out by looking at what happens if enabling speed limit info on a FA level.

[nogren]

Originally Posted by muzzalad

It's the same base B57 as the M40d but from what I understand a different turbo unit and tune.

I honestly don't know. If it's not ASD, then BMW have done an absolutely epic job of making a 6 cylinder diesel engine sound like a 1980s Rover 3.5 Petrol V8.

30 odd years might affect memories, but swear it sounds pretty similar to my dad's 1984 Range Rover.

Agree about the sound. It's a separate ECU, right? Then I should be able to see it in the list in esys...

And I would assume it should be mentioned in the manual, and I haven't seen it there.

EDIT: I can't find the ECU ASD01 in my SVT, i.e. my car does not have that ECU.

[nogren]

Originally Posted by nogren

There should be some coding needed in Kombi as well, and perhaps you can find out by looking at what happens if enabling speed limit info on a FA level.

Maybe DKOMBI2 -> 3000 -> HUD_VSLI_ENABLE

I guess SLI_PERMANENT_ENABLE could be tried, but should affect the one in the Intrument cluster as well. Or it takes the value you configured in iDrive.

[teaston]

Originally Posted by nogren

Well, my manual, and car, function the same way. Must be a UK spec thing.

And like I have mentioned in other posts, it's possible to code it off in the roof module ECU.

Originally Posted by MechX3M40i

Here's from my manual

It's in my manual too, strange!

[nogren]

Originally Posted by teaston

It's in my manual too, strange!

A positive gremlins for you. Now go in to BimmerCode expert mode for FSZ2, if available, and code it according to the manual.

[Nicklebon]

Originally Posted by gugin

My car behaves the same way. When I leave the UniCarScan plugged in the OBD port and lock the car, the alarm goes off after maybe 20 seconds. This only occurs if I lock the car. If I leave the UniCarScan plugged in when the car is sitting in my garage (I don't lock it, but take the car key with me in the house), no alarm sounds.

I've only had the X3 for a few days but, FWIW I do not see the behaviour described above when leaving my OBDLink MX+ plugged in. Pure speculation on my part but, maybe it uses less power than the trigger threshold.

[MOWells]

Originally Posted by Nicklebon

I've only had the X3 for a few days but, FWIW I do not see the behaviour described above when leaving my OBDLink MX+ plugged in. Pure speculation on my part but, maybe it uses less power than the trigger threshold.

It seems that you are right: the MX+ appears to have power-saving features that would keep the X3 from seeing any drain on the OBD port when locked:

“BatterySaver™ Technology
Plug it in, leave it in — without the danger of draining your vehicle’s battery. Fully automatic sleep and wake-up: does not require switches or manual button presses!“

I just ordered this device from Amazon. Being able to leave it plugged in all the time got me off the fence!

[teaston]

Originally Posted by MOWells

It seems that you are right: the MX+ appears to have power-saving features that would keep the X3 from seeing any drain on the OBD port when locked:

“BatterySaver™ Technology
Plug it in, leave it in — without the danger of draining your vehicle’s battery. Fully automatic sleep and wake-up: does not require switches or manual button presses!“

I just ordered this device from Amazon. Being able to leave it plugged in all the time got me off the fence!

Mine is the UniCarScan and also works like this, so it must vary from car to car!

[Rhidium]

Originally Posted by BobsM3Coupe

Just thought I would mention this.

I drove today with the OBDLink MX+ in the OBD port to check the coolant temp, voltage, turbo boost, etc. However, when I stopped and locked the car, the alarm started sounding off.
I was planning to leave the OBD adapter connected for the return trip home. But of course I had to remove the adapter to keep the alarm from sounding.

I've left my OBDLink LX in my car all the time (out of laziness) and no alarm issues. Wonder what's different with the MX.

[nogren]

Originally Posted by Rhidium

I've left my OBDLink LX in my car all the time (out of laziness) and no alarm issues. Wonder what's different with the MX.

You guys must have a faulty alarm. :-)

But yes they are probably not draining much, just running a small cortex cpu, interface to can bus and Bluetooth.
They guy behind UniCarScan didn't see any obvious way to easy save power when ignition is off, and "officially" recommended to remove adapter after each use.

[gugin]

Originally Posted by nogren

There should be some coding needed in Kombi as well, and perhaps you can find out by looking at what happens if enabling speed limit info on a FA level.

I see what you are saying about the need to code Kombi as well. I will try it today. I saw the same FDLs you mentioned (HUD_VSLI_ENABLE and SLI_PERMANENT_ENABLE), but I also found HUD_SPEED_LIMIT_ENABLE, SLI_HUD_PERMANENT_ENABLE, and HMI_VSLI_ENABLE. Do you know what HMI stands for? The instrument cluster? If so, then HUD_VSLI_ENABLE and HMI_VSLI_ENABLE could be the two options controlling the speed limit info in the HUD and the cluster, respectively.

How would I go about seeing what happens when I disable speed limit info or head-up display on the FA level? Is there a tutorial somewhere?