[raizazel]

Hi,

I’ve been able to configure reads from OPC DA using a the OPC DA driver and setting a line in the communicator for that.

After that I’ve set a Data Source of type OPC UA and I’m able to connect to it using UAExpert.

Now I’m worried about losing data in the transformation, I’m running a OPC DA Matrikon Simulation server and some of the data posted runs under 100ms and from the tests I’ve run I’m not able to post to OPC UA consistenly under 100ms.

To check if the simulation server wasn’t the bottleneck I’ve created a simple scripts that uses MQTT to create a triangular signal [-100, 100] that can go up to 1ms and increments 1 by each “tick”. Using MQTT and going through RapidScada results as stable as it should send and recieved the signal without losing points and not much delay. With OPC UA as a publisher it happens the same, anything trying to go sub 100ms starts to get chopped.

Another thing that I wanted to achieve is to store signals into InfluxDB but it bahaves the same as with OPC UA it cannot go under 100ms, I’ve setted it up to be written on change so in principle it shouldn’t be missing data but it does. Am I missing some configuration or is this a hard limit of RapidScada? I’ve tested InfluxDB on its own and is more than capable of running at under 10ms without any issue.

I know that OPC DA is not supposed to go under 100ms but I’m looking at RapidScada not only for OPCDA but also for some future projects that could involve rapid changing signals

Sorry for the long topic and thanks a lot for the support.

[Author]

Posts