Dismiss Notice
Join Physics Forums Today!
The friendliest, high quality science and math community on the planet! Everyone who loves science is here!

Reference Input for State Space Controller

  1. Mar 7, 2013 #1
    In the design of a State Space controller using state feedback the input to the plant is given as (where [itex]y=x[/itex] & [itex]D=0[/itex]): [tex]u=-Kx[/tex]
    1zztv.png



    If there is a "reference input" then it would be:
    [tex]u=-Kx+r[/tex]
    20k3evk.png


    So the state feedback without the reference input simply drives all of the state variables to zero. When there is a reference input do the state variables get driven to match the values of the reference input?
     
    Last edited: Mar 7, 2013
  2. jcsd
  3. Mar 7, 2013 #2
    Introducing a reference input in state-space design is a somewhat larger topic than in classic SISO theory. How you choose to include the reference input in the control topology can change the process dynamics considerably (especially when you include an estimator).

    The question is very broad. Don't you have a good book on state-space design?
     
  4. Mar 7, 2013 #3
    Yes, but I can't find a good explanation of how the reference input works. I was trying to ask a very general question. Let me ask a very specific one instead.

    My question is in regards to the section of "Adding precompensation" on this page:
    http://ctms.engin.umich.edu/CTMS/index.php?example=InvertedPendulum&section=ControlStateSpace

    I am confused about how after they add the precompensator they claim that "...the steady-state error of the cart's position has been eliminated". (I am referring to the third graph on the page).

    If you look at the graph before that one the cart stabilizes at about -3mm (I think that means 3mm to the left). Then after they add the precompensator the cart stabilizes at 200mm (to the right?)!

    How did that get rid of the steady state error? Is this a mistake?
     
  5. Mar 7, 2013 #4
    Notice at the top where they list their design criteria, the objective is to adhere to some performance specifications for a 0.2 m step input. The third graph shows it settling to 0.2 m, as it should.
     
  6. Mar 7, 2013 #5
    But before they add that it only deviates 3mm from the initial point, which is much less than 200mm. Am I interpreting the graphs correctly: the cart moves to the left -3mm in the second graph, and to the right 200mm in the third graph?
     
  7. Mar 7, 2013 #6
    You're missing the point. They _want_ it to go to 0.2 m, so the steady state error in the second graph is terrible (0.2 m - 0.003 m = a lot).

    It's much better in the third graph as it settles to 0.2 m, i.e. there's no steady state error.
     
  8. Mar 7, 2013 #7
    Okay, so this brings me back to my original question. Is the goal of a reference input to drive the state to the point that matches the input?
     
  9. Mar 7, 2013 #8
    Well, yes - the process state or output. The point of introducing the reference input is to have the process track it somehow. Did you have an other idea of what is what for?
     
  10. Mar 7, 2013 #9
    No, that is what I thought, but I wasn't sure. So for my application I am implementing the control system described on that page - but I want all of the states to go to zero, even after a step input (bumping the cart).

    So do I just play around with that Nbar precompensator value until I get the steady state response of the cart to zero?
     
  11. Mar 7, 2013 #10
    That whole 'adding precompensation' step is one of the control topologies you can use to introduce a reference input, but why do you want the system to be able to track a reference if you're not going to use it for anything? You could of course just do the design as they show and set r to the zero vector.

    If you just want a regulator design that can reject disturbances, then you only need to do regular old full-state feedback with pole placement. I'd be very suprised if your book doesn't have a section/chapter on it.
     
  12. Mar 7, 2013 #11
    That is what I thought, but my professor has argued with me about how I need a reference input. So I simply set the reference input to zero - i.e. just leave the reference input out?

    So how would you suggest I account for a step input? Does the state feedback already account for that, or does it only account for the instabilities within the modeled plant?
     
  13. Mar 7, 2013 #12
    I might have misunderstood what you meant here - I thought you meant a step input as in a disturbance which the regulator should reject.

    Let me just get something straight then - do you want the system to be able to track a step input with zero steady state error? If so, then you need to use the design from the page you have linked or some other topology that includes a reference input.
     
  14. Mar 7, 2013 #13
    I want the system to stabilize the pendulum while keeping the cart toward the center of the track.

    So it needs to balance the pendulum in its inverted state and if you tap the cart the pendulum needs to stay stabilized. That's it.
     
  15. Mar 7, 2013 #14
    Then all you need is full-state feedback with pole placement.

    What do you mean by this though?
     
  16. Mar 7, 2013 #15
    When you bump the cart. That is what I am referring to as a step input.

    Sorry for the confusion.
     
  17. Mar 7, 2013 #16
    Alright, so no need for tracking. They use LQR design for pole placement in the page you have linked to - maybe you should stay clear of that for now to keep things simple.

    The design procedure you need is straightforward and covered in any decent book on state-space design - usually in the first couple of chapters.
     
  18. Mar 7, 2013 #17
    So where in the block diagram does the step input actually occur if I don't want to track it?
     
  19. Mar 7, 2013 #18
    At the reference input - I assume its 'r' in your second block diagram? Seems you just added it like you would with a classic SISO system.

    Just use your first block diagram, you don't need the reference input. And again, I'd really recommend you have a readthrough of some basic state space design first.
     
Know someone interested in this topic? Share this thread via Reddit, Google+, Twitter, or Facebook




Similar Discussions: Reference Input for State Space Controller
  1. State space (Replies: 3)

Loading...