[Mikhail]

Hi,

The described features sound good!

Some thoughts:
1. Develop based on v6, not v5, as v5 will be deprecated soon.
2. When we talk about UI, provide design mockups or examples based on existing 3rd party apps.
3. If new schemes are not compatible with the existing, use another file extension and view type to be able to use standard and yours schemes in parallel.

[Mikhail]

But what is the standard place to get the logs if they are not on the RAM Disk ?

If log directory is not specified in ScadaInstanceConfig.xml, logs are written in subfolders under applications, for example, SCADA\ScadaServer\Log

[Mikhail]

Hi,
Answer is here. Additional configuration is not necessary.

[Mikhail]

Hi,

You can find the URL in Logs, DrvDsOpcUaServer_*.log
For example, opc.tcp://mycomp:62541/RapidScada/DrvDsOpcUaServer

[Mikhail]

You can find file formats here. The source code also available. If you need getting data directly from archives, I suggest using PostgreSQL or InfluxDB archives.

[Mikhail]

Hello,
SCADA-Server uses port 10000 by default.

[Mikhail]

Hello,
When The application is not ready. Try again later. is displayed, the details are written in the log file. Did you configure RAM disk for logs? Try to find logs directly on the disk.

• This reply was modified 3 years, 2 months ago by Mikhail.

[Mikhail]

Hi,
No, because OPC DA is a Windows technology only.
You can install SCADA-Communicator (and Agent) on Windows machine and interact with it from RPi.

• This reply was modified 3 years, 2 months ago by Mikhail.

[Mikhail]

Yes, staging branch is important. I don’t know what is implemented in the staging branch that makes the app work.
You should put the files listed in the errors. ScadaAdmin_Wine.zip contains only executable file, but the Administrator app needs other files which should be taken from the installation package.

[Mikhail]

Hi,
Please provide screenshots of the module settings and the module log.

[Mikhail]

Hello,

If the last question is about Automatic Control Module, please ask in a proper topic. This topic is about Telegram driver.

[Mikhail]

As a result you should be able to open a TCP connection to IP 172.40.0.10 port 502 by any application: Communicator, Hercules, Telnet, etc.

[Mikhail]

It’s a network issue. Ping uses another protocol than TCP.
You should check a network configuration. Something like this.

[Mikhail]

Looks like 172.40.0.10:502 is not available from the VM.
You could also download Hercules utility and try to connect by TCP client. I expect that result will be similar.

[Mikhail]

Should the virtual machine have an IP address within the same range of the physical meter to establish communication?

This is not obligatory, and depends on the router settings. Could you copy a part of communication line log? Ctrl + C works in the Administrator app.

[Author]

Posts