Livnitup

A PMI procedure doesn't change values on it's own (at least that's my understanding). A PMI is done when say the dealership is going to replace one of your modules with a new one. The PMI gathers all the values currently set in the module that's going to be replaced and stores them so that when they remove the old module and install the new one, the PMI can be continued and writes all the values from the old module to the new one. If the old module cannot be read then the PMI process will pull the as-built data for the module from Ford's servers and hold those values until the new module is installed.

So if say you didn't have the value at 39-02 set to enabled and you ran a PMI, that bit would still be disabled.

Firerunner

iTrader: (3)

Does the intrusion sensor module show up on FORScan like DDM or IPC?

Livnitup

No, it's not an addressable module.

Firerunner

iTrader: (3)

Ok...that kills my suggestion/idea then.

Coola1

OK that was my true thoughts on the PMI process. Where is BBG to help shed some light on the subject, It be nice to see what values he has set in his BCM for him to have it working on his XLT. I PMed him yesterday but have not heard. I am surprised that 39-02 was not one you all set. OH did the Forscan folks get back to you with why LIN New Module Initialization fails with a DTC set in. I did look at other values in the BCM and tried many that where questionable but still nothing.

Livnitup

They did but there was nothing in the response that gives us anything else to try. You could try sending them your log files and see if they have any suggestions. Response below...

"Hm... this is odd. LIN New Module Initialization in FORScan should work identical to IDS. So if the procedure fails in FORScan, there is quite high chance it will fail in IDS as well. Of course, there is some chance that we missed something in FORScan, but this procedure was tested quite thoroughly (as it is quite often used fir backup camera calibration). So... it is strange.

You are right that :55 Not configured code leads to calibration function that it must work. So if the procedure fails, it may fail because of other reasons. For example, we got a lot of complatins about abort of this function on rear camera calibration. Initial DTC is B115E:55 Camera Module Not Configured. Users try to run the calibration function and it fails. But re-reading DTCs code after the failed calibration attempt show us new code, B115E:08 Camera Module Bus Signal/Message Failure that means the camera doesn't communicate on LIN bus. Our users realized that some cheap cams purchased on Ebay seem to be not fully compatible with OEM ones. So we recommend to re-read DTCs codes after the abortion, it may give some additional information. Also you may send us logs for analysis."

Edit: if I remember tomorrow I'll set my 39-02 to disabled and see if the motion detection still works

l3rian

Well I really appreciate it.

I feel like a hacker or something sitting in the cab of my truck with a laptop.

I enabled my trailer brake controller, bambi mode, made the radio work when the truck is off, windows up/down with key fob, added the temps to the trans and coolant gauges, and disabled the fake engine noise. I haven't driven it yet, but I may turn that back on. I liked the way it sounded even if it was fake. We'll see. Still want to do the autofold mirrors, but that will have to wait until I have more time to switch the pins.

Now just wondering what else I can do. Y'all have created a monster!

Coola1

The only thing is when the DTC of B109F:55 is present what relates with 39-02 X1XX XXXX XXXX. The log shows on running a LIN new module connect nothing but fail stating that to run a self test to see what DTC is in. I don't have IDS to compare if you have a DTC in will the test fail. I guess might get IDS?, then I guess I really don't need Forscan when its time to pay? I guess I am now beyond Forscan reach (I truly hope not). This part is a true OEM part bought from ours and yours supplier in Minnesota.

Gordy49913

Wait until you go pay for IDS for one year. You'll like Forscan much better I would hope

KWS 2.7

I did not update the firmware but I did run the one link software on my android tablet just check it out. Lots of interesting gauges including a boost gauge that works great. Thought about mounting an old phone somewhere just for the boost gauge.