Forum Replies Created
-
Posts
-
Hello,
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.xmlHello,
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
> 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.0xBADD is displayed by the parser in the same order as transferred.
https://ibb.co/tpS0C1Zm
https://ibb.co/v7fyV3SI’ll check the details and come back.
Thank you for noticing.In the above config the EnableFileCommands parameter is true.
So you should see commands in ScadaComm.logHi,
If you mean commands sent from the Administrator application, you should find them in ScadaComm.logRapid SCADA 6.4.7 has been released.
– Communicator API has been updated. Backward compatibility is maintained. Existing drivers do not need to be rebuilt.
– New RS Client Driver for interacting with another Rapid SCADA instance. Useful for publishing calculated channels via an OPC UA server.
– New Redundancy Selector Driver included in the Enterprise edition. This driver selects tag values from one of two devices.
– Fixed bugs in new mimic diagrams.Hi,
If you find a bug, please provide the structured info:
– Testing example
– Expected result of the Modbus parser
– Actual result provided by the Modbus parser
