Forum Replies Created
-
Posts
-
Hi,
It seems that we are close to understanding the cause.
If you restart the PC in usual way, do you get the same error?> Is there a way for me to define what the event says?
The answer depends if you use Rapid SCADA 5 or 6. For version 6, set channel properties:
Input formula would beCnl > 0 ? 0 : 1
Format isOff-OnHi,
1) The error is weird. It’s the first time when we faced this type of error.
What PostreSQL version do you use?2) Probably, it just reconnects. The next time, if the error occurs, try stop and start SCADA-Serve without uploading the project.
Using pgAdmin simply try to connect to the database and open the data tables after the error occurs.Hi Matt,
Thank you for the reminder.
Do you need an example that demonstrates how to create an HTML page that uses JS API to get data (like v5 custom page example)?The OPC UA driver subscribes for data, and receives data in async mode when data comes from the OPC UA server. The driver does not send requests each time to read data.
> in facts it sends all the cycle data in one event type response.
Could you copy the example from the communication line log?OPC DA sometimes unpredictable, unfortunately. While the Rapid SCADA driver uses official .NET OPC libraries, provided by OPC Foundation, they are not ideal.
Is the OPC server installed on the same machine as Rapid SCADA?
What OPC server do you use? (just for information)Please check this video. It should help to connect to OPC UA server. In the video Prosys OPC browser is used. However, any client is OK.
Hi,
You can see that the error isNpgsql.PostgresException (0x80004005): 57P03: the database system is shutting down
You should check the PostgreSQL database. When it is not available from SCADA, try to connect to it by pgAdmin.
It’s weird. Connection is OK. Looks like no device on the line.
Could you check the request sequence? Screenshots can be useful.If you think that the issue depends on the subnet, try other IPs for testing.
