Forscan and the 2020 GT500

[Epiphany]

has there been any movement for the GT500 yet I still cant get mine to connect, but i feel that because I am tuned and its locked

Take some screenshots of the messages you see when trying to connect and post them here...

Sponsored

 

[V00D00]

Take some screenshots of the messages you see when trying to connect and post them here...

Im goign to flash the stock tune just to attempt to play around, se if thats it. Should be as my f150 and Explorer ST both can be accessed by forscan when on stock tune, and both have PBD tunes as well

 

[Snoopy49]

It looks like all you have to do is enter the Factory PCM part number and you should be able to use ForScan with your tune. No need to re-flash the factory tune.

 

[16Kobra]

I did the ST today, suer easy and I think they made headroom as they had premade screens for most, so no # counting/altering.

has there been any movement for the GT500 yet I still cant get mine to connect, but i feel that because I am tuned and its locked

try unloading tune and load stock tune in. make your mods with Forscan. Then reload your tune.

Just an idea. Have heard that works.

I know Lund locks his tunes and you can not do anything unless you unload the tune

 

[bendensez]

Hey all. I have a 2020 GT350 and looks like it shares the same modules as the GT500. My BCM has the same PN and software version as Epiphany's GT500. As we are all learning, many of the previously known memory maps have been changed for 2020. I also desperately wanted to disable the double honk.

We know the double honk bit no longer resides at 726-41-02: xxx? xxxx xxyy. I also bought the IDS file from Jason at FLVPmods.com. I don't want to be the one to take away business from Jason, as he put the time in to figure this out and has decided to charge for it. All I'll say is that you don't need IDS to make this change. Buy the file, do a compare of the file he provides to your as-built .ab file and you'll find the address and bit position to change in FORScan. I'll let someone else decide to divulge the memory address and bit location, if they so choose.

 

[bendensez]

I would also like to calibrate my speedometer for my new GT350R spec wheels with 30 series tires. It is obvious that the two bytes for wheel circumference no longer reside at 726-12-01: xxxx ???? xxyy by inspection of current as-built data for my car and some other 2020s. Based on some 2019 model year as-built data and corroboration from multiple posts on this forum, I'm looking for 0844 hex for wheel circumference on my non-R 350. The GT350R should have 07F9 hex for wheel circumference. (FWIW, It looks like Ford factors in a ~3% circumference reduction from calculated due to tire compression under weight) Comparing 2020 as-built data from my car and a 2020 GT350R, the entries for 726-12-01 are identical between the two and a number much, much larger than my wheel circumference in mm. After sleuthing around on other forums, I found mention on the F250 forum that the two bytes for wheel circumference (for 2020) are now split between 726-15-01: xxxx xxxx ??yy and 726-15-02 ??xx xxxx xxyy. I wondered if the same might apply to the GT350. So, back to as-built data for my 2020 GT350 and a 2020 GT350R and I find the expected wheel circumferences 0844 and 07F9, respectively, split between those memory locations. To further corroborate this, I looked at as-built data for a 2020 base GT500 and it has 0854 hex split between those two positions. 0854 hex is 2132 decimal. The calculated wheel circumference of the 315/30R20 tire is 2190 mm. 2132 is 97.4% of 2190, so there is the ~3% factor for reduction in circumference.

So, I do believe 726-15-01: xxxx xxxx ??yy and 726-15-02 ??xx xxxx xxyy hold the two bytes for wheel circumference used for speedo cal on both the GT350 and GT500. I will be trying this once I get my new wheels on and report back.

 

[gfcobra04]

I would also like to calibrate my speedometer for my new GT350R spec wheels with 30 series tires. It is obvious that the two bytes for wheel circumference no longer reside at 726-12-01: xxxx ???? xxyy by inspection of current as-built data for my car and some other 2020s. Based on some 2019 model year as-built data and corroboration from multiple posts on this forum, I'm looking for 0844 hex for wheel circumference on my non-R 350. The GT350R should have 07F9 hex for wheel circumference. (FWIW, It looks like Ford factors in a ~3% circumference reduction from calculated due to tire compression under weight) Comparing 2020 as-built data from my car and a 2020 GT350R, the entries for 726-12-01 are identical between the two and a number much, much larger than my wheel circumference in mm. After sleuthing around on other forums, I found mention on the F250 forum that the two bytes for wheel circumference (for 2020) are now split between 726-15-01: xxxx xxxx ??yy and 726-15-02 ??xx xxxx xxyy. I wondered if the same might apply to the GT350. So, back to as-built data for my 2020 GT350 and a 2020 GT350R and I find the expected wheel circumferences 0844 and 07F9, respectively, split between those memory locations. To further corroborate this, I looked at as-built data for a 2020 base GT500 and it has 0854 hex split between those two positions. 0854 hex is 2132 decimal. The calculated wheel circumference of the 315/30R20 tire is 2190 mm. 2132 is 97.4% of 2190, so there is the ~3% factor for reduction in circumference.

