You will need FORScan or a similar OBDC reader.
A DTC is a Diagnostic Trouble Code. This tells you something is wrong with the module, or the module experienced a communication failure. It can be very simple issue, or something more. Since the module seems to be working normally except for the nav voice issue, I suspect it is a minor error which can most likely be cleared.
Ah FORSan is something I donāt have and unfortunately I donāt know anyone who has it
I do not think this is an issue in this caseā¦
I havent a DTC fault, and ive still got the āspeak and spellā issue.
Thank you Chief. Iāll try 21265. Are you suggesting that I can roll back by just installing the two files you are indicating over my current 22200 application? That would make for a very easy way to check whether the fault is in F11.
That is exactly correct. It will downgrade you to 3.4.21265 with the proper voice file also, and will try to determine if the F11 nav voice is the issue or not.
OK followed the instructions and installed version 3.4.21265. and still have speak and spell navigation, so Iām inclined to think itās an F11 maps issue.
Letās wait and see what happens after the next map update.
Again many thanks to everyone for the info and help, Iām going to leave it alone for a while now.
Your log says different
Let me know the results if you do thisā¦thanks.
I certainly will. Thank you for your help.
I have made a drive as F150Chief has suggested to roll back to 21265 and another with 22200 and F10 maps in order to try and identify where the bug is. I shall report the results this evening when I have had a chance to try them.
Downgrading to 21265 does not correct the bug so I shall try loading 22200 and the F10 map package next.
Edit. Update: This has worked, so the bug is in the F11 map package. If you donāt want the Speak and spell addressing, you will have for the moment to use the earlier maps.
2 Likes
Thank you for the feedback.
I presume then it must be an issue with one of the F11 base map files;
1U5T-14G421-BAJ or 1U5T-14G421-BBJ ??
I presume it would be possible just to try and reinstall these two files again?
@F150Chief - I might have over looked this in the forums, but what do the Options commands in the autoinstall.lst file do;
Delay
Include
Transaction
Autoinstall
Many thanks
I donāt think so. I have loaded the maps twice and had the same result. One thing I did notice was that the voice files seemed to take longer to unpack with f10 compared to F11. I wonder if the larger space required by a later and presumably ābusierā map has required the developers to trim the voice package software in order to save a bit of space.
Autoinstall - Run the contents of the autoinstall.lst file and reboot APIM.
Delay - Used in conjunction with the autoinstall option, does not reboot Sync after installing the AutoInstall package.
Include - For packages that consist of multiple archives and need to be executed in separate sessions with reboots between the sessions.
Transaction - Produces an output file such as used in the interrogator utility.
Rename - Renames the autoinstall.lst file after the installation.
SilentInstall - When installed there will be no display at the top line.
I am curious if you still have autoupdate enabled in the APIM and Sync is automatically trying to backrev the files over OTA. Check that this is turned off if you choose to use the CyanLabs installations. If your vehicle is already eligible for F11 maps on the Ford Owner website, then this will not matter.
Thanks very much for the explanation of the options.
No, I have turned off the autoupdate in APIM / Sync, to make sure nothing else is going on.
But as my vehicle has the MY20 system, it was automatically eligible for the F11 EU maps off the main Ford Owner website, which is the way I installed the SYNC and F11 map update.
Im not sure if this is 22110 related or if its the age of the car. I have a 2017 Fusion running 22110. My car rarely reconnects the USB drive that has all my music on it. It will say device not available, then kick to radio. then I can go to sources and its there. Its kinda annoying im trying to drop apple music so im exploring other options. Its like it times out trying to reconnect the USB drive. any suggestions? Yes I know theres a new version. I havent tried it yet just seeing if this is a known issue with this version or if my USB hub is the culprit.
What kind and size USB drive? USB 2 or 3?
I have a 120GB USB 3.0 or 3.1 which connects consistently every time. I believe it is a Transcend. Format NTFS.
The Sync version is really not a concern with this. If other devices connect consistently, I would consider a new device or try formatting the USB device again. I have seen some of the USB devices using USB power management have issues with Sync and other equipment.
EDIT:
From your post at 2GFusion:
Went up to 3.4.22200 and it looks like the USB music dismount when a phone is connected by BT or running AA is back.
What Iām seeing is that the dismount doesnāt occur if Audio is in the foreground, but does if youāre on the tri screen, running AA, etc.
Is anybody else seeing this?
For me that problem was gone with the 3.4.21265 build.
The bug is also in 3.4.22251.
Iāve reverted back to 3.4.21265, this one doesnāt dismount the USB and also finds/resumes from the USB on start.
I use CarPlay with 3.4.22251 which does not exhibit these issues so I would say another AA induced issue like last time. This is a polling contention issue with AA again, most likely. Sync was adjusted to fix this in a previous release.