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.
Not sure if this has been done before, or if anyone knows whether it's possible, but I have a touchscreen, infotainment control module, and integrated audio module.
I want to get these working off of the car, so have wired them all up, created the MOST link between them all, and then replayed the can messages that the car sends out when starting up.
I can get the ICM to power on, and begin the MOST communication, then screen turns on to the jaguar logo, however after this the screen turns back off
I'm kind of wondering whether I need every module that's configured in the CCF to be present on the loop, or whether it will work without these?
I can't confirm the most loop is working correct, as when it's not it flashes and it is on a solid steady light.
Any info would be great, even if it's just that people have had systems still work with a module looped out.
Yes - you can definitely get it to work with one of the modules looped out. That's how folks on here have tested Eg if BT module is faulty. Use a fiber loop to bypass it and it should work fine without it.
But maybe there are one or two specific ones that are needed?
Why do you want touchscreen to work out of the car?
Not in your league Rhys but when I look at the MOST loop on my 07 XK wiring diagram, the front stack includes touchscreen, infotainment control module, integrated audio module AND the amplifier and the test connector. I've looped out the trunk stack without issue. All have been with parts in the car though.
So maybe the Canbus is looking for the Amp? Even so, I would think you could loop out the trunk stack in your car, then loop out the amp in your car and see if you can replicate the same failure you're seeing with the modules outside your car.
Not in your league Rhys but when I look at the MOST loop on my 07 XK wiring diagram, the front stack includes touchscreen, infotainment control module, integrated audio module AND the amplifier and the test connector. I've looped out the trunk stack without issue. All have been with parts in the car though.
So maybe the Canbus is looking for the Amp? Even so, I would think you could loop out the trunk stack in your car, then loop out the amp in your car and see if you can replicate the same failure you're seeing with the modules outside your car.
That's useful to know about the trunk stack! According the the xf diagrams the only modules that are cabin side are infotainment, integrated audio, screen and finaly the Bluetooth module. (Lower end xfs the amplifier is built into the integrated audio). The most basic xf has no modules outside of the cabin so just those 4, so in theory it should be good.
I'm beginning to suspect it's CCF related, I just hooked up the code reader to it whilst set up on the test bench, I'm getting a fault on the infotainment module whilst replaying the can messages, along the lines of control unit configuration not compatible, which would explain why it worked fine looping them out in your car with the rest of the components still there.
It's a shame but I may need to go a different route....
I've found the message that creates the fault so may see if I can play around with that and see if can somehow come up with the correct configuration that this doner car had
Yes - you can definitely get it to work with one of the modules looped out. That's how folks on here have tested Eg if BT module is faulty. Use a fiber loop to bypass it and it should work fine without it.
But maybe there are one or two specific ones that are needed?
Why do you want touchscreen to work out of the car?
I've been working on an app that takes over some of the cars can bus functionality, now trying to replace all the functions in the OEM screen, and create a firewall that overrides the ICMs messages with my own when required. It's much easier to do off the car as you don't have to worry about all the traffic from other modules. Thanks for the confirmation regarding it still working whilst linked out!
That's useful to know about the trunk stack! According the the xf diagrams the only modules that are cabin side are infotainment, integrated audio, screen and finaly the Bluetooth module. (Lower end xfs the amplifier is built into the integrated audio).
Yep, sorry. Same applies to the basic XK amps are also built into the integrated audio. Diagram referred to the premium, which I upgraded my XK to, so I spaced out the original setup.
Thought I'd figured this out so many times today! It's quite interesting and have learnt a ton from it, but still now luck, what's happened today:
First I plumbed in my icarsoft into my bench setup, pulled some codes from the ICM, main problematic looking one was: control unit configuration incompatible. I figured the can id of 400 was causing this one.
A mega knowledgeable guy over on the freelander forums helped me out with this and explained the 400 Id is the car configuration, so makes sense. In here is the vin for the car, luckily the guy that sold the parts wrote the vin in the cd player.
Thought I would take a stab at manually inputting the vin into SSD and take a look around, whilst doing this I thought may aswell hookup the mongoose to the test bench and see what I can do.
Done this, got the modules showing online that were set up, and decided if I put my actual cars vin in (the messages I'm replaying are from my car) and then see if I can flash the modules off of the car according to my as-built CCF.
This snagged when you begin the flash, the network test step queries the modules for the vin and then checks that they match, it seems to query the rear junction box, from junction box, and the pcm.
After a while I managed to write a script on the pi that listens to this query, and then responds with the vin.
Boom it worked,
Flashed the ICM through reconfigure, still not working, tried flashing it through new module, it then asks to learn the vin, and this can only be done on a brand new module.
So **** out of luck there, tried to change the vin in the can logs from my car, still no success. Then I noticed the cd changer is called the audio control module, so began to think that this could be the reason for the control module configuration fault...so then gave this a flash, whilst doing this I notice add wants to load the part number beginning 7F6N but the unit I have is 7G9N, flash went though anyway, but yet again still no luck, and same fault code appearing.
Not a complete waste if time, figuring how to flash off the car could be usefull, and being able to trick the VIN, obviously don't do any of the above on your actual car, this was just a cheap set up I sourced off ebay
So, so interested in getting in on all this, I just haven't had time yet. I have a spare screen and was planning on playing with it but from a different angle of repurposing the MOST transceiver driver from inside. It's using an Oasis OS8104 chipset which there's really not a lot of support for, which I guess is why it's so hard to find any kind of off the shelf interface you can just patch into the MOST network which would seem to be the simplest way of achieving a lot of what I wanted to.
Great work so far Rhys!
Last edited by davetibbs; Feb 7, 2020 at 11:26 PM.
The ICM needs to receive the Car Configuration File (CCF) via MS-CAN, all the time, every time, not just the VIN.
CCF tells the ICM what car it's in, and what options are fitted;
e.g.
X250 XF
Premium Sound System
6-stacker CD
Bluetooth Phone
Navigation
No TV
DAB
Radio Band EU
etc
etc
If it doesn't get this data, it cannot pass that data on to the FCDIM (touchscreen) and ACM (head unit) via MOST, if that data is missing, the screen doesn't know which features to display, the radio doesn't know what frequency bands to tune, etc...
So really what you need to do is be able to mimic the MS-CAN broadcast with all the relevant data in it.
The ICM needs to receive the Car Configuration File (CCF) via MS-CAN, all the time, every time, not just the VIN.
CCF tells the ICM what car it's in, and what options are fitted;
e.g.
X250 XF
Premium Sound System
6-stacker CD
Bluetooth Phone
Navigation
No TV
DAB
Radio Band EU
etc
etc
If it doesn't get this data, it cannot pass that data on to the FCDIM (touchscreen) and ACM (head unit) via MOST, if that data is missing, the screen doesn't know which features to display, the radio doesn't know what frequency bands to tune, etc...
So really what you need to do is be able to mimic the MS-CAN broadcast with all the relevant data in it.
Thanks Cambo!
I believe I have this covered (to some degree) I'm replaying the can capture from my car, this was captured for a good 5 minutes right from start up.
So it seems all 36 messages are getting sent over, I'm guessing there's something inside there that's conflicting with the firmware loaded into the ICM?
I had a little look around in the as-built CCF for both cars to try and map some of those values across as I can modify them in the can capture before replaying, but not sure if the addresses in the CCF viewer are 1 to 1 (I'd be very surprised if they are)
The only thing not flashed through sdd (using my actual cars vin) is the FCDIM, but not sure if this would make much difference, or if it's worth the 2 hours.
Last edited by Rhys Morgan; Feb 8, 2020 at 03:01 AM.
Some mismatches (mismatched hardware vs CCF) will stop the infotainment system from starting up;
Head unit; base vs mid/premium
Head unit; single CD vs 6-stacker
Amplifier; mid vs premium
So literally having the wrong module installed.
Incorrect software in the ICM is also a show-stopper, have seen this with XF software in a pre-2010 XK, but i'm not certain about 2009MY vs 2010-2011MY software in an XF ICM.
The accessory modules like NAV, TVM, DAB, BPM, AUU don't make any difference, can be left out.
Wrong software in the FCDIM may also do it, like XK software in an XF & vice-versa, however we did find that the XF didn't seem to care if it was 2009MY or 2010-2011MY software/hardware, that was pretty much a one-off test though.
thats really handy to know, thankyou! I'm definately leaning towards one of those 3 failure points, going to try and figure out which means which in CCF can messages and then see if they can be overridden. If all else fails will try and flash the FCDIM..
The saga continues, I picked through the CCFs for both cars, and highlighted each bit that was different, I then figured out where they were in the 400 canbus messages (400 appears to be for block 2 of the CCF which seems to contain most of the information) and set them all to match the donor cars CCF, but.....still no luck, exact same symptoms. The 401 messages (block 1) should be next to pick through, I did give these a quick run over, and found a couple different, but really need to spend a few hours on it. Strangely enough in this block there's some confusing stuff, like showing abs is not fitted.
Anyway for a check with less effort I'm just flashing the HLDF now, but I'm not hopeful that will work, fingers crossed though, here's a picture of the current rats nest
Another update today, looks like @Cambo was right, I managed to map both blocks of CCF data on the canbus (IDs 400 and 401) to the asbuilt CCF data from the doner car. Now replaying the messages, I no longer get the error code mentioned above, that states configuration is not compatible.
however the screen is still doing the exact same. No error codes that look out of place, nothing. So I've just started to reflash the display again, as last night i put the software from my actual car on there, but I'm not hopeful.
They should both be 2008/2009, both models are the 2.7 engine. which was only in production for a couple of years, so they should be fairly close on that one.
8X2310E889AC - XF to R19384 2009MY
8X2310E889AD - XF to R39470 2009MY
8X2310E889AE - XF to R47153 no sup 2009MY
9X is different tech. Based on Cambo's comment, the one off they were working on, these may be OK.
9X2310E889AB - XF to R61036 no sup 2010MY
9X2310E889AC - XF to S07281 2011MY
9X2310E889AD - XF to S20752 no sup 2011MY
I would check the same numbers against the rest of the modules but if you're confident
thats interesting, the screen from the doner car is
screen - 9X23-10E889-AB
ACM - 7G9N-18C915-TA
ICM - 8X23-14C512-AA
vin for the doner is SAJAC061097R28392
It does look suspiscous with the 9X23 mixed the with 8X23, the guy selling it all on ebay did have a ton of jag stuff, so perhaps he just threw together this set and the screen doesnt belong.... what does the "no sup" mean?
Make touchscreen work off of the car