So, I do believe 726-15-01: xxxx xxxx ??yy and 726-15-02 ??xx xxxx xxyy hold the two bytes for wheel circumference used for speedo cal on both the GT350 and GT500. I will be trying this once I get my new wheels on and report back.

Ford must use this 3% reduction across all models because when my F350 speedo say 75mph per my garmin gps I’m actually only going 72mph.

 

[Epiphany]

I also bought the IDS file from Jason at FLVPmods.com. I don't want to be the one to take away business from Jason, as he put the time in to figure this out and has decided to charge for it. All I'll say is that you don't need IDS to make this change. Buy the file, do a compare of the file he provides to your as-built .ab file and you'll find the address and bit position to change in FORScan. I'll let someone else decide to divulge the memory address and bit location, if they so choose.

That's what I did. I used the comparator tool I linked a few pages ago.

http://www.compulsivecode.com/images/asbuiltexplorer.zip

There was no way I was going to involve a dealer/IDS in this endeavor and simply compared my file to the one Jason wrote until I found the change he made. I then used FORScan to make the appropriate change. Eventually this will all be public or mainstream but I'm trying to respect Jason's efforts here as well. The charge for him to write the file was rather inexpensive.

 

[Jmeo]

I would also like to calibrate my speedometer for my new GT350R spec wheels with 30 series tires. It is obvious that the two bytes for wheel circumference no longer reside at 726-12-01: xxxx ???? xxyy by inspection of current as-built data for my car and some other 2020s. Based on some 2019 model year as-built data and corroboration from multiple posts on this forum, I'm looking for 0844 hex for wheel circumference on my non-R 350. The GT350R should have 07F9 hex for wheel circumference. (FWIW, It looks like Ford factors in a ~3% circumference reduction from calculated due to tire compression under weight) Comparing 2020 as-built data from my car and a 2020 GT350R, the entries for 726-12-01 are identical between the two and a number much, much larger than my wheel circumference in mm. After sleuthing around on other forums, I found mention on the F250 forum that the two bytes for wheel circumference (for 2020) are now split between 726-15-01: xxxx xxxx ??yy and 726-15-02 ??xx xxxx xxyy. I wondered if the same might apply to the GT350. So, back to as-built data for my 2020 GT350 and a 2020 GT350R and I find the expected wheel circumferences 0844 and 07F9, respectively, split between those memory locations. To further corroborate this, I looked at as-built data for a 2020 base GT500 and it has 0854 hex split between those two positions. 0854 hex is 2132 decimal. The calculated wheel circumference of the 315/30R20 tire is 2190 mm. 2132 is 97.4% of 2190, so there is the ~3% factor for reduction in circumference.

So, I do believe 726-15-01: xxxx xxxx ??yy and 726-15-02 ??xx xxxx xxyy hold the two bytes for wheel circumference used for speedo cal on both the GT350 and GT500. I will be trying this once I get my new wheels on and report back.

This is great news. I have new wheels and tires coming in the next few weeks, and I would like to change the BCM to reflect the new sizes. I went from 305/30/20 in the front to 315/30/21, and from 315/30/20 in the rear to 325/30/21. I wonder if you would know what changes I will need to make to correct the speedometer?

Thanks,

Jaime

 

[bendensez]

This is great news. I have new wheels and tires coming in the next few weeks, and I would like to change the BCM to reflect the new sizes. I went from 305/30/20 in the front to 315/30/21, and from 315/30/20 in the rear to 325/30/21. I wonder if you would know what changes I will need to make to correct the speedometer?

Thanks,

Jaime

Hi Jaime -

Just want to make the disclaimer that all of this is preliminary at this point until those of us with MY2020 start trying this out.

The speedometer is based on the rear wheel circumference. The calculated circumference of your new rear wheel/tire combo is 2288.3 mm. I'd use the same factor (97.37%) Ford is using on the stock 30 series to reduce the circumference, which puts your number at at 2228.1 mm. Round to the nearest mm for 2228, which is 08B4 hex. So, I'd go:

