- This topic has 21 replies, 4 voices, and was last updated 1 year, 1 month ago by
.
-
Posts
-
Please try this update. Does it help?
Hi Mikhail, I tested on the test project I uploaded for half hour each, with and without 1 sec delay on AutoControl. It seems working fine on both settings.
Only need to update the server module, no need to update auto control module?
Only need to update the server module, no need to update auto control module?
Yes. Commands are added to a queue inside the Server service and executed independently. That’s why they are not blocked.
does the above update also applied for linux version?
there is a “ScadaServerSvc.exe” in the zip, but no “ScadaServerMono.exe”does the above update also applied for linux version?
Yes. It’s enough to update the *.dll files. ScadaServerMono.exe is just a shell to run the app.
Hi Mikhail,
Just checking back to see if RS has any progress on this?
This is preventing us from puting RS into serious use at scale.
The instablity makes it infeasible for reliable sync at anything 1s sync rate.I mean adding a delay to a command in the module settings, not to request. If delay is added, commands are added to a queue instead of being sent directly. The queue should protect the server app from hanging.
Just curious, is this queue per output channel, per communication-line, per rule or per module?
Yes it is, see v5.1.4.2
Server update for testing.
The command queue is in the Server service.
- You must be logged in to reply to this topic.