Ok guys I could do with some pointers on this one. I have a 2004 Jaguar Xtype 2.0 diesel that has a traction control/abs fault. My story is a little long so I am sorry but here goes.
The jaguar came in for service with a space saver wheel fitted that had been on the car for 5weeks this was removed and the original type fitted back on.
During the service a noisy O/S/F wheel bearing was replaced at the same time. The wheel bearing contains the tone ring on this model for people who are not aware of the setup. I completed the service and work and rang the customer only to be asked about the lack of power that he didn't mention when booking it in.
Road testing the car reviled a huge loss of power but it was down to the traction control intervening at about 20mph it kills the throttle it also makes the front bakes grab intermittently at lower speeds than 20mph.
I graphed the wheel speeds on my solus and there are some small discrepancy's at 50mph both front wheels read 50 the N/S/R reads 48 and O/S/R read 45 but no visible drop outs I thought it might be tyres so I checked the sizes and moved the front to the back and road tested again but no change. I then graphed wheel speeds with my friends Chinese launch scanner and his showed all wheels dropping out intermittently on the road and had a code for can-bus that mine did not retrieve.
The only fault codes stored in abs and only set once but cleared again was c1222 wheel speed conflict.
I thought I must have a drop out on the wheel sensors so I scoped them all on the road and found the signals to be fine even when the traction control is intervening the frequency of the 4 sensors is very close to each other unless I am missing something
I checked power and grounds at abs with load-pro and checked can bus with scope.
the can bus looks a bit odd plugged in and unplugged and its better if you scope both can high and low at the same time for some reason.
At the moment i am thinking the computers faulty based on the scope waveforms of abs sensors frequency being the same and graphed data being off a little plus the drop outs on the launch graphing maybe the solus is not fast enough to catch them but why no codes ?
ok guys If you made it to the bottom of this then thank you very much for taking the time to read though it and I hope someone can help me I do have waveforms that I will try to figure out how to post them the hash on the sensors is when the traction control kicks in and the light comes on