[Mikhail]

Backward compatibility is provided for data archives.
You need to update all files, not only binaries.

[Mikhail]

it asks me in addition to the IP address and port of the server, the address of the device (from 1 to 247) and the number of the register.

Default TCP port is 502 for Modbus. Address is 0 in your settings. But I suggest to change it to 1. Register addresses are shown in the Modbus template on your screenshot.

[Mikhail]

Hi,
Thank you for your positive feedback.
I strongly recommend to upgrade to Rapid SCADA 6. We significantly improved Modbus Slave driver to make it easier to configure. Is it possible for you to upgrade and then discuss the up to date version?

• This reply was modified 1 year, 9 months ago by Mikhail.

[Mikhail]

Hi,

Server 5 and Server 6 must use different TCP ports to be able to work in parallel. Client applications should connect to a proper TCP port.

[Mikhail]

Hi,

does updating from 6.1 to 6.3 require data imigration ?

Projects are compatible. Project migration is not needed.

How to pack souce rapidscada code project to installation .exe file setup ?

Build the source code according to the instructions. Then copy the files from your build output to the necessary folders.

[Mikhail]

Please provide screenshots of the Administrator app version and the module version when you select the module in the Administrator.

• This reply was modified 1 year, 9 months ago by Mikhail.
• This reply was modified 1 year, 9 months ago by Mikhail.

[Mikhail]

Likely, it should be connected to the Linux server where the Communicator service is working.

[Mikhail]

Hi,
According to the logs, Rapid SCADA 6 works well. But you open Rapid SCADA 5.
Try http://localhost:10008 (by default)

[Mikhail]

You can set Modbus ID in the device options (Communicator app). Unit ID = 1 is the most popular. Could you provide screenshots of your settings?

[Mikhail]

Hello,
Could you clarify your question by providing screenshots?

[Mikhail]

Hi,

Probably, you can. The project format and communication protocol are compatible.

• This reply was modified 1 year, 9 months ago by Mikhail.

[Mikhail]

We upload the latest version of the applications and modules on the website. If you need a certain version of a module, use Module Store.

[Mikhail]

Check this link.

[Mikhail]

I noticed the ModAutoControl config file is empty, could this be causing the error?

Yes, this is the cause of the error. Make sure that the module version is compatible with the Rapid SCADA version. I recommend to update the both by downloading them from our website.

You need to restore the module configuration from a backup copy. A file copy also can be found at SCADA\ScadaServer\Config (working copy of the configuration)

[Mikhail]

Hi,
To use REST API you should connect to the web application. The Server application supports custom TCP-based protocol. See this link for more details.

[Author]

Posts