2018 gauge cluster retrofit

[breeves002]

This is a good piece of possible information. Thanks for tracking it down.

I would be weary about too much mudding around in the GWM. Its a very important device that can break the whole CAN network if its configured wrong.

This ONLY looks like it changes how the IPC sees the high beams indication. However I don't think the IPC cares if the message comes from the BCM or SCCM - it just gets a message saying high beams are on so turn that indicator on. Now it is possible that me finding the change in 720-09-01 is telling the IPC to look at the BCM for high beams indication instead of the SCCM. Totally possible.

Sponsored

 

[breeves002]

Update: GWM has the same ABD for 2015-2017 and 2018 model years... thanks but that was a bust..

The GWM do have a different part number though according to the ABD. I've noticed these numbers don't always directly relate to real life part numbers though.

My 2016's part number: GR3T-14F642-AA
2018'S part number: JR3T-14F642-AE

 

[breeves002]

Anyone buying the IPC from Tasca use code "18FEB7" to save 7% off. Thats like $100+ when you order everything... Obviously its only good for a few days.

 

[zackmd1]

Update: GWM has the same ABD for 2015-2017 and 2018 model years... thanks but that was a bust..

The GWM do have a different part number though according to the ABD. I've noticed these numbers don't always directly relate to real life part numbers though.

My 2016's part number: GR3T-14F642-AA
2018'S part number: JR3T-14F642-AE

Same part number. The GWM just has had a slight revision (could literally be anything) between your vehicle and 2018.

So does the new SCCM High beam work as expected before you change that code in IPC? If it no longer works after the IPC ABD line change then I don’t see how it can be anything else but a code problem with the IPC....

 

[breeves002]

Ok so here's the status on the high beams. When you install the new IPC only, without programming the ABD, the high beams work with indication. If you copy ABD from a 2018 the indication goes away but high beams still work. After making one change of ABD (720-09-01 xxxx 0xxx) in the IPC you get your high beams indication and they still work. IPC code does NOT change how the high beams operate it only changes if the indication works or not.

Once you change the SCCM the high beams will only work with flash to pass. They will not stay on. Does not matter if you have your OEM SCCM programming or programming directly from a 2018. Or programming from a 2018 with your old steering wheel controls line. They still do not work.

I do NOT think its an IPC issue. The IPC doesn't command the lights at all as far as I know. Its just the indication. The SCCM tells the BCM to turn the high beams/turn signals on when you press the button. My guess is the 2018's have a different way the BCM is told this for whatever reason and thats where the disconnect it happening. I could be wrong though.

Does that make sense?

The IPC indicator data was found by my testing. That bit was not set in any 2018. My best guess is the BCM also tells the IPC wether to indicate high beams (or other lights) on or off. It would be nice to know exactly what module sends that data to the IPC. Would tell us where the problem is.

I explained that earlier kind of. The high beams indicator stops working with the ABD in the new IPC but the high beams themselves only stop working with the new SCCM. That line of code in the IPC doesn't change anything - [MENTION=32917]p6cl[/MENTION] said his high beams stopped working with the new SCCM and that was before he had changed the line of code in the IPC to turn the indicator on. The IPC only indicates high beams it doesn't command them. I really think that line just tells the IPC what module to look for the message from. If it even cares what module it comes from.

 

[zackmd1]

I explained that earlier kind of. The high beams indicator stops working with the ABD in the new IPC but the high beams themselves only stop working with the new SCCM. That line of code in the IPC doesn't change anything - [MENTION=32917]p6cl[/MENTION] said his high beams stopped working with the new SCCM and that was before he had changed the line of code in the IPC to turn the indicator on. The IPC only indicates high beams it doesn't command them. I really think that line just tells the IPC what module to look for the message from. If it even cares what module it comes from.

Well damn... :frusty:

 

[breeves002]

Yeah I feel the same way. It just has to be some miscommunication between the SCCM an BCM. Thats my best guess.

The switch is a possibility but super unlikely...Like I said I'll try that probably tomorrow. The MFS have their own part numbers. I didn't look if they were the same for my 2016 versus the 2018 though.

 

[racingmason]

Im surprised Ford just doesn't release a kit for this.

 

[breeves002]

So the MFS have the same part number on them. I decided to try swapping anyway. Did not work. High beams issue still unsolved..


On another note...I have a different, odd problem. I wonder if its to do with my RPM set point but my throttle cut happens at like 7200 rpm indicated in the cluster but my throttle cut is set at 7600rpm in the PCM. The old cluster could hit the full 7600 no problem. I actually almost never hit it... Does anyone else have this issue that has their redline set at 6500rpm? I'm going to log data tomorrow and see if FORScan RPM agrees with the cluster or not. I may try switching the redline to 7400rpm and see if somehow that changes something.

I put the stock tune back on and it was cutting out at 6700-6800 rpm indicated...

 

[db252]

You know mine is set at 7400 starting redline and my tach is on point 100%. Did a dyno a couple weeks ago and it hit the limiter exactly at 7800.

 

[breeves002]

Yeah I'll have to see if switching it to 7400 fixes it. Since theres the cool shift point feature I don't care about the redline being lower as much. That would be a bummer though.

 

[buzz-dee]

A little help from a friend...

“
2018:

High Beam

The high beam indicator informs the driver that the high beams are turned on. The IPC receives the headlamp high beam status message from the GWM over the HS-CAN3. The GWM receives the headlamp high beam status message from the SCCM module over the HS-CAN2.

2017:

High Beam

The high beam indicator informs the driver that the high beams are turned on. The IPC receives the headlamp high/low status message from the GWM over the HS-CAN3. The GWM receives the headlamp high/low status message from the BCM module over the HS-CAN1.
“

Check GWM (gateway module) for ABD differences.

Very good find.

Would be interesting to see how the high beams are commanded in MY18. Wondering if there’s a difference too

 

[breeves002]

My guess is they're still commanded the same way. Message from the SCCM through the GWM to the BCM. I just think they changed the message with the new SCCM and our BCM takes it as a flash to pass message.

 

[TexasRebel]

My guess is they're still commanded the same way. Message from the SCCM through the GWM to the BCM. I just think they changed the message with the new SCCM and our BCM takes it as a flash to pass message.

I'll bet there is a change. They are different light technology. High beams in the LEDs likely don't work the same way as the HIDs.

 

[breeves002]

I'll bet there is a change. They are different light technology. High beams in the LEDs likely don't work the same way as the HIDs.

I tried changing the bit in the BCM that tells it what type of bulbs they are to the 2018 value. Ours is a 0 2018 is a 1. Did not work.

The high beams should operate the same way though. All it does is raise the electric cutoff in both types, right?

Sponsored