Mondeo MK5 IPC

[DGAlexandru]

M$ XPS version.

IPC, FCIM, SYNC2-3 and MODULE comm NetWork.7z

[Stevebe]

M$ XPS version.

IPC, FCIM, SYNC2-3 and MODULE comm NetWork.7z

THANKS very much appreciated

[Go4IT]

Anybody ever tried if the MK5 IPC would mechanically fit into MK4?

[Stevebe]

Anybody ever tried if the MK5 IPC would mechanically fit into MK4?

its about cm wider and slightly deeper at the top but with a bit of clever moding you could fit one, but that would be the easy bit

[leader]

Anybody ever tried if the MK5 IPC would mechanically fit into MK4?

its about cm wider and slightly deeper at the top but with a bit of clever moding you could fit one, but that would be the easy bit

Hi,

It's not everything only the dimension...
The Convers+ IPC in MK4 communicate on MS-CAN bus meanwhile the MK5 IPC speaks on HS3-CAN. So atleast you need an MS-CAN <-> HS-CAN gateway.

Regards,
leader

[DGAlexandru]

If we decode all the CAN messages that C+ needs and if we manage to decompile the QNX files from Mondeo 5 Cluster then we might be able to do a retrofit

Meanwhile, some other wiring information for Mondeo 5:

BCM, DDM, PDM, Audio, Rear Camera, TPMS, HeadLamps, Fuses and others.7z

[Stevebe]

If we decode all the CAN messages that C+ needs and if we manage to decompile the QNX files from Mondeo 5 Cluster then we might be able to do a retrofit

that would be a achivement

[Stevebe]

If we decode all the CAN messages that C+ needs and if we manage to decompile the QNX files from Mondeo 5 Cluster then we might be able to do a retrofit

Meanwhile, some other wiring information for Mondeo 5:
BCM, DDM, PDM, Audio, Rear Camera, TPMS, HeadLamps, Fuses and others.7z

I forgot to ask but the SYNC2 uses a remote GPS Receiver it’s a 6 pin device but only 4 connections are used 2 are supply and other 2 are twisted pair
But they don’t match to any of the can bus colours , could have a look and see if yo have any get sold where the module is connected ..
There is pictures

620B318C-5C3B-4F64-9E3F-F4BC576BC253.jpeg

4876DDAB-BCF7-4E15-AE58-957B8E94EA4C.jpeg

It US in a small black case

[leader]

Have you identified some JTAG pins on J500 near to SPC5606S MCU?

Might be usefull
mikrohacker.jpg



Btw. I have also mk5 ipc with those numebers - if it is helpful feel free to ask

IMG_20200214_104750.jpg
IMG_20200214_104742.jpg

Thanls the information.
Maybe do you already dumped the IPC or do you have a full dump for it?

[paxtonix]

Maybe do you already dumped the IPC or do you have a full dump for it?

I've made some dumps form mk5 ipc. The structure of the file itself is not like in mk4 ipc.

Mk5 software is based on java - JADE lang.

Code: Select all

    file_checksum = 0x68f574bf;
}?˙˙ü��� �”ź0�����—#!/bin/sh
# =================================================================================
# Name:			bitmaps_preinstall.sh
#
# Description:	Pre-installation script for Jade SWDL of bitmap images file via CAN
#
# This script is downloaded and executed before any application files.
# It can be used to check flash drive integrity, predelete old files etc
#
# Also, the execution time of all commands in this script must not excede 5 min
# (VBF generator appends a minimum of 6 EOF blocks allowing @55s each block) 
# =================================================================================

echo "** BITMAPS PRE_INSTALL ACTIONS**" >> /tmp/vsfdp_swdl_log
echo "** BITMAPS PRE_INSTALL ACTIONS**"

# =================================================================================
# restart the FLASH driver with the options needed for this script
# =================================================================================
echo sending SIGKILL to devf-generic
kill -9 `pidin -p devf-generic -fa | grep -v -epid`
echo starting the FLASH driver with automount disabled, no reclaim, and full verify
devf-generic -s0x10000000,32M -a -f3

if [ -e /proc/boot/waitfor ] 
then
	echo "waitfor flash driver to start"
	waitfor /dev/fs0 30
else
	echo "poll flash driver to start"
	while  [ "$(ls /dev/fs0)" != "/dev/fs0" ]
	do
 		sleep 1	
	done
fi


# =================================================================================
# Can normally safely erase flash partition while a CAN download is ongoing, since 
# the erase takes 5s/MByte whereas CAN download takes 60s/Mbyte (or 24s/Mbyte 
# when compression is used). However, the raw bitmaps partition is a special case,  
# since compression ratios of up to 95% are common for images. That means the  
# download rate is effectively 3s/Mbyte i.e. FASTER THAN THE ERASE !
#
# FORTUNATELY, for downloads on top of X351/L322 releases after 21st August 09, the  
# post-download scripts use pidin and grep to checks for completion of the flashctl
# erase process.
# 
# =================================================================================
flashctl -p/dev/fs0 -o 14m -l 18m -b 6 -e &

echo "** BITMAPS PRE_INSTALL COMPLETE**"
\L?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü���˙˙˙˙?˙˙ü�����

I have some ipc dumps of various mk5 IPC also other cars where this QNX-style display is present. IPC software that is loaded in to Lincoln models have all features already included from factory.
I call it full sw version - they can be easly instaled on mk5 or fusion IPC , after some changes of script.

for ex. if you load ford edge ipc software in to mondeo , the handbrake lamp will stay on, because in mondeo you have manual Handbrake , and edge have electric. Changing asbuild setup will not turn the lamp off. it's need to be done by script - to be onest.
Ford Mondeo/Fusion/Edge/Explorer/Flex and Lincoln ( Luxury ford brand ) have all same type of IPC like those on picture before.

AllCompilation

Instrument Cluster_FordQNX.rar

Here is the EEPROM DUMP

EEPROM_DUMP_mk5.rar

I have also a software with changed background to dark so let's say the backround script is located

JS7T-14C088-BLB.2020V6.software.rar

Files are not secret , But also not widely available -pm me for password.