Why the terminal can work while OrbiSCADA shows timeout

Modified on Mon, 6 Jul at 10:40 AM

Question

The turbine shows timeout in OrbiSCADA, but the remote terminal still connects. Why does OrbiSCADA show timeout if the terminal is working?


Short answer

A working terminal connection does not always mean that the normal OrbiSCADA controller data connection is working. On some installations, the remote terminal and the normal controller data connection use different communication paths between the OrbiCOM-FC communication unit and the turbine controller. This means that the terminal can still work, even if OrbiSCADA is not receiving live data from the controller.


What this usually means

If the remote terminal connects successfully, the issue is usually not a general network, modem, or SIM card related timeout. It normally means that:

  • OrbiSCADA can reach the communication unit
  • The communication unit is online
  • But OrbiSCADA is not receiving data responses from the controller

In this case, the timeout is related to the controller data communication, not the general network connectivity. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article