[Mikhail]

If the most of data are converted correctly, the current project issues should be fixed.

[Mikhail]

Hello,
See ScadaServer.log to check if the Server app works correctly or not.
Also see ScadaComm.log to check Communicator status.

[Mikhail]

Hi,
I also get the error with that GIF image.
The problem is caused by the image size (15MB), it’s too big.
We will investigate this issue when move Scheme Editor to .NET6 framework. Unfortunately, I cannot provide the exact date. Try to reduce the image file size.

[Mikhail]

Hi,

What error occurred?

[Mikhail]

You should find the cause of the error and fix the 1st request.
If the Modbus driver cannot get data, a communication session is interrupted.

[Mikhail]

Hi,
What Linux version do you use?
May be you should try Rapid SCADA 6 that uses .NET6 instead of Mono.
How to build the project.

[Mikhail]

Hi,

In case a project contains less than 100 channels, sometimes it’s easier to enter them from scratch. 750 channels require project conversion.
I suggest using the above manual to convert your project to v5.8.4. Later you can port the project to v6.

[Mikhail]

I will post the update in this topic.

[Mikhail]

That’s true, the reuired files are missing in the archive.
It will be fixed the next week. Please wait for an update.
Thank you for reporting the issue.

[Mikhail]

Right, there are 2 links: the plugins for Rapid SCADA 5 and Rapid SCADA 6.
Which one do you use?

[Mikhail]

Hi,

1 and 3. Decode the packets using https://rapidscada.net/modbus
When you copy data to the form, split the received data.

2. Send and Receive are the operations performed by the driver.
7/7 means that 7 bytes read and 7 bytes required.

[Mikhail]

Make sure that VS is run as administrator.

[Mikhail]

Thank you. I can check it the next week.

[Mikhail]

You should download the plugin for proper version of Rapid SCADA.

[Mikhail]

I’m glad that now it works.
Thank you for update.

[Author]

Posts