Forums

It is located on the left side in the trunk. You just need to repin the power connection, because Sony wires the power differently. Sony power pin + 5,6 to 8,16 Bang & Olufsen  Sony -negative cables  from 13,14 to 5,13 Bang & Olufsen  parts :  KR3T-18T806-CJ B&O 900W Flash firmware 

@marekrbk thanks for you prompt reply.   I got out my black&white hard copy and its virtually identical and can most certainly be used for the US version - I'll definitely be using this colour copy whenever I have the need - thanks.     .

I will try but I only have access to the schemes in Europe. It would be a good idea to check the connectors and their pinout in your vehicle and compare them; if the wiring matches, the only difference is the coding—meaning the As-Built data will differ, but the electrical setup will be the same. The Edge is manufactured in Canada, even for the European market.

Welcome and thank you for that.   Do you think it's much the same as the US 2017? If not, is there any chance you could post the wiring schematics for the US 2017?

Need canbox https://canbox.ovh/

https://mega.nz/file/GQdUwbyR#i2svtnMxx-E7DyLZ3a8g2ku-lTpcbupLIfpbH1UO6kM

DSM ****** need with ucds enable parameter Column Tilt capable and tele capable- Present Sccm *****Electric steering wheel Telescope + Tilt -Enabled Column coding must be started via forscan in the menu PATS Programming

https://mega.nz/file/iFlQgboB#1RjK20EqBEFdlMWAWtpjcgEFTiOiggZQ0Zs17icrn6o

1. When I got the car new AA was not out yet for the car, later it OTA'd to 3.0 and I had AA. Then I eventually got a new phone and AA would not work with that phone and V3.0, I had read that it was the Sync version and new phones rejected what ford was doing for AA deployment (idk what truth there is to that but the fact is it immediately stopped working) So I used SYNCUpter to go to 3.4 and then my phone worked fine and has worked no matter the phone since, I just had the usb notice to clear each time Sync booted, that notice is only for carplay basically. I have the newer hub in hand that if you wanted carplay in general on 3.0 due to the apple license stuff you have to install regardless. I just never did it as I saw no need using only AA. I will put it in this time since I have it anyways.   2. Thank you for this clarification.   3. I looked around and found local used ones (apim and screen) but then I would have to dig out forscan and program the thing my self. I found china ones or oem refurb know knows but they are the right looking/# part match and will program it for me with my VIN and have 4GB ram vs 2GB (newer vehicle apim design?) for a smoother experience on 3.4, for $200 I figured I would give that a shot then search local if that doesn't pan out. I have the service manual for my VIN I got from ford when I bought the car and have no fear to take out the center to swap/install it. The china special is from a vendor on amazon so regardless its returnable/refundable which is more then I can say for some ebay deals I saw. I am still slightly concerned with the screen being bad but if the apim truly just croaked it self then at this point I need it regardless to even get the rear camera recall done as they need Sync functional to even swap that part they said. My flicker was not a normal symptom of a bad apim from what I can tell but if the apim was so bad it died then perhaps the screen is fine after all.   4. Is the apim what stores the configs for like walking around the running car and the horn honking etc? I think not as with a black screen my gauge cluster right info screen still has the climate screen I coded in and just says 0 as it can't see the apim currently. I assume this must be configs in another module?   Thank you for your advice so far.   EDIT: so I thought about what you said above and it made more sense to be to dive deeper and uh yeah I think I have a bad screen and this is what actually killed the apim. fords software did not like what it saw and reformatted it in a way it was no longer able to.

Picking through the edit and added posts. need v3.4 to use CarPlay/Android Auto? no, you need 2.2 or higher, 3.0 for the early hardware is the highest it can go natively (without using alternate method to install), and it supports wired CarPlay/Android Auto AsBuilt data is 3.4 not 3.0 not really related. AsBuilt is configuration, not software revision. I guess the selection for the boot screen slightly changes between 3.0 and 3.4. didn't install updated media/usb hub I would find that error prompt every start up annoying, and having the part and a small effort to replace? Are you really gonna tear into the center console and center stack to replace the APIM and screen? I am not sure that side loading 3.4 onto the APIM would cause issues when the demand self test was ran by the dealer, I suspect it wouldn't.