When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I think only the Chinese versions. Original screen is using different cabling and for sure many other different stuf inside like communication with other modules.
Updating to phase 4 is complicated at the moment (early March 2020) as the facility to do so via SDD has been suspended due to issues. It currently only allows phase 2.5 updates.
It can be done via Pathfinder, but it requires a bit of creative tweaking. I've only managed it the once while playing, and don't have as much experience with Pathfinder yet so I'm hesitant to share what I did just yet.
My advice today would be to wait for JLR to release the candidates back to SDD again. Their current ETA is "in March 2020" so it could happen tomorrow or it may be a few weeks. Once that has happened it will be easy again (just follow the instructions it gives you to to put the files onto a USB 3 drive and then download to the car).
If you are already 19A or later you will have CarPlay functionality but it may be disabled if the smart phone pack was never enabled. I have just noticed that I didn't put the CCF bit that configures what third party apps are available to you in my software post above, so I will need to hook back up to a car and grab that info.
hi, I’m a discovery sport owner. And came across your phenomenal thread. Well done. As someone had pointed on in here already the discovery owners all say not possible for retro fits. And as someone who’s done plenty (non JLR) I’m not having that.
My discovery sport has mid line UIP I’ve used CCF editor and changed it to high line. I have the 10.2 screen with CarPlay already but only have the 2 usb and 12v UIP I’ve changed it to the one with HDMI and uploaded the CCF. Along with video in motion (for passenger until I get my hands on DV screen and RSE) and disable start up warning.
yet my IMC hasn’t changed. I’ve no option in. Pathfinder to tell the IMC to learn CCF. Any ideas ?
I did successfully edit my CCF for adding LKA from LDW but that’s all I’ve attempted. I also have the 360 cameras. And looking to add auto park and wade sensing.
I found that I can use Android and CarPlay on my 8" without upgrading to a 10". It must be using Phase 2.5 with install the SmartPhone Pack using SDD. If you just want to use Android Auto, the LOW_LINE UIP is fine.(I changed the UIP for use CarPlay.) Of course, the CCF must be modified. I'll post more pictures of the behavior in the near future.
* Phases 3 and 4 are not possible. Only 2.5.
This is interesting. I wonder if anyone explored trying this approach to get the F-Type 8" to support CarPlay instead of only the 10", e.g. for systems that have ITCP such as MY2018. I didn't see any of these attempts, only some attempts to upgrade 8" to 10". Both are done with CCF updates though.
To be very honest, I am thinking about this too because the plastic bezel is still on waiting for the order to be shipped for 6 months already, from the main local dealer (and same would be from Germany, Netherlands, etc.).
I am also in difficulty to find a tool for programming. DA-Dongle shows up almost 100Eur for shipping to Romania the dongle, and on any email I've sent asking if there is an error or fi they can make a special shipping less costly, they never replied back so I start to have doubts on them if I will ever need any kind of support.
To be very honest, I am thinking about this too because the plastic bezel is still on waiting for the order to be shipped for 6 months already, from the main local dealer (and same would be from Germany, Netherlands, etc.).
I am also in difficulty to find a tool for programming. DA-Dongle shows up almost 100Eur for shipping to Romania the dongle, and on any email I've sent asking if there is an error or fi they can make a special shipping less costly, they never replied back so I start to have doubts on them if I will ever need any kind of support.
I was also considering VXDiag as an alternative or OpenPort Tactrix. I am not finding to much out of them on forums, people mentions vaguely using them on JLR vehicles with no real success stories for programming
I will actually check with Britcar if they have it in a way, in the past it was also missing for XJ, in my case.
On a random point - I see that the old "Park Assist" button gets disabled (and removed on the relevant new fascia) - and the overhead parking sensor button also becomes redundant.
So what is this "Power" button for on the new unit? (given the on/off & volume wheel directly under it?)
On a random point - I see that the old "Park Assist" button gets disabled (and removed on the relevant new fascia) - and the overhead parking sensor button also becomes redundant.
So what is this "Power" button for on the new unit? (given the on/off & volume wheel directly under it?)
The on/off/ volume is for media only - the power button circled is for the touch screen.
Thanks. I still miss the voice command my X-Type had for "Display Off"
Just debating on the 10" upgrade. I have no SDD, so would need someone to do it for me, but LR Retrofits are not local to me (and spendy!)
Thanks. I still miss the voice command my X-Type had for "Display Off"
Just debating on the 10" upgrade. I have no SDD, so would need someone to do it for me, but LR Retrofits are not local to me (and spendy!)
See first if you can get the plastic bezel first. All the other things after are easy to get and do.
I have been using the VXdiag VCX SE for about 3 years now on my XJ and F-Pace. So far I have not had any issues after programming many times. I even use the WiFi connection for minor programming so I don’t have to use a USB to connect to laptop. The unit gets all the power it needs from the OBD port.
Originally Posted by hulubei
I was also considering VXDiag as an alternative or OpenPort Tactrix. I am not finding to much out of them on forums, people mentions vaguely using them on JLR vehicles with no real success stories for programming
I will actually check with Britcar if they have it in a way, in the past it was also missing for XJ, in my case.
I mentioned in the first posts that the IPBM module provides the HMI for all the camera functionality rather than the IMC, so we need to update its software so it knows it needs the 10.2" UI and not the 8" one. It also needs to know how to interpret the various CAN messages that are sent out by the other modules, like the AC control panel, and so it understands the "activate camera" soft button on the new touch screen UI.
After various trial and error attempts I have come to the conclusion that you need an IPMB with an existing software version of 20 of later.
If you have the 360 camera system, the new part for the XJ is C2D55068. WERS is JJ32-14F026-AC.
For just the reverse camera, the new part is C2D55071. I am unsure of the WERS for that part.
That part is fitted to various other JLR vehicles, and most used ones are from RRs or E-Paces (the 360 variant is the only module fitted to the E-Pace).
All the 2016MY XJs I've worked on have been fitted with FW93-14F024-AE to AJ, and have been fitted with the 360 camera system.
Both LWB and SWB use the same hardware, but rear camera only and 360 camera system have different hardware.
The calibration software is different between LWB and SWB. This appears to be indicated by an major revision letter of A for SWB and B for LWB to the as-fitted WERS (the module however is the same). That is based on observation not qualified information.
New modules ship with the right strategry software but wrong calibbration data flashed so you need to reflash these on installation. Used modules will have whatever software was fitted to the donor vehicle. In either case it will need to be reflashed.
The process for doing this is simple, but there are some points to mention first:
1) I have bricked 4 IPMBs before I worked out the new/used module must have SW version 20 or later. It is printed on the label. It may be possible to update those on the bench, but not via CAN in the car which is my method.
2) The HW version has been 04.01.04.01 on all those I have used.
3) FW93-14F026-XX can't be reflashed to this software, so keep your current module as a backup or sell it.
4) I have had no success flashing the LWB calibration. I am unsure why. I have flashed the SWB calibration to a module fitted in a LWB car successfully, and the only difference appears to be a slight distortion to the rear or the side image where it stitches to the rear image (as you would expect). TBH the cameras are so poor anyway, and completely useless in the rain, so it hasn't been an issue for me.
Always attached a suitable external power supply to the car before attempting any software programming. A simple battery conditioner in supply mode may not be able to provide enough current. You need to maintain 12.6V minimum at all times. I really mean that - do not let the voltage drop during programming.
The programming process is shown in the steps below.
IMPORTANT NOTE - the part numbers shown are for the 360 camera system variant. I have no experience with the rear camera only variant so cannot compare the part numbers.
I am hoping that by providing original and new numbers for the 360 variant you may be able to infer the equivalent by interogating the part fitted to a rear only vehicle. (Use the parts summary icon on the main session page.)
1) Fit the new module
It is located behind the rear right passenger seat back. There is a cutout in the bulkhead lining which exposes it. Two 10mm nuts secure it to a bracket.
2) Start an SDD session and select Diagnostics.
3) Modify the as-built data for the target vehicle and change the fitted hardware WERS number.
The as-built data file is stored in:
C:\Program Files\Jlr\Common\Xml\IVSAsbuilt
It is downloaded during the new session process.
Copy and paste the file named YOURVINHERE_MODULE_RECORDSET.xml so you have a backup.
Open the file named YOURVINHERE_MODULE_RECORDSET.xml.
Search for IPMB and make a note of the fitted part number. That is the engineering number of the part fitted at the factory, not necessarily the same as the label on the module as they are installed pre-calibrated to save time.
It should be FW93-19H423-AX (SWB) or FW93-19H423-BX (LWB) - 360 variants. Rear camera only will have different versions here.
Change it to JW93-19H423-AC (SWB). Do not change to a BX revision as it will fail to flash and brick the module.
Save the file and set the read-only flag on it. This will prevent SDD from replacing it later in the process.
4) Start the configure the existing module candidate. SDD will detect the software versions are different and download the latest versions from the JLR servers.
5) You will see a screen that shows the current and new software versions. If happy with the changes save them to the vehicle.
This summary screen is the last chance you will get to check everything is ok before starting the reflash.
You should see the following (at the time of writing this, remember 360 variant):
HW part no FW93-14F015-AD
Assembly part no JW93-19H423-AE (this is the pn we set in the as-built data, but we set it to AC to force the software downloads)
Signal calibration part no JJ32-14F016-AA (this is the software that interprets and sends CAN messages, etc)
Strategy software part no JJ32-14F017-AD (the main software)
Calibration data part no JW93-14F022-AC (this is the calibration data for the XJ)
The calibration data part no must not be a B major revision or it fails. I am unsure why, but it has every time for me so if you follow these instructions at least you'll have a working module at the end.
That is basically it - the software download takes about an hour then everything is done. Afterwards everything should work as if it was a 2019MY car.
Guys, can you help me understand in the XML file, what info should I add? I have a FW93 module installed by factory. I sourced ad HY32 one.
Should I in fact add the JW93?
The last 2 letters which ones should be? AC? AE? AH (like the HY32 one ends in?).
I am also having issues with the interface maybe. It is OpenPort Tactrix 2.0 genuine. Was successfully used for Audio Premium upgrade, 10" screen and ACC retrofit. Now I want to finish with the IPMB and after about 15 -20 min I can see in the corner of the screen regarding SDDManager lots of disconnects and reconnects of the interface and the "Download" process fails. Not sure if it is because of interface itself or by having wrong PN configured in the XML file. Interesting this always starts after 15-20min and usually sorts out with laptop reboot. Checking cables and changing USB ports is not helping. Device Manager in Windows is not showing that the device is dis-reconnected .
I have tried the clone Mongoose which gave lots of errors in the dash.
Then I checked VCX SE Pro which as soon as it i was connecting the car to it was doing same "disconnected" "connected" all the time in SDD Manager. Anyone knows how to overcome this behavior?
you are not really adding anything. In the xml file you are just changing it from FW93 to JW93 and also the last two letters if needed. I had 2 entries in my XML file and changed both. That got my cameras up and running again.
the only issue I had is that after switching to the current IPMB, the video quality on my cameras are way worse than the original. If anyone know why I’d appreciate some info or maybe it was just a bad IPMB…
Originally Posted by hulubei
Guys, can you help me understand in the XML file, what info should I add? I have a FW93 module installed by factory. I sourced ad HY32 one.
Should I in fact add the JW93?
The last 2 letters which ones should be? AC? AE? AH (like the HY32 one ends in?).
I am also having issues with the interface maybe. It is OpenPort Tactrix 2.0 genuine. Was successfully used for Audio Premium upgrade, 10" screen and ACC retrofit. Now I want to finish with the IPMB and after about 15 -20 min I can see in the corner of the screen regarding SDDManager lots of disconnects and reconnects of the interface and the "Download" process fails. Not sure if it is because of interface itself or by having wrong PN configured in the XML file. Interesting this always starts after 15-20min and usually sorts out with laptop reboot. Checking cables and changing USB ports is not helping. Device Manager in Windows is not showing that the device is dis-reconnected .
I have tried the clone Mongoose which gave lots of errors in the dash.
Then I checked VCX SE Pro which as soon as it i was connecting the car to it was doing same "disconnected" "connected" all the time in SDD Manager. Anyone knows how to overcome this behavior?
And the last 2 letters would be the one from the new unit installed like on the label?
Fun fact is that between of the many attempts, once it finished in about 30min I can say with no errors, asking for the other things to do in the wizard to clear codes and so on. But still 2 codes remained and I started the coding again, it asked again same process which was failing in 10-15-20min because of dongle reconnects.
Don't worry too much about the label. In the XML file, the same line where you change the FW93 to JW93, change the last to digits to AC. Assuming you have the correct IPMB, that's all you have to do in the XML. After that its just a matter of downloading the software to the module.
Originally Posted by hulubei
And the last 2 letters would be the one from the new unit installed like on the label?
Fun fact is that between of the many attempts, once it finished in about 30min I can say with no errors, asking for the other things to do in the wizard to clear codes and so on. But still 2 codes remained and I started the coding again, it asked again same process which was failing in 10-15-20min because of dongle reconnects.
I am maybe unlucky. I have tried to change in both places from FW to JW and initially left all the rest as it was.
With an older OpenPort Tactrix is going with no disconnects and finishes in about 25-30min instead of 1 hour and 18 min as stated.
But I still get the 2 errors about central management something is not configured.
Then I changed the last 2 letters in AC too, both times. Redo process but still fails. Maybe time to revert to FW and put back the old unit?
@xdave , thanks to your great help, I was able to get this job done successfully. And @Cambo helped replace UIP for use CarPlay, is also very grateful. It's been 3 years since I bought the XJL. Display / CarPlay work has been the most satisfying.
1. PAM
My PAM was GX63-15C859-DL. I reprogrammed it, but it failed and it made to be brick. My choice is "GX63-15C859-DM". I have purchased 2 "-DM". I tried to reprogram one of them, but it also turned a brick. If you're not confident, just buy "-DM" and just replace it(do not reprogramming). There is no problem at all to use.
2. IPMB
Old IPMB was "FW93-14F026-AJ". If you can not change the camera mode without replacing the IPMB. I bought "HY32-14F026-AM" on eBay and replaced it. Even after reprogramming, my car didn't recognize this module. Unlike PAM, no problem occurred during the reprogramming process. I bought "JJ32-14F026-AD", again and changed the calibration software to "-BD". It is perfect!
3. CarPlay
My Jag had LOW_LINE UIP. If you force the "Smart Phone Pack" to be activated, only Android Auto will be available and causes many problems. I replaced it to HIGH_LINE UIP, and connected it used HSD. CarPlay works perfectly, now!!
Thank you everyone!
@gloriashield , having exactly same module as yours from eBay. Have you managed to understand and give advices or maybe the ending in AM is not going to work? @xdave or @Cambo , any clues. Is this module maybe not ever going to work?
