dmhines

I found a 2013 equipped exactly like my 2012 and used prior links to download AS BUILT data. PCM code is identical. Cluster code is Identical. there are maybe five or six hex strings that are different in all the other modules including the ACM. So it must be a module besides the PCM controlling cruise and track apps


Does anyone have a list of modules?

I found 727 is ACM. 730 is cluster according to zeroaviation

Need to find. 7B7. 7D0. 720 726 737 760

dmhines

Found this online.

720 ICM
7D0 APIM
726 GEM
727 ACM
737 RCM
760 ABS

Cluster AS BUILT data is quite a bit different than my 2012 if 720 is the ICM.

zeroaviation

Agreed. I was mis-informed.

Attached is the correct list of Modules and their addresses.

jim010

I trace the signal from the cruise switches to the PCM and SJB.

From the PCM, a signal goes toElectronic throttle control (ETC), accelerator pedal position sensor (APP), brake pedal position switch (BPP), and body control module B.

Hope this helps.

dmhines

Just did the AS BUILT Compare.

My car would need the following AS BUILT updates:

Body Control Module - 1 line different
Accessory Protocol Interface Module - 1 line different.
Instrument Panel Cluster - 2 lines different
Smart Junction Box - 2 lines Different
Audio Control Module - 4 lines different
Restraints Control Module - 3 lines different


Thats a lot of updates and who knows if the changes are compatible with 2012 modules.

Also .. my car has Security Package and Comfort Package.

In 2013 the Security package includes rear sensors which I don't have. In 2013 the Comfort Package includes Heated Mirrors which I don't have. So those two options would be enabled and who knows if it would cause issues or not.

So it looks like the tech has quite a bit of programming to do and if it causes issues will have to set back to 2012 AS BUILT.

Or just Flash the 2013 Cluster to 2012 As Built and hope the LCD stays working.

Good luck Jim ... can't want until you get your car in front of the tech!

Appreciate you being the Guinea Pig!

jim010

Yay ...

jim010

Where are you getting this info from, so I can pull up my car?

dmhines

Go to this link and then plug in YOUR 2012 VIN and then the VIN of the 2013 that is optioned like yours. You can then compare each modules AS BUILT data to see what is different and will need to be changed by the Ford Tech.

The first 3 numbers in the module are shown in the chart that zero posted.

http://www.vrep.fordtechservice.deal...R_Quickstart=#

Greg2011

Since the cruise control resistor voltages are different between 2012 and 2013, the PCM programming cannot be identical. You would need to pop the hood and see if the computer code is labeled the same or not.

Zeroaviation is the only one here with any indepth knowledge of the inner workings of the PCM. The attached link will show you where to look for it.

http://www.americanmuscle.com/computercode.html

dmhines

Greg .. PCM = Powertrain Control Module ... that is engine management and it is indeed the same from 2012 to 2013.

My guess is either the SJB and/or the BCM working together deal with the different resistance.

Zeroaviation asked a few pages back for my PCM Strategy code and I posted it. FPDN1AT

dmhines

check this out .. looks like it will program all the modules we need ... But doesn't seem to be able to do a PATS RELEARN.

http://www.obdgo.com/Mini-VCM-Vehicl...FQLpnAodaA0AYQ

zeroaviation

For the record, my specialty is firewall forward, i'm doing my best to get information for interior objects.

I think we need to gather some facts.

Here are the problems we are facing.

1. Certain gauges are not working. This is because we are missing data on the High speed CAN. (100%)
2. Track Apps are not working. - I think were a little all over the place here.
2a. PATS - Cluster not initializing with Key On.
2c. BCE not initializing the cluster properly at KOER. (my vote)
3. Cruise control illumination not working. - Personal opinion is when the PCM seems Cruise on, it sends out a CAN signal the new cluster will not recognize.
4. Message center switch is handled by the IPC (80% sure).
5. Cruise control switch is handled by the PCM (100%)

