MicroHacker Forum

ronald0001 wrote: ↑27 Dec 2019, 17:35 but the pdc mod is extractet from the chinese cluster
so i think its only importand to have can signal on pam
and this is done with updating the pam

Excactly, but that was already known

If you know the offset of a image then you look for it in Main Firmware in order to find out what function uses that image. From that function, with the help of a disassembler you can find out which other function are related to this one and so you can build a map with the bytes you have to move from one Main FW to another. Next step is to find out how you can integrate this functions between the existing ones - make space for them or relocate them to other addresses and link with the existing ones - modify a JUMP instruction to go to you new main added function and then from it exit also with a JUMP back to the original function where is was originally "jumping".

DPF Icon is present in External Flash of FaceLift.. so if the function exist in Main FW then you only need to enable it and maybe decode what messages it needs over CAN in order to function properly.

China FW and EU FaceLift FW have almost the same images, less DPF and engine temp for China and less Parking sensor images for EU. Also on China the image with the car is a little bit smaller - maybe because of the Parking sensors images or other img that need to be present on screen at the same time.

Video IN function

tomy75 wrote: ↑28 Dec 2019, 19:30 Video IN function

Screenshot (27).png

I dont get that when I turn videoin on

Your "Video IN" is not the same with "Video IN for China market".
EU only have "Reverse Video Camera IN" which was hacked to work also when not in Reverse in order to be able to use it as a "Video IN" port.
On China market there is an extra Video Module that does the same thing as the "EU hack", but being an OEM one, it has full support - so Convers+ also shows this on its screen.

This Video IN is more a Satnav thing... maybe controllable by Convers+. I wonder what the CN Convers+ do with it? Enabling video view on FX+, NX+ or MCA+ needs some deeper investigation into the satnav firmware. You can force video on by simulating reverse gear, but this has drawbacks on the navigation. There must be a better way to do this... i could bet the developers had a service function to activate this on demand.

Well.. the "Audio Unit" knows that the car is in Reverse from a MM-CAN message that comes from Convers.
In China Convers, I think this function is still present, but Convers also listens to another module, the "Video IN module" that when it operates it sends it's own message on MM-CAN (most probably) and this way Convers knows that it should display that image instead of "Radio" or "CD" or "AUX/BT" and so on.
If the "Audio Unit" and "Video IN module" are in this "Video IN Mode" and the car is put in Reverse, then the "Video IN module" swaps its input from external video to "Reverse video IN" so you could see the Camera on the multimedia unit (NX / FX).

I wonder what module "video in" it is and where it could be obtained ...

In China of course

Go4IT wrote: ↑29 Dec 2019, 18:29 In China of course

Of course. I meant the module number ... I was looking for but I couldn't find ...