Forum Replies Created
-
AuthorPosts
-
MikhailModeratorThe old versions are not available for download. Please use the up to date version.
MikhailModerator> The application is not ready. Try again later.
Check the details in ScadaWeb.log
Likely, it’s needed to wait the web app to start.> The requested view is not specified
Please create a new topic to resolve this issue.
MikhailModeratorHi,
Let me know what links are broken to repair them.
If your project < 1000 channels, I suggest to create a new project from scratch. It's possible to simply copy Modbus, OPC settings, and views.
MikhailModeratorHello,
Please check the differences here.
The format of projects and data in the specified versions were not changed. So you can continue using the installed version if you don’t need the features listed in the version history.
MikhailModeratorUsing virtual machines with Rapid SCADA is a good choice.
MikhailModeratorš
MikhailModeratorHi,
Please check this answer.
MikhailModeratorHi,
Please send an email request to get the deprecated release. When you download the project, I strongly recommend to upgrade to the 6th version.December 8, 2025 at 11:03 am in reply to: Errors when migrating existing project to a VMware instance #17387
MikhailModeratorHi,
The Administrator application is run under user account. Possible, it does not have access the project location.
MikhailModeratorHi,
> Channel data has changed fires every time Iām uploading configuration, and another disadvantage
What event is generated on restart?
MikhailModeratorI. Channel data consists of value and status.
2 – value or status changed
3 and 4 – only one part changed.II. Use the HelloWorld project. Set limits for channel 105. Change channel 105 manually step by step, and check the channel status.
MikhailModeratorAs a recap:
– You can send notifications with custom text using the phone book,
– You need to configure commands sent by ACM
MikhailModeratorHi,
Let’s discuss ACM triggers in a new topic. I suppose, it’s possible to find the appropriate type of trigger.December 4, 2025 at 9:25 am in reply to: MQTT Publisher publishes wrong values (e.g., 2.6E-322) instead of OPC DA values #17374
MikhailModeratorHi,
I suggest to enable a detailed log in the data source properties. It allows to check published data.
Log files can be found in Communicator – Logs.
Screenshots are needed to help you.
MikhailModeratorTo use a phone book, see the available commands in the driver description on the Drivers page.
-
AuthorPosts