726-15-01: xxxx xxxx 08yy
726-15-02 B4xx xxxx xxyy

I know on the GT350, you need to perform the PCM relearn process as part of the change, so you should do that. The GT500 also has a TCM and I've read on other forums regarding other vehicles that have a TCM that you also need to perform the relearn process on the TCM as well when changing wheel circumference.

Best,
Brendan

 

[V00D00]

That's what I did. I used the comparator tool I linked a few pages ago.

http://www.compulsivecode.com/images/asbuiltexplorer.zip

There was no way I was going to involve a dealer/IDS in this endeavor and simply compared my file to the one Jason wrote until I found the change he made. I then used FORScan to make the appropriate change. Eventually this will all be public or mainstream but I'm trying to respect Jason's efforts here as well. The charge for him to write the file was rather inexpensive.

thats my thought process as well. let the guy make his money for his time effort/work, but eventualy it will leak. i can hold off until then as im sure there will be more things i want to play with.. hey isnt that the same thought process as ADM's, paying for the here and now vs waitin till demand dies lol

 

[bendensez]

...

So, I do believe 726-15-01: xxxx xxxx ??yy and 726-15-02 ??xx xxxx xxyy hold the two bytes for wheel circumference used for speedo cal on both the GT350 and GT500. I will be trying this once I get my new wheels on and report back.

Check out my post in the GT350 Forscan thread for more detail. Short story is that I have verified that the two bytes that represent wheel diameter are now stored in the above locations. My 2020 GT350 speedometer is now accurate after my Signature SV902 wheel installation.

As I mentioned before, my BCM part number and software version are the same as Epiphany's BCM on his 2020 GT500 and I verified that the numbers in those locations in the GT500 BCM make sense, so I have no reason to believe that the 2020 GT500 is any different than the 2020 GT350.

 

[Jmeo]

Check out my post in the GT350 Forscan thread for more detail. Short story is that I have verified that the two bytes that represent wheel diameter are now stored in the above locations. My 2020 GT350 speedometer is now accurate after my Signature SV902 wheel installation.

As I mentioned before, my BCM part number and software version are the same as Epiphany's BCM on his 2020 GT500 and I verified that the numbers in those locations in the GT500 BCM make sense, so I have no reason to believe that the 2020 GT500 is any different than the 2020 GT350.

Brendan,

Strong work!

I just wanted to ask you one more time what you think I should be changing for the new wheel sizes? My setup ships Monday, and hopefully deliver Friday.

New size front: 315/30/21
New size rear: 325/30/21

I appreciate your help very much.

Jaime

 

[bendensez]

Brendan,

Strong work!

I just wanted to ask you one more time what you think I should be changing for the new wheel sizes? My setup ships Monday, and hopefully deliver Friday.

New size front: 315/30/21
New size rear: 325/30/21

I appreciate your help very much.

Jaime

Hi Jamie -

I'd go with 08B4 split between those two locations.

726-15-01: xxxx xxxx 08yy
726-15-02: B4xx xxyy

This takes into account your new wheel circumference and the 97.37% scaling factor Ford appears to be using on the GT500.

The only thing I'm unsure of with the GT500 is the fact that it's got a TCM and you may get a DTC in that module as well as the PCM. Forscan can perform the relearn on the PCM to eliminate it's DTC, but I'm unsure if Forscan will be able to perform a relearn yet on the new TCM. You may just have to give it a try and see what happens. Worse case, you revert back to original settings until it gets figured out.

Best,
Brendan

 

[Jmeo]

Hi Jamie -

I'd go with 08B4 split between those two locations.

726-15-01: xxxx xxxx 08yy
726-15-02: B4xx xxyy

This takes into account your new wheel circumference and the 97.37% scaling factor Ford appears to be using on the GT500.

The only thing I'm unsure of with the GT500 is the fact that it's got a TCM and you may get a DTC in that module as well as the PCM. Forscan can perform the relearn on the PCM to eliminate it's DTC, but I'm unsure if Forscan will be able to perform a relearn yet on the new TCM. You may just have to give it a try and see what happens. Worse case, you revert back to original settings until it gets figured out.

Best,
Brendan

OK, thanks for the help, and advice. I will give it a try when I get my wheels on the car, and update here to let you know what happened.

Jaime

Sponsored