10.07.2015 Views

Lab Proposal for Integrated Real-time and Control - DCS - UPC

Lab Proposal for Integrated Real-time and Control - DCS - UPC

Lab Proposal for Integrated Real-time and Control - DCS - UPC

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

8Fig. 10.(a) Overshoot controller with/withoutjitters(b) Overshoot controller eliminatingthe jitter problemOvershoot controller: degradation <strong>and</strong> solutionObservation 12: The problem presented above <strong>and</strong> its solutioncan be split into several tasks, like analysis <strong>and</strong> modellingof the new control algorithm, implementation of the controlalgorithm, etc. An interesting issue is how synchronized actuationinstants can be <strong>for</strong>ced in the kernel. For example, asolution could be to use a periodic task <strong>for</strong> computing u k <strong>and</strong>another periodic task <strong>for</strong> applying u k at the required <strong>time</strong>.Another solution could be to en<strong>for</strong>ce synchronized executionsat the kernel level, using the EDF tick counter. Moreover,since different solutions to the jitter problem such as [29]or [30] could have also been applied, students more confidentor interested in specific fields can select the solution that bettermeets their preferences.IV. TENTATIVE WORK PLAN AND ITS APPLICATION TO ASPECIFIC COURSEThe previous section has detailed some of the steps requiredto successfully carry out the lab activity presented in this paper.This section summarizes them in order to propose a tentativework plan that is divided into several sessions, each one beinga two-hour lab.S1 - Introduction: Introduction to the activity, <strong>and</strong> simulationof the open-loop response after obtaining the statespace<strong>for</strong>m of the RCRC circuit from the circuit differentialequations (1) (consider r<strong>and</strong>om values <strong>for</strong> R <strong>and</strong> C). Here itis assumed that state-space notation is chosen.S2 - Problem specification (a): This session should beused to specify the problem in terms of the levels <strong>for</strong> thereference signal <strong>and</strong> <strong>for</strong> discrete controller design, whichincludes selecting the sampling period <strong>and</strong> closed loop polelocations, if pole placement is used. Other control approaches,like optimal control, could also be used.S3 - Problem specification (b): To complement the previoussession, observers should also be designed <strong>and</strong> simulated.The outcome of this session should be the complete simulationsetup.S4 - Basic implementation (a): Build the RCRC circuit<strong>and</strong> verify its dynamics in open-loop. Start the controller implementationin a periodic hard real-<strong>time</strong> task in the processingplat<strong>for</strong>m.S5 - Basic implementation (b): Finish the controllerimplementation <strong>and</strong> test its correctness.S6 - Multitasking (a): Incorporate a noisy task in thesimulation setup to evaluate the effects of jitter. This stepwould require to use, <strong>for</strong> example, the TrueTime simulator.S7 - Multitasking (b): Incorporate the noisy task in theimplementation <strong>and</strong> validate the previous simulation results.S8 - Advanced implementation (a): If degradation in controlper<strong>for</strong>mance is detected in the previous session, simulateadvanced control algorithms or adopt real-<strong>time</strong> techniques tosolve or reduce the jitter problem.S9 - Advanced implementation (b): Implement the previoussolutions <strong>and</strong> validate them.Note that the program timing, layout <strong>and</strong> the set of coveredtopics should be adapted to particular needs/background of thetarget audience or to the goals of the specific curriculum. Forexample, the proposed activity has been introduced as a partof the curriculum of the 2-year master degree on Automatic<strong>Control</strong> <strong>and</strong> Industrial Electronics in the Engineering Schoolin Vilanova i la Geltrú (EPSEVG) of the Technical Universityof Catalonia (<strong>UPC</strong>) [34]. In particular, since 2007, theexperiment was tailored to become part of the laboratory <strong>for</strong>the <strong>Control</strong> Engineering course, which covers continuous <strong>and</strong>discrete linear <strong>time</strong> invariant (LTI) control systems, as well asnon-linear control systems, all using state-space <strong>for</strong>malism.Sessions S1 to S5 were adopted <strong>for</strong> the laboratory of thediscrete LTI control systems part.The <strong>Control</strong> Engineering course can be followed by studentseither in the first semester of the first year or in the firstsemester of the second year. Students choosing the secondoption simultaneously attend a course on real-<strong>time</strong> systems.There<strong>for</strong>e, within the same classroom, not all the students arefamiliar with real-<strong>time</strong> systems. To overcome this apparentdrawback, teams of three students were <strong>for</strong>med containing atleast a student with competence on real-<strong>time</strong> systems. Withinsuch heterogeneous teams in terms of skills <strong>and</strong> theoreticalbackground, it was observed that students took their responsibilities<strong>and</strong> team-work was significantly improved.As in every course edition, after finishing the discrete LTIcontrol systems part, a short <strong>and</strong> simple questionnaire is givento the students to let them evaluate several aspects of this partof the course. The question Do the laboratory activities permitto better underst<strong>and</strong> the theoretical concepts? is the only onerelated to the laboratories. Looking at the students answers,<strong>and</strong> taking into account that be<strong>for</strong>e introducing the presentedexperiment the lab activities were focused on the simulation of

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!