Remote Client - Communication Issues

Hello--

My setup has a remote client that is on a connection with a more limited connection than the other clients.  We believe this is causing periodic issues that result in #COM for the clients SCADA runtime values.

Does citect provide a way to prioritize its processes over all other processes, so that overhead comms (for example) wouldn't saturate the link?

Or maybe you have another solution I can look into that is a better fit?

Please let me know if there is any more information needed.

Thank you

Parents
  • Hi Jacob,
    You could look at increasing the [LAN]Delay parameter to see what impact this has on network usage.
    Another option is to convert this remote station to use RDP type solution instead (Remote Desktop Services, RDP Web Client or CitectAnywhere), so it is just the highly compressed picture from the Server that is sent over the wire. But this will require a change to your licensing and setting up infrastructure to host the Server RDP components.
Reply
  • Hi Jacob,
    You could look at increasing the [LAN]Delay parameter to see what impact this has on network usage.
    Another option is to convert this remote station to use RDP type solution instead (Remote Desktop Services, RDP Web Client or CitectAnywhere), so it is just the highly compressed picture from the Server that is sent over the wire. But this will require a change to your licensing and setting up infrastructure to host the Server RDP components.
Children
No Data