Remote Panel disconnects frequently when over wireless internet

[Priyadarsini]

Hi all,

We use Remote Panel feature to control our application from a different PC connected in the intranet. This works fine when the internet connection between the server & client PCs is through a cable. But when the PCs are connected over wireless internet and when I try to connect to the server LV application from the web-browser of the client, the FP loads but after a few seconds I get a message 'The connection with the server is broken'. What might be the reason for it? Should I do any special settings to make the application work over wireless internet.

Thanks in advance,
Priyadarsini S

[AdnanZ]

I am not sure if your application does work for a few seconds before it gives the error but the following the instructions in the following KB article might help. I would say put a longer wait time in your loops than the one mentioned to see if it works:

Why Do I Get the Message, "Connection With the Server Has Been Broken?"

[Priyadarsini]

Thank you, Adnan. I would like to clarify that it works properly over wired internet even with our time delay. So I am not sure if adding an extra time delay will help solve our issue with wireless internet. Nevertheless we have to experiment more on our application to see if we can add some extra delay. But it is going to be difficult as a lot of data acquisition is involved. It would be very helpful if there is any other workaround/solution. In the meantime I would also check with an increased time delay.

[Priyadarsini · Accepted solution]

One point we noticed for the disconnect is due to the Screen Refresh we perform when a new client connects to the screen. This Screen Refresh gets and sets the properties/values of all the controls/indicators in the FP to make the client also view the same scene. This involves a lot of property read/write. So we made this refresh to happen in stages. Since the FP has a tab control, we update the currently visible page first. Then from the next iteration we update the controls in other pages - page by page. In this way the refresh is distributed across many iterations and the remote client is given enough time to update. This prevented the disconnect - we were able to connect in 1 or 2 attempts.