Hello Temptanner, Each front panel object update is called a "message" to the remote panel server. The client has to be able to keep up with the messages that the server is sending. There is a maximum message backlog that the server will allow that is configured with the following setting:
RemotePanel.MaxMsgBacklog =3D n By default, n =3D 500. You can increase this by adding the above line manually in your server-side INI file, making n > 500. However, this will only increase the amount of time before the failure. The best way to solve this problem is to modify your RT code to reduce the number of messages being generated in a given amount of time. Each of your many property nodes generates a relatively large number of messages. You may need to change the code to only read or write the property when absolutely necessary, perhaps not every iteration. Also, if you have a graph that gets updated every iteration of a loop running at, say, 100 iterations per second, you may consider coding this so that you accumulate 100 points of data and write it to the graph only once per second. This actually would apply to any control or indicator. Perhaps once per second is too slow, but generally you will need to lower the frequency of the front panel control and indicator access. If none of these suggestions help, or if I=92m not correctly understanding your issue, please post the software and versions you are using, the applicable portions of your code, and any other information that may help, and I=92ll be happy to look further into it. Have a nice day! Robert M Applications Engineer National Instruments