A likely cause of this issue is from task overruns. A task overrun occurs if the target hardware is still performing one instance of a task when the next instance of that task is scheduled to begin. To determine if you are encountering overruns, please refer to the following documentation page:
This page outlines the process for detecting overruns and some methods you can employ to mitigate them. Please note that an option is to upgrade from the Uno to an Arduino with a more powerful processor, such as the Due.
To get a better understanding of the parts of your model that are causing overruns, you can profile execution time for your model running on the Arduino in PIL. Execution time profiling can be configured with the option Configuration Parameters > Code Generation > Verification > Measure task execution time. Please refer to the following documentation page for more information on profiling the execution of your generated code:
You can use this feature to determine how the various parts of your model that are affecting overruns and the minimal sample time needed to run the model without overruns.
