This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
is there any option in GUI composer which allows set of update/refresh period ?
Tom
Do you need some thing like this? http://processors.wiki.ti.com/index.php/FAQ_-_CCSv4#Q:_How_do_I_change_the_Realtime_Mode_refresh_rate.3F
I know this setting, however it seems that it does not apply to refresh rate of GUI composer.
Hi Tom,
Add a textbox to your application (aka edit box) and enter this string in "value" binding field "value:pm.$refresh_interval". The interval is in ms, default is 1000ms. Graphs that display arrays have some additional parameters that can be used to further tweak GUI performance as they are most resource intensive widgets. Let me know if you need this and I'll update the wiki with information.
Martin
Hi Martin,
it did not help, refresh is still about 1s. I tried all possible combination of your suggestion.
Hi Tom,
I have created a very simple app that uses F28 simulator with a simple project to draw a graph and also has the refresh interval setting. When I change refresh interval I see the change in graph speed updates. sinewave.zip is a CCS project that contains the target program. You would need to import it into your CCS, Debug project(target configuration file is part of the project and it uses F283x simulator) and then go to Tools->Debugger Options->Auto Run and Launch Options and and check enable "Halt the target before any debugger access" option.
Then open gui composer and import second .zip(modemsim.zip) Use Import Project option in GUI Composer. This contains the sample app. Once it is imported in GUI Composer, run the debugger and click on Preview in GUI Composer. You should see graph changing and refresh interval edit box be set to 1000, changing the value in this box should affect how quickly the graph is refreshed.
You should be able to then check properties of the edit boxes to see if it has same settings as yours.
Martin
Hi Martin,
thanks for help, however I am afraid that enabling of "Halt the target before any debugger access" is not a good idea, especially in motor control application, when generating of output PWM must be precise timing and this behavior depends on interrupt timings.
At least I will try it on real application and I will post result.
Hi Tom,
The example is using simulator. It was the most convenient way of creating a complete sample that should work, thus it needs that option. On HW you shouldn't duplicate the example as is and you are right that option will impact execution of motors. The example was to allow you to compare your settings with what is in the example and see if you can spot a difference that would explain why refresh rate is not working.
Martin