[Mikhail]

Hello,
Please provide screenshots describe you issue. To be honest, I don’t understand the problem.

[Mikhail]

Thank you for the info.

[Mikhail]

Perhaps when prompted in RapidScada need to specify the address of the register + 1

In addition, you can choose addressing (zero based or 1 based) in the template settings.

[Mikhail]

Hi,
A developer of a driver may test it on Linux or not. You should read a description of a driver you need.

[Mikhail]

Hi,
The source code of the default drivers is here.

[Mikhail]

OPC is an additional level that can cause issues. Modbus is clear.

[Mikhail]

Hi,
If it’s possible to use Modbus, I’d prefer Modbus rather than OPC. However, MatLab integration is not typical task.

[Mikhail]

Hi,
You need to specify the IP of the Server into Communicator settings.

[Mikhail]

I can try to fix it using remote connection if you OK with the commercial service. For pricing, please send a request to this email.

[Mikhail]

Hi,
See this.

[Mikhail]

Hi,
You should provide a part of communication line log where we can see the raw data packages from the device. And provide screenshot of the Modbus template.

[Mikhail]

Add a command to your Modbus template, restart Communicator and try the command using the UI of Communicator. When you sure it works, you can add output channel in Administrator.

• This reply was modified 7 years, 11 months ago by Mikhail.

[Mikhail]

Hello,

You create an interesting system.

What Modbus registers do you need to set by a command?
You could try to configure the command as you expect, and if it doesn’t work, post screenshot links of the settings to discuss them.

[Mikhail]

Hi,
If you can’t fix it by yourself, be free to ask.

[Mikhail]

No programmatic limits. You should check performance of your real system.

[Author]

Posts