Go Back   Australian Ford Forums > General Topics > The Pub

The Pub For General Automotive Related Talk

Reply
 
Thread Tools Display Modes
Old 15-07-2021, 11:07 PM   #1
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

[/thread]

Thank you for putting in the effort to post and take photos
jakka351 is offline   Reply With Quote Multi-Quote with this Post
4 users like this post:
Old 16-07-2021, 10:31 PM   #2
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
I think the rev-limiter is 6K - but I've not found a way to lower it to something better like 5.5K - I'm not sure I really care though.

I've done what I came here to do.
I'm not going to make a habit of posting extra stuff like this..

The FG2 EEPROM locations 0x07E, 0x07F & 0x080 all contain byte value 0x78. They can also be read and written by ID 0xEE01 via OBD2. Somehow there are 3 modes, each of which looks up one of these byte values, but I can't tell how to switch modes - so set them all to the same value - as they are presently...

0x78 (hex) is decimal 120, and 120 * 50 = 6000 (RPM).

5500 RPM / 50 = 110 which is 0x6E (hex).

Verified as working, on the bench... You're welcome.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 21-07-2021, 10:12 PM   #3
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
I'm not going to make a habit of posting extra stuff like this..
I wish.

Quote:
Originally Posted by JasonACT View Post
Somehow there are 3 modes, each of which looks up one of these byte values, but I can't tell how to switch modes - so set them all to the same value - as they are presently...
So, I'm talking to my car-mad mate at work about this stuff (the one who says I own a taxi, while he's got a couple of really old Skylines)... I tell him about the RPM alarm I've now got, and he asks, can you set it differently depending on which gear you're in, because that's what I had to do with new my set-up?

ID 0xEE01 via OBD2 may get a work-out sometime later, because I'm not pulling the Cluster out anytime soon again!

Incidentally, the boost gauge on the FPVs, that's a real gimmick I feel - it reacts at the touch of a, well, foot-pedal. I was sure I had the calculations correct for boost on my "home made" gauges (negative at idle, closing in on zero with revs in neutral, building with power in gear) but this thing seems to move about just to make you feel good. Maxes out fairly easily too, and while I've had my car tuned, there's not much more going on in the hardware over stock, cold-air-filter?

Maybe I am going to switch to a 2-Bar gauge soonish too. Lucky I moved the [new full-size] EEPROM to the other side of the circuit board [now using a socket]. 5 of the EEPROM pins are gounded, so I only needed 4 wires in ribbon format of about 9cm to do that. Good decision. I cut a couple of plastic air-vent bits off so it can be removed from the unit without any disassembly. Got to pull it out from the car though.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 21-07-2021, 10:52 PM   #4
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
I wish.



So, I'm talking to my car-mad mate at work about this stuff (the one who says I own a taxi, while he's got a couple of really old Skylines)... I tell him about the RPM alarm I've now got, and he asks, can you set it differently depending on which gear you're in, because that's what I had to do with new my set-up?

ID 0xEE01 via OBD2 may get a work-out sometime later, because I'm not pulling the Cluster out anytime soon again!

Incidentally, the boost gauge on the FPVs, that's a real gimmick I feel - it reacts at the touch of a, well, foot-pedal. I was sure I had the calculations correct for boost on my "home made" gauges (negative at idle, closing in on zero with revs in neutral, building with power in gear) but this thing seems to move about just to make you feel good. Maxes out fairly easily too, and while I've had my car tuned, there's not much more going on in the hardware over stock, cold-air-filter?

Maybe I am going to switch to a 2-Bar gauge soonish too. Lucky I moved the [new full-size] EEPROM to the other side of the circuit board [now using a socket]. 5 of the EEPROM pins are gounded, so I only needed 4 wires in ribbon format of about 9cm to do that. Good decision. I cut a couple of plastic air-vent bits off so it can be removed from the unit without any disassembly. Got to pull it out from the car though.
Refer to it as an R33 Maxima, they get livid.
jakka351 is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 17-07-2021, 12:26 AM   #5
PHATAL
Donating Member
Donating Member1
 
