[Mikhail]

Hello,
Open command window on the other PC and type the command:
ping 192.168.1.101
Does the ping work?
This is not SCADA issue, but network issue.

Also try http://192.168.1.101
Does it work?

Make sure that TCP port 80 is opened for incoming connections by the server firewall.

[Mikhail]

Hi Josef,

You need to create appropriate functions in Formulas table, create input channels of calculated type which use these functions and then define the input channels for an dynamic picture components of the scheme.

Creating functions required programming skills. You can purchase the development of the functions or do it by yourself and ask me general questions about it.

[Mikhail]

Hi,
It’s not a problem.
See this answer https://github.com/RapidScada/scada/issues/38

[Mikhail]

If you create a module for SCADA-Server, you can use PassCommand() method within the module.
If you create a driver for Communicator, you can use CommLineSvc.PassCmd() method to send command to a device that is bound to the same communication line.

[Mikhail]

Hello,
Please provide more information how data are transferred from PostgreSQL to Rapid SCADA?

[Mikhail]

It’s true.
Kurlekar, if you need to speed up development of the required feature, you can be a sponsor of this feature.

[Mikhail]

Hello,
If you choose the fore color “Status” for the dynamic text, its behavior becomes similar to table view.

[Mikhail]

It seems fthe following formula doent work properly

Hello,
Please clarify what do you mean?

[Mikhail]

Sometime the received data are incorrect. You can check it by http://modbus.rapidscada.net/ or any other Modbus parser. I recommend to try increasing a delay after request in Communicator (Request Sequence tab). Probably the polling speed is too fast for the particular device and network.

[Mikhail]

Hi,
First of all, create a new topic and provide screenshots and logs.

[Mikhail]

Also check that Communicator is connected to SCADA-Server.

[Mikhail]

Data are not lost. The values equal 0 from 12am to 12pm.
The next time when the issue repeats, you need to check communication line log in Communicator and find out the cause of the error.

[Mikhail]

Hi,

It would be great if you tell about the progress of your work in this forum topic.

[Mikhail]

Please provide the necessary screenshots.

[Mikhail]

You need to choose the correct parameters in your Modbus template in the Communicator app. Set correct type of register and byte order. Try the empty and 2301 byte order.

[Author]

Posts