When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
i have done 4 displays already but this is the first one without hud. And these problems are new, I nave had them befor.
the steps you talk about aren’t different then mine. They all the same so, answer to you’re question is yes.
my guess is that the missing APIX connection is the culprit, if you added the MOST connection between the KOMBI and HU already. I don't have an up-to-date version of ISTA, so i can't pull the wiring diagram for you
Thank you everyone for helping me figure this out. A little intimidating once you see all those lines of code pop up but I used to code my Audi, it's just been long time since I've done stuff like this. Kind of makes my HUD and Cravenspeed phone mount useless now. Logos popped up automatically for me.
I didn't do these steps: 23. Fire-Up ESYS (with ESYS launcher if you haven't used this originally to start ESYS) 24. Perform FDL coding as necessary on your HU to ensure that the following are set as below: KOMBI_CIC: set to kombi high EXTERNER_MOST: set to aktiv
Are they necessary? What does that coding do? I never use the factory nav only CarPlay
lots of the vehicle data shown in the kombi comes from the headunit, so it tells the headunit that MOST connection is present, and to utilize it, as well as the "Grade" of the KOMBI installed, so it knows the type of data that KOMBI can consume from its outbound messages. In my experience this was already set in my vehicle before coding the 6WB, btu assume for others it might not based on the stock Vehicle Order
I just wanted to mention that I installed the new 6WB cluster myself. I also did the coding myself.
I have done this in a Mini S F56. 2015 but with i-Step 1114. It is equipped with a HUD and a HU_NBT. The MOST cable was present in my case. So I don't have a HU_NBTEvo and I don't miss anything exciting. After physically installing the new cluster, coding was fairly simple. I haven't really run into any problems.
The only thing I failed to do is get the JCW logo in the screen. It seems that with ESYS you cannot do this and you need a program esysx, but that costs around 120 euros. I thought that was a bit much for a logo ..
Oh yes, for the people who use the Bimmercode app. After you have done this or had it done, the Bimmercode app will not find your new KOMBI, so no KOMBI will be displayed in your overview.
For example, if you have programmed the JCW Ref display in your HUD, you will not be able to do this again via the Bimmercode app. You have to do this via Esys, but I have not yet figured out how.
Well, if you have any questions, let me know.
The only thing not showing up in my new screen is the MINI logo you've got in this picture. When do you see that?
my guess is that the missing APIX connection is the culprit, if you added the MOST connection between the KOMBI and HU already. I don't have an up-to-date version of ISTA, so i can't pull the wiring diagram for you
Do you mean the blue connector behind the Kombi?
Why is the purpose off that cable? Because I thought someone installed there kombi on a non hud car. Gues he didn’t have the blue kabel either.
also see this info:
It’s the cable that goes to the HUD so iff you don’t have a hud you don’t have this cable.
Got my initial MINI animation sorted. I noticed earlier today that if I unlock the passenger door and then get in the car, the MINI animation started. So, I set unlock to unlock both doors - and, my only issue with the new digital speedo is fixed.
Worked as expected. I just needed to update my ESYS and psdzdata configuration. I was previously told that "Detect CAFD for SWE" function only worked with ESYS 3.27.1 and psdzdata 4.17.20. This is correct for that version of ESYS, however since we need the updated CAFDs and SWFLs for this GP3 KOMBI, I was successful in using ESYS 3.33.4 and psdzdata lite 4.24.31.
Steps for coding are as follows:
1. uninstall old kombi
2. install new kombi
3. Fire up ESYS 3.33.4 paired with psdzdata lite 4.24.31 in Expert --> Coding mode
4. Connect for F56 Project via Gateway connection
5. Read FA
6. Save FA
7. Edit FA
8. Change Zeitkriterium=0320
9. Edit SALAPA-Element
10. Add 6WB in appropriate alpha-numeric order to existing codes
11. Right-Click on FA at top of tree and click Calculate FP
12. Hit Save Icon
13. Hit Back Icon
14. Anser "Yes" to popup window asing to reload the file in module Coding
15. Right-Click FA and click Activate
16. Read ECU
17. Find "KOMBI" in ECU tree, left-click on it 1x
18. Hit Detect CAFD for SWE button
19. Click the CAFD under the ISTEP that matches the iSTEP of your vehicle
20. Back to ECU tree --> Left-Click on KOMBI ECU
21. Click CODE button, wait for completion and success message
22. Close ESYS
23. Fire-Up ESYS (with ESYS launcher if you haven't used this originally to start ESYS)
24. Perform FDL coding as necessary on your HU to ensure that the following are set as below:
KOMBI_CIC: set to kombi high
EXTERNER_MOST: set to aktiv
25. Enjoy your new GP3 Digital KOMBI
Everything is working as expected on my 2015 (11/2014 build date) F55 Cooper S 4-door Hardtop with NBT EVO retrofit. GP3 6WB KOMBI works perfectly fine on pre-LCI F55 models as this was a previous question in the thread above. Ignore the red triangle in the image ... i have hood open as the car is on a battery tender in the garage all the time as we don't drive it often.
Hi! Thanks for the informations. But for using Esys don't you need a token launcher? Or if you could give me a head on the configuration (launching) Esys at the first time, that would be great.
Hi! Thanks for the informations. But for using Esys don't you need a token launcher? Or if you could give me a head on the configuration (launching) Esys at the first time, that would be great.
You only need an EST token solution to perform FDL coding. To do everything through step 22, you can do with ESYS and PSdZDATA Lite alone. You likely won't have to perform the remaining steps depending on the hardware that you had in your car before retrofit.
Guys, i see different pictures of this digital cluster. Some seem to have a glossy screen, but almost all have a mat less sharp screen. Is this a sticker which can be removed?
Guys, i see different pictures of this digital cluster. Some seem to have a glossy screen, but almost all have a mat less sharp screen. Is this a sticker which can be removed?
i think the Mini E and GP hava shiny screens all the screens I did are S/JCW and they are Matt
Guys, i see different pictures of this digital cluster. Some seem to have a glossy screen, but almost all have a mat less sharp screen. Is this a sticker which can be removed?
I didn't realize that the tach was still "mechanical".
Hi Guys! Thanks for the coding info and everything. I followed all the step but I have a error when I open the door of the car: "Hood is open". I don't know where I did a mistake or what can I do to take off the error (it's every time I open the car)
Hi Guys! Thanks for the coding info and everything. I followed all the step but I have a error when I open the door of the car: "Hood is open". I don't know where I did a mistake or what can I do to take off the error (it's every time I open the car)
maybe you coded the whole car, all ecus with 0320?
1. uninstall old kombi 2. install new kombi 3. Fire up ESYS 3.33.4 paired with psdzdata lite 4.24.31 in Expert --> Coding mode 4. Connect for F56 Project via Gateway connection 5. Read FA 6. Save FA 7. Edit FA 8. Change Zeitkriterium=0320 9. Edit SALAPA-Element 10. Add 6WB in appropriate alpha-numeric order to existing codes 11. Right-Click on FA at top of tree and click Calculate FP 12. Hit Save Icon 13. Hit Back Icon 14. Anser "Yes" to popup window asing to reload the file in module Coding 15. Right-Click FA and click Activate 16. Read ECU 17. Find "KOMBI" in ECU tree, left-click on it 1x 18. Hit Detect CAFD for SWE button 19. Click the CAFD under the ISTEP that matches the iSTEP of your vehicle 20. Back to ECU tree --> Left-Click on KOMBI ECU 21. Click CODE button, wait for completion and success message 22. Close ESYS 23. Fire-Up ESYS (with ESYS launcher if you haven't used this originally to start ESYS) 24. Perform FDL coding as necessary on your HU to ensure that the following are set as below: KOMBI_CIC: set to kombi high EXTERNER_MOST: set to aktiv 25. Enjoy your new GP3 Digital KOMBI
hi after step 16 going to step 17 cant find anywhere at the tree the kombi
can anyone help ?
