[IndotagSwizz]

Originally Posted by maxh

I have to say this forum has been a huge help to an otherwise huge learning curve. I'm UK based with an M135i but all the coding for the F30 is the same for the F20.

I've just managed to code the beep on local/unlock and ticked the relevant option in the iDrive. Is there a way whereby it only beeps on lock and not on unlock?

Shawn - without realising it you have helped me immensely with all your posts - I have coded:

Enhanced Bluetooth
Turn Signal to 5 blinks
M Animation on Pro Nav Screen
Beep on Lock/Unlock
Digital Speed
Temp Gauge on instrument cluster (although no reading is given - just a cold/hot slide bar)
Video in Motion
Video on USB (NBT so can't import on to internal HDD unfortunately)

Cheers.

I wonder what is the car requirements in order to code the beep when lock/unlock.. Anyone knows? I'm guessing you can't code it in any F30

[maxh]

Originally Posted by IndotagSwizz

I wonder what is the car requirements in order to code the beep when lock/unlock.. Anyone knows? I'm guessing you can't code it in any F30

From the reading I've done you just need the factory fitted alarm and if you have a non-USA car that you code the FZD Alarm Type to US.

Then in the HU_NBT ECU change Acoustical_Lock_Confirm to Aktiv. Then tick the flag in the iDrive settings under "Doors".

[shawnsheridan]

Originally Posted by maxh

...
I've just managed to code the beep on local/unlock and ticked the relevant option in the iDrive. Is there a way whereby it only beeps on lock and not on unlock?...

Originally Posted by IndotagSwizz

I wonder what is the car requirements in order to code the beep when lock/unlock.. Anyone knows? I'm guessing you can't code it in any F30

Look at these for Alarm Arming/Disarming Audio options:

FZD => Akkustische Quittierung Entschaerfen = Acoustic acknowledgment when Disarming.
FZD => Akkustische Quittierung Schaerfen = Acoustic acknowledgment when Arming regardless of the door status.
FZD => Akkustische Quittierung Schaerfen mit Klappenbeachtung = Acoustic acknowledgment of Arming depends on the door status

And these for Alarm Arming/Disarming Visual options:

FZD => Optische Quittierung Entschaerfen = Visual Acknowledgment when Disarming.
FZD => Optische Quittierung Schaerfen = Visual Acknowledgment when Arming regardless of the door status.
FZD => Optische Quittierung Schaerfen mit Klappenbetrachtung = Visual Acknowledgment when Arming depends on the door status.

[jrstech]

Originally Posted by maxh

I have to say this forum has been a huge help to an otherwise huge learning curve. I'm UK based with an M135i but all the coding for the F30 is the same for the F20.

I've just managed to code the beep on local/unlock and ticked the relevant option in the iDrive. Is there a way whereby it only beeps on lock and not on unlock?

Shawn - without realising it you have helped me immensely with all your posts so thank you - I have coded:

Enhanced Bluetooth
Turn Signal to 5 blinks
M Animation on Pro Nav Screen
Beep on Lock/Unlock
Digital Speed
Temp Gauge on instrument cluster (although no reading is given - just a cold/hot slide bar)
Video in Motion
Video on USB (NBT so can't import on to internal HDD unfortunately)

Cheers.

What did you code to enable Temp Gauge on cluster? Can't find it in the coding database.

[maxh]

Originally Posted by jrstech

What did you code to enable Temp Gauge on cluster? Can't find it in the coding database.

KOMBI ECU, 3000 Module, BC_MOTORTEMP_ENABLE changed from Nicht Aktiv to Aktiv.

The graphic shows up on the instrument cluster but there is no marker/slider to tell you what the temp is - frustrating.

[maxh]

Originally Posted by shawnsheridan

Look at these for Alarm Arming/Disarming Audio options:

FZD => Akkustische Quittierung Entschaerfen = Acoustic acknowledgment when Disarming.
FZD => Akkustische Quittierung Schaerfen = Acoustic acknowledgment when Arming regardless of the door status.
FZD => Akkustische Quittierung Schaerfen mit Klappenbeachtung = Acoustic acknowledgment of Arming depends on the door status

And these for Alarm Arming/Disarming Visual options:

FZD => Optische Quittierung Entschaerfen = Visual Acknowledgment when Disarming.
FZD => Optische Quittierung Schaerfen = Visual Acknowledgment when Arming regardless of the door status.
FZD => Optische Quittierung Schaerfen mit Klappenbetrachtung = Visual Acknowledgment when Arming depends on the door status.

[jrstech]

Originally Posted by maxh

KOMBI ECU, 3000 Module, BC_MOTORTEMP_ENABLE changed from Nicht Aktiv to Aktiv.

The graphic shows up on the instrument cluster but there is no marker/slider to tell you what the temp is - frustrating.

Thanks for the info, hopefully I have that setting on my F22 since I have no temp gauge at all!

[maxh]

Originally Posted by jrstech

Thanks for the info, hopefully I have that setting on my F22 since I have no temp gauge at all!

This is what it looks like:

[jrstech]

Originally Posted by maxh

This is what it looks like:

Awesome, thank you.

[wagon_guy]

Newbie....Just got my cable and have read through the initial quickstart guide. It's a few years old, is it still accurate or is there an updated version of the guide? Could someone send me the files/download link to get started?

[shawnsheridan]

Originally Posted by wagon_guy

Newbie....Just got my cable and have read through the initial quickstart guide. It's a few years old, is it still accurate or is there an updated version of the guide? Could someone send me the files/download link to get started?

PM sent.

[tokillaworm]

Thanks so much for all the info!

Is there a token for the most recent ESYS that users are sharing, or do I have to go ahead and purchase one? Anyone willing to split?

[shawnsheridan]

Originally Posted by tokillaworm

Thanks so much for all the info!

Is there a token for the most recent ESYS that users are sharing, or do I have to go ahead and purchase one? Anyone willing to split?

Token solution is cheap, and you are driving a brand new $40k plus 2014 BMW. I think you can afford to support one of the two developers, who happen to be fellow Bimmerpost users.

[pitbub]

Originally Posted by shawnsheridan

You need to make sure that inside the VM, the Guest Windows OS does not have Firewall or any Virus / Malware software enabled, and that the VM Network adapter is bridged to the host Network Adapter, and that both Network Adapters are set for DHCP.

Until you are getting a 169.254.xxx.xxx IP adress on your Network Adpater, you will not be able to connect to car.

i leave my ibook for a PC, but for the first step same situation... no connection

if you have an idea... thanks

[shawnsheridan]

Originally Posted by pitbub

i leave my ibook for a PC, but for the first step same situation... no connection

if you have an idea... thanks

Maybe ENET Cable is crap.

[pitbub]

Originally Posted by shawnsheridan

Maybe ENET Cable is crap.

It's from CODECARD... and it's new!
Just to confirm, i need just Esys without Psdzdata to find identification of my I-step?
thanks

[shawnsheridan]

Yes, that is all you need to check I-Step.

Connection to car, should not be a problem so long as:

1) The Target Connection Window should not be blank (It should show multiple target connections for different chassis')
2) ENET Cable must be good
3) Car must have proper voltage (start engine).
4) Laptop must not have Firewall or any Antivirus software running.
5) PC Lan Adapter should get a fallback IP address of 169.254.xxx.xxx (Make sure it is using DHCP and does not have a Static IP address assigned to it)

