[Mikhail]

We’ve published Rapid SCADA 6 RC1 on the official website. It is stable and can be used in projects. For final release we need more docs and modules.

[Mikhail]

Projects for Rapid SCADA 5 and 6 have different structure. Before using an old project for new Rapid SCADA, the project has to be converted. We will provide a project converter app later.

the RAM drive needs to be set up, is this a necessary step?

If you use SSD, using RAM drive is important to save SSD’s life.

How much will the performance decrease if I don’t use a RAM drive but a hard disk?

We have not measured it. RAM drive is needed to avoid much of writing to SSD.

If I use a RAM drive, will I lose log files after a power outage? Or is the RAM drive just caching ?

Some RAM drive apps allow to save files on shutdown. My favorite is ROG RAM Disk.

[Mikhail]

The plugin list uses the external REST API, so if rapidscada.net is temporary unavailable, the list may not display.

[Mikhail]

To get the error details, press F12 in browser and check the Console and Network tabs.
Plugin list displayed there is the same as http://rapidscada.net/scada/plugins/Store/StorePublic.aspx

[Mikhail]

rapidscada_6.0.0~rc1 released.
RC stands for Release Candidate, meaning this release is very close to a full release. Help in testing the installer and the applications is appreciated.

[Mikhail]

Communicator/ is a sub topic of Communicator with a zero-length sub level topic ‘. Maybe the trailing “/” should be left out.

“Communicator/” is used in conjunction with other topic parts, for example Communicator/line001/device001/Sin

You should tick the Detailed log checkbox in the data source properties. The file DrvDsMqtt_XXX.log contains information about sending data, for example:

2022-11-02 11:35:16 Send Communicator/line001/device001/Sin = -0.5229836122997832
2022-11-02 11:35:16 Send Communicator/line001/device001/Sqr = 1
2022-11-02 11:35:16 Send Communicator/line001/device001/Tri = 5.255433325000013
2022-11-02 11:35:16 Send Communicator/line001/device001/DO = NaN

[Mikhail]

So does the MQTT data source publish data or not?

[Mikhail]

I guess that mean it working.

Yes.

I will double check my previous instance setup

For testing, you can set Module to ModArcBasic for MinCopy.

I have some question, why not current data?

All InfluxDB points have timestamp.

What does read only option mean ?

This is kind of lifehack to read data from an archive that is written by another ScadaServer. This option ensures that the data is not affected.

Can I disable file backends if I use influx?

Yes. In this case I suggest to use ModArcInfluxDb for Cur, Min and Hour archives. Otherwise, Webstation settings should be updated.

[Mikhail]

Hello,
The question is duplicated.

[Mikhail]

Hello,
If you have issues with displaying the above data, please provide screenshots.

Can I export this excel data via WebStation?

Yes, Webstation allows to export historical data to Excel.

[Mikhail]

maybe it should be highlighted in the document regarding these data types

You right. Currently, the documentation for v6 is not ready. Nuances of the algorithms should be added to the docs.

[Mikhail]

@zzz, do you get data from Communicator to ScadaServer successfully?

[Mikhail]

Let me try later today since I have my own Mqtt server locally and on the cloud.

@kumajaya, if you already have tried the MQTT publishing data source, could you share the experience?

[Mikhail]

Writing of 0 data points completed successfully in 1 ms
It looks like no channels are associated with the archive.

[Mikhail]

InfluxDB2 is supported.
In ScadaServer.txt there are statuses of archives. Is the MinCopy archive displayed as ready?

In ScadaServer.log how many channels for archiving? For example
Number of active channels for archiving: 271

[Author]

Posts