EFIDynoTuning Forum

Michael, this had been bugging me for many years, maybe you can explain why! Please keep it a simple as possible, I'm no programmer. lol

The Scenario: installing a larger maf housing onto a perfectly tuned engine, and updating the new maf transfer data only in the tune for the larger housing, the load gets skewed. And we all know higher load means less timing, more fuel, etc.

What I'm trying to understand is WHY this happens. (I have observed this on both my 91 and my 13 coyote). My gut feeling tells me that the eec does infact use Mafv or Maf period to calculate load in addition to the measured air.

Ps:I'm not looking for free advice here on how to 'properly install a larger maf'. Just trying to understand what the eec is doing in the background.

Bonus question: why does my 13 coyote complain about a non-existent O2 sensor 3, bank 4? This does not throw the light, I just see this failure under "test results" in Torque.

If your tps is 'unmolested', it should be fine. Yes, the holes had to be hogged to make it adjustable.
How does it run without the chip? And with a chip and a stock file?

Stock MAF and injectors?

Idle is the most difficult to dial in, you will spend a lot of time trying settings. (I NEVER had it learn its way 'out of surging'.)

If you have upgraded injectors and MAF, work on getting fuel dialed in first. (maf transfer, injector slopes, inj breakpoint, inj offset vs volts, NOT the tables for startup)
Set throttle stop an additional 1 1/2 turns after the stop screw contacts the throttle plate.

If you adjusted TPS volts, make sure its not too high. This is an old myth that this needed adjustment. If you are really close to the open throttle break point, it can cause high idle after the car warms up. Suggest setting TRLOAD=0, it may help idle transition when coming to a stop.

WIthout a log of the stumble, I don't have a guess as to what it could be.

Control pack strategy is the easiest way for no PATS.

I was hoping Decipha jumped in this thread!

At one point I was hoping to fit a 13 cluster. I got one, wired it up temporarily. And the odometer reading was received from the 13 instrument cluster. So I'm confused as to why you said the BCM/SJB comms the odometer.

In the current config, PCM reports 0 miles. This is the only thing I would like to get working.

I have used ALL flavors of ELM, bluetooth, WIFI, USB, Forscan usually prompts some crap about the adapter. lol
I got a Vlinker usb, it is capable of FEPS flashing and has auto HS/MS can switching.
https://www.ebay.com/itm/175955913754?i ... BMjPqzg5pk

Got a spare PCM, I'm going to do some bench testing with.
Yea, I got asbuilt files for both 06 and 13 mustangs. I will post what I find.

I am hoping protocols did not change too much. As the cluster/gauges work, so atleast those broadcast messages from the PCM are the same. Gen 2 coyote swaps and later, things definitely changed. Not sure how folks get the speedo working with Gen 2 and later PCMs.

Thanks for the docs. I think the info I'm looking for is Ford proprietary. (module addressing on the network)

From testing/observation:
I can communicate with all modules using Forscan, but it depends on which profile I chose to connect with. If I scan without using a profile, Forscan does not find the ABS and RCM modules with the coyote PCM. If I use the original 4.0 profile, the ABS&RCM are found. What's interesting is, the SJB is always found.

My theory is: The PCM provides the 'ip address' to Forscan. (static network, no DHCP, to put it into networking terms) Forscan only looks where the PCM told it to look. I think I need to update the module addresses in the coyote PCM. Seems like I have some more 'testing' in my future. lol

Using a 2013 Mustang GT pcm, in a 2006 v6 chassis.

Yea, if protocols changed, than this is not getting 'checked off' lol. I would really just like to see the odometer reading when scanning the PCM. I built it fully smog compliant, just in case I go over 5k/year. For any diagnostics, I can just use the saved profile.

Thank you Boosted!

Gen 1 coyote in an 06 S197.
Using Forscan to communicate with modules.
Harness repinned for the copperhead PCM. Car drives great. The 06 gauge cluster works, speedo, tack, temp, oil pressure, CEL..... all work.

I lost access via Forscan to the RCM, ABS, instrument cluster after the swap. Now, here is the strange part, If I use a stored Forscan profile from before the swap, I can access the cluster, abs and rcm modules with Forscan.

I am good with pc networking, but I can't seem to figure this out! lol The modules clearly get data over the can From the PCM, but the PCM is not getting data from the modules. Like the odometer reading from the cluster, PCM reports zero miles.

Is this a network address issue?