Codesign Tools for Embedded Control Systems

1. Codesign Tools for Embedded Control Systems Karl-Erik Årzén, Anton Cervin, Dan Henriksson, Martin Ohlin, Bo Lincoln, Johan Eker

2. Outline • Introduction • JitterBug – statistical analysis of how timing affects control performance • TrueTime – simulation-based analysis of how timing affects control performance

3. What is Good Control Performance? • Application dependent • Time-domain criteria • Rise time • Overshoot • Settling time • Frequency-domain criteria • Cross-over frequency • Closed-loop bandwidth • Amplitude and phase margins • Quadratic cost function • System excited by white noise • Statistical (average) measure • ……

4. Control Performance Task TimingParameters (latencies, jitter, …) ControlPerformance (variance, rise time, overshoot, ….) Scheduling &NetworkParameters (T,D,Prio, Protocol,…) Complex relationship Complex relationship

5. Control Performance in Reality • Real applications consists of multiple cooperating control loops: • cascade controller • industrial robots • combustion engines • flight control systems • Implemented as one or several tasks • The performance is related to the goal or mission rather than to individual loops • How should we define control performance in this case?

6. Resource Constraints • Product-level constraints ($$, size, connectability, …) generate platform-level resource constraints: • Computing speed • Memory and chip size • Communication bandwidth • Power consumption • … • True in spite of the rapid development of computing hardware

7. Co-Design • Increasingly important due to the resource constraints • Several levels: • Mechatronics • Hardware-software • Functionality-dependability • Control and computing • …. • Why control? • Important class of embedded systems • Unique possibilities to manage uncertainty

8. Not a New Topic • In the 1960-70s constrained computer resources and temporal non-determinism were a general problem that was well-known among control engineers • E.g. effects of fixed point calculations on control performance • During the last 20 years a lot of old knowledge has been forgotten • Example: ”Rediscovered” PhD thesis • ”Random sampling and random delays in optimal control systems”, Charles Davidson, KTH Stockholm, 1973

9. Co-Design Tools • Especially in embedded systems separation-of-concern based approaches are not enough • New types of tools needed that take implementation-level timing effects and constraints into account • Analysis, simulation, synthesis

10. The Control and Scheduling Co-Design Problem “Given a set of plants to be controlled and an implementation platform with limited computing and communication resources, design a set of controllers and schedule them such that the overall control performance is optimized”

11. Dependencies The nature and degree of difficulty of the codesign problem depend on: • The RTOS • scheduling algorithms supported • I/O handling • execution time measurements, overrun handlers • The scheduling algorithm • time or event-driven • priority or deadline-driven • schedulability and response time results available • which parameters can be changed on-line

12. Dependencies • The controller synthesis method • design criteria • continuous-time or discrete-time design • robustness towards timing variations • active or passive compensation for timing variations • Execution-time characteristics of controller code • predictable WCET • sample-to-sample variations • multiple operating modes with different timing profiles

13. Dependencies • Off-line or on-line optimization • what information is available for off-line design? • how accurate is it? • what can be measured on –line? • dynamic task allocation • re-optimization at workload changes • feedback from control performance to scheduling algorithm • Network communication • network protocol • guarantees on network latency • probability of lost packets • global notion of time • time stamping

14. Co-Design Tool Origins Hybrid Systems Control Co-Design Tools Multi-Model DesignEnvironments Real-Time Scheduling &Computing Networking

15. Multi-Model Tools Focus: • modeling, simulation, and design of concurrent, real-time, embedded systems. • assembly of concurrent components • well-defined models of computation that govern the interaction between components • use of heterogeneous mixtures of models of computation Examples: • Ptolemy II • Metropolis • MetaH

16. Ptolemy II • Berkeley / CHESS / Edgar Lee • Focus on complex embedded systems that mix widely different operations, such as networking, signal processing, feedback control, mode changes, sequential decision making, and user interfaces • Models of computations • Continuous Time • Discrete Events • Distributed Discrete Events • Communication Sequential Processes (CSP) • Discrete Time • Finite State Machine • Process Networks • Synchronous Data Flow & Dynamic Data Flow • Giotto • Synchronous/Reactive • Timed Multitasking • …. • http://ptolemy.eecs.berkeley.edu/ptolemyII/ • Status: Public domain, Version 5.0 Beta released in May 2005

17. Metropolis • Gigascale Systems Research Center (GSRC) • Berkeley + Politechnico di Torino + Cadence • Alberto Sangiovanni-Vincentelli • Design environment for heterogeneous systems • An infrastructure, a tool set, and design methodologies for various application domains • Tools • simulation • synthesis • analysis/verification • Appears to be less homogeneous than Ptolemy II • http://www.gigascale.org/metropolis/ • Status: Released in the open domain in September 2005

18. MetaH • Honeywell • Language and toolset for developing reliable, real-time multiprocessor avionics system architectures • Describe the interfaces and properties of software and hardware components and combine them into an overall integrated system. • Tools for analyzing real-time schedulability, reliability, and partition integrity • Targeting to avionics real-time execution environments • http://www.htc.honeywell.com/metah/ • Status unclear

19. Hybrid System Tools • Continuous + discrete dynamics • differential equations • automata • Continuous systems with • events • switches • modes • Not well suited for modeling real-time computations

