jakka351

0x640#1000000000000000 Is easy to configure for manual, just a few params.

He's.got a Crown.Vic with a supercharged 5.4 and tremec in it. Let err rip tato chip

https://github.com/jakka351/FG-Falcon/blob/master/BigFalconSheet.xlsx Uncensored.

Have you checked that the wheel speed sensor wiring is cable tied nicely and not hanging loose or catching on moving parts?

If you get the VIN/rego and bang it into the Ford service page that should tell you what is was from factory. Did this car have an engine in it when you got it? It could be an Xr8, with the engine and bonnet missing they are essentially the same,

This is Fg1 right? Are you sending messages on both buses? You are missing most of the module keep alives for the ms-can(FNOS Identifiers). These are the 0x5XY IDs on the Ms-can. On the high speed you'll need 0xFC and 0x210 (ABS) and 0x623, 640, 650(PCM). 0x353 should be broadcast only from the hscan as it is transmitted by the HIM and then re-sent into the midspeed by the cluster for the FDIM display.

Can you not drive it like you stole it for a bit and do a bit of enthusiastic adaptation re-learning

What is the ABS Config set to in the stock tune, and what have you tried setting it to currently? Also what is the car originally? specifically is an Xt, and Xr6, G6? Can you also post what these parameters are set to: auF1718, auF2552, auF2531, auF1210

CAN Messages - General - PCMTEC Forums

Yep. CAN ID 307 byte 3 will turn the Hazard Lights on - MSCAN transmitted by the FDIM upon pushing the hazard light button. It is retransmitted by the IPC on the same ID onto the HSCAN. Every actuator within the cluster is independently controllable via diagnostic commands, so needles, LED's, LCD and you can even send a can message that will have the same effect as physically pushing the buttons.

Does anyone ever pull the VIN off of the ABS module when these issues are happening? I see that FORScan does not appear to be able to do it. However it is there in the As Built in block 0. Hmmmmmmmmmmmmmmmmmmmmmmmm

PCMTec will run on a 2005 Panasonic CF-19 Toughbook with Windows 10 and 2 gigs of RAM. The issue here is Apple.

A stock engine/tune is going to go through a bunch of different different protection mechanisms before shutting down, like torque reduction, cylinder shutdown, before finally killing the engine. Could you not just wire up a relay in line with the CHT signal wire to the pcm, when your condition is met the relay activates and x amount of resistance is added/removed to/from the CHT signal wire circuit such that the CHT reads to the pcm as hot enough for immediate shutdown - there may also be plausability checking done by the PCM that could cause it to ignore such a signal and then use the 'default CHT in case of failed sensor' value.

Boom Tuna!

Small Update: Parameters auF1718, auF2552, auF2531, auF12105 control the data which is sent on CAN ID 0x623 bytes 0-3 respectively(0 being the first byte). I am still mapping the rest, and as for how this can be used in practice to match ABS Config to PCM Strategy, the end goal would be to have the ABS configured as per the physical setup on the vehicle, so Xr6 NA should really be set to Xr6 NA Configuration in the ABS module, but to have that work with an Xr6 Turbo Strategy/PCM the above is likely what the ABS module reads before deciding if it is good to operate or if it will go into fault mode. I suspect that on the same makes the ABS module and pump hardware is all the same, this makes sense from the point of the manufacturer, however there is a lot of different hardware between BA/BF/FG/FGII/FG-X as well as 3 different diagnostic protocols. This means that in theory, as long as you can tell the ABS module the right data you should be able to match the correct ABS config for the vehicle setup to any PCM strategy. More to come.