Forum Replies Created
-
AuthorPosts
-
MikhailModeratorOn Linux, the web app tries to load a plugin after you activate it in the Administrator app and upload the project for execution. Check ScadaWeb.log for details.
MikhailModeratorHello,
Make sure that a plugin is copied in the valid location. For example,
C:\Program Files\SCADA\ScadaAdmin\Lib\PlgMimExtraComp.View.dll
The Administrator application looks for DLLs in that location.July 6, 2026 at 12:39 pm in reply to: ModArcPostgreSql always connects to port 5432 instead of configured PostgreSQL p #18120
MikhailModeratorI hope, together we could resolve this issue. I really want to help.
July 6, 2026 at 12:36 pm in reply to: ModArcPostgreSql always connects to port 5432 instead of configured PostgreSQL p #18119
MikhailModeratorHello,
Could you please explain where the PostgreSQL connections created by Manage Connections are actually stored?
They are stored in ModArcPostgreSql.xml in the Server configuration.
https://ibb.co/6jGy0gZAll my PostgreSQL instances use the default port. If you have a widely accessible PostgreSQL instance, I could try to connect to it.
-
This reply was modified 5 days, 2 hours ago by
Mikhail.
July 6, 2026 at 12:32 pm in reply to: [Release] Communication Drivers Collection for Rapid SCADA v6.0 #18118
MikhailModeratorHello Ketut,
The current naming is accepted. It’s clear and unique.
Could you fill out the form to add the drivers to the Store (one submit per driver)?July 3, 2026 at 12:36 pm in reply to: [Release] Communication Drivers Collection for Rapid SCADA v6.0 #18113
MikhailModeratorDoes the Sig part refer to the package name, author, or something similar?
July 3, 2026 at 12:33 pm in reply to: [Release] Communication Drivers Collection for Rapid SCADA v6.0 #18112
MikhailModeratorHello,
This is great news!
We will be glad to add those drivers to the Store. Please check the requirements for driver naming. We use suffix related to the author’s name to avoid driver name duplication.July 3, 2026 at 12:27 pm in reply to: ModArcPostgreSql always connects to port 5432 instead of configured PostgreSQL p #18111
MikhailModeratorHello,
Should I create a dedicated connection here (for example using server 192.168.1.4:15432) and disable “Use default connection”?
Or should ModArcPostgreSql always use the default connection defined in ScadaInstanceConfig.xml?
Both are possible.
Deployment profile stores the connection options for itself only. Try changing the connection string in ScadaInstanceConfig.xmlJuly 2, 2026 at 7:23 am in reply to: ModArcPostgreSql always connects to port 5432 instead of configured PostgreSQL p #18107
MikhailModeratorHello,
Does ModArcPostgreSql in version 6.2.2.1 always use the default PostgreSQL port (5432)?
You can change the port in ScadaInstanceConfig.xml
Try set
Server to 192.168.1.4:15432
or specify the ConnectionString parameter.Is there another configuration location for the archive modules where the PostgreSQL port must be configured?
It is possible to add connections in the archive options. I would suggest using ScadaInstanceConfig.xml
MikhailModeratorDone.
MikhailModeratorI’ll check it.
Thanks.
MikhailModeratorFixed.
June 26, 2026 at 12:29 pm in reply to: Communicator error “unable to read data packet header” #18098
MikhailModerator> Stop the Communicator service
> Service control command failed
The above messages indicate that Communicator is taking too long to stop.> 2026-06-25 15:00:10 [webserver][root][WARN] Following communication lines are still working: 2
This one similar.What does line #2 do?
It should be optimized.
MikhailModeratorThank you for the update.
MikhailModeratorNow it is clear. It’s looks like CRC displaying should be fixed.
Thanks. -
This reply was modified 5 days, 2 hours ago by
-
AuthorPosts