F82 idrive display screen - Printable Version

F82 idrive display screen - Printable Version

+- Bimmer Scene - Latest BMW Coding / Retrofits / Maps (https://www.bimmerscene.com)
+-- Forum: Bimmer Scene Coding & Navigation (https://www.bimmerscene.com/forumdisplay.php?fid=1)
+--- Forum: BMW F / G Series Coding & Retrofits & Diagnostics (https://www.bimmerscene.com/forumdisplay.php?fid=3)
+--- Thread: F82 idrive display screen (/showthread.php?tid=706)

Pages: 1 2

RE: F82 idrive display screen - babyk - 09-18-2020

(09-17-2020, 08:56 PM)Mantuanas Wrote:
(09-12-2020, 06:09 AM)babyk Wrote:
(09-12-2020, 05:14 AM)Mantuanas Wrote:
(09-12-2020, 01:46 AM)Rob Wrote: @Mantuanas , Yes it will fit .

Apply these 2 parameters in esys

HU_NBT > 3000 HMI > DISPLAY_SIZE_RESOLUTION = 8.8_1280x480
HU_NBT > 3001 EXBOX > DISPLAY_VARIANTE = breites_display

thank you Rob

donor screen date is 17-02-2020
my hu entrynav is 2016-mid
will it really work because here is the new version I think,
or the screen may not show anything blank?

thank you

Regards M

Yes it will work, remember to code
CID_Touch = Aktiv
CID_Resolution = 1280 x 480
CID_Display_size = 8.8
DISPLAY_VARIANTE = breites_display

Hi,
I done coding on my HU_ENTRYNAV and screen still show NO SIGNAL
Maybe problem is APIX1-APIX2? Different voltage? And on my HU_ENTRYNAV can’t find apix coding option I think is only on NBT and NBT EVO
My HU_ENTRYNAV 2016 SCREEN 2020 EVO TOUCH
Maybe cable problem? Or voltage?

any ideas?

THANK YOU

REGARDS M

EntryNav might have APIX1

Touch screen is APIX2

So you might have issue with the communication

RE: F82 idrive display screen - Rob - 09-18-2020

touch screen Apix 2

RE: F82 idrive display screen - Mantuanas - 09-18-2020

(09-17-2020, 10:40 PM)Tuerkay Wrote: Correct me if i´m wrong but isn´t HU_Entrynav based on NBT (not evo)?
If that´s the case, the F82 touch Screen won´t work.
The Screen needs APIX2, MII interface and 12V while the HU_Entrynav supports APIX1, SPI and 9.5V

Thank you for your replay Tuerkay

APIX1 and APIX2 only different voltage and screen without MII interface will not work
so L7 screen support APIX1 MII yes?
But HU_ENTRYNAV not support MII and voltage is 9.5 or 12 or 7.5?

Thank you

Regards M

RE: F82 idrive display screen - Tuerkay - 09-18-2020

(09-18-2020, 06:46 AM)Mantuanas Wrote:
(09-17-2020, 10:40 PM)Tuerkay Wrote: Correct me if i´m wrong but isn´t HU_Entrynav based on NBT (not evo)?
If that´s the case, the F82 touch Screen won´t work.
The Screen needs APIX2, MII interface and 12V while the HU_Entrynav supports APIX1, SPI and 9.5V
Thank you for your replay Tuerkay

APIX1 and APIX2 only different voltage and screen without MII interface will not work
so L7 screen support APIX1 MII yes?
But HU_ENTRYNAV not support MII and voltage is 9.5 or 12 or 7.5?

Thank you

Regards M

There is more difference than just the Voltage.
APIX1 is an output-only interface for audio and video.
APIX2 is an multipurpose input-output interface needed for touchdisplays.

APIX2 can use SPI (non-touch/output only) and MII (touch/input output) while APIX1 can only handle SPI.

The BMW touchscreens need APIX2 and MII to work, even if you don´t use touchfunctionalty.

your HU_ENTRYNAV only supports APIX1, therefore only SPI for non-touchscreens.

i can´t tell you about the exact voltages. I just know that APIX2 (NBT Evo) uses 12V-14V while APIX1 (NBT not Evo) uses something lower. Found everything between 8V-9.5V.

so you need another screen. You can´t use the Evo screen on an NBT/ENTRYNAV system even with a voltage regulator.

RE: F82 idrive display screen - Mantuanas - 09-18-2020

NBT 12v
NEWER NBT 9.5v
NEW NBT 7.5

Thats what I find

So I need L7 8.8 APIX1 screen

Thank you again for your reply