Sync 3 black screen, radio still plays

I have a 2013 Escape Titanium, it originally came with my ford touch but a few months ago i did the sync 3 upgrade kit. The kit came with new new screen, APIM, USB hubs and ran sync 3.4. It has been working fine no issues.
VIN: 1FMCU9J98DUB86724

The problem now is that the screen won’t turn on, not even the backlighting. it still seems to work in the background as i can hear the stereo, my phone connects, voice commands work etc. but the screen it self does not come on anymore. I tried plugging in my old my ford touch unit and it works just fine.

BACKGROUND

Today I was messing around on forscan in the BCM Central Configuration (Main) my first time going into the bcm since i upgraded the sync unit.
I changed a few settings including, fog lights staying on with hi beams and global windows.

A few things to note, the calibration file loaded from the boot loader was from when i had the my ford touch unit.
Second, a few times when i was writing to the BCM it failed.

Is it possible the calibration file was for the older my ford touch unit and corrupted the sync 3.4 unit i have?

I’m not sure what to do at this point, so far i tried undoing the changes i made in the bcm as i also tried a reset of the screen, checked all the fuses and disconnected the battery for 30 mins well as doing lots of research but im not entirely sure what to do. Some help would be greatly appreciated.


SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: Retrofit

Old SYNC Version: 3.4

New SYNC Version: 3.4

Do you have a error message, if so what is it?
U3000: General Checksum Failure
U0162: lost communication with navigation display module
U2101: control module configuration incompatible

Update Method: Official Ford

Post your asbuilt page for the APIM via Forscan.
Do you have an DTC?.

U3000: General Checksum Failure
U0162: lost communication with navigation display module
U2101: control module configuration incompatible

Thanks for Replying! Here is the current asbuiilt for the apim. not sure if it’s right since i’m getting checksum failure.

Thanks.
I’ve re-read your original post and I have to say I’ve got it wrong.
So, you performed your upgrade an amount of time ago and it was working fine until you started changing other stuff in other modules and THEN it failed. But your old screen works…

That does it deed seem to be maybe related to calibration stuff, but I do not know about those. Let see what others have to say…

But checking your asbuilt, the value for “DE02/7D0-03-01 xxxx-**xx-xxxx” does not seem correct. You can check for those values here → https://cyanlabs.net/asbuilt-db/sync3-apim/?search=Visual%2520Design%2520Variants%2520(VDV)%2520Sync%2520Versions%25203.0%2520thru%25203.4#database

Value for “DE01/7D0-02-01 xxxx-**xx-xxxx” seems ok.

Both categories can be found under the “Theme” section in the asbuilt database.

It’s worth checking both values are within range, but I’m not sure that would prevent the boot screen from appearing (which seems to be the case).

Here’s a AB for a 2014 Escape TI Sync 3.4 that my daughter used for 2 years with no problems.
2014 Escape Ti Sync3 APIM.abt (495 Bytes)

Hi, Thank you both for replying.
SandMan: Yes I did the upgrade back in September, and it new sync unit with 3.4 has worked with no issues up until now, In terms of the theme values I just tried all the possible themes and still no screen sadly.

Warlock12118: Thank you for that; I loaded the as built you provided but still my screen did not come on.

I should note, I am still getting the checksum error code, as well as the apim still seems to function even after all these changes but sadly not the screen.

Also is it possible that something was changed by mistake in the body control (main) that would be the issue?

I didn’t think correcting the values for the theme in the asbuilt would fix it (since you had no splash screen), but it was worth the shot.

Which module is giving you the checksum error?.

The APIM is giving the checksum error.
These are the errors in the APIM i am getting:

U3000: General Checksum Failure
U0162: lost communication with navigation display module
U2101: control module configuration incompatible

I am also getting a code from DSP: U0155 lost communication with instrument panel cluster control, module a.

These are the codes that exist after doing a clear.

Also now that i think of it, the last thing i did was mess around in the ipc before i noticed the screen being black.

I also just went into the live data section and got this.
It seems it’s not detecting the touch screen?

Reading back through this I wondering if this is actually a BCM issue.
Try reverting the BCM back to factory using the AB file from Ford.

Thats a good Idea, i’ll try that and report back how it goes.

Now i’ve got a new issue. My BCM is only showing 3 blocks. There used to be 14 i believe.

1 Like

Did you flash the BCM to another firmware?
That’s the only way the number of blocks would drop unless you’re not reading the secondary BCM.
It should go 726-01-01 through 726-01-10 / 726-02-01 / 726-03-01 / 726-04-01 / 726-05-01

I don’t believe I did. the odd thing is that with an older version of forscan i was able to see all the blocks in the bcm as built. but since i updated to the latest version the blocks dropped to 3. also since i updated forscan tells me my connected is not recommended for use with my car. Its an ELM 327.

Well… there’s your problem, I think…

So I just downgraded my Forscan since that is why i could not read all the modules. After than i was able to get access to all the bcm blocks. i reverted the asbuilt to factory but alas the screen is still black. Also i apologize for asking questions for some pretty basic stuff.

Are you resetting the modules once you rewrite the asbuilts ?

No. is that something that needs to be done?

No. Is that something that needs to be done?

I’m no specialist, but the few docs I’ve read about that, they mention resetting the module to pick the new configuration up… But do not take my word for it…

I See, i’ll try that tomorrow. If that does not work I can’t really think of anything else to get it working. It’s just so bizarre. It almost seems like the screen just died or failed coincidentally at the same time i was using forscan originally. In my head i still think it’s something software since everything still works in the background, but i can’t really think of anything else to try. Thanks