Forum Replies Created
-
AuthorPosts
-
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, 9 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.
MikhailModeratorI suggest to upgrade to the version 6.
MikhailModeratorScada.ScadaException: Unable to unpack the configuration archive.
This error can occur when you upload the configuration locally on the same computer. It is generated by the Agent service.
Check, may be some directories do not exist.August 27, 2024 at 10:12 am in reply to: RS5 Interface and Config db must be common for all deployed Instances? #15242
MikhailModeratorDespite the high isolation between instances, do you collect data on a central server?
Do remote users connect to their local and the main servers?August 27, 2024 at 10:10 am in reply to: RS5 Interface and Config db must be common for all deployed Instances? #15241
MikhailModeratorProbably, it’s technically possible to filter users that have custom roles based on an object filter (version 6, in the future).
Yes, you need different passwords or different secret keys for application accounts that belong to different instances.
August 27, 2024 at 10:06 am in reply to: RS5 Interface and Config db must be common for all deployed Instances? #15240
MikhailModeratorSpecify the object filter in the deployment profile to skip unnecessary channels and views when upload. I suggest to check the actually uploaded files on the target server.
August 27, 2024 at 10:01 am in reply to: RS5 Interface and Config db must be common for all deployed Instances? #15239
MikhailModeratorHi,
In Rapid SCADA 5, user passwords that stored in the database are not encrypted, which is not safe for the described architecture.
In Rapid SCADA 6, only password hashes are stored in the Users table. So it’s safe to spread the table to several instances. It’s not possible to restore a password from its hash. Users can login to another server, but they have no access to views and other functions.
MikhailModeratorIt’s good that Chinese users have easy access to the video lessons.
MikhailModeratorHi,
Please copy the full error message to this topic. Check C:\Users\_user_\AppData\Local\ScadaAdmin\Log\ScadaAdmin.log for additional error details.
There is no size limits. May be some required folders are missing.
August 26, 2024 at 1:44 pm in reply to: Modbus TCP No sending command for write new value to slave device #15232
MikhailModeratorHi,
Please send a screenshot of the Modbus template that you created in the Rapid SCADA project. -
This reply was modified 1 year, 9 months ago by
-
AuthorPosts