Forum Replies Created
-
Posts
-
In addition, this video shows how to connect from the Administrator app, which is installed on Windows, to a Linux instance of Rapid SCADA.
That article is about configuring OPC Classic for Rapid SCADA 5.
> What about the timeout, delay, time, period, string address or host name, name ?
Time and period do not work. Address is ignored. Delay is used internally. I recommend to use the default values.> Also on the TagName thing, for the first time, I need to join two OPCUA string values together.
It would be easier if you get a string in a one OPC UA tag instead of joining channels. Concatenation of string channels is possible, but the formula may be tricky.Hello,
You need to add a new channel of the calculated type with a formula
Val(101) > Val(102) ? 1 : 0
where 101 and 102 the channels to compare.
Then use Automatic Control Module to send command according to the value of the added channel.If you have questions during the implementation of the above solution, send screenshots of your settings.
Hi,
You don’t need to disable firewall. You need to configure it. Allow incoming connections to the TCP port in use.
Please use different topics for different questions. Discussion about scheme components should be in other thread.
Hi,
There is no software limits. However, if you have many connections, you should test if the network is good enough for that.Hi,
Yes, you can use archive replication for this purpose.
Command example for database exportcmd=ExportArchive startDT=2022-12-23 10:00:00 endDT=2022-12-23 11:00:00
According to the log, TCP server is waiting for incoming connections, but no client is trying to connect.
Is Rapid SCADA installed on a cloud server or in the local network?Also try to connect to Communicator by any TCP client utility. You should see that a connection is established.
Hello Ibrahim,
Please provide screenshots of the Communicator settings and the communication line log.
Make sure that the modems are configured to initiate a connection to the TCP server.
Device status is available. Each device in Communicator contains a hidden tag with the code
Status
If you create a channel, specify the device and tag code (Status), the device status will be received in this channel. 0 – normal, 1 – errorLine status currently cannot be received by a channel. To implement this, there should be a channel number in the line options. But it looks ugly. We should find a better idea.
