EFIDynoTuning Forum

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?

Depending on the vehicle the PCM is from, Those modules are most likely on a different network. Network protocols changed drastically between the two generations. Could also be that the old PCM was the terminating module in the network, I can't remember off the top of my head. Get the make and model vehicle from the swap and if the car it is going into was v6 or v8 originally and I can see if I can find any info on the network protocols for the modules.

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!

Gateway Module

The IPC is the gateway module, translating messages on the HS-CAN to MS-CAN and vice versa. This allows a message to be distributed throughout both networks.

The IPC is the only module on this vehicle that has this ability.

From the 2013 Mustang shop manual.
I attached a pdf of the section from the 2013 manual. I will look for the other one and see if I can find it.

Here is the section for the 2006, Hopefully this will help with the diagnosis. But I am sure that the modules most likely will not communicate with each other, if they do the data most likely will be incorrect due to protocol changes and programming differences.

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

The PCM does provide the address to all the modules on the network, but the protocols have changed as well. The messages that the modules send on the network are most likely not the same and the PCM may not understand what the rest of the modules are actually sending to it and vice versa. But it is worth a try to attempt to change addressing. Addressing is not proprietary, so to speak. The aftermarket scan tool companies have to have this info to communicate and find all the modules on the network as well.. Let me see what I can find, but most likely will need vin numbers to get as built data and module addressing.

interesting problem. just curious. what diagnostic adapter are you using? i have had weird things happen with forscan and some cheap elm327 devices that cant switch protocols. not saying i dont use cheap elm based interfaces with forscan sometimes, but i also have a couple of proper j2534 spec adapters to use and i will try them if i run into weird comm issues. is the adapter you are using able to switch between the 2 networks? there are some cheap elm based devices that are very good at doing this and work well with forscan.

when i diagnose can or j1939 issues, i use a piece of software called saavycan with a kvaser can interface thru a home made adapter cable on the end to connect to whatever i was working on. you can find it at https://github.com/collin80/SavvyCAN

another piece of software i use is written by kvaser called can king . https://kvaser.com/canking/

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.

Have you tried setting to just high speed? Maybe it is not scanning that databus long enough to detect the other modules when starting a new profile.