Forum Replies Created
-
AuthorPosts
-
September 4, 2024 at 11:36 am in reply to: How to Implement Custom Data Interaction Between Server and WebStation #15298
MikhailModeratorYou right. For more details check this link if you haven’t found it yet.
Is your custom data like channel values or events? If custom data similar to channel data, it can be encoded into channel data, and then retrieved using existing application protocol. If custom data similar to events, you can use the Data field of events to extend events.
Currently, there is no option to process new request types from a Server module. It can be a good idea for the future.
MikhailModeratorHi,
Widget width can only use relative quantities from 1 to 12, because the plugin is based on Bootstrap grid system, which makes widgets stretchable.
If you need a fixed size, try a Frame component from Extra Scheme Components.
MikhailModeratorHi,
Please make similar screenshots of your system as you can found in this topic.
MikhailModeratorHow many data points you need to collect per minute or second?
MikhailModeratorI suppose, you should develop a driver for the Communicator application. Collected data then transferred by Communicator to Server, which writes it to the archives.
Check this article. In the driver, you can use a connection provided by Communicator engine, or open serial ports from your code.If you need to poll all ports in parallel, each port will relate to its communication line that uses a separate thread.
MikhailModeratorHello,
If TCP port 10002 is used by another application, the Agent service cannot open it. Agent provides data for the Administrator app.
Check the ports by TCP View utility, and check ScadaAgent.log
MikhailModeratorHi,
Could you provide an example of a data packet or protocol description?
MikhailModeratorMake sure that you download ASP.NET Core Runtime Hosting Bundle.
August 30, 2024 at 12:03 pm in reply to: Modbus TCP No sending command for write new value to slave device #15267
MikhailModeratorGood 🙂
MikhailModeratorPlease expand the Sites node and make a new screenshot.
Also make a screenshot similar to this.August 29, 2024 at 11:38 am in reply to: RS5 Interface and Config db must be common for all deployed Instances? #15263
MikhailModeratorThis discussion may contain sensitive information. So email the details of the system architecture and what services based on Rapid SCADA do the end customers pay for. It helps me to find the best solution.
MikhailModeratorAlso check ScadaAgent.log for more details.
MikhailModeratorTo fix the current error, you should check if all configuration directories exist or not. May be some Rapid SCADA apps are not installed. You can just create configuration directories for them.
MikhailModeratorWhile upgrading to version 6 takes some effort, it’s worth it. The v5 is frozen since 2022. The good fact is that v5 and v6 can work in parallel on the same computer, so you can keep v5 running as long as needed.
-
This reply was modified 1 year, 7 months ago by
Mikhail.
August 28, 2024 at 10:37 am in reply to: RS5 Interface and Config db must be common for all deployed Instances? #15255
MikhailModeratorIf remote Raspberries belong to the same client organization, it’s OK to send the user table with password hashes (v6).
If they are different customers, may be consider using different main servers for them, or create separate projects and then merge into the main project in order to hide other client’s configuration. -
This reply was modified 1 year, 7 months ago by
-
AuthorPosts