PHATAL's Avatar
 
Join Date: Feb 2006
Location: Roxby Downs, SA
Posts: 1,437
Default Re: FORD technical service bulletin : ICC touch screen display

Again - I don't understand most of this (I probably should though) but thanks sincerely mate for your efforts. It has been a wild ride.

Sent from my SM-G998B using Tapatalk
__________________
ZG Fairlane 500 351 - First car - Now restoring! - LOOKING FOR ZG PARTS - BLACK AUTO CONSOLE - BLACK DASH PAD - BLACK SEAT BELTS (WITH THE METAL BUCKLES) -
RIGHT REAR CHROME TRIM

XF Falcon S Update EFI - SOLD
EL2 XR8 - SOLD
BF F6 RSPEC #139 - SOLD
Now rocking the SZ Territory Titanium Petrol Family Beast
PHATAL is offline   Reply With Quote Multi-Quote with this Post
3 users like this post:
Old 17-07-2021, 06:54 PM   #6
QIKESP
Regular Member
 
QIKESP's Avatar
 
Join Date: May 2006
Location: Melbourne
Posts: 372
Default Re: FORD technical service bulletin : ICC touch screen display

Thanks again, Time to dust off the spare cluster and give this a go !

Appreciate all the effort you've put into this thread
QIKESP is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 24-07-2021, 03:48 PM   #7
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

