Free Sync 3 Navigation Map Updates (NA 1 18)

[Dan Keil]

My map update is a 1 19. My sync is 3.3 right now. I have everything loaded on a thumb drive and the system is not showing anything

Sponsored

 

[CoastieN70]

My map update is a 1 19. My sync is 3.3 right now. I have everything loaded on a thumb drive and the system is not showing anything

I went through this too. You need to go to Ford Owners dot com and download and install SYNC 3.4 before Maps 1 19 will load, show, work...

 

[Richard Conley]

Tried waze, prefer Google Maps. Hoping Apple Maps is going to be update as they claim in the next rrelease!

Interested - big Apple fan for phones and stock (wish I had more). But like I say have a Waze history so lot of fave places are already available. So it would be nice if locations transferred automatically like contacts. Trying to be Google free, switched to Edge but not sure it matter much.

 

[Dan Keil]

I went through this too. You need to go to Ford Owners dot com and download and install SYNC 3.4 before Maps 1 19 will load, show, work...

I will try to get my sync updated when I get time

 

[Geoff]

I went through this too. You need to go to Ford Owners dot com and download and install SYNC 3.4 before Maps 1 19 will load, show, work...

No, that's not quite right. You can load the map under 3.3 but 3.3 will not update the map version number due to a bug. But you can verify that Map 119 is loaded by looking in the diagnostic menu.

That version number bug has been fixed in Sync 3.4 so it'll show the correct version number if you load Map 119 under 3.4.

Since the version number bug exists in 3.3 it does not get updated when the map is updated and because 3.4 looks at the 3.3 version number it cannot 'know' if a newer map is loaded so it'll show an incorrect version number under that circumstance (but again the map version can be verified in the IVSU Diagnostic screen).

As a point of reference, I've loaded map 119 under 3.3 and then again under 3.4. My recommendation is to update sync to 3.4 then load map 119. But if you want a newer map and don't want to gamble on losing the climate controls 119 works fine under 3.3.

 

[CoastieN70]

No, that's not quite right. You can load the map under 3.3 but 3.3 will not update the map version number due to a bug. But you can verify that Map 119 is loaded by looking in the diagnostic menu.

That version number bug has been fixed in Sync 3.4 so it'll show the correct version number if you load Map 119 under 3.4.

Since the version number bug exists in 3.3 it does not get updated when the map is updated and because 3.4 looks at the 3.3 version number it cannot 'know' if a newer map is loaded so it'll show an incorrect version number under that circumstance (but again the map version can be verified in the IVSU Diagnostic screen).

As a point of reference, I've loaded map 119 under 3.3 and then again under 3.4. My recommendation is to update sync to 3.4 then load map 119. But if you want a newer map and don't want to gamble on losing the climate controls 119 works fine under 3.3.

Interesting BUT I loaded SYNC 3.4 via the Ford site (not the hack so many have used) and did not loose Climate Control or anything else from V3.3 except the sluggishness that drove me crazy from day 1 of my Ranger experience. So I say if you haven't upgraded to SYNC V3.4 do so via the Authorized upgrade from Ford...

 

[VAMike]

Interesting BUT I loaded SYNC 3.4 via the Ford site (not the hack so many have used) and did not loose Climate Control or anything else from V3.3 except the sluggishness that drove me crazy from day 1 of my Ranger experience. So I say if you haven't upgraded to SYNC V3.4 do so via the Authorized upgrade from Ford...

I did that, it was a horrible process, and I ended up without climate control. AFAICT there's no way to predict whether the Ford update will kill your climate screen.

 

[Geoff]

Interesting BUT I loaded SYNC 3.4 via the Ford site (not the hack so many have used) and did not loose Climate Control or anything else from V3.3 except the sluggishness that drove me crazy from day 1 of my Ranger experience. So I say if you haven't upgraded to SYNC V3.4 do so via the Authorized upgrade from Ford...

I also upgraded to 3.4 using the official Ford release (which is no longer available due to web site maintenance) but there are those who have used the official Ford updater and lost Climate controls -

Some subset has a bit set in the as built for Climate Off. There was a bug in v3.3 that it ignored this. Now that v3.4 is reading it correctly, the screen is being removed though voice commands remain (controlled via a different bit for Auto climate type). The only way to know if you'll be impacted is to check your as built data for the specific byte. If it's 0x80 you'll lose the Climate UI, if it's 0x00 you'll keep it.

 

[UofMEngineer]

I did that, it was a horrible process, and I ended up without climate control. AFAICT there's no way to predict whether the Ford update will kill your climate screen.

You need to check your as built to know if you'll lose it or not with the update.

 

[CoastieN70]

I did that, it was a horrible process, and I ended up without climate control. AFAICT there's no way to predict whether the Ford update will kill your climate screen.

Generally if something like this is going to screw things up, I am the one that will be most affected by it. I guess I got lucky this time...

 

[RedlandRanger]

You need to check your as built to know if you'll lose it or not with the update.

Just curious - what specific value are we looking for? I saw your reference to one bit being the culprit, but I didn't see what key it was stored in.

 

[VAMike]

You need to check your as built to know if you'll lose it or not with the update.

Grubbing around in byte code using an unsupported third party tool doesn't count, IMO. So while the problem is deterministic, implying that there is a state that can be learned, it's still reasonable to classify it as unpredictable for a typical customer.

 

[UofMEngineer]

Just curious - what specific value are we looking for? I saw your reference to one bit being the culprit, but I didn't see what key it was stored in.

Go here: https://www.motorcraftservice.com/asbuilt

Run your VIN, check 7D0-04-01 to see if it is: xxxx xx8x xxxx. If so, you'll lose Climate at the moment when you update.

 

[RedlandRanger]

Go here: https://www.motorcraftservice.com/asbuilt

Run your VIN, check 7D0-04-01 to see if it is: xxxx xx8x xxxx. If so, you'll lose Climate at the moment when you update.

Perfect! Thank you. That was the piece of data I was missing. And yes, I have an 8 there, so I would lose Climate option when doing the update.

Do you know if that is being addressed? I did the "hack" method of upgrading to 3.4, but I kind of wanted to do the "official" build. I guess I could always reset my climate control like I did earlier.

 

[RedlandRanger]

Grubbing around in byte code using an unsupported third party tool doesn't count, IMO. So while the problem is deterministic, implying that there is a state that can be learned, it's still reasonable to classify it as unpredictable for a typical customer.

Actually you don't need to use an "unsupported third party tool" - you can use the Ford as built data:

https://www.motorcraftservice.com/asbuilt

I won't say that is simple to do for a non technical person, but at least it is using official Ford tools.

Sponsored