Hi Nandhini,
I understand that angle estimation is erroneous, and it varies only between 0 to 330. It could be due to various factors. Without the actual model, it is difficult to provide an exact answer for the problem but here are some potential causes and troubleshooting steps you can take:
- Configuration of the Hall Decoder and Validity blocks: Double check and ensure that the parameters for the blocks are correctly set and the incoming signals to the blocks are correct. If the validity condition is not met for some angles, it might prevent the Hall Decoder block from updating the angle estimate for those positions.
- Incorrect Number of Pole Pairs: Ensure that the number of pole pairs is correctly set in the Hall Decoder block. If the number of pole pairs is not set correctly, the angle estimation may not cover the full range.
- Simulation Time Step: If the simulation time step is too large, it might miss some transitions of the Hall sensor signals. Try decreasing the simulation time step to see if it captures the full range of angles.
- Signal Saturation and Output Limiting Issues: Check if there is any block in the signal path that might be saturating or limiting the angle output. For example, ensure there is no "Wrap To Zero" block incorrectly configured that might be wrapping the angle before it reaches 360 degrees.
- Other Simulink parameters: Check that the model parameters are correctly set and the simulation parameters like solver type, step size, etc. are appropriate for the system dynamics.
These steps could be a good starting point to troubleshoot your model. To assist you further and to accurately reproduce the issue on my end, it would be beneficial to have access to the model along with the information regarding the parameters and settings currently in use.
Hope this helps!
