Paul Neubauer
Well-known member
What steps are required to reset the transmission shift tables using FDRS?
Sponsored
It was changed to 4x1x-xxxx-xxxx. I backed it out. So it was the process of backing out the change that fixed it. Good to know.Whoa! You changed one of the digits on the checksum. That gets automatically calculated by FORScan. By changing it, you had to have changed one of the earlier, primary bits in the string.. This really isn’t good practice, What primary bit was affected by changing the checksum?
I’m not completely following, but I’m glad it worked out.It was changed to 4x1x-xxxx-xxxx. I backed it out. So it was the process of backing out the change that fixed it. Good to know.
I’m just about sure your issues is the gateway config being goofed.For mine I had to go 5684-008D because I enabled the climate auto seats functionality. Power flow is now back for me as well. Not sure about the camera in motion message being fixed about features being disabled though. Will need to test.
Amazon Alexa should be under settings, while PowerFlow is under Features. So that shouldn't be the explanation.Anyone else with a ‘21 job 1 power boost notice their “Power Flow” screen is now gone? Was it replaced by Alexa or was it removed when I added the HVAC temps or enabled the unreal engine?
So nothing I did as that module was updated by Ford and their OTA updates. I only touched the APIM today.I’m just about sure your issues is the gateway config being goofed.
You’re correct, but I had enabled the HVAC temps on the top bar and in doing so told the APIM it was not a HEV. I needed to go back and adjust in Forscan and all is well.Amazon Alexa should be under settings, while PoerFlow is under Features. So that shouldn't be the explanation.
And here's Alexa with Unreal Engine rendering.
![]()
So I don't know what would be the reason Power Flow would be missing. (not missing on my Powerboost, but not a 2021 either)
The OTA updated the software but failed to update the config this was an update that required a new config yours didn’t flip to the new config it needs toSo nothing I did as that module was updated by Ford and their OTA updates. I only touched the APIM today.
Nope I did not assume that was your intention. Thanks for the clarification.So you guys know if I say 4 that is what enables that particular thing. So you would add it to what you currently have.
So if you have an 8 and add a 4 it would be C
If you want a specific change for your vin let me know. In situations where there are already values existing I can help you get it right
Thanks, I havent worked with Forscan much. I’m going to education myself before making any more changes.So you guys know if I say 4 that is what enables that particular thing. So you would add it to what you currently have.
So if you have an 8 and add a 4 it would be C
If you want a specific change for your vin let me know. In situations where there are already values existing I can help you get it right
Got it, and I suspect there is a problem with FDRS and the GWM config tool.The OTA updated the software but failed to update the config this was an update that required a new config yours didn’t flip to the new config it needs to
I think so. I think ther w is an issue in fdrs this time. I’ll look for a previous version when I get home.Got it, and I suspect there is a problem with FDRS and the GWM config tool.
I do have 32.5.4, 32.5.7 and 33.5.1 I could try. Will let you know.I think so. I think ther w is an issue in fdrs this time. I’ll look for a previous version when I get home.
If you have the previous version try to install it maybe .