Nigel

Luke - how did you work out some of that data - it seemed quite advanced when you had it Nigel

I wonder if the PCM is waiting for the clutch switch to actually cycle before working - just as it does with the Brake switches

Darryl. Ive taken a look. That was interesting - as the same data exists for FG1 as well. However - it does not mute the cluster One to look at is 0x35c, in particular the 5th Byte. When the 3rd and 4th bits are set (&0x0c), I do not get communications fault. When they are not set, Communications Fault. This may be completely related to invalid data, however it is also the same behaviour I saw with 0x200 on the FG Cluster. P.S. I would love the complete breakdown of 0x35c. There is a very interesting behaviour/interaction between 5th Byte, 8th bit, and the Tach where the FG2 cluster changes its data source for RPM from 0x35c to 0x15f. Actually I have a range of CAN ID's Id love, but this is one of them

Let me know if its in BA - it matters (to me). Its also higher speed than the data the cluster uses (more frequent).

Darryl. Is there any note there of the intended target for this data? I know that for the general stuff, this is not where the FG2 Cluster gets its running data from - Hence my assumption that this was data for Trans/ABS. I'll take a look as soon as I have a second.

Darryl. can you give me more information on 0x12d? - I have only got Tach and Throttle Pos here, and it appears for ABS not cluster? If you can tell me which is the cranking flag I'll give that a go

Nice work Darryl. I had the two lower bits of byte 7 as the two that disabled noise. Interesting to see how much it mutes. Can you confirm if its the same for FG2? - completely understand if timing doesnt allow. Not sure if this needs to be moved to another Thread. All of the Factory stuff says that Crank Pending is enough to mute the Alarms (and that reflects my experience on the cluster). Which alarms needed to be silenced?

Roland thats interesting. When I had an FG Turbo, I was quite surprised at how poorly it would run on 98. There was an interesting Engine Roughness which just wasnt there on 95. Did Ford just tune for 95? - or even 91 on the turbos? - Mine certainly ran well on all fuels. I ended up going with 95, and the odd half a tank of 98, always BP

This is where its a little interesting. There are bits and pieces of the CANID in the PCM Sections for BA, BF, however they only list a very few. There were odd ones - I came across this gem : (BF Falcon) Message 427, Bit 6 = Travel Assistance Service (Unlock all doors). Makes sense, but its not mentioned again in any later manual I have. The FG1 Manual only, for the Cluster Only, has the CanID's for all alerts etc, as well as a comprehensive list of RX and TX Source/Destinations. Again - not in ba, bf, and not in FG2 either. But it helps!. I am not able to confirm at the moment if 0x200 will silence the oil alarm etc. However, I do have an FG Cluster on the bench, and an FG2 cluster, and I can try. Im not sure I have enough info to correctly Simulate it yet.

Roland. It was a pain in my backside - I had RSS Enabled on the cluster I had, and if I sent 0x200, then it would stop. However then other stuff wouldnt work - its one of those weird "ok, how come its fixed something, but broken all this other stuff". Page 413-01-51 (FG1, but Im not sure that this one would have changed for FG2). Ive attached the Documentation in the Cluster Section of FG1. 0x210, 0x230, and 0x360 are disabled while cranking. 0x210 is your ABS/DSC Warnings, 0x230 is the PCM Telling Cluster about Gear Selected, and (on MS Can) 0x360 is the Reverse Park Sonar (PAM) Wouldnt take much here to work out exactly which bit it is. It could be Bits 0,1 of Byte 6 that actually signal the Crank

This is interesting - Id been looking for more data on 0x640. In the factory workshop manuals in the cluster/instrumentation section, data is listed as CanData : "ManualTrans" - Removes PRNDL from cluster if Manual. That would appear to be 0x640, Byte 3, bit 5 which might indicate this. Also in the Factory Manual for the FG powertrain, there is a table on page 303-14-96/97 which shows what canbus data is sent from/to the PCM. Whats particularly interesting is that the only Data it shows the TCM receiving from the PCM is Throttle Position. I guess thats possible with the ZF - it has Speed and Tach already available. Ive seen documentation errors before, and also in the ford factory stuff. But thats an interesting observation. I didnt see it further up the list, but 0x200 also has Crank Status Warning, which is used to disable a pile of alerts on the clusters while the engine is cranking. that was an interesting one, because if you send 0x200 to a cluster it will stop many warning lamps from working correctly, and will silence the Alarm. Speaking of the Alarm - Roland, this may be a way to silence any alerts that happen while your displaying the CustomOS Selection on the cluster Im not as far into this as you guys, but I love the work. Nigel

The FG XR6T' Chasers have LSD and Traction Control, and being honest I wouldnt drive one without it anymore. The Turbo just makes them a little too non-linear. Track of course is different, but Traction Control will still work with a LSD.

Darryl. Reading what youve just posted, does this mean that PCMTec can change or flash the ZF Calibration so that FG ZF can work in a BF? If so, what level is required? Thanks nigel