The Definitive EPC Guide (Continued)
For part ONE Click Here!
Having said that, in my humble opinion, the EPC circuit with its drive-by-wire circuit and its "Limp-mode home" mode, is a value-add for modern car design; and though frowned upon by many, is a very valuable safety feature. Also bearing in mind that when the communication network is momentarily unavailable and an application that depends on it is unable to communicate, it may trigger the ECU into "Limp-mode home" and set a DTC. Exception errors do occur in synchronous or asynchronous distributed system, where software entities act as clients or servers or both. So when where 1...n clients are requesting services via a specific protocol from typically one server; the server services the client but temporarily blocks its service request and data flow control, whilst other client expects a response from the server.
If 1 client to n server communication can be established, it would certainly solve the problem but it’s currently not supported. Also remembering that the CAN bus is a serial communication network through which all modules communicate with the ECU via a Central Gateway, some uses FlexRay frames and others Lin bus or CAN, each with a differing topology, some synchronous and others asynchronous. The Central Gateway is responsible for frame or signal mapping function between two communication systems, like from LIN/MOST/CAN/FlexRay to Ethernet transport systems. However ECU gateways often have two or more internal Gateways like the Service Data Unit (SDU) gateway, Layer 3 Tunnelling Protocol (L3TP) gateway and the Signal Gateway needed for frame or signal mapping function between two disparate communication systems.
The best analogy with which to explain the above would be your cell phone. Cell phones are native Global System for Mobiles (GSM) devices with a microprocessor and its support chips, much like the automotive ECU. Cell phones support the Hypertext Transfer Protocol (HTTP) and the Wireless Application Protocol (WAP) for Wi-Fi as well as the Bluetooth communications protocol through a "Gateway" which translates it to a common data stream native to the Cell phone operating system.
So, while you’re downloading an email and the phone rings and you answer; the email download temporarily stops but will resume when the call is terminated. The same applies to a Bluetooth file transfer which will be interrupted even possibly terminated when a phone call is answered. However, not all services are prone to such interruptions because some services are inherent to the design. For example, when you’re listening to music on your cell phone and you answer an incoming call, the music is temporarily suspended until the call is terminated then the music will resume.
This function is purposely part of the design whereas exception errors are not and are more prone to happen with asynchronous communication, caused by propagation delays. This is what also happens when the ECU inter communicates with other modules and when the messages are not delivered within a prescribed period of time, can cause the car to go into "Limp-mode home" . So if for some reason the radio that is a non-essential service is hogging the network bus, and you step on the brake which the ECU will undoubtedly detect but the brake light didn't illuminate within the expected response time, which the ECU will also detect, then the car may go into "Limp-mode home" .
Or you could hit a speed bump in the road at high speed and bounce back onto the road; the thump if hard enough or loud enough to trip a knock sensor would cause the car to go into "Limp-mode home" . Or you could have just done some high rev spirited driving to cause the car to go into "Limp-mode home" . One consolation is that, when the ignition is initially turned on; right before the car is started the ECU does a self-test to verify that all’s well, and if that is the case, the car will start and drive normally.
However, if the self-test fails, one of the caution lights may remain on. It could be either the EPC light or the Check Engine light or perhaps both, or one or both could be blinking, which is a sure sign that you may have a problem. Once again, a diagnostic scanned would be the most informative way of establishing what the problem is. But I’ve encountered car owner who took their vehicles for diagnostic tests and no errors were flagged, so in some cases may be a futile exercise.
Having said that, if you are stranded along the road side, the best would be to reset the ECU by removing the battery earth terminal for a minute or two, but make absolutely certain that you have access to your radio / DVD code before you disconnect. Whatever errors occurred prior to this will be safely stored in the ECU non-volatile memory and may be checked when a diagnostic scanner is available but all stored values will be lost. The downside of doing this, is that an additional error would be flagged because the battery (+30V) supply was interrupted, and now the ECU has to relearn your driving style.
ECUs are fairly robust and are more-likely-than-not the cause of your EPC problems, though unlikely but not impossible. The most likely component in my humble opinion that would cause constant and annoying EPC problems would be the wiring harness. Not the actual wires, unless they are frayed and damaged by rubbing against the chassis but rather its edge connectors.
The ECUs and associated modules each have multi-pin connector that’s tin plated and can become intermittent due to the constant vibration of the car. Copper contacts also oxidizes fairly quickly, so to prevent this from happening, they are tin plated which provides for a low resistance, good contact surface. However when water enters this connection, especially in the presence of a voltage or current flow, the contact normally turns black or corrodes green, impeding continuity hence connectivity.
A poor vehicle ground connection is another culprit that can intermittently trigger the EPC light without leaving a DTC. A blown tail light / brake light bulb can also cause the EPC light to turn on without leaving a DTC. Always make sure that the replacement is a 12V 21/5W bulb because the wrong bulb will also cause the EPC to trigger also without leaving a DTC. A faulty brake-light switch (DPST) is also commonly known for triggering the EPC light and sometimes causes the 10A fuse to blow.
So, when the brake is applied and the switch throws, its contacts reverse, meaning the normally-open contact closes and the normally-closed contact, open. If there is a delay in the switching time, even as short as .5 of a second, the EPC light will trigger, without leaving a DTC. A tell-tale sign that the brake-light switch is faulty or that the fuse is blown; is that the Cruise Control appears to be faulty. Since they are both interconnected, the Cruise Control is reliant on a voltage provided through the brake switch.
DTC can often be intermittent or sporadic so it’s best to ignore those, in preference of repairing those that are permanent. In so doing, they may have interrelations and the sporadic ones may disappear after the permanent errors are fixed. So, it’s best to perform a diagnostic scan, preferably an autoscan with VCDS first, then delete all DTC in the process. Thereafter save this scan and printout a hardcopy to store with the vehicles registration papers.
The importance of this printout is that it’s a reference to all the modules coding, and if something is inadvertently changed, there would be an unalterable record to refer to. Once done, and as mentioned above, disconnect the battery's negative terminal then disconnect the positive pole and place the battery on charge for about two hour. Replace the battery by first connecting the positive pole then lastly the negative pole.
By following this sequence you will prevent damage to the electronics modules strew throughout the car. At this point, all pre-learnt and all stored values would have been erased from the ECU. Essentially all the control modules would have been completely reset, restarting with a clean slate. After starting the engine and driving the car for a short distance, check to see if any DTC have been flagged.
Resetting an ECU occasionally is a good thing, because any and all electronic equipment with a microprocessor can experience an unrecoverable error or an internal parity error or fail a cyclic redundancy check and requires a "cold" system restart. Computer memory (RAM) also experience memory read/write errors, interrupt or address errors and general protection errors; so when the ECU is reset/cleared, along with its non-volatile memory, the memory (RAM) is also reset. AUOTSAR and its core partners are trying their utmost to rectify such problems in automotive ECU, but until they do, we will have to contend with EPC problems.
No comments:
Post a Comment
Thank you for visiting....