[Mikhail]

Hi,
To export historical data from Rapid SCADA to XML, a converter application should be developed. Another method is export PostgreSQL archive as written here.

[Mikhail]

Does your device include MQTT broker, or it is an MQTT client?

[Mikhail]

dotnet-install: .NET Core SDK with version ‘6.0.406’ is already installed.

May be you need to uninstall .NET Core before new installation.

[Mikhail]

Hi,
Please create a new topic for the new question and provide the details.

[Mikhail]

Hello,
Log files should be in /var/log/scada/
If they don’t exist, check .NET version:
dotnet --info

[Mikhail]

Why do you need websockets instead of usual TCP?

[Mikhail]

The MQTT driver in Rapid SCADA is based on MQTTnet library. On the mentioned web page is written that websockets are supported: “Communication via TCP (+TLS) or WS (WebSocket) supported”. I suppose, to be able to use WS in the driver, the driver should be updated.

[Mikhail]

Hi,

Modbus server does not respond. You should check logs of Modbus server if it provides info.

[Mikhail]

The parameter is in PlgChartPro.xml, not PlgChartPro_Reg.xml. Look for PlgChartPro.xml in the distributive.

ScadaWebConfig.xml, MaxReportPeriod

[Mikhail]

🙂

[Mikhail]

PlgChartPro.xml, parameter MaxFixedPeriod
ScadaWebConfig.xml, parameter MaxReportPeriod

[Mikhail]

Check that AspNetCoreModuleV2 is installed as described here.

[Mikhail]

Also possible that requests are not delivered to RPi by VPN.

[Mikhail]

Hi,
You can connect to the device, but it does not respond. Check that the Modbus device address is correct. Use https://rapidscada.net/modbus to validate the packets: 01 1E 00 00 00 06 0A 03 00 00 00 0A

[Mikhail]

Hello,
Please check the log files of the Server, Communicator and Webstation services.

[Author]

Posts