21 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCAN bus Message data
Leading reported evidence
Adjust swa in my version
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
I adjusted the SWA in my version to be 450 degrees in each direction.
Leading evidence: 'Adjust swa in my version' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Adjust swa in my version' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Does anybody have a logfile of the raw CAN data with running engine?
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'm only looking to pick up CLT/IAT/TPS/Speed/oil temp for the maxxecu to use (I'm going to look probably at using it in a sort of hybrid/piggyback role), I might have to use OBD2 CAN to pick up IAT I think as am not sure it's broadcast.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'm only looking to pick up CLT/IAT/TPS/Speed/oil temp for the maxxecu to use (I'm going to look probably at using it in a sort of hybrid/piggyback role), I might have to use OBD2 CAN to pick up IAT I think as am not sure it's broadcast.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'm only looking to pick up CLT/IAT/TPS/Speed/oil temp for the maxxecu to use (I'm going to look probably at using it in a sort of hybrid/piggyback role), I might have to use OBD2 CAN to pick up IAT I think as am not sure it's broadcast.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
21 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T000231Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi all,
I'm looking for information on the CAN traffic for a 2002 996.2 C2.
I've found some info online and I've decoded (part of) some messages by sniffing the bus and reverse-engineering but I'm still missing some info.
If anyone is interested, I can post what I have so far.
The goal is to ditch the ECU and Tiptronic modules and replace them with my own controller.
I'm particularly interested in the data coming from the ABS/PSM (torque reduction request) and I'm also missing some ECU message(s) that result in a faultcode in the ABS/PSM unit.
Does anybody have a logfile of the raw CAN data with running engine? (My car has no engine/gearbox)
Any help is appreciated.
I've got a maxxecu mini on its way to hook up (to listen to CAN) and can use that to get you some raw CAN data when it turns up. What are you looking to replace the DME with? Can't help with tip as I'm manual.
I'm only looking to pick up CLT/IAT/TPS/Speed/oil temp for the maxxecu to use (I'm going to look probably at using it in a sort of hybrid/piggyback role), I might have to use OBD2 CAN to pick up IAT I think as am not sure it's broadcast. Not a biggy either way for me and I can always plumb in some analog sensors if needed, just from a packaging and wiring point of view this would be neat.
I'd be interested in what you've done so far and what your plans are...
Thank you for your fast responses.
The info from @Damo996 helped fill in some gaps in my spreadsheet.
I'm especially chuffed about the 0x1A0 message. That's one of the things I was looking for.
Do you have any idea how the standard DME reacts to the 'intervention' signals?
I would imagine an "ABS intervention" would result in a complete 'minimal torque state' or 'close throttle'.
Not so sure what "ABD" and "TCS" is and how the DME should react to those interventions though (TCS=TractionControlSystem? , ABD=StabilityControl?).
My best guess is that the "fast" and "slow" values command a decrease in torque by the given percentage but how 'fast' or 'slow' this should happen is unclear.
So far I haven't been able to get the RPM dial in the instrument cluster to move by sending an RPM signal in msg 0x280. It would be nice if I could figure that out. I know that the fuel level indicator works in a peculiar way, so I think hacking into the PCB and taking over control of the steppermotor will be required to get that one to work.
As for the plans...
The car was bought without engine/gearbox. Those will get replaced with two electric units.
The DME and Tip unit are still in the car for now, but they will most likely be removed.
A VCU (Vehicle Control Unit) will be wired into the CAN bus to interact with both the existing vehicle units and the added units (bms, charger, inverters, DC-DC converter, pumps etc.).
For now, a National Instruments cRIO embedded controller will be used for that.
I'm having trouble attaching my spreadsheet file. I'll try to post in a separate post.
PJ.
The module listed as ASR, which I believe is the traction control, transmits the following IDs.
0x1A0 TCS, ABS, ABD intervention, TCS intervention slow and fast, operating torque
0x2A8 FL,FR,RL,RR wheel speeds, 15 bits each
0x4A0 yaw rate sign and yaw rate, braking and error flags, byte 4 is multiplexed braking data,
MC
Thanks for that @MisterCorn !
Do you have more info you could share about bit positions for the 0x4A0 message?
What should I expect from "Operating torque' (from ABS/PSM in 0x1A0)?
Could you share the bit positions for that one as well?
PJ
Here is a bit more to get stuck in to. No point asking me what any of the descriptions mean, they are translated from German and your guess is probably as good as mine on some of them...
0x4A0
Byte 0
bit 0 yaw rate sign, 0 = positive, 1 = negative
Bit 1, start of 9 bit yaw rate, range 0-510, 0.0021326 rad/s/bit
Byte 1
bit 2 no actively built up brake pressure, 1=no pressure
bit 3 reserved
bit 4 ACC related error occured 1=errror occured
bit 5 Receipt for ACC message 1=message implausible
bit 6 Driver braking 1=braking
bit 7 Regulator error in the FDR system, 1=error
Byte 2 to 3
bit 0 9 bit acceleration, values 0-1022 for -15.97 to 15.97 m/s^2
Byte 3
bit 2 Error driver brake detection 1=error
bits 3-5 reserved
bits 6-7 multiplex code for byte 4
Byte 4
multiplex 00 Brake normal 0-255, 0 - 25.5 m/s^2
multiplex 01 Brake offset 0-255 0-25.5 m/s^2
multiplex 10 and 11 reserved
Bytes 5-7
Reserved
0x1A0
byte 0 is status
bit 0 ASR request
bit 1 MSR request
bit 2 ABS active
bit 3 ABD active
bit 4 FDR active
bits 5-6 ASR ***** control
00 not required
01 shiftmap
10 downshift
11 switching prohibition
bit 7 FDR lamp
byte 1 is status
bit 0 ABS lamp
bit 1 FDR lamp
bit 2 brake warnign light
bit 3 brake light switch
bit 4 brake light switch, comment to say inverted??
bit 5 rough road suppression 1=blanking
bit 6 rough road suppression status, 1=bit 5 valid
bit 7 parking brake
byte 2
bit 0 lamp on PSM button
bits 1-7 vehicle ref speed low data 0.01km/h/bit
byte 3 ref speed high data, 1.28 km/h/bit
NOTE Reference speed refers to a fixed tire circumference of 1.938m for ASR5.3 and 2.00m for FDR5.3/5.7 and ASR5.7
Bytes 4,5,6 are TCS intervention torque slow,fast, intervention torque
0-99.6%, 0-254, resolution 0.39%
Byte 7 is lateral g force, 0-254, -1.27 to 1.27g, only with FDR, otherwise 0xFF
MC
Thanks again, MC!
I might be able to help if you need anything translated from German (I know a little myself and I have some German contacts).
Ar you sure about the 0x4A0 address? I didn't see that message on the car but I do get a 0x4A
1
message from the ABS/PSM unit...
I'll update the list on monday and edit my earlier post.
Have a nice weekend.
PJ
This is an old post, but I have been working on the 996 for my 2001 C4 Cab. I've made a little progress and fixed a few errors. However, this one is in MPH not KPH. With the help of
@MisterCorn
, I've added some info to the Tiptronic section but am still trying to figure out a few things, like turbine, temp, and torqe converter. I did add limp mode, selected gear, shifter position, and (maybe) shift status and torque retard.
One fix was making the ABS_3 ID appear in SavvyCan Signal Viewer. It was mislabeled, at least for that purpose.
Thank you for posting this. I've been digging through this compiling everyone's info on the CAN bus and pushing updates to my AIM SOLO 2 and i'm getting close to having really good data! I'll post updates when i get it finalized!
Since I'm working with a 996 Turbo manual, I’m currently excluding Tiptronic references from my testing. I’ll report back with my findings once I’ve made more progress. I plan to confirm the steering angle gain and offset this evening to corroborate all the data points; the current readings are a bit light on degrees, so I'll be fine-tuning that. Additionally, I’ve successfully pulled both oil pressure and ambient temperature data from ID 0x520, which seems to address the concerns others have raised about that bus.
About 1,073° total steering wheel rotation, or roughly ±536° from center.
That comes from the factory spec of 2.98 steering wheel turns lock to lock with a 16.9:1 steering ratio. The Turbo shares the rack with the C4S, so it carries the same numbers — turning circle is fractionally larger due to the wider front track, but wheel turns are the same.