Forum Replies Created
-
Posts
-
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.When a device is disconnected, channel status = 0. You should also store status in the database, or use status to convert values to NULL if status is zero.
Hi,
There are 2 independent tasks:
1. Get data from OPC DA.
2. Provide data as OPC UA. Rapid SCADA 6 is needed for this.To solve the 1st task, use usual configuring sequence, as written above. In case of errors, please provide screenshots of the settings and logs.
After the 1st task is done, ask about the 2nd,
Hello,
In the connection options of the Communicator B you should specify the Server A.
It would be more efficient if you provide screenshots of your settings.Hello,
API provides access to channel data by channel numbers. Channel names are not unique, so cannot be used to get data.Getting channel data using REST API by some unique string codes can be a good idea for the future improvements. Currently, you need an internal dictionary that provides channel number by its name or code.
Hello,
I think, you need 4 instances in the project:
– Default
– Remote1
– Remote2
– Remote3The instances are declared in the project, and deployed on different machines.
In Rapid SCADA all data uses UTC timestamps. Some databases (like PostgreSQL) have special data type to work with timezone, some databases don’t have such data type.
If actual timestamps always differs by timezone offset, it’s OK and can be corrected in the SQL request.Hi,
I recommend use the same Tag Code and Topic parameters.
You don’t need to create commands under the Command node.
If a subscription is created and not read only, a value can be published.I suggest trying broker.mqtt-dashboard.com for testing.
