Lukeyson
-
Posts
6 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Events
Posts posted by Lukeyson
-
-
I wonder if this is applicable to the earlier Bosch 8.0 SX Territory ABS units - in order to add Hill Descent. The wiring for hill descent was on all territories - it just needed a switch in the blanking to the lower left of the steering wheel.
Time to dig out some 10 year old Data and see if I'd captured my original As-Built on the old SX. I didn't know it was called As-Built at the time, but I remember seeing it.
Lukeyson
-
- 3
- 1
-
You know, I wish I could recall where that data came from. It's making my efforts to do the same work on the XR4 all that much harder. A few messages map across but not all. Clearly I had access to something at the time given the detail - like the data ID's and the offset/mult/div. I am doing the discovery now using a J2534 tool - a few cheaper tools have popped up in the 10 years since - and the software I used back in the day, which is still useful. It's very good at showing the broadcast ID's and highlighting when data changes (including graphing, or doing a live offset/mult conversion on the fly). Or Blocking all other messages so I can focus on a smaller subset.
I might sanitise the BA/BF/SX/SY data i have and upload it somewhere The work I'm doing on the WQ I have up in a Google Sheet and am still updating it:
Luke
- 1
-
I cannot for the life of me remember my source, but this is what I have for CAN ID 200 for Black Oak/Spanish Oak, whic hI saw you all chatting about above. This is copy and pasted out of an Excel spreadsheet. Byte 6 in particular looks terrible when I paste - it's a bitwise field.
Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 200
PCMTorqueDataEngineFlags ActualEngTorque MinAvailibleTorque MaxAvailibleTorque KeyOffTimer ActualEngTorque
Units:Nm
Offset:-512;Mult:1;Div:1MinAvailibleTorque
Units:Nm
Offset:-512;Mult:1;Div:1MaxAvailibleTorque
Units:Nm
Offset:-512;Mult:1;Div:1TorqueType_PCM
0=Axle;1=EngineInertiaLosses
0=Axle;1=EngineCatProtectionActive
0-Off;1=OnCrankStatusPCM_HS
0=NoAction;1=CrankPending;
2=CrankInProgress;3=LowVoltageCrankAttemptKeyOffTimer
Unit:Minutes
Offset:0;Mult:1;Div:1 -
Hey Guys
Many years ago I did a whole lot of work like this on BA, BF Falcon and SX Territory - reverse engineer CAN Arbitration messages/ IDs. I didn't do so much on the PCM side like you guys are doing, but I did a whole lot on the other modules - PAM, RCM, IC, ICC, HIM etc
I've just started some similar work recently on a 2007 WQ Fiesta XR4.
Is there any appetite for me sharing any of my data? Or is this mainly a thread with Focus in PCM broadcasts...?
I'm kinda on the hunt for a forum or message group with people doing similar reverse-engineer analysis on Ford messages. There's not much around. Some US based F150 guys, one on a Focus which, depending on the model, is likely to be very similar to the WQ Fiesta and BA Falcon, as both used ECU architectures that were derivatives of the original MkI Focus.
Luke
micro-controller using CAN bus data for ancillary control
in General
Posted
<Crawls out of the woodwork, tips hat....>