Quite a while ago now, someone sent me their corrupt 2014 firmware which was non-Nav, I looked again today, there are appear to be no differences in the apps, bar the bootloader, kernel, missing navi and missing "FpvLe" directory with the images needed for the Fpv Gauges (/packages/factory/hmi/root_dir/usr/hmi/HighSeries/FpvLe). You would have to copy the FpvLe directory over (it's about 1MB - so should fit with what little space is left on those units - they are on github in the 2014 Navi archive).

You can possibly enable these gauges ONLY IF you are running the 2014 software (I've done it, but only on the Navi unit) with a script to run ***some*** of these commands (pick the 2 you want) in QNX:

#turn on FPV button (off=0 or on=1)
send2 -w /hmi/dp/1/1907 0
send2 -w /hmi/dp/1/1907 1

#switch manual (volts=0) or automatic (temperature=1)
send2 -w /hmi/dp/1/1908 0
send2 -w /hmi/dp/1/1908 1

To automate this when the unit boots, I created a shell file (unix line endings! not ms-dos, called say "gauges.sh") in the directory "/packages/system/trailer" with the chosen 2 lines.

Note: Only the voltage gauge works, but it could be a fun thing to do anyway. This can be done (copy guages.sh to the right place) with the recore program I posted earlier (WHICH YOU MUST NOT USE!).

Thanks to the anonymous PM guy who I did this for, who then blocked private messages before I could send these details. Have a nice day

(You should be able to remove the file easily too, the same way, if it doesn't work out.)

Last edited by JasonACT; 24-07-2021 at 03:56 PM. Reason: Edit: add remove
JasonACT is offline   Reply With Quote Multi-Quote with this Post
4 users like this post:
Old 03-08-2021, 07:39 PM   #8
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

I bought one of these off ebay for $15 (came with a USB programmer too, but I was only really after the clip):



Here's a brand new EEPROM I've clipped in, to have a look how it connects:



Seems to work well enough...

Tried it out tonight, the V850E chip's manual states that if you are in reset mode (see the picture below for where I connected the wire to the capacitor to reset the chip when I wanted - you should be able to hold it in reset mode as long as is needed) OR you are in flash programming mode, where most pins stay in their reset (tri-state) configuration...



Then you can connect up an Arduino Nano using pins A4 & A5 (SDA & SCL respectively) to the EEPROM pins (using a common ground, and +12v applied to the Cluster's black-socket power pin) and read/write it while it's still soldered to the circuit board. That youtube video showed some specialist equipment that supplies ~3.0v to the board so the V850E chip doesn't quite power up properly, but still lets you talk to the EEPROM. No-one should attempt that with the cheap stuff being used here, you're likely to corrupt the EEPROM or ruin some of the other components.

This has been a community safety announcement

I forgot to mention, viewing from the front of the Cluster circuit board, the EEPROM is actually upside down - best not to mess with it if that comes as a surprise though.

Last edited by JasonACT; 03-08-2021 at 07:46 PM. Reason: Edit: forgot to mention about the EEPROM's orientation.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
4 users like this post:
Old 30-08-2021, 09:48 AM   #9
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

You can't hit it in an non-FPV with the default setting, true. By default it's set to 6K RPM like the limiter. From what I see of the FPV Cluster though, the limit is higher @6.25K RPM.

I have adjusted mine (it's an OBD2 writable setting, so no need for direct access to the EEPROM) to go off at 5.25K RPM and I can certainly "hit it" and use it to let me know when to shift up.

Whoever said what's in that quote thinks it's an on-off thing, and not adjustable, probably only fiddled with the known As-Built OBD flags - which is where the on-off part is. The adjustable setting is not part of the As-Built data, so they probably never found it while they were fiddling.

JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 30-08-2021, 11:56 AM   #10
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Talking Re: FORD technical service bulletin : ICC touch screen display

Definetly something I'm going to adjust, i can hit the alarm in every gear up until changing into 5th,( havent been able to since moving into the city, but probably a good thing).


It does log a faut code in the pcm everytime I hit it, saying max rpm reached - but that could also be limiter.

Ill post what I find after I figure it out while fidding with my falcon on this forum.
jakka351 is offline   Reply With Quote Multi-Quote with this Post
Old 30-08-2021, 06:05 PM   #11
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

I checked my "Read By ID" dumps of the donor MKI G6E Cluster I've got here, also checked the MKI EEPROM dump in general. I don't see the same repeating value of 0x78 like I do in my MKII Cluster. It's possible it wasn't a changeable setting in the MKI.

EE01 is the ID to use in a MKII. That ID doesn't exist in a MKI either.

If you can get hold of a MKI Cluster firmware update file (should be a bit less than about 256KB) then I can find out for sure. I have managed to find another 8.8KB firmware part/file for the MKII Cluster (this bit loads into RAM for speedier execution, branching out to the larger Flash memory firmware when needed). But I have not been able to download any MKI firmware files from the Ford-IDS download site.

They remove old firmware files when there is an update and you need to guess the latest filename exactly to be given it. You would need to know someone who has had the IDS system for a while, and who has a nice collection of firmware files in the IDS Program Files directory. You would only need the filenames/directly-listing as the files will be available to download.

Last edited by JasonACT; 30-08-2021 at 06:24 PM.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 30-08-2021, 06:30 PM   #12
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
I checked my "Read By ID" dumps of the donor MKI G6E Cluster I've got here, also checked the MKI EEPROM dump in general. I don't see the same repeating value of 0x78 like I do in my MKII Cluster. It's possible it wasn't a changeable setting in the MKI.

EE01 is the ID to use in a MKII. That ID doesn't exist in a MKI either.

If you can get hold of a MKI Cluster firmware update file (should be a bit less than about 256KB) then I can find out for sure. I have managed to find another 8.8KB firmware part/file for the MKII Cluster (this bit loads into RAM for speedier execution, branching out to the larger Flash memory firmware when needed). But I have not been able to download any MKI firmware files from the Ford-IDS download site.

They remove old firmware files when there is an update and you need to guess the latest filename exactly to be given it. You would need to know someone who has had the IDS system for a while, and who has a nice collection of firmware files in the IDS Program Files directory. You would only need the filenames/directly-listing as the files will be available to download.
unfortunately I havent that sort of access to ids stuff, i am going trial and error with this document
https://github.com/jakka351/FG-Falco...ar_hacking.pdf
jakka351 is offline   Reply With Quote Multi-Quote with this Post
Old 30-08-2021, 06:38 PM   #13
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

You might be surprised about who sometimes reads this thread and does have that information. I'll take a look for sure, if it appears here.

My best guess (which doesn't work) is that it (the first update) is called "8R29-14C026-AB" (-AA will never have been made available).

For an FG2, it's not "BR29" like most of the stuff in one, because some of the electronics came from the SZ which seems to have come out first, and which is "AR79".

Last edited by JasonACT; 30-08-2021 at 06:56 PM.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 01-09-2021, 05:28 PM   #14
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Havent found anything yet, but am convinced I will be able to make my cluster play the guitar riff from the Sunday Bloody Sunday intro
jakka351 is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 04-09-2021, 03:13 PM   #15
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

From the dump at the top of this page (post 481, if this post spills over) there's a dump of a MKI XR6 with this content:

0x070 20 20 20 20 10 20 20 20 20 20 81 0e 80 00 ff 00 ____._____..€.ÿ.

Position 0x07A controls features: Police Mode & RPM Alarm
(81 = those two are off, 85 = Police, 89 = RPM Alarm ... 8D = Police & RPM)

Position 0x07E & 0x07F are the RPM Alarm configuration (here they are not set, being FF 00). On my spare MKI G6E Cluster, I've coded these bytes as 69 4A and turned on the RPM Alarm and it goes off when you hit 5250rpm (you can hit 5249 as much as you like, it won't go off). The value for 6000rpm (as mentioned earlier) and what an FPV will have set in these positions is 78 4A. The 4A part is some weird config to do with timing and how low the RPM needs to go below the set limit to reset.

Sad news though, I'm sorry to say, but even though I can enable the RPM Alarm and set where it goes off, these config changes in the EEPROM do not alter any of the values you can read via an OBD2 tool.

So... These are not settable on a non-FPV MKI without disassembling the Cluster.

Even if you enable the alarm, the default set limit will not allow the alarm to go off.

Edit: I forgot to mention... No special checksum needs to be recalculated for changes in that particular area.

Last edited by JasonACT; 04-09-2021 at 03:29 PM. Reason: Edit: No checksum in that area.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 04-09-2021, 03:57 PM   #16
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
From the dump at the top of this page (post 481, if this post spills over) there's a dump of a MKI XR6 with this content:

0x070 20 20 20 20 10 20 20 20 20 20 81 0e 80 00 ff 00 ____._____..€.ÿ.

Position 0x07A controls features: Police Mode & RPM Alarm
(81 = those two are off, 85 = Police, 89 = RPM Alarm ... 8D = Police & RPM)

Position 0x07E & 0x07F are the RPM Alarm configuration (here they are not set, being FF 00). On my spare MKI G6E Cluster, I've coded these bytes as 69 4A and turned on the RPM Alarm and it goes off when you hit 5250rpm (you can hit 5249 as much as you like, it won't go off). The value for 6000rpm (as mentioned earlier) and what an FPV will have set in these positions is 78 4A. The 4A part is some weird config to do with timing and how low the RPM needs to go below the set limit to reset.

Sad news though, I'm sorry to say, but even though I can enable the RPM Alarm and set where it goes off, these config changes in the EEPROM do not alter any of the values you can read via an OBD2 tool.

So... These are not settable on a non-FPV MKI without disassembling the Cluster.

Even if you enable the alarm, the default set limit will not allow the alarm to go off.

Edit: I forgot to mention... No special checksum needs to be recalculated for changes in that particular area.
What about mk1 FPV clusters, although I dare say mine is an XR8 one, its one of the first GS's
jakka351 is offline   Reply With Quote Multi-Quote with this Post
Old 22-09-2021, 08:41 PM   #17
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
From the dump at the top of this page (post 481, if this post spills over) there's a dump of a MKI XR6 with this content:

0x070 20 20 20 20 10 20 20 20 20 20 81 0e 80 00 ff 00 ____._____..€.ÿ.

Position 0x07A controls features: Police Mode & RPM Alarm
(81 = those two are off, 85 = Police, 89 = RPM Alarm ... 8D = Police & RPM)

Position 0x07E & 0x07F are the RPM Alarm configuration (here they are not set, being FF 00). On my spare MKI G6E Cluster, I've coded these bytes as 69 4A and turned on the RPM Alarm and it goes off when you hit 5250rpm (you can hit 5249 as much as you like, it won't go off). The value for 6000rpm (as mentioned earlier) and what an FPV will have set in these positions is 78 4A. The 4A part is some weird config to do with timing and how low the RPM needs to go below the set limit to reset.

Sad news though, I'm sorry to say, but even though I can enable the RPM Alarm and set where it goes off, these config changes in the EEPROM do not alter any of the values you can read via an OBD2 tool.

So... These are not settable on a non-FPV MKI without disassembling the Cluster.

Even if you enable the alarm, the default set limit will not allow the alarm to go off.

Edit: I forgot to mention... No special checksum needs to be recalculated for changes in that particular area.
Ive come up with a bit of a work-around, not going to risk damaging my cluster, but with a bit of raspberry magic and socketcan, can trick the cluster into momentarily thinking the engine is past the limit, triggering the shift alarm, and then clearing the resulting fault code that is logged everytime you the alarm goes off.

Was driving for around with it going off at 1000 rpm, became quite annoying after the novelty wore off.

Havent gotten the light to light up though, just the sound.
jakka351 is offline   Reply With Quote Multi-Quote with this Post
3 users like this post:
Old 04-09-2021, 04:20 PM   #18
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

The G6E Cluster I have has an old firmware loaded into it, from July 2008 (though it's a bit more than a year older than that). It's possible a 2010 Cluster firmware from an FPV has been updated to allow using an OBD2 device to change those values. I've also seen pictures of MKI FPV Clusters, there is a later firmware. There is space for 2 extra gauges in this old G6E model, and I have no doubts I can enable them via the EEPROM.

You would have to scan the 65K IDs to find out. I don't like your chances though :(

I guess the take from my post is, MKI owners in general will need to go to extreme lengths to set this - but then again, they are far more easy to match-up to your car (using Forscan).

I actually have a feeling, you could copy a MKI FPV EEPROM into any MKI cluster and your car wouldn't know it wasn't the original. I think it's only the MK2 that has moved the security stuff into Flash memory, along with the EEPROM.

Edit: Even the FG2 OBD2 interface will not allow you to set the 4A byte, so I do feel it's locked out on MKI's.

Last edited by JasonACT; 04-09-2021 at 04:31 PM. Reason: Edit: About the 4A byte..
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 04-09-2021, 05:36 PM   #19
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

FYI - I can enable the 2 extra gauges, but there is no FPV Splash Screen in this old MKI G6E unit's firmware.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 25-10-2021, 12:22 AM   #20
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
FYI - I can enable the 2 extra gauges, but there is no FPV Splash Screen in this old MKI G6E unit's firmware.

What would it take to edit that firmware and put in my own picture?
jakka351 is offline   Reply With Quote Multi-Quote with this Post
Old 26-10-2021, 06:22 PM   #21
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

I never was able to find/download the MK1 firmware. Then it's protected from changes by a checksum, tested in the firmware bootloader (code of which Ford would never have made public). So, what would it take? Being good buddies with someone in their technology section who worked on all this, and them having held onto enough files and/or details, is about the only way.. So not going to happen, IMHO, sorry.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Old 26-10-2021, 06:44 PM   #22
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
I never was able to find/download the MK1 firmware. Then it's protected from changes by a checksum, tested in the firmware bootloader (code of which Ford would never have made public). So, what would it take? Being good buddies with someone in their technology section who worked on all this, and them having held onto enough files and/or details, is about the only way.. So not going to happen, IMHO, sorry.
What about with renesas software?
jakka351 is offline   Reply With Quote Multi-Quote with this Post
Old 02-11-2021, 08:55 PM   #23
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

I didn't just want to immediately say "No". But that's my answer. Even so, I had put this on my list of things to look at... I had previously gone to a lot of trouble to work out what Ford had done with these devices, they are locked down, Renesas do describe in detail how to secure their chips.. and from what I could see, there are no avenues to open them up.

The thing is, if you flash a bad image into the cluster, then for everyone's sake it's best to not "run" what got flashed - because doing so may crash the chip... Once it's crashed, you can't re-flash. The routines needed for doing so are no longer running.

You can't blame them.

In other news, I've managed to write some USB device drivers (I converted quite a few Linux USB drivers) for the MK2 touch screen. I've got the WiFi chip I'm using, which is connected to the "spare" HW serial port, working at ~250KB/s (or around 70KB/s with constant video decompression)... it's all a bit technical... But on a device plugged into the USB port it only runs at ~30KB/s. The difference is enough to make it not worth bothering too much with it. My application is a remote desktop to a raspberry pi running the Kodi media player.

Look at it this way, "remote desktop" has about 9 frames per second with a hacked-in device (smooth enough video, if you reduce the size to 25%, with a renderer that increases it back to full-screen) compared to less than 4 FPS with a non-modified unit with a USB WiFi dongle. FYI - they did use undocumented APIs for USB memory sticks which seems to work at 860KB/s, the internal flash chip runs at about 4MB/s while my SD card driver I made works at a little over 3MB/s.

But I think this thing is now "done". You either hack hardware into it to get something that works OK, otherwise it's not really ever going to be anything special. I'm a bit sad about that.
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 03-11-2021, 03:56 AM   #24
happy1
FF.Com.Au Hardcore
 
Join Date: Jun 2010
Location: Perth
Posts: 1,315
Default Re: FORD technical service bulletin : ICC touch screen display

Hi, very impressive what you have been able to find out and do with the ICC and cluster. '

Some years ago when I tried to swap in a full set of 2011 Mk2 XR6T(auto) electronics into a 2011 Mk1 XR6T(manual) I had problems to update the As-built data in the cluster, I needed to set it to 'manual' instead of 'auto', but couldn't figure that out back then.

Back then, if the vehicle had been a Focus III, there was a Russian website that had an as-built editor. http://ford.xtlt.ru/ab/ That editor wouldn't quite work with the Falcon file. Is that something that would be useful to do now, to develop an as-built data file fixer that works for FG2 and late Terri?

This link explains a little more how the FoCCCus app worked: http://blog.obdii365.com/2020/01/24/...-coder-reader/

I haven't looked too closely what Forscan can do these days, so maybe that has a solution for it already.

Cheers,

Last edited by happy1; 03-11-2021 at 04:16 AM.
happy1 is offline   Reply With Quote Multi-Quote with this Post
Old 03-11-2021, 05:49 PM   #25
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by happy1 View Post
Hi, very impressive what you have been able to find out and do with the ICC and cluster. '

Some years ago when I tried to swap in a full set of 2011 Mk2 XR6T(auto) electronics into a 2011 Mk1 XR6T(manual) I had problems to update the As-built data in the cluster, I needed to set it to 'manual' instead of 'auto', but couldn't figure that out back then.

Back then, if the vehicle had been a Focus III, there was a Russian website that had an as-built editor. http://ford.xtlt.ru/ab/ That editor wouldn't quite work with the Falcon file. Is that something that would be useful to do now, to develop an as-built data file fixer that works for FG2 and late Terri?

This link explains a little more how the FoCCCus app worked: http://blog.obdii365.com/2020/01/24/...-coder-reader/

I haven't looked too closely what Forscan can do these days, so maybe that has a solution for it already.

Cheers,
Thanks!

I've been running a 2nd hand 2014 cluster (so the newest Mk2 firmware) in my 2012 XR6T for the past half-year and I suspect it came out of a ute. Since I copied over my EEPROM and flashed the CCC data into the last block of flash memory, it is now a full clone - except for the FPV upgrades I gave myself. I'm sure if it came out of a manual, which I don't think it did, it wouldn't "remember" after what I did.

But other than a few details in the CCC data, like the formatted byte and VIN, I really don't know what any of the values do. I assume because it's "Central" data, it gets sent to a few other devices over the CAN BUS, so I didn't bother looking too closely at what the cluster firmware does with it. Most of the cluster firmware is driven by the EEPROM values.

Yeah, I have not looked at Forscan for a while either... I was hanging out for the in-code-out-code stuff to work on a Mk2 (they got it working on the Mk1) but I kind of beat them to the finish-line. I think my method of installing a new cluster is better anyway, nothing else in the car needs to be re-programmed to install the different cluster (or swap them back later).
JasonACT is offline   Reply With Quote Multi-Quote with this Post
This user likes this post:
Old 03-11-2021, 07:37 PM   #26
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Forscan Beta is inching closer to IDS level but not quite there yet. Even using a VCMII you still intermittently get 'this adaptor has can bus problems'. They had released a beta that could update firmwares, but has since been retracted due to people trying to flash things with china obdii dongles.

If you flash a chinese made car with a chinese obd clone will you have a bad time?

Also there are issues with reprogramming vin numbers as forscan only unlocks some modules when going into as built daaaada.


Some guides for anyone out there that might need:


ABS guide by Nigel, the CAN man:
https://www.tiperformance.com.au/kno...bo-conversion/

ICC modules by yours truly:
https://github.com/jakka351/FG-Falco...s-with-Forscan
jakka351 is offline   Reply With Quote Multi-Quote with this Post
2 users like this post:
Old 03-11-2021, 09:06 PM   #27
rollex
PCMTEC
 
Join Date: Jun 2014
Posts: 57
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by jakka351 View Post
Also there are issues with reprogramming vin numbers as forscan only unlocks some modules when going into as built daaaada.
It is a suprise anything works at all ever with how uncomprehendingly complex the systems have become recently.

I have no idea how they manage the systems internally to keep everything running on the assembly line without frantic end of line re-flashing of modules to fix random issues.
rollex is offline   Reply With Quote Multi-Quote with this Post
Old 03-11-2021, 10:33 PM   #28
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Talking Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by rollex View Post
It is a suprise anything works at all ever with how uncomprehendingly complex the systems have become recently.

I have no idea how they manage the systems internally to keep everything running on the assembly line without frantic end of line re-flashing of modules to fix random issues.
Thats why you have a team of dealerships to do that, just a little bit later on in the process.

What does a 2021 model year car have, 100 different modules or close to it. And these are probably all running some ridiculously complicated CAN networks, internet connected and borderline autonomous. May take a while to get used to that instead of the nice simple ms/hs can set up from ten years ago that the DIYer can play with at home.

Have to wait ten years until we see what theyre up to now.
jakka351 is offline   Reply With Quote Multi-Quote with this Post
Old 16-12-2021, 06:48 PM   #29
jakka351
Regular Member
 
jakka351's Avatar
 
Join Date: Oct 2015
Posts: 237
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by JasonACT View Post
Thanks!

I've been running a 2nd hand 2014 cluster (so the newest Mk2 firmware) in my 2012 XR6T for the past half-year and I suspect it came out of a ute. Since I copied over my EEPROM and flashed the CCC data into the last block of flash memory, it is now a full clone - except for the FPV upgrades I gave myself. I'm sure if it came out of a manual, which I don't think it did, it wouldn't "remember" after what I did.

But other than a few details in the CCC data, like the formatted byte and VIN, I really don't know what any of the values do. I assume because it's "Central" data, it gets sent to a few other devices over the CAN BUS, so I didn't bother looking too closely at what the cluster firmware does with it. Most of the cluster firmware is driven by the EEPROM values.

Yeah, I have not looked at Forscan for a while either... I was hanging out for the in-code-out-code stuff to work on a Mk2 (they got it working on the Mk1) but I kind of beat them to the finish-line. I think my method of installing a new cluster is better anyway, nothing else in the car needs to be re-programmed to install the different cluster (or swap them back later).
Would you be able to shed any light on (cluster) CAN id 0x1D7, a remote frame request. I have seen it appear on the FDIM and the IC when they are isolated from all other modules.


And I also saw a 29 bit CAN id (not 11) message from the cluster with a DLC higher than 8. It appeared on the hscan, I am unsure whether it was a socketcan error, but it appeared along side the 0x1D7[7] remote frame request, one single message. have yet to reproduce.
jakka351 is offline   Reply With Quote Multi-Quote with this Post
Old 16-12-2021, 07:51 PM   #30
JasonACT
Away on leave
 
Join Date: Apr 2019
Location: ACT
Posts: 1,732
Tech Writer: Recognition for the technical writers of AFF - Issue reason: Outstanding work on the FG ICC issues. Technical Contributor: For members who share their technical expertise. - Issue reason: The insane amount of work he has put into the Falcon FG ICC is unbelievable. He has shared everything he has done and made a great deal of it available to us all. He has definitely helped a great deal of us with no personal gains to himself. 
Default Re: FORD technical service bulletin : ICC touch screen display

Quote:
Originally Posted by jakka351 View Post
Would you be able to shed any light on (cluster) CAN id 0x1D7, a remote frame request. I have seen it appear on the FDIM and the IC when they are isolated from all other modules.

And I also saw a 29 bit CAN id (not 11) message from the cluster with a DLC higher than 8. It appeared on the hscan, I am unsure whether it was a socketcan error, but it appeared along side the 0x1D7[7] remote frame request, one single message. have yet to reproduce.
No idea sorry, that value does not appear in any of my CAN-BUS recordings on my FG2. Nor does it appear in the WSMs.

Just going back to your quote:

Quote:
Shift Alert or Engine Overspeed Alert?
See page 413-01-50 (instrument cluster) WSM for the FG(1) (section 9.3.33) "Transmission Shift Alarm":

Quote:
An audible chime for maximum vehicle performance will be sounded when a preset RPM threshold
is reached. A hyteresis offset is included to stop it from faults re-triggering. These
parameters - RPM threshold and hysteresis offset, plus number of chimes is EEPROM configurable.
No such statement is included in the FG2 WSM. Most of the really technical details (CAN ids) are gone too for the FG2.

It may be something you can set on the FG(1) or it may be the "secondary boot loader" that allows you to save and restore an EEPROM image... I don't really know (yet).

I wrote:

Quote:
I don't see the same repeating value of 0x78 like I do in my MKII Cluster.

Position 0x07E & 0x07F are the RPM Alarm configuration (here they are not set, being FF 00). On my spare MKI G6E Cluster, I've coded these bytes as 69 4A and turned on the RPM Alarm and it goes off when you hit 5250rpm (you can hit 5249 as much as you like, it won't go off). The value for 6000rpm (as mentioned earlier) and what an FPV will have set in these positions is 78 4A. The 4A part is some weird config to do with timing and how low the RPM needs to go below the set limit to reset.

Sad news though, I'm sorry to say, but even though I can enable the RPM Alarm and set where it goes off, these config changes in the EEPROM do not alter any of the values you can read via an OBD2 tool.

So... These are not settable on a non-FPV MKI without disassembling the Cluster.
Again, maybe the SBL can do this??

When I changed the number of chimes (that weird config thing) it didn't actually work! So, a bug in the firmware.

I.E.
The 4A part:
the '4' part=4*50=200 RPM offset which you need to drop below before the alarm goes off again.
the 'A' part is the number of chimes, A hex is 10 decimal, and... which doesn't work properly in the FG2, you only ever get 10 or 15 or something like that depending on what you set.

The FG2 WSM states, the 3 repeating values I saw are for the different engine types (4cyl eco-boost, I6 & v8).
JasonACT is offline   Reply With Quote Multi-Quote with this Post
Reply

Thread Tools
Display Modes

Forum Jump


All times are GMT +11. The time now is 09:10 AM.


Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Other than what is legally copyrighted by the respective owners, this site is copyright www.fordforums.com.au
Positive SSL