Bear with me folks. I am currently updating the ZGW proxy software I wrote to make it rather more suitable for general consumption before making it public, as this is required to code any ECU which the car expects to be on KCAN3.
I will let you know once this is available, with write up, diagrams, pictures, etc. It will still require a bit of computer savvy, but not to the point of modifying or compiling stuff!!
For VO coding, ECU coding & programming I tried ISTA but found E-Sys far more useful. Through painful trial and error (again!) I found that E-Sys 3.27.1 didn't work on my (2015) car. E-Sys 3.33.4 isn't supported by E-Sys Launcher (required for FDL coding & programming). E-Sys 3.30.1 worked well for me.
Resources:
- E-Sys Software, Launcher & psdzdata - Use launcher v2.8.2. It's free
- E-Sys v3.30.1 if you need find that neither v3.27.1 or v3.31 work for you, however do not use the linked Token Generator - It contains malware.
- VO (Vehicle Option) Coding Guide. Practice by adding 6NS to the Headunit if you don't already have it. That will give you "enhanced bluetooth" functionality such as SMS messages from your phone.
- If you want the older tools (you don't need them, however I find them simpler for some tasks such as reading fault codes) - Mike's Easy BMW Tools
Please remember that I don't have any inside information. All I have done is reverse engineer the protocols and messages involved using tools such as candump (which requires Linux, hence my use of a Raspberry Pi) and Wireshark.
Radj411
I haven't tried to get LED Headlights working but had a look at the wiring diagrams and to be honest it does look like a real challenge. I would
guess that the LIN bus connection is for the levelling. It might just work if you connect it directly to the LIN bus connection to the level dial next to the light switch.
KCAN2 certainly has the side light messages since that's where the trailer module (AHM) resides. This doesn't require VO coding (I fitted mine myself way before I touched coding), so would be my first try too.
Have you coded the LED headlights to the car in some way? They are unlikely to play without this at least.
Given that the halogen headlights are driven directly by the BDC, the actual main beam/side beam messages may not be on any other CAN bus.
The way I identified the messages sent by the ICAM was to put it on it's own dedicated CAN bus, relaying all messages between this and the actual car CAN bus network. This is straightforward with a Linux machine (e.g. Raspberry Pi) with two CAN modules. If you then record the dedicated CAN bus messages, you just see those generated by the ECU under test.
Eyalco101
From your screenshot I can see that the VO coding (add 3AG to HU_ENTRYNAV & PMA) is yet to be done - See the VO coding guide above. Then if you pull up that ECU map you will see TRSVC (which is equivalent to ICAM) shown but "not responding".
The rest of it I will come back once I have everything written up.