Pushing the limits of Controller Area Network (CAN)
Download as PPT, PDF1 like1,146 views
1) Scheduling CAN frames with offsets provides a major performance boost by desynchronizing transmissions to avoid load peaks and make CAN networks more predictable at higher loads over 60%. 2) Computing the optimal offsets is an exponential problem but approximate algorithms can efficiently assign offsets to reduce worst-case response times, often cutting them by over half. 3) The NETCAR-Analyzer software can compute frame response times on CAN networks with offsets and help dimension system buffers using a fast implementation.
![Pushing the limits of CAN - Scheduling frames with offsets provides a major performance boost Nicolas NAVET INRIA / RealTime-at-Work http://www.loria.fr/~nnavet http://www.realtimeatwork.com [email_address] ERTS – 30/01/2008 Joint work with Mathieu GRENIER and Lionel HAVET](https://image.slidesharecdn.com/offsetserts-090529125534-phpapp02/85/Pushing-the-limits-of-Controller-Area-Network-CAN-1-320.jpg)
![Questions, feedback? please contact me at [email_address]](https://image.slidesharecdn.com/offsetserts-090529125534-phpapp02/85/Pushing-the-limits-of-Controller-Area-Network-CAN-24-320.jpg)
Pushing the limits of Controller Area Network (CAN)
- 1. Pushing the limits of CAN - Scheduling frames with offsets provides a major performance boost Nicolas NAVET INRIA / RealTime-at-Work http://www.loria.fr/~nnavet http://www.realtimeatwork.com [email_address] ERTS – 30/01/2008 Joint work with Mathieu GRENIER and Lionel HAVET
- 2. In-vehicle networking : will CAN be able to keep up the pace? Typically max. bus load is set to 35% Not enough wrt to short/medium term bandwidth needs … Solution 1: multiple CAN networks … but gateways induce heavy overhead Solution 2: switch to FlexRay … expensive for bandwidth alone Solution 3: optimize the scheduling of CAN frame .. Offsets provide a solution to make CAN predictable at higher network load (≥60%)
- 3. Scheduling frames with offsets ?! Principle: desynchronize transmissions to avoid load peaks Algorithms to decide offsets are based on arithmetical properties of the periods and size of the frame 0 0 0 10 5 0 15 5 5 0 10 20 30 40 50 60 70 80 90 100 110 Periods 20 ms 15 ms 10 ms 0 10 20 30 40 50 60 70 80 90 100 5 2,5 0 110 5 2,5 0 Periods 20 ms 15 ms 10 ms
- 4. System model (1/2) ECU Frame Transmission request task Frame response time Performance metric: worst-case response time CAN Higher prio. frames frame
- 5. System model (2/2) The offset of a message stream is the time at which the transmission request of the first frame is issued Complexity: best choosing the offsets is exponential in the task periods -> approximate solutions Middleware task imposes a certain granularity Without ECU synchronisation, offsets are local to ECUs
- 6. But task scheduling has to be adapted… ECU In addition, avoiding consecutive frame constructions on an ECU allows to reduce latency Frame Transmission request task Frame response time CAN Higher prio. frames frame
- 7. Offsets Algorithm (1/3) Ideas: assign offsets in the order of the transmission frequencies release of the first frame is as far as possible from adjacent frames identify “least loaded interval” Ex: f 1 =(T 1 =10) , f 2 =(T 2 =20) , f 3 (T 3 =20) f 1,1 f 1,2 f 2,1 f 3,1 Frame 18 16 14 12 10 8 6 4 2 0 Time
- 8. Offsets Algorithm applied on a typical body network 21 ms 65 ms
- 9. Offsets Algorithm (3/3) Low complexity and efficient as is but further improvements possible: add frame(s) / ECU(s) to an existing design user defined criteria : optimize last 10 frames, a specific frame, take into account priorities optimization algorithms: tabu search, hill climbing, genetic algorithms …
- 10. Efficiency of offsets : some insight (1/2) Almost a straight line, suggests that our algorithm is near-optimal Work = time to transmit the CAN frames sent by the stations
- 11. Efficiency of offsets : some insight (2/2) A larger workload waiting for transmission implies larger response times for the low priority frames ..
- 12. Computing worst-case response times with offsets
- 13. Computing frame worst-case response time with offsets CAN Controller buffer Tx CAN Bus 9 6 8 1 2 Waiting queue : FIFO Highest Priority First (HPF - Autosar) Carmaker specific Requirements : handle 100+ frames very fast execution times ≠ waiting queue policy at the microcontroller level limited number of transmission buffers AUTOSAR COM Frame-packing task 5ms
- 14. WCRT : State of the art Scientific literature: Complexity is exponential No schedulability analysis with offsets in the distributed non-preemptive case Offsets in the preemptive case : not suited for > 10-20 tasks WCRT without offsets: infinite number of Tx buffers and no queue at the microcontroller level Our software: NETCAR-Analyzer
- 15. NETCAR-Analyzer : developed at INRIA, then RealTime-at-Work
- 16. NETCAR-Analyzer : an overview Worst-case response time on CAN with and without offsets Proven near-optimal offsets assignments with user-defined performance criteria (e.g. WCRT of the 10 lowest prio. frames) Exhibit the situations leading to the worst-case (results can be checked by simulations/testing) Enable to dimension transmission/reception buffers (RAM) Handle both FIFO and prioritized ECUs Fast multi-core implementation (<1mn for 100 frames) Industrial use since December 2006
- 17. Experimental Setup WCRT of the frames wrt random offsets and lower bound WCRT reduction ratio for chassis and body networks Load increase : add new ECUs / add more traffic Performance evaluation :
- 18. Experimental Setup Body and chassis networks Set of frames generated with NETCARBENCH (GPL-licenced) With / without load concentration: one ECU generates 30% of the load N e t w o r k # E C U s # M e s s a g e s B a n d w i d t h F r a m e p e r i o d s B o d y 1 5 - 2 0 ¼ 7 0 1 2 5 K b i t / s 5 0 m s - 2 s C h a s s i s 5 - 1 5 ¼ 6 0 5 0 0 K b i t / s 1 0 m s - 1 s
- 19. Offsets in practice : large response time improvements (1/2) 21 17 32 65 ms
- 20. WCRT Reduction Ratio Body Networks Chassis Networks Results are even better with loaded stations
- 21. Offsets allow higher network loads Typically: WCRT at 60% with offsets WCRT at 30% without offsets
- 22. Partial offset usage 34 17 42 65 ms
- 23. Conclusions Offsets provide an cost-effective short-term solution to postpone multiple CANs and FlexRay Tradeoff between Event and Time Triggered Further large improvements are possible by synchronizing the ECUs … ET CAN CAN with offsets TT-CAN + Complexity + Determinism
- 24. Questions, feedback? please contact me at [email_address]