Forum Replies Created
-
Posts
-
For example, the device returns a list of registers A1…A10. And a manufacturer says that this is an array. A driver should create a tag that has length > 1 to support an array. But the current Modbus driver does not support this.
While OPC devices can return data of array types. And the OPC driver also supports this.
Hello,
OPC UA driver in Rapid SCADA 6 can read arrays from the OPC server. On SCADA level each array element is stored in a separate channel. It’s easier to try and watch how it works.
Yes, event has it’s own timestamp that equals to an event creation time. While archive timestamp may be different if the archive uses a writing period. But 20 seconds difference is too big if the archive period parameter is 1 second. I would be OK if the archive writing period is 1 minute for example.
Hello,
If I understand you correctly, the channel 5767 (Output) was created to set the value of the channel 5567 (Calculated).
Try disabling the channel’s 5567 formula. Commands should work in this case. Next, you need to fix CKLP. Could you describe how CKLP should work?
Hi,
May be you need to install OPC Core Components (available on our website).
Also, you should configure access rights in DCOM settings, which can work unpredictable.
OPC DA does not need to specify TCP port.Consider installing the Communicator service on the same machine as OPC server. Communicator can send data to SCADA-Server remotely. And configuration may be simplified.
The examples were added. Check this link.
Hello,
The existing OPC DA driver (DrvOpcClassic.dll) does not support the OPC XML DA standard.
In my opinion, OPC XML DA is a transition standard between OPC DA and OPC UA, so the standard too rare to implement its support.
A timestamp of the event is set by the Server service when the event is created.
A timestamp of the data point may be changed according to the archive writing period. It depends on the archive properties.Hello,
Channel 46804 is not needed.
In the channel 46805 the output formula is justSetData()
The above should work, see https://ibb.co/KqvK15r> migrate all the *.dat files (in v6 format already) into Postgresql database
Currently, there is no ready to use converter. 2 approaches come to my mind:
1. We can develop a converter by a contract.
2. Deploy an additional instance of Rapid SCADA and use Rapid Gate module to transfer data from the additional instance to the main instance of Rapid SCADA.Hi,
> decided to use PostgreSql as only one achieve as main achieve
It’s up to you. However, why don’t you use *.dat format as a secondary to make the system more reliable?
