trasfer function to work space

error incorect number of arguments? how to resolve it?

Answer 1

[Walter Roberson]

You appear to have a simulink model named stepinfo somewhere on your path that is interfering with calling the Control Systems Toolbox stepinfo() functions.

I do not find any simulink model named stepinfo in my R2019a installation. Also, the GSCreatingModelsDT.mlx example does not have any invocation of Simulink, and does not create any variable named simout

You should check

which -all stepinfo

to try to figure out where the stepinfo model is coming from.

Answer 2

[Sergiy Kuzmych]

I dont actually undesrand you. My purpose is to get the output of these two tranfer function and work with this output. For example get characteristics

[Walter Roberson]

Execute the command

which -all stepinfo

You will find a stepinfo SIMULINK model listed (otherwise you would not be getting the error message that you are getting). Delete or rename that SIMULINK model.

It is normal for the command to list two .m functions for stepinfo, in

toolbox/shared/controllib/engine/stepinfo.m
toolbox/control/ctrlanalysis/@DynamicSystem/stepinfo.m

but on your system there will be a third entry that names a simulink .mdl or .slx file; that .mdl or .slx is interfering with your code.

Answer 3

[Sergiy Kuzmych]

Actually i wanted to take characteristics of tranfer function but i dont know how. I knew about ltiview and i was trying to use this function and i wanted to get the output from my transfer functions but then i discovered linear analysis tool that helped me a lot. The subject is Control engineering from kpi fict auts

Answer 4

[Sergiy Kuzmych]

The answer is to mark lines in simulink like in this video

https://www.mathworks.com/videos/transfer-functions-in-simulink-part-2-extracting-transfer-functions-106147.html

and than use

stepinfo(tout)

and get characteristics

>> stepinfo(out.tout)

ans = 

  struct with fields:

        RiseTime: 80
    SettlingTime: 100
     SettlingMin: 9
     SettlingMax: 10
       Overshoot: 0
      Undershoot: 0
            Peak: 10
        PeakTime: 102

but they are different from previous picute. Why?

[Walter Roberson]

Are you still getting the error message about Simulink model stepinfo being called with the incorrect number of arguments?

[Sergiy Kuzmych]

No

[Walter Roberson]

The original question appears to be solved then, and it is not at all clear to me what your current question is?

I would suggest opening a new question.

I am not experienced in control system use of Simulink, so I will probably not be able to answer