If the above are true, and you have tried multiple PC's, then you must examine Cable, and if it is good, then something is not right with Car Gateway Module.

[pitbub]

Originally Posted by shawnsheridan

Yes, that is all you need to check I-Step.

Connection to car, should not be a problem so long as:

1) The Target Connection Window should not be blank (It should show multiple target connections for different chassis')
2) ENET Cable must be good
3) Car must have proper voltage (start engine).
4) Laptop must not have Firewall or any Antivirus software running.
5) PC Lan Adapter should get a fallback IP address of 169.254.xxx.xxx (Make sure it is using DHCP and does not have a Static IP address assigned to it)

If the above are true, and you have tried multiple PC's, then you must examine Cable, and if it is good, then something is not right with Car Gateway Module.

Very thanks for quick response
sorry but i'm novice...

1) target connection in Esys ? (for choose my serie? it's blank for me) or in Windows?
2) indeed at the end
3) that, it's ok and easy
4) i'll check another time but normaly it's fine
5)

[shawnsheridan]

So, you are saying that when you hit the E-Sys Connect button, you do not see Chassis Target Selections like this?

[pitbub]

Originally Posted by shawnsheridan

So, you are saying that when you hit the E-Sys Connect button, you do not see Chassis Target Selections like this?

Attachment 1065819

I don't have anything in this window... it's blank

[shawnsheridan]

Originally Posted by pitbub

I don't have anything in this window... it's blank

So, you have not properly installed your PSdZData to the E-Sys Data folder, or you have not set E-Sys Options properly to point to PSdZData location.

[pitbub]

Originally Posted by shawnsheridan

So, you have not properly installed your PSdZData to the E-Sys Data folder, or you have not set E-Sys Options properly to point to PSdZData location.

Ok it's exactly my doubt, i need PSdZData for the first step too... my previous request is'nt clear...
OK for resume, I copy my PSdZData in the good path, I connect my Esys and i read my I-step...