The singularity error identifies the block in which the problem occurs (e.g.Integrator), however, the problem initiates in other part of block which finally causes singularity in integrator. What are the troubleshooting tips and tricks that can help identifying the underpinning causes?
When working in simulink the debugging can be done by checking each block independently along with the interconnections, starting from the block indicating error and going back to the first one. The singularity can be caused in case of division by 0 somewhere in the simulink diagram.
Any ways if you are solving a dynamic system which seems to be the case then the selection of step size and type of sovler becomes critical for solution to converge. so you can try different solvers or may reduce the step size to achieve convergence. If the sytem of dynamic equations is stiff then the you need to choose stiff ODE solvers.
When working in simulink the debugging can be done by checking each block independently along with the interconnections, starting from the block indicating error and going back to the first one. The singularity can be caused in case of division by 0 somewhere in the simulink diagram.
Any ways if you are solving a dynamic system which seems to be the case then the selection of step size and type of sovler becomes critical for solution to converge. so you can try different solvers or may reduce the step size to achieve convergence. If the sytem of dynamic equations is stiff then the you need to choose stiff ODE solvers.
While working with simulink, especially for dynamic systems having small parameter values such as micro dc motors or the like, the singularity issue could occur while integrating as certain values might evaluate to NaN or zero. One way out of this problem is to change from using a PID controller supplied by Matlab and switch to one designed yourself or a different controller that leaves out an integrator e.g. fuzzy logic controller
- Badges
- Science topic