ECU module programming guide using FDRS

[rugedraw]

Well that sucks. Don't have license time for that. Is this related to doing Forscan changes? I don't remember this being an issue in my past update sessions.

It has nothing to do with the changes you made. This is relatively new to FDRS.

Try clicking each module in first page where fdrs loads and click the read config data for each one that has the option to do so.

You can also go to the support section of fdrs and try refreshing the files. If the updates don't release, then all you can do is submit the request.

Sponsored

 

[fordtruckman2003]

I saw there is option to read data that says it is for APIM TCU GWM. Might try that later in year I ran out of time on my license. Those updates didn't show up on first day of using FDRS.

 

[JohnTrigger]

I’ve had a few GVMS “errors” on my different Fords. Before my license expires, I’ve submitted them to Ford. Next time I got a license months later, each of them had been ”taken care of”.

 

[digitaltrucker]

Anyone using 45.6.7? I see it but it says not to use it until your region is announced?

 

[fordtruckman2003]

I’ve had a few GVMS “errors” on my different Fords. Before my license expires, I’ve submitted them to Ford. Next time I got a license months later, each of them had been ”taken care of”.

I'm still confused what the issue is that causes it.

 

[JohnTrigger]

I'm still confused what the issue is that causes it.

I’m not completely sure either. Basically some sort of mismatch between Ford servers and your truck on module configuration/software revision having something to do with “as built” data, I think. I suspect when you submit a GVMS request, a human is notified and goes in and sees what’s wrong and (hopefully) resolves the issue, and then any software updates could flow again after that, if there are any for that module.

Something like that is what I speculate. I could be way wrong.

 

[fordtruckman2003]

I’m not completely sure either. Basically some sort of mismatch between Ford servers and your truck on module configuration/software revision having something to do with “as built” data, I think. I suspect when you submit a GVMS request, a human is notified and goes in and sees what’s wrong and (hopefully) resolves the issue, and then any software updates could flow again after that, if there are any for that module.

Something like that is what I speculate. I could be way wrong.

Did you remove any Forscan changes before submitting a request? That is only issue I see is if a human looks at it and denies request when they see changes done.

 

[SomebodyInGNV]

... If the updates don't release, then all you can do is submit the request.

Do you know how long it takes to get a response?

I haven't activated my FDRS license yet and planned to start tomorrow AM. But that would result in review requests being sent at the start of a weekend when I'm unlikely to get a response, but my license clock will be ticking. If turnaround times are short, I'll wait until Monday; if long, it doesn't matter becasue my license will expire first, either way.

Is there any way to determine quickly if there are any blocks that need to be cleared? I'd want to trigger those early so I can get that clock running.

 

[rugedraw]

Do you know how long it takes to get a response?

I haven't activated my FDRS license yet and planned to start tomorrow AM. But that would result in review requests being sent at the start of a weekend when I'm unlikely to get a response, but my license clock will be ticking. If turnaround times are short, I'll wait until Monday; if long, it doesn't matter becasue my license will expire first, either way.

Is there any way to determine quickly if there are any blocks that need to be cleared? I'd want to trigger those early so I can get that clock running.

No way of determining when they will respond. I've seen them get removed in a day or two, and I've seen them linger for weeks and everything in between.

 

[SomebodyInGNV]

No way of determining when they will respond. I've seen them get removed in a day or two, and I've seen them linger for weeks and everything in between.

Thanks. I'll plan for the worst and, assuming my FDRS license will expire before they respond, just subscribe tomorrow. If I get a reply within a couple of days of my license expiring, I'll renew it for 2 days. Otherwise, I'll return the Mongoose cable so you can forward it to the next person on the list.

And that assumes I'll even have an issue that requires engineer intervention.

 

[JohnTrigger]

After you submit the GVMS request, the response status comes back through Ford PTS system. In FDRS you’d only see that it has been cleared.

 

[JohnTrigger]

Did you remove any Forscan changes before submitting a request? That is only issue I see is if a human looks at it and denies request when they see changes done.

I’ve not done any Forscan changes surprisingly, so obviously no concern for me. Sorry no help.

 

[digitaltrucker]

So I went in my Ford Pass and started a chat. They gave me the number to the OTA people. I called them and spoke to Kera who verified for me that Ford has not cut off any updates to any models at this time. So that was not my issue. She then took some time and confirmed as I already knew, that I had numerous updates out there that were "stuck." She said that it was unknown what it would take to un jam these updates and that I should take it to the dealer.

I told her that the dealer wanted $1500 to complete my updates and that if they were stuck, it was something that was a Ford issue because they are responsible for the updates. She agreed but could offer nothing more other than transfer me to Ford Customer Care.

After she briefed Ford Customer Care, they agent came on the phone with me and said "I understand you need financial assistance with a repair, is that correct?'" Too which I replied well yes and no! I explained that my truck has a history of not getting updates and that the "Update Team Member" verified this and that I had current updates that were stuck and that it would need to go to the dealer."

I further explained to her that I recently had my truck at the dealer and that they charged me to do the one update that the dealer is required to do now and that the others would cost $1500.00. I elected not to have them done and would wait for them to come naturally, which they have not.

The Ford CS rep told me that they have no "customer assistance" for this type of assistance. I again told her that this was a Ford issue and not something caused by me, but I was willing to use my Ford ESP and pay the deductible, if they would cover the charges to the dealer. She responded no that I could pay for them and apply for a refund if this issue ever became a recall. I said no!

In closing she said please take this report number, my name and phone number in case there is anything we can do for you should the dealer not be able to help you!

Thanks Ford!

 

[Snakebitten]

Never been a better description of just THE scenario that created and continues to sustain this thread.

Or put another way, it's the exact impetus for the group of F150 owners that collectively took matters into their own hands.

 

[jfalat]

Anyone using 45.6.7? I see it but it says not to use it until your region is announced?

I'm still on 45.5.7 i don't see anything for 45.6.7 yet.

Sponsored