How can we test these theories?
1. Disable PATS - BamaTunes should be able to do this. (See attached, I'm fairly certain that's it.) I would try talking to John Lund, maybe get another tune from another vendor.
2. Update BCE with asbuilt for cluster. I'm not feeling to confident here, if the firmware on the BCE was from 2013, then it would work and be backwards compatible. I dont know if Dealer techs can update these with a VCM.
3. Once i get my hands on a cluster, I can inject can traffic from a 2014 and find out what enables the track apps. (Just like controlling the radio in a previous vid).
4. If someone wants to help bench with their existing cluster, I can build a CAN translator, ship it to you, and we could work remote on trying to activate the cluster and track apps.


Thoughts? Concerns? I hope you guys are not ready to give up...

zeroaviation

Thats a VCM knockoff. I've heard mixed results, come people have excellent luck. Some people brick their cars

The ones that have had the most luck is using the following.
http://www.ecutool.com/GNA600VCM-2-in-1_9073.html

Its almost worth a try, the worst that could happen is have to tow your car in to dealer.

-Matt

dmhines

Matt ... I had Bama send me a tune with the PATS DISABLE switch checked. It didn't work. I called SCT about it and they told me they have not been able to get the PATS disable working in the newer Mustangs. There is another thread someplace of a guy installing a GT500 cluster in his car. He also got a tune with PATS disabled and it did not work for him either.

I found that particular programmer cheaper and it says supports up to 2012 Ford Cars. Also mentions PATS but still not sure it can do a PATS RELEARN

http://www.ecutool.com/Ford-VCM-IDS-...lity_9536.html

jim010

Finished wiring up the switch from the clock spring to the cluster. I just tapped into the wires, thereby keeping the lower switches active.

dmhines, it seems I can't have both the steering wheel switches and the lower switches, as the message center keeps resetting and doing ither weird things. Did you find this?

Also, I cannot get my nav to switch back to metric. I hit the button for metric on the nav, but it will not switch. Can you check to see if this is the same issue with you?

I'm starting to think that I should cut my losses as 1 too many things are not working right for me.

jim010

Naver mind. I disconnected the lower switches, and then I changed the units from English to metric on the cluster. This automatically changed teh units to metric on the nav as well. There is obviously some comminicating going on between the nav and cluster via the PCM as evidenced by this and the nav error message.

dmhines

Jim .. I moved the wires back to my 2012 switches so I don't have the 2013 switches hooked up right now.

As far as Metric .. you have the 2012 cluster installed and still having issues?


I'm thinking the best thing to do for now is put the 2012 AS BUILT into the 2013 cluster .. if we lose the LCD Display (I don't think we will) ... then we call it quits. If the LCD still works then we can figure out what we want to do with the control switches .. either use the 2012 switches like in my second video or tastefully integrate the 2013 switches someplace into the dash.

Feel free to go out and do the AS BUILT data in every module .. but I'm think that is much less likely to work than just doing the cluster. I think most people including myself don't really care about track-apps .. its a short lived novelty.

jim010

Agreed. I don't car if I have it.

No, I was tinkering with the 2013. When 2012 is back in, all is normal except cruise (because I left the 2013 switches in.)

I haven't given up on using the 2013 switches in the wheel yet, though.

I will do PATS for sure, and then see what he tech and I can play around with. I will check the links you posted.

Sounded like a great idea until you mentioned the towing part ...

dmhines

I have not been able to determine what my Cluster came out of. Perhaps it came out of a NON-NAV car so that would explain my navigation errors. So I have two options when I get my PATS reset.

1) Load 2012 AS BUILT in Cluster only and see if my NAV errors go away and LCD stays.
2) Load 2013 AS BUILT from a VIN with NAV in the cluster only and see if my NAV errors go away.

jim010

My cluster came out of a car that did not have nav, so you could be right. Although, I have no issues with my nav and my old cluster (I retrofitted my nav).