Solved Entrynav 8.8" Display Retrofit

Solved ✔ Entrynav 8.8" Display Retrofit - Printable Version

+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: Solved ✔ Entrynav 8.8" Display Retrofit (/showthread.php?tid=72800)

Entrynav 8.8" Display Retrofit - SK223 - 18-12-2022

Hi there,

I have a friend who retrofitted a 8.8" display to replace his 6.5" in an F20 with entrynav. I helped him to FDL code the new screen as I've done in the past but for some reason the screen resolution and size is now correct, but there is a black box on the right side of the screen which is strange. It's as if its still on the 6.5" display but the UI is the correct scale as the right side is cut off.

Only thing I haven't tried yet is to update the HU, maybe that will resolve it?

Any suggestions on what to do to resolve it?

Thank you

RE: Entrynav 8.8" Display Retrofit - nonymou - 18-12-2022

With esys or something else?

I had the same issue
And it must be coded with esys

RE: Entrynav 8.8" Display Retrofit - CEBEP - 19-12-2022

DISPLAY_VARIANTE: breites_display [02]

RE: Entrynav 8.8" Display Retrofit - SK223 - 31-01-2023

(18-12-2022, 19:05 PM)nonymou Wrote: With esys or something else?

I had the same issue
And it must be coded with esys

Yeah it was with esys, will try again tonight with a newer version of esys

(19-12-2022, 04:39 AM)CEBEP Wrote: DISPLAY_VARIANTE: breites_display [02]

Pretty sure I did that already as I have coded it on another F30 and it was fine, but I will double check.

Thanks for the reply

RE: Entrynav 8.8" Display Retrofit - Maxx18771 - 31-01-2023

Try to search display_size_resolution and set to correct value.

Max

RE: Entrynav 8.8" Display Retrofit - SK223 - 06-02-2023

All good, solved it now

The car had a MMI box that was installed which I did not know about, and it caused an error while trying to code the headunit on esys. Removing the MMI box and coding it as normal worked. Checked and all of the coding values that I was changing and they were correct, but the MMI box was causing the coding not to actually be deployed onto the headunit.

Thank you all for your help