Forum Replies Created
-
Posts
-
In the case of using Modbus RTU you need to create virtual serial port. The most of converters including Moxa supports creating virtual serial ports.
Probably, Moxa converts Modbus RTU to Modbus TCP and the data exchange is correct as you show in the first sample, so you don’t need RTU.Auto create channels feature doesn’t work for Modbus, unfortunately. The reason is that Modbus devices can contain different set of tags. You need to create channels manually. Use existing channels as templates. It is possible to clone them.
12 should be entered in Address field of Devices table using SCADA-Administrator.
40832 should be entered in the device template using SCADA-Communicator as described in the article.Each energy meter is a device (a one row in the appropriate table of DB).
Address column should contain a Modbus address (or ID) of a device.
Call number is filled by IP address for Modbus TCP or left empty for Modbus RTU.Object is a logical entity. For instance, a building or a house. Yes, it helps grouping of data and doesn’t affect communication with devices.
A one object is enough for test purposes.Dear Joel,
Step by step instructions are described in this article. If some details are not clear, ask about the particulars in the topic.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?
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.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.Firstly let’s realize a delay in SCADA-Communicator.
Then I’ll describe other kinds of possible delays, OK?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.
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?I understand your idea. To be honest, I had the same thoughts. But it is not supported. The other approach is preferable. Most likely SCADA-Web would contain a system of visual components those implement dynamics.
