Search results

I guess I would be interested depending on cost, haven’t found the correct pin yet

I have the same question… have everything but the correct pin to insert in position 15. Tried one I found posted somewhere, but would not work. Don’t really want to use a fuse tap. Temped it into cigarette lighter plug to get everything working but want to finish it right. I also have a...

IF you use the appropriate gauge wire it should be ok to use speaker wire. Also, make sure it's really copper and not copper clad aluminum which is common now in speaker wiring.

Check out posts 325 and 354, those are both good info...

If you mean solid wire, not stranded, that is not what you want. Go ahead and find some good stranded copper wire.

Yeah, it's already like magic to see the speed limit show up after passing a sign, lol.. So If swap the APIM do I get nav back as well?

Alright!! Success!! Got it calibrated and working! Thank you all so much for the help! One thing I am seeing is when I first enable it says speed recognition not available, but it works once I pass a sign. I'm not sure if that is normal or not. I did see that it is set to use map data +...

Ok, didn't find any changes missed, but do have a question with one... there is a start / stop enabled setting in the IPMA. Is that for ACC or should that be disabled? My truck doesn't have the Start/stop fuel saving stuff. When I try turning that off I get an incompatible configuration DCT...

I didn't change anything else in the ipma, hopefully I wasn't supposed to, but did do all the other changes in the other modules if that's what you are asking. I'll re-do all that this morning and see if there's anything listed in simple mode I can turn on. If not, I'll check wiring with meter...

This is what I did in the IPMA… Is there something else I’m missing? Last column on right is my changes ModuleFeatureCfg_DistAlert (MFCDA) • ModuleFeatureCfg_FcwHUD (MFCFHUD) 706-01-01 *xxx xxxx xx-- MFCDA Enabled to 8 0 to 8 ModuleFeatureCfg_TSR (MFCTSR) •...

I will… done for the night though. The change is one listed in the sheet correct? I did go through the one superfordman posted. Could be I brain farted my pinout though I was meticulous about it.

it's an xlt but no 360 camera. I had to wire it. 4 wires from sensor to plug under dash.

Ok, I couldn't stand it, updated forscan to 2.3.51 and went back out there... and progress! It did write to all modules. Now I still don't see the CCM, so trying to figure that out. I did restart forscan, not loading a profile, but still doesn't see the ccm

Ok, I reset all the modules to my backup files, and cleared all the codes. Module still won't program. I did get all my normal stuff working again so I think I'm gonna call it a night. I did note all my changes on the spreadsheet if anybody wants to see it. Thanks for your help riderryan92...

I tried the non as-built area, same failure. I do see a DTC for the IPMA, actually for a lot of stuff, I'm assuming because of all the changes made that aren't finished but the code for the IPMA is U2300 - Central Configuration -Signal Plausibility Failure

2.3.49, let me see if there is a new one

Yes, the as built. the slower data setting did not help, same result. Should I try the other non-as built area?

I'm about to try not using the faster communication setting, will update in a min

I reset the IPMA, completed successfully, then tried my changes again just on the first line and it errored out like before. I'm using the OBDlink EX, I believe it was recommended.

Ok, tried just one change on a few different lines, no go. the error is service procedure has been interrupted. It appears to load to 100% then goes to the log where that shows up.