Group Abstract Group Abstract

Message Boards Message Boards

Either SystemModelLinearize or TransferFunctionModel does not work for this model

Posted 1 year ago
POSTED BY: Fabián Peña
2 Replies
Posted 1 year ago

Dear Sergio,

Thank you very much for your reply.

Your suggestion of constraining the motion of the springs in the vertical direction using prismatic joints worked out of the box, without having to adjust anything else other than connecting them and defining the direction of motion. Furthermore, in my original model, it also fixed some warnings about the initial conditions. Also, the mathematical expressions of the transfer functions that were correct, were greatly simplified.

Just for the record, the model that I shared was already some sort of minimal example. The original model is part of a package, with classes that favor the usage of many of instances of the same kind, with many inputs and outputs. Somehow, I was not getting an obvious miscalculation when the number of springs was small. The problem began after increasing the number of components. Somehow, the complexity made the problem evident.

Thank you very much again.

Cheers,

Fabián

POSTED BY: Fabián Peña

You can look at the model DocumentationExamples.Control.CameraStabilizer for help here, specially if, and I'm guessing here, but you seem to be interested in the forces all being aligned along the z axis, so introducing them through prismatic constraints would help, as is done in the model I mention above. This model also has input forces, similarly constrained, and it does some initialization of the system, that I think may be affecting your model. And it forces some state selection through stateSelect = StateSelect.always that may be helpful. If this does not work, consider making a smaller minimal model indicating precisely what you expect in the linearization.

POSTED BY: Sergio Vargas
Reply to this discussion
Community posts can be styled and formatted using the Markdown syntax.
Reply Preview
Attachments
Remove
or Discard