Runtime Events

[Bang]

Hi. I recently used Rapid for a project and I’ve been setting up a project with a Modbus device.
My only concern is that the tag values and events does not change real time. It takes 50 minutes or so for the Values to change. Do I have to purchase any driver or modules to help me with this?

My Writing Period for Current Data is already set to 1second

[Mikhail]

Hi,
Please provide screenshots of the Communicator settings and communication line log.

[Bang]

Hi,

Please refer to the link for the screenshots.

https://mega.nz/folder/IcoARZaa#_-yVQk5PtjbQ_X0-VjIMtg

Your assistance is much appreciated.
Thanks.

[Bang]

Hi,

I tested it today with all the devices connected, it went well with only 5-8seconds delay on tag real time values.

I previously tested it with only one device simulated, hence the 1 minute delay on tag feedbacks.

If there’s any way to lessen the 5-8sec delay, that’d be better, if none, then that’s that.

[Mikhail]

Hi,

You could try the following:
1. By default, there is a delay 200 ms after each request. You can set it to 100 ms in the device options, for each device.

2. Split the communication line into 2 communication lines. They work in parallel.

[Merdock]

Hello.
As a recommendation to speed up the readings I create a line for each device.
in this way, minimum times of 1 second between readings are achieved.
It is also recommended that you try to get the maximum number of records per request.
The minimum time between readings is 1 second, it is given by the writing in the Current Data file.
The Web interface takes data from this file.
This is in version 5x.
Layers that in version 6 this changed.
The Modbus Driver reads the 16 bit registers without problems.
For reading 32-bit registers, the bit order must be changed in the configuration since it does not transpose the LSBs with the MSBs and Rapid Scada reads the 2 16-bit registers consecutively.
in Default Byte Order you must put 2301.
in most cases, except device specifications.

[Author]

Posts