So when you retrofitted your nav .. did your dealer have to flash anything? Or it was plug and play?

 

I had to put in a new dash and climate system harness, but I just plugged it all in. No repinning plugs or anything, unless you count the external amp. No reprogramming at all. Everything works as it should.

 

Just compared teh as built data between my car and 2 other 2013s with similar options. Interestingly enough I was closer to one car than the other. The only difference I could see was that one car had a rear camera.

I also only have 1 code different from the other 2 in the PCM.

Is there a way of seeing what each code is for?

 

So you decide what you are gonna do as far as AS BUILT data? Your bringing in this week for PATS relearn right?

 

I'm not wiling to spend alot of cash on this. I'll get PATS and see what else can be done, but I'd like to have as much info as possible.

Do you know what the codes on the 'as built' data mean? What is all this? I know that 7B7 indicates what module we're talking about, but what about the rest of it? For example:

BCE Modules
7B7-01-01 1062 4080 F2
7B7-02-01 0300 0000 C4
7B7-03-01 0100 0000 C3
7B7-04-01 8500 0000 48
7B7-05-01 253A 0C00 2F
7B7-06-01 6400 0000 29
7B7-07-01 1101 0101 DA

 

I work with IBM mainframes. That hex code looks exactly like a "zap". What a zap does is directly update object code without having to recompile the source. So I think Ford is zapping code into the module to alter the logic and programming depending on options installed. For example they could be zapping in the new resistance values for the 2013 cruise buttons.

 

I will try to get to dealer myself one day this week. I think I may have them load 2012 AS Built and see what happens.

 

Is there any way of knowing which codes aer for cruise? I assume it may be the only one code that is different on the PCM, but it could also be the SJB, BCM. And that different code for the restraint module is interesting. Quite a few that are different on the ACM - may explain issue with nav.

 

Wait until after Tuesday. That is when I go in.

 

You would need to know what type of processor the modules are using. Then there should be a table that would show you hex code values of specific instructions. They could also be zapping data and values and not instructions.

 

In other words, I don't have access to this info?

 

Nope. Some engineer at ford who writes code does though.

 

zeroaviation, you got friends in high places?

 

As an FYI, looks like 2013 base cars without the LCD screen have the info buttons on the steering wheel as well.

 

So did anyone get this working?

 

Got some info on the car my cluster came out of.

Manual Transmission. It was a GT/CS so definitely no rear camera. Did not have comfort Package. Did Not have Navigstion. So that could explain my Navigation error. I will compare 2012 with and without Nav and see if AS BUILT is different in cluster.

 

Do our cars even have the air inlet, transmission, cylinder head temperature sensors? Oil should have a reading.

 

Not sure about transmission. Definitely has Air inlet temp and Cylinder head temp. I can read them with SCT. Oil pressure reading only comes up as NORMAL on 13 cluster .. No temp available to cluster.

 

FYI .. been looking at different 2012 VIN AS BUILT data with different options. As far as I an tell .. the CLUSTER code is different for NAV and NON-NAV cars. The cluster code is also different for AUTO vs Manual Transmission cars.

Depending on how things work out with Jim .. I think I should have dealer update the 2013 AS BUILT data in my cluster while they are doing the PATS relearn.

 

Well, if auto vs manual makes a difference, I still need a VIN

Anybody got a VIN for a 2013 that has:

V8
automatic
Sync
Navigation
crash alert
reverse sensing