Problem with Section 7.1 Task 5 of Simscape onramp
Show older comments
Although I correctly configured the model blocks and parameters accordingly to the directions, the training evaluation said my output did not match the answer. It prevents me from proceeding to the next task.
Here I attach two snapshots of the evaluation plot of Section 7.1 Task 5 where the problem occured.
The first picture shows comparison of the signals spanning to the end time (10sec). It looks to me exact agreement between the requirement and my signal, but it indicates slight discrepancies in the beginning of simulation (from 0 sec to around 1.0 sec) shown by the red dots. Due to these errors, the evaluator says my signal is incorrect.

The second picture zooms into the details of the red dots. It looks to me my signal has a slight delay to the answer.

I confirmed that my setup is consistent with the directions and the results unchanged even after several retries from the beginning of Section 7.1.
I am wondering if there is another parameter to be adjusted, which is not explicitly directed.
Can I have your help for solving this problem?
9 Comments
Jan Kirner
on 16 May 2021
I have the same problem. Best regards.
Lianna Cubias
on 7 Aug 2021
i seem to be experiencing this issue and have consulted many but have failed to find anyone with a solution or explanation as to why this is happening. Your answer for the thread about the problem with Simscape Onramp task 9 helped so can you offer some insight here, please?
Lianna Cubias
on 7 Aug 2021
Figured it out! Finally!
Do tasks 1-5 as instructed. All that is correct. Before running the model in Task 5 try this:
Check the settings on the "Rotational electromechanical converter" block that your "ideal rotational motion sensor" is connected to. Go to the "Variables" tab, check the override box for "Angular velocity" and set priority to "high". Everything else, leave it the way it is. Then run the model. This worked for me because I was having this exact problem.
Philipe Doughty
on 5 Nov 2021
It worked for me by setting the priority of angular velocity to low.
玄人 市川
on 7 Nov 2021
Amanullah S
on 4 Dec 2021
Thank you I too strucked and rectified after giving priority as low
Eric Guil Vidal
on 19 Dec 2021
For me worked setting "low"
Kevin
on 4 Oct 2025
DELETE CONNECTIONS OF IDEAL ROTATIONAL SENSOR AND AGAIN CONNECT THEM

Wisdom
on 28 Feb 2026
None has worked for me!!!!!!
Accepted Answer
More Answers (3)
Orkhan Alikhanov
on 26 Sep 2021
18 votes
It only worked for me after I set priority to "low" in the "Variables" tab of "Rotational electromechanical converter" block.
11 Comments
Douglas Johnson
on 27 Sep 2021
I had to set the priority to "low" and change the constant to 500.3745
Jichao Fang
on 13 Oct 2021
Douglas's solution worked for me.
Puskar Neupane
on 26 Oct 2021
Orkhan solution works for me
Karl Frode Ring
on 27 Oct 2021
Me also
Mohit
on 27 Oct 2021
thanks for the solution, worked for me .
Eric Liu
on 1 Nov 2021
Thank you for the tips, it works for me
Philipe Doughty
on 5 Nov 2021
It worked for me by setting the priority of angular velocity to low.
玄人 市川
on 7 Nov 2021
俊 井
on 11 Dec 2021
Me too.
Shafie Mohamed Shafie Hassan
on 27 Jan 2023
yes , set the Angular Velocity in the 'variables' section of 'rotational electro mechanical converter'MAT
that should work
[R2021b]
Alisha Schor
on 11 Feb 2022
Edited: Alisha Schor
on 11 Feb 2022
1 vote
If possible, please update to R2021b, Update 1 or newer. This should resolve the issue without having to change any block settings.
An error will occur that resets the values of the PID block.
Change the PID back to PI.
Change the Proportional (P) value from 1 back to 1e-6.
Change the Integral (I) value from 1 back to 5e-3.
Change the Sample Time (-1 for inherent) from -1 back to 0.05.
This glitch is frustrating. I question the Previous solutions.
Categories
Find more on Simulink in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!