*banner
 

Ramifications of software implementation and deployment: A case study on yaw moment controller design

Citation
"Ramifications of software implementation and deployment: A case study on yaw moment controller design". IEEE American Control Conference (ACC), July, 2015.

Abstract
Automotive controllers are often first designed in a simulation environment using continuous time models of the controller and vehicle plant. Unfortunately, the controller's implementation in software and deployment onto a microcontroller has ramifications for performance and cost. In this paper, we use an automotive case study of a yaw moment controller to demonstrate that these ramifications can and should be modeled, investigated, and accounted for early in the design process. More specifically, we evaluate and compare the effects of sampling period, timing delay, jitter, code size, and execution time for three yaw moment controllers, with insights applicable to control design in general.

Electronic downloads

Citation formats  
  • HTML
     <a
    href="http://chess.eecs.berkeley.edu/pubs/1114.html"
    ><i>Ramifications of software implementation and
    deployment:  A case study on yaw moment controller
    design</i></a>, IEEE American Control Conference
    (ACC), July, 2015.
  • Plain text
     "Ramifications of software implementation and
    deployment:  A case study on yaw moment controller
    design". IEEE American Control Conference (ACC), July,
    2015.
  • BibTeX
    @proceedings{15_RamificationsOfSoftwareImplementationDeploymentCase,
        title = {Ramifications of software implementation and
                  deployment:  A case study on yaw moment controller
                  design},
        organization = {IEEE American Control Conference (ACC)},
        month = {July},
        year = {2015},
        abstract = {Automotive controllers are often first designed in
                  a simulation environment using continuous time
                  models of the controller and vehicle plant.
                  Unfortunately, the controller's implementation in
                  software and deployment onto a microcontroller has
                  ramifications for performance and cost. In this
                  paper, we use an automotive case study of a yaw
                  moment controller to demonstrate that these
                  ramifications can and should be modeled,
                  investigated, and accounted for early in the
                  design process. More specifically, we evaluate and
                  compare the effects of sampling period, timing
                  delay, jitter, code size, and execution time for
                  three yaw moment controllers, with insights
                  applicable to control design in general.},
        URL = {http://chess.eecs.berkeley.edu/pubs/1114.html}
    }
    

Posted by Mary Stewart on 16 Sep 2015.
For additional information, see the Publications FAQ or contact webmaster at chess eecs berkeley edu.

Notice: This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright.

©2002-2018 Chess