[Mikhail]

Hi,

Yes, you can use archive replication for this purpose.
Command example for database export

cmd=ExportArchive
startDT=2022-12-23 10:00:00
endDT=2022-12-23 11:00:00

[Mikhail]

Note that the above works in Rapid SCADA 6.

[Mikhail]

🙂

[Mikhail]

According to the log, TCP server is waiting for incoming connections, but no client is trying to connect.
Is Rapid SCADA installed on a cloud server or in the local network?

[Mikhail]

Make sure that you copied PlgChartPro.xml and PlgChartPro_Config.xml into the project.

[Mikhail]

Also try to connect to Communicator by any TCP client utility. You should see that a connection is established.

[Mikhail]

Hello Ibrahim,

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

Make sure that the modems are configured to initiate a connection to the TCP server.

[Mikhail]

I recommend to upgrade Rapid SCADA to the latest version.

[Mikhail]

Thank you.

[Mikhail]

Device status is available. Each device in Communicator contains a hidden tag with the code Status
If you create a channel, specify the device and tag code (Status), the device status will be received in this channel. 0 – normal, 1 – error

Line status currently cannot be received by a channel. To implement this, there should be a channel number in the line options. But it looks ugly. We should find a better idea.

[Mikhail]

Hi,
Saving data every minutes generates 1440 slices per day.
So, there are 1440 * 850 * 2688 = 3 290 112 000 data points.
Therefore the archive size is big.

[Mikhail]

Could you share the final settings? It can be useful for other users.

[Mikhail]

Hi,
How many slices in a day? How many days?

[Mikhail]

Hi,
Create only 1 subscription, named Voltage (delete 2 others). The subscription should contain 3 sub items (3 lines).

[Mikhail]

Hi,
You need subitems as Voltage L1, Voltage L2 and Voltage L3. And only 1 subscription,

[Author]

Posts