Fixed via coding: tailgate "slam!"

[///d]

This came across a facebook page for you 17+ owners. I don't have a 17+ so I cant speak for how well it does or does not work.

"For those who have F15 ‘17+ that have been trying to code their tailgates to stop slamming, I found this code to be super helpful. Although not fully soft closing, it’s not as painful as it’s current settings now.

And sorry I only know this code for Bimmercode, not sure for esys:

Tailgate Module (HKFM2) > search for ‘Profileclosestopnode2PWMplg > custom > change first byte to 00x00 and second byte to 00xC8.

Good luck!"

[CanadianLurker]

Originally Posted by 2one8

This came across a facebook page for you 17+ owners. I don't have a 17+ so I cant speak for how well it does or does not work.

"For those who have F15 ‘17+ that have been trying to code their tailgates to stop slamming, I found this code to be super helpful. Although not fully soft closing, it’s not as painful as it’s current settings now.

And sorry I only know this code for Bimmercode, not sure for esys:

Tailgate Module (HKFM2) > search for ‘Profileclosestopnode2PWMplg > custom > change first byte to 00x00 and second byte to 00xC8.

Good luck!"

Thanks!

Updated my 2018 with these values and it made a significant difference.

As noted, it isn't a fully soft-close fix but at this point it's such an improvement over the original jarring slam that I'm very pleased with the result. You'll still notice when the hatch closes, but you'll no longer be disturbed or alarmed by a harsh slam!

[crystalworks]

Welp... now I need to learn esys, FA, and VO coding for the F15. Just recently learned ZCS for my E53 and VO for my E61/E70 with NCSexpert/dummy/inpa. BMWs, what are you gonna do. Still need to get ISTA running on the laptop...

I'll put a pot of coffee on in the morning and do some more "light" reading.

[Sophisticated Redneck]

This fix applies to the E70 and I learned that the hexadecimal values are divided into 9 segments that each segment controls approx 10 degrees of motion.

Not much appears to have changed on the F15 so these values will also apply to the F15. Keep in mind its hexadecimal so use an online calculator to convert (example if you want a 20% closing speed at the last 10 degrees of movement before it latches, 20 in hex is 14. Also if you go too slow it can freak out the safety override as it thinks the hatch is stuck and will open back up.
Here are the values I used: 10161E262E36404040 this translates to a transition of speed from 64% to 16% right before it latches. The stock speed was 64% all the way down to latch/close. You can hear an see it slow down in the videos below.

Stock:

Coded:

[sbrook02]

Originally Posted by X5X35D

yeah i see those, there's actually a lot more options close and speed related but i don't know what parameters to change
i guess one day i'll just start changing them one by one until i get it right

Originally Posted by 2one8

This came across a facebook page for you 17+ owners. I don't have a 17+ so I cant speak for how well it does or does not work.

"For those who have F15 '17+ that have been trying to code their tailgates to stop slamming, I found this code to be super helpful. Although not fully soft closing, it's not as painful as it's current settings now.

And sorry I only know this code for Bimmercode, not sure for esys:

Tailgate Module (HKFM2) > search for 'Profileclosestopnode2PWMplg > custom > change first byte to 00x00 and second byte to 00xC8.

Good luck!"

Based on the above tips for 2017+ X5, here is where to find the coding locations in BimmerCode:

Tailgate Function Module > 3011 APPL_PLG_SPEED_PROFILE

Parameters to change are the byte values for closing power at different positions in movement. Reduce to slow down.

ProfileCloseStopNode1PwmPlg, ProfileCloseStopNode2PwmPlg, etc.

Make sure you change both Node1 and Node2 power values for best results (the Facebook tips only mention Node2 therefore it's not ideal. If you only want to change one then better to change Node1). A lower power will give you less slam. So if you are not happy with 00C8, pick a smaller byte value such as 00A0.

The following hex values in ascending order are provided by BMW:

000A, 00A0, 00BE, 00C8, 00FA, 017C, 0212, 0226

corresponding to decimal values of:

10, 160, 190, 200, 250, 380, 530, 550, respectively.

[MK2018]

Yesterday I coded mine, I have changed parameters in 4 spots

ProfileCloseStopNode1PwmPlg, ProfileCloseStopNode2PwmPlg

ProfileCloseStopNode1PosPlg, ProfileCloseStopNode2PosPlg

It works very good on my 2018 X5

[CanadianLurker]

Originally Posted by sbrook02

Based on the above tips for 2017+ X5, here is where to find the coding locations in BimmerCode:

Tailgate Function Module > 3011 APPL_PLG_SPEED_PROFILE

Parameters to change are the byte values for closing power at different positions in movement. Reduce to slow down.

ProfileCloseStopNode1PwmPlg, ProfileCloseStopNode2PwmPlg, etc.

Make sure you change both Node1 and Node2 power values for best results (the Facebook tips only mention Node2 therefore it's not ideal. If you only want to change one then better to change Node1). A lower power will give you less slam. So if you are not happy with 00C8, pick a smaller byte value such as 00A0.

The following hex values in ascending order are provided by BMW:

000A, 00A0, 00BE, 00C8, 00FA, 017C, 0212, 0226

corresponding to decimal values of:

10, 160, 190, 200, 250, 380, 530, 550, respectively.

Thanks for the additional detail provide - I changed from 00C8 which was an improvement to 00BE which is even better! I also coded both Node1 and Node2 while I was in there for good measure.

[CanadianLurker]

Originally Posted by MK2018

Yesterday I coded mine, I have changed parameters in 4 spots

ProfileCloseStopNode1PwmPlg, ProfileCloseStopNode2PwmPlg

ProfileCloseStopNode1PosPlg, ProfileCloseStopNode2PosPlg

It works very good on my 2018 X5

What values did you use for: ProfileCloseStopNode1PosPlg, ProfileCloseStopNode2PosPlg ??

[MK2018]

Originally Posted by CanadianLurker

What values did you use for: ProfileCloseStopNode1PosPlg, ProfileCloseStopNode2PosPlg ??

00A0 for all 4

[jdbretz]

If you are using and E-Sys, you can add this to your cheat code XML:

	<cafd id="00005710" name="HKFM_2015" author="J" series="F015">
		<code description="ENABLE No Slam Tailgate">
			<group id="3011">
				<function start="75" end="76" comment="ProfileCloseStopNode1PosPlg" mask="11111111b">00, A0</function>
				<function start="77" end="78" comment="ProfileCloseStopNode1PwmPlg" mask="11111111b">00, A0</function>
				<function start="79" end="80" comment="ProfileCloseStopNode2PosPlg" mask="11111111b">00, A0</function>
				<function start="81" end="82" comment="ProfileCloseStopNode2PwmPlg" mask="11111111b">00, A0</function>
			</group>
		</code>
	</cafd>

For my vehicle ('18), my CAFD ID for the HKFM_2015 module is 5710. Other vehicles may have 2098 (at least going off what I found present in my FDLCheat.xml), so if this doesn't show up in your cheat sheet, you may need to change the ID at the beginning. This is set to code the value 00A0 for each.

[j.maldo]

Thank you @jdbretz modifying the cheat sheet didn't work for me but I was able to find the parameters with Esys following your code and manually change them (that specific module is not mapped by my launcher pro). Anyway, the tailgate now closes softly.

[135iUSN]

The coded the magic yesterday - much improved thanks

[scotty339]

Coded the trunk soft close as well as changed key fob close from press to hold to one touch.

THANKS!

[toth]

Hi, does anyone knows how to make this coding in MK2017? In my E-SYS 3.27.1 i can't see much in HKFM2 while editing FDL. Looks like nothing is translated into "proper" names, only folders with numbers. Do I need newer version of E-SYS?

[bmwx5nyc]

Originally Posted by smyles

Stumbled upon this quick fix for the infamous tailgate slam, using custom values in 3020 HKL_KINEMATIC in the tailgate module. Pic 1 is my default, pic 2 is new values (I used bimmercode, purists can use e-sys, obviously).

The improvement is most apparent when closing while inside, the "slam!" is completely replaced with a soft touch, very equivalent of how soft close doors operate.

this is a good coding feature but there's a downside, it doesn't code your trunk fully and it's not a big deal. but just for people that don't know.

[wolfy]

Hi, I tried the coding on a f25 2017, here’s what I learned

- car has the “old module” meaning you need to search for HKL_KINEMATIK
- worked fine with Bimmercode on Android and enet cable, super fast
- it’s not enough to alter the first byte and leave the rest at 58. Looks like only editing the first byte has no impact.
- I changed to 0A 0A 58 58 58… (also tried 0A 32 58 58…)
- values are in HEX so use a conversion from decimal. Do not simply put 10-20-30.. because 20 in hex is actually 32 in decimal
- the new values will slow down the lid by reducing the power of the engine, not the speed. Speed reduction is a consequence of reducing the power
- If the car is inclined with the tailgate lower than the front of the car, the tailgate may not close because the engine does not have enough power to close it (!!!) I tested and this validates. Probably that is why bmw chose to slam it, to make sure it closes no matter the inclination
- the 0A 0A 58 58… configuration is fine for flat and low inclinations, but if you generally operate the trunk on steep slopes, you will have to manually push the tailgate to get it closed
- even with 0A as the first byte (10% power) it will still slam, just not as hard as with the default 32 (which is 50% power)

Does anyone know how to control the speed without affecting the power ?

[Arthuar]

Sorry, I was following, thought the module on E70 and F11 are similar.
I got an F11, 2010.

I inserted the values of the first page ( 0x20, 0x30, 0x40, 0x58, 0x58...etc) using expert mode with BimmerCode.
Once saved and coded, no difference at all.

Any suggestion?

[Qsilver7]

Originally Posted by Arthuar

Sorry, I was following, considering the module on E70 and F11 are similar.
I got an F11, 2010.
I inserted the values of the first page ( 0x20, 0x30, 0x40, 0x58, 0x58...etc) using expert mode with BimmerCode.
Once saved and coded, no difference at all.

Any siggestion?

The coding parameters for the F11 are different than the parameters for the F15 (X5) & F85 (X5M). Using the F15 numbers is probably why it didn’t work.

You can see the different codes the F11 has vs the F15 in the screen shot below from the Bimmercode app. The idea is to slow the closing of the lift gate the closer it gets to being shut. I’m not what the number needs to change to for the F11…but perhaps someone understands the hex (?) code numbers.

[Arthuar]

Originally Posted by Qsilver7

The coding parameters for the F11 are different than the parameters for the F15 (X5) & F85 (X5M). Using the F15 numbers is probably why it didn’t work.

You can see the different codes the F11 has vs the F15 in the screen shot below from the Bimmercode app. The idea is to slow the closing of the lift gate the closer it gets to being shut. I’m not what the number needs to change to for the F11…but perhaps someone understands the hex (?) code numbers.

Bad I’m answering late, though I needto say appreciated it.
Unfortunately I haven’t found anything good yet, even though I’m investigating.
In the mean time, the parameter has been changed, now I setted F31 preset in expert mode; its’ not a big jump but the “slam” is a bit “softer” to say..

[Qsilver7]

Originally Posted by Arthuar

Bad I’m answering late, though I needto say appreciated it.
Unfortunately I haven’t found anything good yet, even though I’m investigating.
In the mean time, the parameter has been changed, now I setted F31 preset in expert mode; its’ not a big jump but the “slam” is a bit “softer” to say..

Thanks for the update. The only suggestion I have that may help "fine-tune" your tailgate is...take note that the original coding uses the same parameters all the way down to BYTE 1. This means that the speed of the tailgate is the same until it gets to the end. This is what's causing the slam.

Try keeping the original Byte 3 through Byte 8 coding parameters...then lower the values for Byte 1 and Byte 2 (to slow the tailgate just before closing).

Try that and see if it works better. You can see an example from an F85 below that was posted early in the thread...note how the "customized" Byte 0,1, and 2 have lower values (to slow the movement) which should prevent the "slam" vs the original coding parameters that were all the same except for Byte 0.

[mrfochon]

Wondering if we could find the same fir the windows when pulling windows all the way up slowing it down before touching the end
Could not find it but if someone has knowledge in Expert mode

[Arthuar]

Originally Posted by Qsilver7

Thanks for the update. The only suggestion I have that may help "fine-tune" your tailgate is...take note that the original coding uses the same parameters all the way down to BYTE 1. This means that the speed of the tailgate is the same until it gets to the end. This is what's causing the slam.

Try keeping the original Byte 3 through Byte 8 coding parameters...then lower the values for Byte 1 and Byte 2 (to slow the tailgate just before closing).

Try that and see if it works better. You can see an example from an F85 below that was posted early in the thread...note how the "customized" Byte 0,1, and 2 have lower values (to slow the movement) which should prevent the "slam" vs the original coding parameters that were all the same except for Byte 0.

...then, if I had understood correctly I must change the numeric values inserted in Byte 0, 1, 2 Right?!
That said, these number must be of a special kind or..I mean, like 10, 20 30 or I can fill them as 18, 21, 25?
Thanks for ur passion