ECU module programming guide using FDRS

[Ebrou]

I tried that and it didn't work. The break-in procedure really helped the transmission shift better. Its all done via FDRS (i believe) but I think the vehicle needs to be on a Frame Lift to do the procedure.

What is your F188 Strategy version at after the IPC update?

I was able to get the strategy using Forscan lite.

Sponsored

 

[JEB]

I was able to get the strategy using Forscan lite.

That is the strategy for an 8” cluster, I think. Here is the strategy using FORScan Lite, for a 12” cluster and reflecting the most recent IPC update:

IPC - Instrument Panel Control Module
Bus: HSCAN3
Part number: ML3T-10849-CCM
Calibration level: ML3T-10849-CCM
Strategy : MU5T-10F906-FCA
Odometer: 12409.5 km

Note the fairly radical change in the software format Ford is now using. It’s causing a lot of confusion and disruption. It even threw off the FORScan Team, which initially thought it was a glitch.

 

[Bob_Mac]

Ok everyone, I have some great news about the Mongoose but, you'll have to wait until I complete my analysis. I have a conversation with @Jesse-Infotainment , @iceman77 & @tonesto7 that I need to converse with about my findings.

 

[Ebrou]

That is the strategy for an 8” cluster, I think. Here is the strategy using FORScan Lite, for a 12” cluster and reflecting the most recent IPC update:

IPC - Instrument Panel Control Module
Bus: HSCAN3
Part number: ML3T-10849-CCM
Calibration level: ML3T-10849-CCM
Strategy : MU5T-10F906-FCA
Odometer: 12409.5 km

Note the fairly radical change in the software format Ford is now using. It’s causing a lot of confusion and disruption. It even threw off the FORScan Team, which initially thought it was a glitch.

@JEB, you are correct, as that is for an 8" cluster. I have an XLT 302 High package.

 

[JEB]

@JEB, you are correct, as that is for an 8" cluster. I have an XLT 302 High package.

Got it. In addition, I think the strategy for the most recent IPC update for the 8” is ML3T-14C026-CTF. The second calibration (at node F124) is deleted. Which might be the problem. It is unclear whether there should be a second calibration file at F124 or not after the update. There wasn’t for me or @Bob_Mac, if I’m reading his screenshot above correctly.

 

[Ebrou]

Got it. In addition, I think the strategy for the most recent IPC update for the 8” is ML3T-14C026-CTF. The second calibration (at node F124) is deleted. Which might be the problem. It is unclear whether there should be a second calibration file at F124 or not after the update. There wasn’t for me or @Bob_Mac, if I’m reading his screenshot above correctly.

@JEB, I'll have to re-up my subscription for FDRS and see if there is another IPC update, as I updated to this version about 2 weeks ago. If there is, I'll hold off on the update until the issues with updating are resolved. It took me 6.5 hours over CAN bus to complete the update. That was the first and only module I had updated... geeee, I had to pick the largest update to do first, and now knowing it might not be at the latest strategy, Ugh. LOL

 

[RellIk&5]

@JEB, I'll have to re-up my subscription for FDRS and see if there is another IPC update, as I updated to this version about 2 weeks ago. If there is, I'll hold off on the update until the issues with updating are resolved. It took me 6.5 hours over CAN bus to complete the update. That was the first and only module I had updated... geeee, I had to pick the largest update to do first, and now knowing it might not be at the latest strategy, Ugh. LOL

At least you didn't have yours fail on the initial update and then get stuck with a completed dead center cluster. I, too, had to suffer through a 6+ hour install just to get my cluster back. At this point, I'm sitting and watching to see how things pan out with this Mongoose adapter. And when I reactivate my FDRS subscription, I'm probably going to bite the bullet and buy it for a month. And it seems like mid-March might be a good time to jump back on the updates again as the Wiki mentioned earlier in this thread shows that there is at least one update expected in March and two were supposed to have been released in Feb.

 

[Bob_Mac]

At least you didn't have yours fail on the initial update and then get stuck with a completed dead center cluster. I, too, had to suffer through a 6+ hour install just to get my cluster back. At this point, I'm sitting and watching to see how things pan out with this Mongoose adapter. And when I reactivate my FDRS subscription, I'm probably going to bite the bullet and buy it for a month. And it seems like mid-March might be a good time to jump back on the updates again as the Wiki mentioned earlier in this thread shows that there is at least one update expected in March and two were supposed to have been released in Feb.

I'm still waiting on @iceman77 @Jesse-Infotainment & @tonesto7 to respond to my message but, if you can afford it get the Mongoose.

 

[JEB]

I'm still waiting on @iceman77 @Jesse-Infotainment & @tonesto7 to respond to my message but, if you can afford it get the Mongoose.

Mine arrives today. I’m looking forward to your report.

 

[JEB]

@JEB, I'll have to re-up my subscription for FDRS and see if there is another IPC update, as I updated to this version about 2 weeks ago. If there is, I'll hold off on the update until the issues with updating are resolved. It took me 6.5 hours over CAN bus to complete the update. That was the first and only module I had updated... geeee, I had to pick the largest update to do first, and now knowing it might not be at the latest strategy, Ugh. LOL

I can’t verify the software version for certain, since I don’t have the 8”. I’m going off the screenshot of a part fail/part success installation on an 8” which showed the strategy I noted above successfully loaded into node F188.

 

[jperry5835]

At least you didn't have yours fail on the initial update and then get stuck with a completed dead center cluster. I, too, had to suffer through a 6+ hour install just to get my cluster back. At this point, I'm sitting and watching to see how things pan out with this Mongoose adapter. And when I reactivate my FDRS subscription, I'm probably going to bite the bullet and buy it for a month. And it seems like mid-March might be a good time to jump back on the updates again as the Wiki mentioned earlier in this thread shows that there is at least one update expected in March and two were supposed to have been released in Feb.

I am in the watch and wait stage myself now. I purchased the VXDiag module but just submitted a return for it now. Once I know the march updates are released I will just puchase the Mongoose.

 

[iceman77]

Mine arrives today. I’m looking forward to your report.

When it arrives, can you run a full Network Scan in FDRS for me and DM me your VIN ? I would want to review your AB data, possibly right after Network Scan

 

[JEB]

When it arrives, can you run a full Network Scan in FDRS for me and DM me your VIN ? I would want to review your AB data, possibly right after Network Scan

You got it.

 

[Bob_Mac]

You got it.

I would check the AsBuilt after the first scan then run another scan and check the AsBuilt again. I'm seeing differences so not sure where the issue is each time I scan.

 

[iceman77]

So far what I seen, the Mongoose adapter is producing same type of corruptions as VCX Nano. I don't want to jump into conclusions yet, I will wait for JEB's test results to confirm for sure

Sponsored