| Author |
 Topic  |
|
|
Julien
1 Posts |
 Posted - 19 May 2006 : 02:43:15
|
First, sorry for my bad English. I live in Belgium and It’s not easy to speak English for me. I hope that you will understand my question.
I have read in your documentation that it’s the graph should be rended to the screen at a frame rate of 10 updates/second. It’s the maximum value? If i have a lot of multi-channel scrolling plots on a same window, this speed is always possible?
When I use RTXYPlot example and that I replace the function javax.swing.Timer(300, new Action….) by javax.swing.Timer(100, new Action….), I don’t see a difference, the display is always jerked and I think that the speed of the update is fonction of the dimension of the window. I have the same problem with polygraph. example.
|
|
|
quinncurtis
1586 Posts |
Posted - 19 May 2006 : 09:02:06
|
The speed of the update is dependent on many, many, factors, including the speed of the underlying computer, the speed of the specific graphics card or chip used in the computer, the number of data points that are displayed in the graph, the number of historical values carried in the RTProcessVariable objects, the complexity of other elements in the graph, the size of the display, and other tasks being carried out by the computer. If you are using Windows you can get some idea of the maximum rate you can expect by running the program and looking at the Task Manager to see what percentage of the CPU usage is dedicated to the program. If it is 80-90% then you are probably close to the maximum update rate.
Even though the display may not be as smooth as you like with only 3-updates/second, keep in mind that you are not losing data. The RTProcessVariable objects holding the historical data can be updated asynchronous with the the display. This means that you can update the RTProcessVariable objects orders of magnitude faster than the display updates. The display updates will always reflect all of the most current data. |
 |
|
| |
Topic |
|
|
|
speed of update
