Retrofitted Power Tailgate 2007 BMW X5

[physguy]

Originally Posted by monto

Great write up. Based on your comments that the auto struts snap into place of your existing gas struts it would seem a pretty easy DIY to swap out a failed auto strut? Can you confirm and or provide any direction on removal/install.

Regards,
monto


Sent from my iPhone using Tapatalk

Yes, they swap out pretty easily. Actually broke the right-side autostrut and replaced with a gas strut until I found a replacement on eBay. (Dealer wanted $350). Only prblm was the wife bending my ear while she held the trunk up.

[ModBargains]

Sweet. Good to know the old cars can have the luxuries.

[forum1]

Originally Posted by LONE RANGER

Any pics? I have a BMW E70 X5 4.8I 2007.Missing auto trunk,rear center tv and Sat coding.Looking to do auto trunk and sat.

I'd like to see pics too, especially one of the switch (button) installed in the trim of the liftgate that was modified to accept the switch.

For folks that may not be aware, the reason so many otherwise loaded 2007 X5s don't have the power liftgate (Automatic Tailgate) is that for this first model year of the E70 BMW reported a parts shortage/supplier issue. If I recall correctly the Automatic Tailgate option was supposed to be available from the get go but was delayed, being listed as a late production availability item, and then finally scrapped altogether for model year 2007. If anyone recalls differently or knows of a 2007 that was built with the Automatic Tailgate please feel free to chime in.

For the 2012 model year the Automatic Tailgate was made standard equipment, among other options.

[95wildtt]

Hi,
Got all of the wiring run yesterday and added $316 to the VA for both the CAS and FRM modules.

I can read and code the HKL module, but it's not doing anything... doesn't even light up the button on the inside of the tailgate.
Got Error Code A2C7 (can't find what this is anywhere??) in the HKL module a couple of times last night, but cleared them and they haven't re-occurred.

I tested both actuators with 12v and they both move OK. The switches on the dash, outside of the tailgate and the new switch inside of the tailgate all unlatch the locking mechanism like they should, but nothing from the HKL... it's just doing nothing at all.

Been over the wiring and tested all connections (lower tailgate switch, CAN obviously if Ic an read the module, inside switch) and all seem to be proper and working OK, and the two 12v connections are correct.

All of the parts and the HKL module are new, so shouldn't have any concerns about bad parts.

Any ideas?

Thanks,
John

[blue dragon]

Did you code JBE (JBBF) as well? I would guess that the junction box electronics is part of it?

[95wildtt]

Originally Posted by blue dragon

Did you code JBE (JBBF) as well? I would guess that the junction box electronics is part of it?

Hey Blue, thanks for the suggestion...
Do you have any idea what would need to be coded in the JBE?
I haven't seen anyone mention this in the retrofit threads, but maybe I missed something.

Also, as part of the retrofit, you add 2 fuses to the rear junction box: #99 (40A) for the spindle drive power and #121 (5A) the power for the HKL logic itself. I've verified that the HKL is getting +12v from both of these sources.

I don't believe the OP, pendzint or islandboytrini (who posted in the What have you done to your X5 lately thread) had a CIC retrofit done...
Could that be an option?

I did the CIC retrofit a couple of years ago, and I seem to have read something about being able to control, the height of the tailgate in the CIC.
That may have been for another Exx platform or the newer Fxx, but I remember seeing that somewhere. Maybe I need to enable something in the CIC??

Left the X5 sit overnight thinking maybe the coding would take some time to be active, but still no luck...

Thanks for the feedback,
John

[blue dragon]

You'll need to code CIC to be able to adjust the height that the door opens, but there isn't anything else in there for the rear hatch

Originally Posted by 95wildtt

Hey Blue, thanks for the suggestion...
Do you have any idea what would need to be coded in the JBE?
I haven't seen anyone mention this in the retrofit threads, but maybe I missed something.


John

Are using the expert profile? After you modify the FA with code for power trunk, just code JBBF, see if fixes it. If you have any other coding in there to change default values, you will have to redo it as the expert profile defaults the values

[95wildtt]

Hi Blue,
I used the Expert Profile to Write_FA for the CAS module, then did the same for the FRM module.
No problems!
The values I had coded in each module didn't get reset in either of them, as all of the coding that I have done previously still works.
It seemed odd since I read that the modules are supposed to get reset to factory coding...
I wasn't coding the modules with the new code for the added item to the FA.

I read another post somewhere where you stated:
Write_FA ($xxx) to the CAS then code it back to the defaults (SG_CODIEREN) with the new FA...
That all went smoothly with no issues.
Assume this is now rest back to factory defaults.

Write_FA ($xxx) to the FRM then code it back to the defaults (SG_CODIEREN) with the new FA...
Now I keep getting this error when I try to code (SG_CODIEREN) the FRM module:
COAPI-1043: error during processing CBD-file
FRM2_E70.C09

I'm pretty sure that I have the latest Daten:
Version 60.1
Downloaded from here:https://mega.nz/#F!4pQjXRYb!YmZcD6u1taTxzmiCbn5TDA

Also I'm pretty sure that I have the latest version for NCS (3.1) and it's a fresh install that has been working fine until this activity.

Thought for sure I was about done with this, and now this Error...
This is driving me crazy!!

Thanks again you are always very helpful!
John

[95wildtt]

bump

[blue dragon]

1. After you do F1, then F3, select E70, then read the ECU (pick CAS or FRM) You should have the full FA loaded.
Pick enter FA, then go modify it with the ($xxx) for the power trunk. Then go code FRM, CAS and HKL (maybe JBBF too) with that FA. That will reset all the coding to the values in the FA (and in the process code them to work with the power trunk).

2. You will need to redo any individual coding you have, make sure you use the manipulation profile first before you do step 1 and backup all your .man files in the work directory as you read each module that you plan on defaulting. Apparently there is another program that allows you to save your coding while changing the FA, but I haven't used it.


Edit, I just looked at your FA trace, why are you changing your date to 1011? Not sure if you will be able to code the FRM with that date, since the script may be expecting FRM3 (which is what came with that build date)