Log In

New Kvaser white paper discusses ways to maximise CAN’s efficiency in next generation vehicles


By using a Virtual CAN Bus, we separate the control task from other tasks. The distributed embedded control system can be developed using standard CAN Controllers and transceivers in a traditional way with well proven tools.

Other tasks such as encryption, transmitter authentication, re-flashing, etc. can be developed by experts in these fields and carried out by using other protocols. With modern technology, the different tasks can run in parallel and simultaneously communicate on the same physical layer.

It is a great advantage to separate the control problems from other problems. The control problem can be solved once and for all by the control experts and other problems by experts in their respective technology fields.

 

Details here......

 

Celebrating 36 Years

Follow us on Facebook for all the latest news, updates and promotions

 

 

CAN Test Box

can test box

 

Continuing with our mission to make vehicle diagnostics easier and faster…the new CAN Test Box gives you easy access to the 16 pins of the diagnostic connector that is fitted to all modern vehicles. Depending on the configuration of the vehicle, this may allow you to check power, ground and CAN Bus signal quality. With the test leads supplied you can connect your PicoScope lab scope to the CAN Test Box to monitor signals such as the CAN High and Low. More.....

Attention all
Automotive Scope Users


Pico Automotive Scope software now sports a new Waveform Library browser.
Must own PicoScope to view.
See details here

 

Credit Cards Accepted

website security

 

Corsafantastic!

Pico Logo

By Nick Hibberd

Hibtech Auto-Electrical Diagnostics

 
 
 

 

The complaint

Ordinarily I wouldn't have given this the time of day had it not been for an unusual recorded trace, which I felt would be interesting to share. The eventual cause of the fault was... you'll have to see it to believe it. The vehicle was a 1999 Vauxhall Corsa into which someone had shoehorned a V6 lump. This particular production run also came with a second instrument cluster hack: sawed (literally!) into the passenger dashboard and providing amusement for onboard participants, no doubt. Quite a little cherub.

The complaint was that at high rpms the engine would stumble and misfire. Release the throttle to idle, and it fired on all six again. The problem didn't appear temperature- or load related, and I could recreate the complaint in the workshop, which is always helpful. Checking the engine system with the scan tool proved a waste of time as no socket connection was wired up. All things considered, I made up my mind to make one hook-up with the scope and if that didn't point me in a clear direction then I was handing back the keys.

The tests

figure 1 figure  1a

You will, no doubt, have spotted the erratic coil primary events, which are a serious contributing factor to the engine's stumbling. There isn't much right about the primary events during the fault period: primary dwell is sometimes too short, sometimes too long, sometimes overlapped, and sometimes missing altogether. The ECM is clearly struggling to maintain correct ignition timing.

Not least is the odd CKP signal momentarily hanging high immediately after the sync trigger. All the captures recorded during high rpms displayed the same unusual signature after the sync, yet the remaining rotor signals generally appeared normal and acceptable. In fact, those with a keen eye may be able make out the early stages of this signature back in the idle capture, Fig.1.

figure 2

The diagnosis

With different issues to deal with, I find it best to break the problem down and prioritise the concerns. Very often when one root cause is found it usually explains other related issues. For me the most important anomaly here is the unusual drift in the CKP signal, and considering this critical signal is used to determine each ignition point, there's a good chance to eliminate multiple issues following one test plan.

figure 3

A bad CKP sensor? To very briefly summarise the variable reluctance (VR) sensor operation: it can only react to what it sees. During our signal drift the sensor is still capable of producing a recognisable sine wave, and its general operation is further confirmed by the remaining rotor teeth being displayed as normal, centred on the ground bias. Simply put, the VR sensor does not get to choose what bias voltage the generated signal rests on. This is entirely left to external factors within the management system design. For the moment, a faulty CKP sensor is low down on the list for this root cause.

A bad trigger wheel? This is one which provoked the most thought. It does seem evident that our unusual signature only appears in one place on the trigger wheel, each and every time. A bad spot on the wheel would certainly create a repetitive pattern and throw the signal out in one way or another. Thus, so far, all the boxes are ticked. But we have to be clear what "fault" we are chasing. The fault lifts the entire waveform so that its negative peaks are above the bias voltage (in this case, zero volts), something that no defect in the trigger wheel could cause. This was not a mechanical problem: this was electrical in origin.

A problem with the CKP electrical circuit? This now is most likely, although at this point in the investigation I could only describe the fault as something pulling the signal line towards a positive potential: a circuit leak perhaps. We can eliminate a problem with the ground bias as this remains steady throughout the fault.

figure 4

The autopsy

With a theory in place, the next step was to verify circuit insulation all the way back to the ECM. I followed the engine harness routing through the firewall and down to the driver's kick panel, where I found the ECM rattling loose behind a trim. The test plan was to disconnect the ECM connector and check continuity between the CKP circuit and other connector terminals, hopefully resulting in some abnormal insulation readings. I didn't get that far...

figure 5

The ECM connector had suffered severe water ingress and was well on the way corroding the ECM male pins too. With this degree of severity and a maze of cross-circuit voltage leaks it's impossible to isolate the track our CKP signal was taking, except to say it had a lot of choice.

figure 6

The voltage kick we normally see around the sync gap was, I suspect, a contributing factor to our unusual signature, leaving residual voltage after the peak leaking into the corrosive chaos and hanging on the end of the peak. Scrutinising the captures further revealed signs of the signal wavering at other points too. There's a lot happening here and it would certainly have manifested with other issues in the surrounding circuits producing some problems of their own. A real mess.

The subtle wheel arch modification was likely created to accommodate the bulky ECM and connector not original to this car. Once discovered, this butchery justified my apprehension at the beginning. It's OK though: the plastic wheel liner will stop any water from getting in!

PicoScope data files

  • Download the PicoScope data files of the waveforms featured in this article:
  • psdata          'bad' waveform (1.75 MiB - about 5 minutes @ 56 kbps)

back

 
 
 
USA Office

Tel:1.877.902.2979-1.425.223.4311
Fax:1.877.329.4324
Address: 1480 Gulf Road, Suite 837,
PO Box 1280
Point Roberts, WA 98281

Western Canada - Vancouver BC

Tel:1.800.663.6001 or 1.604.925.6150
Fax:1.604.925.6170
Address: 2454 Haywood Ave
West Vancouver, BC V7V 1Y1

Eastern Canada - Markham, Ontario

Tel:1.800.465.0164 or 1.905.513.7027
Fax:1.877.329.4324
Address: 3075 14th Ave, Unit 219,
Markham, Ontario L3R 0G9