Hello all,
UPDATE2: If your seller does not correct its mcu firmware you can find what I did for my car here : https://github.com/ulysse31/CID_Faker Project is open-source ^^ WARNING : I just installed it, it works, but no idea of what it will give in the long term. I AM NOT RESPONSIBLE FOR ANY DAMAGE THIS WOULD CAUSE TO YOUR CAR, YOURSELF OR ANY OTHER PERSON. BEST SOLUTION WOULD BE A MCU UPGRADE FROM MANUFACTURERS.
UPDATE: Problem was identified, and we have a "first patch solution" that allows us to wait from a potential MCU firmware update to correct this...
The Problem :
BMW with "flap screen" (motorized screens), sends there own status messages on the can bus network, when replacing the screen with an Android HU, the MCU of the Android HU does not send those message IDs to simulate the original screen presence, and if the CCC controller does not see them, it does not interpret the messages from the idrive knob.
The Solution :
Updating the MCU firmware, that will send those messages on the network, to indicate the presence of a screen. This needs that the chinese manufacturer works on this issue, and modify there firmware (mcu firmware source code is not released anywhere)
The Possible Patch:
Build an little device that will "simulate" the genuine screen presence on the car CAN bus network, by sending the correct ID messages, with the correct data values and the correct timing => a first POC works with a arduino board and a MCP2515 module ! ^^ Next step is to find the best clean message sending sequence, to avoid any potential harm to the car.
Original post :
I tried to install a new Android Head Unit on my car today, Everything was doing great, once installed, Android booted up, my idrive wheel was working on Android with no problem.
Then, I tried to go to the BMW original screen, by using the wrapper menu "Car Info" (ID6 interface), it switched correctly, but my idrive wheel simply does not work once in the original menu (??).
If I press the "menu" button on the idrive for 3 secs (or tap the touch screen), it goes back to the android side, and I then use without problem the idrive again on the Android side.
I tried some tweaks going on the "Factory Setup" menu :
- Changing from idrive_B/idrive_A => originally idrive_B, if i put idrive_A, the idrive wheel stops working on both android and original bmw menu.
- Changing car type : my car is a 2005 BMW e87 with CCC, it had genuinely an old motorised flip/flap screen, and the android head unit seller preset the unit to type [18] "CCC e60 6.5 screen (2008)", tried the type [2], which is "CCC e60 6.5 screen", but it does not change anything => the idrive wheel still works on android side only with mode idrive_B, and not at all with mode idrive_A.
I really don't get why it works on android side, but not in the BMW original menu.
If someone has some ideas, I would really appreciate.
Thanks a lot for the help.
Cheers all,
--
Ulysse31
update
Hello all,
Adding steps that I've made and what I've found :
- I have checked with a multimeter all the cables on the main Y connector, they are all good : CANBUS signals (L and H) are redirected to the screen, and then, the secondary CANBUS link of the screen is correctly connected to the CCC car controller.
- when in the original BMW menu, rotating the knob or validating does not do anything, BUT, if I go back to the android menu, keys were received and interpreted by the android side. So, for some reason, the android does not resend CANBUS signal on its secondary CANBUS to the CCC as it should, and interpret it for himself ...
- I have contacted the seller, he first as me for a video, and then ask me to do a MCU update, after update (which "seems" to have worked since it detected the update and launched the update process, then rebooted) problem still there, same as before.
- I have tried to : update from another usb port, modify parameters on the factory setup and reboot => nothing changes ...
I'm going clueless, if someone has an idea, I would be really thankful.
Cheers all,
--
ulysse31_revient said:
Hello all,
I tried to install a new Android Head Unit on my car today, Everything was doing great, once installed, Android booted up, my idrive wheel was working on Android with no problem.
Then, I tried to go to the BMW original screen, by using the wrapper menu "Car Info" (ID6 interface), it switched correctly, but my idrive wheel simply does not work once in the original menu (??).
If I press the "menu" button on the idrive for 3 secs (or tap the touch screen), it goes back to the android side, and I then use without problem the idrive again on the Android side.
I tried some tweaks going on the "Factory Setup" menu :
- Changing from idrive_B/idrive_A => originally idrive_B, if i put idrive_A, the idrive wheel stops working on both android and original bmw menu.
- Changing car type : my car is a 2005 BMW e87 with CCC, it had genuinely an old motorised flip/flap screen, and the android head unit seller preset the unit to type [18] "CCC e60 6.5 screen (2008)", tried the type [2], which is "CCC e60 6.5 screen", but it does not change anything => the idrive wheel still works on android side only with mode idrive_B, and not at all with mode idrive_A.
I really don't get why it works on android side, but not in the BMW original menu.
If someone has some ideas, I would really appreciate.
Thanks a lot for the help.
Cheers all,
--
Victor
Click to expand...
Click to collapse
update 2
Hello all,
After searching on the internet, I've found that it seems to be a problem with PX6 android 8.1 devices and CCC idrive, cannot post link for now ... the http link is:
f30.bimmerpost.com/forums/showthread.php?p=24747828
Reading this thread (and other threads about it on the same site), it seems that several persons with CCC idrive, are having trouble with the PX6 devices with android 8.1 on it.
It seems that the device, with android 8.1, does not resend correctly the canbus signal to the CCC car controller, which leads to the impossibility to navigate on the original BMW menu.
Does someone knows where can I find android 8.1 install/update images for this type of devices ? (AVIN 10.25 PX6 rk3399 2G RAM 32G ROM clones like JSTMAX, COIKA, JRNAV, etc ...)
Thanks a lot for reading.
Regards,
--
Victor
update 3
Hello,
Still no solution for my problem :
- seller sent me a second mcuupdate.bin => that didn't change a thing
- I have not found any suitable update on the net for this unit (10.25" android 8.1 PX6 CCC idrive HU).
I'm really getting desperate, if someone has any idea or trick to try (just to give me some hope) ... please don't hesitate to post and share.
Thanks a lot.
Regards,
ulysse31_revient said:
Hello,
Still no solution for my problem :
- seller sent me a second mcuupdate.bin => that didn't change a thing
- I have not found any suitable update on the net for this unit (10.25" android 8.1 PX6 CCC idrive HU).
I'm really getting desperate, if someone has any idea or trick to try (just to give me some hope) ... please don't hesitate to post and share.
Thanks a lot.
Regards,
Click to expand...
Click to collapse
Hi,
I have the same problem with my unit. android 8.1 PX6 E87 2007 with original folding ccc screen. I read your remark about the canbus signal not being redirected correctly but what i do not understand (maybe i am missing something) is that when i connect my original screen together with the android unit it seems to work (the OEM menu on the original screen of course). The only difference is that the cable from the radio unit is not going into the android system but into the orignal screen. From that it looks like it has something to do with the lvds cable they provided. I had a closer look and one thing that seems odd is that the original has a metal harness and the cable that comes with the android HU doesn't. BUT on the android HU connector for the lvds cable there is a metal clip that, i would expect, should connect to something... could i simply be that the cable needs a metal harness / ground?
UPDATE: Tried the ground but that doesn't work.
Here is a video where can see how the two screens together do work: (search on youtube for: "Idrive not working in android 10.25 car info" my username is pietklazen100) (sorry as a new member i am not allowed to post links yet)
ErikE87 said:
Hi,
I have the same problem with my unit. android 8.1 PX6 E87 2007 with original folding ccc screen. I read your remark about the canbus signal not being redirected correctly but what i do not understand (maybe i am missing something) is that when i connect my original screen together with the android unit it seems to work (the OEM menu on the original screen of course). The only difference is that the cable from the radio unit is not going into the android system but into the orignal screen. From that it looks like it has something to do with the lvds cable they provided. I had a closer look and one thing that seems odd is that the original has a metal harness and the cable that comes with the android HU doesn't. BUT on the android HU connector for the lvds cable there is a metal clip that, i would expect, should connect to something... could i simply be that the cable needs a metal harness / ground?
UPDATE: Tried the ground but that doesn't work.
Here is a video where can see how the two screens together do work: (search on youtube for: "Idrive not working in android 10.25 car info" my username is pietklazen100) (sorry as a new member i am not allowed to post links yet)
Click to expand...
Click to collapse
I need also to dig on your grounding in lvds, maybe if screen motor (or entire screen) is not detected, it does not read the incoming message from idrive ? I will dig on this possibility once I have check the one I'm onto right now :
I have found some other stuffs about the possibility of the can bus signal not being send out correctly :
- on another forum, a user posted the photo of its MCU on his head unit, when I saw the photo, something jump to my eyes (since I just looked to mine this morning), here is the photo he posted :
And here is mine :
It seems mine DOES NOT have the chips on U7 and U8 ...
The MCU used is a STM32F105RB, this MCU as 2 embedded CAN controllers, a CAN controller sends signal to the can bus via RX and TX pins, but THEY DO NOT SEND SIGNAL DIRECTLY, a can controller is generally used in combination with a CAN transceiver, on the photo the guy posted (thanks dice66), we can see those 2 CAN transceivers and read on them NXP TJXXXX2, we cannot read entirely because chips are usually scrapped by chinese manufacturer ... BUT ! digging with google I came to the assumption that it may certainly be a NXP TJA1042 ^^'
Digging more on internet about can bus protocol, made me read that a CAN controller MAY send/receive signals directly without transceivers, but they will be exposed to high noise, and will see their signal range reduced to a single meter max.
I suppose that without this chip, signal strength can be severely reduced, and thus signal from idrive might be received by android HU, but not correctly resend because of the lack of these chips ?
If the original screen is connected, maybe more strength for the MCU to resend since video signal is not being managed by the android HU ?
So I made the following assumption : their are lot of different 10.25 HU unit clones, would some of them try to reduce cost by removing those kind of chips ?
Have some people checked inside their HU and see if they have those chips ?
(HINT: the MCU is on the back of the motherboard).
Regards,
--
Ulysse31
ErikE87 said:
Hi,
I have the same problem with my unit. android 8.1 PX6 E87 2007 with original folding ccc screen. I read your remark about the canbus signal not being redirected correctly but what i do not understand (maybe i am missing something) is that when i connect my original screen together with the android unit it seems to work (the OEM menu on the original screen of course). The only difference is that the cable from the radio unit is not going into the android system but into the orignal screen. From that it looks like it has something to do with the lvds cable they provided. I had a closer look and one thing that seems odd is that the original has a metal harness and the cable that comes with the android HU doesn't. BUT on the android HU connector for the lvds cable there is a metal clip that, i would expect, should connect to something... could i simply be that the cable needs a metal harness / ground?
UPDATE: Tried the ground but that doesn't work.
Here is a video where can see how the two screens together do work: (search on youtube for: "Idrive not working in android 10.25 car info" my username is pietklazen100) (sorry as a new member i am not allowed to post links yet)
Click to expand...
Click to collapse
ulysse31_revient said:
I need also to dig on your grounding in lvds, maybe if screen motor (or entire screen) is not detected, it does not read the incoming message from idrive ? I will dig on this possibility once I have check the one I'm onto right now :
I have found some other stuffs about the possibility of the can bus signal not being send out correctly :
- on another forum, a user posted the photo of its MCU on his head unit, when I saw the photo, something jump to my eyes (since I just looked to mine this morning), here is the photo he posted :
And here is mine :
It seems mine DOES NOT have the chips on U7 and U8 ...
The MCU used is a STM32F105RB, this MCU as 2 embedded CAN controllers, a CAN controller sends signal to the can bus via RX and TX pins, but THEY DO NOT SEND SIGNAL DIRECTLY, a can controller is generally used in combination with a CAN transceiver, on the photo the guy posted (thanks dice66), we can see those 2 CAN transceivers and read on them NXP TJXXXX2, we cannot read entirely because chips are usually scrapped by chinese manufacturer ... BUT ! digging with google I came to the assumption that it may certainly be a NXP TJA1042 ^^'
Digging more on internet about can bus protocol, made me read that a CAN controller MAY send/receive signals directly without transceivers, but they will be exposed to high noise, and will see their signal range reduced to a single meter max.
I suppose that without this chip, signal strength can be severely reduced, and thus signal from idrive might be received by android HU, but not correctly resend because of the lack of these chips ?
If the original screen is connected, maybe more strength for the MCU to resend since video signal is not being managed by the android HU ?
So I made the following assumption : their are lot of different 10.25 HU unit clones, would some of them try to reduce cost by removing those kind of chips ?
Have some people checked inside their HU and see if they have those chips ?
(HINT: the MCU is on the back of the motherboard).
Regards,
--
Ulysse31
Click to expand...
Click to collapse
Thanks for your explanation! Makes sense! I can confirm that having the screen motor attached does not make a difference. When i connect the original screen and change only the lvds cable (so screen motor cable is connected) it still doesn't work. Could it be that the screen actually has logic in it? So the can signal is send over the lvds cable?? and the screen interprets it? Seems weird to be honest... I tried to open my original screen to measure the original lvds cable and the android HU one but i don't know how to open it and am afraid to brake it since it is my only way to work on the original interface at the moment.
ErikE87 said:
Thanks for your explanation! Makes sense! I can confirm that having the screen motor attached does not make a difference. When i connect the original screen and change only the lvds cable (so screen motor cable is connected) it still doesn't work. Could it be that the screen actually has logic in it? So the can signal is send over the lvds cable?? and the screen interprets it? Seems weird to be honest... I tried to open my original screen to measure the original lvds cable and the android HU one but i don't know how to open it and am afraid to brake it since it is my only way to work on the original interface at the moment.
Click to expand...
Click to collapse
Hi,
From what you explain here, I'm thinking several tests that could be done :
- Checking that motor is really NOT needed : leave the original screen connected (no parts from android HU), but motor disconnected, try with the original screen open if it shows menu, and if you can interact with the idrive.
- Checking if outer metal cable as an interest : for this point 2 sequential tests :
* with the original screen connected and key car in (BMW menu on screen), mesure with a multimeter in volt if their is a difference between the outer shell of the cable (take one test head of multimeter on the back of the CCC controller for example), and the ground of the vehicule (the black wires on the big power connector of the CCC controller on its back) if you see a voltage (check first range 0-20V, then mV if 0 !). if you see a voltage, then it means that it is used for sending a signal. if not, well, it means outer shell is useless.
* if their was a result on last test, connect the new android HU screen completely (Y connector, screen cable, etc ...), and a 1 meter wire, connect one side of the wire to the outer shell of the screen connector on the back of the CCC controller and the other side to the other side of the android lvds screen connector (from my remembering, there is a metal part in its outer shell).
Test those and keep me in touch.
UPDATE: TIP for the original screen : when powered off (motor disconnected), you can open or close the original screen without forcing (do not forget to remove the screen BEHIND the screen when screen is opened, because those screw may block the opening or closing is not taken out).
--
Ulysse31
ulysse31_revient said:
Hi,
From what you explain here, I'm thinking several tests that could be done :
- Checking that motor is really NOT needed : leave the original screen connected (no parts from android HU), but motor disconnected, try with the original screen open if it shows menu, and if you can interact with the idrive.
Tried it: The original screen gets the power from the motor cable so there is no way to see if the original screen works but i tried using the idrive contol and were able to switch to aux.. so it seems it is not needed.
- Checking if outer metal cable as an interest : for this point 2 sequential tests :
* with the original screen connected and key car in (BMW menu on screen), mesure with a multimeter in volt if their is a difference between the outer shell of the cable (take one test head of multimeter on the back of the CCC controller for example), and the ground of the vehicule (the black wires on the big power connector of the CCC controller on its back) if you see a voltage (check first range 0-20V, then mV if 0 !). if you see a voltage, then it means that it is used for sending a signal. if not, well, it means outer shell is useless.
* if their was a result on last test, connect the new android HU screen completely (Y connector, screen cable, etc ...), and a 1 meter wire, connect one side of the wire to the outer shell of the screen connector on the back of the CCC controller and the other side to the other side of the android lvds screen connector (from my remembering, there is a metal part in its outer shell).
Did not test this exactly but soldered the outer metal part of the ccc lvds connector (female on the back of the radio) to the metal part of the lvds connector of the android HU. No difference, but this could potentially also means the metal part on the connector of the android HU isn't connected to anything,,
Test those and keep me in touch.
UPDATE: TIP for the original screen : when powered off (motor disconnected), you can open or close the original screen without forcing (do not forget to remove the screen BEHIND the screen when screen is opened, because those screw may block the opening or closing is not taken out).
--
Ulysse31
Click to expand...
Click to collapse
Hi! In red my findings.. it is weird. It doesn't seem the outer metal part does anything and the motor cable isn't needed. After the tests i found this online: https://www.newtis.info/tisv2/a/en/e60-m5-lim/repair-manuals/84-communication-systems/1puXMxl
It looks like besides the lvds cable another cable comes in with k-can signal? That is connected to the idrive control (nr 35 on the diagram). The only cable that is connected to to the CID besides the lvds is the motor cable... Will try my test again to validate.
Are we sure the lvds cable only provides the signal for the screen and not also some canbus signal??
ErikE87 said:
Hi! In red my findings.. it is weird. It doesn't seem the outer metal part does anything and the motor cable isn't needed. After the tests i found this online: https://www.newtis.info/tisv2/a/en/e60-m5-lim/repair-manuals/84-communication-systems/1puXMxl
It looks like besides the lvds cable another cable comes in with k-can signal? That is connected to the idrive control (nr 35 on the diagram). The only cable that is connected to to the CID besides the lvds is the motor cable... Will try my test again to validate.
Are we sure the lvds cable only provides the signal for the screen and not also some canbus signal??
Click to expand...
Click to collapse
Hi again,
The only thing I am sure, is that can bus is, by definition, only one pair of cable (composed of wire CAN High and wire CAN Low), and all equipments are linked to this bus, the goal of can bus is to reduce cabling, so I doubt that the screen would send a can bus signal (which, would need 2 pins/wires), in addition to the can bus that is already connected to the CCC controller.
One other thing, have you noticed that when you reconnect the screen motor, your can "ear" can bus devices getting initialized (a little noise of different equipment, very particular ^^' i don't know how to describe it by writting ^^') (UPDATE: maybe the JBE initialisation ?) so yes, I think that the original screen (CID) is connected to can bus, but I would suppose by the motor wires (6pin/wire flat cable/connector).
But has you say that you can "navigate" the menu and change audio input while motor cable is disconnected, I suppose that even if it has can connection, it is not mandatory for menu interaction with idrive.
Anyways, this schema is really interresting, thanks for sharing it ^^.
--
Ulysse31
Ok retried the test where i had the lvds and motor power cable connected to the original screen and disconnected the lvds cable to see if i can still control the ccc system on the (darked out) original screen. Spoilers: really interesting findings, here it goes:
1. When i have the lvds and motor power cable connected to the original unit everything works as in this video: https://www.youtube.com/watch?v=E7b7ipcs6Hk
2. when i disconnect the lvds cable but leave the motor power cable connected at first i could not control the ccc system with idrive controller anymore.
3. BUT BUT BUT, when i connected the lvds cable and quickly tried the idrive control i could switch from aux to FM (remembered what to do since the screen was black) a few seconds later i was not able to control it anymore!
4. to verify these results at last i disconnected the lvds cable (original) and really quickly connected the android HU lvds cable and quess what! I was able to control the original idrive menu on the android HU for only 1 second (one twist on the idrive controller).
I don't know that much about electronics but to me this really looks like a ground thing... for a few seconds it holds it or something and than loses it and you cannot control the original screen with the idrive controller anymore... Could it than just be that the ground (metal outer part) of the lvds connector on the radio unit needs to be connected to a ground or something? Is the motor cable acting as a ground??
I think we are on to something but don't know exactly how to proceed now.. any ideas?
ErikE87 said:
Ok retried the test where i had the lvds and motor power cable connected to the original screen and disconnected the lvds cable to see if i can still control the ccc system on the (darked out) original screen. Spoilers: really interesting findings, here it goes:
1. When i have the lvds and motor power cable connected to the original unit everything works as in this video: https://www.youtube.com/watch?v=E7b7ipcs6Hk
2. when i disconnect the lvds cable but leave the motor power cable connected at first i could not control the ccc system with idrive controller anymore.
3. BUT BUT BUT, when i connected the lvds cable and quickly tried the idrive control i could switch from aux to FM (remembered what to do since the screen was black) a few seconds later i was not able to control it anymore!
4. to verify these results at last i disconnected the lvds cable (original) and really quickly connected the android HU lvds cable and quess what! I was able to control the original idrive menu on the android HU for only 1 second (one twist on the idrive controller).
I don't know that much about electronics but to me this really looks like a ground thing... for a few seconds it holds it or something and than loses it and you cannot control the original screen with the idrive controller anymore... Could it than just be that the ground (metal outer part) of the lvds connector on the radio unit needs to be connected to a ground or something? Is the motor cable acting as a ground??
I think we are on to something but don't know exactly how to proceed now.. any ideas?
Click to expand...
Click to collapse
Sorry if you already tried this but :
- if you connect a wire to the outer of the lvds connector on the CCC (it is metallic), and that you connect the other side of the wire to the outer of the lvds connector of the android (which is plastic, but one side has a metallic shield), what does it gives ?
ulysse31_revient said:
Sorry if you already tried this but :
- if you connect a wire to the outer of the lvds connector on the CCC (it is metallic), and that you connect the other side of the wire to the outer of the lvds connector of the android (which is plastic, but one side has a metallic shield), what does it gives ?
Click to expand...
Click to collapse
Hi! Already tried this and didn't work. Did some more tests and it is very interesting. Besides my previous tests i did the following now:
1. start with original screen (motor power cable and lvds) connected. --> everything works on the original screen (as in the video i posted earlier.
2. When i disconnect the motor power cable it still works: https://www.youtube.com/watch?v=MtYQFO_f6n0
3. But when i then pull out the lvds cable and reconnect it or pull out the key (ccc off and android HU off) and then start again the idrive control doesn't work.
So after all these tests we have the following results:
1. It seems that the lvds cable needs te be connected to be able to let it work (or really shortly after disconnecting it, it works for a couple of seconds)
2. when the motor cable is disconnect while the ccc system works it keeps working
3. when the motor cable is disconnected when starting or when you disconnect the lvds cable and reconnect it again the ccc system doesn't work anymore.
No idea yet what this means but it seems somehow that the motor cable needs to be connected when the power is put on the system. Just thinking out loud: could it be that the car (based on the motor power cable) detects that the screen is open (what it does during startup) and that the metal outer part is needed on the lvds cable? This would explain the above if i'm not making a mistake.
My next test tomorrow will be to solder the outer metal part of the radio to the android HU metal part of the lvds connector and starting with the motor power cable so the screen opens during startup. If this works i think it will prove the above hypothesis.
If i am missing something or making a mistake please do tell!
ErikE87 said:
Hi! Already tried this and didn't work. Did some more tests and it is very interesting. Besides my previous tests i did the following now:
1. start with original screen (motor power cable and lvds) connected. --> everything works on the original screen (as in the video i posted earlier.
2. When i disconnect the motor power cable it still works: https://www.youtube.com/watch?v=MtYQFO_f6n0
3. But when i then pull out the lvds cable and reconnect it or pull out the key (ccc off and android HU off) and then start again the idrive control doesn't work.
So after all these tests we have the following results:
1. It seems that the lvds cable needs te be connected to be able to let it work (or really shortly after disconnecting it, it works for a couple of seconds)
2. when the motor cable is disconnect while the ccc system works it keeps working
3. when the motor cable is disconnected when starting or when you disconnect the lvds cable and reconnect it again the ccc system doesn't work anymore.
No idea yet what this means but it seems somehow that the motor cable needs to be connected when the power is put on the system. Just thinking out loud: could it be that the car (based on the motor power cable) detects that the screen is open (what it does during startup) and that the metal outer part is needed on the lvds cable? This would explain the above if i'm not making a mistake.
My next test tomorrow will be to solder the outer metal part of the radio to the android HU metal part of the lvds connector and starting with the motor power cable so the screen opens during startup. If this works i think it will prove the above hypothesis.
If i am missing something or making a mistake please do tell!
Click to expand...
Click to collapse
Crossing fingers ^^
Keep me in touch
Thanks a lot for your share
ulysse31_revient said:
Crossing fingers ^^
Keep me in touch
Thanks a lot for your share
Click to expand...
Click to collapse
Ok was too curious. Tried it but doesn't work....
The original menu definitely doesn't work when the screen is closed:
It opens the screen first before you can go one. Disconnecting the motor power cable after it is closed results in no control over the original unit anymore. So it really looks like it knows from the motor power cable that it is open or not or a combination of the lvds and motor power cable.
Little bit out of ideas to test again.
@ulysse31_revient: you have an open unit right? Could you see where the metal part of the lvds connector on the android unit goes to?
Any other ideas to test?
ErikE87 said:
Ok was too curious. Tried it but doesn't work....
The original menu definitely doesn't work when the screen is closed:
It opens the screen first before you can go one. Disconnecting the motor power cable after it is closed results in no control over the original unit anymore. So it really looks like it knows from the motor power cable that it is open or not or a combination of the lvds and motor power cable.
Little bit out of ideas to test again.
@ulysse31_revient: you have an open unit right? Could you see where the metal part of the lvds connector on the android unit goes to?
Any other ideas to test?
Click to expand...
Click to collapse
On the android HU, the lvds connector cable is one molded plastic cable, the plastic cable goes inside then to a flat connector on the motherboard, I need to re-open it and test with a multimeter to know which cable on the flat connector is the outside metallic part. Give me some time: this type of activity is not WAF (Wife Acceptance Factor) compatible ^^'
ulysse31_revient said:
On the android HU, the lvds connector cable is one molded plastic cable, the plastic cable goes inside then to a flat connector on the motherboard, I need to re-open it and test with a multimeter to know which cable on the flat connector is the outside metallic part. Give me some time: this type of activity is not WAF (Wife Acceptance Factor) compatible ^^'
Click to expand...
Click to collapse
Hahaha can relate ?
I found a interesting video on YouTube where someone also says the car thinks the screen is closed and that you need to code your car. What do you think of this? Do you have coding experience?
ErikE87 said:
Hahaha can relate
I found a interesting video on YouTube where someone also says the car thinks the screen is closed and that you need to code your car. What do you think of this? Do you have coding experience?
Click to expand...
Click to collapse
Hmmm, I would say ... "maybe" ... but if true, leaving the motor connected and the android screen connected to lvds should work: unless it is a problem of "bad lvds cable + motor opening detection", and if true, when you test to solder the cable tomorrow, also try it with and without old screen motor connected ^^' ... just in case.
For the lvds cable on the android side, I have tested with a multimeter : it is cabled to the 5th cable (black rugged) on the flat connector to the motherboard (12 pin flat connector ... yes 12 ... don't ask me why ...)
I say black rugged, because there is another black wire on the connector, but thin like the others, this one (the fifth) is ticker and rough.
Cheers,
--
Ulysse31
ulysse31_revient said:
Hmmm, I would say ... "maybe" ... but if true, leaving the motor connected and the android screen connected to lvds should work: unless it is a problem of "bad lvds cable + motor opening detection", and if true, when you test to solder the cable tomorrow, also try it with and without old screen motor connected ^^' ... just in case.
For the lvds cable on the android side, I have tested with a multimeter : it is cabled to the 5th cable (black rugged) on the flat connector to the motherboard (12 pin flat connector ... yes 12 ... don't ask me why ...)
I say black rugged, because there is another black wire on the connector, but thin like the others, this one (the fifth) is ticker and rough.
Cheers,
--
Ulysse31
Click to expand...
Click to collapse
Think you missed my comment but already tried the soldering to the metal outer part with motor connected. Both with motor and without motor attached it does not work. But because the original system also stops working after I disconnect the lvds cable might it be that the car also thinks the screen is off when the lvds connector is disconnected? Seems weird and some over engineering of the BMW team way back in 2006 but you never know. I cannot explain why the system doesn't work without the lvds cable otherwise.
Do you have experience with coding your car or know anyone who can?
ErikE87 said:
Think you missed my comment but already tried the soldering to the metal outer part with motor connected. Both with motor and without motor attached it does not work. But because the original system also stops working after I disconnect the lvds cable might it be that the car also thinks the screen is off when the lvds connector is disconnected? Seems weird and some over engineering of the BMW team way back in 2006 but you never know. I cannot explain why the system doesn't work without the lvds cable otherwise.
Do you have experience with coding your car or know anyone who can?
Click to expand...
Click to collapse
When you tried with the cable soldered, have you check the conductivity of it ? What I found strange is that if the outer shell was not important, why would the manufacturer of the android HU connect that to the motherboard ?
I've read about using NCS Expert with a ODB/K-CAN usb cable, from what I read, you need to download a set of files corresponding to your vehicule, the set contains the "configuration" (programming) of each modules on your car (so the set must match your car year and model, of course), once you have the files, you import them on NCSExpert and then you can upload them to the selected module, before uploading you need to set some variables like the VIN code of your car to be uploaded to the module : if a module does not have the same VIN code than the rest of the car, it may stop working. I suppose that in the variables, their is one for the flap screen like indicated on the youtube video comment.
Finding someone who can use NCSExpert would be simple : just find a third party garage (not bmw), that can repair BMW, they have people for doing those kind of things, since NCSExpert is used for updating vehicule modules, and to replace failed modules.