20. Hybrid System Tools • Simulation tools • sometimes with automatic code generation • Examples • Simulink + Stateflow • SCICOS • public domain “Simulink” • connection to SynDEx CAD software for rapid prototyping of distributed r-t embedded applications • Modelica/Dymola • Sildex / RT-Builder • based on the SIGNAL language • mathematical foundation • HyVisual • based on Ptolemy II

21. Hybrid System Tools • Formal verification tools • Charon (UPenn) • agents with modes with continuous and discrete behaviour • CheckMate (CMU) • verification toolbox on top of Matlab • threshold event-driven hybrid systems • Masaccio (Berkeley) • formal model for hybrid dynamical systems built from atomic discrete components (difference equations) and atomic continuous components (differential equations) by parallel and serial composition • hybrid automata • Shift (Berkeley) • programming language for describing dynamic networks of hybrid automata • continuous-time phases separated by discrete-event transitions • Hysdel (ETHZ) • describe discrete hybrid automata and generate piecewise affine systems (PWA) • UPPAAL (Uppsala/Aalborg) • integrated tool environment for modeling, validation and verification of real-time systems modeled as networks of timed automata, extended with data types (bounded integers, arrays, etc.). • Others: LSTools, HDV, PHAVer, HyTech, d/dt, Requiem, Ellipsoidal toolbox, HSOLVER, ……

22. Hybrid System Tools • Restrictions necessary in order to apply formal methods, e.g. • timed and hybrid automata – integrators (clocks) with different speed • piecewise affine systems • In addition to the tools mentioned here there are additional tools developed within the Petri Net community

23. Networking tools • Based on tools from the networking community • analyze/simulate communication protocols • analyze/simulate ad hoc networks, e.g., sensor networks • Extended with support for computations and continuous dynamics • Still focused on the networking aspects

24. Networking tools Examples: • ns-2 • most widely used wired/wireless network simulator • movement models for mobile applications • OMNeT • TOSSIM • TinyOS sensor network simulator • TinyOS code + ZigBee networks • NAB (Network in A Box) • large scale sensor networks • Network/control cosimulation tool (Branicky) • based on ns-2 • extended with continuous dynamics to model plants • Ptolemy 2 • extended to suppotr wireless sensor networks • …..

25. Real-Time Scheduling • Scheduling simulators and/or microprocessor simulators/emulators extended with networking and/or continuous dynamics • Examples: • RTSIM (Pisa) • extended with continuous dynamics (OCTAVE) • SIMICS (Virtutech) • software emulation on various target models • extended with networking support

26. Control-Based Tools • Basis in continuous control & dynamics • Extended with support for computing and communication • Often based on Matlab-Simulink • Examples • TrueTime (Lund) • Co-simulation of rt-kernels, networks and continuous plant dynamics in Simulink • Jitterbug (Lund) • Analysis of control performance subject to timing variations • Matlab • AIDA Toolset (KTH) • Matlab/Simulink-based environment for model-based codesign and analysis of real-time control systems • support for timing analysis • XILO (KTH) • related to AIDA • also supports fault injection

27. Outline • Introduction • JitterBug – statistical analysis of how timing affects control performance • TrueTime – simulation-based analysis of how timing affects control performance

28. Jitterbug • Matlab-based toolbox for analysis of real-time control performance • Evaluate effects of latencies, jitter, lost samples, aborted computations, etc on control performance • Analyze jitter-compensating controllers, aperiodic controllers, multi-rate controllers • Calculation of a quadratic performance criterion function • Packaging of existing theory for linear quadratic Gaussian systems and jump-linear systems Developed by Bo Lincoln and Anton Cervin

29. Cost Function Computation

30. Cost Function Computation

31. Cost Function Computation

32. Cost Function Computation

33. Cost Function Computation

34. Cost Function Computation

35. Jitter • What if the delay L is random? • Impossible to obtain closed-form expression for J • Alternatives: • Analysis with Jitterbug • Simulation with TrueTime

36. Jitterbug Analysis • System described using a number of connected continuous-time and discrete-time transfer function blocks driven by white noise Distributed Control Loop: Actuator Plant Sensor Controller

37. Jitterbug Analysis • The execution of the blocks is described by a stochastic timing model expressed as an automaton • Each state can trigger one or more discrete systems • Time intervals are represented by discrete probability distributions

38. Jitterbug Model - Example

39. Jitterbug Example Script % Corresponds to zero delay

40. Jitterbug example script

41. Timing model: S(z) 1 K(z) 2 Simple Example • P(s) – Process (Inverted pendulum) • S(z) – Sampler (perfect sampling) • K(z) – Controller + actuator • Lio – input output latency Lio

42. Demo

43. Results

44. More complicated cases

45. Aperiodic Systems • Jitterbug supports both periodic and aperiodic systems • Periodic: • >calccost • Analytical solution, reasonably fast • Aperiodic: • >calccostiter • Iterative computation with possibly very slow convergence

46. Internal Workings (periodic case)

47. Computational complexity (periodic case)

48. Markov Models [0 0.1 0.2 0.3 0.4] Timing Nodes: 1 2 1 1 1 Markov Nodes: 1 2 0.4 0.3 0.2 0.1

49. Markov Models Continuous Dynamics 1 2 Discrete Dynamics

50. Jitterbug Limitations • Only linear systems • Simplistic timing model • Delays assumed to be independent from period to period • Delay characteristics may not change over time • Only quadratic performance measures • Statistical analysis • Assumes that timing distributions are known • No GUI yet