Here’s mine after applying the update released on Sunday.Here’s mine.
@turbopilotAs an FDRS newbie I am totally confused about what these software update P/N's mean and what should stand with regard to the recall update.
Yesterday I updated to the new BB TRM module firmware. ML3T-19J297-BB is what showed up in FDRS after I applied the new update and did a new network scan.
After the update I went to the Ford widget and did a refresh and this is what the widget says. F188 is showing up as ML3T-19J297-BA, while F113 is showing up as MU5T-19J294-DH.
So is F113 the target for the recall update?
Yes. Several times. The last refreshed time stamp for the for the widget was this morning. Update applied 24 hours ago.
No. F188 is ordinarily the target, particularly for modules that don’t have calibration nodes, like the TRM. Although it is possible for a hardware version (e.g., F113) to change with an update, it would be very unusual. That’s why when you said you saw more than one node update with the latest TRM release, I was intrigued. Your data, however, shows that this was a very ordinary update with software that has been out there for awhile and there was nothing particularly unusual about it. False alarm.As an FDRS newbie I am totally confused about what these software update P/N's mean and what should stand with regard to the recall update.
Yesterday I updated to the new BB TRM module firmware. ML3T-19J297-BB is what showed up in FDRS after I applied the new update and did a new network scan.
After the update I went to the Ford widget and did a refresh and this is what the widget says. F188 is showing up as ML3T-19J297-BA, while F113 is showing up as MU5T-19J294-DH.
So is F113 the target for the recall update?
The difference is @tonesto7 ’s widget reads the as-built data from Motorcraft Service and FDRS reports directly from the module. They should be the same, but for some reason the former hasn’t updated yet.
One last thing. Which refresh are you talking about? There is the general refresh for the widget data. There is also a separate refresh/download for the module data. Did you both? If you were not prompted for and did not reenter the three character captcha code, then you did not update the module data in the widget and that might be the problem.
Yeah. That’s what I experienced this morning as well. Did an update, rescanned, then downloaded the as-built. Changes showed up immediately. Which kinda surprised me. That’s why it took me a few minutes to figure out why your widget and the FDRS data for @turbopilot differed. There should be no difference.In my testing, if a network scan is run in FRDS the new data is present in the Asbuilt almost instantly. I just tested after updating my TRM module about 15 minutes ago.
It's one of the few things Ford has that updates in a reasonable time frame
Done today -> TCU, APIM, GWM, TRM, GSM. A bunch of PMIs. Then this module update repair was the last thing done:
Showing as remaining is only a GSM (likely the one that gets stuck often...)
That “procedure unsuccessful” notation is actually good news. It means that the tech did not have to use the fastboot update in the TSB to get past a stuck 1.7.1 OTA. He was able to go directly to the modules and update them.
