Controller Area Network- Carrier Sense

Carrier Sense -

• Carrier here is nothing but a CAN Bus. Carrier sense is to check the bus before transmitting anything on the Bus.

• CAN Controller checks if the bus is Idle.

• It starts transmission only if the bus is idle.

• If the bus us not idle then it will wait for current transmission to end.

• Consider a Scenario when CAN Node wants to send a message on the CAN bus.

Refer below link to see a Video to visualize it.

Comments

What is a Diagnostic Communication

Diagnostic Communication : Diagnostic Communication is base of Automotive Diagnostics . It is an exchange of Diagnostic messages between an two entities. Those could be two , ECUs or ECU and Tester Application.or it could be a group of ECUs and a tester application The basic components of the diagnostic communication are : A Diagnostic Message : It could be of these types - 1. A Request 2. A Response 3. A Negative Response Code Diagnostic Address : 1. Functional 2. Physical Diagnostic Protocol : 1. UDS 2. J1939 3. KWP 2000 etc. Supporting Protocols : 1. CAN 2. Ethernet 3. K-line ,etc What is Diagnostic Protocols ans supporting Protocols ? ECUs and tester communication are connected to each other by physical or wireless media. They exchange messages (requests and responses) over that physical or wireless channel. It is same as we connect to each other over internet or phone...

Diagnostic Session : Function 5 - Session Oriented Access to Services

There are multiple users those need to use UDS protocol for various purposes like Garage person for fault detection, ECU manufacture for Testing activities and development purpose. Also OEM needs access to ECU memory for flashing purposes. UDS services can be categorized in different groups like few services will just read some Data from memory,a few will write or update the data to memory, some will erase/update ECU sw itself , some will control Inputs outs of ECU directly. So there are chances that any improper usage of UDS service may result in safety issues , security breaches or damage to ECU resources. Hence, it doesn't make sense to give access to all services to everyone. To achieve this UDS has designed some mechanisms like Sessions, Security Authentication, Preconditions. I hope you are aware about what a Diagnostic Session is. Please visit : https://thevehiclediagnostics.blogspot.com/2020/01/what-is-diagnostic-session.html if you ...

Diagnostic Session : Function 2 - Part 2 - Support Session layer requirements of OSI layer

We have seen a concept of P2 Timer and P2 * Timer in the blog – https://thevehiclediagnostics.blogspot.com/2020/01/diagnostic-session-function-1-maintain.html So it is time to know how Service $ 10 – Diagnostic Session Control is having on a function related to these timers. Session Layer requirement Overview of P2 Timer : P2 timer and P2 * timer are mentioned as a performance parameters Standard values for these parameters are defined in ISO 14229 Part -2 But an ECU may change these timings in non-default sessions and Client needs to adapt them dynamically (some conditions are applicable). Explanation : Though there is defined value of P2 timer, this timing can be still improved. As these are marked as performance requirement, if the ECU can give better performance, then these timings can be reduced. ECU can change these values in non-default session as per the performance. ...

Automotive Diagnostics

Search This Blog