Forum Replies Created
-
Posts
-
There are 2 different issues.
1. Lock of ScadaComm.txt file. Try deleting the existing file, so it will be automatically recreated.2. Browser error. Could you switch to the Network tab of the tools to check which request causes the error?
Note that in the screenshot of the device data, the tag is not bound to the channel. It is incorrect. You should not change channel data type manually.
Hi,
SVGs containing JS are not tested.
You could open the browser tools pressing F12 to check the errors.I mean get channel value and status in your database. After that play with SQL functions to set channel value to NULL if status = 0.
Hi,
It changed in Rapid SCADA 6, see the example https://ibb.co/zXj9HCN
Hello,
What username is written in the Communicator log?
If the port exists, but cannot be open, you would get another error message.
Could you copy here a part of communication line log?SQL functions should be used. First of all, get the correct raw data. Then try using SQL functions to add some processing.
Hello,
I recommend to use the same Rapid SCADA project for all instances (servers).
Also you need to configure the Agent service on the remote server by providing correct instance name instead of Default.Hi,
You can use Automatic Control Module to send commands (write data to the target OPC server) on incoming data change. It would require to add a trigger for each channel.
If you have a lot of channels, the above methods is not comfortable to configure, and some custom solution is preferable.
Hi,
You should check the configuration and log files of DB Export module.
Current data and events are exported independently.Hi,
Some thoughts:
– Server v5 requires a lot of RAM when trends (charts) are requested by a user.
– Is it possible to check what amount of RAM was consumed by the Server service when it was killed?
– 218 MB of free memory is not big. If possible, add memory to the server.
– Rapid SCADA 6 uses systemd daemons. Consider moving to v6 in the future.
