- This topic has 17 replies, 2 voices, and was last updated 9 years ago by
.
-
Posts
-
SCADA-Communicator has a delay respect to the server (which is also in my computer) more than a second. I have changed “Delay after request cycle, ms” to 0 and “Delay” to 0 in “Request Sequence”, it improves a little but still delays very much.
I have checked the server connection with other OPC client, and it runs quickly, at the same time as the server.
Is there some method to speed up the data receive with SCADA-Communicator from the OPC server?
The server receive the signals from a simulation device software. Then I connect SCADA-Communicator to the server and finally I open a Quick client (server tool) connected to the server which shows me the signals from the simulation.
The quick client values changes simultaneously to the simulation software, but the values showed in SCADA-Communicator changes with delay. I have checked the options of the server and I select the scan mode: Respect client specified scan rate, so there should not be any kind of delay.
The server I use is Toolbox OPC Power Server 5.16.
Please compare the moment of receiving new data using Communication Line Log page of SCADA-Communicator. In this page incoming data are shown as soon as they received.
What will be the difference beetween the applications if you measure in the described way?Also try setting Update rate field for a data group in Device configration form that appears by clicking Properties item of device popup menu in Communicator.
I can’t find “Update rate field for a data group”. In Device popup menu there is not any kind of rate field. The only fields I see for read data in device configuration form are: name, path, active checkbox, is array checkbox, channel and signal.
I have noticed that the delay is composed by two delays: one between the server and SCADA-Communicator and the other between SCADA-Communicator and SCADA-Web.
Respect to SCADA-Web I have created a dinamyc picture that appears or desappears depending on the value of a boolean variable (1 or 0), so, when SCADA-Communicator changes in some variable, the respective picture changes its status but with some delay.
Firstly let’s realize a delay in SCADA-Communicator.
Then I’ll describe other kinds of possible delays, OK?Perfect!!!! Sincronization OPC Server and SCADA-Communicator is totally solved.
It remains to solve the delay SCADA-Web with SCADA-Communicator. As I told before, the dinamyc pictures changes with delay respect to SCADA-Communicator signals.
Great! Could you share how did you solve the issue?
SCADA-Web interacts with SCADA-Server, not SCADA-Communicator.
The default SCADA-Web data refresh frequency is 5 seconds. It is set in SCADA-Web Configurator. The minimum value is 1 second. So you can change the refresh rate.Full sincronization achieved!
Sincornization OPC Server and SCADA-Communicator:
– In SCADA-Communicator -> Line 2 “OPC” -> Communication Line Parameters tab -> Communication parameters -> Delay after request cycle,ms = 0
– In SCADA-Communicator -> Line 2 “OPC” -> Request Sequence tab -> Select the OPC device -> Delay = 0
– In SCADA-Communicator -> Line 2 “OPC” -> Right click on the device -> Properties -> Select the read data folder created which contains the signals -> Update rate, ms = 0Sincronization SCADA-Web and SCADA-Server:
-In SCADA-Web Configurator -> Application tab -> Data refresh frequency, sec = 0
Doing the previos, I reached no delay between the OPC Server and SCADA-Web.
Please check load of your CPU. Probably, setting 50 ms delay in Request Sequence tab is a good idea.
Data refresh frequency that equals 0 works within schemes but does not work within table views.Yes, the CPU load is 100% the whole time I am receiving data from OPC server. But, setting the delay to 50 ms, the result stais practically the same, however, the sincronization reduces significantly. I have to say, that my PC hardware is not very powerfull.
I think that using more powerfull hardware will not solve the problem. Any application has to do a delays those allow other applications operating.
Did you set 50 ms delay into Request Sequence?What protocols are used by your devices? May be it is better to develop native drivers instead of OPC?
- You must be logged in to reply to this topic.