Post here if you have an active FDRS account and are willing to look up info for others

[Rory]

Just hit me that I forgot to say "thank you!" -- so here's my correction on that bad behavior point. Thank you, @Rory!

You're welcome!

Sponsored

 

[florky]

Can you be more specific about the issue you're experiencing with your 15" Sync screen?

Here's the list of available software updates in FDRS:

question : are these going to be installed via ÔTA one day or the other or are they needed to be updated at the garage ?

Also , I see post about 6.4, 10.1, etc … where should I look to see that version number ? All i can see is « sync4 version 23291_product revision 1049 »
And all I can see in the ford pass app update report is « 23-PU1103-NAT-VCE ». That was made 13th sept.

‘thanks !

 

[jyagnd]

So the dealer did in fact install the Tesla update. My car plug and charged today at a Tesla charger Now they just need to figure out why the car is not doing the over the air updates Since October 23. Possible 12 volt battery? Don’t want to be stuck paying 100s of dollars to get updates done at the dealership with the warranty about to run out.

 

[Mike G]

Still needing help on mine from earlier in the week.

Your list of available updates showing in FDRS:

You do have a recurring DTC that fits the attached bulletin. The remedy is to update the IPMA (and the PSCM would be updated along with it). Getting this IPMA done is the largest chunk of enabling BC 1.3 BTW....

 

[Mike G]

question : are these going to be installed via ÔTA one day or the other or are they needed to be updated at the garage ?

Also , I see post about 6.4, 10.1, etc … where should I look to see that version number ? All i can see is « sync4 version 23291_product revision 1049 »
And all I can see in the ford pass app update report is « 23-PU1103-NAT-VCE ». That was made 13th sept.

‘thanks !

Theoretically possible that they would get installed eventually as OTAs. However, confidence is not high.

OTA version numbering does not correlate to Sync revisions numbering scheme. There used to be a community supported webpage for that, but it doesn't look like it's been updated in a while.

 

[florky]

Theoretically possible that they would get installed eventually as OTAs. However, confidence is not high.

OTA version numbering does not correlate to Sync revisions numbering scheme. There used to be a community supported webpage for that, but it doesn't look like it's been updated in a while.

thanks a ton for all your help Mike. Will go and see my dealer soon

 

[PianoDan0]

Have you tried a PMI?

So I tried PMI and it failed.

Procedure Unsuccessful -
com.ford.otx.command.exception.FdrsRuntimeException: java.lang.RuntimeException: java.lang.IndexOutOfBoundsException: Index: 2, Size: 1

 

[rugedraw]

Still needing help on mine from earlier in the week.

If you're looking for modules pending updates, your list is below:

 

[Mike G]

So I tried PMI and it failed.

Procedure Unsuccessful -
com.ford.otx.command.exception.FdrsRuntimeException: java.lang.RuntimeException: java.lang.IndexOutOfBoundsException: Index: 2, Size: 1

That looks like a FDRS program error.

 

[PianoDan0]

That looks like a FDRS program error.

I reinstalled the newest version and same error.

I guess I'll just ignore it.

 

[jyagnd]

I just did a master reset. “Not completed” is gone. Woo hoo !! Who needs friggin dealers.

 

[TallNate]

Your list of available updates showing in FDRS:

You do have a recurring DTC that fits the attached bulletin. The remedy is to update the IPMA (and the PSCM would be updated along with it). Getting this IPMA done is the largest chunk of enabling BC 1.3 BTW....

Thank you so much. I always want the dealer service to do all software updates, but here in Colorado Springs they have said stuff like “we have to have a symptom or diagnosis to work on these” and now probably want to get paid for stinkin software updates because I’m past 3 years ?

if you all have recommendations on how to get them to do these, I would love to ask the “right way”.

 

[kennelh]

Thank you so much. I always want the dealer service to do all software updates, but here in Colorado Springs they have said stuff like “we have to have a symptom or diagnosis to work on these” and now probably want to get paid for stinkin software updates because I’m past 3 years ?

if you all have recommendations on how to get them to do these, I would love to ask the “right way”.

I hate to say this, but the best way to get all the updates done is

1. buy a Mongoose, get a Windows laptop, purchase a FDRS license, and do them yourself
2. contact @rugedraw about "borrowing" all the equipment, and do them yourself
3. find a nearby forum member who has the equipment, and spend an afternoon with them

I'll volunteer to help you out if you're ever in the Sacramento area. Just bring the beer and nacho chips.

 

[TallNate]

I hate to say this, but the best way to get all the updates done is

1. buy a Mongoose, get a Windows laptop, purchase a FDRS license, and do them yourself
2. contact @rugedraw about "borrowing" all the equipment, and do them yourself
3. find a nearby forum member who has the equipment, and spend an afternoon with them

I'll volunteer to help you out if you're ever in the Sacramento area. Just bring the beer and nacho chips.

Yikes. Thanks for the offer but it doesn’t road trip to CA…

 

[Space_Pony]

There is no incorrect time to schedule updates. Ford's default time is 0100 (1 AM) but that doesn't mean anything. I set mine to check/update 0900 every day. I don't have a set driving (commute) schedule. Early in the morning is when your 12V battery will be at its lowest state of charge. So I set mine to 0900 in the event that I'm out driving and the check will then happen while the 12V battery is fully charged back up. If I do download an update on that drive, I just tell it to update while I'm in the store shopping or something.

Will a car that is being charged interfere with an update? I left mine at 01:00 because I plug it in when I get home from work and my 48 amp charger has it fully charged before that time.

Sponsored